Scribd Logo
Carica

Benvenuto in Scribd!

  • PTVVisum13 Manual PDF

    Caricato da

    sujatanathv
    198 visualizzazioni2.786 pagine
    The information contained in this documentation is subject to change without notice. Without the prior written permission of PTV AG, this manual may not be reproduced or stored in a retrieval system. The content accuracy is not warranted. We are grateful for any information on errors.

    Descrizione originale:

    Titolo originale

    PTVVisum13_Manual.pdf

    Copyright

    © © All Rights Reserved

    Formati disponibili

    PDF, TXT o leggi online da Scribd

    Hai trovato utile questo documento?

    Questo contenuto è inappropriato?

    Segnala questo documento
    The information contained in this documentation is subject to change without notice. Without the prior written permission of PTV AG, this manual may not be reproduced or stored in a retrieval system. The content accuracy is not warranted. We are grateful for any information on errors.

    Copyright:

    © All Rights Reserved
    Scarica in formato PDF, TXT o leggi online su Scribd
    Segnala contenuti inappropriati
    198 visualizzazioni2.786 pagine

    PTVVisum13 Manual PDF

    Caricato da

    sujatanathv
    The information contained in this documentation is subject to change without notice. Without the prior written permission of PTV AG, this manual may not be reproduced or stored in a retrieval system. The content accuracy is not warranted. We are grateful for any information on errors.

    Copyright:

    © All Rights Reserved
    Scarica in formato PDF, TXT o leggi online su Scribd
    Segnala contenuti inappropriati
    di 2786

    379 9,680 

    0$18$/

    Copyright and legal agreements

    Copyright and legal agreements


    Copyright
    2013 PTV AG, Karlsruhe, Germany
    All brand or product names in this document are trademarks or registered trademarks of the
    corresponding companies or organizations. All rights reserved.
    Cover picture: VBZ
    Legal agreements
    The information contained in this documentation is subject to change without notice and
    should not be construed as a commitment on the part of the vendor.
    Without the prior written permission of PTV AG, this manual may neither be reproduced or stored in a retrieval system, nor transmitted in any form or by any means, electronically, mechanically, photocopying, recording, or otherwise, except for the buyer's personal use as permitted
    under the terms of the copyright.
    Warranty restriction
    The content accuracy is not warranted. We are grateful for any information on errors.
    Imprint
    PTV AG
    Haid-und-Neu-Str. 15
    76131 Karlsruhe
    Germany
    Tel. +49 721 9651-300
    Fax +49 721 9651-562
    info@vision.ptvgroup.com
    www.ptvgroup.com
    www.vision-traffic.ptvgroup.com

    Last amended: Thursday, October 31, 2013 EN-US F

    PTVGROUP

    Contents

    Contents
    Copyright and legal agreements
    Contents
    1 Welcome
    1.1 Fields of Visum application for PrT and PuT
    1.2 Documents
    1.2.1 Manuals
    1.2.2 Online Help
    1.2.3 Tutorials und examples
    1.2.4 More documents
    1.2.5 Typography and conventions
    1.3 Technical information
    1.3.1 Version sizes
    1.3.2 Add-ons
    1.3.3 Hardware and software requirements
    1.3.4 Dongle
    1.3.5 Interfaces
    1.4 How to install and start Visum
    1.4.1 Download and installation of software updates
    1.5 Service & Support
    1.5.1 Usage of manual and FAQ list
    1.5.2 Posting a support request
    1.5.3 Requests to the Traffic customer service
    2 Fundamentals of the program
    2.1 Network model the transport supply
    2.2 Transport demand model
    2.3 Impact models methods to calculate the impact of traffic
    2.4 Analysis of results
    2.5 Comparing and transferring networks
    2.5.1 Comparing version files
    2.5.2 Network merge
    2.5.3 Model transfer files
    2.6 Managing scenarios
    2.6.1 Keywords: project, modification, scenario
    2.6.2 Managing projects efficiently
    2.6.2.1 Creating or selecting a base version
    2.6.2.2 Defining modifications
    2.6.2.3 Defining scenarios based on modifications
    2.6.2.4 Specifying the procedure sequence
    2.6.2.5 Calculating scenarios
    2.6.2.6 Distributing scenario calculations across multiple computers

    PTVGROUP

    1
    I
    1
    1
    2
    2
    2
    2
    3
    4
    5
    5
    5
    6
    7
    7
    9
    10
    10
    10
    11
    11
    15
    16
    17
    20
    21
    22
    23
    28
    31
    31
    32
    34
    34
    35
    36
    36
    36
    37

    Contents

    2.6.2.7 Analyzing and comparing calculation results


    3 Network model
    3.1 Network objects
    3.1.1 Transport systems, modes and demand segments
    3.1.1.1 Transport systems
    3.1.1.2 Modes
    3.1.1.3 Demand segments
    3.1.2 Nodes and turns
    3.1.2.1 Nodes
    3.1.2.2 Turns
    3.1.2.3 Turn types
    3.1.2.4 Turn standards
    3.1.2.5 PrT capacity and PrT turn time
    3.1.3 Links
    3.1.3.1 Link types
    3.1.3.2 Permitted transport systems
    3.1.3.3 PrT capacity, PrT speed and PrT travel time
    3.1.3.4 PuT run time
    3.1.4 Zones
    3.1.5 OD pairs
    3.1.6 Connectors
    3.1.6.1 Distribution of demand of a zone to the connectors
    3.1.7 Main nodes and main turns
    3.1.7.1 Main nodes
    3.1.7.2 Main turns
    3.1.8 Main zones and main OD pairs
    3.1.9 Territories
    3.1.10 Paths
    3.1.11 Stop hierarchy: Stops, stop areas, stop points
    3.1.11.1 Stop points
    3.1.11.2 Stop areas
    3.1.11.3 Stops
    3.1.12 PuT operators
    3.1.13 PuT vehicles: Vehicle units and vehicle combinations
    3.1.14 The line hierarchy
    3.1.14.1 Network objects of the line hierarchy
    3.1.14.2 Specifications of lengths and times
    3.1.14.3 The term timetable in Visum
    3.1.14.4 Data consistency along the line hierarchy
    3.1.14.5 Aggregation of line routes
    3.1.14.6 Coupling time profiles
    3.1.15 System routes
    3.1.16 Points of Interest (POI)
    3.1.17 Count locations and detectors
    II

    39
    40
    40
    46
    46
    48
    48
    50
    50
    50
    51
    51
    52
    52
    53
    54
    55
    56
    56
    57
    58
    59
    60
    60
    61
    62
    63
    63
    64
    65
    66
    67
    67
    68
    68
    68
    74
    75
    76
    76
    77
    80
    81
    84

    PTVGROUP

    Contents

    3.1.18 Toll systems


    3.1.19 GIS objects
    3.1.20 Screenlines
    3.1.21 Junction modeling
    3.1.21.1 Link orientations
    3.1.21.2 Geometries
    3.1.21.3 Signal control
    3.1.22 Network check
    3.2 Spatial and temporal correlations in Visum
    3.2.1 Calendar and valid days
    3.2.1.1 Calendar
    3.2.1.2 Valid days
    3.2.2 Time reference of the demand (time series)
    3.2.3 Time reference of the volumes: Analysis time slots and projection
    3.2.4 Temporal and spatial differentiation of calculation results
    3.2.4.1 Temporal distinction with analysis time intervals
    3.2.4.2 Spatial distinction with territories
    3.2.5 Adjustment of the capacities to the demand values
    3.3 Attributes
    3.3.1 Direct attributes
    3.3.2 Indirect attributes
    3.3.3 User-defined attributes
    3.3.3.1 Formula attributes
    3.3.4 Time-varying attributes
    3.4 Subnetwork generator
    3.5 The surface data model in Visum
    3.5.1 Tables in the surface model
    3.5.2 Multi-part surfaces
    3.5.3 Sharing points between surfaces
    3.5.4 Fuzzy surface alignment
    4 Demand model
    4.1 Demand objects
    4.1.1 Matrices
    4.1.2 Demand segments
    4.1.3 Time series
    4.1.4 Demand models
    4.1.5 Person groups
    4.1.6 Activities, activity pairs, activity chains
    4.1.7 Demand strata
    4.2 Demand modeling procedures
    4.2.1 Standard 4-step model
    4.2.1.1 Trip generation
    4.2.1.2 Trip distribution

    PTVGROUP

    85
    86
    87
    88
    89
    90
    92
    94
    94
    94
    94
    95
    96
    98
    101
    102
    102
    103
    103
    103
    104
    110
    113
    114
    117
    120
    120
    124
    126
    127
    129
    129
    130
    130
    131
    131
    132
    132
    134
    136
    136
    138
    139

    III

    Contents

    4.2.1.3 Mode choice


    4.2.1.4 Nested Mode Choice
    4.2.1.5 Time-of-day choice
    4.2.2 EVA model for passenger demand
    4.2.2.1 EVA data model
    4.2.2.2 EVA trip generation
    4.2.2.3 EVA trip distribution and mode choice
    4.2.3 Activity chain based model (tour-based model)
    4.2.3.1 Tour-based data model
    4.2.3.2 Tour-based model - trip generation
    4.2.3.3 Tour-based model: trip distribution / mode choice combined
    4.2.4 Estimate gravitation parameters (KALIBRI)
    4.2.5 Gravity model calculation
    4.2.6 Iterative repetition
    4.2.6.1 Go to the procedure
    4.2.6.2 Method of successive averages (MSA) over matrices
    4.2.6.3 Method of Successive Averages over attributes
    4.3 Displaying and editing matrices
    4.3.1 Displaying matrices in tabular form
    4.3.2 Displaying matrix values as a histogram
    4.3.3 Comparing matrices graphically in pairs
    4.3.4 Transpose, reflect upper or lower triangle, apply mean value
    4.3.5 Copy, paste and apply diagonal
    4.3.6 Round
    4.3.7 Form reciprocal, raise to power, take logarithm, exponential function
    4.3.8 Maximum or minimum formation
    4.3.9 Make symmetrical: mean value upper / lower triangle
    4.3.10 Calculate the combination of matrices and vectors
    4.3.11 Defining matrices as formulas
    4.3.12 Projection
    4.3.13 Projection of aggregated areas
    4.3.14 Converting zone and main zone matrix into each other
    4.3.15 Extending matrices
    4.3.16 Aggregating matrix objects
    4.3.17 Splitting (extending) matrix objects
    4.4 Matrix correction
    4.4.1 Updating demand matrix with TFlowFuzzy
    4.4.1.1 Methodological basics of TFlowFuzzy
    4.4.1.2 Numeric example for TFlowFuzzy
    4.4.2 Projecting PrT path volumes
    4.4.3 Calibrating a PrT matrix
    4.4.3.1 General principle of the calculation procedure
    4.4.3.2 Example: Matrix projection

    IV

    139
    140
    141
    142
    142
    146
    165
    174
    175
    176
    178
    187
    188
    196
    196
    198
    198
    199
    200
    201
    201
    201
    201
    202
    202
    202
    202
    202
    203
    203
    205
    205
    206
    207
    208
    209
    210
    212
    216
    218
    218
    218
    219

    PTVGROUP

    Contents

    5 Impact models
    5.1 The types of impact models
    5.1.1 The user model
    5.1.2 The operator model
    5.1.3 The environmental impact model
    5.2 Impedance functions
    5.3 Paths in PrT and PuT
    5.4 Skims / indicators
    5.4.1 Skim matrices
    5.4.2 Global indicators
    6 User model PrT
    6.1 Overview of PrT assignment procedures
    6.2 Example network for PrT assignment procedures
    6.3 PrT paths
    6.4 Impedance and VD functions
    6.4.1 Impedance of a PrT route
    6.4.2 Predefined VD functions
    6.4.3 Example of link impedance calculation
    6.4.4 User-defined VD functions
    6.5 Impedances at node
    6.5.1 Node impedances of turns VD function
    6.5.2 Node impedance of nodes VD function
    6.5.3 Intersection Capacity Analysis according to the Highway Capacity Manual
    (ICA)
    6.5.3.1 Uncontrolled nodes
    6.5.3.2 Signalized nodes
    6.5.3.3 Two-way stop nodes
    6.5.3.4 All-way stop
    6.5.3.5 Roundabouts according to the HCM 2010 method
    6.5.3.6 Roundabouts according to the TRL/Kimber method
    6.5.4 Signal time optimization
    6.5.4.1 Data model for SC cycle and green time optimization
    6.5.4.2 Green time optimization
    6.5.4.3 Signal cycle and green time optimization
    6.5.4.4 Signal coordination (Signal offset optimization)
    6.6 PrT skims
    6.7 Distribution of traffic demand across PrT connectors
    6.8 Blocking back model
    6.8.1 General notes on the blocking back model
    6.8.2 Procedure of the blocking back model
    6.9 Convergence criteria of assignment quality
    6.10 Distribution models in the assignment
    6.10.1 The Kirchhoff model in the assignment

    PTVGROUP

    220
    220
    220
    221
    222
    222
    223
    224
    224
    225
    226
    226
    228
    230
    231
    231
    233
    239
    240
    241
    243
    243
    244
    245
    246
    268
    279
    287
    293
    298
    298
    299
    302
    302
    311
    312
    314
    315
    317
    329
    329
    330

    Contents

    6.10.2 The Logit model in the assignment


    6.10.3 The Box-Cox model in the assignment
    6.10.4 The Lohse model in the assignment
    6.10.5 Lohse model with variable beta in the assignment
    6.10.6 Comparison of the distribution models for the assignment
    6.11 Incremental assignment
    6.11.1 Example of incremental assignment
    6.11.2 The procedure of incremental assignment
    6.11.3 Input and output attributes of incremental assignment
    6.11.4 Evaluation of incremental assignment
    6.12 Equilibrium assignment
    6.12.1 Evaluation of the equilibrium assignment
    6.12.2 Introductory example of equilibrium assignment
    6.12.3 Input and output attributes of equilibrium assignment
    6.12.4 The procedure of equilibrium assignment
    6.12.5 Calculation example for the equilibrium assignment
    6.13 Linear User Cost Equilibrium (LUCE)
    6.13.1 Mathematical formulation and theoretical framework
    6.13.2 Local user equilibrium
    6.13.3 Descent direction
    6.13.4 Assignment algorithm
    6.13.5 Input and output attributes of equilibrium assignment (LUCE)
    6.13.6 Persistent storage of bushes
    6.13.7 Start from an initial assignment
    6.13.8 Optimizing the proportionality in the route distribution
    6.14 Equilibrium_Lohse
    6.14.1 Example of the Equilibrium_Lohse procedure
    6.14.2 Input and output attributes of the Equilibrium_Lohse procedure
    6.14.3 The procedure of Equilibrium_Lohse assignment
    6.14.4 Evaluation of the Equilibrium_Lohse procedure
    6.15 Assignment with ICA
    6.15.1 Fundamental principle
    6.15.2 Evaluation of the Assignment with ICA
    6.15.3 Input and output attributes of assignment with ICA
    6.15.4 The procedure of assignment with ICA
    6.15.5 VD functions in assignments with ICA
    6.15.5.1 Used turn VDF
    6.15.5.2 Adjusting the VD functions used
    6.16 Stochastic assignment
    6.16.1 Evaluation of stochastic assignment
    6.16.2 Input and output attributes of stochastic assignment
    6.16.3 The procedure of stochastic assignment
    6.16.4 Similarity of routes and commonality factor

    VI

    331
    331
    332
    333
    335
    336
    337
    338
    339
    341
    342
    342
    343
    345
    347
    350
    351
    351
    354
    358
    361
    363
    363
    364
    364
    366
    367
    371
    373
    374
    374
    374
    376
    377
    380
    383
    383
    384
    385
    385
    386
    388
    391

    PTVGROUP

    Contents

    6.16.5 Example of stochastic assignment


    6.17 TRIBUT
    6.17.1 Input and output attributes of the TRIBUT procedure
    6.17.2 Basics of assignment with toll consideration
    6.17.3 LogN distribution of the random variable VT
    6.17.4 Efficient routes - exclusion criterion in route search
    6.17.5 Route split
    6.17.6 Route balancing in the equilibrium iteration
    6.17.7 Route distribution in the iteration of the TRIBUT Equilibrium_Lohse
    6.17.8 List outputs
    6.18 Dynamic User Equilibrium (DUE)
    6.18.1 Fields of application of dynamic equilibrium assignment
    6.18.2 Overview of the dynamic equilibrium assignment model
    6.18.3 Mathematical framework of the Dynamic User Equilibrium
    6.18.4 Network performance model
    6.18.5 Assignment of network demand (network loading)
    6.18.6 The overall model
    6.18.7 Example of dynamic user equilibrium
    6.18.8 Input and output attributes of dynamic user equilibrium
    6.18.9 References to the appropriate modeling for a DUE assignment
    6.19 Dynamic stochastic assignment
    6.19.1 Evaluation of dynamic stochastic assignment
    6.19.2 Input and output attributes of dynamic stochastic assignment
    6.19.3 The procedure of dynamic stochastic assignment
    6.20 NCHRP 255
    6.21 Assignment analysis PrT
    7 User model PuT
    7.1 Overview of PuT assignment procedures
    7.2 Example network for the PuT assignment procedures
    7.3 PuT paths
    7.4 PuT skims
    7.4.1 PuT skim categories
    7.4.1.1 Skims of time
    7.4.1.2 Skims of length
    7.4.1.3 Monetary skims
    7.4.1.4 Skims of frequency
    7.4.1.5 Skims of attribute data
    7.4.1.6 Derived skims
    7.4.1.7 Examples for skims
    7.4.1.8 Availability of the skims in the PuT assignment procedures
    7.4.1.9 Aggregation to mean skims per OD pair
    7.4.2 Perceived journey time
    7.4.3 Fares

    PTVGROUP

    393
    397
    397
    399
    405
    406
    407
    408
    409
    409
    410
    410
    411
    413
    417
    427
    429
    431
    433
    438
    439
    441
    441
    443
    445
    446
    449
    449
    450
    453
    456
    457
    457
    459
    459
    459
    460
    460
    463
    464
    465
    467
    468

    VII

    Contents

    7.4.4 Temporal utility


    7.5 PuT impedance functions
    7.6 Distribution of the travel demand to PuT connectors
    7.7 Allocation of skims with reference to lines/links
    7.8 Transport system-based assignment
    7.8.1 Evaluation of the transport system-based assignment
    7.8.2 Example for the transport system-based assignment
    7.8.3 Steps of the transport system-based assignment
    7.8.3.1 Route search
    7.8.3.2 Route loading
    7.9 Headway-based assignment
    7.9.1 Evaluation of the headway-based assignment
    7.9.2 Headway calculation
    7.9.3 Generalized costs as impedance
    7.9.4 Choice models for boarding decisions
    7.9.4.1 No information and exponentially distributed headways
    7.9.4.2 No information and constant headways
    7.9.4.3 Information on the elapsed wait time
    7.9.4.4 Information on departure times
    7.9.5 The complete choice model
    7.9.5.1 Extended applicability of the departure time model
    7.9.5.2 Modeling the choice on the basis of estimates
    7.9.5.3 Hierarchical structure of the choice
    7.9.5.4 Example for the choice models
    7.9.6 The search in general
    7.9.7 Example for the headway-based assignment
    7.9.8 Coordination
    7.9.8.1 Function of coordination groups
    7.9.8.2 Matched transfers
    7.9.8.3 Example for the coordination
    7.9.8.4 Assume coordinated time profiles to be undistinguishable
    7.10 Timetable-based assignment
    7.10.1 Evaluation of the timetable-based assignment
    7.10.2 Connection search
    7.10.2.1 Connection search using Branch and Bound
    7.10.2.2 Connection search using shortest path search
    7.10.3 Connection preselection
    7.10.4 Impedance and Perceived journey time (PJT) of a connection
    7.10.4.1 Perceived journey time
    7.10.4.2 Temporal utility of a connection
    7.10.4.3 Fare
    7.10.5 Connection choice
    7.10.5.1 Distribution of trips over connections
    7.10.5.2 Independence of connections

    VIII

    468
    468
    469
    470
    471
    472
    472
    473
    473
    473
    473
    474
    475
    476
    480
    481
    483
    483
    484
    486
    486
    487
    487
    488
    491
    492
    495
    495
    496
    496
    497
    498
    499
    499
    499
    501
    502
    502
    502
    504
    505
    505
    505
    506

    PTVGROUP

    Contents

    7.10.5.3 Example for the connection choice


    7.10.6 Handling of public transport systems of the PuT-Aux type
    7.10.7 Opening of the timetable-based assignment: Export/Import of connections
    7.10.7.1 Use case (1): External choice / Connection import
    7.10.7.2 Use case (2): Connection export
    7.10.7.3 Use case (3): Using existing connections for the search
    7.10.7.4 File format for connection import and export
    7.10.7.5 Consistency check during connection import
    7.10.8 Capacity restriction
    7.10.8.1 How the procedure works
    7.10.8.2 Calculation of Vol/Cap ratio-dependent impedances
    7.10.8.3 Smoothing of impedances
    7.10.8.4 Smoothing of the vol/cap ratios
    7.10.8.5 Distribution of volumes onto alternatives
    7.10.8.6 Distance of the current solution from the balanced state
    7.10.8.7 Termination criteria
    7.11 Assignment analysis PuT
    7.12 PuT passenger survey
    7.12.1 Basic data of a passenger trip
    7.12.2 Passenger onboard survey: Basic approach
    7.12.3 Read survey data
    7.12.4 Plausibilization of survey data
    7.12.5 Assignment of survey data
    8 Operator model PuT
    8.1 Application areas and scope of operations
    8.1.1 Calculation of indicators on different aggregation levels
    8.1.2 Introductory examples for PuT indicators
    8.1.2.1 Indicator data by territory
    8.1.2.2 Territory-based evaluation on different aggregation levels
    8.1.2.3 Indicators at the line hierarchy
    8.1.2.4 Evaluation of indicators on the operator level
    8.1.2.5 Indicator data by time slice
    8.2 Network objects in the Operator model
    8.3 Typical work flow in the PuT operator model
    8.4 Line blocking
    8.4.1 Introduction to the line blocking procedure
    8.4.2 Line blocking application example
    8.4.2.1 Closed blocks according to different criteria
    8.4.2.2 Open and closed blocks
    8.4.3 Data model
    8.4.3.1 Block version
    8.4.3.2 Block
    8.4.3.3 Block item and block item type
    8.4.3.4 Attributes of the line blocking cost function

    PTVGROUP

    510
    512
    513
    515
    515
    516
    517
    521
    521
    522
    523
    524
    525
    526
    527
    528
    528
    531
    532
    533
    535
    535
    540
    541
    541
    542
    543
    543
    545
    546
    549
    550
    551
    552
    553
    553
    557
    557
    565
    568
    568
    570
    573
    575

    IX

    Contents

    8.4.3.5 Downtimes at depots and stop points


    577
    578
    8.4.3.6 Empty trips
    8.4.3.7 Regard running direction
    579
    581
    8.4.3.8 Forced chainings
    8.4.3.9 Line block check
    582
    585
    8.4.3.10 Coverage check
    8.4.4 Line blocking description without vehicle interchange
    585
    8.4.4.1 Partitioning
    585
    8.4.4.2 Construction of the graph
    586
    8.4.4.3 Flow problem solution
    592
    8.4.4.4 Decomposition of the flow into blocks
    592
    8.4.5 Line blocking description with vehicle interchange
    595
    8.4.5.1 Selection principles of vehicle combinations
    596
    8.4.5.2 Solution evaluation via objective function
    597
    8.4.5.3 Parameters and convergence
    599
    8.4.5.4 Consideration of different vehicle combination-specific minimum layover
    times
    600
    8.4.6 Line block display and editing in the timetable editor
    601
    8.4.7 Vehicle requirement and line blocking indicators
    601
    8.4.7.1 Vehicle requirement
    602
    8.4.7.2 Distribution of empty trips and empty times to vehicle journeys
    603
    8.4.8 PuT interlining matrix procedure
    604
    8.5 PuT fare model
    605
    8.5.1 Ticket types
    608
    8.5.1.1 Base fare calculation
    609
    8.5.1.2 Transport system-specific supplements
    615
    8.5.2 Fare systems
    619
    8.5.2.1 "Fare reference" of a fare system
    620
    8.5.2.2 Ticket selection in a fare system
    622
    8.5.2.3 Initial fare and transfer fare
    623
    8.5.2.4 Fare weights
    623
    8.5.3 Fare calculation
    623
    8.5.3.1 Procedure for ambiguous fare systems
    624
    8.5.3.2 Algorithm for fare calculation
    627
    8.5.4 Application of fares
    628
    8.6 PuT operating Indicators
    629
    8.6.1 Example for PuT operating indicators
    630
    8.6.2 Indicators for line route and timetable evaluation
    633
    8.6.3 Measurement of the transport supply
    639
    8.6.4 Measurement of the network performance
    643
    8.6.5 Calculation of operating costs and fare gains (revenues)
    648
    8.6.6 Calculation of the operating costs
    649
    8.6.6.1 Vehicle type-dependent costs
    650
    8.6.6.2 Link costs
    652

    PTVGROUP

    Contents

    8.6.6.3 Stop point cost


    8.6.6.4 Operator cost
    8.6.7 Calculation of the fare revenues (revenue calculation)
    8.6.7.1 Revenue calculation from fixed revenue per passenger trip
    8.6.7.2 Revenue calculation from fixed revenue per traversed fare point
    8.6.7.3 Revenue calculation using the fare model
    8.6.7.4 Revenue distribution
    8.6.7.5 Calculation of cost coverage
    8.6.8 Basic calculation principles for indicators
    8.6.8.1 Projection to the analysis horizon
    8.6.8.2 Example for temporal dependencies of indicators
    8.6.8.3 Aggregation along the line hierarchy
    8.6.8.4 Temporal cut (Time cut)
    8.6.8.5 Spatial cut (Territory cut)
    8.6.8.6 Partially traversed links
    8.6.8.7 Impact caused by couplings
    8.6.8.8 Projection of additional attributes
    9 Environmental impact model and HBEFA
    9.1 Noise volume
    9.1.1 Noise-Emis-Rls90 procedure
    9.1.2 The Noise-Emis-Nordic procedure
    9.1.3 Link attributes for noise calculations
    9.2 Air pollution emissions
    9.2.1 Pollution-Emis procedure
    9.2.2 Pollutant-Emis link attributes
    9.3 Emission calculation according to HBEFA 3.1
    9.3.1 Fundamental principle
    9.3.2 Basics of the HBEFA calculation in Visum
    9.3.2.1 Basis for calculating warm emissions
    9.3.2.2 Basis for calculating cold start excess emissions
    10 GIS functions
    10.1 Connection to the Personal Geodatabase and GIS objects
    10.2 Shape files as a GIS interface
    10.2.1 Importing shape files
    10.2.2 Exporting shape files
    10.3 Intersect
    10.4 Coordinate systems
    10.5 Processing the network display with graphic objects
    10.5.1 Texts
    10.5.2 Legend
    10.5.3 Backgrounds
    10.5.3.1 Dynamic background map
    10.5.3.2 Statically embedding background images by map providers

    PTVGROUP

    655
    656
    659
    660
    661
    663
    664
    668
    669
    669
    670
    673
    674
    675
    675
    676
    676
    679
    679
    679
    680
    680
    682
    682
    684
    685
    685
    685
    686
    688
    691
    691
    692
    692
    694
    696
    705
    707
    708
    708
    709
    709
    710

    XI

    Contents

    10.5.3.3 Backgrounds by Bing Maps


    10.5.3.4 Background images from graphic and GIS files
    10.5.3.5 Supported background file formats
    10.5.3.6 Automatic positioning of the background in the network with World files
    10.5.4 Polygons
    10.6 GPS tracking
    11 Interactive analyses
    11.1 Flow bundles
    11.1.1 Flow bundle definition through selection of network objects
    11.1.2 Flow bundle definition through selection of traffic types
    11.1.2.1 Traffic type flow bundle for active links
    11.1.2.2 Traffic type flow bundle for active PuT lines
    11.1.3 PuT supply filter
    11.1.4 Combining flow bundle criteria
    11.1.5 Flow bundles with alternative routes
    11.2 Isochrones
    11.2.1 PrT isochrones
    11.2.2 PuT isochrones
    11.2.3 Combination of PrT and PuT isochrones
    11.3 Shortest path search
    12 Tabular and graphical display
    12.1 Lists
    12.1.1 List display and entry options
    12.1.2 Specific network object lists
    12.1.3 Matrix list
    12.1.4 Evaluation lists
    12.2 Bars
    12.3 Categorized display with attribute values
    12.4 Labeling with tables
    12.5 Labeling with charts
    12.6 Turn volumes
    12.7 Desire lines
    12.8 Stop catchment areas
    12.9 PuT transfer relations
    12.10 PuT connections and transfer flows
    12.11 Lane allocation
    12.12 2D display
    12.13 Schematic line diagram
    12.13.1 Defining and editing a schematic line diagram
    12.13.2 Display of supply in the schematic line diagram
    12.13.3 Display of demand and transfer flows in the schematic line diagram
    12.13.4 Saving layout information and transferring layouts to variants
    12.14 Signal time-space diagram

    XII

    710
    711
    712
    713
    714
    714
    716
    716
    718
    721
    723
    723
    725
    725
    730
    732
    734
    736
    740
    741
    744
    745
    745
    747
    750
    750
    753
    755
    757
    757
    759
    760
    762
    764
    765
    766
    768
    770
    770
    771
    772
    772
    773

    PTVGROUP

    Contents

    12.15 Column charts


    12.16 Evaluations in the timetable editor
    13 Literature
    List of illustrations
    List of tables
    14 Basics of program operation
    14.1 Program start and start screen
    14.2 Program interface
    14.2.1 Working with windows
    14.2.1.1 Arranging windows via the toolbar
    14.2.1.2 Moving windows
    14.2.1.3 Docking windows together
    14.2.1.4 Removing window docking
    14.2.2 Network window
    14.2.3 Marking window
    14.2.4 Matrices window
    14.2.5 Quick view window
    14.2.5.1 Selecting attributes for the Quick view display
    14.2.5.2 Editing Quick view settings
    14.2.5.3 Saving Quick view layout
    14.2.5.4 Opening the Quick view layout
    14.2.6 The Smart map window
    14.2.6.1 Refreshing the Smart map
    14.2.6.2 Moving the Network editor view
    14.2.6.3 Enlarging and reducing the view of the Network editor window
    14.2.6.4 Specifying a new view of the Network editor window
    14.2.6.5 Enlarging or reducing the Smart map view (zoom)
    14.2.6.6 Shifting view in the Smart map
    14.2.6.7 Setting the graphic parameters for the Smart map window
    14.2.7 Network editor window
    14.2.7.1 Scaled display
    14.2.7.2 Enlarging the view (zooming in)
    14.2.7.3 Reducing the view (zooming out)
    14.2.7.4 Displaying the entire network
    14.2.7.5 Shifting the view
    14.2.7.6 Refreshing the view
    14.2.7.7 Displaying previous views
    14.2.7.8 View by analysis time interval
    14.2.8 The Graphics tools window
    14.2.8.1 Showing the Graphics tools window
    14.2.9 Other windows
    14.2.10 Tool bars
    14.2.11 Modifying toolbars and windows
    14.2.11.1 Shifting tool bars
    PTVGROUP

    775
    776
    784
    787
    795
    803
    803
    804
    806
    806
    807
    807
    808
    808
    810
    810
    810
    811
    812
    813
    813
    813
    814
    814
    815
    815
    815
    816
    816
    818
    818
    818
    819
    820
    820
    821
    821
    821
    822
    823
    823
    823
    824
    824
    XIII

    Contents

    14.2.11.2 Moving the windows Network, Marking, Matrices, Quick view, Protocol, Smart Map and Find/Shift network object
    14.2.11.3 Scaling windows
    14.2.11.4 Showing and hiding windows and toolbars
    14.2.11.5 Hiding a window temporarily
    14.2.11.6 Restoring window settings
    14.2.12 Toggling between windows
    14.3 Shortcuts and functions keys in Visum
    14.4 Opening and saving files
    14.4.1 Opening and saving files separately
    14.4.1.1 Saving a file
    14.4.1.2 Opening a file
    14.4.2 Settings for opening and saving data files
    14.4.3 Editing the storage location of files
    14.4.4 Opening and saving a project directories file
    14.4.4.1 Saving a project directories file
    14.4.4.2 Opening a project directories file
    14.4.5 Opening and saving a version file
    14.4.5.1 Opening a version file
    14.4.5.2 Saving a version file
    14.4.5.3 How to handle matrix data when opening or saving a version file
    14.4.6 Opening and saving a network file and adding comments
    14.4.6.1 Adding comments to the network
    14.4.6.2 Opening a network file
    14.4.6.3 Saving a network file
    14.4.7 Reading network data additionally
    14.4.7.1 Specifying settings for reading in additional network data
    14.4.7.2 Selecting data tables you want to read in
    14.4.7.3 Specifying settings for conflict avoidance and conflict handling
    14.4.7.4 Saving settings for reading additional network data
    14.4.7.5 Opening settings for reading additional network data
    14.4.8 Reading a network file with incomplete line routes or system routes
    14.4.9 Starting with an empty program interface
    14.5 Selecting the direction of traffic
    14.5.1 Selecting the standard unit for direction of traffic in the current network
    14.5.2 Selecting the standard unit for the direction of traffic in the new network
    14.6 Specifying standard units for length and speed
    14.6.1 Selecting the standard unit for lengths and speed in the current network
    14.6.2 Selecting standard units for length and speed in new networks
    14.7 Specifying time periods and points in time
    14.8 Editing user preferences
    14.8.1 User preferences overview
    14.8.2 Saving, opening and restoring user preferences
    14.8.3 Undoing and redoing actions
    XIV

    825
    825
    825
    825
    827
    828
    829
    831
    831
    831
    833
    835
    837
    838
    839
    839
    840
    840
    841
    843
    844
    844
    845
    846
    851
    852
    854
    857
    860
    861
    861
    864
    864
    865
    865
    865
    866
    866
    866
    867
    867
    869
    870

    PTVGROUP

    Contents

    14.8.3.1 Activating the undo command and specifying number of actions


    14.8.3.2 Actions:undoing
    14.8.3.3 Redoing undone actions
    14.8.4 Specifying the size and position of windows
    14.8.5 Selecting a decimal point
    14.8.6 Specifying the number of processor cores to be used
    14.8.7 Registering Visum version as COM server
    14.8.8 Default settings for Visum updates
    14.8.9 Language of the graphical user interface
    14.8.10 Using protocol files
    14.8.10.1 Specifying settings for protocol files
    14.8.10.2 Adding a comment to the activity protocol
    14.8.10.3 Viewing log files
    14.8.10.4 Examples: Protocol files
    14.8.11 Messages window
    14.8.12 Displaying document names in progress dialogs
    14.9 Displaying information about Visum
    14.9.1 General information on Visum
    14.9.2 Displaying details on program and license
    14.10 Enabling or disabling installed add-ons
    14.11 Starting Visum with different settings
    14.11.1 Specifying command line parameters for the start of Visum
    14.11.2 Changes to settings in the configuration file
    14.11.3 Using a different configuration file during program start
    14.11.4 Starting Visum without graphical user interface
    14.12 Comparing and transferring versions and networks
    14.12.1 Comparing versions
    14.12.1.1 Specifying a network name for version comparison
    14.12.1.2 Comparing version files
    14.12.1.3 Using comparison values / set graphic parameters
    14.12.1.4 Copying comparison values to user-defined attributes
    14.12.1.5 Editing version comparisons
    14.12.1.6 Updating version comparisons
    14.12.1.7 Deleting version comparisons or attributes
    14.12.2 Merging networks
    14.12.2.1 Creating a network merge
    14.12.2.2 Setting the graphic parameters for the display of difference values
    14.12.2.3 Displaying merged network values in lists
    14.12.2.4 Saving merged networks
    14.12.3 Creating and applying model transfer files
    14.12.3.1 Creating a model transfer file
    14.12.3.2 Showing the content of a model transfer file
    14.12.3.3 Applying model transfer files
    14.13 Scenario management

    PTVGROUP

    870
    871
    871
    872
    873
    873
    874
    875
    875
    876
    876
    879
    879
    879
    883
    885
    885
    885
    886
    886
    887
    887
    889
    891
    892
    892
    892
    893
    893
    898
    899
    901
    902
    902
    902
    903
    905
    907
    908
    908
    908
    913
    916
    921

    XV

    Contents

    14.13.1 Creating a project for Scenario management


    14.13.2 Editing basic settings of the project
    14.13.3 Editing the base version
    14.13.4 Managing modifications
    14.13.4.1 Creating modifications
    14.13.4.2 Information on uniqueness of IDs in modifications
    14.13.4.3 Editing modifications
    14.13.4.4 Viewing modifications in the Network editor window
    14.13.4.5 Editing the properties of a modification
    14.13.4.6 Specifying the load order of modifications
    14.13.4.7 Checking modifications
    14.13.4.8 Deleting modifications
    14.13.5 Managing scenarios
    14.13.5.1 Creating scenarios
    14.13.5.2 Assigning modifications to a scenario
    14.13.5.3 Opening the network of a scenario
    14.13.5.4 Deleting scenarios
    14.13.6 Specifying procedure parameters
    14.13.6.1 Specifying procedure parameters for the base version
    14.13.6.2 Creating a procedure parameter set
    14.13.6.3 Editing procedure parameter sets
    14.13.6.4 Loading procedure parameters from a file
    14.13.7 Calculating scenarios and showing results
    14.13.7.1 Calculating scenarios locally on a computer
    14.13.7.2 Distributing scenario calculations across multiple computers
    14.13.7.3 Resetting the calculation status of scenarios
    14.13.7.4 Opening a scenario containing calculation results
    14.13.7.5 Showing message and log files of scenarios
    14.13.8 Comparing scenarios
    14.13.8.1 Specifying comparison patterns
    14.13.8.2 Editing comparison patterns
    14.13.8.3 Deleting comparison patterns
    14.13.8.4 Comparing scenarios
    14.13.9 Exporting data of a Scenario management project
    14.13.9.1 Forward project
    14.13.9.2 Saving a scenario as a version file
    14.13.9.3 Saving modifications as a model transfer file
    15 Editing the network
    15.1 Network object types
    15.2 Managing attributes
    15.2.1 Specifying general settings for attributes
    15.2.1.1 Displaying short names or long names of attributes
    15.2.1.2 Specifying settings for the attribute selection windows
    15.2.1.3 Settings for decimal places and aggregate functions

    XVI

    922
    923
    925
    925
    926
    928
    928
    928
    929
    930
    931
    932
    933
    933
    934
    935
    935
    935
    935
    936
    937
    937
    938
    938
    938
    947
    948
    948
    948
    949
    953
    954
    954
    955
    955
    956
    956
    957
    958
    958
    959
    959
    959
    960

    PTVGROUP

    Contents

    15.2.2 The Attributes.xls file


    962
    15.2.3 Accessing attributes
    963
    15.2.4 The window used for the selection of one attribute
    963
    15.2.4.1 Indirect attributes: relation types and aggregate functions
    966
    967
    15.2.4.2 Specifying an alias for attribute names
    15.2.4.3 Preset the analysis time slot
    967
    968
    15.2.5 The window used for the selection of multiple attributes
    15.2.5.1 Adding a group of attributes to the attribute selection
    969
    15.2.5.2 Editing the display properties of attributes
    970
    15.2.6 Managing user-defined attributes
    973
    15.2.6.1 Creating a user-defined attribute
    973
    15.2.6.2 Generating user-defined attributes when reading attributes
    977
    15.2.6.3 Editing attribute values of user-defined attributes
    978
    15.2.6.4 Editing a user-defined attribute
    979
    15.2.6.5 Deleting user-defined attributes
    979
    15.2.7 Managing time-varying attributes
    979
    15.2.7.1 Creating time-varying attributes
    980
    15.2.7.2 Entering and editing time-varying data for time-varying attributes
    980
    15.2.7.3 Deleting time-varying attribute data
    982
    15.3 Editing attribute values of network objects
    983
    15.3.1 The attribute value zero
    984
    15.3.2 Assigning a constant value to an attribute or adding attribute values
    984
    15.3.3 Editing attribute values of set attributes
    985
    15.3.4 Multiplying an attribute value with a factor
    987
    15.3.5 Allocating an attribute value to a different attribute
    988
    15.3.6 Calculating attribute values from the values of other attributes
    989
    15.3.7 Rounding attribute values
    990
    15.3.8 Editing attribute values during a procedure sequence
    990
    15.3.9 Allocating attribute values by intersecting a source attribute
    993
    15.3.10 Exchanging attribute values via the clipboard
    993
    15.3.10.1 Copying attribute values to the clipboard
    993
    15.3.10.2 Pasting attribute values from the clipboard
    994
    15.3.11 Modifying attribute values in the Quick view
    995
    15.3.11.1 Editing attribute values in the Quick view
    995
    15.3.11.2 Editing attribute values in the Quick view with arithmetic operations
    995
    15.4 The operating modes of the network model
    996
    15.4.1 Activating the Insert mode
    996
    15.4.2 Activating the Edit mode
    997
    15.4.3 Activating the Spatial selection mode
    997
    15.5 Finding network objects in the network
    999
    15.5.1 Editing search results
    1003
    15.6 Marking network objects in the network
    1004
    15.6.1 Marking active and passive network objects
    1004

    PTVGROUP

    XVII

    Contents

    15.6.2 Marking only active network objects


    15.6.3 Accessing associated objects in the View menu
    15.7 Using filters to set network objects active or passive
    15.7.1 Opening a filter window
    15.7.2 Specifying filter conditions and applying filters
    15.7.2.1 Specifying a filter condition
    15.7.2.2 Specifying combined filter conditions
    15.7.2.3 Setting filter conditions in brackets
    15.7.2.4 Working with hierarchical filters
    15.7.2.5 Working with relations in filters
    15.7.3 Switching filters on or off
    15.7.3.1 Switching on filters
    15.7.3.2 Switching off individual filters
    15.7.3.3 Switching off several filters at the same time
    15.7.4 Initializing filter conditions
    15.7.4.1 Initializing the filter conditions of a filter
    15.7.4.2 Initializing the filter conditions of several filters
    15.7.4.3 Initializing all filters during a procedure sequence
    15.7.5 Reading and saving filters
    15.7.5.1 Saving filters
    15.7.5.2 Reading filters
    15.7.5.3 Reading filters during a procedure sequence
    15.7.6 Exception: Filter for OD pairs
    15.7.6.1 Opening an OD pair filter
    15.7.6.2 Defining filter conditions for OD pairs and PuT paths
    15.7.6.3 Applying filters for OD pairs
    15.7.6.4 Filtering the traffic between two zones
    15.8 Setting network objects active/passive via the spatial selection
    15.8.1 Selecting network object types for the spatial selection mode
    15.8.2 Setting all network objects passive
    15.8.3 Setting all network objects active
    15.8.4 Setting individual network objects active or passive
    15.8.5 Setting network objects active within a polygon
    15.8.6 Setting network objects active within territories
    15.8.7 Inverting the active/passive state of network objects
    15.8.8 Extending and reducing the spatial selection of network objects
    15.8.9 Saving a spatial selection of network objects
    15.8.10 Reading a spatial selection of network objects
    15.9 Checking the state of network objects
    15.9.1 Checking the state of a network object type
    15.9.2 berblick ber die Zustnde aller Netzobjekte
    15.10 Managing boundaries of polygonal network objects
    15.10.1 Creating a boundary
    15.10.2 Editing polygon points
    XVIII

    1005
    1005
    1008
    1008
    1009
    1010
    1014
    1015
    1016
    1020
    1022
    1022
    1023
    1023
    1023
    1023
    1024
    1024
    1024
    1024
    1025
    1026
    1026
    1027
    1027
    1031
    1032
    1033
    1034
    1035
    1035
    1035
    1036
    1037
    1038
    1038
    1039
    1039
    1040
    1041
    1041
    1042
    1042
    1044
    PTVGROUP

    Contents

    15.10.2.1 Creating polygon points


    15.10.2.2 Shifting polygon points
    15.10.2.3 Deleting polygon points
    15.10.2.4 Merging polygon points of two polygons
    15.10.2.5 Separating merged polygon points
    15.10.3 Creating new faces
    15.10.4 Deleting faces
    15.10.5 Deleting boundaries
    15.10.6 Normalizing all surfaces
    15.10.7 Merging all polygon points with identical co-ordinates
    15.10.8 Fuzzy alignment of surfaces
    15.11 Managing transport systems, modes and demand segments
    15.11.1 Managing transport systems
    15.11.1.1 Creating a transport system
    15.11.1.2 Properties and options of transport systems
    15.11.1.3 Editing the attribute values of transport systems
    15.11.1.4 Deleting transport systems
    15.11.2 Managing modes
    15.11.2.1 Creating a mode
    15.11.2.2 Properties and options of modes
    15.11.2.3 Editing the attribute values of modes
    15.11.2.4 Deleting modes
    15.11.3 Managing demand segments
    15.11.3.1 Creating a demand segment
    15.11.3.2 Properties and options of demand segments
    15.11.3.3 Editing the attribute values of demand segments
    15.11.3.4 Deleting demand segments
    15.12 Managing nodes
    15.12.1 Creating a node
    15.12.2 Properties and options of nodes
    15.12.3 Finding a node
    15.12.4 Selecting nodes
    15.12.4.1 Marking nodes
    15.12.4.2 Setting nodes active/passive
    15.12.5 Editing the attribute values of nodes
    15.12.5.1 Editing the attribute values of a node
    15.12.5.2 Editing the attribute values of marked nodes
    15.12.5.3 Editing the attribute values of all or all active nodes
    15.12.5.4 Displaying the attribute values of a node in a column chart
    15.12.6 Shifting nodes
    15.12.7 Merging nodes
    15.12.8 Specifying major flows at nodes
    15.12.9 Setting the polygon allocation of nodes
    15.12.10 Updating impedances at nodes

    PTVGROUP

    1044
    1045
    1046
    1047
    1049
    1050
    1051
    1052
    1052
    1053
    1053
    1055
    1055
    1055
    1057
    1058
    1058
    1059
    1059
    1060
    1060
    1061
    1061
    1061
    1062
    1062
    1063
    1063
    1063
    1066
    1066
    1066
    1066
    1066
    1066
    1067
    1067
    1067
    1068
    1068
    1069
    1070
    1071
    1072

    XIX

    Contents

    15.12.11 Updating the impedances at all nodes and main nodes


    15.12.12 Setting coordination groups for signal controls
    15.12.13 Resetting the lane data of nodes
    15.12.14 Aggregating isolated nodes
    15.12.15 Deleting nodes
    15.12.15.1 Deleting a node
    15.12.15.2 Deleting several marked nodes
    15.12.15.3 Deleting active nodes
    15.13 Managing turns
    15.13.1 Managing turn standards
    15.13.1.1 Creating turn standards
    15.13.1.2 Editing turn standards
    15.13.1.3 Deleting turn standards
    15.13.2 Creating turns
    15.13.3 Properties and options of turns
    15.13.4 Finding a turn
    15.13.5 Selecting turns
    15.13.5.1 Marking a turn
    15.13.5.2 Setting turns active/passive
    15.13.6 Editing the attribute values of turns
    15.13.6.1 Editing the attribute values of all or all active turns
    15.13.6.2 Displaying the attribute values of a turn in a column chart
    15.13.6.3 Allocating standard data to turns
    15.13.6.4 Recalculating the transport system set of turns
    15.13.7 Specifying an automatic allocation of the turn type
    15.13.8 Deleting turns
    15.14 Managing links
    15.14.1 Specifying a rounding factor for the PuT run time on links
    15.14.2 Specifying link types
    15.14.3 Allocating standard values to link attributes
    15.14.4 Specifying the number of link orientations
    15.14.5 Recalculating link orientations
    15.14.6 Creating a link
    15.14.7 Properties and options of links
    15.14.7.1 Links: General attributes
    15.14.7.2 Links: Basis tab
    15.14.7.3 Links: PrT TSys tab
    15.14.7.4 Links: PuT TSys tab
    15.14.7.5 Links: Environment tab
    15.14.7.6 Links: Congestion tab
    15.14.7.7 Links: DUE tab
    15.14.7.8 Links: ICA tab
    15.14.8 Finding a link
    15.14.9 Selecting links

    XX

    1073
    1074
    1075
    1076
    1083
    1083
    1085
    1088
    1090
    1090
    1090
    1092
    1093
    1093
    1093
    1093
    1094
    1094
    1094
    1094
    1094
    1095
    1095
    1096
    1097
    1098
    1099
    1099
    1099
    1102
    1103
    1104
    1105
    1107
    1108
    1108
    1109
    1109
    1110
    1110
    1111
    1112
    1112
    1112

    PTVGROUP

    Contents

    15.14.9.1 Marking links


    15.14.9.2 Setting links active/passive
    15.14.10 Editing the attribute values of links
    15.14.10.1 Editing the attribute values of a link
    15.14.10.2 Editing the attribute values of marked links
    15.14.10.3 Editing the attribute values of all or all active links
    15.14.10.4 Displaying the attribute values of a link in a column chart
    15.14.11 Editing the shape of a link course
    15.14.12 Reshaping the course of a link
    15.14.13 Reallocating links
    15.14.14 Resetting link polygons
    15.14.15 Generalizing link polygons
    15.14.16 Splitting a link
    15.14.17 Copying attribute values to the opposite direction
    15.14.18 Labeling link bars
    15.14.19 Switching on/off the labels of link bars
    15.14.19.1 Switching on/off the bar label of a link
    15.14.19.2 Switching on/off labels of marked links
    15.14.19.3 Switching on/off bar labels of all or all active links
    15.14.20 Shifting the labels of link bars
    15.14.21 Relocating the link bars to their standard positions
    15.14.22 Links: Opening the Timetable editor
    15.14.23 Determining the link course based on a shortest path search
    15.14.24 Checking the symmetry of both directions of a link
    15.14.25 Removing collinear points
    15.14.26 Calculating the gradient from z-coordinates
    15.14.27 Interpolating z-coordinates
    15.14.28 Generating link attribute values from turn attribute values
    15.14.29 Generating link run times from line run times
    15.14.30 Generating link run times from line run times in a procedure sequence
    15.14.31 Resetting DUE attributes to the standard values
    15.14.32 Deleting links
    15.15 Managing zones
    15.15.1 Creating a zone
    15.15.2 Properties and options of zones
    15.15.2.1 Zones: General attributes
    15.15.2.2 Zones: Basis tab
    15.15.2.3 Zones: Connections tab
    15.15.2.4 Zones: Demand tab
    15.15.2.5 Zones: DStrata tab
    15.15.2.6 Zones: HBEFA tab
    15.15.3 Finding a zone
    15.15.4 Selecting zones

    PTVGROUP

    1112
    1113
    1113
    1113
    1113
    1114
    1114
    1115
    1116
    1117
    1118
    1118
    1119
    1120
    1120
    1121
    1121
    1121
    1122
    1122
    1123
    1124
    1125
    1127
    1127
    1128
    1129
    1130
    1132
    1133
    1133
    1134
    1135
    1136
    1137
    1137
    1137
    1138
    1139
    1140
    1141
    1141
    1141

    XXI

    Contents

    15.15.4.1 Marking zones


    15.15.4.2 Setting active/passive zones
    15.15.5 Editing the attribute values of zones
    15.15.5.1 Editing the attribute values of a zone
    15.15.5.2 Editing the attribute values of marked zones
    15.15.5.3 Editing the attribute values of all or all active zones
    15.15.5.4 Displaying the attribute values of a zone in a column chart
    15.15.6 Editing the boundary of a zone
    15.15.7 Deleting the boundaries of several zones
    15.15.8 Shifting the centroid of a zone
    15.15.9 Splitting zones
    15.15.10 Aggregating marked or active zones to one zone
    15.15.10.1 Aggregating marked zones to one zone
    15.15.10.2 Aggregating all active zones to one zone
    15.15.11 Aggregating zones based on main zones
    15.15.12 Generating zones
    15.15.13 Setting zone labels to the centroids
    15.15.14 Deleting enclaves from zones
    15.15.15 Normalizing surfaces of zones
    15.15.16 Fuzzy alignment of zone surfaces
    15.15.17 Deleting zones
    15.15.17.1 Deleting a zone
    15.15.17.2 Deleting several marked zones
    15.15.17.3 Deleting active zones
    15.16 Managing OD pairs
    15.17 Managing main OD pairs
    15.18 Managing connectors
    15.18.1 Specifying standard values for connectors
    15.18.2 Creating a connector
    15.18.3 Properties and options of connectors
    15.18.3.1 Connectors: General attributes
    15.18.3.2 Connectors: Basis tab
    15.18.3.3 Connectors: Transport systems tab
    15.18.4 Finding a connector
    15.18.5 Selecting connectors
    15.18.5.1 Marking connectors
    15.18.5.2 Setting active/passive connectors
    15.18.6 Editing the attribute values of connectors
    15.18.6.1 Editing the attribute values of a connector
    15.18.6.2 Editing the attribute values of marked connectors
    15.18.6.3 Editing the attribute values of all or all active connectors
    15.18.6.4 Displaying the attribute values of a connector in a column chart
    15.18.7 Copying the attribute values of a connector to the opposite direction
    15.18.8 Generating connectors
    XXII

    1141
    1142
    1142
    1142
    1142
    1143
    1144
    1144
    1144
    1144
    1145
    1147
    1147
    1148
    1150
    1152
    1153
    1154
    1155
    1156
    1157
    1157
    1157
    1158
    1159
    1159
    1159
    1159
    1160
    1161
    1161
    1162
    1163
    1163
    1163
    1164
    1164
    1164
    1164
    1165
    1165
    1166
    1166
    1166

    PTVGROUP

    Contents

    15.18.9 Deleting connectors


    15.18.9.1 Deleting a connector
    15.18.9.2 Deleting several marked connectors
    15.18.9.3 Deleting active connectors
    15.19 Managing main nodes
    15.19.1 Creating a main node
    15.19.2 Properties and options of main nodes
    15.19.3 Finding a main node
    15.19.4 Selecting main nodes
    15.19.4.1 Marking main nodes
    15.19.4.2 Setting main nodes active/passive
    15.19.5 Editing the attribute values of main nodes
    15.19.5.1 Editing the attribute values of one main node
    15.19.5.2 Editing the attribute values of marked main nodes
    15.19.5.3 Editing the attribute values of all or all active main nodes
    15.19.5.4 Displaying the attribute values of a main node in a column chart
    15.19.6 Reshaping the boundary of a main node
    15.19.7 Shifting the centroid of a main node
    15.19.8 Specifying major flows at main nodes
    15.19.9 Setting the polygon allocation of main nodes
    15.19.10 Updating the impedances at main nodes
    15.19.11 Setting coordination groups for signal controls
    15.19.12 Resetting the lane data of main nodes
    15.19.13 Deleting the boundaries of several main nodes
    15.19.14 Allocating nodes to one or multiple main nodes
    15.19.15 Setting main node labels to the centroids
    15.19.16 Deleting enclaves of main nodes
    15.19.17 Normalizing surfaces of main nodes
    15.19.18 Fuzzy alignment of main node surfaces
    15.19.19 Deleting main nodes
    15.19.19.1 Deleting a main node
    15.19.19.2 Deleting several marked main nodes
    15.19.19.3 Deleting active main nodes
    15.19.20 Effects of cordon link changes
    15.20 Managing main turns
    15.20.1 Creating a main turn
    15.20.2 Properties and options of main turns
    15.20.3 Finding a main turn
    15.20.4 Selecting main turns
    15.20.4.1 Displaying main turns in the Junction editor
    15.20.5 Setting main turns active/passive
    15.20.6 Editing the attribute values of main turns
    15.20.6.1 Editing the attribute values of all or all active main turns

    PTVGROUP

    1168
    1168
    1168
    1168
    1169
    1169
    1172
    1172
    1173
    1173
    1173
    1173
    1173
    1173
    1174
    1175
    1175
    1175
    1175
    1176
    1177
    1178
    1179
    1180
    1181
    1182
    1183
    1184
    1185
    1186
    1186
    1186
    1186
    1187
    1188
    1188
    1189
    1189
    1189
    1189
    1189
    1190
    1190

    XXIII

    Contents

    15.20.6.2 Displaying the attribute values of a main turn in a column chart


    15.20.6.3 Allocating standard data or shortest path data to main turns
    15.20.6.4 Recalculating the transport system set of main turns
    15.20.7 Calculating main turn lengths from shortest paths
    15.20.8 Deleting main turns
    15.21 Managing main zones
    15.21.1 Creating a main zone
    15.21.2 Properties and options of main zones
    15.21.2.1 Main zones: General attributes
    15.21.2.2 Main zones: Basis tab
    15.21.2.3 Main zones: Demand tab
    15.21.3 Finding a main zone
    15.21.4 Selecting main zones
    15.21.4.1 Marking main zones
    15.21.4.2 Setting main zones active/passive
    15.21.5 Editing the attribute values of main zones
    15.21.5.1 Editing the attribute values of a main zone
    15.21.5.2 Editing the attribute values of marked main zones
    15.21.5.3 Editing the attribute values of all or all active main zones
    15.21.5.4 Displaying the attribute values of a main zone in a column chart
    15.21.6 Editing the boundary of a main zone
    15.21.7 Shifting the centroid of a main zone
    15.21.8 Deleting the boundaries of several main zones
    15.21.9 Moving main zone labels to the centroids
    15.21.10 Merging zone polygons
    15.21.10.1 Merging the zone polygons of one main zone
    15.21.10.2 Merging the zone polygons per main zone
    15.21.10.3 Deleting enclaves from main zones
    15.21.11 Normalizing surfaces of main zones
    15.21.12 Fuzzy alignment of main zone surfaces
    15.21.13 Deleting main zones
    15.21.13.1 Deleting a main zone
    15.21.13.2 Deleting several marked main zones
    15.21.13.3 Deleting all active main zones
    15.22 Managing territories
    15.22.1 Creating a territory
    15.22.2 Properties and options of territories
    15.22.2.1 Territories: General attributes
    15.22.2.2 Territories: Basis tab
    15.22.3 Finding a territory
    15.22.4 Selecting territories
    15.22.4.1 Marking territories
    15.22.4.2 Setting territories active/passive
    15.22.5 Editing the attribute values of territories
    XXIV

    1190
    1190
    1192
    1193
    1194
    1194
    1194
    1195
    1196
    1196
    1197
    1197
    1197
    1197
    1198
    1198
    1198
    1198
    1199
    1199
    1200
    1200
    1200
    1201
    1202
    1202
    1202
    1203
    1204
    1204
    1205
    1205
    1206
    1206
    1206
    1206
    1208
    1208
    1208
    1208
    1209
    1209
    1209
    1209

    PTVGROUP

    Contents

    15.22.5.1 Editing the attribute values of a territory


    15.22.5.2 Editing the attribute values of marked territories
    15.22.5.3 Editing the attribute values of all or all active territories
    15.22.5.4 Displaying the attribute values of a territory in a column chart
    15.22.6 Editing the shape of a territory boundary
    15.22.7 Shifting the centroid of a territory
    15.22.8 Aggregating marked or active territories to one territory
    15.22.8.1 Aggregating marked territories to one territory
    15.22.8.2 Aggregating all active territories to one territory
    15.22.9 Setting territory labels to the centroids
    15.22.10 Deleting enclaves from territories
    15.22.11 Normalizing surfaces of territories
    15.22.12 Fuzzy alignment of territory surfaces
    15.22.13 Deleting territories
    15.22.13.1 Deleting a territory
    15.22.13.2 Deleting several marked territories
    15.22.13.3 Deleting the active territories
    15.23 Managing PrT paths and sets of paths
    15.23.1 Creating a path set
    15.23.2 Properties and options of path sets
    15.23.2.1 PrT path sets: General attributes
    15.23.2.2 PrT path sets: User-defined attributes
    15.23.3 Selecting path sets
    15.23.3.1 Marking a path set
    15.23.3.2 Marking several path sets
    15.23.3.3 Setting active/passive path sets
    15.23.4 Editing the attribute values of path sets
    15.23.4.1 Editing the attribute values of one path set
    15.23.4.2 Editing the attribute values of marked path sets
    15.23.4.3 Editing the attribute values of all or all active path sets
    15.23.4.4 Displaying the attribute values of a path set in a column chart
    15.23.5 Deleting path sets
    15.23.5.1 Deleting a path set
    15.23.5.2 Deleting several marked path sets
    15.23.5.3 Deleting all path sets
    15.23.6 Creating a PrT path
    15.23.7 Properties and options of PrT paths
    15.23.7.1 Paths: General attributes (path of a path set)
    15.23.7.2 Paths: General attributes (path of a demand segment)
    15.23.7.3 Paths: Basis tab (path of a path set)
    15.23.7.4 Paths: Basis tab (path of a demand segment)
    15.23.8 Opening the Paths window
    15.23.9 Selecting paths
    15.23.9.1 Marking a path

    PTVGROUP

    1209
    1210
    1210
    1211
    1211
    1211
    1212
    1212
    1213
    1214
    1215
    1215
    1216
    1217
    1217
    1217
    1218
    1218
    1218
    1219
    1219
    1219
    1219
    1220
    1220
    1221
    1221
    1221
    1222
    1222
    1223
    1223
    1223
    1223
    1224
    1224
    1226
    1227
    1227
    1227
    1228
    1228
    1229
    1229

    XXV

    Contents

    15.23.9.2 Marking several paths


    15.23.9.3 Setting paths active/passive
    15.23.10 Editing the attribute values of PrT paths
    15.23.10.1 Editing the attribute values of a path
    15.23.10.2 Editing the attribute values of marked paths
    15.23.10.3 Editing the attribute values of all or all active paths
    15.23.10.4 Displaying the attribute values of a path in a column chart
    15.23.11 Editing the shape of a path course
    15.23.12 Converting paths
    15.23.12.1 Converting a path
    15.23.12.2 Converting the paths of a path set or demand segment
    15.23.13 Deleting paths
    15.23.13.1 Deleting a path
    15.23.13.2 Deleting several marked paths
    15.23.13.3 Deleting all paths
    15.23.14 Distributing a matrix on paths
    15.23.15 Paths in lists
    15.24 Managing stops
    15.24.1 Creating a stop
    15.24.2 Properties and options of stops
    15.24.2.1 Stops: General attributes
    15.24.2.2 Stops: Basis tab
    15.24.2.3 Stops: Stop areas tab
    15.24.2.4 Stops: Stop points tab
    15.24.2.5 Stops: Walk times / stop areas tab
    15.24.2.6 Stops: Spec. walk times tab
    15.24.2.7 Stops: Wait times tab
    15.24.3 Finding a stop
    15.24.4 Selecting stops
    15.24.4.1 Marking stops
    15.24.4.2 Setting stops active/passive
    15.24.5 Editing the attribute values of stops
    15.24.5.1 Editing the attribute values of a stop
    15.24.5.2 Editing the attribute values of marked stops
    15.24.5.3 Editing the attribute values of all or all active stops
    15.24.5.4 Displaying the attribute values of a stop in a column chart
    15.24.6 Shifting stops
    15.24.7 Merging stops
    15.24.8 Stops: Opening the Timetable editor
    15.24.9 Setting the polygon allocation of stops
    15.24.10 Setting transition walk times for stop areas
    15.24.11 Setting specific transition walk times
    15.24.12 Deleting specific walk and wait times
    15.24.13 Deleting stops

    XXVI

    1230
    1230
    1230
    1231
    1231
    1231
    1232
    1232
    1232
    1233
    1233
    1235
    1235
    1235
    1235
    1236
    1237
    1237
    1237
    1238
    1238
    1238
    1239
    1239
    1240
    1240
    1241
    1242
    1242
    1242
    1242
    1242
    1243
    1243
    1243
    1244
    1244
    1245
    1246
    1247
    1248
    1250
    1251
    1253

    PTVGROUP

    Contents

    15.24.13.1 Deleting a stop


    15.24.13.2 Deleting several marked stops
    15.24.13.3 Deleting all active stops
    15.25 Managing stop areas
    15.25.1 Creating a stop area
    15.25.2 Properties and options of stop areas
    15.25.2.1 Stop areas: General attributes
    15.25.2.2 Stop areas: Basis tab
    15.25.2.3 Stop areas: Stop points tab
    15.25.3 Finding a stop area
    15.25.4 Selecting stop areas
    15.25.4.1 Marking stop areas
    15.25.4.2 Setting stop areas active/passive
    15.25.5 Editing the attribute values of stop areas
    15.25.5.1 Editing the attribute values of a stop area
    15.25.5.2 Editing the attribute values of marked stop areas
    15.25.5.3 Editing the attribute values of all or all active stop areas
    15.25.5.4 Displaying the attribute values of a stop area in a column chart
    15.25.6 Shifting a stop area
    15.25.7 Stop areas: Opening the Timetable editor
    15.25.8 Setting the polygon allocation of stop areas
    15.25.9 Setting access nodes
    15.25.10 Deleting stop areas
    15.25.10.1 Deleting a stop area
    15.25.10.2 Deleting several marked stop areas
    15.25.10.3 Deleting active stop areas
    15.26 Managing stop points
    15.26.1 Creating a stop point
    15.26.2 Properties and options of stop points
    15.26.2.1 Stop points: General attributes
    15.26.2.2 Stop points: Basis tab
    15.26.2.3 Stop points: Transport systems tab
    15.26.2.4 Stop points: Cost tab
    15.26.2.5 Stop points: Time profiles tab
    15.26.2.6 Stop points: Depot tab
    15.26.3 Finding a stop point
    15.26.4 Selecting stop points
    15.26.4.1 Marking stop points
    15.26.4.2 Setting stop points active/passive
    15.26.5 Editing the attribute values of stop points
    15.26.5.1 Editing the attribute values of a stop point
    15.26.5.2 Editing the attribute values of marked stop points
    15.26.5.3 Editing the attribute values of all or all active stop points
    15.26.5.4 Displaying the attribute values of a stop point in a column chart

    PTVGROUP

    1253
    1253
    1254
    1255
    1255
    1256
    1256
    1257
    1257
    1258
    1258
    1258
    1258
    1258
    1258
    1259
    1259
    1260
    1260
    1261
    1261
    1262
    1264
    1264
    1264
    1265
    1266
    1266
    1267
    1269
    1270
    1271
    1271
    1271
    1272
    1272
    1272
    1272
    1273
    1273
    1273
    1274
    1274
    1275

    XXVII

    Contents

    15.26.6 Shifting or merging stop points


    15.26.7 Stop points: Opening the Timetable editor
    15.26.8 Setting the polygon allocation of stop points
    15.26.9 Deleting stop points
    15.26.9.1 Deleting a stop point
    15.26.9.2 Deleting several marked stop points
    15.26.9.3 Deleting active stop points
    15.27 Managing operators of the public transport
    15.27.1 Creating an operator
    15.27.2 Editing the attribute values of operators
    15.27.3 Deleting operators
    15.28 Managing PuT vehicles
    15.28.1 Creating a vehicle unit
    15.28.2 Properties and options of vehicle units
    15.28.3 Editing the attributes of vehicle units
    15.28.4 Deleting vehicle units
    15.28.5 Creating vehicle combinations
    15.28.6 Properties and options of vehicle combinations
    15.28.6.1 Vehicle combinations: General attributes
    15.28.6.2 Vehicle combinations: Basis tab
    15.28.6.3 Vehicle combinations: Cost rates tab
    15.28.7 Editing the attribute values of vehicle combinations
    15.28.8 Deleting vehicle combinations
    15.29 Managing PuT directions
    15.30 Managing lines
    15.30.1 Specifying default values for lines and line routes
    15.30.2 Creating a line
    15.30.3 Properties and options of lines
    15.30.4 Finding lines
    15.30.4.1 Finding a line directly
    15.30.4.2 Finding a line by vehicle journey
    15.30.5 Selecting lines
    15.30.5.1 Marking lines
    15.30.5.2 Setting lines active/passive
    15.30.6 Editing the attribute values of lines
    15.30.6.1 Editing the attribute values of a line
    15.30.6.2 Editing the attribute values of marked lines
    15.30.6.3 Editing the attribute values of all or all active lines
    15.30.6.4 Displaying the attribute values of a line in a column chart
    15.30.7 Copying lines
    15.30.8 Lines: Opening the Timetable editor
    15.30.9 Aggregating lines
    15.30.10 Disaggregate lines

    XXVIII

    1275
    1277
    1278
    1279
    1279
    1279
    1280
    1281
    1281
    1282
    1282
    1282
    1283
    1284
    1285
    1285
    1286
    1287
    1287
    1288
    1289
    1289
    1290
    1290
    1291
    1291
    1292
    1292
    1294
    1294
    1294
    1295
    1295
    1296
    1297
    1297
    1297
    1297
    1298
    1298
    1299
    1300
    1303

    PTVGROUP

    Contents

    15.30.11 Deleting lines


    15.30.11.1 Deleting marked lines
    15.30.11.2 Deleting active lines
    15.31 Managing line routes and time profiles
    15.31.1 Opening the Line routes window
    15.31.2 Creating a line route
    15.31.3 Properties and options of line routes and time profiles
    15.31.3.1 Line routes: General attributes
    15.31.3.2 Line routes: Basis tab
    15.31.3.3 Line routes: Items and time profiles tab
    15.31.4 Finding line routes
    15.31.4.1 Finding a line route directly
    15.31.4.2 Searching a line route by vehicle journey
    15.31.5 Managing time profiles
    15.31.5.1 Setting the reference journey for a time profile
    15.31.5.2 Creating a time profile
    15.31.5.3 Copying a time profile
    15.31.5.4 Editing a time profile
    15.31.5.5 Coupling multiple time profiles
    15.31.5.6 Deleting couplings of time profiles
    15.31.5.7 Multiple display of time profiles
    15.31.5.8 Deleting a time profile
    15.31.6 Selecting line routes
    15.31.6.1 Marking a line route
    15.31.6.2 Marking several line routes
    15.31.6.3 Setting active/passive line routes
    15.31.7 Editing attribute values of line routes
    15.31.7.1 Editing the attribute values of line routes
    15.31.7.2 Editing the attribute values of marked line routes
    15.31.7.3 Editing the attribute values of all or all active line routes
    15.31.7.4 Displaying the attribute values of a line route in a column chart
    15.31.8 Editing the shape of a line route course
    15.31.8.1 Editing the shape of a line route
    15.31.8.2 Editing the course of several line routes at the same time
    15.31.8.3 Basic rules: Editing a route course
    15.31.8.4 Tabular editing of a line route course
    15.31.9 Copying a line route
    15.31.10 Connecting a line route
    15.31.11 Creating the opposite direction of a line route
    15.31.12 Line routes: Opening the Timetable editor
    15.31.13 Aggregating line routes
    15.31.14 Specifying the lengths of line routes
    15.31.15 Specifying the direction of the line route
    15.31.16 Generating profile points for line route items

    PTVGROUP

    1305
    1305
    1306
    1306
    1306
    1307
    1311
    1311
    1312
    1313
    1315
    1315
    1315
    1316
    1318
    1320
    1320
    1321
    1331
    1333
    1333
    1334
    1334
    1335
    1336
    1336
    1336
    1336
    1337
    1337
    1338
    1338
    1338
    1339
    1340
    1347
    1353
    1355
    1357
    1358
    1360
    1360
    1360
    1361

    XXIX

    Contents

    15.31.17 Deleting line routes


    15.31.17.1 Deleting a line route
    15.31.17.2 Deleting several marked line routes
    15.31.17.3 Deleting active line routes
    15.32 Managing main lines
    15.32.1 Creating a main line
    15.32.2 Properties and options of main lines
    15.32.3 Setting active/passive main lines
    15.32.4 Editing the attribute values of main lines
    15.32.4.1 Editing the attribute values of a main line
    15.32.4.2 Editing the attribute values of all or all active main lines
    15.32.5 Deleting main lines
    15.32.5.1 Deleting a main line
    15.32.5.2 Deleting all or all active main lines
    15.33 Managing system routes
    15.33.1 Creating a system route
    15.33.2 Properties and options of system routes
    15.33.2.1 System routes: General attributes
    15.33.2.2 System routes: Basis tab
    15.33.2.3 System routes: Vehicle combinations tab
    15.33.3 Selecting system routes
    15.33.3.1 Marking a system route
    15.33.3.2 Marking several system routes
    15.33.3.3 Setting system routes active or passive
    15.33.4 Editing the attribute values of system routes
    15.33.4.1 Editing the attribute values of a system route
    15.33.4.2 Editing the attribute values of marked system routes
    15.33.4.3 Editing the attribute values of all or all active system routes
    15.33.4.4 Displaying the attribute values of a system route in a column chart
    15.33.5 Editing the course of a system route
    15.33.6 Copying a system route
    15.33.7 Creating the opposite direction of a system route
    15.33.8 Creating system routes
    15.33.8.1 Creating system routes from time profiles
    15.33.8.2 Creating system routes for pairs of stop points
    15.33.9 Deleting system routes
    15.33.9.1 Deleting a system route
    15.33.9.2 Deleting several system routes
    15.33.9.3 Deleting the active system routes
    15.34 Managing Points of Interest (POIs)
    15.34.1 Creating a POI category
    15.34.2 Editing a POI category
    15.34.3 Deleting a POI category
    15.34.4 Using user-defined attributes for POI categories

    XXX

    1362
    1362
    1362
    1363
    1364
    1364
    1365
    1366
    1366
    1366
    1367
    1367
    1367
    1368
    1368
    1368
    1371
    1371
    1371
    1372
    1372
    1372
    1373
    1373
    1374
    1374
    1374
    1375
    1375
    1375
    1376
    1377
    1378
    1378
    1380
    1383
    1383
    1383
    1384
    1384
    1384
    1385
    1385
    1386

    PTVGROUP

    Contents

    15.34.5 Creating a POI


    15.34.6 Properties and options of POIs
    15.34.7 Displaying POIs
    15.34.7.1 Hiding or showing POIs
    15.34.7.2 Changing the symbol of an individual POI
    15.34.7.3 Changing image size and rotation angle of a POI
    15.34.8 Finding POIs
    15.34.9 Selecting POIs
    15.34.9.1 Marking POIs
    15.34.9.2 Setting POIs active/passive
    15.34.10 Editing the attribute values of POIs
    15.34.10.1 Editing the attribute values of POIs
    15.34.10.2 Editing the attribute values of marked POIs
    15.34.10.3 Editing the attribute values of all or all active POIs
    15.34.10.4 Displaying the attribute values of a POI in a column chart
    15.34.11 Shifting POIs
    15.34.12 Aggregating marked or active POIs to one POI
    15.34.12.1 Aggregating marked POIs to one POI
    15.34.12.2 Aggregating all active POIs to one POI
    15.34.13 Deleting enclaves of POIs
    15.34.14 Normalizing surfaces of POIs
    15.34.15 Fuzzy alignment of POIs surfaces
    15.34.16 Allocating a POI to a different category
    15.34.17 Allocating network objects to a POI
    15.34.17.1 Allocating network objects in a list
    15.34.17.2 Allocating network objects graphically
    15.34.17.3 Specifying settings for POI allocations
    15.34.18 Deleting POIs
    15.34.18.1 Deleting a POI
    15.34.18.2 Deleting several marked POIs
    15.34.18.3 Deleting all POIs of a category
    15.34.18.4 Deleting all active POIs
    15.35 Managing GIS objects
    15.36 Managing count locations
    15.36.1 Creating a count location
    15.36.2 Properties and options of count locations
    15.36.2.1 Count locations: General attributes
    15.36.2.2 Count locations: Basis tab
    15.36.3 Finding a count location
    15.36.4 Selecting count locations
    15.36.4.1 Marking count locations
    15.36.4.2 Setting count locations active/passive
    15.36.5 Editing attribute values of count locations
    15.36.5.1 Editing the attribute values of a count location
    PTVGROUP

    1386
    1387
    1388
    1388
    1389
    1389
    1390
    1390
    1390
    1390
    1390
    1390
    1391
    1391
    1392
    1392
    1393
    1393
    1393
    1394
    1395
    1395
    1396
    1398
    1398
    1400
    1401
    1401
    1401
    1402
    1402
    1402
    1403
    1403
    1403
    1404
    1404
    1404
    1405
    1405
    1405
    1406
    1406
    1406

    XXXI

    Contents

    15.36.5.2 Editing attribute values of marked count locations


    15.36.5.3 Editing the attribute values of all or all active count locations
    15.36.5.4 Displaying the attribute values of a count location in a column chart
    15.36.6 Shifting a count location
    15.36.7 Setting the polygon allocation of count locations
    15.36.8 Deleting count locations
    15.36.8.1 Deleting a count location
    15.36.8.2 Deleting several marked count locations
    15.36.8.3 Deleting all active count locations
    15.37 Managing detectors
    15.37.1 Creating a detector
    15.37.1.1 Creating a detector for a count location
    15.37.1.2 Creating a detector in the node and main node section
    15.37.2 Properties and options of detectors
    15.37.2.1 Detectors: General attributes
    15.37.2.2 Detectors: Basis tab
    15.37.2.3 Detectors: Data tab
    15.37.3 Finding a detector
    15.37.4 Selecting detectors
    15.37.4.1 Marking detectors
    15.37.4.2 Setting active/passive detectors
    15.37.5 Editing attribute values of detectors
    15.37.5.1 Editing a detector attribute
    15.37.5.2 Editing the attribute values of marked detectors
    15.37.5.3 Editing the attribute values of all or all active detectors
    15.37.5.4 Displaying the attribute values of a detector in a column chart
    15.37.6 Shifting a detector
    15.37.7 Deleting detectors
    15.37.7.1 Deleting a detector
    15.37.7.2 Deleting several marked detectors
    15.37.7.3 Deleting all active detectors
    15.38 Managing toll systems
    15.38.1 Creating a toll system
    15.38.2 Properties and options of toll systems
    15.38.2.1 Toll systems: General attributes
    15.38.2.2 Toll systems: Area toll tab
    15.38.3 Finding a toll system
    15.38.4 Selecting toll systems
    15.38.4.1 Marking toll systems
    15.38.4.2 Setting toll systems active/passive
    15.38.5 Editing attribute values of toll systems
    15.38.5.1 Editing the attribute values of a toll system
    15.38.5.2 Editing attribute values of marked toll systems
    15.38.5.3 Editing the attribute values of all or all active toll systems

    XXXII

    1406
    1407
    1407
    1407
    1408
    1409
    1409
    1409
    1409
    1410
    1410
    1410
    1410
    1411
    1411
    1412
    1412
    1413
    1413
    1413
    1413
    1414
    1414
    1414
    1414
    1415
    1415
    1416
    1416
    1416
    1416
    1417
    1417
    1418
    1419
    1419
    1419
    1419
    1420
    1420
    1420
    1420
    1421
    1421

    PTVGROUP

    Contents

    15.38.5.4 Displaying the attribute values of a toll system in a column chart


    15.38.6 Specifying the matrix toll of a toll system
    15.38.7 Editing the shape of a toll system boundary
    15.38.8 Shifting the centroid of a toll system
    15.38.9 Setting toll system labels to the centroids
    15.38.10 Deleting enclaves from toll systems
    15.38.11 Normalizing surfaces of toll systems
    15.38.12 Fuzzy alignment of toll system surfaces
    15.38.13 Deleting toll systems
    15.38.13.1 Deleting a toll system
    15.38.13.2 Deleting several marked toll systems
    15.38.13.3 Deleting active toll systems
    15.39 Managing screenlines
    15.39.1 Creating a screenline
    15.39.2 Properties and options of screenlines
    15.39.2.1 Screenlines: General attributes
    15.39.2.2 Screenlines: Link attributes tab
    15.39.3 Finding a screenline
    15.39.4 Selecting screenlines
    15.39.4.1 Marking a screenline
    15.39.4.2 Marking several screenlines
    15.39.4.3 Setting screenlines active/passive
    15.39.5 Editing attribute values of screenlines
    15.39.5.1 Editing the attribute values of a screenline
    15.39.5.2 Editing the attribute values of marked screenlines
    15.39.5.3 Editing the attribute values of all or all active screenlines
    15.39.5.4 Displaying the attribute values of a screenline in a column chart
    15.39.6 Editing the shape of a screenline course
    15.39.6.1 Resetting the course of a screenline
    15.39.7 Creating the opposite direction
    15.39.8 Deleting screenlines
    15.39.8.1 Deleting a screenline
    15.39.8.2 Deleting several marked screenlines
    15.39.8.3 Deleting all active screenlines
    15.40 Using the Junction editor
    15.40.1 Displaying a network object in the Junction editor
    15.40.2 Switching to a different network object
    15.40.3 Adjusting the attribute selection in the Junction editor
    15.40.4 Adjusting the display and the input options of the list view
    15.40.5 Editing a node in the Junction editor
    15.40.5.1 Editing nodes in the schematic view
    15.40.5.2 Editing node attributes in the list view
    15.40.6 Editing a main node in the Junction editor

    PTVGROUP

    1422
    1422
    1423
    1423
    1424
    1424
    1425
    1426
    1427
    1427
    1427
    1428
    1428
    1428
    1429
    1429
    1429
    1430
    1430
    1430
    1430
    1431
    1431
    1431
    1431
    1432
    1432
    1432
    1433
    1433
    1434
    1434
    1434
    1435
    1435
    1439
    1439
    1440
    1440
    1441
    1441
    1443
    1446

    XXXIII

    Contents

    15.40.6.1 Editing main nodes in the schematic view


    15.40.6.2 Editing main node attributes in the list view
    15.40.7 Editing turns in the Junction editor
    15.40.7.1 Editing turns in the schematic view
    15.40.7.2 Editing main node attributes in the list view
    15.40.8 Editing main turns in the Junction editor
    15.40.8.1 Displaying main turns in the schematic view
    15.40.8.2 Editing main turn attributes in the list view
    15.40.9 Editing links in the Junction editor
    15.40.9.1 Editing links in the schematic view
    15.40.9.2 Editing link attributes in the list view
    15.40.10 Managing signal controls
    15.40.10.1 Creating a signal control
    15.40.10.2 Properties and options of signal controls
    15.40.10.3 Editing the attribute values of a signal control
    15.40.10.4 Editing a signal control of the RBC type
    15.40.10.5 Editing the external control of a signal control
    15.40.10.6 Deleting a signal control
    15.40.11 Managing signal groups
    15.40.11.1 Creating a signal group
    15.40.11.2 Properties and options of signal groups
    15.40.11.3 Deleting a signal group
    15.40.12 Editing the geometry of a node
    15.40.12.1 Editing the geometry in the schematic view
    15.40.12.2 Editing the geometry in the list view
    15.40.13 Editing the signal timing of a node
    15.40.13.1 Switching off signal programs
    15.40.13.2 Editing the signal times of signal group-based controls
    15.40.13.3 Editing the signal times of stage-based controls
    15.40.14 Managing signal coordination groups
    15.40.14.1 Creating a signal coordination group
    15.40.14.2 Properties and options of signal coordination groups
    15.40.14.3 Editing signal coordination groups
    15.40.14.4 Deleting a signal coordination group
    15.40.15 Edit time-varying attributes
    15.40.16 Calculating and exporting ICA
    15.40.16.1 Checking the status of ICA calculations
    15.40.16.2 Starting an ICA calculation
    15.40.16.3 Displaying the ICA calculation in the report window
    15.40.16.4 Recalculating ICA automatically
    15.40.16.5 Exporting an ICA report
    15.40.17 Optimizing signal cycles and split of a single signal control
    15.40.18 Displaying turn volumes in the Junction editor
    15.40.18.1 Displaying turn volumes in the Junction editor

    XXXIV

    1446
    1447
    1450
    1450
    1452
    1454
    1455
    1456
    1458
    1458
    1460
    1463
    1464
    1465
    1469
    1470
    1471
    1472
    1473
    1473
    1474
    1475
    1475
    1475
    1479
    1487
    1488
    1488
    1492
    1497
    1497
    1498
    1498
    1498
    1499
    1499
    1499
    1499
    1500
    1500
    1500
    1501
    1501
    1502

    PTVGROUP

    Contents

    15.40.18.2 Specifying settings for the print frame of turn volumes


    15.40.18.3 Positioning link labels along links
    15.40.18.4 Exporting turn volumes as graphics
    15.41 Checking the network and fixing errors
    15.41.1 Checking the network
    15.41.2 Displaying the results of the check and fixing errors
    15.42 Specifying a calendar and valid days
    15.42.1 Selecting a calendar
    15.42.2 Creating a valid day
    15.42.3 Properties and options of valid days
    15.42.3.1 No calendar
    15.42.3.2 Weekly calendar
    15.42.3.3 Annual calendar
    15.42.4 Editing attribute values of valid days
    15.42.5 Deleting valid days
    15.42.6 Collate valid days
    15.42.7 Creating a vacation day
    15.42.8 Properties and options of vacation days
    15.42.9 Editing attribute values of vacation days
    15.42.10 Deleting vacation days
    15.43 Using the Timetable editor
    15.43.1 Opening the Timetable editor
    15.43.2 Selecting line(s) to be displayed in the Timetable editor
    15.43.3 The Timetable editor window
    15.43.4 Managing vehicle journeys and vehicle journey sections
    15.43.4.1 Showing only active vehicle journeys
    15.43.4.2 Creating a vehicle journey
    15.43.4.3 Duplicating vehicle journey
    15.43.4.4 Finding vehicle journeys
    15.43.4.5 Creating regular services
    15.43.4.6 Editing the values of vehicle journey attributes
    15.43.4.7 Marking vehicle journeys
    15.43.4.8 Editing vehicle journeys
    15.43.4.9 Editing the attribute values of all or all active vehicle journeys
    15.43.4.10 Shifting vehicle journeys temporally
    15.43.4.11 Shifting vehicle journeys to a different line
    15.43.4.12 Coupling vehicle journeys in pairs
    15.43.4.13 Separating coupled vehicle journeys or shortening the coupling
    15.43.4.14 Editing regular services
    15.43.4.15 Deleting vehicle journeys
    15.43.4.16 Creating vehicle journey sections
    15.43.4.17 Editing a vehicle journey section
    15.43.4.18 Editing the attribute values of all or all active vehicle journey sections

    PTVGROUP

    1502
    1503
    1503
    1504
    1504
    1510
    1511
    1511
    1512
    1513
    1513
    1514
    1515
    1519
    1520
    1520
    1521
    1521
    1525
    1525
    1526
    1526
    1527
    1530
    1531
    1533
    1534
    1536
    1536
    1536
    1538
    1539
    1541
    1541
    1542
    1543
    1544
    1545
    1546
    1550
    1551
    1551
    1554

    XXXV

    Contents

    15.43.4.19 Replacing vehicle journey combinations on vehicle journey sections


    15.43.4.20 Normalizing vehicle journey sections
    15.43.4.21 Deleting vehicle journey sections
    15.43.5 Calculating stop sequences hierarchically
    15.43.6 Sorting vehicle journeys in the tabular timetable
    15.43.6.1 No sorting (standard sorting)
    15.43.6.2 Sorting by a sort station
    15.43.6.3 Sorting by vehicle journey attribute
    15.43.7 Special functions of the graphical timetable
    15.43.7.1 Adjusting the display of the graphical timetable
    15.43.7.2 Marking and editing vehicle journeys in the graphical timetable
    15.43.7.3 Displaying and adjusting margins
    15.43.7.4 Saving graphical timetable as graphics file
    15.43.8 Specifying the layout of the Timetable editor
    15.43.8.1 Selecting the attributes to be displayed
    15.43.8.2 Specifying the display of stop events
    15.43.8.3 Saving the layout of the Timetable editor
    15.43.8.4 Reading the layout of the Timetable editor
    15.43.9 Setting the graphic parameters of the tabular timetable
    15.43.9.1 Specifying the background of the table
    15.43.9.2 Specifying the table font
    15.43.10 Setting the graphic parameters of the graphical timetable
    15.43.10.1 Setting the print frame
    15.43.10.2 Specifying the axes labeling
    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    15.43.10.4 Resetting the graphic parameters of the timetable
    15.43.10.5 Saving the graphic parameters of the timetable
    15.43.10.6 Reading graphic parameters for the timetable
    15.43.11 Printing the graphical timetable
    15.43.12 Printing the tabular timetable
    15.44 Using the subnetwork generator
    15.44.1 Subnetwork generation
    15.44.2 Selecting options for line routes
    16 Modeling demand
    16.1 Managing demand objects
    16.1.1 Managing matrices
    16.1.1.1 Working with matrices
    16.1.1.2 Connecting demand matrices and demand segments
    16.1.2 Managing time series
    16.1.2.1 Creating standard time series
    16.1.2.2 Properties and options of standard time series
    16.1.2.3 Editing attribute data of standard time series

    XXXVI

    1554
    1556
    1557
    1558
    1563
    1564
    1564
    1564
    1565
    1566
    1567
    1567
    1568
    1568
    1568
    1570
    1571
    1572
    1573
    1574
    1576
    1577
    1577
    1581
    1583
    1599
    1599
    1600
    1600
    1600
    1601
    1602
    1604
    1606
    1606
    1607
    1607
    1607
    1608
    1608
    1608
    1609

    PTVGROUP

    Contents

    16.1.2.4 Creating time intervals for standard time series


    16.1.2.5 Creating multiple time intervals of identical length
    16.1.2.6 Editing time intervals of standard time series
    16.1.2.7 Deleting time intervals of standard time series
    16.1.2.8 Editing the first day (start) and start time of standard time series
    16.1.2.9 Deleting standard time series
    16.1.2.10 Creating demand time series
    16.1.2.11 Allocating different standard time series to relations between certain
    zone types
    16.1.2.12 Combining demand time series and demand segment
    16.1.2.13 Deleting demand time series
    16.1.3 Managing demand objects
    16.1.3.1 Creating a demand model
    16.1.3.2 Properties and options of demand models
    16.1.3.3 Editing attribute data of demand models
    16.1.3.4 Deleting demand models
    16.1.3.5 Importing predefined demand models *.dmd
    16.1.3.6 Reading tour-based demand models from VISEM data files (*.vhd)
    16.1.4 Managing person groups
    16.1.4.1 Creating a person group
    16.1.4.2 Properties and options of person groups
    16.1.4.3 Editing attribute data of person groups
    16.1.4.4 Editing the number of persons in a person group
    16.1.4.5 Deleting person groups
    16.1.5 Managing structural properties
    16.1.5.1 Creating a structural property
    16.1.5.2 Properties and options of structural properties
    16.1.5.3 Editing attribute data of structural properties
    16.1.5.4 Editing structural property data
    16.1.5.5 Deleting structural properties
    16.1.6 Managing activities, activity pairs and activity chains
    16.1.6.1 Creating an activity
    16.1.6.2 Properties and options of activities
    16.1.6.3 Editing attribute data of activities
    16.1.6.4 Deleting activities
    16.1.6.5 Creating an activity pair
    16.1.6.6 Properties and options of activity pairs
    16.1.6.7 Editing attribute data of activity pairs
    16.1.6.8 Connecting activity pairs and standard time series
    16.1.6.9 Deleting activity pairs
    16.1.6.10 Creating an activity chain
    16.1.6.11 Properties and options of activity chains
    16.1.6.12 Editing attribute data of activity chains
    16.1.6.13 Deleting activity chains
    16.1.7 Managing demand strata

    PTVGROUP

    1609
    1611
    1612
    1612
    1613
    1614
    1614
    1615
    1616
    1616
    1617
    1617
    1617
    1618
    1618
    1619
    1619
    1620
    1620
    1620
    1621
    1621
    1621
    1622
    1622
    1622
    1623
    1623
    1623
    1624
    1624
    1625
    1626
    1626
    1627
    1628
    1629
    1630
    1630
    1631
    1632
    1632
    1632
    1633

    XXXVII

    Contents

    16.1.7.1 Creating a demand stratum


    16.1.7.2 Properties and options of demand strata
    16.1.7.3 Editing attribute data of demand strata
    16.1.7.4 Deleting demand strata
    16.2 Calculating trip demand
    16.2.1 Calculating demand with the Standard 4-step model
    16.2.1.1 Calculating trip generation
    16.2.1.2 Editing the demand of Standard 4-step demand strata
    16.2.1.3 Generating demand matrices for Standard 4-step trip distribution
    16.2.1.4 Calculating trip distribution
    16.2.1.5 Allocating demand matrices to modes for mode choice
    16.2.1.6 Calculate mode choice
    16.2.1.7 Calculating nested mode choice
    16.2.1.8 Calculating Time-of-day choice
    16.2.2 Calculating demand with the EVA-P model
    16.2.2.1 Defining constraints
    16.2.2.2 Editing non-constant constraint factors values
    16.2.2.3 Calculating EVA trip generation
    16.2.2.4 Editing values for non-constant rates and factors
    16.2.2.5 Editing the demand of EVA-P demand strata
    16.2.2.6 Viewing the demand of EVA-P demand strata in lists
    16.2.2.7 Calculating EVA weighting
    16.2.2.8 Managing weighting matrices
    16.2.2.9 Creating demand matrices for EVA trip distribution
    16.2.2.10 Allocating demand matrices to modes for EVA mode choice
    16.2.2.11 Calculating EVA trip distribution and mode choice
    16.2.3 Demand calculation with the tour-based model (VISEM)
    16.2.3.1 Calculating Tour-based model - Trip generation
    16.2.3.2 Editing values for non-constant mobility rates and study area shares
    16.2.3.3 Editing the demand of tour-based demand strata
    16.2.3.4 Viewing the demand of Tour-based model demand strata in lists
    16.2.3.5 Creating demand matrices for tour-based model - trip distribution and
    mode choice
    16.2.3.6 Calculating tour-based model - combined trip distribution and mode
    choice
    16.2.4 Starting the iterative repetition
    16.2.4.1 Go to a procedure in the procedure sequence (GoTo procedure)
    16.2.4.2 Calculating the weighted mean of matrices
    16.2.4.3 Calculating the weighted mean of attributes
    16.2.5 Estimate gravitation parameters (KALIBRI)
    16.2.5.1 Estimate gravitation parameters
    16.2.6 Creating a procedure sequence automatically
    16.3 Managing, showing and analyzing matrices
    16.3.1 Matrices overview
    16.3.1.1 Showing matrices in the Matrices window
    XXXVIII

    1633
    1635
    1637
    1637
    1637
    1638
    1638
    1641
    1642
    1643
    1648
    1649
    1653
    1658
    1661
    1662
    1665
    1666
    1668
    1669
    1670
    1671
    1677
    1679
    1680
    1680
    1683
    1684
    1686
    1687
    1687
    1688
    1689
    1697
    1697
    1700
    1701
    1703
    1704
    1707
    1715
    1715
    1716

    PTVGROUP

    Contents

    16.3.1.2 The Matrix editor window


    16.3.2 Opening matrices
    16.3.2.1 Opening a Visum matrix
    16.3.2.2 Opening an external matrix
    16.3.2.3 Opening matrices in the List view
    16.3.2.4 Opening several matrices in separate windows
    16.3.2.5 Opening several matrices in one window
    16.3.2.6 Opening the same matrix several times
    16.3.3 Managing matrices in the Matrix window or Histogram window
    16.3.4 Generating new matrix
    16.3.4.1 Generating matrix with zero values
    16.3.4.2 Create matrix calculated from formula
    16.3.5 Editing formula matrices
    16.3.6 Reading an external matrix into a network model
    16.3.7 Showing and editing matrix attribute values
    16.3.8 Saving matrices
    16.3.8.1 Saving a Visum matrix to a file
    16.3.8.2 Saving external matrices
    16.3.8.3 Saving partial matrices
    16.3.8.4 Saving matrices during procedure sequence execution
    16.3.8.5 Saving partial matrices during the execution of the procedure
    sequence
    16.3.9 Filtering and aggregating matrix data, changing the view
    16.3.9.1 Filtering matrix data
    16.3.9.2 Showing matrix values in an aggregated form
    16.3.9.3 Changing the matrix data view
    16.3.10 Saving and loading the layout of a Matrix editor or Histogram window
    16.3.10.1 Saving the layout of a Matrix editor or Histogram window
    16.3.10.2 Loading the layout of a Matrix editor or Histogram window
    16.3.11 Setting graphic parameters for the Matrix editor window
    16.3.11.1 Setting the graphic parameters for active OD pairs
    16.3.11.2 Setting the graphic parameters for passive OD pairs
    16.3.11.3 Setting the graphic parameters for the matrix diagonal
    16.3.11.4 Resetting the matrix window graphic parameters
    16.3.12 Reading and saving the graphic parameters of the matrix window
    16.3.12.1 Saving the matrix window graphic parameters
    16.3.12.2 Reading the matrix window graphic parameters
    16.3.13 Showing matrices in a histogram
    16.3.13.1 Create histogram
    16.3.13.2 Classifying a histogram on the basis of another matrix
    16.3.13.3 Changing the number of decimal places in intervals
    16.3.13.4 Saving intervals to an attribute file
    16.3.14 Comparing two matrices in a scatter plot
    16.3.15 Deleting Visum matrices

    PTVGROUP

    1717
    1721
    1721
    1722
    1722
    1723
    1723
    1724
    1724
    1725
    1726
    1727
    1730
    1731
    1731
    1733
    1733
    1736
    1738
    1738
    1739
    1742
    1742
    1744
    1746
    1747
    1748
    1748
    1749
    1749
    1751
    1751
    1752
    1752
    1752
    1752
    1752
    1753
    1755
    1755
    1756
    1756
    1757

    XXXIX

    Contents

    16.3.16 Basic settings for matrices


    16.3.16.1 Setting options for display in the Matrix window
    16.3.16.2 Specifying treatment of division by zero
    16.3.16.3 Specifying a default value for new relations
    16.3.16.4 Specifying settings for treatment of matrices
    16.3.16.5 Settings for Reading matrix from file in $O format
    16.4 Editing matrix values
    16.4.1 Marking matrix data
    16.4.1.1 Finding cells
    16.4.1.2 Selecting cells using the mouse
    16.4.1.3 Selecting cells using the keyboard
    16.4.2 Editing matrix values interactively
    16.4.3 Replacing matrix values
    16.4.3.1 Replacing all matrix values
    16.4.3.2 Replacing selected matrix values
    16.4.3.3 Replacing the matrix diagonal
    16.4.3.4 Replacing selected values in the matrix diagonal
    16.4.3.5 Setting new matrix values based on a condition
    16.4.3.6 Setting matrix values of several matrices to null
    16.4.3.7 Importing matrix values into Visum matrices
    16.4.4 Copying and pasting matrix values
    16.4.4.1 Copying and pasting a matrix
    16.4.4.2 Exchanging matrix values between opened matrices
    16.4.5 Copying and pasting matrix diagonal values
    16.4.6 Importing matrix values during execution of the procedure sequence
    16.4.7 Exporting matrix values to a database
    16.4.7.1 Exporting matrix to an access database
    16.4.7.2 Exporting matrix values to an SQL database
    16.4.8 Reflecting the upper triangle of a matrix
    16.4.8.1 Reflecting the upper triangle in the matrix window
    16.4.8.2 Reflecting the upper triangle in the procedure sequence
    16.4.9 Reflecting the lower triangle of a matrix
    16.4.9.1 Reflecting the lower triangle in the Matrix window
    16.4.9.2 Reflecting the lower triangle during the procedure sequence run
    16.4.10 Transposing the matrix values
    16.4.10.1 Transposing matrix values in a Matrix window
    16.4.10.2 Transposing matrix values during the procedure sequence
    16.4.11 Editing matrix values using a log file during the procedure sequence run
    16.5 Using matrix values for calculations
    16.5.1 Rounding matrix values
    16.5.2 Adding up matrix values
    16.5.2.1 Add values to whole matrix
    16.5.2.2 Adding values to selected matrix data
    16.5.2.3 Adding up matrix values during the procedure sequence run

    XL

    1758
    1758
    1759
    1759
    1760
    1761
    1761
    1761
    1762
    1762
    1763
    1763
    1764
    1764
    1765
    1765
    1766
    1767
    1768
    1768
    1768
    1769
    1769
    1770
    1770
    1771
    1771
    1772
    1772
    1772
    1773
    1773
    1773
    1774
    1774
    1774
    1775
    1775
    1776
    1777
    1777
    1777
    1779
    1780

    PTVGROUP

    Contents

    16.5.3 Subtracting matrix values


    1781
    16.5.3.1 Subtracting values from all matrix data
    1781
    1782
    16.5.3.2 Subtracting values from selected matrix data
    16.5.4 Multiplying matrix values
    1783
    16.5.4.1 Multiplying values by all matrix data
    1783
    16.5.4.2 Multiplying the matrix data by selected values
    1784
    1785
    16.5.5 Dividing matrix values
    16.5.5.1 Dividing all matrix data
    1785
    16.5.5.2 Dividing selected matrix data
    1786
    16.5.6 Forming the reciprocal of matrix values
    1787
    16.5.6.1 Forming the reciprocal for all matrix data
    1787
    16.5.6.2 Forming the reciprocal for selected matrix data
    1787
    16.5.6.3 Forming the reciprocal during the procedure sequence run
    1788
    16.5.7 Raise to power
    1788
    16.5.7.1 Applying raise to power function to all matrix data
    1788
    16.5.7.2 Using raise to power function for selected matrices
    1790
    16.5.8 Take logarithm
    1790
    16.5.8.1 Taking the logarithm of all matrix data
    1790
    16.5.8.2 Taking the logarithm of selected matrix values
    1791
    16.5.8.3 Taking the logarithm during procedure sequence run
    1791
    16.5.9 Exponential function
    1792
    16.5.9.1 Applying the exponential function to all matrix data
    1792
    16.5.9.2 Applying the exponential function to selected matrix data
    1792
    16.5.9.3 Applying the exponential function during the procedure sequence run 1793
    16.5.10 Replacing matrix data by a maximum value
    1793
    16.5.10.1 Replacing all matrix data with a maximum value
    1793
    16.5.10.2 Replacing selected matrix data with a maximum value
    1795
    16.5.11 Replacing matrix data by a minimum value
    1795
    16.5.11.1 Replacing all matrix data by a minimum value
    1795
    16.5.11.2 Replacing selected matrix data with a minimum value
    1797
    16.5.12 Symmetrizing a matrix
    1797
    16.5.12.1 Symmetrizing a matrix in the Matrix window
    1797
    16.5.12.2 Symmetrizing a matrix during the procedure sequence run
    1797
    16.5.13 Combining matrices and attribute vectors
    1798
    16.5.13.1 Combining matrices and attribute vectors in the Matrix window
    1799
    16.5.13.2 Combining matrices and attribute vectors during the procedure
    sequence run
    1799
    16.5.14 Projecting matrix values
    1800
    16.5.14.1 Projecting all matrix values evenly
    1800
    16.5.14.2 Singly constrained projection of matrices
    1801
    16.5.14.3 Doubly constrained projection of matrices
    1803
    16.5.15 Projecting matrix values by territory
    1805
    16.5.15.1 Projection by territory singly constrained
    1805
    16.5.15.2 Projection by territory - element-wise
    1806

    PTVGROUP

    XLI

    Contents

    16.5.15.3 Dividing rows or cells into groups


    16.5.16 Calculating a main zone matrix from a zone matrix
    16.5.17 Calculating a zone matrix from a main zone matrix
    16.6 Changing the structure of matrices
    16.6.1 Extending external matrices during an arithmetic operation
    16.6.2 Aggregating or deleting matrix columns and rows
    16.6.2.1 Basic settings for aggregation
    16.6.2.2 Selecting rows and columns for aggregation
    16.6.3 Splitting columns and rows
    16.6.4 Saving settings for special matrix operations
    16.7 Correcting matrices
    16.7.1 Matrix update using TFlowFuzzy
    16.7.1.1 Preparing data for the matrix update
    16.7.1.2 Matrix correction using TFlowFuzzy
    16.7.1.3 TFlowFuzzy parameters
    16.7.1.4 Performing analyses of TFlowFuzzy solution procedures
    16.7.1.5 Creating a filter matrix
    16.7.1.6 Reading old TFlowFuzzy settings from file
    16.7.2 Projecting PrT path volumes
    16.7.3 Calibrating a PrT matrix
    16.8 Reading and saving demand data
    16.8.1 Reading demand data from file
    16.8.1.1 Reading the entire OD demand data file
    16.8.1.2 Reading OD demand data additively
    16.8.2 Saving demand data
    17 Setting the procedure sequence
    17.1 Setting up and starting the procedure sequence
    17.1.1 Opening the procedure sequence
    17.1.2 Adding procedures to the procedure sequence
    17.1.3 Forming and naming groups
    17.1.4 Showing or hiding the procedures of a group
    17.1.5 Duplicating procedures or groups
    17.1.6 Rearranging the order of procedures and groups in the list
    17.1.7 Setting procedures or groups to the active or inactive state
    17.1.8 Editing procedures
    17.1.9 Deleting a listed procedure or column
    17.1.10 Unlocking a group of procedures
    17.1.11 Executing procedures in the procedure sequence
    17.1.11.1 Executing a single procedure
    17.1.11.2 Executing all active procedures
    17.1.11.3 Executing marked procedures
    17.1.11.4 Executing all procedures until a certain procedure
    17.1.11.5 Resetting status information of the procedures run

    XLII

    1806
    1808
    1808
    1810
    1810
    1811
    1811
    1813
    1814
    1815
    1816
    1817
    1817
    1818
    1819
    1830
    1833
    1833
    1833
    1834
    1836
    1836
    1836
    1837
    1842
    1847
    1847
    1847
    1848
    1854
    1854
    1855
    1855
    1855
    1856
    1857
    1857
    1857
    1858
    1858
    1859
    1859
    1859

    PTVGROUP

    Contents

    17.2 Adjusting the general procedure settings


    17.2.1 Defining the analysis period
    17.2.2 Defining analysis time intervals
    17.2.2.1 Creating a single analysis time interval
    17.2.2.2 Creating multiple successive analysis time intervals
    17.2.2.3 Sorting analysis time intervals chronologically
    17.2.2.4 Deleting a single analysis time interval
    17.2.3 Saving assignment results by analysis time interval
    17.2.4 Aggregating results of analysis time intervals
    17.2.5 Setting metadata for skim matrices
    17.3 Saving procedure parameters to a file and loading them from a file
    17.3.1 Saving procedure parameter settings to file
    17.3.2 Reading procedure parameter settings from file
    17.3.2.1 Reading procedure parameter settings from *.par file
    17.3.2.2 Reading procedure parameter settings from *.xml file
    17.3.2.3 Data format of the procedure parameter file *.xml
    17.4 Calculating general procedures (PrT and PuT)
    17.4.1 Deleting PrT/PuT assignment results
    17.4.2 Analyzing the assignment quality
    17.4.2.1 Calculating assignment analysis
    17.4.2.2 Viewing assignment analysis results in a list
    17.4.2.3 Viewing assignment analysis results in a scatter diagram
    17.4.2.4 Exporting the assignment analysis chart
    17.4.3 Calculating basic territory indicators
    17.4.4 Distribution of demand matrix to paths
    17.5 Displaying the calculation status
    18 Settings for the PrT user model
    18.1 Setting parameters for PrT assignments
    18.1.1 Distributing the demand to PrT connectors
    18.1.1.1 Absolute (free) distribution of demand
    18.1.1.2 Proportional distribution of demand
    18.1.2 Settings for saving PrT assignment results
    18.1.3 Taking basic volume into account
    18.1.4 Limiting the number of non-converged network objects logged to the log
    file
    18.2 Definition and application of volume-delay functions
    18.2.1 Allocating VDFs to network object types
    18.2.1.1 Selecting VDFs for link types
    18.2.1.2 Allocating a VDF to proportional connectors without MPA
    18.2.1.3 Selecting VDFs for node types
    18.2.1.4 Selecting VDFs for turn types
    18.2.1.5 Selecting a VDF and setting the parameters
    18.2.1.6 Applying user-defined volume-delay functions
    18.2.2 Defining impedance functions for transport systems
    PTVGROUP

    1860
    1860
    1861
    1861
    1862
    1863
    1863
    1863
    1864
    1865
    1867
    1868
    1868
    1868
    1869
    1871
    1878
    1879
    1879
    1880
    1883
    1883
    1884
    1885
    1886
    1887
    1888
    1888
    1888
    1888
    1888
    1890
    1891
    1892
    1892
    1892
    1893
    1894
    1894
    1896
    1896
    1899
    1908
    XLIII

    Contents

    18.3 Calculating node impedances


    18.3.1 Selecting the method for node impedance calculation
    18.3.2 Setting the design hourly volume for node impedance calculations
    18.3.3 Calculating node impedances via Turns VDF
    18.3.4 Calculating node impedances using Nodes VDF
    18.3.5 Calculating node impedances using Node impedance calculation (ICA)
    18.3.5.1 Signalized nodes (LOS)
    18.3.5.2 Two-way stop nodes (LOS)
    18.3.5.3 Roundabout
    18.3.5.4 All-way stop (LOS)
    18.3.5.5 Uncontrolled nodes (TModel)
    18.3.6 Using VD functions of assignment with ICA for other assignments
    18.3.7 Methods for node impedance calculation
    18.4 Signal timing optimization and coordination
    18.4.1 Optimizing signal cycle and split times for active nodes
    18.4.2 Signal offset optimization
    18.4.3 SC offset analysis
    18.5 Blocking back model settings and calculation
    18.5.1 Executing an assignment with the blocking back model
    18.5.2 Executing the blocking back model after assignment
    18.6 Setting and calculating the parameters for PrT assignment
    18.6.1 Incremental assignment (static)
    18.6.1.1 Selecting and executing incremental assignment
    18.6.1.2 Parameters of incremental assignment
    18.6.2 Equilibrium assignment (static)
    18.6.2.1 Selecting and executing the Equilibrium assignment
    18.6.2.2 Parameters of Equilibrium assignment
    18.6.3 Equilibrium assignment LUCE
    18.6.3.1 Selecting and executing the Equilibrium assignment LUCE
    18.6.3.2 Parameters of Equilibrium assignment LUCE
    18.6.4 Equilibrium_Lohse assignment (static)
    18.6.4.1 Selecting and executing Equilibrium_Lohse
    18.6.4.2 Parameters of the Equilibrium_Lohse assignment
    18.6.5 Assignment with ICA
    18.6.5.1 Selecting and executing Assignment with ICA
    18.6.5.2 Parameters for Assignment with ICA
    18.6.6 Stochastic assignment (static)
    18.6.6.1 Selecting and executing the Stochastic assignment
    18.6.6.2 Parameters of Stochastic assignment
    18.6.7 TRIBUT - Equilibrium assignment
    18.6.7.1 Selecting and executing the TRIBUT - Equilibrium assignment
    18.6.7.2 Parameters of TRIBUT - Equilibrium assignment
    18.6.8 TRIBUT - Equilibrium_Lohse (static)

    XLIV

    1911
    1911
    1912
    1913
    1914
    1914
    1917
    1918
    1918
    1919
    1919
    1920
    1921
    1921
    1921
    1923
    1925
    1925
    1926
    1927
    1931
    1932
    1932
    1933
    1934
    1934
    1935
    1939
    1939
    1941
    1942
    1943
    1944
    1946
    1946
    1948
    1951
    1951
    1953
    1961
    1961
    1963
    1966

    PTVGROUP

    Contents

    18.6.8.1 Selecting and executing TRIBUT - Equilibrium_Lohse


    18.6.8.2 Parameters of the TRIBUT - Equilibrium_Lohse assignment
    18.6.9 Dynamic User Equilibrium (DUE)
    18.6.9.1 Selecting and executing the Dynamic User Equilibrium
    18.6.9.2 Parameters of Dynamic User Equilibrium (DUE)
    18.6.10 Dynamic stochastic assignment
    18.6.10.1 Selecting and executing the Dynamic stochastic assignment
    18.6.10.2 Parameters of Dynamic stochastic assignment
    18.7 Evaluating the goodness of the PrT assignment
    18.7.1 Viewing convergence criteria and convergence speed
    18.7.2 NCHRP 255 (Post-processor for PrT assignments)
    18.8 Calculating:PrT skims
    18.8.1 Setting parameters for PrT skim matrices
    18.8.1.1 Defining units for PrT skims
    18.8.1.2 User-defined PrT skims
    18.8.2 Calculating PrT skim matrices
    18.8.3 Setting parameters for the calculation of PrT skim matrices
    19 Settings for the PuT user model
    19.1 Setting parameters for PuT assignments
    19.1.1 Settings for calculating and saving results
    19.1.1.1 Round demand and volume data
    19.1.1.2 Settings for saving PuT assignment results
    19.1.1.3 Limiting the path leg time
    19.1.1.4 Restricting the walk link search
    19.1.2 Saving volumes by demand segment or additively
    19.1.3 Coordination groups for headway-based assignment
    19.1.3.1 Creating a coordination group
    19.1.3.2 Editing a coordination group
    19.1.3.3 Deleting a coordination group
    19.2 Setting and calculating PuT assignment parameters
    19.2.1 Selecting and executing a PuT assignment procedure
    19.2.2 Parameters of the TSys-based assignment
    19.2.2.1 Transport system-based assignment:Basis tab
    19.2.2.2 Transport system-based assignment:Search tab
    19.2.2.3 Transport system-based assignment: Skim matrices tab
    19.2.3 Parameters of headway-based assignment
    19.2.3.1 Headway-based assignment:Basis tab
    19.2.3.2 Headway-based assignment:Search tab
    19.2.3.3 Headway-based assignment:Demand segments tab
    19.2.3.4 Headway-based assignment:Impedance tab
    19.2.3.5 Headway-based assignment: Skim matrices tab
    19.2.4 Parameters of timetable-based assignment
    19.2.4.1 Timetable-based assignment:Basis tab
    19.2.4.2 Timetable-based assignment:Search tab

    PTVGROUP

    1966
    1969
    1969
    1970
    1971
    1976
    1976
    1978
    1982
    1982
    1983
    1984
    1984
    1985
    1986
    1988
    1989
    1995
    1995
    1995
    1995
    1996
    1999
    2000
    2003
    2004
    2004
    2005
    2005
    2006
    2006
    2007
    2007
    2008
    2010
    2010
    2011
    2014
    2018
    2019
    2021
    2021
    2022
    2025

    XLV

    Contents

    19.2.4.3 Timetable-based assignment:Preselection tab


    2030
    2034
    19.2.4.4 Timetable-based assignment:Demand segments tab
    19.2.4.5 Timetable-based assignment:Impedance tab
    2034
    2041
    19.2.4.6 Timetable-based assignment:Choice tab
    19.2.4.7 Timetable-based assignment:Capacity restriction tab
    2042
    19.2.4.8 Timetable-based assignment:Vol/Cap ratio-dependent impedance tab2044
    19.2.4.9 Timetable-based assignment:Skim matrices tab
    2046
    2047
    19.2.4.10 Timetable-based assignment:Connection export tab
    19.3 Importing, checking and assigning passenger onboard surveys
    2051
    19.3.1 Preparing survey sample data
    2051
    19.3.1.1 Format of a single-row survey file
    2052
    19.3.1.2 Format of a multi-row survey file
    2053
    19.3.2 Read survey data
    2055
    19.3.2.1 Settings for reading survey data from file
    2057
    19.3.3 Plausibilization of survey data
    2059
    19.3.3.1 Settings for plausibilization of survey data records
    2060
    19.3.3.2 Viewing results of plausibilization
    2070
    19.3.4 Assignment of survey data
    2071
    19.3.4.1 Parameters of direct assignment
    2072
    19.4 Calculating PuT skims
    2073
    19.4.1 Setting parameters for PuT skim matrices
    2074
    19.4.2 Calculating PuT skim matrices
    2076
    19.4.3 Calculating skim matrices during an assignment
    2078
    19.4.4 Settings for PuT skim matrix calculation
    2078
    19.4.4.1 PuT skim matrices:Aggregation section
    2079
    19.4.4.2 PuT skim matrices:Analyzed OD pairs section
    2082
    19.4.4.3 PuT skim matrices:List of PuT skims
    2083
    19.4.4.4 PuT skim matrices:Settings for journey time equivalent
    2083
    19.4.4.5 PuT skim matrices:Output file section
    2084
    19.5 Calculate service trip patterns
    2086
    20 Settings for the PuT operator model
    2091
    20.1 Calculating PuT line blocks
    2091
    20.1.1 Managing line block versions
    2091
    20.1.1.1 Creating a line block version
    2091
    20.1.1.2 Attributes of line block versions
    2093
    20.1.1.3 Editing a block version
    2097
    20.1.1.4 Checking the coverage
    2098
    20.1.1.5 Performing the line block check
    2099
    20.1.1.6 Selecting the active line block version
    2101
    20.1.1.7 Deleting a line block version
    2101
    20.1.2 Managing line block item types
    2102
    20.1.2.1 Creating a block item type
    2102
    20.1.2.2 Attributes of block item types
    2103
    20.1.2.3 Editing a block item type
    2103

    XLVI

    PTVGROUP

    Contents

    20.1.2.4 Deleting a block item type


    20.1.3 Executing the PuT line blocking procedure
    20.1.3.1 Executing the line blocking procedure
    20.1.3.2 Parameters of the line blocking procedure
    20.1.3.3 Additional parameters for line blocking with vehicle interchange
    20.1.3.4 Initializing PuT line blocking
    20.1.4 Tabular output of line block results
    20.1.5 Displaying line blocks in the block view
    20.1.5.1 Opening the block view
    20.1.5.2 Filtering displayed block items by a valid day
    20.1.5.3 Editing the time of the day change
    20.1.5.4 Displaying free actions in the block view
    20.1.5.5 Printing or exporting free actions
    20.1.5.6 Finding a block item in the block view
    20.1.5.7 Influencing program behavior when inserting block items
    20.1.5.8 Setting graphic parameters for the block view
    20.1.5.9 Printing or exporting the Block view
    20.1.6 Editing block versions and line blocks
    20.1.6.1 Marking items in the block view
    20.1.6.2 Copying line blocks or block versions
    20.1.6.3 Creating a line block
    20.1.6.4 Properties and options of line blocks
    20.1.6.5 Fixing a line block
    20.1.6.6 Editing a line block
    20.1.6.7 Resolving line blocks
    20.1.6.8 Deleting line blocks
    20.1.6.9 Creating a block day
    20.1.6.10 Deleting a block day
    20.1.6.11 Creating a user-defined block item
    20.1.6.12 Editing a block item
    20.1.6.13 Shifting block items to different line block or block day
    20.1.6.14 Inserting free actions into a line block
    20.1.6.15 Shifting empty trips and user-defined block items to another time
    20.1.6.16 Deleting block items
    20.1.6.17 Editing vehicle journeys and vehicle journey sections
    20.1.6.18 Converting an empty trip into a vehicle journey
    20.1.6.19 Shifting a standstill from/to depot
    20.1.7 Setting forced chainings
    20.1.7.1 Creating a forced chaining
    20.1.7.2 Editing forced chainings
    20.1.7.3 Deleting forced chainings
    20.1.8 Calculating skim matrices for interlining trips
    20.1.8.1 Performing the PuT interlining matrix procedure
    20.1.8.2 Setting parameters for PuT interlining matrices
    20.1.8.3 Examples for PuT interlining matrices

    PTVGROUP

    2103
    2104
    2104
    2105
    2114
    2118
    2119
    2119
    2120
    2121
    2121
    2121
    2123
    2123
    2123
    2124
    2129
    2129
    2129
    2130
    2132
    2133
    2135
    2135
    2136
    2136
    2136
    2137
    2137
    2138
    2139
    2140
    2140
    2141
    2141
    2141
    2143
    2144
    2144
    2147
    2148
    2148
    2148
    2149
    2152

    XLVII

    Contents

    20.2 Creating a cost model


    20.2.1 Infrastructure costs
    20.2.2 Vehicle-bound costs
    20.2.2.1 Defining cost rates by vehicle unit
    20.2.2.2 Defining cost rates by vehicle combination
    20.2.2.3 Calculating vehicle-bound costs
    20.3 Calculating PuT operating indicators
    20.3.1 Carrying out the procedure PuT operating indicators
    20.3.2 Parameters for PuT operating indicators calculation
    20.3.2.1 PuT operating indicators:General tab
    20.3.2.2 PuT operating indicators: Transport supply tab
    20.3.2.3 PuT operating indicators:Network performance tab
    20.3.2.4 PuT operating indicators:Revenue tab
    20.3.2.5 PuT operating indicators:Infrastructure cost tab
    20.3.2.6 PuT operating indicators: User-defined attributes tab
    20.3.3 Discarding calculated PuT operating indicators
    20.4 Revenue calculation using a fixed revenue per PTripUnlinked
    20.5 Revenue calculation using revenue per fare point
    20.5.1 Inserting fare points at network objects
    20.5.1.1 Defining fare points of links by transport system
    20.5.1.2 Defining fare points at time profile items
    20.6 Revenue calculation using the fare model
    20.6.1 Using fare points
    20.6.2 Using fare zones
    20.6.2.1 Defining fare zones
    20.6.2.2 Properties and options of fare zones
    20.6.2.3 Editing attribute values of fare zones
    20.6.2.4 Deleting a fare zone
    20.6.3 Defining PuT fares
    20.6.3.1 Defining fare systems
    20.6.3.2 Creating ticket types
    20.6.3.3 Allocating transfer fares to fare systems
    20.6.3.4 Allocating ticket types to demand segments and fare systems
    20.6.3.5 Setting general options for PuT fares
    21 Settings for the environmental impact model and emission calculation according
    to HBEFA
    21.1 Setting environmental impact parameters
    21.2 Editing environmental link attributes
    21.3 Resetting the calculation
    21.4 Calculating noise volumes
    21.5 Displaying noise volumes
    21.5.1 Graphic display of noise volumes
    21.5.2 List output of noise volumes
    21.6 Saving noise volumes

    XLVIII

    2153
    2153
    2153
    2153
    2154
    2155
    2156
    2156
    2156
    2157
    2157
    2159
    2159
    2162
    2165
    2166
    2167
    2167
    2168
    2168
    2168
    2169
    2169
    2169
    2169
    2170
    2171
    2171
    2171
    2172
    2173
    2179
    2180
    2181
    2183
    2183
    2185
    2185
    2185
    2187
    2187
    2188
    2188

    PTVGROUP

    Contents

    21.7 Calculating air pollution emissions


    21.8 Displaying air pollution emissions
    21.8.1 Graphic display of air pollution emissions
    21.8.2 List output of noise volumes
    21.9 Saving air pollution emissions
    21.10 Settings for emission calculation according to HBEFA
    21.10.1 Defining fleet compositions for the calculation
    21.10.1.1 Creating a fleet composition
    21.10.1.2 Attributes and options of fleet compositions
    21.10.1.3 Editing fleet compositions
    21.10.1.4 Duplicating fleet compositions
    21.10.1.5 Combining existing fleet compositions
    21.10.1.6 Adopting fleet compositions from HBEFA
    21.10.1.7 Editing subsegment shares
    21.10.1.8 Deleting a fleet composition
    21.10.2 Input attributes for calculation
    21.10.3 Calculating emissions according to HBEFA
    21.10.3.1 Emission calculation according to HBEFA
    21.10.3.2 Parameters of the HBEFA procedure
    21.10.4 Resetting emission calculation
    21.10.5 Displaying the emission calculation results
    21.10.5.1 Displaying the results in lists
    21.10.5.2 Graphic display of HBEFA results
    21.10.6 Saving HBEFA results
    22 Using GIS functionalities
    22.1 Editing the coordinate system and scale
    22.1.1 Selecting a coordinate system
    22.1.2 Editing the network scale
    22.1.3 Recalculating lengths
    22.1.4 Rotating and/or shifting the network
    22.2 GIS objects
    22.2.1 Connecting Visum to a Personal Geodatabase
    22.2.2 Finding a GIS object
    22.2.3 Selecting GIS objects
    22.2.3.1 Marking a GIS object
    22.2.3.2 Marking several GIS objects
    22.2.3.3 Setting GIS objects active/passive
    22.2.4 Editing attribute values of GIS objects
    22.2.4.1 Editing the attribute values of a GIS object
    22.2.4.2 Editing the attribute values of marked GIS objects
    22.2.4.3 Editing the attribute values of all or all active GIS objects
    22.2.5 Setting graphic parameters for GIS objects
    22.2.6 Output of GIS objects in lists

    PTVGROUP

    2188
    2190
    2190
    2191
    2191
    2191
    2192
    2192
    2193
    2193
    2194
    2194
    2195
    2196
    2197
    2197
    2198
    2198
    2199
    2203
    2203
    2204
    2204
    2205
    2207
    2207
    2207
    2209
    2209
    2210
    2211
    2211
    2212
    2213
    2213
    2214
    2214
    2214
    2214
    2214
    2214
    2215
    2217

    XLIX

    Contents

    22.2.7 Disconnecting a Personal Geodatabase


    22.3 Intersecting objects
    22.4 The Shapefiles interface
    22.4.1 Importing Shapefiles
    22.4.2 Exporting Shapefiles
    22.5 Inserting additional information in the network display
    22.6 Using texts in the network display
    22.6.1 Inserting background/legend text
    22.6.2 Editing background/legend text
    22.6.3 Shifting a text
    22.6.4 Rotating a text
    22.6.5 Copying and pasting a text
    22.6.6 Background/legend text parameters
    22.6.7 Deleting a text
    22.6.8 Editing the font size of background / legend texts
    22.6.9 Editing the font of background / legend texts
    22.6.10 Deleting all existing background / legend texts
    22.6.11 Saving texts
    22.6.12 Reading texts
    22.7 Using backgrounds in the network display
    22.7.1 Inserting background images of map services on the Internet
    22.7.1.1 Dynamically embedding background maps provided on the Internet
    22.7.1.2 Statically embedding background maps provided on the Internet
    22.7.1.3 Specifying default settings for inserting background maps
    22.7.2 Creating a background from a file
    22.7.3 Editing the drawing order of backgrounds
    22.7.4 Showing and hiding backgrounds
    22.7.5 Editing a background manually
    22.7.6 Measuring links with the scale
    22.7.7 Editing a background
    22.7.7.1 Setting a tie point
    22.7.8 Editing backgrounds of type shape
    22.7.9 Deleting backgrounds
    22.7.10 Saving a background
    22.7.11 Generating world file
    22.8 Using polygons in the network display
    22.8.1 Creating a rectangle
    22.8.2 Creating lines/polygons
    22.8.3 Editing the properties of a closed polygon
    22.8.4 Editing the properties of an open polygon
    22.8.5 Shifting a polygon
    22.8.6 Copying and pasting a polygon
    22.8.7 Deleting a polygon

    2217
    2217
    2221
    2221
    2230
    2232
    2232
    2232
    2233
    2233
    2233
    2234
    2234
    2235
    2235
    2236
    2236
    2237
    2237
    2237
    2237
    2237
    2239
    2240
    2243
    2244
    2244
    2245
    2246
    2247
    2249
    2249
    2250
    2250
    2251
    2251
    2251
    2251
    2252
    2253
    2253
    2254
    2254

    PTVGROUP

    Contents

    22.8.8 Deleting all polygons


    2254
    22.8.9 Saving polygons
    2255
    22.9 Creating legends
    2255
    22.9.1 Inserting legends
    2255
    22.9.2 Editing the legend
    2260
    22.9.3 Hiding the legend
    2260
    2260
    22.9.4 Opening and saving legend parameters
    22.9.4.1 Saving legend parameters
    2260
    22.9.4.2 Opening legend parameters
    2261
    22.10 GPS tracking
    2261
    22.10.1 Setting graphic parameters for the GPS signal
    2262
    23 Settings for interactive analyses
    2265
    23.1 Displaying flow bundles
    2265
    23.1.1 Inserting a flow bundle
    2265
    23.1.1.1 Setting a network object as flow bundle condition
    2266
    23.1.1.2 Using PuT network objects to make settings for flow bundle conditions2269
    23.1.1.3 Filtering paths via active and passive network objects and traffic types 2271
    23.1.1.4 Linking flow bundle conditions with AND THEN and OR
    2273
    23.1.2 Setting graphic parameters for the display of flow bundles
    2275
    23.1.3 Displaying flow bundles in lists
    2277
    23.1.4 Saving flow bundle volumes
    2278
    23.2 Displaying isochrones and the accessibility of network objects
    2278
    23.2.1 Displaying isochrones and accessibility in PrT
    2279
    23.2.1.1 Displaying PrT isochrones
    2279
    23.2.1.2 Displaying the accessibility of links
    2281
    23.2.1.3 Displaying the accessibility of network object types in PrT according to
    classes
    2283
    23.2.2 Displaying isochrones and accessibility in PuT
    2285
    23.2.2.1 Displaying PuT isochrones
    2285
    23.2.2.2 Displaying the accessibility of network object in PuT
    2287
    23.2.3 Setting graphic parameters for the display of isochrones
    2288
    23.2.4 Displaying isochrones in lists
    2290
    23.2.5 Saving isochrones
    2290
    23.3 Searching for and displaying shortest paths
    2291
    23.3.1 Shortest path search PrT
    2291
    23.3.2 Shortest path search PuT
    2292
    23.3.3 Setting the graphic parameters for shortest paths
    2296
    23.3.4 Displaying shortest path searches in lists
    2297
    23.3.5 Saving a shortest path search
    2298
    24 Displaying data graphically and in lists
    2299
    24.1 Working with lists
    2299
    24.1.1 Opening a list
    2299
    24.1.2 The list window
    2304

    PTVGROUP

    LI

    Contents

    24.1.3 Setting list options


    24.1.4 Adjusting the list layout
    24.1.4.1 Editing window headers of lists
    24.1.4.2 Viewing/Hiding attributes
    24.1.4.3 Adding statistical evaluation data rows to a list
    24.1.4.4 Fixing the columns of a list
    24.1.4.5 Adjusting the column width to the contents
    24.1.4.6 Aggregating rows of a list
    24.1.4.7 Saving a list layout
    24.1.4.8 Reading a list layout
    24.1.5 Sorting a list
    24.1.5.1 Sorting a list by one column
    24.1.5.2 Sorting a list by several columns
    24.1.6 Applying filters to lists
    24.1.6.1 Show only active network objects
    24.1.6.2 Limiting list display to a selection
    24.1.7 Finding objects in lists
    24.1.7.1 Finding an object in a list
    24.1.7.2 Finding object in either direction
    24.1.7.3 Searching for data records in PuT path lists
    24.1.7.4 Finding objects in PrT paths lists
    24.1.8 Selecting list sections
    24.1.8.1 Marking list sections with the mouse
    24.1.8.2 Selecting list sections via the keyboard
    24.1.9 Synchronizing network object lists with other windows
    24.1.10 Editing the properties of objects in lists
    24.1.10.1 Editing attribute values in a list
    24.1.10.2 Using attribute values for calculations in a network object list
    24.1.11 Delete object in list
    24.1.12 Importing and exporting list contents
    24.1.12.1 Save list to attribute file
    24.1.12.2 Reading attribute data into lists
    24.1.12.3 Exchanging list contents via the Clipboard
    24.1.12.4 Exporting attributes to a database
    24.1.13 Printing a list and print settings
    24.1.13.1 Specifying the layout for list printout
    24.1.13.2 Printing a list
    24.1.13.3 Saving the list as a PDF
    24.2 Specifying basic settings for the network window
    24.2.1 Specifying basic settings
    24.2.2 Editing the display and order of drawing settings for graphic layers
    24.3 Displaying point objects in the network window
    24.3.1 Displaying active point objects
    24.3.2 Displaying passive point objects

    LII

    2306
    2308
    2309
    2309
    2309
    2310
    2310
    2311
    2313
    2314
    2314
    2314
    2315
    2315
    2315
    2315
    2317
    2318
    2318
    2318
    2318
    2319
    2319
    2320
    2320
    2321
    2321
    2323
    2324
    2325
    2325
    2328
    2328
    2329
    2331
    2331
    2336
    2336
    2337
    2337
    2339
    2341
    2341
    2346

    PTVGROUP

    Contents

    24.3.3 Displaying marked point objects


    2347
    24.3.4 Displaying traversed stop points
    2347
    24.3.5 Displaying Points of Interest
    2348
    24.3.5.1 Displaying Points of Interest
    2348
    2350
    24.3.5.2 Editing the display settings of a POI category
    24.3.5.3 Applying display settings to sub-categories
    2350
    2351
    24.3.5.4 Defining the standard display for the display of POIs
    24.3.5.5 Showing POI connections
    2351
    24.3.6 Displaying GIS objects
    2352
    24.3.7 Two-dimensional display of attribute values around point objects
    2352
    24.4 Displaying line objects in the network window
    2354
    24.4.1 Displaying active line objects
    2355
    24.4.2 Displaying passive line objects
    2358
    24.4.3 Displaying marked line objects
    2358
    24.4.4 Displaying one-way roads
    2359
    24.4.5 Labeling line objects
    2359
    24.4.5.1 Labeling active line objects
    2359
    24.4.5.2 Labeling passive line objects
    2362
    24.4.5.3 Labeling marked line objects
    2363
    24.4.6 Setting the line style properties
    2363
    24.4.7 Setting parameters for the line style
    2365
    24.5 Displaying properties via bars
    2367
    24.5.1 Displaying bars and adjusting basic settings
    2368
    24.5.2 Defining one or multiple bars
    2373
    24.5.3 Setting the display properties of a bar
    2374
    24.5.3.1 Setting the display properties of a standard bar
    2375
    24.5.3.2 Configuring a difference bar display
    2379
    24.5.3.3 Configuring the display of a PuT line bar
    2380
    24.5.3.4 Configuring the display of a PrT path bar
    2386
    24.6 Displaying route courses in the network window
    2387
    24.7 Displaying stop catchment areas in the network window
    2389
    24.7.1 Activating the display of stop catchment areas
    2389
    24.7.2 Editing the graphic parameters of stop catchment areas
    2389
    24.8 Displaying transfer relations between stop areas
    2392
    24.8.1 Displaying transfer relations
    2392
    24.9 Displaying connections and transfer flows at stops
    2392
    24.9.1 Activating the transfers display of regular services
    2392
    24.9.2 Setting the bar display for transfer flows
    2394
    24.9.3 Synchronizing the transfers display of regular services with other windows 2395
    24.9.4 Setting the graphic parameters for the Transfers display of regular services
    2396
    24.9.4.1 Setting graphic parameters for arrival and departure groups in the
    transfers display of regular services
    2396

    PTVGROUP

    LIII

    Contents

    24.9.4.2 Setting the graphic parameters for transfer flows


    24.9.4.3 Setting graphic parameters for the print frame
    24.9.5 Reading and saving graphic parameters for the Transfers display of regular services
    24.9.5.1 Saving the graphic parameters of the transfers display of regular services
    24.9.5.2 Opening graphic parameters of the transfers display of regular services
    24.9.6 Printing or exporting the transfers display of regular services
    24.9.6.1 Printing the transfers display of regular services
    24.9.6.2 Exporting the transfers display of regular services as graphics file
    24.10 Displaying lane allocations in the network window
    24.10.1 Activating the display of lane allocations
    24.10.2 Setting graphic parameters for lane allocation
    24.11 Labeling network objects with tables or charts
    24.11.1 Labeling network objects with tables
    24.11.2 Labeling network objects with column charts
    24.11.3 Labeling network objects with pie charts
    24.12 Displaying classified objects based on attribute values
    24.12.1 Setting up classes and class limits for classification
    24.12.2 Editing the classification classes
    24.12.2.1 Changing the classification settings of a point object
    24.12.2.2 Changing the classification settings of a line object
    24.12.2.3 Editing the colors of all classes
    24.12.2.4 Editing the sizes for all classes
    24.12.3 Creating and deleting an individual class
    24.12.4 Editing the display settings and class limits of a class
    24.12.4.1 Editing the display settings and class limits of a point object class
    24.12.4.2 Editing the display settings and class limits of a line object class
    24.13 Displaying desire lines
    24.13.1 Displaying desire line bars and adjusting basic settings
    24.13.2 Displaying bars for desire lines
    24.13.3 Hiding the display of single desire lines
    24.14 Displaying turns, main turns, and turn volumes
    24.14.1 Displaying turns and main turns
    24.14.2 Adjusting the basic settings for the display of turn volumes
    24.14.3 Displaying turn volumes
    24.14.3.1 Displaying turn volumes at single nodes
    24.14.3.2 Displaying the turn volumes of the visible nodes
    24.14.4 Hiding turn volumes
    24.14.5 Editing the display of turn volumes in the network window
    24.14.5.1 Editing the radius of turn volumes
    24.14.5.2 Hiding/Showing turn volume labels
    24.14.6 Exporting turn volumes
    LIV

    2397
    2398
    2398
    2399
    2399
    2399
    2399
    2400
    2400
    2400
    2401
    2402
    2402
    2405
    2409
    2411
    2412
    2414
    2414
    2415
    2416
    2421
    2422
    2423
    2423
    2426
    2429
    2429
    2433
    2434
    2435
    2435
    2437
    2441
    2442
    2443
    2444
    2445
    2445
    2446
    2446

    PTVGROUP

    Contents

    24.15 Showing/hiding extended markings


    2448
    24.15.1 Highlighting related network objects permanently
    2449
    24.15.2 Disabling the highlighting of the related network objects permanently
    2450
    24.15.3 Highlighting related network objects temporarily
    2450
    24.16 Creating schematic line diagrams
    2451
    24.16.1 Opening schematic line diagrams
    2451
    2452
    24.16.2 Selecting display level for displayed edges
    24.16.3 Displaying stops in the schematic line diagram
    2452
    24.16.3.1 Displaying individual stops as transfer nodes
    2452
    24.16.3.2 Displaying active stops as transfer nodes
    2452
    24.16.4 Displaying vehicle journeys in the schematic line diagram
    2453
    24.16.5 Setting graphic parameters for the schematic line diagram
    2455
    24.16.5.1 Showing help grids
    2455
    24.16.5.2 Setting the display of transfer nodes
    2456
    24.16.5.3 Setting the display of edge courses
    2459
    24.16.5.4 Setting graphics parameters for the label of the edge courses
    2464
    24.16.5.5 Setting the display properties of edge course bars
    2465
    24.16.5.6 Setting the display properties of transfer bars
    2466
    24.16.5.7 Setting the display properties for branches
    2466
    24.16.5.8 Setting the display properties of the print frame
    2467
    24.16.5.9 Creating legend for the schematic line diagram
    2467
    24.16.6 Post-processing schematic line diagrams
    2467
    24.16.6.1 Manually editing schematic line diagrams
    2467
    24.16.6.2 Separating all edges
    2472
    24.16.6.3 Bundling edges according to conditions
    2472
    24.16.6.4 Deleting unused edge courses
    2474
    24.16.7 Synchronizing the schematic line diagram with other windows
    2474
    24.16.8 Setting the layout for schematic line diagrams
    2475
    24.16.9 Reading and saving the layout of schematic line diagrams
    2478
    24.16.9.1 Saving the layout of a schematic line diagram
    2478
    24.16.9.2 Reading the layout of a schematic line diagram
    2479
    24.16.10 Displaying statistics
    2479
    24.17 Displaying signal time-space diagrams
    2479
    24.17.1 Opening a signal time-space diagram
    2480
    24.17.2 The signal time-space diagram window
    2482
    24.17.3 Adjusting the signal time-space diagram
    2483
    24.17.4 Synchronizing the signal time-space diagram with other windows
    2485
    24.17.5 Changing offsets in the signal time-space diagram
    2487
    24.17.6 Setting graphic parameters for the signal time-space diagram
    2487
    24.17.7 Saving and reading the graphic parameters of the signal time-space diagram
    2490
    24.17.7.1 Saving the graphic parameters of the signal time-space diagram
    2490
    24.17.7.2 Opening graphic parameters of the signal time-space diagram
    2491
    24.17.8 Printing or exporting the signal time-space diagram
    2491
    PTVGROUP

    LV

    Contents

    24.18 Creating column charts


    24.18.1 Displaying column charts
    24.18.2 Exporting a column chart
    24.19 Reading and saving the graphic parameters of the network window
    24.19.1 Saving the graphic parameters of the network window
    24.19.2 Reading graphic parameters of the network window
    24.20 Printing the network display
    24.20.1 Set print page
    24.20.2 Specifying the print area
    24.20.3 Setting the print frame
    24.20.4 Preview of the print output
    24.20.5 Starting print output
    25 Using interfaces for data exchange
    25.1 ANM interface
    25.1.1 Transferring data from Visum to Vissim
    25.1.2 Saving an abstract network model
    25.1.3 Saving settings for a Vissim export
    25.1.4 Reading settings for a Vissim export
    25.1.5 Reading an abstract network model
    25.1.6 Exporting subnetworks via ANM interface
    25.1.7 Description of the data generated by an ANM import
    25.2 Editing a signal control in Vissig
    25.2.1 Creating a signal control of the type Vissig
    25.2.2 Editing a controller of the type Vissig
    25.2.3 The Vissig window
    25.2.4 Setting a language in Vissig
    25.2.5 Specifying general settings for the signal control
    25.2.6 Signal states in Vissig
    25.2.7 Managing signal groups
    25.2.7.1 Creating a signal group
    25.2.7.2 Duplicating a signal group
    25.2.7.3 Editing signal groups
    25.2.7.4 Deleting a signal group
    25.2.8 Managing intergreen matrices
    25.2.8.1 Creating an intergreen matrix
    25.2.8.2 Duplicating an intergreen matrix
    25.2.8.3 Editing an intergreen matrix
    25.2.8.4 Deleting an intergreen matrix
    25.2.8.5 Importing intergreens from Excel
    25.2.9 Managing stages
    25.2.9.1 Adjusting the stage display
    25.2.9.2 Creating a stage
    25.2.9.3 Editing stages

    LVI

    2492
    2492
    2496
    2496
    2496
    2497
    2499
    2499
    2502
    2504
    2508
    2508
    2511
    2511
    2512
    2512
    2516
    2516
    2516
    2517
    2518
    2528
    2529
    2530
    2530
    2530
    2531
    2531
    2532
    2532
    2532
    2533
    2534
    2534
    2535
    2535
    2535
    2535
    2535
    2536
    2536
    2536
    2537

    PTVGROUP

    Contents

    25.2.9.4 Duplicating a stage


    25.2.9.5 Deleting a stage
    25.2.10 Editing stage assignments
    25.2.10.1 Selecting a default intergreen matrix
    25.2.10.2 Assigning stages
    25.2.11 Specifying a stage sequence and creating a signal program
    25.2.11.1 Exporting a stage sequence
    25.2.12 Managing signal programs
    25.2.12.1 Creating signal group-based signal programs manually
    25.2.12.2 Editing signal group-based signal programs
    25.2.12.3 Editing stage-based signal programs
    25.2.12.4 Exporting a signal program as graphics file
    25.2.13 Managing interstages
    25.2.13.1 Inserting an interstage manually
    25.2.13.2 Duplicating an interstage
    25.2.13.3 Editing an interstage
    25.2.13.4 Optimizing interstages
    25.2.13.5 Deleting an interstage
    25.2.13.6 Exporting interstages as graphic files
    25.2.13.7 Exporting interstages as PUA files
    25.2.14 Managing daily signal program lists
    25.2.14.1 Creating a daily signal program list
    25.2.14.2 Duplicating daily signal program lists
    25.2.14.3 Editing a daily signal program list
    25.2.14.4 Deleting a daily signal program list
    25.2.15 Specifying settings for the export of graphic files
    25.2.16 Export to Excel
    25.2.17 Detecting inconsistent planning scenarios
    25.2.17.1 Detecting intergreen violations
    25.2.17.2 Detecting invalid interstages
    25.2.18 Returning to Visum from Vissig
    25.2.19 Switching off or manually changing signal programs in Visum
    25.2.20 Automatically changing or switching off signal programs in Visum
    25.2.21 Converting a Vissig signal control into a Visum signal control
    25.3 Reading connections and routes
    25.3.1 Connections:importing
    25.3.2 Importing routes
    25.3.3 Extended route import
    25.4 HAFAS import
    25.4.1 Importing HAFAS data
    25.4.2 Notes on the imported HAFAS data
    25.4.3 Saving settings for HAFAS import
    25.4.4 Reading settings for the HAFAS import
    25.4.5 Resetting the HAFAS import settings
    PTVGROUP

    2538
    2538
    2538
    2539
    2539
    2539
    2541
    2542
    2542
    2543
    2547
    2548
    2549
    2549
    2550
    2550
    2552
    2552
    2552
    2553
    2553
    2553
    2554
    2554
    2555
    2555
    2556
    2556
    2556
    2557
    2558
    2558
    2558
    2560
    2560
    2560
    2561
    2562
    2565
    2566
    2570
    2573
    2573
    2573

    LVII

    Contents

    25.5 RailML interface


    25.5.1 Importing RailML data
    25.5.2 Notes on imported railML data
    25.5.3 Saving settings for railML import
    25.5.4 Reading in settings for railML import
    25.5.5 Resetting the railML import settings
    25.5.6 Exporting Visum data to railML
    25.5.7 Saving settings for railML export
    25.5.8 Loading settings for railML export
    25.5.9 Resetting railML export settings
    25.6 EMME/2 import
    25.6.1 Importing EMME/2 data
    25.6.2 Saving the settings for the EMME/2 import
    25.6.3 Reading the settings for an EMME/2 import
    25.6.4 Resetting the EMME/2 import settings
    25.7 TModel import
    25.7.1 Importing TModel data
    25.7.2 Saving settings for the TModel import
    25.7.3 Reading settings for the TModel import
    25.7.4 Resetting the TModel import settings
    25.8 SATURN import
    25.8.1 Importing SATURN data
    25.8.2 Description of the network file generated through SATURN import
    25.8.3 SATURN import: Notes on changes to the network topology
    25.8.3.1 Basic rules for reading connectors in the simulation network
    25.8.3.2 Different cases for importing connectors
    25.8.4 Notes on data adjustment for assignment with ICA
    25.8.4.1 SATURN import: Node and turn attribute values
    25.8.4.2 SATURN import: Nodes with control type "unknown"
    25.8.4.3 SATURN import: New signal group for unsignalized left turns
    25.9 OpenStreetMap import
    25.9.1 Notes on the data generated from OpenStreetMap data
    25.9.2 Importing OpenStreetMap data
    25.9.2.1 Downloading and preparing OpenStreetMap data
    25.9.2.2 Running the import process with a predefined configuration
    25.9.2.3 Checking the import results
    25.9.3 Adapting the import process
    25.9.3.1 Running the import process with a user-defined configuration
    25.9.4 Structure of the configuration sets
    25.9.4.1 Network file with default settings
    25.9.4.2 Configuration file for import parameters
    25.9.4.3 Defining the import process
    25.9.4.4 Expressions

    LVIII

    2573
    2574
    2581
    2584
    2584
    2585
    2585
    2586
    2587
    2587
    2587
    2588
    2591
    2591
    2592
    2592
    2592
    2594
    2594
    2595
    2595
    2595
    2596
    2610
    2610
    2611
    2613
    2613
    2613
    2614
    2614
    2615
    2617
    2617
    2617
    2618
    2619
    2619
    2620
    2620
    2620
    2623
    2623

    PTVGROUP

    Contents

    25.10 VDV 452 interface


    25.10.1 Importing VDV 452 data
    25.10.2 Comparison of VDV 452 and Visum data model
    25.10.3 Exporting Visum data to VDV 452
    25.11 Database interface
    25.11.1 Exporting Visum data to an Access database
    25.11.2 Exporting Visum data to an SQL database
    25.11.3 Importing an Access database
    25.11.4 Importing an SQL database
    25.11.5 Connecting Visum to a Personal Geodatabase
    25.12 Attribute interface
    25.12.1 Saving an attribute file
    25.12.2 Reading an attribute file
    25.12.3 Exchanging attribute data via the clipboard
    25.13 Graphics interfaces
    25.13.1 PostScript-PDF export
    25.13.1.1 Exporting the network display as a PostScript file
    25.13.1.2 Converting a PostScript file into a PDF file
    25.13.2 DXF export
    25.13.3 SVG export
    25.13.3.1 Exporting a network display as a *.svg graphics file
    25.13.3.2 Notes on Visum SVG files in Adobe Illustrator
    25.13.3.3 Changing the coding of Visum SVG files
    25.13.4 Exporting screenshots
    26 Working with scripts
    26.1 Running script files
    26.2 Editing the script menu
    26.2.1 Creating a new entry in the script menu
    26.2.2 Creating a new submenu entry in the script menu
    26.2.3 Editing a submenu entry or an entry in the script menu
    26.2.4 Functions in the script menu entry window
    26.3 Embedding add-ins automatically via a project directory
    26.3.1 Adjusting parameters of add-ins
    26.4 Integrating script files or script code into the procedure sequence
    26.4.1 Integrate script file
    26.4.2 Integrate script code
    26.5 Python as additional script language
    26.5.1 Example 1 for applying script language
    26.5.2 Example 2 for applying script language
    27 Appendix
    27.1 File types
    27.2 Matrix formats
    27.2.1 Visum-specific matrix file formats
    PTVGROUP

    2625
    2626
    2627
    2640
    2642
    2642
    2643
    2644
    2645
    2646
    2646
    2646
    2646
    2650
    2650
    2651
    2652
    2654
    2654
    2656
    2656
    2661
    2662
    2663
    2664
    2664
    2664
    2665
    2666
    2666
    2667
    2667
    2668
    2668
    2669
    2669
    2669
    2670
    2670
    2674
    2674
    2678
    2678

    LIX

    Contents

    27.2.2 Data structures of matrices in Visum-specific text formats


    27.2.2.1 Format $V
    27.2.2.2 Format $O
    27.2.2.3 Format $E
    27.2.2.4 Format $S
    27.2.2.5 Format $T
    27.2.3 Format CSV for skim matrices
    Index

    LX

    2679
    2680
    2682
    2683
    2683
    2684
    2685
    2687

    PTVGROUP

    1 Welcome

    Welcome
    Welcome to PTV Visum (Visum), which is the leading software program for traffic and transport
    analyses and forecasts worldwide and allows for GIS-based data management in the field of
    private and public transport.
    Visum is a program for computer-aided transport planning which serves to analyze and plan a
    transportation system. A transportation system includes private and public transport supplies
    (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 you in your work with
    the program. However, it is not considered to be a substitute for a training course.
    Subjects
    Fields of Visum application for PrT and PuT
    Documents
    Technical information
    How to install and start Visum
    Service & Support

    1.1

    Fields of Visum application for PrT and PuT


    Visum determines the impacts of existing or planned transport supply which can encompass
    both the PrT road network and the PuT line network (including timetables). You are supported
    in developing a supply design, in analyzing the supply, and in evaluating network variants.
    Fields of application for planning tasks in Public Transport (PuT)
    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 indicators (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
    Calculation and forecast of territory and operator-specific expenditure and revenue indicators
    Operational indicators for line costing calculation
    Generation of subnetworks with corresponding partial demand matrices
    Fields of application for planning tasks in Private Traffic (PrT)
    Simulation of transport planning measures or construction measures to forecast resulting
    traffic volumes and their impacts
    Prognosis of the impacts of road tolls
    Intersection capacity analyses
    Separate analysis of different PrT transport systems (car, HGV, bicycle)

    PTVGROUP

    1.2 Documents
    Comparison of a demand matrix with current counted data
    Determination of noise and/or pollution emissions
    Generation of subnetworks with corresponding partial demand matrices

    1.2

    Documents
    We supply extensive documentation to enable you to navigate quickly and easily in Visum.
    The program also contains an integrated online help that provides appropriate information
    about the current view.

    1.2.1

    Manuals
    This Visum documentation consists of the Fundamentals volume and the User Manual volume
    complementing one another.
    From the Fundamentals volume, you gain information on the theoretical backgrounds of transport modeling and on procedural methods in the software program. Furthermore, the design of
    the network model is explained as well as the procedures for calculating the impact resulting
    from the transport supply side. To make the procedures easier to understand, their mode of
    operation is demonstrated with a small and easily comprehensible example of transport supply. The network data used for illustration is provided with Visum, thus you can verify the described calculations and results immediately in Visum.
    From the User Manual, you gain any information required for transport planning operations to
    be performed in Visum. For each chapter one to twelve from the Fundamentals volume of the
    manual you find an analogical chapter with identical numbering here which explains how to
    proceed in practice in Visum. Chapter 13 provides an overview of the interfaces to other software programs and in chapter 14 you get to know how to read scripts from file interactively.
    Note: You will find the manuals in PDF format in the Doc/Eng directory of your Visum
    installation folder once the installation is finished. You may also access them via the
    menu point Help during a program session.

    1.2.2

    Online Help
    The online Help is divided into three parts. The first part covers the "Fundamentals" and its
    pages have a light blue background. The second part "Application" corresponds to the user
    manual. The background of the pages is white. The third part consists of a description of the
    COM interface. The online help can be accessed in two ways:
    The context-sensitive help provides you with information on the current window or view of
    Visum. Press the F1 key to access the context-sensitive online help.
    Regardless of the window you are currently working in or the current view mode, you can
    access the online help via Help > HTML help. It opens with the start page.

    1.2.3

    Tutorials und examples


    The Visum tutorials provide a detailed description of how to use Visum for several specific use
    cases. They illustrate different steps and typical procedures by means of examples. The tuto-

    PTVGROUP

    1.2.4 More documents


    rials are supplied with the installation. In Windows Vista and Windows 7, they are located in
    the following directory: ...\User\Public\Public documents\PTV Vision\PTV Visum 13\Tutorials.
    Besides comprehensive tutorials, illustrative brief examples of the many functional areas are
    provided. The clearly structured network and step-by-step instructions help you gain an overview of the general program handling and options available. The examples are supplied with
    the installation and are located in the following directory: ...\User\Public\Public documents\PTV
    Vision\PTV Visum 13\Training.

    1.2.4

    More documents
    Additionally to the manuals, the following documents are provided:
    Installation guide
    (Directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng\Installation_Visum13.pdf)
    This document provides important information on the installation of Visum.
    Visum Quick start
    (Directory ...User\Public\Public documents\PTV Vision\PTV Visum 13\Quickstart Tutorial\PTV Visum Quickstart.pdf)
    Based on an integrated example you are exposed to the essential Visum operations.
    Visum Release Notes
    (Directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng\ReleaseNotes_Visum_
    ENG.pdf)
    This document contains brief notes on changes, fixed bugs and new functionality included
    in the Visum service packs provided for download. Via the PTV homepage, new service
    packs are continuously provided for download.
    Visum overview
    (Directory ...\Program files\PTV Vision\PTV Visum 13\Doc\Eng\Overview_Visum13.pdf)
    Here you can gain an overview of the program changes and new functions compared to the
    previous version.
    Description of the Visum COM interface
    (Directory ...User\Public\Documents\PTV Vision\PTV Visum 13\COM\VisumComDocu.pdf)
    With the help of script files you have access to Visum data and functionality via the Component Object Model (COM) interface.
    Tip: For COM applications, Visum can be used without the graphical user interface
    (see "Starting Visum without graphical user interface" on page 892).
    Reference to the Visum data model
    (Directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng\attribute.xls)
    This file stores the descriptions of all tables, attributes and relations which are used in
    Visum.
    Overview of the origin of indicators
    (Directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng\IndicatorSource.xls)
    Overview of the availability of indicators

    PTVGROUP

    1.2.5 Typography and conventions


    (Directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng\IndicatorAvailability.xls)
    Information on how to use the Visum dongles
    (Directories
    ...\Program files\PTV Vision\PTV Visum 13\Doc\Eng\Overview_Dongle.pdf and Overview_
    CodeMeter.pdf)
    Here you find information on the purpose of the dongles enclosed in the installation
    package and details on dongle installation and usage.
    Manual for RBC controllers
    (Directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng\Manual_RBC.pdf)

    1.2.5

    Typography and conventions


    To ease orientation in the manual for you the following typography is used throughout the
    document.
    Element

    Description

    Program elements Elements of the graphical user interface are bold-formatted:


    Names of windows and tabbed pages
    Entries in menus and selection lists
    Names of options, window sections, buttons, input fields and
    icons
    Sample files

    Sample files illustrate the conventions (terminology, format) of input


    or output files in text format. They are formatted in a different font.

    KEYS

    Keys to be pressed are printed in capital letters, e.g. C TRL+ C.

    Path and file name


    data

    The paths of directories and file names are shown in italics, e.g.
    C:\Program files\PTV_Vision_PTV Visum 13\Doc\.

    Prompts for actions and results of actions


    If just a single step is required to solve a task, the paraphrase is indicated by an arrow.
    1. In case of multiple steps to be done, these are numbered consecutively.
    If the prompt for an action is followed by a visible intermediate result this result is listed in italic format.
    Also the final result of an action appears in italic format.
    Notes & Tips for operating the program
    Note: Notes provide either information on possible consequences caused by an action or
    background information on the program logic.

    Tip: Tips contain alternative methods for operating the program.

    PTVGROUP

    1.3 Technical information

    1.3

    Technical information
    Subjects
    Version sizes
    Add-ons
    Hardware and software requirements
    Dongle
    Interfaces

    1.3.1

    Version sizes
    Visum can be purchased in various version sizes. The versions differ in the number of network
    objects that can be managed.
    For more information visit our homepage at
    http://www.vision-traffic.ptvgroup.com/ or contact info@vision.ptvgroup.com.

    1.3.2

    Add-ons
    The following add-ons are available for Visum.
    Add-on

    Description

    User interface PrT

    Module for PrT assignments and skim data calculations

    User interface PuT

    Module for PuT assignments and skim data calculations

    Line costing calculation

    Module for line blocking without vehicle exchange and for line
    costing calculation

    Passenger onboard
    survey

    Module for the evaluation of PuT passenger surveys

    Calendar / valid
    days

    Definition of valid days for different evaluations

    HBEFA

    Module for HBEFA 3.1-based emission calculation

    Subnetwork generator

    Module for generating a subnetwork with the corresponding partial


    demand matrices as a version file from the original network

    TFlowFuzzy

    Module for demand matrix update and correction based on count


    data (private and public transport)

    TRIBUT toll model

    Specific PuT assignment method to take road toll into account

    Schematic line diagram

    Visualization of line routes and connections in headway-based


    PuT networks

    EVA (passenger
    demand model)

    Module providing an aggregated passenger demand model developed at the Technical University of Dresden

    Detailed line
    blocking

    Module for line blocking with vehicle interchange and for the definition of forced chaining of vehicle journey sections

    PTVGROUP

    1.3.3 Hardware and software requirements


    Add-on

    Description

    Noise emissions
    RLS 90

    Module for the calculation of noise emissions from motorized private transport

    NCHRP 255

    Module for the correction of link and turn volumes in forecast scenarios by means of a correction factor which is calculated according to the NCHRP 255 guideline

    Junction editor and


    control

    Module for modeling node impedances

    Intersection capacity analysis

    Node impedance calculation based on assignment with ICA

    Tour based demand Demand calculation with the tour-based model (VISEM)
    model
    Signal offset optimization

    The procedures Optimization of the SC offset and Analysis of the


    SC offset are available

    Graphical timetable
    editor

    Generation and editing of timetables and graphical display of line


    blocks

    Bing Maps

    Including Microsoft Bing Maps

    Vissig

    Editing of external signal controls in Vissig

    Vistro

    Display of attributes, which are exclusively required by Vistro

    Distributed computing

    Module for distributed computing across multiple computers for


    Scenario management.

    Safety

    Module for the analysis of black spots and accidents

    GIS interface shape

    Export of graphic data to ArcGIS (ESRI)

    MS SQL server inter- Network export to a database on the SQL server


    face

    1.3.3

    EMME import

    Import of EMME/2 demand models

    HAFAS import

    Import of HAFAS data

    RailML import

    Import of railML data

    RailML export

    Export of network and timetable data to railML

    SATURN import

    Import of SATURN data

    Vissim Export

    Data exchange for microscopic simulation

    SVG export

    Data exchange with browsers or graphics programs using an SVG


    data format, e.g. Adobe Illustrator.

    RBC controllers

    Editing control strategies in the Ring Barrier Controller

    Hardware and software requirements


    The following requirements need to be met for working with Visum.

    PTVGROUP

    1.3.4 Dongle
    Operating systems
    Windows XP
    Windows Vista (32 bit/64 bit)
    Windows 7 (32 bit/64 bit)
    Windows 8 (32 bit/64 bit)
    Hardware (minimum requirements)
    Processor providing SSE2 support, i.e. at least Intel Pentium 4, Intel Core, AMD Athlon 64
    or AMD Opteron. (Quad Core or higher quality recommended).
    Minimum processor speed of 1GHz, for optimal performance use 2GHz
    Minimum working memory of 512 MB, 4GB recommended, for large networks and complex models increase accordingly.
    Note: For smooth operation and optimal multitasking enough RAM reserves should
    be available. For extraordinary RAM peaks the virtual memory (swap file) can be
    extended.
    Minimum monitor resolution of 1024 x 768 Pixel
    Minimum graphics memory of 32MB, for optimal performance use 64MB
    Minimum free space of 1.5 GB on hard disk

    1.3.4

    Dongle
    To operate Visum, you need to install a dongle. The following types of dongles are distinguished:
    Stand-alone dongle for local installation on a stand-alone PC
    Network dongle for installation on a server
    In addition to this, these dongle types are distinguished by the following.
    Single dongle for operating only Visum
    Collective dongle for operating several PTVAG software products (Visum, Vissim).
    You need a license information file and have to install a dongle before you can use Visum. Further information can be found in the following document ...\Program files\ PTV Vision\PTV
    Visum 13\Doc\Eng\Overview_Dongle.pdf.

    1.3.5

    Interfaces
    The table below provides an overview of the data import and export interfaces.

    PTVGROUP

    1.3.5 Interfaces
    ANM interface The Vissim export creates an abstract network model (ANM) from the
    (Vissim)
    Visum network which can then be imported in Vissim for further editing
    (see "ANM interface" on page 2511). Modifications of the Visum network
    can also be added later to a previously exported network that has been edited in Vissim. In the Vissim network, only the parts affected by the Visum
    modifications will be adjusted then.
    This function is only available with the Vissim export add on.
    Furthermore, you can read the *.anm files in Visum and edit the data read
    from file (see "Reading an abstract network model" on page 2516).
    Vissig interface

    Vissig is an external program which allows you to administer complex


    signal control data. Signal control data that already exists can be converted into external control data and edited in Vissig to be then re-imported
    into Visum (see "Editing a signal control in Vissig" on page 2528).
    This function is only available with the Vissig add-on.

    RBC controllers

    RBC controllers allow you to manage complex signal control data (see
    "Editing a signal control of the RBC type" on page 1470).
    This function is only available with the RBC controllers add-on.

    HAFAS import The HAFAS interface in Visum enables users to import HAFAS data sets in
    raw data format (see "HAFAS import" on page 2565). This procedure corresponds to the (non-additional) reading of a network, i.e. data are read
    into an initially empty network.
    This function is only available with the HAFAS import add-on.
    railML inter- Via the railML interface, you can read data from file provided in railML
    face
    2.0/2.1 raw data format which is relevant for Visum models (especially timetable data) (http://www.railml.org). The data can be read additionally in an
    existing network. The data content is allocated via mapping attributes (see
    "RailML interface" on page 2573). Furthermore you can export your
    Visum data to railML .
    These functions are only available with the RailML import or RailML
    export add-on module.

    EMME/2
    import

    EMME/2 is a software program for demand modeling (see "EMME/2


    import" on page 2587). Visum has an integrated interface to this system
    which allows for migration of EMME/2 models to Visum.
    This function is only available with the EMME import add-on.

    TModel
    import

    Visum provides an interface for the import of TModel data (see "TModel
    import" on page 2592).

    SATURN
    import

    In Visum, you can read network data that was created using SATURN (see
    "SATURN import" on page 2595).
    This function is only available with the SATURN import add-on.

    Database
    interface

    Via this interface, Visum network data can for example be imported from
    an Access database or exported to an Access database (see "Database

    PTVGROUP

    1.4 How to install and start Visum


    interface" on page 2642).
    Attribute inter- The attribute interface serves for Visum network object attribute data transface
    fer (e.g. node names or link volumes) between two Visum networks or between Visum and another program. Data can be transferred via attribute
    files or via the Windows clipboard (see "Attribute interface" on page 2646).
    Shapefile
    interface

    1.4

    Shape files fit for data exchange with geographical information systems
    (GIS). With the help of the shapefile interface, shape files can be imported
    into Visum and exported from Visum(see "The Shapefiles interface" on
    page 2221).
    Data can always be imported. For data export, you need the GIS interface
    shape add-on.

    How to install and start Visum


    Visum is supplied with demo files, sample files and online documentation. You can find a detailed installation guide under ...\Program\PTV Vision\PTV Visum 13\Doc\Eng\Installation_
    Visum13.pdf.
    After you have installed Visum, by default several icons are listed with the Visum program
    group (Start> Programs> PTV_Vision2013> PTV Visum 13):
    Icon
    PTV Visum

    Description
    Starts Visum with an empty network.

    13
    PTV Visum
    support
    PTV Visum
    Scenario calculation server
    Examples

    PTVGROUP

    Starts your Internet browser and calls the Visum support page.
    Starts the server for distributed calculation of scenarios across multiple
    computers within Scenario management.

    Open the Examples folder: Opens a Windows Explorer window. It contains several folders with Visum version files of various example networks.
    Overview Examples: Opens a *.pdf file with descriptions of the Visum
    examples.
    PTV Visum 13 Example: Opens Visum with an example network
    PTV Visum 13 Example (dynamic): Opens Visum with an example network

    1.4.1 Download and installation of software updates


    Icon

    Description

    Documentation

    Various Visum documentations in the languages you have selected


    during the installation

    Tools

    Register PTV Visum 13 as COM server

    Note: Required after updates only.


    Click this icon to register the COM server.
    Required after Visum update via download from the Internet only.

    1.4.1

    Download and installation of software updates


    Note: For a Visum update, access to the Internet is required.
    1. From the Help menu, choose About.
    The PTV Visum window opens.
    2. Click the Call update server button.
    In your browser, the Visum download area appears.
    3. Follow the instructions.

    1.5

    Service & Support


    PTV provides technical Visum support in the following cases:
    Program errors in the current Visum version.
    Note: As our software is continually being improved, we regret that we cannot always
    provide hotline support for previous Visum versions.
    To trained users with software maintenance agreement we offer support in the case of project-specific questions and modeling problems.
    We hope you understand that our PTV Vision Support team cannot impart you with the knowledge of a training course. Neither can they provide you with specialist engineering knowledge that goes beyond Visum's functionality or solve project- related tasks. If you are
    interested in skills or project solutions, we are happy to offer you consulting or a dedicated training course on that subject.

    1.5.1

    Usage of manual and FAQ list


    Please read the information on the various topics described in the manual or online help
    before posting your support request.
    A huge amount of items is already described in the Visum FAQ list.
    Note: For access to the FAQ list you need access to the Internet.
    In the Help menu, select FAQ via internet.

    10

    PTVGROUP

    1.5.2 Posting a support request


    In your browser, the Visum FAQ list appears.

    1.5.2

    Posting a support request


    You can use a contact form to contact our PTV Vision Support team 24/7.
    Note: For posting a support request you need access to the Internet.
    1. From the Help menu, choose Support.
    In your browser, the Visum Technical Support page appears.
    2. Follow the instructions.

    1.5.3

    Requests to the Traffic customer service


    Our Traffic customer service will respond to general requests concerning Visum.
    Any questions regarding Visum license fees, please forward to info@vision.ptvgroup.com.
    For software maintenance agreements, please contact customerservice@vision.ptvgroup.com.

    PTVGROUP

    11

    PTV VISUM 13
    FUNDAMENTALS

    2 Fundamentals of the program

    Fundamentals of the program


    PTV Visum (Visum) is a software system that allows you to model all private and public transport types in one single integrated model. It is complemented by the microscopic traffic simulation system PTV Vissim (Vissim). Using Visum, most basic data provided by transport
    information and planning systems can be managed consistently and maintained with the network editor. Unlike simple GIS systems, Visum allows complex relationships within single or
    several transport systems to be retained, enabling you to create a suitable transport model.
    A transport model normally consists of a demand model, a network model based on Visum
    and various impact models (illustration 1):
    The demand model contains travel demand data. Information on the demand within a
    planning area is required for the analysis of transportation networks. Demand matrices
    can only partially be created based on survey data. This is why mathematical models are
    used to reproduce real demand ratios. They allow you to calculate the traffic flows between zones of the planning area based on structure and behavior data, the spatial utilization structure and the transport system. Visum includes the Standard 4-step model, the
    EVA model, and the Tour-based model. Thus you can create your own travel demand
    matrices in the program (see "Demand model" on page 129).
    The network model stores the transport supply-side. The network model consists of traffic
    zones, nodes, public transport stops, links representing roads and railway tracks, and the
    public transport lines with their timetables. Transport supply data can be visualized with
    Visum and edited interactively with different methods.
    The impact models use input data provided by the network model and the demand
    model. Visum offers several impact models for analysis and evaluation of transport supply. The user model simulates the travel behavior of public transport passengers and car
    drivers (see "User model PuT" on page 449 and "User model PrT" on page 226). It calculates traffic volumes and service skims (such as journey time or number of transfers). An
    operator model determines operational indicators of a public transport service, like service kilometers, service hours, number of vehicles or operating costs (see "Operator
    model PuT" on page 541). Revenues by ticket type derived from the demand data allow
    line related revenue estimates for a line costing calculation. An environmental impact
    model offers several methods to assess the impacts of motorized private traffic on the environment (see "Environmental impact model and HBEFA" on page 679).
    Visum displays the calculation results in graphical and tabular form and allows you to perform various graphical analyses of the results. You can e.g. display and analyze routes
    and connections per OD pair, flow bundles, isochrones and turning volumes at nodes.
    Indicators such as journey time, number of transfers, service frequency, and many more
    are computed as skim matrices.
    You can compare different versions using the version comparison or network merge functionalities. You can further exchange the changes made to your model via model transfer
    files.

    PTVGROUP

    15

    2.1 Network model the transport supply

    Illustration 1: Visum network model and impact model


    Like all models, a transportation represents an abstraction of the real world. The aim of the
    modeling process is system analysis, forecasting and model-based preparation for decisions
    taken in the real world.
    In the following, especially the network data model and the procedures available in Visum are
    described and explained in a simple way.

    2.1

    Network model the transport supply


    A network model representing the comprehensive 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 lines and timetables and traffic zones. The most important network object types in Visum are described here.
    Zones (also called traffic cells) describe areas with a particular land use and their location
    in the network (for example residential areas, commercial areas, shopping centers,
    schools). They are origin and destination of trips within the transport network, which
    means zones and the transport network are connected through connectors.
    Nodes are objects which define the position of intersections in the link network and of switches in the railway network. They are start and end points of links.
    Links connect 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.
    Turns indicate which turning movements are permitted at a node and store the turning
    time penalty.

    16

    PTVGROUP

    2.2 Transport demand model


    Connectors connect zones to the link network. They represent the access and egress
    distances to be covered between a zones center of gravity and the nodes/stops of the network.
    Stops are subdivided into stop areas and stop points served by lines where passengers
    may board or alight.
    Lines which are listed with a name in a timetable usually go into both directions. A line
    can consist of several line variants, so-called line routes which differ for example, in their
    route courses. Line routes describe the spatial course of line services, for each line route
    one or several time profiles can be defined.
    Territories are network objects, which can be used for example, to model districts or counties. Based on a polygon which defines the territorial border, PrT and PuT indicators for
    regular or single PuT line services can precisely be accounted for each territory.
    Every network object is described by its attributes. Attributes can be subdivided as follows:
    Input attributes such as link length or link number.
    Calculated attributes (output attributes) such as boarding passengers at a stop or the number of assigned vehicles. They are only filled with values in the course of calculation procedures.
    For all network object types, users can define additional so-called user-defined attributes.
    They can contain additional information or temporary values which are like "normal" attributes
    presented in lists and graphically, and are available as filter criteria. Because these are not
    required to understand the basics, no further detail is required at this point.
    The integrated network model distinguishes between transport systems of the private transport
    and the public transport type. PrT transport systems depend on permissible speed and link
    capacity. PuT transport systems are bound to a timetable.

    2.2

    Transport demand model


    Travel demand develops when a sequence of activities (home- work- shopping- home) cannot be carried out at the same location and thus requires a trip.
    The travel demand is stored in a matrix, where all zones contained in a traffic model are in
    columns and rows.
    A PrT demand matrix element has the unit car trips, a PuT demand matrix element has the
    unit passenger trips (do not mistake with the vehicle journey of a PuT line). It contains the
    number of travel demand from a traffic zone i to a traffic zone j.
    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 demand matrix can refer to the total transport system, to partial transport systems (for example pedestrian, bicycle, PuT, car), to person groups (for example employed,
    students, retired persons) or to purposes (for example commuting, shopping, leisure).
    A demand matrix is assigned to exactly one demand segment. A demand segment describes a group of road users with homogeneous travel behavior.
    Travel demand can be divided into surveyed and calculated demand as well as into today's
    and future demand.

    PTVGROUP

    17

    2.2 Transport demand model


    Surveyed 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 today's current
    travel demand in an area of interest is not possible in practice because all travelers would
    have to be interviewed at the same time. For this reason, only a representative, random sample of travelers is interviewed to determine travel demand for the purposes of transportation
    planning. From this survey a matrix of today's travel demand is then deducted. It represents the
    travel demand for the existing supply system.
    Calculated travel demand 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. The
    calculated travel demand can be designated differently depending on the used input data.
    Calculated travel demand is called today's travel demand if the input of the demand calculation is today's land use structure, today's population and economic structure, and
    today's transport supply system.
    Forecasted travel demand is based on data on future land use, 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).
    Within Visum all 4 stages of the classical traffic model (4-step model) can be calculated, besides traffic assignment (choice and volume of the route to get from origin zone to destination
    zone) the other three steps Trip generation, trip distribution and Mode choice (choice of
    means of transport), too.
    In the first step of the classical model, Trip generation, the production and attraction (origin and
    destination traffic) of each zone is determined on the basis of socio-demographic data (for
    example, number of inhabitants and jobs). These production and attraction values define the
    totals of the total demand matrix, which is determined by means of relevant skim data (for
    example, journey times, fares etc.) in the second step, Trip distribution. In the third step the
    total demand matrix is distributed onto the different traffic modes (for example, PrT, PuT) on the
    basis of mode-specific skims. In a fourth step the resulting mode-dependent demand matrices
    can be assigned to the supply (Visum network) by means of the PrT and PuT assignment procedures in order to obtain link volumes and new skims. This skim data can again be used as
    inputs for trip distribution or mode choice of a new demand calculation. The Go to the procedure function allows you to iterate the calculations until a convergence criterion concerning
    link volumes or matrix values is satisfied.
    Visum contains three alternative calculation models for the demand modeling.
    The Standard 4-step model is based on North American practice for aggregated demand
    models (see "Standard 4-step model" on page 136).
    The EVA model is another aggregated demand model for passenger demand. It differs
    from the Standard-4-Step Model by a simultaneous trip distribution and mode choice as
    well as by its particular method of balancing the differences between origin and destination traffic (see "EVA model for passenger demand" on page 142).

    18

    PTVGROUP

    2.2 Transport demand model


    When calculating demand matrices, the Tour-based model (traffic in cities generation
    model) takes into consideration activity chains which homogenous-behavior user groups
    (for example employees with or without a car, pupils, students) perform during the course
    of the day (see "Activity chain based model (tour-based model)" on page 174).
    The matrix editor integrated in Visum supports matrix processing and provides a gravity
    model.
    The calculation models are based on specific Visum demand objects describing the characteristics of trip purposes and road users. Person groups combine road users featuring comparable mobility behavior to groups. The break-down of the population into person groups
    may be based on their job status (employed, students, retired persons) and (optionally) their
    car ownership (with/without car). Activities are activities or locations of a person in the course
    of the day which are not traffic related (work, school, home). Activity pairs describe transitions
    between two activities and may imply trips from one place to the other (home - work, home school). They are then called trip purposes.
    A demand stratum combines one or several person groups with an activity . Almost all calculations of the first three stages of the model are carried through separately for each demand
    stratum and their results are stored separately for a better illustration and verification. The
    resulting demand matrices always have the unit [persons].
    By aggregating the demand strata to demand segments parts of the demand jointly to be assigned are combined prior to the fourth stage, which is the assignment. Hereby, the PrT demand
    matrices are converted into the [Vehicles] unit by dividing the demand stratum matrices by the
    occupancy rate of the respective transport system.
    Temporal distribution of travel demand
    The trips from one traffic zone to another traffic zone in reality take place at different times. The
    temporal distribution of travel demand within the analysis period is described by a start time
    and a time series when modeling in Visum. The time series is taken into consideration at the
    PuT assignments and the dynamic PrT assignment. The demand distribution is ignored in the
    case of static PrT assignments. Temporal distribution of the trips within each time interval of an
    observed time period can therefore not be set for this procedure.
    The start time specifies the time and if the weekly or annual calendar is used - the day on
    which the period referred to by the demand in the matrix starts. The end of the period is calculated from the length of the assigned time series.
    Time series can be defined in two different ways:
    proportional time series of one demand matrix
    as a distribution curve consisting of several demand matrices
    A time series by percentage specifies the proportion of trips with the desired departure time
    within the respective time interval. Demand distribution curves can cover more than 24 hours if
    a weekly or annual calendar is used. An equal distribution of travel demand during the observed time period is assumed as default. Instead of this default, a user-defined demand distribution curve can be specified for the entire matrix. This user-defined demand distribution
    curve can be overwritten again for selected pairs of origin-destination zone types with specific
    demand distribution curves. In this way, it is possible to specify deviating distribution curves for

    PTVGROUP

    19

    2.3 Impact models methods to calculate the impact of traffic


    zones, for example, with known structural features (for example purely residential or commercial areas) that reflect the different traffic loads in one direction (illustration 2 ) at certain
    times of the day for journeys between home and work.

    Illustration 2: Example of the temporal distribution of travel demand by four intervals of 30 minutes
    A time series of demand matrices allocates a separate matrix to each time interval which contains the demand with the desired departure time in the respective time interval. It should be
    used if for example matrices on an hourly basis already exist based on a trip generation
    model. Contrasting time series, here the time dependent course of the demand can be freely
    selected for each matrix item. However, the data entry expenditure and the memory requirements are higher accordingly, because several complete matrices are supplied.

    2.3

    Impact models methods to calculate the impact of traffic


    A transport supply system has diverse impacts which may vary because of measures (for
    example the construction of a new tram line or a bypass).
    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 PuT contractor which may have to account for a political deficit
    Impacts on the environment which is harmed by pollution
    Transport supply-side users
    Users of infrastructure for private transport are mostly car drivers and their passengers, but
    also non-motorized travelers such as cyclists and pedestrians. Users of public transport are
    public transport passengers.
    Transport supply-side operators
    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. PuT operators are the
    transport companies and transportation agencies. In the broader sense, the PuT contractors
    also belong to the operators. To offer public transport service, PuT operators develop line networks and timetables from which the user can then choose connections. To organize drivers
    and vehicles, PuT operators develop vehicle employment plans and rosters.

    20

    PTVGROUP

    2.4 Analysis of results


    Models to calculate the impact of traffic
    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 most important information of these
    assignment procedures are network object volumes (link volumes for example).
    The connection quality of each transport systems or for the selected demand segments is
    described via skims, which can be output in skim 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,
    projection of data to analysis period or analysis horizon, as applicable, is possible. The
    number of required vehicles is computed by a line-blocking calculation procedure, which
    are necessary to be able to offer the PuT supply.

    2.4

    Analysis of results
    Transportation demand and the results of the impact models can be evaluated and output
    under different aspects. The following functionalities are available (see "Tabular and graphical
    display" on page 744 and "Interactive analyses" on page 716).
    Flow bundles, which filter demand segment-specific paths traversing network objects
    selected by the user (nodes, links, zones, stop points, stop areas and stops)
    Flow bundles for the analysis of network volumes according to traffic types (origin, destination, through, external, internal and bypassing internal trips)
    Turn volumes, 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 shortest path search for the PrT, which visualizes the shortest path between
    zones or nodes in the network for a PrT transport system
    Graphical shortest path search for the PuT, which visualizes the shortest path between
    zones, nodes or stop areas. The shortest paths can be based on transport systems or
    determined on the basis of the timetable provided in Visum
    Skim matrices describe different properties for each OD pair from origin zone to a destination zone in the traffic model. Each skim (such as the in-vehicle-time) is derived from
    the properties of all paths found from origin zone to a destination zone
    Lists for all network object types, which allow a tabular display of all attribute values of a
    network object
    Display of bars, charts and tables on the map (for example to visualize the link volumes)
    Statistics for the assignment analysis and the analysis of the assignment quality. This is
    how the coefficient of determination R2 can be determined approximately between the
    volumes calculated in the assignment and the observed values, and the assignment
    model can continue to be calibrated.
    Column charts for the display of time series (for example link volumes in the course of the
    day)

    PTVGROUP

    21

    2.5 Comparing and transferring networks


    Graphic and tabular display of vehicle journeys in the Timetable editor. This is how volumes from the assignment can be displayed as bars for each journey.
    Comparing and transferring networks (Network merge, Version comparison, Model
    transfer files)

    2.5

    Comparing and transferring networks


    Visum offers various possibilities to compare and transfer networks and version files:
    Version comparison (see "Comparing version files" on page 23)
    Network merge (see "Network merge" on page 28)
    Model transfer files (see "Model transfer files" on page 31)
    Version comparison and network merge
    Besides the network merge, two version comparison variants are provided:
    Version comparison with transfer of selected direct attributes
    Version comparison with comparison network loaded in the background
    In contrast to the first variant, which includes the transfer of selected attributes into the opened
    version, the second variant builds relations to the loaded network in the background. This
    means that all attributes of the loaded network are visible in the opened version. Additionally
    to the existing relations to other objects (for a node, for instance, to the in-links, out-links, turns
    etc.) another relation to the loaded network will appear in the attribute selection windows.
    The unique feature of the network merge is the unification of different data.
    The following table gives an overview of the essential differences between network merge and
    version comparison. In most cases you will be working with the new version comparison in
    future.
    Version comparison

    Network merge (previously difference network)

    Normal working is possible. For the relations, simply additional evaluation attributes/values are created, which can be
    deleted or updated, if required.

    Special mode serving mere evaluation purposes, hardly editable, not savable

    Simultaneous comparison of various variants possible

    Comparison with exactly one variant

    New evaluation attributes/values of relations Evaluation attributes replace original attriare listed with original attributes, i.e. graphic butes, i.e. graphic parameters, filters etc.
    parameters, filters etc. can still be used
    have to be adjusted
    Evaluation attributes (beside value of original network): Value of comparison network, difference, relative difference,
    minimum, maximum

    Evaluation attributes: Value of original network, value of comparison network, difference, DiffNet (see "Network merge" on
    page 28)

    According to the type of version comparison, All attributes and network object types are

    22

    PTVGROUP

    2.5.1 Comparing version files


    Version comparison

    Network merge (previously difference network)

    either attributes are selected or relations are compared.


    built to all objects
    Updatable by pushing a button

    Not updatable

    Model transfer files


    A model transfer file allows recording the modifications required to transfer a model, i.e. a
    combination of network data and OD demand data, to another model. You generate the model
    transfer file from two version files, whereby data can be limited to selected network object
    types or attributes. You can exchange modifications between the different version files at any
    time, and equally maintain several scenarios.

    2.5.1

    Comparing version files


    The version comparison provides easy and quick access to attribute values from other network
    variants. Therefore, compared to the Network merge function, this function is more suitable for
    networks basically including the same network objects. The table below lists the differences of
    the two version comparison variants.
    Version comparison with transfer of attributes

    Version comparison with comparison network


    in the background

    Attributes of the comparison network are


    transferred during the version comparison
    and will be saved with the version file.

    Via a relation to the comparison network, all


    attributes are automatically available as
    long as this network is loaded in the background. When the program session is closed, the attributes of the comparison
    network will not be stored with the version.
    Nevertheless they will be displayed when
    the session is reopened.

    The direct attributes selected are adopted.

    All direct and indirect attributes can be analyzed.

    Filters are not regarded.

    Filters in the opened network are also evaluated in the comparison network. There
    they have an effect on indirect attributes with
    the 'Active' reference.

    Updating means, that current attribute


    values of the comparison network version
    are used to overwrite the values of preselected attributes in the opened network
    version. A prerequisite is that the storage
    location of the comparison network was not
    changed.

    Updating means, that the path can optionally be changed and then the comparison
    network is be reloaded in the background.
    Reopening a version with such a comparison complies with an update as described in the column to the left.

    PTVGROUP

    23

    2.5.1 Comparing version files


    Version comparison with transfer of attributes

    Version comparison with comparison network


    in the background

    When you delete the version comparison,


    To prevent automatic comparison network
    the comparison network attributes are remo- loading in the background, the reference to
    ved from the opened network.
    the comparison network has to be removed.
    The values of the selected attributes of the
    opened network and the comparison network are displayed underneath the attribute
    of the particular object in the opened network.

    The attributes of the comparison network


    become visible via an additional relation to
    the loaded network. All attributes and relations of the comparison network are subordinated to this relation.

    Use cases for version comparison


    The examples 1 - 3 can be modeled with either version comparison variant. In these cases,
    the decision which of the variants to use will depend on the form the attributes and relations
    shall exist in the opened network and whether the results of a snapshot will be required in the
    future.
    Example 1: You have increased the capacity of a link corridor or extended the timetable of PuT
    lines. By comparing the assignment attributes of each version comparison you can analyze
    how and where these measures are having impact.
    Example 2: For one network you have calculated assignments in two different version files,
    e.g. for different OD demand data. Then you can compare the typical assignment attributes like
    Volume and Passengers transferring as well as the modified OD demand data directly by
    means of a version comparison.
    Example 3: In two version files you have performed line blockings under different constraints.
    You can compare the different results, for example the number of vehicles per vehicle combination, by means of the version comparison.
    Note: Using the model transfer file you can transfer the network data and the OD demand
    data of the compared models (see "Model transfer files" on page 31).
    The examples 4 and 5 are typical applications which require comparison network loading in
    the background. In other words, these cases can only be modeled with this version comparison variant.
    Example 4: You have two networks with identical infrastructure, only the PuT supply is different. By link bars, varying volumes shall be visualized which depend on the various criteria
    provided for selection (line name, valid day). For that purpose, indirect link attributes are required, which refer to a filtered supply, e.g. Sum:LineRouteItems\Sum:UsingTimeProfileItems\
    SumActive:VehicleJourneyItems\Volume(AP). The filter in the opened network is evaluated in
    either network, i.e. in the particular context of each network. In this way, you can easily display
    the link volume differences.
    Example 5: You would like to visualize all links with different PuT line S5 volumes in the two
    networks. In the opened network, two filter conditions are set: Via the line filter, line S5 is selected. This filter criterion can be evaluated in both networks. This evaluation is independent of

    24

    PTVGROUP

    2.5.1 Comparing version files


    the particular other network, it causes changes to indirect attributes with reference 'Active' in either network. In the link filter it has to be specified that the difference of the link volumes differs
    from zero (network B\this network - comparison network\Sum:LineRouteItems\
    Sum:UsingTimeProfileItems\SumActive:VehicleJourneyItems\Volume (AP) 0), i.e. in the opened network, the relation to the comparison network provides access to the calculated difference. This includes indirect active attributes. The link filter criterion can only be evaluated in
    the opened network.
    Version comparison with transfer of attributes
    Read one or several version files to an already opened version file for comparison. As a result
    of this version comparison Visum automatically creates attributes containing the selected attribute values of the other version files. You can recognize the newly added attributes because
    the attribute name (table 1) is suffixed by the code labeling the comparison.
    In case of numerical attributes Visum automatically adds various comparison attributes: For
    each compared numerical attribute additional attributes are created for the absolute difference, the relative deviation as well as the minimum and maximum.
    By way of example the following table lists the seven additional attributes which are created
    for the numerical attribute Volume PrT (AP) when comparing version A with version B.
    New attribute

    Short name English Long name English

    Value of network B

    VolVehPrT,B(AP)

    Volume PrT [Veh] B (AP)

    Absolute difference A-B

    VolVehPrT,-B(AP)

    Volume PrT [Veh] - B (AP)

    Absolute difference B-A

    VolVehPrT,B-(AP)

    Volume PrT [Veh] B - (AP)

    Relative deviation regarding B (A-B)/B VolVehPrT,-B%(AP) Volume PrT [Veh] - B % (AP)


    Relative deviation regarding A (B-A)/A VolVehPrT,B-%(AP) Volume PrT [Veh] B - % (AP)
    Minimum of both attribute values

    VolVehPrT,B,Min
    (AP)

    Volume PrT [Veh] B Min


    (AP)

    Maximum of both attribute values

    VolVehPrT,B,Max
    Volume PrT [Veh] B Max
    (AP)
    (AP)
    Table 1: Additional attributes for a compared numerical attribute after version comparison
    The values of the additionally read attributes cannot be modified manually. However, all calculated values, i.e. all values except the value of network B, are recalculated automatically as
    soon as the corresponding values of network A are modified.
    With the version file containing the version comparison you can continue to use all Visum functions, including calculations. The comparisons read can be saved together with the version.
    The additionally read attributes can be displayed and evaluated, as required (see "Analysis of
    results" on page 21).

    PTVGROUP

    25

    2.5.1 Comparing version files

    Illustration 3: Network of the original version

    Illustration 4: Network of the version used for version comparison

    26

    PTVGROUP

    2.5.1 Comparing version files

    Illustration 5: Network with version comparison: The volumes of both versions compared as
    well their difference are displayed. "Verscomp" is the name of the version comparison.
    Above all, you can convert the attribute values of the additionally read version easily into userdefined attributes so that they are still available after the version comparison has been terminated.
    The reference to the additionally read data is not updated automatically, but can be updated, if
    required. Thus, for example, you can read the same version file at different times, thus tracing
    the modifications.
    The reference to the additionally read data can be dropped again at any time.
    Special cases
    If the compared versions do not contain the same network objects or attributes, the following
    will happen (opened version: A, additionally read version: B)
    If an object exists in B only, it does not appear in the version comparison.
    If an object exists in A only, the attribute values of B are empty.
    Note: You can use the attribute Exists in network <Code of version comparison> to
    check whether a network object is available in one of the compared versions.
    If an attribute exists in B only, it cannot be selected for the version comparison.
    If an attribute exists in A only, it is not compared.
    If the sub-attributes of an attribute are different in A and B, only those sub-attributes valid
    in A are considered. Sub-attributes which do not exist in B have an empty attribute value.
    Version comparison with comparison network in the background
    For an opened version file, one or several selected version file (s) are loaded in the background as comparison networks. Thus, all attributes (indirect attributes included) of the

    PTVGROUP

    27

    2.5.2 Network merge


    comparison network become visible in the attribute selection windows via the relation to the
    loaded network. This relation is identified by the code of the version comparison. In the opened network, new possibilities are provided especially through the combination of filters and
    indirect attributes with aggregate functions which regard the active objects. You can define filters in the opened network and apply them to both networks in a given context. In this way, indirect attributes can systematically be evaluated in an easy way by just modifying the filter
    criteria.
    Similar to the version comparison with attribute transfer, for numerical values additional comparison attributes are generated such as relative deviation, difference, maximum and minimum. Furthermore, they can also be converted into user-defined attributes subsequently to the
    selection.
    Special cases
    Objects are generally identified via their key. Using the opened network version (network A),
    you can create a relation to the object in the comparison network (network B). If the compared
    versions do not contain the same network objects or attributes, the following rules apply:
    If an object exists in B only, access to this object is only provided via indirect attributes
    (e.g. a node existing in B only belongs to all nodes in B - the latter is a relation within network B, to which a relation from network A refers).
    If an object exists in A only, the attribute values of the relation to B are empty.
    If an attribute has different sub-attribute variants in A and B, then indirect attributes provide
    access to the variants which exist only in B. If there is no sub-attribute variant in B, then
    the attribute value calculated for the relation is empty.

    2.5.2

    Network merge
    The network merge function provides for the comparison of two transport networks and the output of their differences. For network merge any networks can be combined with each other.
    After that, however, only evaluation functions are available, hardly any editing functions.
    Use cases for network merge
    For project management you want to determine the differences between two Visum models.
    Occasionally there are two different version files available for one project (for example for different scenarios) and you want to be able to relate to the differences in the two models.
    Two variants of one model usually differ in that some attributes of a few network objects have
    different values. If, for example, you model different expansion statuses of the same network in
    two version files, there will be deviations in the Number of lanes and Capacity PrT attributes
    of some links, for instance. Furthermore, network objects can only be in one of the two models
    and missing completely in the other. If for example, one of the two models contains a planned
    case with an additional by-pass, the respective links will be missing in the other model.
    The following illustrations show both cases. Compared to Network 1, Network 2 contains an
    additional link. The two networks further have different TSysSet and v0PrT values.

    28

    PTVGROUP

    2.5.2 Network merge

    Illustration 6: Network 1 used for merge network

    Illustration 7: Network 2 used for merge network


    The merge network
    The two models to be compared, network 1 and network 2 have to be available as version
    files. If you open both version files in the network merge mode, Visum shows a so-called
    merge network. The merge network is created by first identifying all objects which occur in
    both models. Two objects are the same if they have identical key attributes. Compulsory references to other network objects (for example, for links the keys 'From Node' and 'To Node')
    must correspond. Exceeding this intersection of the network objects, objects which only occur
    in one of the two models are also transferred to the merge network. This is the main difference
    compared to version comparison. The disadvantage to be put up with is the limited editability.
    Additionally, a calculated DIFFNET attribute is created for each network object. It reflects the
    status of the network object.
    In network 1: Only network 1 contains the object, network 2 does not.
    In network 2: Only network 2 contains the object, network 1 does not.
    DIFF: Network 1 and 2 both contain the object, with at least 1 attribute having different
    values in both networks.
    EQ: Network 1 and 2 both contain the object, all attributes are identical in both networks.
    In no network: The object exists only in the merge network and has no attribute values.
    Example: A turn between a link of network 1 and a link of network 2. Such objects are created in rare cases, so that the merge network is a permissible Visum network. They have
    no real equivalent and no attribute values.
    In the merge network, a read-only attribute is created for each network 1 and/or network 2 attribute (Visum attributes and user-defined attributes). This attribute has the following properties:

    PTVGROUP

    29

    2.5.2 Network merge


    The attribute has identical properties as in network 1 or network 2.
    The attribute has a sub-attribute with values Network1, Network2 and Difference. Network1 and network2 indicate the original attribute values stored with each original network version file if the object is part of the original network version; otherwise, 0 or blank is
    output.
    The Difference sub-attribute value serves to output the difference and has the following
    values.
    For numerical attributes, the difference is calculated from Net1 and Net2 data
    For strings, "==" is output in case of identical strings, whereas "<>" indicates deviating
    strings. Blanks are output for objects which are not part of both original network versions.
    Note: In case of user-defined attributes with identical IDs but different min/max value ranges, the value range of Net1 will be used. For objects with coordinates, the coordination
    values are taken from network 1for the display in the network.
    Note: Network merge ignores the following objects and settings:
    Junction geometry/control objects
    Demand description (neither matrices nor time series)
    All path information
    Analysis periods and horizons
    Filters
    Blocks
    Graphic parameters
    The illustration 8 displays the merge network of network 1 (illustration 6) and network 2 (illustration 7).

    Illustration 8: Merge network of network 1 and network 2


    In the network view of the merge network, you can see that the link at the bottom left of network
    2 has a lower speed of about 20 km/h and varies in TSysSet. The link at the bottom right is,
    however, identical in both networks.
    Characteristic: Analysis time intervals
    In case of identical analysis time intervals of network 1 and network 2 (ID and interval limits),
    these intervals are equally stored with the merge network. In case of deviating interval

    30

    PTVGROUP

    2.5.3 Model transfer files


    properties, no intervals will be created in the merge network. The conformity of the analysis
    periods and horizons is not checked. Attribute values which refer to different analysis periods
    or horizons in network 1 and network 2 will still be stored with the merge network.

    2.5.3

    Model transfer files


    Using model transfer files you can save the difference between two models, i.e. network and
    OD demand data. A model transfer file created that way can be applied again to a suitable version file in order to add the modifications. With this function it becomes easier to manage the
    different scenarios.
    Scenario management is based on model transfer files (see "Managing scenarios" on page
    31).
    When creating the model transfer file, you can specify which data you want to save. However,
    just like when saving a network, make sure that your choice contains the information you
    need.
    Example: You would like to adjust the timetable of one network to that of another one. The PrT
    attributes of the networks are different, which is to remain unchanged. In this case, when creating the model transfer file, you only select the network objects with regard to the timetables.
    Use cases for model transfer files
    In your network you make certain modifications at one point, for example, you insert new links
    or delete others. You save these modifications as model transfer file. Then based on the original network you plan further variants and save them each equally as model transfer file. If
    now modifications have to be made in the original network, you can easily redo the various
    variants using the model transfer files and even combine them with each other, if required, by
    reading several model transfer files consecutively one after the other.
    In another case it may happen that one editor creates and edits zones and saves these modifications to a model transfer file. In the meantime, a second user has edited links, reads the
    model transfer file and adds the new zones to his network.

    2.6

    Managing scenarios
    In most Visum applications you create a model of supply (the network) and demand for an
    area of investigation. Then you develop several variants of the initial situation and various scenarios. The variants are then compared and evaluated based on calculation results. Thereby
    numerous files (including and excluding calculation results) are created for the individual variants. You can use the Compare networks function to organize the file contents, making sure
    that information is only saved to one storage location (see "Comparing and transferring networks" on page 22). This allows you to reduce data maintenance when changing your model.
    In Visum, scenario management takes care of maintaining all your files.
    It provides the following benefits:
    Visum saves all project files in a standard folder structure.
    Visum provides a clear project overview, showing all variants of your model. When you
    enter a meaningful name for a variant and its parts, your entry is not limited by any file system specifications.

    PTVGROUP

    31

    2.6.1 Keywords: project, modification, scenario


    To edit a variant, use it in calculations or for analyzing results, simply open it by entering
    its name in the project view (you will not have to search for it in the Windows file system).
    When you perform calculations or comparisons across all variants, scenario management
    spares you many manual steps and automatically merges the calculation results of
    several variants. You can easily adopt the results in form of a comparison table into your
    project report.

    2.6.1

    Keywords: project, modification, scenario


    Scenario management has three main concepts: project, modification and scenario.

    A project contains all data required to use Visum. It has a unique name and a protocol in
    which users can save notes on the project status. Each project is based on a base model
    which is also called initial situation, analysis case or null case. It is saved as a version file, the
    so-called base version. Just as other supporting files (procedure and graphic parameters,
    etc.), the base version is saved to a uniform folder structure for which you can specify the path.
    All other project information, specifically definitions of modifications and scenarios, are saved
    to the Visum project database, a database file that is saved to the same folder structure.
    A modification is a grouping of changes that belong together content-wise and are made to the
    supply or demand. A modification could refer to the building of a by-pass road and include
    several new links, changes to existing links and to nodes. Another modification might describe
    the introduction of a speed limit on certain roads. It would consist of changing a single attribute
    (v 0 ) for several network links. Modifications may also refer to PuT supply, for example describing line route or headway changes as well as new stops. On the demand side, typical modifications include changes to data on the socio-demographic structure, i.e. changes to the zone
    attributes. Modifications may also change matrix content, e.g. externally specified matrices for
    through trips. The number of modifications is not limited per project. Modifications may also be
    based upon other modifications, e.g. one describes the construction of a by-pass road and
    another its extension by a second lane per direction. The second modification only changes
    the attributes Capacity PrT and Number of lanes for those links that were added through the
    32

    PTVGROUP

    2.6.1 Keywords: project, modification, scenario


    first modification of the base model. When creating a modification, you specify the other modification it is based on.
    A scenario corresponds to a variant you want to investigate. It is often also called planned
    case. Each scenario is based on the base version of the project and includes one or several
    modifications. The distinction between modification and scenario has the advantage that you
    can easily investigate all combinations of several measures. Let us assume your project is
    about the construction of a by-pass road. At the same time it is suggested to introduce a speed
    limit in the city center for traffic calming. Define two modifications for your project: M1 for the
    by-pass road and M2 for the speed limit. Using these two modifications, you can easily define
    four scenarios without any additional modeling effort:
    Scenario code

    Meaning

    Base version

    M1

    M2

    S0

    Null case

    by-pass road only

    speed limit only

    BS

    by-pass road +
    speed limit

    Table 2: Definition of scenarios based on modifications


    Should your customer additionally ask for an investigation of the demand variant for 2020, you
    can change your project with a minimum effort. First define a modification M3 for the second
    demand variant. Then duplicate all previously created scenarios and in the copy additionally
    activate M3. Now you are ready to calculate the model for all eight scenarios.
    Scenario
    code

    Meaning

    Base version

    M1

    M2

    M3

    S0

    Null case

    by-pass road only

    speed limit only

    BS

    by-pass road + speed limit

    S0_2020

    Null case 2020

    B_2020

    by-pass road 2020 only

    S_2020

    speed limit 2020 only

    BS_2020

    by-pass road + speed limit


    2020

    Table 3: Extension of scenarios for a demand variant


    When combining scenarios based on modifications, make sure that the modifications do not
    contain any contradictory information on the value of the same attributes. Visum can account
    for this and check whether it is possible to combine two modifications. In few cases, you might
    want modifications to overlap. Example: M1 describes the extension of a link sequence to two
    PTVGROUP

    33

    2.6.2 Managing projects efficiently


    lanes. M2 includes a third lane for some of the same links. For some links, M1 and M2 contain
    contradictory information on the attribute Number of lanes . If you first apply M1 and then M2,
    you will still achieve the desired result: for some links the attribute Number of lanes will be
    overwritten twice. This way you need not define a copy of M1 without the links mentioned in
    the original M1. In these cases, it is important that you can specify in which sequence the modifications are applied. To avoid conflicts when combining scenarios, you can also specify which
    scenarios must not and which ones may be combined when defining the modification.

    2.6.2

    Managing projects efficiently


    A project is ideally carried out in the following steps:
    Creating or selecting a base version
    Defining modifications
    Defining scenarios based on modifications
    Specifying the procedure sequence
    Calculating scenarios
    Comparing calculation results
    All steps are carried out in the Project view. The Project view is a modeless window and
    remains open while you are working on the project. It provides an overview of all modifications, scenarios and other parts of the project.

    You can find a detailed description on how to use the Project view in the User Manual (see
    User Manual: Chpt. 14.13 , page 921). In the following, you will find useful information on each
    step.
    2.6.2.1

    34

    Creating or selecting a base version


    When working on a new project, you first specify the version file of the base model. In most
    cases, the version file already exists. Especially, if you have already started working on the project without using scenario management. Select the existing version file, when creating the

    PTVGROUP

    2.6.2.2 Defining modifications


    project. Visum stores a copy of this version file with a different name to the project directory
    structure. This copy is now used in scenario management. The original version file is not touched. Alternatively, you can use the model currently loaded as the base version. If you select
    this option just after project start, the model will still be empty and you can create your base
    model from scratch. All options are equally suitable to create a base model, no matter whether
    you create the model within the context of scenario management or of a project. The project
    becomes important once you define modifications and scenarios.
    2.6.2.2

    Defining modifications
    When adding a new modification to your project, you assign a unique name and a project description, if required. You further specify any existing modifications your new modification
    depends on and the ones it cannot be combined with. Visum then loads the base version and
    all its modifications. A floating window informs you that all changes you now make to the
    model will be included in the new modification.

    Now you can use all editing functions to change the model. Data processing, however, is
    disabled in the Project view. After making all your changes, click the Finish button in the floating window. Visum calculates the differences between the current model and the base model.
    These differences are saved as content of the new modification.
    Of course you can add modifications during any stage of your project. You can also change
    modifications later on. You can further have the content of modifications displayed any time.
    If you are working on an extensive project, you might want to assign the creation of modifications to several users. To do so, proceed as follows:
    Provide each user with a copy of the base version.
    Each user works with his/her copy of the base version, without using scenario management. As soon as a user has completed a modification, he/she saves the changes
    made to the base version as a model transfer file.
    Make sure you have access to all the model transfer files created.
    Open your project in Visum. Then carry out the following steps for each model transfer file:
    Add the modification to your program.
    When Visum asks you to change the modification based on the base version, select
    Model transfer file as the only option.
    Then finish editing the modification.
    Now define your scenarios based on the modifications.
    This procedure allows you to use files centrally under scenario management, although they
    were created decentrally by several users.

    PTVGROUP

    35

    2.6.2.3 Defining scenarios based on modifications


    Note: If several users are working on creating model transfer files, they might use the
    same code for a new network object, although the content of their objects differs. Visum
    will recognize these code conflicts when you use the model transfer files in scenario
    management. So, if the same code has been assigned twice, one of the objects is automatically assigned a new, unique code.
    2.6.2.3

    Defining scenarios based on modifications


    After you have defined modifications for your project, you can combine them to create scenarios. Scenarios are also assigned a unique name and a description. For each scenario, you
    can choose several modifications that are applied to the base version. If you do not select a
    modification, the scenario simply corresponds to the base model. If you select several modifications, Visum applies them according to the sequence in your list of modifications. Then
    check to make sure the modifications you selected can be combined. You can also remove or
    add modifications to a scenario later on.
    Under Project view, you can open any scenario in the entry view or the results view. Choose
    the entry view to check the scenario or to perform an interactive analysis, e.g. isochrones calculation or shortest path search. Avoid editing the model in this view, as your changes will
    then be lost the next time you open the scenario. Instead, always make your changes to the
    base version or the modifications. If you save a scenario as a version file, your version file will
    have no connection to scenario management. However, you can use it to pass on the entry
    data of a certain scenario to other users. The results view is described further below.

    2.6.2.4

    Specifying the procedure sequence


    In most cases you will want to apply the same model calculation to several or all scenarios in
    order to compare the results. By default, Visum uses the procedure parameters of the base version to calculate a scenario. To specify the calculation sequence, in the Project view, click the
    Edit base version button. Then, under Procedure sequence, choose the sequence in which
    you want the operations performed.
    Some operations require reading or writing access to files, e.g. to externally saved skim matrices or filter files. Under Project view, you specify whether Visum has access to one file for the
    entire project or to file copies of the respective scenarios. You can specify this for all files of a
    certain type or globally for the entire project.
    However, sometimes you might want to use a different than the default calculation sequence
    for a scenario, e.g. when changing the procedure parameters. If you do not wish to change the
    network or demand in a scenario, but the Value of Time, change the fare or toll coefficient in
    the impedance definition. These parameters are not taken into account for difference calculation when you create modifications. Instead change the procedure parameters of the base
    version and add the edited procedure parameters file to the project. Then close the base version without saving the changes. Assign the scenario the procedure parameters saved to the
    project. This setting has a higher priority than the procedure parameters of the base version.

    2.6.2.5

    36

    Calculating scenarios
    After specifying the calculation sequence for the project, assign it to all or part of the scenarios
    in the Project view. If you select several scenarios, Visum will automatically load the scenarios

    PTVGROUP

    2.6.2.6 Distributing scenario calculations across multiple computers


    in the sequence selected and will perform the respective calculations. This function is very helpful if you have to carry out numerous calculations, e.g. overnight, and no interaction is required. Moreover, you can distribute scenario calculations across multiple computers to exploit
    the computing power available (see Fundamentals: Chpt. 2.6.2.6 , page 37). After all calculations have been performed, Visum saves the model state with all results to a version file in
    the project directory. Saving the results of each scenario to a separate version file might seem
    like a "disruption" of scenario management, but this is the only way to save the many results
    (e.g. assignment results) in a compact form.
    In the Project view, the scenarios for which calculations have been performed are marked "calculated". If after scenario calculation you change the base version, its modifications, the calculation sequence or the number of modifications, Visum will reset the status to "not
    calculated". The results version file then still exists, but the results might no longer be up-todate and you should have the calculation performed again.
    2.6.2.6

    Distributing scenario calculations across multiple computers


    You can distribute scenario calculations across multiple computers to calculate multiple scenarios simultaneously and obtain the results earlier for analysis purposes. You do not require
    any additional system or other software, provided that the add-on module is licensed. Then
    you can use all software belonging to the license group installation of Visum. Workstations
    used during the day for project work, e.g., can be used at night for extensive, automated scenario calculations (see User Manual: Chpt. 14.13.7.2 , page 938).
    Requirements for distributed scenario calculation
    Besides licensing for the add-on module, the computers used for distributed calculation (compute node) must fulfill certain requirements:
    The computers must have compatible Visum versions installed (with the same binary version, e.g. 13.00-xx).
    All computers must be licensed for the add-on modules required for calculation and for an
    adequate network size.
    If you are using Python scripts or add-ins, the respective Python version and add-ins must
    be installed on the computers.
    Depending on the use case, ensure that additional resources, e.g. HBEFA data files or
    user-defined VD functions, are available on the computers. Project-specific data is automatically copied to the respective computers by Visum.
    Do not specify absolute paths for additional files, e.g. matrices or scripts, within the procedure used for scenario calculation. On the compute node, the files might not be available under the path specified. Only specify project folders available within scenario
    management.
    Ensure the same program options are selected on each computer. This is not done automatically.
    The computers must be connected via the network. If required, in the firewall of the computers, open the ports used for communication and assign the corresponding user rights.
    The ports can be freely selected. The compute nodes must be located in the same subnetwork as Visum to be found automatically by the program. If this is not the case, you can

    PTVGROUP

    37

    2.6.2.6 Distributing scenario calculations across multiple computers


    still use them for distributed calculation. However, you need to enter the computer addresses manually.
    The PTV Visum Scenario Calculation Server of the respective installation must run on
    the compute node. Only if this software is run, can the calculation orders be carried out.
    The Scenario calculation server is automatically installed with Visum. It is not necessary to
    start Visum on the compute node.
    The Scenario calculation server is not a Windows service. The software is only run when
    a user logs on to the computer.
    Setting up the compute node
    The Scenario calculation server receives the calculation requests and controls execution of
    the calculations. When you do not want to use the compute node for distributed calculation,
    e.g. during the day when it is used for project work, deactivate it.
    You can start the software via the Start menu of the respective Visum installation or via the
    symbol in the Windows taskbar. Click the symbol to open the dialog for configuration of the
    Scenario calculation server.
    Besides the number of Visum instances and cores you want to use, you can specify a Base
    directory to which the scenario data is saved during the calculation process. In the Service
    address section, specify the name and port under which the compute node shall be available.
    You can use the same computer to simultaneously run multiple instances of the Scenario calculation server for different Visum installations, e.g. different service pack versions. To do so,
    for each installation, you must start the Scenario calculation server and configure a different
    port. Each server started uses the respective Visum version located in its installation folder.
    The Base address of the service box contains the URL based on these settings. If the compute node is not automatically found by the controlling Visum version, the URL can be used for
    manual configuration. You can select the option Start Visum Scenario Calculation Server
    when logging in to start the server automatically, as soon as a user logs on to the system.
    Execution of distributed scenario calculation
    Distributed calculation is carried out by any computer in the Visum Project view. On the Compute node page, you can manage existing compute nodes as well as input and output files
    relevant for calculation. Here the nodes available are automatically identified. You can also
    manually add compute nodes by entering their URL. By default, the Input data transferred to
    the compute node includes all files of the shared Project folder and the respective Scenario folder. If required, additional files may be added manually or excluded from data transfer, e.g. to
    save data transfer time or storage space on the compute node. By default, the result files consist of the respective Scenario folder files that are transferred back to the controlling computer.
    Here you may also add files to or exclude files from data transfer.
    To start distributed calculation, as in local calculation, on the Scenarios page, select the scenarios of your choice and click Calculate. At the beginning of the calculation process, you can
    assign the scenarios to individual compute nodes. You can also choose whether you want to
    have the result files of the compute node automatically transferred back to the respective folders.

    38

    PTVGROUP

    2.6.2.7 Analyzing and comparing calculation results


    After you have started the calculation, Visum transfers the files required to the compute nodes
    (if the current files are not already available there). In the Project view, the scenario overview
    shows the calculation step currently carried out. During the calculation procedure, you can use
    the controlling Visum to perform other tasks or simply close it. The calculation process is continued autonomously on the compute node. After the calculation has been completed, the scenario indicators calculated are listed. They are now available for scenario comparison. If
    specified during calculation start, all other result data is also listed, so that you can analyze the
    scenarios using the tools you are familiar with. If the result data is not automatically listed, you
    can list it for selected scenarios. The scenarios are then available for local calculations and
    analyses.
    2.6.2.7

    Analyzing and comparing calculation results


    You need not open the results version file in the Windows file system. In the Project view, simply open the respective scenario in the results view. Visum then loads and displays the resulting version file and all functions are available for analysis of the results for this scenario.
    If you want to compare two or several scenarios with each other, highlight them in the Project
    view. Then specify one of them as the master scenario. In the master scenario, open the version comparison. Visum shows a comparison of the master scenario with each of the other scenarios. Version comparison works the same way when used outside scenario management
    (see "Comparing version files" on page 23). In the course of the project, you are likely to use
    version comparison many times. You can combine the parameters of version comparison
    (optionally also graphic parameters and filter settings) to a so-called comparison pattern and
    save it to the project. Then you can open version comparison in the Project view, without
    having to change the settings again each time.
    You can also compare all scenarios at a glance by using selected, network code numbers.
    You specify the code number in the Basic settings tab of the Project view. They can then be
    selected as columns in the Scenarios tab. You can use them to create a table with the scenarios as rows and the columns containing the code numbers.

    You can use the Copy & Paste command to copy this table to a project report.
    PTVGROUP

    39

    3 Network model

    Network model
    The supply data of the transport network are described in a network model consisting of
    various network objects.
    Subjects
    Network objects
    Spatial and temporal correlations in Visum
    Attributes
    Subnetwork generator
    The surface data model in Visum

    3.1

    Network objects
    The network model differentiates basic network objects such as nodes and links, which illustrate a network structure (see "Basic network objects of a transport network" on page 42). Additionally, there are network objects which are only used for modeling PuT networks (see "PuT
    network objects of a transport network" on page 45) and general network objects, which do not
    have to have any relevance to traffic and especially no influence on procedure calculations
    (see "General network objects" on page 46).
    Network object

    Description

    Transport system
    (TSys)

    The transport supply consists of several transport systems. Transport


    systems are used for example, to allocate attributes for network
    objects dependent on transport systems. This is how links can be
    opened for a transport system bike, for the transport systems car and
    HGV blocked, however.

    Mode

    In PrT a mode comprises exactly one transport system. In PuT, however, a mode can comprise several transport systems. This is how
    you can define a mode PuT for example, which comprises the PuT
    transport systems tram, bus and train.

    Demand segment
    (DSeg)

    A demand segment makes the connection between transport supply


    and traffic demand. A demand segment is assigned exactly one
    mode and each demand segment exactly one demand matrix. A
    mode can comprise several demand segments. This is how you can
    create a demand segment for the mode PuT, for transporting students and one for the remaining PuT.

    Node

    Turn

    40

    Nodes are point objects, which specify the location of intersections,


    merging links or points in road and rail network. They are start and
    end points of links. Nodes connect zones with the network (connected nodes).
    Turns specify which movements are permitted at a node, that is, whether turning at a node from one link to another link is permitted.
    For PrT transport systems, turning time penalties and capacities can
    be specified which describe the influence of the intersection on the

    PTVGROUP

    3.1 Network objects


    Network object

    Description
    performance of the network.
    Turning prohibitions are taken into consideration as follows:
    For public transport systems in the construction of a line route
    For private transport systems in a route search

    Turn standard

    Link

    Link type

    Zone

    Connector

    Main nodes

    Main turns

    Main zone

    Territory

    PTVGROUP

    Turn standards are templates used to create new turns with default
    values for the attributes Time penalty and Capacity PrT. Which turn
    standard is used for the allocation of turn attributes, depends on the
    node type, the turn type and the flow hierarchy.
    Links connect nodes and thus describe the structure of the road and
    rail network. A link is a directed edge, i.e. both directions of a link are
    independent network objects and thus, can have different attributes.
    Link types are used as a template when inserting new links. When
    inserting a link, a link type has to be specified. The link then takes
    over the attributes permitted transport systems (TSysSet), Capacity
    PrT, velocities (v0-PrT, vMin-PrT, vMax-PrT and vDef-PuT), Number of lanes and the link rank as default values.
    Zones (traffic cells) describe the positions of utilities in the network
    (for example, residential areas, commercial areas, shopping centers, schools). They are origins and destinations of movements
    within the transport network, which means of traffic. Zones and the
    transport network are connected through connectors.
    Connectors connect zones to the link network. They represent the
    distance to be covered between a zones center of gravity and the
    connector nodes. For public transport demand, the zone has to be
    connected via a stop area with stop(s) allocated to a node.
    Several nodes can be aggregated to one main node. Each node is
    only allowed to be part of a main node. Using main nodes is useful,
    if the Visum network is strongly disaggregated and lanes are available as individual links, for example, and intersections therefore consist of several nodes (this situation can occur when working with
    navigation networks in Visum).
    Main turns are created when using main nodes. Each movement via
    the main node is represented by a main turn. Main turns possess the
    same attributes as turns. In the assignment, the main turn replaces
    the node turn, which has the effect that only one turn penalty flows
    into the assignment for each main turn.
    Main zones group multiple zones and allow aggregated evaluations. A main zone can represent a county for example, which
    has multiple communities as traffic cells.
    Territories are network objects, which can be used for example, to
    illustrate districts or counties. Based on a polygon which defines the

    41

    3.1 Network objects


    Network object

    Description
    territorial border, PrT and PuT indicators can be precisely accounted
    for each zone (for example the driven service kilometers within a
    zone).

    OD pair

    OD pairs exist between all zones of the network. The values in skim
    matrices and demand matrices (see "Matrices" on page 130) refer to
    one OD pair each. Compared to the other network objects, you cannot edit OD pairs interactively in the network editor, but you can filter
    OD pairs and display them graphically. For each OD pair you can
    select the skim matrix values, the demand matrix values and the
    direct distance as attributes.

    Path

    For assignment calculation, paths are found between the origin and
    destination zone, and their volume is calculated. Paths are therefore
    the central result of the assignment procedure. In PrT, the user can
    manually edit paths. This is how the assignment results could be
    manually imported to Visum or the Visum assignment results could
    be adjusted manually. Both the path volumes and the course of the
    path can be edited.

    Valid day

    Valid day is a freely definable set of days of the calendar used. If a


    weekly calendar is used, a valid day may comprise the days from
    Monday to Sunday (e.g. "Monday to Friday"). If an annual calendar
    is used, any individual days can be selected within the validity
    period. If no calendar is used, there is only the valid day "daily". It is
    then not possible to create new valid days.
    In PuT: a valid day can be assigned to each vehicle journey section.
    In PrT: in the Dynamic stochastic assignment and DUE, traffic supply
    can be time-varying. Time-varying attributes are used (see "Timevarying attributes" on page 114). When using a calendar, valid days
    can be specified for these time-varying attributes, on which they
    should have an effect.

    Table 4: Basic network objects of a transport network


    Network object

    42

    Description

    Stop

    A stop combines stop areas and therefore also stop points. To


    ensure that a stop can be localized and displayed in graphical form,
    it has a coordinate, but it is not assigned directly to a network node
    or link.

    Stop area

    A stop area divides a stop into areas. It can, for example, represent
    a train station platform, intersections with multiple stop points or a
    station concourse. A stop area has the following properties:
    It is assigned exactly one stop.
    It can comprise multiple stop points.

    PTVGROUP

    3.1 Network objects


    Network object

    Description
    It can be assigned a network node. This allows a PuT connection of a zone to the road network.
    The stop areas are connected with each other with a transfer
    walk matrix (walk times between the stop areas). It contains the
    transfer walk time of each PuTWalk for example.

    Stop point

    Line

    A stop point is the location, where PuT lines stop for passenger boarding. A stop point can either lie on a node or on a link (link stop
    point).
    A stop point at a node can be served by all lines which pass the
    node.
    A stop point on a link can only be served by lines which pass
    this link. A detailed direction modeling based on masts is optionally possible with link stop points. Alternatively, undirected
    stop points can also be inserted on links.
    Lines combine all line routes and timetables of a line. A line has at
    least one line route and this at least one time profile. For line variant
    modeling, several line routes can be specified for the line, and
    several time profiles can be specified for each line route.

    Line route

    Line routes describe the spatial course of the line route for one direction as a sequence of route points. Route points are selected points
    in the line routes, namely all stops and possibly traversed nodes.
    The first and last route point of a line route must be stop points that
    are open for the transport system of the line.

    Time profile

    Time profiles describe the length of travel times between stop points
    of a line route and if boarding or alighting is allowed at the stop
    points of the line route. Since it is possible to create several time profiles per line route, you can model, for example, that the travel times
    of a tram between stop points are longer during evening rush hours
    than during the rest of the day. Time profiles are allocated at vehicle
    journey level so that each vehicle journey can be allocated a different time profile.

    Vehicle journey

    Vehicle journeys (also called journeys only) are the basic objects to
    describe the timetable. Each vehicle journey has exactly one time
    profile. In most cases all vehicle journeys of a line route use the
    same time profile, if this does not vary depending on the time of day.

    Vehicle journey sec- Vehicle journey sections (also called journey sections) are used to
    tion
    sub-divide a vehicle journey. You can define different valid days
    and different vehicle combinations for the individual vehicle journey
    sections of a vehicle journey. This is how you can achieve, that a
    train travels on days with high saturation with a vehicle combination,
    which has more coaches attached. Furthermore, you can specify different start and end points for each vehicle journey section, and the-

    PTVGROUP

    43

    3.1 Network objects


    Network object

    Description
    refore achieve for example, that the additional coaches are only attached to one part of the line route course.

    Main line

    System route

    PuT operators

    Main lines are used to aggregate several lines and evaluations


    (such as for PuT operating indicators) on this aggregation level.
    Aggregation can also be carried out via lines with different transport
    systems.
    A system route describes the in-vehicle time and the spatial course
    between two stop points. Compared to the line route, it is independent of the affiliation to a line or even a concrete vehicle journey.
    System routes with their path and in-vehicle-time information are
    used as a template for the efficient digitalization of line routes and
    for setting in-vehicle-times in the time profile. System routes are
    optional network objects, therefore not mandatory when creating a
    PuT model.
    You can assign an operator to each vehicle journey section. When
    working with the operator model, you can evaluate PuT operating
    indicators per operator (see "Operator model PuT" on page 541).
    Furthermore, you can assign each operator cost values for depreciations and running costs, and then evaluate operator costs referring to different network objects.

    Vehicle combination You can optionally assign each vehicle journey section a vehicle
    combination. To a vehicle combination you can allocate time and
    distance dependent cost rates for vehicle journeys and empty trips,
    and cost rates for the layover in the depot and the stand time. These
    cost rates are applied within the operator model (see "Operator
    model PuT" on page 541).

    44

    Vehicle unit

    A vehicle combination consists of one or more vehicle units. This is


    how you can compose a vehicle combination Intercity out of
    several vehicle units Coach, for example. For each you can specify
    the number of seats and total seats. Furthermore, you can assign
    time and distance dependent cost rates for vehicle journeys and
    empty trips, and cost rates for the layover in the depot and stand
    time. You can also define a fixed cost rate per vehicle. This allows
    much differentiated modeling of your vehicle pool.

    Block version

    In Visum multiple line blocking results can be kept simultaneously.


    These are saved in so-called block versions. This is how alternative
    plans with different parameter settings can be compared with each
    other. In the model, for example one block version can be kept
    where interlining is allowed, and another block version where it is
    not allowed.

    Block item type

    Each block is composed of individual sections, which are called


    block items. Each block item is of a special type (block item type). By

    PTVGROUP

    3.1 Network objects


    Network object

    Description
    default, Visum provides the block item types vehicle journey, empty
    trip, layover time, and stand. You can also create user-defined block
    item types and include these manually in your blocks (for example
    for maintenance or wash).

    Ticket type

    If revenues are modeled with a fare model, the ticket type creates
    the basis for the fare calculation of a connection. Basic fares and
    transport system dependent supplements can be defined.

    Fare zone

    For revenue calculation with fare model and zone-based fare, fare
    zones are used to calculate the fare of a connection. For the zonebased fare this complies with the number of traversed fare zones. To
    determine the number of traversed fare zones, stops are assigned to
    the fare zones.

    PuT coordination
    group

    This network object is only relevant for headway-based assignment.


    If there are two lines for example, which complement each other on
    a common section of the route course to a headway interval half the
    length, we speak of coordination. The coordination group combines
    two or more time profiles over a common section of the line courses.
    If two or more time profiles were coordinated via a route section,
    they behave like a time profile with a corresponding increased frequency on this section. The random variable, which illustrates the
    waiting time within headway-based assignment, thus is reduced to
    the coordinated section.

    Table 5: PuT network objects of a transport network


    Network object

    Description

    Points of Interest are user-defined network objects with a spatial refePoint of Interest
    (POI) and POI cate- rence, e.g. parking facilities, pre-emption points for AVLS (automatic
    vehicle location systems) or SCJ controllers in public transport. POIs
    gory
    are used to display special land uses such as restaurants or hotels,
    for data management as well as for reachability analyses.
    Count location

    Detector

    Toll system

    GIS object

    PTVGROUP

    A count location is an independent network object allocated to a link


    by direction. Count locations serve for data management and display of counted link data.
    Detectors are optional network objects of the count locations addon. They are used for lane-based management of counted data and
    for signal control modeling.
    Toll systems are optional network objects which can be used to integrate toll zones into the network model. For the TRIBUT procedure,
    they are the basis for the calculation of road tolls.
    GIS objects (GIS = geographic information system) extend the network model by special layers which are directly incorporated from

    45

    3.1.1 Transport systems, modes and demand segments


    Network object

    Description
    GIS ArcGIS and can be linked with the Visum network data via blending features. The objects are only available during the connection
    with a Personal Geodatabase (PGD).

    Screenline

    Screenlines are a useful construction to calibrate an assignment


    model by means of counted link data. The course of screenlines
    often follows natural realities, for example rivers or railway tracks.

    Table 6: General network objects


    Network processing modifies the properties of the transport network which produces different
    indicator values and assignment results.
    In the case of modifications to the network structure, a current assignment result is initialized. Inserting, deleting or renumbering a network object as well as merging nodes, splitting zones or links and aggregating zones represent modifications to the network
    structure. PuT assignment results are kept if new zones and connectors are inserted.
    As long as only attribute data of network objects are modified, for example the length of a
    link, the current assignment result will not be initialized, although another assignment
    might produce a different result.

    3.1.1

    Transport systems, modes and demand segments


    The transport supply consists of several transport systems. Modes and demand segments are
    used to link the transport supply with the transportation demand.

    Illustration 9: Connection between transport systems, modes, demand segments and demand
    matrices
    3.1.1.1

    46

    Transport systems
    The transport supply consists of several transport systems. Links, turns and connections can
    be attributed subject to the transport system ("transport system-based"). It can be specifically
    determined, if a transport system is allowed to traverse one of these network objects or not. For
    example, links can only be opened for the transport system Car, but not for the transport sys-

    PTVGROUP

    3.1.1.1 Transport systems


    tem HGV. Furthermore, the impedance functions (see "Impedance and VD functions" on page
    231) are defined for the assignment transport system dependent.
    A transport system has the following properties:
    Transport system type (available are PrT, PuT, PuTWalk or PuTAux)
    Means of transport (= vehicle type), for example car, tram, taxi, wheelchair
    Note: The number of modeled transport systems, modes or demand segments is not limited.
    The four types of transport systems are different in the following ways.
    PrT
    Travel times of a private transport system depend on the following attributes:
    Maximum speed of the means of transport for example 100 km/h for HGV
    Permitted speed of the traversed link for example 80 km/h
    Capacity of the traversed link
    PuT
    Run times of vehicles of a public transport system and the dwell times at stops are determined by the timetable.
    PuTWalk
    This mode serves to model entrance and exit paths for public transport and walking transfer links between stop points of a stop or several stops. In order to calculate a public transport assignment, at least one transport system of type PuTWalk must exist. Several
    transport systems of type PuTWalk can be defined.
    PuTAux
    This type describes subordinated PuT transport systems without a specified timetable. It is
    suitable for the following use cases.
    Modeling lower-ranking public transport (supply systems):
    In large networks, for example in train networks, one often does not want to enter the
    reachability of long-distance stations by means of a connector, but in instead one
    wants to roughly display the available public transport supply. For a simple representation such as this, it is meaningful to define one or several additional public transport systems. In this case, the successive public transport supply is only described as a
    link network with run times. Line routes and timetables are not used.
    Modeling different types of public transport connectors:
    A zone is connected to the PuT supply via one or several PuT systems. In many cases,
    passengers not only select nearby start stops for their PuT journey that can be reached
    on foot, but they also select distant stops that can be reached by bicycle or car
    (Park&Ride, Kiss&Ride, Bike&Ride). In order to be better able to model these alternatives, for connectors it is possible to disable individual transport systems of type
    PuTWalk or to define different connector times. Two modes can then be defined for the
    PuT assignment: one mode that is only used if the stop is reached on foot and one
    mode that can be used if the stop is reached by car or bicycle.

    PTVGROUP

    47

    3.1.1.2 Modes
    Note: Transport systems of type PuTAux are only taken into consideration for the
    transport system-based and timetable-based assignment. In headway-based assignment, however, they are not considered.
    The table 7 provides an overview of properties of the transport system types:
    TSys type

    Description

    PrT

    Transport system for private transport


    Capacity-dependent travel times resulting from link
    speed and turn times

    Car,
    HGV

    PuT

    PuT with timetable


    Run times from timetable
    Transport system is not valid for transfer walks or on
    a connector

    Bus,
    Tram,
    Train

    PuTAux

    Public transport system without timetable or


    PrT access system to PuT
    Run times result from links
    Transport system is not valid for transfer paths within
    a stop - just between stops

    Bus,
    Taxi,
    P&R access

    PuTWalk

    Transport system for


    access/egress paths from/to stops or
    transfer paths within a stop or between stops
    Travel times from links or from a transfer walk time
    matrix of the stop
    Table 7: PrT transport systems properties
    3.1.1.2

    Example

    Footpath,
    Escalator,
    Lift

    Modes
    A mode can include either one private transport system or several public transport systems.
    Examples for modes are for example:
    HGV mode
    Transport system HGV
    PuT mode
    all PuT transport systems, for example bus, tram, subway
    Park & Ride mode
    PuT transport systems and transport system PuTAux car
    You can define multiple PuT modes. This way it is possible to model that for example longdistance passengers (Mode PuT-Long) may use all public transport systems (e.g. Intercity,
    Regional train, Bus) whereas, for example, commuters (Mode PuT-Local) may use only particular transport systems (Regional train, Bus).

    3.1.1.3

    48

    Demand segments
    A demand segment belongs to exactly one mode. It is the link between transport supply and
    transport demand. As several demand segments can be defined for each mode, different types

    PTVGROUP

    3.1.1.3 Demand segments


    of demand can be combined in the transport model.
    Demand segments can be used for differentiation among
    Population groups
    Employed PrT (car drivers), Employed PuT, Students PuT, etc.
    Ticket types
    Single trip ticket, monthly pass, etc.
    Trip purposes
    to work, shopping, home
    Vehicle types
    Car - diesel, Car - petrol, etc.
    To each demand segment a demand matrix is assigned. Assignment results therefore always
    exist on the level of a demand segment (for example the volume for the demand segment PuT
    pupil transport).
    In principle, it is assumed that demand matrices are available in the following units.
    PrT
    in car units (CarUnits)
    PuT
    in passenger units
    For the calculation of person trips (PrT) from car units, the occupancy rate can be specified for
    each demand segment (see User Manual: Chpt. 15.11.3.2 , page 1062).
    Assignment of demand segments
    In all private transport assignment procedures (see "User model PrT" on page 226), demand
    segments of different PrT modes can be assigned simultaneously.
    Tribut procedure, Stochastic or Dynamic stochastic assignment
    Per iteration step, a route search is carried out for each transport system, because each
    transport system has a transport system-specific impedance function.
    Incremental and Equilibrium assignment, Equilibrium_Lohse assignment
    The search for each demand segment is carried out individually, using the same TSysspecific impedance function. This means, that volumes can be issued by DSeg. Adding
    the demand matrices prior to the assignment saves calculating time.
    DUE
    Due to the parameterization by demand segment, the route search is always carried out
    by TSys.
    For public transport, only the demand segments of one public transport mode can be selected
    for assignment calculation (see "User model PuT" on page 449). For modeling more than one
    PuT mode (for example 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 for example, deviating tolerance levels towards transfers or of specific fares due to the
    tariff (students, employees, pensioners).

    PTVGROUP

    49

    3.1.2 Nodes and turns

    3.1.2

    Nodes and turns


    Nodes specify the location of intersections, merging links or points in road and rail network.
    Turns specify which movements are permitted at a node.

    3.1.2.1

    Nodes
    Nodes determine the locations of street junctions and points in the railway network. They are
    starting and terminating elements of links, where there are turning relations from one link to
    another in PrT or PuT transport systems (see "Turns" on page 50). Optionally, a major flow can
    be defined 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 (see "Links" on page 52). Any number of nodes can be incorporated in a
    main node (see "Main nodes" on page 60). Impedances can be modeled for nodes, which
    then have an effect on the route search and thus on the assignment results (see "Impedances
    at node" on page 241). This is how influential factors on time can be integrated in the assignments, which a vehicle needs to cross an intersection.

    3.1.2.2

    Turns
    Turns indicate whether turning is permitted at a node and what time penalty has to be considered 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. Turns 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.
    Turns representing a change of direction are important for PuT line blocking.
    When inserting a link, Visum creates all theoretically possible turns at both nodes of the link
    and uses the standard values from the user-defined turn standards.
    For example, at a four-way intersection, there is a total of 16 turns (4 right turns, 4 straight
    ahead, 4 left turns and 4 U-turns).
    Each turn is described by the following elements:
    A list of permitted/not permitted transport systems
    PrT capacity
    PrT time penalty
    Actual change of direction
    For each turn, the transport systems have to be specified which may use this turn. A turn differentiates permitted and blocked transport systems.
    Permitted PuT trans- The turn can be used when constructing the line route.
    port systems
    Permitted PrT trans- The turn can be used for the assignment taking the PrT capacity and
    port systems
    the PrT time penalty into account.
    Blocked transport
    systems

    50

    Prohibited turns

    PTVGROUP

    3.1.2.3 Turn types


    Per default, the following rule applies when you insert a new turn:
    All turns are open to all transport systems that are allowed on both the "from link" and the
    "to link". This also applies to u-turns.
    An exception are the PuTWalk transport systems: These are not automatically incorporated into the transport system set of turns.
    3.1.2.3

    Turn types
    Visum distinguishes 10 turn types (0 to 9), of which types 0 to 4 are predefined.
    0: Not specified
    1: Right turn
    2: Straight ahead
    3: Left turn
    4: U-turn
    5: Free for user-defined cases
    The turn type can be calculated automatically from the geometry of the turn.

    3.1.2.4

    Turn standards
    Turn standards are templates which assign a newly created turn with values for their attributes
    Turn time penalty (t0-PrT) and Capacity . Which turn standard is used to assign attributes of
    each turn, conforms to the three following criteria.
    the type of node, via which the turn runs
    the type of turn (right, straight ahead, left)
    the flow hierarchy which depends on the rank of a link entering a node
    For each node, Visum evaluates the rank of the links involved and thus determines a major
    flow (see "Link types" on page 53). This automatically determined major flow can be edited
    manually. The flow hierarchy describes whether a turn follows this major flow, from this one
    into a minor flow, from one minor flow into the major flow or leads from minor flow to minor
    flow. These four steps of the flow hierarchy are designated with the symbols from table 8.
    Symbol

    Right of way

    ++

    from major flow into major flow

    +-

    from major flow into minor flow

    -+

    from minor flow into major flow

    -from minor flow into minor flow


    Table 8: Flow hierarchy symbols
    In combination with node types, turn types and flow hierarchy, you can assign the turns very differentiated turn times as standard. These turn times can then be considered within the assignment (see "Impedances at node" on page 241). The illustration 10 shows an example of
    turn standards.

    PTVGROUP

    51

    3.1.2.5 PrT capacity and PrT turn time


    * Attention: Time always in seconds
    * Table: Turn standards
    $TURNSTANDARD:ID;NODETYPE;TURNTYPE;FLOWHIERARCHY;T0PRT;CAPPRT
    1;10;1;--;10s;32000
    2;10;1;-+;10s;32000 // Right turn from minor flow into major flow
    3;10;1;+-;10s;32000 // Right turn from major flow into minor flow
    4;10;1;++;0s;32000
    // Road with right of way which bends to the right
    5;10;2;--;15s;32000 // Crossing from minor flow into minor flow
    6;10;2;-+;10s;32000
    7;10;2;+-;10s;32000
    8;10;2;++;0s;32000
    // Crossing straight from major into major flow
    9;10;3;--;20s;32000
    10;10;3;-+;20s;32000 // Left turn from minor flow into major flow
    11;10;3;+-;15s;32000 // Left turn from major flow into minor flow
    12;10;3;++;0s;32000

    Illustration 10: Example of a TURNSTANDARD table in the network file, which is used to specify standard values for turn penalties and turn capacity
    3.1.2.5

    PrT capacity and PrT turn time


    Turns show basically the same correlation between capacity and travel time as links. The only
    difference results from the fact that a turn does not have a length and that the travel time t0 therefore comes from the turn time penalty.
    The turn time tCur in the loaded network then results from the selected VD function and the relationship between the current traffic volume q and the capacity qmax:
    Input: Free flow turn time t0 (turn time penalty) [s]
    Input: Volume q of the turn [car units/analysis time interval]
    Input: Capacity qmax of the turn [car units/analysis time interval]
    Input: VD function, for example BPR function from U.S. Bureau of Public Roads
    Result: current turn time in the loaded network [1], for example

    To model turn times which do not depend on capacity, a constant VD function must be chosen.

    [1]

    How the impedance at a turn depends on these parameters in particular, depends on the set
    method for impedances at nodes (see "Impedances at node" on page 241).

    3.1.3

    Links
    Links describe roads and railways of the transport network. They connect nodes, which means
    intersections in PrT or stop points in PuT. A link is represented as a directed element and is
    described by the From Node number and To Node number. Both directions of a link are two
    independent objects in the network model, who are assigned the same link number and
    whose From Node number and To Node number has been swapped. This means, that you
    can attribute both directions of a link differently. For every link, you must specify the permitted

    52

    PTVGROUP

    3.1.3.1 Link types


    transport systems of PrT and PuT (which are allowed to use the link). This means, that you can
    close one of the directions to any traffic and model a one-way road in this way.
    3.1.3.1

    Link types
    Visum describes the traffic-related properties of links with link attributes. It also offers the possibility of dividing links with the same properties into 100 link types, which themselves have
    attributes. Each link belongs to a link type via its attribute Type number . The 00 to 99 link
    types serve as network classifiers and make it possible to assign type-specific standard values
    for the following link attributes.
    List of permitted transport systems on a link
    Capacity PrT
    Permitted free flow PrT speed (v0 PrT)
    Minimum speed
    Number of lanes
    Rank of identification of the link rating
    Permitted maximum speed vMax-TSys of every PrT transport system
    Transport system-specific speed in PrT for toll
    Transport system-specific speed v-PuTSys for the calculation of transport system-specific PuT run times t-PuT from the link lengths
    Three cost rates per transport system in PuT for the calculation of link costs within the
    operator model (see "Calculation of the operating costs" on page 649)
    In principle, the values of the attribute of a link of the assigned link type, is independent. This
    means, that you can attribute each link independent of the link type. However, it is recommended to apply exactly those values of the link type in the link. This is how you will achieve
    as consistent as possible modeling of links and modifications to attributes can be made more
    easily, because you can change these in the link type and then apply these to the links (see
    User Manual: Chpt. 15.14.2 , page 1099).
    For the assignment, each link type can be assigned a capacity restraint function, which thus
    applies for all links of this link type (see "Impedance and VD functions" on page 231). This
    allows you to apply a different mathematical correlation for the calculation of impedance on
    non built up rural roads and built up urban roads.
    Major flows
    From the rank of the link types of the link which flow into a node, Visum determines a flow hierarchy with a major flow. This always refers to two different link orientations (see "Network
    objects of the junction model" on page 89). The major flow is taken from one of the three criteria (see "Turn standards" on page 51) to determine the time penalties for the exiting turning
    processes from the major flow or from another link. If possible, it should correspond to the right
    of way or movement, advantaged through the SC. With this the rank of the link types indirectly
    influences the result of the PrT assignment. The illustration 11 shows an example of determining the flow hierarchy and particularly the major flows.

    PTVGROUP

    53

    3.1.3.2 Permitted transport systems

    Illustration 11: Rank of the link type and its resulting major flows (yellow), flow hierarchy (red)
    Note: In the PuT model, the rank has no influence on the assignment result.
    3.1.3.2

    Permitted transport systems


    The permitted transport systems specify the configuration of a link. The following types can, for
    example, occur:
    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 walk link between PuT-stops
    The illustration 12 shows three examples for permitted transport systems on different types of
    links.

    Road with tram lines

    54

    One-way road without tram


    lines

    Transfer walk link

    PTVGROUP

    3.1.3.3 PrT capacity, PrT speed and PrT travel time


    Illustration 12: Examples for defining transport systems of a link
    The number of the lanes of a link is entered as an attribute, but also has to be considered for
    the capacity (this means that the entered capacity does not refer to one lane, but to all lanes).
    A link is always meant for both directions. In order to define a one-way road, close the opposite direction to all transport systems.
    Links which are open to PrT transport systems are taken into account during private
    transport assignment.
    Links which are open to PuT transport systems are taken into account during the construction of line routes for public transport lines. PuT assignments (headway-based
    or timetable-based procedures) are not based on link data, but on PuT line timetables.
    To model passenger transfers between certain public transport stops, a special public transport system PuTWalk may be introduced. These links are taken into consideration for PuT assignments.
    3.1.3.3

    PrT capacity, PrT speed and PrT travel time


    If 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: Length L [m]
    Input: Free flow speed, v0 [km/h]
    Result: 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 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.
    Therefore, for speed v0-TSys and travel time t0-TSys applies:
    v0-TSys = MIN (v0, vMax-TSys)
    t0-TSys = L 3.6 / v0-TSys
    In a loaded network, travel time of a link is determined through a so-called volume-delay function (also known as capacity restraint function) which describes the correlation between the
    current traffic volume q and the capacity q max. The result of the VD function is the travel time in
    the loaded network tcur.
    Input: Free flow travel time t0 [s]
    Input: Traffic volume q [car units/time interval]
    Input: Capacity qmax [car units/time interval]
    Input: VD function, for example BPR function from U.S. Bureau of Public Roads
    Result: Current in-vehicle time in the loaded network, for example

    (dependent on VD function type)


    Result: Current travel time of a T-Sys = MAX (tcur, t0-TSys)
    The illustration 13 illustrates how speeds vcur of two PrT transport systems develop depending
    on the volume.

    PTVGROUP

    55

    3.1.3.4 PuT run time


    Link type Motorway
    vmax (car) = 150 km/h
    vmax (HGV) = 100 km/h

    Link
    v0 = 130 km/h

    Free traffic flow


    vcur (car) = 130 km/h
    vcur (HGV) = 100 km/h
    partially linked traffic flow
    vcur (car) = 110 km/h
    vcur (HGV) = 100 km/h
    linked traffic flow
    vcur (car) = 80 km/h
    vcur (HGV) = 80 km/h
    Illustration 13: Example for the different speeds of two PrT transport systems depending on the
    volume
    3.1.3.4

    3.1.4

    PuT run time


    With every link, a PuT run time is stored for each PuT transport system. When inserting a link,
    this run time is automatically calculated from the link length and the link type specific speed of
    the PuT transport system. From the PuT run times of the traversed links the run time between
    the stop points is then calculated when constructing a line route. This run time is in the respective time profile (see "Specifications of lengths and times" on page 74).

    Zones
    Zones (also traffic cells) are the origins and destinations of movements (demand). This means
    that each trip starts in a zone and ends in another zone. Zones connect the transport supply
    (network model with nodes, links, PuT lines, etc.) and the travel demand (in form of demand
    matrices (see "Matrices" on page 130)), which contain the demand (trips) of all OD pairs of the
    model.
    Every zone can be assigned a zone boundary (zone polygon) which represents the spatial
    extension of the zone. In the network model, zones are reduced to a zone centroid. Here the
    trips of a demand matrix are fed into the network. Every zone must be connected via a connector (see "OD pairs" on page 57) to at least one node. The optional zone polygon has no influence on the calculation results in the assignment; however, typical GIS functions such as
    intersecting can be realized with the zone polygon (see "Intersect" on page 696). Multiple
    zones can also be combined to a main zone for evaluation purposes.
    The zone size can vary depending on the level of detail of the model. Zones generally describe the position of places or utilities (for example, residential areas, work places, shopping
    centers, schools). Structural data such as the number of inhabitants, the number of jobs or the
    number of school places are stored here, which are used for calculating the traffic demand as
    input data (see "Demand modeling procedures" on page 136).

    56

    PTVGROUP

    3.1.5 OD pairs
    The illustration 14 shows an example of the transport demand between the zones and how
    they are available in the demand matrix.

    Illustration 14: Transportation demand between zones illustrated in the transport network and
    as a demand matrix
    Note: Zone boundaries are managed (see "The surface data model in Visum" on page
    120) like surfaces and can consist of multi-face polygons and polygons with holes.

    3.1.5

    OD pairs
    OD pairs exist between all zones of the network. The values in skim matrices and demand
    matrices (see "Matrices" on page 130) refer to one OD pair each. Compared to the other network objects, you cannot edit OD pairs interactively in the network editor, but you can filter OD
    pairs and display them graphically. For each OD pair you can select the skim matrix values,
    the demand matrix values and the direct distance as attributes. The table 9 shows a demand
    matrix value for Matrix 1 X and the skim matrix values for the skim of mean travel time for all
    OD pairs in the example Example.ver.
    From zone

    To zone

    100

    100

    0.00

    0.00

    100

    200

    2,000.00

    38.00

    100

    201

    200.00

    12.00

    100

    202

    0.00

    32.00

    200

    100

    2,000.00

    38.00

    200

    200

    0.00

    0.00

    200

    201

    5,000.00

    16.00

    200

    202

    2,000.00

    13.00

    201

    100

    200.00

    12.00

    201

    200

    5,000.00

    16.00

    201

    201

    0.00

    0.00

    201

    202

    0.00

    20.00

    PTVGROUP

    Demand matrix
    value (1 X)

    Skim matrix value


    (JRT)

    57

    3.1.6 Connectors
    From zone

    To zone

    Demand matrix
    value (1 X)

    Skim matrix value


    (JRT)

    202

    100

    0.00

    32.00

    202

    200

    2,000.00

    13.00

    202

    201

    0.00

    20.00

    202

    202

    0.00

    0.00

    Table 9: OD pairs in the example Example.ver

    3.1.6

    Connectors
    Connectors connect zones to the link network. Each zone has to be connected to at least one
    origin zone and one destination connector to the network for the assignment, so that the road
    users can exit and enter this zone. A zone can be connected to the network with any number
    of connector nodes.
    A connector corresponds to an access or egress route between the zone centroid and the
    connecting node. A connector has therefore two directions.
    Origin connector from zone to node
    Illustrates the access route to the network and thus the first part of the change of location.
    Destination connector from node to zone
    Illustrates the egress route from the network and therefore the last part of the change of
    location.
    The illustration 15 shows an example of how the travel demand between the zones, which is
    saved in the demand matrix, is applied via the connectors to the network.

    Illustration 15: Supply of the travel demand via connectors to the network
    For each direction, the permitted transport systems, meaning those transport systems which
    are permitted to use this connector, can be determined. In PrT, connections can be opened for
    all PrT transport systems. In PuT, however, a path always starts and ends with a route traveled
    by PuT pedestrian transit system on the connection. It is therefore assumed, that the access
    and egress of the stop is always by foot. For connectors in PuT there are basically two possibilities of modeling.

    58

    PTVGROUP

    3.1.6.1 Distribution of demand of a zone to the connectors


    One or more nodes in proximity to the zone centroid are connected. A PuT path always
    starts and ends with a walk link on the connector and continues on the network links to the
    access nodes of the next stop area and from there to the stop point, from which a vehicle
    journey is used (this approach is not recommended).
    Only nodes which are also access nodes of a stop area are connected. In this case, each
    path starts and ends with a walk link on the connector and within the stop continues to the
    start stop point. Links are not used like that (this procedure is recommended).
    The transport system dependent Connector time in unloaded network t0 is the time which
    each transport system requires to pass the connector. The standard value for t0 per transport
    system is calculated from the connector length (standard value is the direct distance) and the
    connector speed which also exists as a standard value (see User Manual: Chpt. 15.18.1 ,
    page 1159). The standard value for the connector speed can be assigned separately for PuT
    and PrT connectors. t0 can be overwritten manually by the user.
    3.1.6.1

    Distribution of demand of a zone to the connectors


    For modeling connectors in PuT and PrT, there are different possibilities of influencing the distribution of a zone demand to the connectors (see "Distribution of traffic demand across PrT
    connectors" on page 312 and "Distribution of the travel demand to PuT connectors" on page
    469). The illustration 16 provides an overview of these possibilities and describes each effect.

    Illustration 16: Possibilities for modeling connectors

    PTVGROUP

    59

    3.1.7 Main nodes and main turns

    3.1.7

    Main nodes and main turns


    Any number of nodes can be incorporated in a main node. Main nodes can be used if the
    Visum network is strongly disaggregated.
    Main turns are constituent parts of main nodes. They are created automatically when a main
    node is defined.

    3.1.7.1

    Main nodes
    For the illustration of roads and other transport-related areas, which are more or less structured by central reservation or traffic islands, there are several possibilities of displaying these
    in a transport model. For relatively strong abstraction, the correlation of components with
    regard to content, for example lanes of both directions on a road are illustrated by an individual link. This is the best view for traffic engineering analyses. With the increasing application of navigation networks with disaggregated illustrations of reality as a basis for
    transportation models, networks divided into small sections play an increasing role. These
    models then have both lane directions as two separated links in the Visum model. However,
    combining these in an aggregated display would create a lot of work as well as a loss of information, because the existing refined distribution is required when carrying out micro-simulations with the micro-simulation program Vissim.
    For conventional modeling, there is a contradiction between the activated demand for disaggregated network display and that of differentiated turn delays per turn type. We want to
    make it clear using an example.

    Illustration 17: Intersection area with multiple nodes


    If two roads intersect as in illustration 17 with separated lanes, the intersection area splits up
    into four nodes. If a triangle island is also present, the turns with the respective node are also
    added. A road user who comes from the bottom of the image and turns left, successively passes nodes 1 to 5. Only at node 3 he follows a turn, which constitutes a left turn; all other nodes
    he passes straight. Right turns only meet two nodes, at both nodes they traverse a turn to the
    right, whereas straight paths pass four nodes. If turn penalties were assigned, the sum of all traversed turns effects the node, although the contained shares, such as waiting at a SC only
    once has an effect in reality. A possible solution could be, to individually set the turn times of
    each movement, so that the sum of all traversing turns results in the desired value for the movement. This, however, is not possible with a type-based allocation of values, because turns of
    the same type would have to be attributed differently at the same node. There should rather be
    a linear equation system for each intersection area.
    The main node puts the thought underlying such a solution into effect by incorporating the
    nodes belonging to an intersection area explicitly in a separate object. All nodes of the intersection area thus form a logic unit, which takes the place of the previous nodes. Turns are
    regarded on the logic level of the main node and are called main turns here.
    60

    PTVGROUP

    3.1.7.2 Main turns


    Links whose From node and To node belong to the same main node are called inner links of
    the main node. It is called a cordon link if only one of the nodes is part of the main node. These
    constitute the access to and egress of main node: Each OD pair accesses the main node via a
    cordon link and egresses it via another one. A link is also a cordon link, if both nodes are allocated to different main nodes.
    The combination of several nodes in a main node defines, based on the nodes of the main
    nodes, different kinds of links:
    Inner links: From node and To node belong to the main node (illustration 18: (1)).
    Cordon links: one of the two nodes belongs to the main node, the other one lies outside of it (illustration 18: (2)).
    Directed links or One-way streets: this is a link with at least one direction with an
    empty TSys set or zero lanes.
    There is also cohesion between main nodes and different node types:
    Inner nodes: only inner links originate here (illustration 18: (3)).
    Cordon nodes at least one cordon link originates here, additionally possibly inner
    links (illustration 18: (4)).
    Partial nodes:any nodes that are allocated to a main node. These could be inner
    nodes, cordon nodes, and nodes lying beyond the boundary of the main node.

    Illustration 18: Node and link types of main nodes


    Note: Main node polygons are managed like surfaces and can be made up of multi-face
    polygons or polygons with "holes" (see "Multi-part surfaces" on page 124).
    3.1.7.2

    Main turns
    Main turns are constituent parts of main nodes. They are created automatically when defining
    a main node and can be edited manually.
    Main turns possess the same attributes as turns. They are automatically inserted or deleted
    when editing cordon links, i.e. when inserting or deleting cordon links and when editing the
    allocations to main nodes or relevant attributes (TSysSet, NumLanes).
    Each movement via the main node is represented by a main turn. A main turn is therefore the
    transfer from one cordon link to another. If the main node consists of a single node only, the
    main turn corresponds to exactly the turn between the links concerned. It is thus a generalization of the usual turns at a node on the level of the main node.
    If we reconsider the intersection area in illustration 17, assuming that all displayed nodes were
    incorporated in a main node, seven cordon links exist. Since a main turn leads from each

    PTVGROUP

    61

    3.1.8 Main zones and main OD pairs


    cordon link to each cordon link, there are 49 main turns at this main node. However, it does
    not make sense to traverse some of them, as they enter one-way roads in opposite directions
    (see "Main turns not open to traffic" on page 62). Exactly the 16 (or 12, in case of closed Uturns) convenient movements via the main node remain the main turns that are open to traffic
    (see " Main turns open to traffic" on page 62).

    Illustration 19: Main turns open to traffic

    Illustration 20: Main turns not open to traffic


    Within a main node the main turn completely takes the place of the network. This means that
    all traffic-related properties which take effect when crossing the main node are described
    exclusively by the attributes of the main turn and the main node. A path that crosses the main
    node only uses the main turn between the incoming and the outgoing cordon link. Neither the
    attributes of the (inner) links, nodes and turns in between are evaluated, nor will these network
    objects be loaded during assignment.

    3.1.8

    Main zones and main OD pairs


    Any number of zones may be combined to form a main zone. The zones themselves remain.
    There are OD pairs between all main zones of the network. The zone matrices (demand matrices and skim matrices) can be aggregated to main zone matrices if desired. Likewise, main
    zones can be broken down to zones. The same function is available for main zone matrices,
    as for zone matrices. As an option, main zone boundaries (polygons) can be defined.
    Note: Main zone boundaries are managed (see "The surface data model in Visum" on
    page 120) like surfaces and can be made up of multi-face polygons or polygons with
    "holes".
    Use cases for the application of main zones arise in the following situations:
    Multiple zones can be aggregated to larger study areas in very detailed modeled networks. This often also makes the graphical display in the network editor clearer.

    62

    PTVGROUP

    3.1.9 Territories
    Display of flow bundles on main zone level
    Display of desire lines
    If you connect multiple zones to one main zone, you can make the desire lines clearer.
    Executing diverse procedures on main zone level
    Note: It is currently not possible to calculate assignments or demand models on main
    zone level.

    3.1.9

    Territories
    Local authorities such as counties or districts can be displayed as territories, for example. PrT
    and PuT attributes can be calculated precisely by inserting territories and applying the operations territorial indicators (see User Manual: Chpt. 17.4.3 , page 1885) and PuT operating
    indicators (see User Manual: Chpt. 20.3.1 , page 2156). This means, that the indicator share is
    calculated which applies to a territory. Use cases occur especially when calculating PuT operating indicators.
    Note: Zone boundaries are managed (see "The surface data model in Visum" on page
    120) like surfaces and can be made up of multi-face polygons or polygons with "holes".

    3.1.10

    Paths
    All assignments in Visum in PrT as well as in PuT are path based, meaning that possible paths
    in the assignment are calculated for each origin-destination relation and loaded with a
    demand share. All other results, especially the volumes of the different network objects and
    the skim matrices are derived from these loaded paths. Paths are therefore the central result of
    the assignment procedure.
    In Visum the definitions path (PrT path and PuT path), PuT path leg and PrT paths on link level
    are used. PuT paths are thus described with a sequence of PuT path legs. Link-based PrT
    paths display all links which lie on a PrT path.
    On the basis of assignment results, using paths you can execute detailed evaluations, such as
    flow bundles (see "Flow bundles" on page 716), or verify the assignment results. As an option,
    Visum saves the assignment of paths found (see User Manual: Chpt. 18.1.2 , page 1890).
    Editing paths in PrT (PrT path object)
    In PrT, the user can manually edit paths. New paths can be inserted and existing paths can be
    modified. Both the course of PrT paths and their volume can be modified by the user (see User
    Manual: Chpt. 15.23.7 , page 1226). These paths are also available in the usual procedure
    (such as ICA or flow bundle calculations) like those paths created by a Visum assignment.
    Beforehand however, they have to be converted into demand segment paths, using the procedure convert paths. Furthermore, multiple so-called path sets can be maintained parallel in
    a network. Path sets thus combine multiple paths to a group. This is how you can successively
    store and switch between these assignment results in the network, for example. The following
    use cases occur, editing paths manually:
    Creating an own assignment result either by creating a network file in a text editor or interactively by digitalizing paths.

    PTVGROUP

    63

    3.1.11 Stop hierarchy: Stops, stop areas, stop points


    Editing assignment results calculated by Visum. This may occur interactively by digitalizing the path course in the network editor or by editing the path volume in the path list.
    On the other hand, the paths can be written as network files and edited in a text editor.
    Maintaining different assignment results in a network as path sets. Each path set then contains the paths in an assignment.
    Maintaining different flow bundle results as path sets. Each path set then contains the
    result (the paths) of one flow bundle calculation.
    Overwriting a selected section of the assignment result with external data. This is how
    only paths which start in this planned residential area can be edited manually and the rest
    of the assignment maintained in a transportation analysis.
    Distributing a matrix on paths. For a given matrix and given paths, the matrix values are
    distributed to the paths. This enables you to replicate the trip distribution and quickly
    update the manual assignment.
    There are two procedures for handling PrT path objects, which can be integrated into calculation processes (see User Manual: Chpt. 15.23 , page 1218):
    Converting paths (see User Manual: Chpt. 15.23.12 , page 1232). The procedure can be
    used for example, to replace one assignment result with another. There are the following
    possibilities:
    Converting assignment result to path set
    Converting path set to assignment result
    Converting path set to path set
    Converting assignment result to assignment result
    Distributing a matrix to paths (see User Manual: Chpt. 15.23.14 , page 1236). Based on a
    matrix and paths, the trips of the matrix are distributed to the paths. This enables you to
    modify the demand on the level of OD pairs and then distribute the new demand to all existing paths of the OD pair, in proportion to the previous shares. Distribution is carried out
    with the attribute ShareOfPathTarget. The attribute can be defined for each path by the
    user. For each OD pair of a path set the attribute ShareOfPathTarget is first added up
    (total weight) on all paths.

    Where P is all paths in a path set of origin O to destination D. If e.g. there are five paths from
    zone A to zone B, the ShareOfPathTarget of the five zones is added together.
    The volume of an individual path p then results from the following equation.

    3.1.11

    Stop hierarchy: Stops, stop areas, stop points


    In the PuT sector there are a variety of stops, which extremely differ in construction and size.
    This variety can range from simple masts by the roadside to large, multi-story railroad stations,
    bus terminal or subways. Compared to this, there is a concept in Visum, which also allows
    large stations to be illustrated in detail and also comprehend simpler situations, without having
    to specify many entries. This illustration is shown in Visum, by the so-called stop area

    64

    PTVGROUP

    3.1.11.1 Stop points


    hierarchy, which is composed of the network objects stop, stop area and stop point. Each of
    these three levels fulfills certain, clearly separated tasks within the transport network.
    Stop point
    Specified departure point for one or more lines. PuT lines stop here for passenger
    boarding. In the most detailed model, the stop point corresponds to a stop sign for bus
    services or the edge of a platform in the case of rail services.
    Stop area
    Combines several stop points in close proximity and displays the access to the stop
    points in the remaining transport network via an access node.
    Stop
    Is the object which comprises the entire complex of stop points and stop areas. It is the
    highest object of the stop hierarchy and carries the name of the stop and others, for the
    entire construction applying attribute. In the real network, it is therefore of more organizational nature.

    Illustration 21: The stop hierarchy


    3.1.11.1

    Stop points
    Because the vehicles can only move within the modeled network, a stop point has to be
    connected to the network. This is achieved, by either inserting a stop point on a link or on a
    node. If a stop point is on a link, it is called a link stop point. A stop point on a node can be supplied by all lines which traverse this node. A stop point on a link can only be served by lines
    which pass this link. This permits detailed direction modeling based on masts. Stop point links
    can, however, also be inserted undirected, so that they can be run for both directions of the
    link.

    PTVGROUP

    65

    3.1.11.2 Stop areas

    Stop point on node


    Link stop points
    Illustration 22: Possibilities of modeling stop points
    The differentiation between stop points on nodes and links allows network models of different
    levels of detail to be generated with Visum:
    For strategic planning, stop points on nodes are sufficient, since the exact position of
    the stop point in front of or behind the road junction is usually of no interest. The
    stop area and stop are generated automatically in the background, but generally
    remain hidden to the user, if desired.
    For operational planning and AVLS supply, it is useful to model the stop points on
    links, as you can then achieve the required degree of detail.
    It is also possible, of course, to mix both types in Visum, for example by using the more accurate link-based model in built-up areas and the node-based model in non-built-up areas.
    A stop point can be permitted or blocked for each existing transport system. Only line route
    vehicle journeys, whose transport system is permitted, can stop there.
    Notes: We recommend to set the start or end point of a line route only at stop points
    which are located on nodes, because inaccurate results might occur if a line route starts
    or ends at link stop points, for example, when calculating PuT operational indicators or in
    case of PuT volumes which are displayed on link level.
    Because vehicle journey stops always occur at a stop point, each stop has to have at
    least one stop point.
    3.1.11.2

    Stop areas
    A stop area divides a stop into areas. An area can for example represent a bus or train station
    platform, an intersection with stop points, a P&R car park, a station concourse, etc. A stop area
    is assigned to a single stop and can comprise several stop points.
    Stop areas are used on the one hand to determine transfer walk times between the stop areas
    of a stop. They combine stop points which do not differ from other stop points with respect to
    their transfer walk times. If for example at a railway station the stop points of the individual platforms are combined into a single stop area and the bus stops on the forecourt as well, this
    makes it possible to include closely separated minimum transfer times from rail to rail, rail to
    bus, and bus to bus. The matrix of transfer walk times (From Stop Area To Stop Area) can

    66

    PTVGROUP

    3.1.11.3 Stops
    indicate which public transport walk system (for example, stairs, escalator, lift, ground-level
    walkway) is used. The transfer time for a demand segment is always the minimum time required for all permitted PuTWalk systems. User group-dependent transfer times, for example for
    mobility-impaired persons, can be modeled by permitting selected PuTWalk systems (for example, ground-level walkways and lifts) only for specific demand segments. Stop areas can also
    represent intermediary levels in large station areas. In this case, while transfer times to other
    stop areas exist, the stop area itself does not contain stop points.
    Note: The transfer walk times (transfer walk times matrix) between the stop areas is defined at the stop.
    The second function of stop areas is to connect stops to zones and the walkway network
    beyond the stop. As an option, to each stop area a network node which can be reached with
    the same transfer times like each stop point of the area can be allocated. The time within a
    stop area (diagonal of the transition matrix) is not used for the transfer to the access node. Via
    this network node, PuT paths can change from a public transport line to links with PuTWalk or
    PuT-Aux transport systems as well as to connections to zones and vice versa.
    3.1.11.3

    Stops
    A stop comprises the entire complex of stop areas and thus also stop points. To ensure that a
    stop can be localized and displayed in graphical form, it has a coordinate, but it is not assigned directly to a network node or link.
    The stop contains information on route times within each stop area (on the transfer walk time
    matrix diagonal) and between two stop areas. In addition to these walk times, as an option the
    stop also has transfer walk times and wait times between transport systems. With this a particularly through structural or organizational measures aggrieved or favored transfer between
    vehicle journeys can be illustrated, for a modeled stop without stop areas, for example. The
    general transfer walk time of eight minutes could apply in a large train station, when changing
    from an ICE train to another train, however, because of track information, three minutes should
    be sufficient, for example. In such a case, these three minutes could be defined as transfer
    time of the transport system ICE in the same transport system.

    3.1.12

    PuT operators
    Providers of public transport vehicle journeys, for example local transport services or train operating companies, are called operators. The network object operator is the starting point for
    analyses of the public transport supply from operator point of view. It is therefore used within
    the network for grouping lines and vehicle journeys to jointly evaluate units. An example is the
    distribution of the revenues to the various operators of a transportation agency. This is often
    based on service kilometers or seat kilometers. If you have assigned operators to the vehicle
    journeys in your model, you can evaluate these and many other indicators (see "Operator
    model PuT" on page 541).
    Operators can either be assigned to a whole line (one then talks about a standard operator) or
    individual vehicle journeys.
    Note: Please note that changing the standard operator of a line subsequently, does not
    overwrite the operators of existing vehicle journeys.

    PTVGROUP

    67

    3.1.13 PuT vehicles: Vehicle units and vehicle combinations

    3.1.13

    PuT vehicles: Vehicle units and vehicle combinations


    In Visum, PuT vehicles such as buses, trams or intercity trains are modeled through the network objects vehicle unit and vehicle combination. Using these network objects, it is possible
    to change the composition of a vehicle journey en route (see "Network objects of the line hierarchy" on page 68). This is how a train in the preceding and succeeding legs can run with
    fewer coaches than in the main leg. The second application case for PuT vehicles is in the operator model section. Indicators such as service kilometers can be evaluated on the level of
    vehicle combinations (see "Operator model PuT" on page 541).
    Each vehicle unit is allocated to one or more transport systems. It can only be used for vehicle
    journeys, lines or system routes, which belong to one of these transport systems. Furthermore,
    for each vehicle it is specified whether it is a railcar or not. In addition to the number of seats
    and the total capacity including also the standing capacity, cost rates can be entered per
    distance and time unit, for vehicle journeys und empty trips separately. These data are determined within the scope of the operator model for evaluations.
    Vehicle units are combined to vehicle combinations. A vehicle combination thus always comprises one or more vehicle units. The same vehicle unit can appear repeatedly in the vehicle
    combination. This is how a vehicle combination intercity train can be composed of a vehicle
    unit railcar and multiple vehicle units coaches, whereas for the railcar and the coaches different cost rates or capacities can be specified.
    The set of permitted transport systems for a vehicle combination is determined as a mean of
    the permitted transport system sets of the respective vehicle units. If there is no transport system permitted for all associated vehicle units, these cannot be combined to a vehicle combination.
    Also for vehicle combinations, separate distance and time related cost rates can be specified
    for vehicle journeys and empty trips. These take effect together with the cost rates of the
    respective vehicle units. Use these input possibilities therefore for such costs, which accumulate only once per vehicle combination. Typically, maintenance costs should be specified
    per vehicle unit, and personnel costs however, per vehicle combination.
    Vehicle combinations can be assigned eitehr to entire lines or time profiles (one then talks
    about a standard vehicle combination) or to individual vehicle journey sections. This enables
    very detailed modeling of changes in train formations or also strongly disaggregated evaluations of PuT operator indicators, for example.
    Note: Please note that subsequent modifications of standard vehicle combinations of a
    line or a vehicle profile do not overwrite the vehicle combinations of the existing vehicle
    journey sections.

    3.1.14

    The line hierarchy


    The modeling of the transport supply in PuT is hierarchical. This structure enables the user to
    reuse data specified once as efficiently as possible, for example the course of a line for
    several vehicle journeys.

    3.1.14.1

    68

    Network objects of the line hierarchy


    The illustration 23 shows the six network objects of the line hierarchy.
    PTVGROUP

    3.1.14.1 Network objects of the line hierarchy

    Illustration 23: The line hierarchy used to model the PuT supply
    Main lines
    This optional network object is used for an aggregated evaluation of the lines allocated to the
    main line. A main line can also incorporate lines of different transport systems. The network
    object does not affect the assignment or the structure of the timetable.
    Lines
    A line structures the public transport supply. Within the Visum data model, it is mainly used to
    aggregate several line routes. Each line has at least one line route or multiple line routes. The
    line itself neither has a spatial course in the network (see "Line routes" on page 69), nor are
    run times specified between the stop points (see "Time profiles" on page 70) . Each line
    belongs to exactly one transport system. You can optionally allocate a standard operator and
    a standard vehicle combination to a line. When creating new vehicle journeys, they will then
    be suggested as default values.
    Line routes
    A line route is part of exactly one line and describes the Spatial route course of the line for
    one direction (from now on called the Line route course).
    The line route course is issued as a classified series of route points. The length data of the line
    route course are output between two consecutive route points. A route point can be a node or
    a stop point along the line route course. All stop points along the course at which the line route
    can stop, are always route points. All nodes along the course can optionally be declared as
    route points. The line route course must start and end at a stop point that is located on a node.
    The line routes of a line are usually available in pairs for the two directions. However, each
    line can incorporate any number of line routes (cf. for example illustration 24). Different line
    routes (pairs) of a line represent different route courses, which are organized in lines.
    Line routes can be generated either manually or based on existing system routes (see "System routes" on page 80).

    PTVGROUP

    69

    3.1.14.1 Network objects of the line hierarchy


    Link network

    Line route 1

    Line route 2

    Illustration 24: Example for two line routes of a line


    Time profiles
    Each line route has one or more time profiles. A time profile describes the temporal sequence
    of the line along the line route. However, specific departure times are not specified, but the run
    times between the individual route points.
    Analogous to the line route (route points), the time profile is described by a sequence of profile
    points. This sequence of profile points is called the course of the time profile. Any route points
    of the underlying line route can be profile points. However, the start stop point and the end
    stop point of the line route as well as all stop points, at which passengers can board or alight
    must be among them. The time profile may also contain passage times for any route points of
    the line route, e.g. for a conflict check of the timetable routes. Profile points are the points in the
    network, between which the run times are specified in the time profile. The run time is specified for the section between the previous and the current profile point. In case of stop points,
    a stop time can additionally be specified and boarding and alighting can be permitted or prohibited.
    Multiple time profiles of a line route can, for example, differ in the selection of the profile points
    or the run times on the different sections between the profile points (cf. for example illustration
    25). If a vehicle journey of a line route shall stop at a stop point along the route yet another one
    shall not stop, you need to define two time profiles for the same line route (yet not if a vehicle
    journey shall serve just a section of the line route and thus of the time profile).

    70

    PTVGROUP

    3.1.14.1 Network objects of the line hierarchy


    Furthermore, each time profile has a name and an allocation to a direction. Optionally, a standard vehicle combination can be allocated to the time profile. When inserting a new vehicle
    journey, this is then applied automatically as a default value.
    Note: Please note that the vehicle combinations of existing vehicle journeys are not overwritten. If a standard vehicle combination is specified for the line also, the standard
    vehicle combination of the time profile takes effect when inserting a new vehicle journey.
    Fare points can still be specified at the time profile, for each profile point. These can enter the
    calculation of revenues (see User Manual: Chpt. 20 , page 2091).
    When modeling public transport, time profiles are important in the following use cases:
    Couplings are set on time profile level (see User Manual: Chpt. 15.31.5.5 , page 1331).
    Headways for the headway-based assignment are specified on time profile level (see
    User Manual: Chpt. 7.9 , page 473).
    As a consequence, all network objects which, in the line hierarchy are located below the time
    profiles (vehicle journeys and vehicle journey sections), are not relevant when defining headways or couplings. Therefore, if you want to couple profiles on vehicle journey level or specify
    headways, you need to create a separate time profile for the respective vehicle journeys and
    carry out the coupling or the definition of the headways here.
    Line route 1

    Time profile 1.1


    SPoint

    Stop

    Time profile 1.2


    Arr

    Dep.

    SPoint

    Stop

    Arr

    Dep.

    0:00

    1:00

    1:02

    2:00

    2:02

    1:50

    1:52

    3:00

    3:02

    2:50

    2:52

    5:00

    5:02

    4:50

    5:02

    6:00

    6:00

    0:00

    Illustration 25: Example of two time profiles of a line route

    PTVGROUP

    71

    3.1.14.1 Network objects of the line hierarchy


    Vehicle journeys (=journeys)
    A vehicle journey describes a planned public transport service or a set of planned service
    trips, which are summarized to an administrative unit with a given ID number. Every day of the
    calendar used in the network, at most one of these vehicle journeys will then run.
    Each vehicle journey belongs to exactly one line route and exactly one time profile. It also has
    a reference to two stop points of the line route, which define the section on which the vehicle
    journey follows the course of the line route. Vehicle journeys can therefore traverse any section of a line route. It is therefore not necessary to define a line route with a shorter extension
    for vehicle journeys, which only traverse a line route partially. Vehicle journeys cannot, however, switch from one line route to another. This means that each trip can only run on exactly
    one line route.
    Furthermore, the vehicle journey contains a departure time at the start stop point from which,
    together with the relative times of the time profile, all arrival, departure and non-stop run times
    of the vehicle journey are determined.
    A vehicle journey can optionally be assigned an operator. You can then calculate aggregated
    evaluations of PuT operating indicators on operator level (see "Operator model PuT" on page
    541).
    Vehicle journey sections (=journey sections)
    There is normally exactly one journey section per vehicle journey. This is created automatically when inserting a vehicle journey. As an option, a vehicle journey can be subdivided
    into multiple vehicle journey sections, which can then be divided into the following properties.
    Valid day
    Vehicle combination
    Start and end stop point
    Pre and post preparation time for line blocking (see "Line blocking" on page 553)
    This results in the following application possibilities for example.
    A vehicle journey, which traverses from A to C via B from Monday to Friday, on the weekend however, only from A to B, can be modeled by two vehicle journey sections, which
    only differ in their valid days.
    A train, running from A via B to C, between A and B however with less coaches, can be
    modeled by two vehicle journey sections, which differ in their vehicle combinations and
    start and end stop points.
    Any combinations are possible, for example a train which runs between A and B and
    which is only short on the weekend.
    Vehicle journey sections are network objects, with which line blocking is carried out (see
    "Line blocking" on page 553).
    The table 10 shows an example with three vehicle journeys of a line route. The line route has
    two time profiles. Vehicle journey 993 is divided into three vehicle journey sections, which differ in valid days and vehicle combinations.

    72

    PTVGROUP

    3.1.14.1 Network objects of the line hierarchy


    Trip number

    from -> to

    Departure time

    991

    NH

    06:02 a.m. (daily) Daily

    Loco + 6 coaches

    992

    MH

    05:10 a.m. (daily) Daily

    Loco + 6 coaches

    993

    MH

    06:00 a.m. (daily) Daily

    Loco + 6 coaches

    HS

    11:02 a.m.
    (Sat+Sun)

    Sat+Sun

    Loco + 6 coaches

    MN

    06:00 a.m. (MonFri)

    Mon-Fri

    1 additional coach

    Line
    Line route

    Valid day

    Vehicle combination

    IC1

    IC1

    IC1

    Time profile

    1.1

    1.2

    1.1

    Trip number

    991

    992

    993

    Valid day

    Daily

    Daily

    Mon-Fri

    Sat+Sun

    Mon-Fri

    Vehicle combination

    L+6C

    L+6C

    L+6C

    L+6C

    1C

    M dep.

    05:10
    a.m.

    06:00
    a.m.

    I arr.

    07:00
    a.m.

    I dep.

    07:02
    a.m.

    N arr.

    07:00
    a.m.

    08:00
    a.m.

    N dep.

    06:02
    a.m.

    07:02
    a.m.

    08:02
    a.m.

    W arr.

    7.00

    08:00
    a.m.

    09:00
    a.m.

    W dep.

    07:02
    a.m.

    08:02
    a.m.

    09:02
    a.m.

    H arr.

    09:00
    a.m.

    10:00
    a.m.

    11:00
    a.m.

    H dep.

    11:02
    a.m.

    S arr.

    12:00
    a.m.

    Trip number 991 requires one vehicle journey section


    Trip number 992 requires one vehicle journey section
    Trip number 993 requires three vehicle journey sections

    PTVGROUP

    73

    3.1.14.2 Specifications of lengths and times


    Table 10: Example of three vehicle journeys
    3.1.14.2

    Specifications of lengths and times


    In conjunction with lengths, different attributes exist at different network objects. The illustration
    26 displays these attributes and their correlations. The attribute Length at the link is used as
    standard value for the attribute PostLength at the line route items. The user has the possibility
    of overwriting these standard values. This can be done manually, for example in the list for line
    route items (see User Manual: Chpt. 24.1.10 , page 2321). If the standard value from the link
    lengths should be carried out, you can use the function set lengths. There are four possibilities
    for changing the link length.
    The link length can be allocated from the direct distance of the link (see User Manual:
    Chpt. 15.14 , page 1099).
    The link length can be allocated from the polygon length of the link (see User Manual:
    Chpt. 15.14 , page 1099).
    When shaping the link, it can be specified that the link length should comply with the polygon length (see User Manual: Chpt. 15.14.11 , page 1115).
    You can overwrite the link length in the link list manually, for example, and thus assign
    any length to the link (see User Manual: Chpt. 24.1.10 , page 2321).

    Illustration 26: Lengths in Visum and their coherence


    Visum offers different possibilities to assign times to links and time profiles. The illustration 27
    provides an overview on how you can influence the run time values for links and time profiles.
    The standard values for the link run time of a PuT transport system (t-PuTSys ) is calculated
    from link length divided by the link-specific speed of the PuT transport system. The link run
    time of the PuT transport system again provides the standard values for the travel times in the
    time profile. The departures and arrivals of a vehicle journey always automatically result from
    the times provided in the respective time profile. The run times for each PuT transport system
    can be changed as follows.

    74

    PTVGROUP

    3.1.14.3 The term timetable in Visum


    The run times can be assigned from the line run times.
    The standard value (quotient of link length and link-specific speed of the PuT transport system) can be restored.
    You can overwrite the times manually in the link list, for example (see User Manual: Chpt.
    24.1.10 , page 2321).
    The run times of the time profile can be edited as follows.
    Transferring the standard values from the link run time
    Transferring the times from a system route
    Transferring the times from a link attribute
    Setting the times from a time profile attribute
    You can overwrite the times manually in the time profile list, for example (see User
    Manual: Chpt. 24.1.10 , page 2321).

    Illustration 27: Assignment of run times in Visum


    3.1.14.3

    The term timetable in Visum


    According to the line hierarchy the timetable in PuT in Visum is set up hierarchically. The line
    route contains the information on the location, the time profile accounts for relative time

    PTVGROUP

    75

    3.1.14.4 Data consistency along the line hierarchy


    specifications and the vehicle journeys and their vehicle journey sections provide valid day,
    departure time and the traversed sections of the line route. All four object types together make
    up the timetable, therefore the information, where and when PuT vehicle journeys take place.
    Alternatively, the public transport supply side can also be described through line routes, time
    profiles and a regular service per time profile (see "Headway-based assignment" on page
    473). In this case we are also talking about a timetable in Visum.
    Due to this hierarchical structure of the timetable, is it possible to reuse the data for various
    similar vehicle journeys. Otherwise, the exact route in the network would have to be specified
    for each individual vehicle journey and all times entered. With the line hierarchy however, a
    regular headway can easily be defined by specifying the departure times, the time profile and
    the line route.
    3.1.14.4

    Data consistency along the line hierarchy


    An important property of the line hierarchy is the consistency of the various data. Line route,
    time profile and vehicle journey section must match at any point of time. A run time between
    two stop points, which are not touched by the used line route, are never allowed to be specified in the time profile. Visum assures that this consistency is always maintained. If you make
    changes to the objects of the line route, the objects based on these may be adjusted, to reestablish a consistent state applicable to the new situation.

    3.1.14.5

    Aggregation of line routes


    Aggregation of line routes is the aggregation of several line routes or time profiles to combined
    objects. A number of line routes with the same or similar information can occur especially
    when importing old networks from Visum 8 or when importing timetable data from an external
    source. In an extreme case, both an individual line route and a specific time profile are created
    for each individual vehicle journey. Essential advantages of the hierarchical setup of the
    Visum PuT model are thus lost, such as the reuse of line route data for many vehicle journeys.
    Furthermore, the number of line routes makes editing and maintaining the overview more difficult. The function aggregate line routes supports you when importing third-party data, to use
    these to your advantage.
    Criteria for aggregating line routes
    When aggregating, two line routes are aggregated in the first step. Both line routes have to
    have common line path sections, but do not have to necessarily correspond with each other. If
    it has been determined, that two line routes can be aggregated successfully, the time profiles
    of a line route are tried to be aggregated in a second step. The following general criteria for
    the aggregation of line routes apply.
    1. Both line routes have a common path leg.
    2. The start of the common path leg is also the start of (at least) one of both line routes.
    3. The end of the common path leg is also the end of (at least) one of both line routes.
    The illustration 28 shows examples of cases in which aggregation is possible and in where
    not.

    76

    PTVGROUP

    3.1.14.6 Coupling time profiles

    Illustration 28: Example of the aggregation of line routes


    As an option, aggregating line routes can be made more difficult with the following conditions.
    Line routes have to be assigned to the same line.
    Line routes must have the same lengths on the common section.
    Line routes must have the same direction.
    Aggregating time profiles can also be made more difficult as an option.
    Time profiles must have the same run and dwell times.
    Time profiles must have the same settings for boarding and alighting.
    Time profiles must have the same vehicle combination.
    3.1.14.6

    Coupling time profiles


    Coupling means connecting cars of two or more trains on a line route section. The figure
    shows several examples of coupling two or three line routes. If you want to link two line routes
    on a section, the stop points of their time profiles must correspond to each other. Their run
    times and stop times on the "linking" section, however, need not be identical. If required, they
    can be changed.

    PTVGROUP

    77

    3.1.14.6 Coupling time profiles

    Illustration 29: Examples: Coupling two and three line routes


    The number of vehicle journeys and their departure times from From/To Stop Points of coupled
    sections may deviate. Missing vehicle journeys are generated.
    In Visum, coupled line routes form a coupling group. Visum adjusts the times and the timetable
    of the coupled line routes. Visum automatically adjusts the data of all line routes of the coupling group after changes to the time profile of a single coupled line route.
    Changes to the number of vehicle journeys
    Changes to the number of vehicle journeys on a coupled section may occur in the following
    cases.
    Inserting and deleting vehicle journeys (see User Manual: Chpt. 15.43 , page 1526)
    Inserting and deleting vehicle journey sections (see User Manual: Chpt. 15.43 , page
    1526)
    Changing the length of vehicle journeys (see User Manual: Chpt. 15.43 , page 1526)
    These changes need to have an effect on coupled time profiles, so that the supply of vehicle
    journeys in each coupling section is synchronized again.
    Changes to the temporal position of vehicle journeys
    In the following cases, the temporal position of vehicle journeys may change. These changes
    need to have an effect on coupled time profiles, so that the supply of vehicle journeys in each
    coupling section is synchronized again.
    In-vehicle time/stop time changes to the time profile
    This has an effect on all vehicle journeys that include the section start item --> reference point or reference point --> start item respectively in the altered section.
    Changes to the departure time of one or more vehicle journeys via Edit vehicle journey in the timetable editor, Multi-edit in the network editor or by shifting the vehicle
    journey within the timetable editor.

    78

    PTVGROUP

    3.1.14.6 Coupling time profiles


    Coupling when calculating the PuT operating indicators
    Couplings in some cases have an effect on the calculation of PuT operating indicators (see
    "Impact caused by couplings" on page 676). On which indicators exactly they have an effect
    can be found in the file Indicator availability.xls in your Visum installation. The effect on coupling is illustrated by some examples.
    Service-km of the line route
    The kilometers traversed by the coupling section are considered only once and distributed to the coupled line routes. 50% of the length of the coupled route section is
    assigned to each of the coupled line routes after coupling 2 line routes.
    Service time of the line route
    As for kilometers, the service time is only calculated once and distributed evenly.
    Infrastructure cost of the line routes for links and stop points
    Link costs (for example rail track cost) and stop point costs are considered only once.
    These costs are distributed evenly to the coupled line routes.
    The number of line services and vehicle kilometers per link are only counted once.
    As service-km, service-time and the infrastructure cost influence the operating cost of a line
    route, coupled line routes which result in lower costs.
    Coupling does not have an impact on line blocking or assignments.
    During assignment, changing seats within a coupled line is thus regarded as a regular transfer
    between line routes.

    Illustration 30: Calculation example for the calculation of indicators in case of couplings
    Number of trips

    10 trips

    Empty time

    10 min/trip

    Kilometer costs

    1 euro/km

    Hourly costs

    60 euros/h

    Track price

    1 euro/km

    Seats

    100 seats/vehicle combination

    PTVGROUP

    79

    3.1.15 System routes


    Table 11: Input data for the calculation example

    Line route

    Not coupled

    Not coupled

    Coupled

    Coupled

    L1-1

    L1-2

    L1-1

    L1-2

    ServiceKm
    SeatKm

    1,300 km

    1,300 km

    1,050 km

    1,050 km

    13,000 km

    13,000 km

    13,000 km

    13,000 km

    Service time

    900 min

    1,000 min

    750 min

    850 min

    Out-of-depot
    time

    1,000 min

    1,100 min

    850 min

    950 min

    Cost

    1,300 EUR

    1,300 EUR

    1,050 EUR

    1,050 EUR

    Cost

    1,000 EUR

    1,100 EUR

    850 EUR

    950 EUR

    Track costs

    1,300 EUR

    1,300 EUR

    1,050 EUR

    1,050 EUR

    Total cost

    3,500 EUR

    3,600 EUR

    2,950 EUR

    3,050 EUR

    10

    10

    10

    10

    Num Vehicle
    journeys

    Table 12: Calculation of indicators for the line route


    Link
    ServiceKm

    H2-H3

    H3-H4
    1,000 km

    Num Vehicle
    20
    journeys
    Table 13: Calculation of indicators for the links

    3.1.15

    H2-H3

    H3-H4

    400 km

    500 km

    400 km

    10

    10

    10

    System routes
    A system route describes a route within the network from one stop point to another, with the
    time required. As an option, this required travel time as well as supplements for starting and
    braking per vehicle combination can be further specified. It is important that the travel times
    are always stored independent of concrete lines in the system route. The system route thus
    represents a time which a certain vehicle combination requires on a given route between two
    stop points, independent of whether they belong to a line or even to a concrete vehicle journey.
    This travel time and route information can be used in two ways for creating a timetable.
    Editing the shape of a line route with system routes
    Travel times of existing line routes and time profiles are composed of system routes
    Editing the shape of a line route with system routes
    System route path information provides a part of the line route path. The travel time information
    goes into the upper travel time profile in sections. Alternatively, you can create line routes or
    individual sections with system routes. As soon as there are successive system routes at the

    80

    PTVGROUP

    3.1.16 Points of Interest (POI)


    current end point, these can be used to extend the line route to the end stop point of the system route. The travel times for this section can be taken from the system route, preferably the
    one for the correct vehicle combination, if this is specified. If both the start stop point and the
    end stop point of the system route are served by the line route, the run time is determined as
    the sum of the passage time and the TStartStop and TEndStop of the line route. If the line route
    runs past one of the successive stop points, the share of the corresponding supplement is omitted. In this way, it is possible to use system routes for stopping as well as for traversing time
    profiles.
    Setting travel times of existing line routes and time profiles
    You can use system routes to reset run times of existing line routes and time profiles. The path
    information of the line route is not lost. If a matching system route exists between two profile
    points of the time profile, its run time will be used for the time profile. Depending on whether
    passengers are scheduled to board and alight at the limiting stop points, only the pure passage time or the sum of the passage time TStartStop and TEndStop will be used.
    A system route matches a section between two profile points, if the following conditions apply.
    Both profile points are located at stop points.
    These stop points are start stop point and end stop point of the system route (this requires
    that these stop points must be open to the transport system of the time profile).
    The course of the line route underlying the time profile is identical to the course of the system route.
    The transport system of the system route is identical to the one of the time profile (i.e. the
    line).
    If the respective option has been selected, at the system route, a specific run time must be
    specified for the vehicle combination allocated to the time profile or line.
    If several matching system routes exist, the times are not set for the sections in question.
    When new time profiles are created, the run times are calculated on the basis of the system
    route (if available). Special defaults are taken into account for the vehicle combination if it is
    specified for both the system route and the time profile.
    If no system routes have been defined, link times are used as before.
    Besides being used in the timetable, system routes play an important role in line blocking. As
    an option, system routes can be used for empty trips within line blocking or new system routes
    can be generated automatically for that purpose (see User Manual: Chpt. 15.33.8 , page
    1378).

    3.1.16

    Points of Interest (POI)


    A Point of Interest (POI) is a user-defined network object with spatial reference. The spatial
    reference is established by entering an X and a Y coordinate for each POI. POIs can be inserted as point or surface objects. Each POI can be assigned a surface (attribute Surface ID ) as
    an option or any image (attribute Image file name ). By default, Visum already offers a preselection of symbols, which can be used for visualizing POIs (star, cross, triangle, SC, and
    others).

    PTVGROUP

    81

    3.1.16 Points of Interest (POI)


    Note: POI polygons are managed like surfaces and can be made up of multi-face polygons or polygons with "holes" (see "The surface data model in Visum" on page 120).
    Points of interest are mainly used for data management (for example, network data maintenance in Traffic management centers) and accessibility studies. For your data management,
    you can create as many user-defined attributes for POIs as you like, in which you can store
    your data (see "User-defined attributes" on page 110). The illustration 31 shows an example
    for applying POIs in reachability analyses. Here secondary schools are included as POIs (red
    stars) in the model. The catchment area of these schools was visualized with the 2D display
    (see "2D display" on page 768).

    Illustration 31: Reachability analyses for secondary schools


    POIs are managed in POI categories. Each POI must be allocated to a POI category. Before
    inserting the first POI, you thus have to create a POI category (see User Manual: Chpt. 15.34.1
    , page 1384). Any number of POI objects can then be inserted in the defined POI category, in
    the network.
    POI categories in a transport network are for example

    82

    PTVGROUP

    3.1.16 Points of Interest (POI)


    Parking and Park&Ride facilities
    Public facilities such as schools, churches of hospitals
    Pre-emption points for AVLS (automatic vehicle location systems)
    SC controllers etc.
    POI categories can be organized as a hierarchy. This is how you can create a POI category
    schools with the three subcategories secondary schools, junior high schools and elementary
    schools.
    Each POI can be assigned to a node, a link, another POI, a stop area, a stop point or a POI
    category. You can illustrate this assignment graphically in the network (see User Manual:
    Chpt. 24.3.5 , page 2348). In the example of illustration 32allocations are used to illustrate for
    parking lots in a downtown area which links the approaches lead to.

    Illustration 32: Allocating POIs to links


    If you want to import data from GIS systems into Visum, these data can be stored as POIs in the
    network model (see User Manual: Chpt. 22.4 , page 2221).
    Notes: POIs and their assignment to network objects do not have an influence on procedures, such as assignments for example.
    If you create a user-defined attribute for a POI category, it will also be created for all subcategories of the POI category.

    PTVGROUP

    83

    3.1.17 Count locations and detectors

    3.1.17

    Count locations and detectors


    Count locations mark the geographical position of traffic counts. This can be both one-off
    counts and permanently installed counting features. A count location is identified by a number.
    Apart from a code and a name, it always has a position on a link, described by the ID of the
    link (From Node and To Node) as well as a relative position. This is a number between 0.0
    and 1.0 and describes where the count location lies on the link. Since a link in Visum is always
    directed, a direction is indicated as well. Furthermore, the count location has a type, to differentiate permanent count locations and manual count locations, for example. The coordinates of the count location are available as a calculated attribute; these are calculated from
    the coordinates of the link and the position along this link. Each link can be assigned by direction to one or more count locations. Each count location can in turn be assigned to detectors.
    The detector is identified by its number and in addition to code and name it has a geographic
    position, specified by a pair of coordinates. Two types of detectors are distinguished:
    The detector is allocated to a node or a main node. This type of detector serves for modeling signal control, for example, traffic-responsive signal control. It is not possible to define
    a reference to count locations.
    The detector is defined freely in the network and as an option, it can be allocated to a
    count location, and so also indirectly to a link. In this case the detector constitutes a lanebased count location. It breaks down the count data of a count location precisely by lane.
    The number of observed lanes is defined via the observed lanes attribute. The lane
    observed on the far right is defined via the Lane position attribute. If a detector is allocated to a count location and therefore, to a link, the observed lanes have to be compatible with the number of link lanes. This means that no lane which is not defined on the
    link may be observed. With a lane number of two the detectors for lanes 1 and 2 are allowed to be defined. It is however permitted, that a lane is observed by several or no detectors.
    Count locations and their detectors are used less to maintain data, but more to visualize and
    process thematic maps. Even though you can save count data to user-defined attributes of
    count locations, you can also save them directly to user-defined attributes of the link (see
    "User-defined attributes" on page 110). The advantage of saving count data directly at links is
    that, in evaluations, you can compare them directly with the calculated volumes, which are
    also saved with the link attributes. This approach is particularly recommended if you want to
    use the matrix correction technique TFlowFuzzy (see "Updating demand matrix with
    TFlowFuzzy" on page 210).
    Count locations are thus primarily used for marking the position of a count in the network. You
    can use the number to refer to external data, where applicable. The illustration 33 shows a
    map, which is illustrated in the local position of the count location in the network, together with
    the date of the last traffic count.

    84

    PTVGROUP

    3.1.18 Toll systems

    Illustration 33: Visualization of the local position of count locations with the date of the count
    Notes: Do not just use count locations to integrate count values into the network. Instead
    use user-defined attributes on links. However, if the current project requires the visualization of counts or count location-related values shall be managed externally, the effort
    for the coverage of count locations and detectors can pay off.
    Compared to assignments for example, count locations and detectors do not have an
    influence on procedures. The only exception are detectors near nodes which can be
    taken into account for traffic-responsive signal control. Information provided by these
    detectors are also used for ANM export to Vissim.

    3.1.18

    Toll systems
    Toll systems are network objects which can be used to integrate toll zones and tolls into the
    network model (see User Manual: Chpt. 15.38 , page 1417). They represent the basis for the
    calculation of road tolls in the Tribut procedure (see "Basics of assignment with toll consideration" on page 399).
    In Visum, there are two kinds of toll model types:

    PTVGROUP

    85

    3.1.19 GIS objects


    Area toll
    In case of an area toll, a geographically contiguous part of the network is designated as a
    toll zone and a distance-independent charge applies if a portion of the route is located
    within the toll zone. In Visum, you can define such toll zones by inserting a polygon and
    specifying a toll for all associated chargeable links.
    The "Congestion Charge" in London is an example of an area toll. In the city center, a toll
    is charged as soon as the specified area is entered.

    Illustration 34: The Congestion Charge in London is an area toll


    Matrix toll
    This type of toll model is the typical road pricing scheme for motorway corridors. A subset
    of links is designated as a toll zone with a small number of connections (entries and exits)
    to the rest of the network. Toll prices are not defined as a total of link toll prices, but there
    is an individual price for each pair (entry exit). Because of these pairs, this type of road
    pricing scheme is called a matrix toll. Toll typically increases with distance but in a degressive way, i.e. the toll per km decreases with distance.

    3.1.19

    GIS objects
    GIS objects are POI-like network objects (n categories with m objects of the type point, polyline
    or polygon) that are only available during a Personal Geodatabase (PGD) connection (see
    "Connection to the Personal Geodatabase and GIS objects" on page 691). This is how GIS
    data can constantly be synchronized between the PGD and Visum.

    86

    PTVGROUP

    3.1.20 Screenlines

    3.1.20

    Screenlines
    A screenline is a polygon, which can be inserted into the network by the user with any number
    of intermediate points. The screenline is inserted so that it intersects multiple links. The values
    of any attributes of all links, which are intersected by the screenline, can then be aggregated
    with the screenline. The following aggregate functions are thus available respectively for all or
    only for the active links (see "Indirect attributes" on page 104).
    Number of links which intersect the screenline.
    Minimum of the values of the selected attribute from all links intersected by the screenline.
    Maximum of the values of the selected attribute from all links intersected by the screenline.
    Sum of the values of the selected attribute from all links intersected by the screenline.
    Mean of the values of the selected attribute from all links intersected by the screenline.
    Interlinking of the values of the selected attribute from all links intersected by the screenline.
    The orientation of a screenline depends on the sequence of the polygon points along its
    course. It is always oriented to the right in the direction of creating. By default, arrow heads
    along the course indicate the orientation. For the aggregation, you can take into account all
    links in screenline orientation, all links against the screenline orientation, or all links, independently of the direction.
    In the following example, the screenline intersects two links whose volume amounts to 1,000
    and 3,000 persons. The screenline then aggregates the values of the links that it intersects. In
    the example it identifies a total of 4,000 persons in screenline orientation for all links and an
    average of 2,000 persons.

    Illustration 35: Summation and average calculations with screenlines


    With the aid of screenlines, you can for example determine the traffic that enters and exits the
    downtown area every day in a traffic engineering study which analyses the traffic volume of a

    PTVGROUP

    87

    3.1.21 Junction modeling


    downtown area. In illustration 36, 149,334 vehicles in PrT and 76,370 persons in PuT are entering the downtown area.

    Illustration 36: Calculation of the urban traffic volume with screenlines


    Screenlines are a useful construction to calibrate an assignment model by means of counted
    link data. A screenline aggregates all links intersecting it. This is useful for the calibration of
    the model as cumulative assignment volumes can be compared with cumulative link count
    data. When inserting screenlines, it is often recommended to adjust them to natural phenomena. A screenline could, for example, take the course of a river. For the calibration of the
    model, in principle, at least the sums of the volumes on all bridges should then agree throughout the day, even if the distribution of the volumes to the individual bridges (route split) can differ. With the aid of the assignment analysis, you can evaluate aggregated count data and
    assigned volumes of the screenline statistically (see User Manual: Chpt. 17.4.2 , page 1879).
    With this analysis functionality, the efficiency of the calibration can be increased considerably.

    3.1.21

    Junction modeling
    Visum provides the possibility to model junctions in detail. There are two major fields of application, namely the use of a detailed node impedance model among others in assignment procedures, and the export for a micro-simulation in Vissim.

    88

    PTVGROUP

    3.1.21.1 Link orientations


    Element

    Description

    Geometry

    Geometries are used to describe the geometry of nodes and main


    nodes in detail. The principal elements of geometries are legs.

    Leg

    A leg geometry consists of a set of legs. A leg describes an entry to


    the node section and the corresponding exit. A set of legs at a node
    or main node is defined by the set of link orientations.

    Lanes

    A leg consists of a set of incoming and outgoing lanes. Through


    lanes are the ones that lead right up to the adjacent node and
    pocket lanes start and end at a certain distance from the node area.

    Lane turn

    Lane turns define a relation between an incoming lane and an outgoing lane. They are used for detailed transport system and lanebased descriptions of the turn conditions at a node.

    Signal control

    A signal control describes the total of all signal control data at one or
    more nodes or main nodes. There are stage based and signal group
    based signal controls, as well as external signal controls of the type
    RBC.

    Stage

    A stage is the basic unit of a signal plan in case of stage-based


    signal controls. A set of signal groups is allocated to each stage.
    Then the green times of the signal group result from the green times
    of the stages.

    Signal group

    A signal control contains a set of signal groups, even if it is stagebased. Signal groups serve to describe lane turn-based signal controls in detail.

    Crosswalk

    Crosswalks serve to describe the pedestrian conditions at nodes


    and main nodes. They refer to legs. A leg can have several crosswalks depending on whether a center island or a channelized island
    has been defined.

    Detector

    A detector is allocated to a node or a main node. This type of detector serves for modeling signal control, for example, traffic-responsive
    signal control.
    Table 14: Network objects of the junction model
    3.1.21.1

    Link orientations
    Link orientations play an essential role when defining node geometries (see "Geometries" on
    page 90). The link orientations are used to determine the amount of legs. Each link has at
    least four orientation attributes: From and To node orientation, and From and To main node
    orientation. The two latter attributes are only defined for cordon links of a main node (see
    "Main nodes and main turns" on page 60). The orientations are always undefined for closed
    links. A link is closed, if its transport system set is empty or if the number of lanes is zero. If a
    link is not closed, it is an open link.
    Up to sixteen link orientations can be defined at a node or main node. If a node or main node
    has more than sixteen open incoming links or more than sixteen open outgoing links, all link

    PTVGROUP

    89

    3.1.21.2 Geometries
    orientations will be undefined. At such nodes, a geometry and thus a signal control cannot be
    defined.
    The allocation of link orientations complies with specific rules. If an incoming link and its opposite outgoing link are open, the To (Main) Node Orientation of the incoming link and the From
    (Main) Node Orientation of the outgoing link are identical. If there is an incoming link whose
    opposite direction is closed, you can allocate the same orientation to an outgoing link, as long
    as its opposite incoming link is also closed. You can also combine incoming one-way roads
    and outgoing one-way roads in one leg (see "Geometries" on page 90), if you give them the
    same orientation.
    Whether Visum calculates the link orientations automatically at a node or main node or not,
    depends on the attribute Use automatic link orientation. If the link orientations are calculated
    automatically, the type of calculation depends on the option set under Network > Network
    parameters > Network objects > Link orientations (see User Manual: Chpt. 15.14.4 , page
    1103). Normally, the value is set to 8. This means that Visum picks the best orientations from
    the four main directions (N, E, S, W) and the four secondary orientations (NE, SE, SW, NW).
    The entry angle of the link at the node or main node is decisive when selecting the orientation.
    If the orientations do not suffice i.e. the node or main node has more than eight legs Visum
    adds the subordinated secondary orientations (e.g. NNE).
    Notes: In Visum versions prior to 11.5, this setting did not exist for the calculation. Visum
    used to implicitly calculate with today's setting 4. This means that Visum first tried to allocate only the main orientations, and only switched to the secondary orientations in case
    of nodes with more than four legs. The subordinated secondary orientations were not
    used in earlier Visum versions.
    Please note that you can define varying numbers of legs at a node or main node, depending on the number of pairs of incoming and outgoing one-way roads that are given the
    same orientation.
    3.1.21.2

    Geometries
    In macroscopic traffic models, an at-grade junction is represented by a node (point object) with
    turns. Macroscopic modeling, however, does not reveal anything on the detailed geometry or
    the geometric design of a junction. Nearly the same applies to the node control. The optional
    extension of the Visum network model by node geometry and junction control can be used in
    the following fields:
    Calculating the performance at a node
    Considering node impedances during assignment
    Providing entire junctions for the microscopic model Vissim
    A node geometry consists of the items node legs, lanes, lane turns, detectors, and crosswalks.
    If a signal control is allocated to a node, its data refer to the node geometry. By default, no geometry data are provided at a node. These are generated not until the first access.
    Legs
    The principal elements of the geometry are the legs. A node/main node can have up to sixteen
    legs. The set of legs is determined by the orientations of the incoming and outgoing links (see

    90

    PTVGROUP

    3.1.21.2 Geometries
    "Network objects of the junction model" on page 89). For each used link orientation, exactly
    one leg is generated. Legs can thus either consist of an incoming link and its opposite direction, or of an incoming one-way road and an outgoing one-way road.
    Legs can have a center island, a channelized island, or both. For a center island to exist, the
    center island length and width both need to have a value > zero. For a channelized island to
    exist, the channelized island length needs to be > zero. The Stop line position attribute is only
    used for the export to Vissim. Legs also possess a set of lanes.
    Lanes
    There are incoming lanes and outgoing lanes, as well as through lanes and pockets. The number of through lanes at a leg cannot be changed. It is based on the set number of lanes at the
    links which underlie the leg. Therefore, if the incoming link of the leg has three lanes (Number
    of lanes attribute on the link) and at least one transport system, the leg features three incoming through lanes. If the number of lanes at this link is changed, the number of through lanes
    at the leg will be adjusted automatically. We recommend double-checking the adjusted geometry data after such modifications. Since at least one open link underlies each leg, each leg
    features at least one through lane.
    The number of lanes at a leg can be changed by creating pocket lanes (pockets). Pocket lanes
    always refer to a through lane on which they originate (origin lane). In contrast to through
    lanes, pockets can be removed again. For pockets, a length can be specified. This is used
    during Vissim exports and for specific methods of impedance calculations at nodes.
    By default, the transport system set permitted on a lane corresponds to the transport system
    set of the underlying link. For pockets, the transport system set of the origin lane is used by
    default.
    Note: The numbering of the lanes differs from the one in Vissim.
    Lane turn
    A lane turn connects an incoming lane with an outgoing lane. When generating a geometry
    automatically, a set of lane turns is also generated automatically. In order to define a lane turn,
    the turn or main turn between the link underlying the incoming lane and the link underlying the
    outgoing lane must be open. This means that it needs to have at least one transport system.
    It is usually not desired that lane turns intersect. Two lane turns, for example, intersect if one of
    them makes a left turn on a right lane and the other one goes straight on a left lane. This is yet
    possible and desired, if the left turn is a PrT turn and the other one a PuT turn. In this way, a
    tram can, for example, be modeled in central position.
    The set of lane turns basically determines the results of the node impedance calculations at a
    node/main node.
    Crosswalks
    Crosswalks are objects that connect the sides or the islands of a leg per direction. Depending
    on the combination of islands at a leg, you can define up to six crosswalks. If the node leg e.g.
    has a center island (i.e. its center island length and width are both > zero) and a channelized
    turn, six crosswalks can be defined: One between a side and the center island, one between
    PTVGROUP

    91

    3.1.21.3 Signal control


    the center island and the channelized island, one between the channelized island and the
    other side, and one each in the opposite direction.
    Crosswalks are exported to Vissim. For crosswalks, a pedestrian volume can be specified.
    This is relevant when calculating the node impedance using ICA (see "Intersection Capacity
    Analysis according to the Highway Capacity Manual (ICA)" on page 244).
    Leg templates and geometry templates
    In order to ease the input, leg templates can be used for legs. With the aid of leg templates, a
    set of predefined lanes, lane turns, and crosswalks are generated at a leg. Contrary to earlier
    program versions, the object's reference to the template is not kept when using leg and geometry templates. Previously, legs could not be edited, if they were allocated a template. Now,
    templates are used exclusively to define leg and node geometries.
    For the generation of leg templates, existing legs are used. The attribute values of the leg are
    transferred to the template. They can, however, be edited later on. A leg template consists of
    lane templates. If a leg template is generated from a leg, the lanes of the leg are used as a
    model for the lane templates. The lane templates can also be edited later on.
    Leg templates can only be used at geometries of 3 or 4 legs. The data must match so that a
    leg template can be used at a leg. If a template is suitable for nodes with three legs, it can thus
    not be used for legs at nodes with four legs. The number of incoming and outgoing lanes of
    the leg and of the template must also be identical.
    Contrary to leg templates, geometry templates can be applied to all legs of the node. They can
    also be used exclusively at nodes with 3 or 4 legs. A geometry template is made up of several
    leg templates. When using a geometry template, the leg templates are applied to the legs of
    the node. To determine which leg template is to be used at which leg, a reference leg must be
    specified for the template. Geometry templates can only be used, if at least one valid reference
    leg exists, so that all leg templates can be used in the right order for all legs at the node.
    3.1.21.3

    Signal control
    Signal controls (SCs) can be allocated to nodes and main nodes. There are four types of
    signal controls: signal group based, phase based, RBCs (ring-barrier controller), and external
    signal controls (Vissig). In case of signal-group SCs, signal groups can be defined immediately. In case of stage-based SCs, stages must be defined first, and after that, signal groups can
    be allocated to the stages. Vissig controls are managed with an external program (see "External controls" on page 94).
    Note: For further information please refer on RBCs, please refer to the RBC manual in
    the Doc\Eng folder of your Visum installation directory.
    Signal controls can be switched off. In this case, nodes and main nodes for which the signal
    controls have been switched off are treated as two-way stop nodes in procedures such as ICA
    and signal time optimization. So switching off a signal control will change the node control
    type.

    92

    PTVGROUP

    3.1.21.3 Signal control


    Note: An SC can be allocated to multiple nodes or main nodes. However, we only recommend to do so for Vissig controls, as the procedure Signal cycle and split optimization
    only delivers good results for multiple nodes and main nodes in combination with Vissig
    controls. The number of the coordination group of the SC plays a role in the Optimization
    of the SC offset operation (see User Manual: Chpt. 15.40.14.1 , page 1497).
    The key attributes of a signal group are its Green time start and its Green time end. These
    attributes are relevant to the node impedance calculation (see "Signalized nodes" on page
    246). In external controls signal groups can have two pairs of green time start and green time
    end. Thus, you can model a second green time, represent it correctly in the signal time display
    of the network editor and take it into account in the node impedance calculation. In case of
    stage-based SCs, green time start and green time end of a signal group correspond to the
    green time start and green time end of its stage. If for a signal group or stage, the Green time
    start attribute is 0 and the Green time end attribute is identical with the SC cycle time, this is
    interpreted as permanent green. Both attributes are restricted by the cycle time of the SC. The
    Green time end can have a smaller value than the Green time start. In this case, the green
    time is calculated by subtracting the difference of both values from the SC cycle time. The
    green time cannot fall below the minimum green time of a signal group.
    Signal groups also have the attributes Amber and Allred. Furthermore, intergreens can be
    defined between signal groups. All of these values are important when calculating the signal
    cycle and split optimization. Hereby, the Used intergreen method attribute of the signal control determines whether the amber and all-red time or the intergreen matrix is used for optimization. The ICA loss time adjustment attribute is used in the calculation of the impedances
    with ICA to determine the effective green times with the aid of the specified green times. The
    Minimum green time attribute is used for signal cycle and split optimization, serving as a low
    threshold value for the green time calculated. The Vissim coordinated attribute is only relevant for the Vissim export.
    The relation between the signal control and the network is established when allocating the
    signal groups to lane turns. Each signal group can be allocated to any number of lane turns.
    Prerequisite is, that the lane turns are located at nodes or main nodes which are allocated to
    the SC of the signal group. Likewise, any number of signal groups of the SC can be allocated
    to each lane turn that is allocated to the node or main node of the lane turn. A signal group can
    also be allocated to any number of crosswalks. A crosswalk, however, can only refer to one
    signal group. The data model is not restricted here. As an example, Visum does not check whether a signal group is allocated to each lane turn. It does not check either whether conflicting
    volumes have overlapping green times. Should the signal control be used to determine node
    impedances, it is recommended to carry out the respective ICA network check option to detect
    incomplete junction models (see User Manual: Chpt. 15.41 , page 1504).
    Note: It is recommended to complete the modeling of a node or main node, before allocating signal groups to lane turns. When deleting or inserting lane turns, the signal control data can get lost.

    PTVGROUP

    93

    3.1.22 Network check


    External controls
    A special feature of external SCs is that the data are not saved in the version file. Vissig control
    files are saved in the *.sig format. This way, they can also be accessed by other programs, for
    example Vissim. To edit external control data in Visum, you use the Vissig program. In external
    controls, multiple signal programs can be stored. This is not the case for signal group based or
    stage based controls. Therefore, the SC attribute Signal program number is only relevant
    when dealing with external controls. Visum accesses the data saved in the control file at certain times. This is, for example, the case when opening a version file or when running the operations Signal cycle and split optimization and Update impedances at node via ICA.
    Note: Up to Visum 12, RBCs belonged to the external controls. Now RBC files in the *.rbc
    format are still read in, but are no longer used.
    Stage templates
    Stage templates can be used to easily generate signal control data at a node or main node
    (see User Manual: Chpt. 15.40.13.3 , page 1492). If a stage template is allocated to a node,
    the SC of the node then possesses a lot of stages and signal groups. Lane turns are already
    allocated to the signal groups. This means, for example, that conflicting volumes are signalized with different green times.
    Note: Prerequisite for the use of a stage template is, however, that a stage-based SC is
    already allocated to the node or main node.

    3.1.22

    Network check
    Visum supports the user when checking the consistence of the network model. If the network,
    for example, contains zones which are not connected to the rest of the network, this indicates a
    modeling error. To identify such errors, several tests are provided (see User Manual: Chpt.
    15.41 , page 1504).

    3.2

    Spatial and temporal correlations in Visum


    In Visum, the following can be specified:
    Calendar
    Valid days
    Time series
    Analysis time slots

    3.2.1

    Calendar and valid days


    You can specify a calendar and valid days for your network.

    3.2.1.1

    94

    Calendar
    With the aid of the calendar, the modeling of transport supply (in PuT and for the DUE procedure in PrT) and demand (for the dynamic procedures of PrT and the headway-based and
    timetable-based assignments of PuT) can be refined considerably. It is not only possible to
    model any day, but also to manage any combination of weekdays or individual days. The

    PTVGROUP

    3.2.1.2 Valid days


    calendar is global, i.e. only one of the following three calendar options can be applied to the
    entire model. Use of the calendar is optional. The following options can be selected for a network model:
    No calendar
    The transport options for one day are indicated. The analysis period is thus automatically one day and cannot be edited by the user.
    Weekly calendar
    The demand (for the dynamic procedures of the PrT and for the headway-based and
    timetable-based procedures of the PuT) and the PuT supply can be differentiated for
    the individual weekdays Monday to Sunday. It is possible to specify for each vehicle
    journey section weekdays on which there will be a service. The analysis period can be
    any time period of entire days within the week (such as Monday to Friday).
    Annual calendar
    Valid days can be defined for any day of the year. The analysis period can be set to
    any time period (in entire days) within the calendar period (e.g. 14th July 2008 to 20th
    July 2008).
    The calendar takes effect in the following procedures (all other procedures are not affected):
    Dynamic assignment in PrT
    In the Dynamic stochastic assignment and DUE, traffic supply can be time-varying.
    Time-varying attributes are used (see "Time-varying attributes" on page 114). When
    using a calendar, valid days can be specified for these time-varying attributes, on
    which they should take effect.
    Assignments in PuT
    Valid days are allocated to and affect single vehicle journey sections.
    PuT analysis (operation PuT operational indicators)
    PuT passenger survey
    3.2.1.2

    Valid days
    Valid days are closely linked to the calendar as they can be specified on the basis of the selected calendar. First the kind of calendar is thus chosen when modeling, and then valid days are
    specified on the basis of the respective calendar.
    Valid day is a freely definable set of days of the calendar used. If a weekly calendar is used, a
    valid day may comprise the days Monday to Friday, for example (the valid day then is designated Mondays to Fridays).
    In PuT the timetable is based on a calendar (see "Calendar" on page 94). A valid day can be
    assigned to each vehicle journey section. Optionally, this can consist of an individual day or
    an example week, however, a defined period on the calendar can also be used. In each case,
    the availability of individual vehicle journey sections can be specified by valid days. A valid
    day is a freely definable set of days of the underlying calendar. For each valid day a separate
    name can be allocated. Valid days usually represent regularly recurring patterns, such as Monday to Friday, but these could also be individual days (for example 01.01.2009). How to define
    a valid day depends of the selected calendar:
    No calendar
    Exclusively uses the valid day daily. It is not possible to create further valid days. Demand

    PTVGROUP

    95

    3.2.2 Time reference of the demand (time series)


    and supply are modeled for an unspecified, recurring day in this case.
    Weekly calendar
    Apart from the predefined valid day daily any desired valid days can be created, which
    are specified by entering one or several valid weekdays (e.g. all weekdays with the valid
    day name Mon-Fri).
    Annual calendar
    Valid days can be defined for any day of the year within the calendar period. The following possibilities are provided:
    fixed time period (e.g. 01.01.2008 to 30.06.2008)
    weekdays (e.g. Mon-Fri)
    hard rule (for example during the summer holidays)
    free selection of calendar days (for example 24.12.2007 and 31.12.2007)
    Valid days play a minor part in PrT. Valid days can be used in the following assignment procedures:
    Dynamic stochastic assignment (see "Dynamic stochastic assignment" on page 439)
    Dynamic User Equilibrium (DUE) (see "Dynamic User Equilibrium (DUE)" on page 410)
    Tip: In these procedures, the transport supply can be time-varying. Time-varying attributes are used (see "Time-varying attributes" on page 114). When using a calendar,
    valid days can be specified for these time-varying attributes, on which they should have
    an effect.

    3.2.2

    Time reference of the demand (time series)


    Just like the transport supply and the assignment, any demand has a time reference.
    In statistic PrT assignments, the demand always refers to the analysis period. The demand
    time series allocated to the demand segment and the start time are irrelevant here.
    This is different in the dynamic PrT assignments (DUE and Dynamic Stochastic assignment)
    and the headway-based and timetable-based assignment in PuT. Demand matrices do not
    have an explicit time reference here, but are described by a start time and a time series.
    Note: A time series must be allocated to the demand segments in order to calculate an
    assignment with these procedures.
    The start time specifies the time and if the weekly or annual calendar is used - the day on
    which the period referred to by the demand in the matrix starts. The end of the period is calculated from the length of the assigned time series.
    In Visum, there are two different ways to define so-called standard time series:
    For time series as percentages a weight is specified for each time interval. It specifies
    which share of the total demand accounts for the respective time interval. If a time
    series as percentages is used for a demand segment, a demand matrix must also be
    specified, whose demand is distributed temporarily with the specified weights. This
    matrix must contain the number of travel demands in the time period, defined by the
    starting time and the length of the time series.

    96

    PTVGROUP

    3.2.2 Time reference of the demand (time series)

    Illustration 37: Time series by percentage


    However, for time series of matrix numbers for each time interval a separate demand
    matrix is specified. It contains the travel demands of this time interval only.

    Illustration 38: Time series of matrix numbers


    Note: When using time series of matrix numbers, it is possible to specify a value for the
    demand for each OD relation and time interval. This way, asymmetric changes of the
    demand (load direction) can be illustrated. For time series as percentages however, the
    same factor applies to each OD relation per time interval.
    Time series of matrix numbers require a full matrix for each time interval, which must be generated and also saved. In order to save the effort and still be able to model a certain load direction in the demand, Visum provides demand time series as a compromise. These are
    generated on the basis of a standard time series, whereas a different standard time series can
    be specified for each pair of zone types. In this way, it is possible to specify deviating time
    series for selected pairs of origin and destination zones with known structural features (for
    example purely residential or commercial areas).
    For each demand segment, either a fixed demand matrix together with a time series as percentages is specified, or a demand time series which itself is a time series of matrices. Moreover, a start day and the start time per demand segment must be specified.

    PTVGROUP

    97

    3.2.3 Time reference of the volumes: Analysis time slots and projection
    Note: The start time shifts the time intervals of the time series since it is specified relative
    to this start time point. If the time series defines an interval A from 0 am to 1 am and an
    interval B from 1 am to 2 am, and the start time is set to day 2 at 2 pm, the share of the
    demand defined in interval A will arise on day 2 from 2 pm to 3pm, and the share of interval B on day 2 from 3 pm to 4 pm. Outside of these times, for example on the first day of
    the calendar, there is no demand.

    3.2.3

    Time reference of the volumes: Analysis time slots and projection


    Volumes always have at least an implicit time reference which they get from the time reference
    of the demand (if the demand matrix contains the demand of the peak traffic hour for example,
    the assignment results will also refer to the peak hour). To apply the resulting volumes to a shared time unit and then project them evenly to longer temporal horizons, the following analysis
    time slots are provided in Visum.
    The calendar period covers the set calendar, i.e. one, seven or any number of days.
    The Time reference of the demand determines the number of travel demands within the
    assignment time interval. The time reference is established by the start time of the
    demand segment and the time series allocated to the demand segment (see User
    Manual: Chpt. 16.1 , page 1606).
    The assignment time interval mainly serves to determine the share of the demand that
    needs to be assigned. It is crucial that the assignment time interval of each assignment
    lies within the analysis time period. In the assignment, the share of the demand that
    accounts for the assignment time interval according to the time series is assigned to the
    paths found in this time period. The assignment area and the demand time series need to
    overlap, since otherwise no demand exists within this time period and no assignment can
    be calculated. An assignment time interval can only be specified for dynamic assignments
    (DUE, Dynamic Stochastic assignment) of the PrT and for the headway-based and timetable-based assignment of the PuT. The assignment time interval is specified in the parameters of the assignment procedure. In all statistic PrT assignments (Equilibrium
    assignment, Incremental procedure, Equilibrium_Lohse, Stochastic assignment, Tribut),
    the assignment time interval automatically corresponds to the analysis period.
    The analysis period (AP) represents the period on which all evaluations are based. If no
    calendar is used, the analysis period is one day. If a weekly or annual calendar is used,
    the analysis period is specified in the procedure parameters. Theanalysis period is a time
    period between at least one day and a maximum of the whole calendar period Initially, calculated results are available for the analysis period, before they are converted into analysis time intervals or the analysis horizon. The analysis period must be within the
    calendar period. The assignment intervals must lie completely within the analysis period.
    For the analysis period projection factors can be specified at the demand segments,
    which project the assignment results from the assignment time interval to the analysis
    period. They serve to scale the demand to the analysis period. If the time period of the
    demand matrix is identical to the analysis period, the projection factor is 1. If the demand
    matrix is based on one day, yet the analysis period on a week, the factor would have to be
    set to 7 (when assuming that the traffic is the same on all 7 days of the week).
    The analysis horizon (AH) is a longer time period on which the results can be projected.
    It is not specified explicitly. Instead, the projection factors on the analysis horizon are

    98

    PTVGROUP

    3.2.3 Time reference of the volumes: Analysis time slots and projection
    predefined. These can be specified at the demand segment (for the volumes) and at the
    valid day (for the operator model) (see "Basic calculation principles for indicators" on
    page 669). As a rule, an analysis horizon of a year is regarded. Since a different projection factor can be specified for each demand segment, the projection factor of daily
    values to a year can for example be smaller for a demand segment Pupils than for a
    demand segment Commuters, as the pupils have more vacation days on which they do
    not generate any traffic. The volume of a network object in terms of the analysis period is
    the total of the volumes of all paths traversing the network object, multiplied by the projection factor of the demand segment. This projection factor compensates that the assignment time interval may cover only a part of the analysis period.
    Analysis time interval (AI)
    For a more refined temporal evaluation of calculated results, analysis time intervals can
    be defined (see "Temporal distinction with analysis time intervals" on page 102). Each
    analysis time interval needs to lie completely within a calendar day of the analysis period.
    Note: Contrary to the analysis period, which incorporates the assignment time interval
    and thus requires a projection of the volumes, the analysis time intervals identify the
    exact volume which arises in the respective time period. Thus, the projection factors of
    the individual demand segments do not have an effect on the volume per analysis time
    interval. If the analysis period is completely covered by analysis time intervals, the relationship between the total volumes for the intervals and the volume related to the analysis period exactly corresponds to the projection factor.

    Illustration 39: The relationship between the different analysis time slots
    Example of projection factors
    Volumes are to be determined per week in a model with a weekly calendar. To reduce the run
    time of an assignment procedure, the entire week should not be used as an assignment time
    interval. It is assumed that the demand and the supply of week days Monday to Friday are the
    same. Demand data are available for the standard working day, Saturday and Sunday.
    This is solved in the following way. Three demand segments are set, which each represent the
    demand on the working day, Saturday and Sunday. Each demand segment is provided with
    an appropriate time series, whereas the standard working day has to be one of the days
    PTVGROUP

    99

    3.2.3 Time reference of the volumes: Analysis time slots and projection
    Monday to Friday. Three assignments are calculated. The assignment time interval is only one
    day, namely Tuesday (representing the standard working day), Saturday and Sunday.
    A week is set for the analysis period and a year for the analysis horizon. The following projection factors are used, to correctly project the volumes.
    Demand segment

    Projection factor AP

    Standard working day

    Projection factor AH

    Saturday

    52

    Sunday

    52

    Table 15: Deriving projection factors for AP and AH


    Example of the interaction of analysis time intervals and time series
    To calculate an assignment, the assignment time interval and the time, which is valid for the
    demand, have to overlap. Three examples are shown below. In the first case (illustration 40),
    the demand and assignment intervals do not match and the assignment cannot be calculated.
    Visum then issues the error message No OD pair shows demand > 0 within assignment time
    interval. No connections calculated. In the second (illustration 41) and third example (illustration 42) assignment time interval and validity period of the demand overlap so that an assignment can be calculated. The illustration 40 provides an overview on analysis time intervals
    and time series of the three examples.
    Calendar

    Analysis
    period

    DSeg
    start
    day

    DSeg
    start
    time

    Standard
    time
    series
    from

    Standard
    time
    series
    to

    Assignment
    can be calculated

    Ex. 1

    Weekly Mon 06:30- Moncalendar 07:30 a.m. Mon

    Mon

    01:00:0- 00:00:00 02:00:00


    0

    No

    Ex. 2

    Weekly Mon 06:30- Moncalendar 07:30 a.m. Mon

    Mon

    05:30:0- 00:00:00 02:00:00


    0

    Yes

    Weekly Mon 06:30- MonMon


    00:00:0- 05:30:00 07:30:00
    calendar 07:30 a.m. Mon
    0
    a.m.
    Table 16: Example of the interaction of analysis time intervals and time series

    Yes

    Ex. 3

    100

    Assignment
    time interval

    PTVGROUP

    3.2.4 Temporal and spatial differentiation of calculation results

    Illustration 40: Assignment not possible because the validity of the demand and the assignment time interval do not overlap.

    Illustration 41: The demand between 6:30 and 7:30 a.m. is assigned.

    Illustration 42: The demand between 6:30 and 7:30 a.m. is assigned.

    3.2.4

    Temporal and spatial differentiation of calculation results


    The results of the impact models, after the completion of the calculation, are available as a
    large number of attributes, some of which refer to the routes or connections found in the assignment procedures, while the majority refers to the network objects (links, nodes, turns) and

    PTVGROUP

    101

    3.2.4.1 Temporal distinction with analysis time intervals


    all objects of the PuT network model (see "Impact models" on page 220). In addition to structuring the content, many attributes can additionally be differentiated by space, by modeling territories (territorial section) or by time, by creating analysis time slots (time section).
    An extremely high level of model detail can be achieved with a combination of temporal and
    spatial distinctions. Passenger kilometers, costs, and revenue, for example, can be displayed
    for vehicle journeys run by a specific line using low-floor buses between 6:00 and 7:00 a.m. in
    the community territory.
    3.2.4.1

    Temporal distinction with analysis time intervals


    If a period which is shorter than the analysis period shall be analyzed for the temporal differentiation of calculation results, several analysis time intervals can be specified (see User
    Manual: Chpt. 17.2.2 , page 1861). The analysis time intervals must lie within the analysis
    period. They have to neither be consecutive nor of the same length. The analysis time period,
    must however, be within a day, is therefore not allowed to contain a day changeover. Provided
    that attributes can be assigned on a time basis, the portion assigned to each defined analysis
    time interval can be identified separately.
    In addition, you can show aggregated data across multiple analysis time intervals. To do so,
    you can create additional analysis time intervals, assign them existing time intervals, and specify an aggregation function. Using these time intervals, you can output data for more than a
    day.
    In PrT, evaluations broken down by time slices can only be made for the dynamic assignment
    DUE and the dynamic stochastic assignment (see "Dynamic User Equilibrium (DUE)" on page
    410 and "Dynamic stochastic assignment" on page 439). The reason is that only in those assignments, the traffic demand can be time-varying. Therefore, evaluations for analysis time intervals within the analysis period can only be made in the course of these procedures. The link
    volume of the rush-hour traffic from 7 to 9 am can thus for example be evaluated separately.
    In PuT, evaluations broken down to time slices are only possible for the timetable-based assignment procedure. In the timetable-based assignment procedure however, there are no
    connections that are fixed in time, so that it is not possible to apply assignment results to a specific analysis time interval.

    3.2.4.2

    Spatial distinction with territories


    For spatial distinctions, the user initially defines territories (see "Territories" on page 63).
    These are network objects, which are only relevant for analysis purposes and possess a polygon (boundary) as the most important feature. Provided that attributes such as the passenger
    kilometers of a line can be spatially localized, the share assigned to each territory can be identified separately. Thus all passenger kilometers will be calculated, which arise within the territory polygon. To calculate such an evaluation, the Territory indicators procedure must be
    run (see User Manual: Chpt. 17.4.3 , page 1885). The results can be displayed in the list
    Territories> Basis (see User Manual: Chpt. 24.1.10 , page 2321) and are also available in
    the filters and in the graphic parameters in the form of territory attributes.
    In PuT even more detailed evaluations can be carried out (see "Operator model PuT" on page
    541). Here you can even calculate indicators for combinations of territories, objects of the line
    hierarchy (transport system, main line, line, line route, time profile, vehicle journey) and as an

    102

    PTVGROUP

    3.2.5 Adjustment of the capacities to the demand values


    option, vehicle combinations. You can thus for example calculate the number of service kilometers traveled by the vehicle combination tram on line 2 in the urban area. Here, an additional distinction can be made for most of the indicators on a temporal basis. You would thus
    get just the service kilometers between 5 and 6 pm for example. Use the procedure PuT Operating Indicators to carry out such an evaluation (see User Manual: Chpt. 20.3.1 , page 2156).
    The results can be displayed in the Territories> PuT detail list (see User Manual: Chpt.
    24.1.10 , page 2321).

    3.2.5

    Adjustment of the capacities to the demand values


    Please note that the link and turn capacities can have different units depending on the selected assignment procedure. While in statistic assignments of the PrT (such as the Equilibrium
    assignment) the link capacity is, for example, entered in car units per analysis period
    (PCU/AP), in the dynamic DUE procedure, the link capacity is interpreted in car units per hour
    (PCU/h). Although the Capacity attribute is attributed identically at the link, its unit is interpreted differently depending on the assignment procedure that is used.
    Furthermore, the units in which link and turn capacities are modeled always need to match the
    units of the demand matrix. It is thus not allowed to manage link capacity values in unit PCU/h
    and assign a demand matrix in the same model which contains values for the whole day.
    More detailed information on which units are used for capacity and demand in the individual
    procedures will be given in the section on input and output attributes of each assignment procedure (see "User model PrT" on page 226).

    3.3

    Attributes
    In Visum, network objects have many attributes you can save your input or output data to.
    Generally, there are two types of attributes:
    Direct attributes
    Indirect attributes
    Direct attributes contain data that refer directly to a network object, e.g. the length or volume of
    a link (see "Direct attributes" on page 103).
    Indirect attributes refer to the relations between one network object and other network objects.
    E.g. the sum of volumes of all outgoing links is an indirect attribute of a node (see "Indirect attributes" on page 104).
    The number of attributes available in Visum is not static, but can be extended by user-defined
    attributes (see "User-defined attributes" on page 110).
    Time-varying attributes play a special role in dynamic assignments (see "Time-varying attributes" on page 114).

    3.3.1

    Direct attributes
    Each network object is described by means of Visum attributes (direct attributes). The following types are differentiated as follows:

    PTVGROUP

    103

    3.3.2 Indirect attributes


    Input attributes (e.g. stop number) and
    calculated attributes, which are also called output attributes (for example, the number of
    Passengers boarding at a stop)
    Each Visum attribute is described as follows:
    by a name (for example Number)
    by a code (for example No.)
    by an attribute identifier (attribute ID), which is always in English (for example No)
    Note: The Attribute.xls file in the Doc folder of your Visum installation contains a complete
    list of all types of Visum network objects (which in connection with databases are also called tables) and of all attributes of each network object. There, you find the ID of each attribute, by which it can be identified clearly, its name and code as well as the description of
    what each attribute indicates.
    The table 17 shows an example of some input and output attributes of the link.
    Attribute

    Input attribute

    Number

    TSysSet

    Capacity PrT

    Number of lanes

    Calculated attribute

    t0-PrTSys

    tCur-PrTSys

    Capacity PrT [Veh]

    Saturation PuT seats

    Passenger kilometers

    Table 17: Examples of input and output attributes at the link


    Apart from predefined Visum attributes, for each network object type, user-defined attributes
    (see "User-defined attributes" on page 110) can be created and edited. They are also direct
    attributes of the respective network object type and can be edited, saved, displayed graphically and in tables like Visum attributes.
    In addition, for some network object types, it is possible to overwrite defined attribute values
    with other values for a limited time (see "Time-varying attributes" on page 114).

    3.3.2

    Indirect attributes
    Besides the direct attributes of the currently selected network object, you can also access its
    indirect attributes. These are direct objects of other network object types that are network
    model-related to the selected object. Therefore, for a network object, both the direct attributes
    as well as its relations to other network objects can be selected.
    Indirect attributes give access to properties of other network objects, which bear a logical relation to the base object. It is often convenient to filter network objects not only by their own

    104

    PTVGROUP

    3.3.2 Indirect attributes


    properties, but also by the properties of their logical neighbors in the network, or to display
    these properties next to their own properties in listings or graphics (for example displaying the
    aggregated values of the attributes of all stop points, which belong to a stop, in a list).
    Relations between network object types are displayed explicitly in the user interface and allow
    access to all attributes of the referenced network object types (e.g. Link From node Outgoing Links). The three existing kinds of relations between the currently selected network
    object type and other network object types are indicated as follows.
    exactly one relation (1...1). Such a relation, for example, exists between connector and
    zone: each connector connects exactly one zone with the connector node. In the example
    of table 18, for connectors, the indirect attribute Zone\Number of connectors is output.
    For each connector, you can thus see how many other connectors the zone of this connector has.

    Selection of the indirect attribute Zone\Num- The indirect attribute is displayed in the list
    ber of connectors in the attribute selection next to the direct attributes of the connector.
    window
    Table 18: Example of a 1..1 relation in the Visum network model
    either one or no relation (0..1). Such a relation, for example, exists between nodes and
    main nodes. A node can be allocated to a main node, but does not have to be. Besides,
    each node can be allocated to just one main node. As depicted in table 19, with the aid of
    indirect attributes you can see for each node to which main node it is allocated by selecting the name of the main node as indirect attribute (Main node\Name).

    Selection of the indirect attribute Main


    The indirect attribute is displayed in the list
    node\Name in the attribute selection winnext to the direct attributes of the node.
    dow
    Table 19: Example of a 0..1 relation in the Visum network model

    PTVGROUP

    105

    3.3.2 Indirect attributes


    several relations (0..n). Such a relation, for example, exists between stop areas and
    stop points. Since no 1:1 link exists between the network objects types in this case, you
    need to select an aggregate function which pools all related network objects (the aggregate function Sum for example ensures that all indirect attributes are allocated with the
    sum of, for example, all boarding passengers at all stop points that have a relation to the
    selected stop area). Below, an example is given for each of the aggregate functions provided in Visum.
    If a 0..n relation has been selected at the Visum interface, the aggregate functions of either all
    network objects or merely the active ones are displayed. Aggregate functions are not provided
    in case of 1..1 and 0..1 relations, as there is only one relation from the current network object
    to another network object in this case (just one link type is for example allocated to each link).
    For 0..n relations, the following aggregate functions are provided:
    Count and CountActive
    Determine the number of associated network objects. In table 20, the number of stop
    areas associated with a stop is determined.

    Selection of the indirect attribute


    The indirect attribute is displayed in the list
    Count:Stop areas in the attribute selection next to the direct attributes of the stop.
    window for stops
    Table 20: Example of a 0..n relation with aggregate function Count
    Min and MinActive
    Determine the minimum value of all associated network objects for the selected attribute. In table 4, the minimum number of boarding passengers at all stop points of the
    stop area is output.

    Selection of the indirect attribute Min:Stop

    106

    The indirect attribute is displayed in the list

    PTVGROUP

    3.3.2 Indirect attributes


    points\Passengers boarding(AP) in the
    next to the direct attributes of the stop area.
    attribute selection window
    Table 21: Example of a 0..n relation with aggregate function Min
    Max and MaxActive
    Determine the maximum value of all associated network objects for the selected attribute. The table 22 displays the maximum number of boarding passengers at all stop
    points of the stop area.

    Selection of the indirect attribute Max:Stop The indirect attribute is displayed in the list
    points\Passengers boarding(AP) in the
    next to the direct attributes of the stop area.
    attribute selection window
    Table 22: Example of a 0..n relation with aggregate function Max
    Sum and SumActive
    Determine the total of the values of all associated network objects for the selected attribute. The displays the total of boarding passengers at all stop points of the stop area.

    Selection of the indirect attribute Sum:Stop The indirect attribute is displayed in the list
    points\Passengers boarding(AP) in the
    next to the direct attributes of the stop area.
    attribute selection window
    Table 23: Example of a 0..n relation with aggregate function Sum
    Avg and AvgActive
    Determine the mean of the values of all associated network objects for the selected
    PTVGROUP

    107

    3.3.2 Indirect attributes


    attribute. The table 24 displays the average number of boarding passengers at all stop
    points of the stop area.

    Selection of the indirect attribute


    The indirect attribute is displayed in the list next
    Avg:Stop points\Passengers boarding to the direct attributes of the stop area.
    (AP) in the attribute selection window
    Table 24: Example of a 0..n relation with aggregate function Avg
    Concatenate and ConcatenateActive
    String all values of the associated network objects together for the selected attribute.
    The table 25 displays the number of boarding passengers at each stop point of the
    stop area. At the stop points of stop area 2012 for example, 545 and 1046 passengers
    board each.

    Selection of the indirect attribute ConThe indirect attribute is displayed in the list
    catenate:Stop points\Passengers boar- next to the direct attributes of the stop area.
    ding(AP) in the attribute selection window
    Table 25: Example of a 0..n relation with aggregate function Concatenate
    Histogram and HistogramActive
    Contrary to the aggregate function Concatenate, each occurring value is issued only

    108

    PTVGROUP

    3.3.2 Indirect attributes


    once along with the frequency of its occurrence. This display offers more clarity especially if the user wants to see which values occur at all and how many times. The table
    26 illustrates the difference between the Concatenate and the Histogram display.
    Here, for each line, the number of stop points of the associated line routes is displayed. For example, 13 line routes are allocated to line S4. Two of the line routes
    have 10 stop points, 4 line routes have 20 stop points, and 7 line routes have 21 stop
    points.

    Selection of the indirect attribute Histo- The indirect attribute is displayed in the list next to
    gram:Line routes\Number stop
    the direct attributes of the line.
    points in the attribute selection window
    Table 26: Example of a 0..n relation with aggregate function Histogram
    Distinct and DistinctActive
    Contrary to the aggregate function Histogram, each occurring value is issued only
    once regardless of the frequency of its occurrence. This display offers more clarity
    especially if the user wants to see which values occur at all. table 26 shows the difference between the Histogram display and the Distinct display. Here Capacity PrT of
    the entrance turns is displayed for each link.

    PTVGROUP

    109

    3.3.3 User-defined attributes

    Selection of the indirect attriThe indirect attribute is displayed in the list next to the
    bute Distinct:InTurns\Capacity direct attributes of the link.
    PrT in the attribute selection
    window
    Table 27: Example of a 0..n relation with aggregate function Distinct
    Indirect attributes can also be used as source attributes for operation Intersect and thus allow
    the combination of logical and geometric relations (see "Intersect" on page 696).

    3.3.3

    User-defined attributes
    For all network objects - just as in databases or other geographical information systems - you
    can define your own attributes in addition to the default input and output attributes in Visum.
    User-defined attributes can be edited and stored just like predefined Visum attributes.
    The following data can thus be included in the model.
    Structural data of traffic zones (such as the number of households or the number of workplaces), which serve as input data for demand modeling.

    110

    PTVGROUP

    3.3.3 User-defined attributes

    Illustration 43: Structural data of zones stored in user-defined attributes


    Count data of links over several years (e.g. DTV2005, DTV2006)

    PTVGROUP

    111

    3.3.3 User-defined attributes

    Illustration 44: Count data stored in user-defined link attributes


    Different categories of vehicle journeys
    User-defined attributes for storing calculation results from Multi-Edit operations (see User
    Manual: Chpt. 15.3 , page 983). The table 28 shows an example in which the line costs
    per kilometer of the link length are calculated with the aid of a formula and the result is
    saved in the user-defined attribute Cost_per_Km.
    Line name

    112

    Costs [CU]

    Line network length Cost_per_Km


    [km]
    [CU/km]

    001

    13,012.86

    22.94

    567.06

    002

    22,797.80

    36.02

    632.83

    003

    13,390.06

    14.60

    916.71

    004

    10,428.43

    19.99

    521.58

    005

    10,109.21

    17.87

    565.65

    006
    6,833.93
    23.03
    Table 28: Saving the cost per kilometer to a user-defined attribute

    296.65

    PTVGROUP

    3.3.3.1 Formula attributes


    Note: Use formula attributes if you want the attribute Cost_per_Km to be updated automatically when costs or link lengths change (see "Formula attributes" on page 113). Then
    you need not repeat the calculation procedure in order to update the attribute. Visum will
    automatically calculate the current values for you.
    Each user-defined attribute has one data type. The following data types can be selected.
    Bool (for example for a user-defined attribute "in scenario active", which can only be 0 or
    1)
    File (for example for a user-defined attribute at count locations which specifies which file
    contains further information on the count location)
    Formula (for automatic update of calculated attribute values) (see "Formula attributes" on
    page 113)
    Integer
    Precise duration
    Number with decimal places
    Kilometers
    Meters
    Long text
    Text
    Time period
    Time (for example 06:32:45)
    3.3.3.1

    Formula attributes
    User-defined attributes of the formula type largely differ from other user-defined attributes.
    They are not used to save data (they do not belong to the input attributes), but consist of an
    arithmetic expression that contains other attributes. This expression is created when you
    create the attribute, but can be changed later on.
    The advantage of using formula attributes is that Visum automatically recalculates the formula
    when one of the input values changes. Then your values are always up-to-date. Just as the
    other attributes, you can also use formula attributes to graphically display data, filter data or to
    perform analyses.
    Example
    For a PrT and PuT assignment, Visum calculates link volumes for PrT and PuT that are saved
    to the attributes volume PrT [Pers] and volume PuT [Pers]. When creating a formula attribute
    Advantage PrT = Volume PrT [Pers] - Volume PuT [Pers]
    , you have direct access to the difference between the two volumes. This difference is automatically updated if one of the input values changes.
    Formula attributes are always numerical. When creating a formula expression, you have the
    same options as for the procedure Edit attribute (see User Manual: Chpt. 15.3.8 , page 990):
    A formula is the sum of (a number of) subexpressions that each consist of attributes combined
    with a binary operator or a function. The operators and functions available are the four basic

    PTVGROUP

    113

    3.3.4 Time-varying attributes


    arithmetic operations, division in percent, raise to power, minimum and maximum. Each subexpression can be included, rounded, or truncated.
    There are no restrictions concerning the attributes you can use in a formula. You can use formula attributes within other formula attributes to form more complex expressions. You can also
    use brackets.
    Example
    Links formula attribute Detour = [LENGTH]-[LENGTHDIR]
    Links formula attribute Detour percentage = Percent([DETOUR],[LENGTHDIR])

    3.3.4

    Time-varying attributes
    The procedures DUE (see "Dynamic User Equilibrium (DUE)" on page 410) and dynamic stochastic assignment (see "Dynamic stochastic assignment" on page 439) allow you to model
    time-dependent transport supply. In Visum, time-varying attributes are used for this purpose.
    Time-varying attributes only affect these assignment procedures.
    Otherwise time-varying attributes override the valid value of an attribute with a deviating value
    for a certain amount of time. They can thus model, for example the impact of tidal flow lane allocation or transient road works.
    Time-dependent attributes can be assigned to the following network objects.
    Links
    Turns
    Main turns
    Node
    Main nodes
    For these network objects, only specific attributes can be time-varying, and the deviating value
    of the attributes is not relevant to all procedures. The table 29 gives an overview of which attributes can be time-varying in which assignment procedures. For details, please refer to the description of the dynamic stochastic assignment (see "Dynamic stochastic assignment" on page
    439) and DUE (see "Dynamic User Equilibrium (DUE)" on page 410).
    Network object

    Time-varying attribute

    Links

    Out capacity PrT


    Capacity PrT

    Dynamic Stochastic Assignment

    DUE

    X
    X

    Toll-PrTSys

    X
    X

    v0 PrT

    TSysSet

    AddValue 1-3
    AddValue-TSys

    114

    PTVGROUP

    3.3.4 Time-varying attributes


    Network object

    Time-varying attribute

    Turns

    Capacity PrT

    Dynamic Stochastic Assignment

    DUE

    ICA final capacity


    t0 PrT

    TSysSet

    AddValue 1-3
    Main turns

    Capacity PrT

    t0 PrT

    TSysSet

    AddValue 1-3
    Nodes

    Capacity PrT

    t0 PrT

    AddValue 1-3
    Main nodes

    Capacity PrT

    t0 PrT

    AddValue 1-3
    Table 29: Time-varying attributes and their allocation to assignment procedures
    The example in table 30 illustrates the effect of time-varying attributes using the example of the
    Dynamic Stochastic assignment. The upper image shows the volumes and the capacity PrT on
    the links in time period from 5 am to 7 am. The lower image shows the volumes and the capacity PrT in the time period from 7 am to 9 am (a constant time series has been used here to simplify the comparison of both conditions, so that the traffic supply is the same in both of the time
    intervals).

    PTVGROUP

    115

    3.3.4 Time-varying attributes

    The links 11 - 41 and 41 - 40 are charged with the full capacity of 800.

    With the aid of a time-varying attribute for the capacity PrT on the two links (11-41 and 4140), both links are charged with a reduced capacity of 100. Therefore, the volumes of the
    links are lower.
    116

    PTVGROUP

    3.4 Subnetwork generator


    Table 30: Impact of time-varying attributes in the Dynamic Stochastic assignment

    3.4

    Subnetwork generator
    With the Subnetwork generator add-on module, a subnetwork 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 subnetwork.
    The subnetwork is generated on the basis of the following rules:
    The basis are all active links and all active line routes.
    Apart from that, the following network objects are transferred to the subnetwork:
    All From nodes and To nodes of the active links.
    All junction editor / junction control data for nodes with at least one leg in the subnetwork
    Turns whose From link and To link belong to the subnetwork
    All connectors at a node located in the subnetwork
    All zones with connectors at a node located in the subnetwork
    All PrT paths that belong to path sets
    All count locations located on active links
    All active POIs and, if applicable within the subnetwork; all references to nodes, links,
    POIs, stop points and stop areas are copied
    All screenlines
    All existing toll systems with at least one active link
    All active territories
    All main nodes if all associated partial nodes are active, and all associated main turns
    All stops that have at least one stop point on an active line route or a stop area within
    the active area are transferred in full (inclusive of all stop points and stop areas).
    Moreover, nodes (of the stop areas or stop points) referenced by the stop and, where
    applicable, connectors and zones connected to them are transferred.
    All active line routes, cut off if necessary
    All stop points and links of cut-to-length line routes
    All lines that have at least one active line route
    All main lines with at least one line included in the generated subnetwork
    All line route items of the active line routes
    All time profiles and time profile items of the active line routes
    All vehicle journeys, vehicle journey sections and journey routes of active line routes
    All coordination groups which are with their time profiles and extension completely
    within the subnet.
    All turn standards and block item types
    In addition, the following network objects are transferred from the entire network to the subnetwork:
    Demand segments
    Modes
    Transport systems
    Link types

    PTVGROUP

    117

    3.4 Subnetwork generator


    Main zones
    Calendar periods
    Valid days
    Fare zones
    Ticket types
    Directions
    Operators
    Vehicle combinations
    Vehicle units
    Surfaces
    Demand matrices
    Time series
    Demand time series
    Activities, activity pairs, activity chains *
    Person groups, structural properties *
    Demand strata *
    Skim matrices
    Procedure parameters
    * when activating option Include the demand model in the subnetwork
    Demand matrices
    Apart from the selected partial matrices (see User Manual: Chpt. 15.44 , page 1601), all
    other matrices that exist in the original network are saved to the subnetwork. The values of
    these matrices are set to zero. In order to indicate that they are part of the subnetwork, a
    suffix is attached to the matrix file names. If the version file contains references to matrices, they are updated accordingly.
    Example
    Subnetwork version name: tgen_ver
    Matrix file name in the original network: car.mtx
    Matrix file name in the subnetwork: car_tgen.mtx
    The subnetwork generator considers the paths 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 (subnetwork cordon zones) are added to the partial matrices of the
    demand segments so that no traffic demand in the subnetwork is lost.
    PrT demand matrices
    Cordon connectors are generated at all boundary nodes. Boundary nodes are nodes at
    which active and passive links meet, meaning at which at least one link is not included in
    the subnetwork. A subnetwork cordon zone is generated for each generated connector.
    Visum can then supplement the demand matrix using the paths. This requires performing
    an assignment.
    PuT demand matrix
    Boundary stop points are the first and last stop points of the active line routes and all stop
    points at which transfer events to passive line routes take place. Generated connectors
    are created at each stop area of a boundary stop point. A subnetwork cordon zone is

    118

    PTVGROUP

    3.4 Subnetwork generator


    generated for each generated connector. This requires performing an assignment. Alternatively, two kinds of stop point matrices can be generated.
    On path leg level
    For each partial route that is assigned to an active line route, a subnetwork cordon
    zone is generated each at the start and end stop point. The volume of the route is recorded as a demand between the respective zones, which means it emerges as many
    times in the new matrix as there are partial routes within that route.
    On path level
    For each route a cordon zone is generated for the first stop point of all active line routes (start). If the route is no longer active or if a partial route is followed by a walking
    link which leads across a passive link, a subnetwork cordon zone is created at the last
    stop point of the last active partial route (end). The demand is recorded between the
    start and the end. As soon as the route is active again, a subnetwork cordon zone is
    firstly generated at the first stop point of the first active partial route again etc.
    If all line routes of all links are active, the total of the stop point matrix equals the total of the
    demand matrix.
    For matrices on path level and path leg level the following applies: If the PuTAux transport system is used in a PuT assignment, the subnetwork generator manages routes that contain
    PuTAux as follows:
    If there is a passive link on a route section that uses PuTAux, a subnetwork cordon zone is
    generated at the From node of this link. As soon as the next active link is found, the subnetwork generator creates another subnetwork cordon zone at the From node of that link.
    The volume is transferred as demand data from one subnetwork cordon zone to the next
    one.
    In contrast, the following applies to the PuT Walk transport system: If there is at least one
    passive link within a walk link, subnetwork cordon zones are created at the last stop point
    before the walk link and at the next stop point after the walk link and not at the nodes of
    the passive link, as for PuTAux.
    The example in illustration 45 illustrates the differences. The Numbering of cordon zones
    with offset option has been selected in order to clarify the connection with the nodes. The offset specified is 10.

    PTVGROUP

    119

    3.5 The surface data model in Visum

    Illustration 45: Generating a subnetwork with stop point matrices regarding path legs and stop
    point matrices regarding paths
    Procedure parameters
    All procedure parameters that exist in the original network are transferred to the subnetwork. In order to indicate that they are part of the subnetwork, a suffix is attached to the
    files that store procedure parameters.

    3.5

    The surface data model in Visum


    In Visum boundaries can be shaped for the network objects zones, main zones, toll systems,
    territories, main nodes, GIS objects and POIs (polygons). Polygons describe the location and
    extent of network objects. Based on freely definable points and edges that connect these
    points, they are defined as surfaces independent of the network and allocated to the respective network objects via the SurfaceID attribute. The surfaces are displayed in the Visum surface model.

    3.5.1

    Tables in the surface model


    The Visum surface model consists of the following seven tables. In these tables, the surfaces
    of all network objects are displayed. The tables are explained with the aid of an example.
    Point
    Edge
    Edge item
    Face
    Face item

    120

    PTVGROUP

    3.5.1 Tables in the surface model


    Surface
    Surface item
    Note: In Visum, you can save polygons together with the network object type using them
    to a network file (see User Manual: Chpt. 14.4.6 , page 844). However, thereby all polygons are saved, independent of whether they were used for an object of the type specified or not.
    Example
    In the following example, the seven tables are displayed and explained for a network that contains three main nodes with surfaces.
    The network includes the three main nodes with the IDs 2, 3 and 4. These main nodes are allocated via the SurfaceID attribute to the surfaces with the IDs 866, 867 and 868 (table 31).
    * Table: Main nodes
    $MAINNODE:NO;SURFACEID
    2;866
    3;867
    4;868

    Table 31: Table Main nodes


    In the Surfaces table, all surfaces contained in the network are stored with their IDs. Since, in
    the example, only the three main nodes have a surface, there are exactly three entries for the
    main node surfaces in this instance (table 32).
    * Table: Surfaces
    $SURFACE:ID
    866
    867
    868

    Table 32: Table Surfaces


    Each surface is composed of one or multiple faces. The allocation of surfaces to faces is carried out in table Surface items. In the example, the surfaces 866 and 868 have exactly one
    face, whereas surface 869 has two faces. Thus, there are four faces in total with the IDs 1139,
    1141, 1144 and 1145 (table 33).
    * Table: Surface items
    $SURFACEITEM:SURFACEID;FACEID;ENCLAVE
    866;1139;0
    868;1141;0
    869;1144;0
    869;1145;0

    Table 33: Table Surface items

    PTVGROUP

    121

    3.5.1 Tables in the surface model


    In the Faces table, all faces contained in the network are stored with their IDs. In this example,
    there are thus four faces (table 34).
    * Table: Faces
    $FACE:ID
    1139
    1141
    1144
    1145

    Table 34: Table Faces


    In the Face items table, each face is allocated the IDs of the edges which define the face. As
    you can see in table 35, the faces with the IDs 1141, 1144 and 1145 are squares each, as they
    are defined by four edges. Face 1139 however, is a pentagon with five edges.
    * Table: Face items
    $FACEITEM:FACEID;INDEX;EDGEID;DIRECTION
    1139;1;33136;0
    1139;2;33137;0
    1139;3;33138;0
    1139;4;33139;0
    1139;5;33140;0
    1141;1;33145;0
    1141;2;33146;0
    1141;3;33147;0
    1141;4 33148;0
    1144;1 33160;0
    1144;2 33161;0
    1144;3;33162;0
    1144;4;33163;0
    1145;1;33164;0
    1145;2;33165;0
    1145;3;33166;0
    1145;4;33167;0

    Table 35: Table Face items


    The table Edges contains all edges which are required for the description of the face items.
    Each edge is defined by a start point and an end point, which bear the attribute names
    FromPointID and ToPointID in the table (table 36).

    122

    PTVGROUP

    3.5.1 Tables in the surface model


    * Table: Edges
    $EDGE:ID;FROMPOINTID;TOPOINTID
    33136;9449;9450
    33137;9450;9451
    33138;9451;9452
    33139;9452;9453
    33140;9453;9449
    33145;9458;9459
    33146;9459;9460
    33147;9460;9461
    33148;9461;9458
    33160;9473;9474
    33161;9474;9475
    33162;9475;9476
    33163;9476;9473
    33164;9477;9478
    33165;9478;9479
    33166;9479;9480
    33167;9480;9477

    Table 36: Table Edges


    In the Points table, all points are displayed which in turn define the edges. Each one contains
    information on the coordinates (XCoord and YCoord). This establishes the spatial reference of
    the surface to the network (table 37).
    * Table: Points
    $POINT:ID;XCOORD;YCOORD
    9449;3456991.5413;5430055.0204
    9450;3456991.5413;5430004.3885
    9451;3457052.3873;5429991.7699
    9452;3457070.0872;5430048.9542
    9453;3457026.8560;5430057.9988
    9458;3458808.0227;5431086.8027
    9459;3458821.3171;5431061.4225
    9460;3458848.5102;5431078.9469
    9461;3458835.5180;5431101.9100
    9473;3456956.4483;5430005.5296
    9474;3456948.8422;5430060.3735
    9475;3456887.1928;5430052.7674
    9476;3456903.2057;5429996.7225
    9477;3456896.8005;5430097.6033
    9478;3456938.0336;5430071.1821
    9479;3456961.6525;5430097.6033
    9480;3456945.2393;5430125.2254

    Table 37: Table Points


    No intermediate points were generated in the example. The table is therefore empty (table 38).
    * Table: Intermediate points
    $EDGEITEM:EDGEID;INDEX;XCOORD;YCOORD

    Table 38: Table Intermediate points


    PTVGROUP

    123

    3.5.2 Multi-part surfaces

    3.5.2

    Multi-part surfaces
    A surface can be made up of several faces (multi-part surfaces). Generally, a multi-part surface
    is defined by a set of so-called faces. Each face is a polygon with a sign. This is positive, if
    coordinates encircle the polygon anti-clockwise and negative, if the coordinate sequence is
    clockwise. Positive faces are thus digitalized anticlockwise, negative faces clockwise. This
    way, the type of polygon is clearly defined when interactively modifying polygons in the network display. This orientation of a face is thus a significant object feature. Positive faces add to
    the surface, negative surfaces subtract from it (holes).

    Illustration 46: Positive and negative surfaces


    Visum automatically normalizes the definition of any surface it encounters. Faces never intersect and a positive face will always (directly) contain only negative faces and vice versa.
    What is a normalized surface and why does it need to be normalized?
    Running geometrical operations (like Intersect or Territory indicators) efficiently on complex
    surfaces requires the use of a normalized representation. The table 39 shows some examples
    for the normalization of surfaces.
    Specified surface

    Normalized shape of the surface

    Two separate faces

    OK the surface remains unchanged

    Two overlapping faces

    124

    not OK both faces have been merged

    PTVGROUP

    3.5.2 Multi-part surfaces


    Specified surface

    Normalized shape of the surface

    OK the surface remains unchanged


    A face with a hole
    4

    A face with a hole which intersects


    the boundary of the surface

    not OK the hole is omitted and the


    face adjusted

    not OK the negative part is deleted


    A face with an intersecting boundary
    Table 39: Examples of the normalization of surfaces
    A surface is thus "normalizedif the following conditions are met:
    None of the faces of the same orientation overlap. This means
    all positive faces are separated (criterion 1a).
    none of the negative faces intersect nor touch the open plane (criterion 1b).
    none of the faces have intersecting boundaries (criterion 2).
    The simple example of the area calculation suffices to understand why a normalized representation facilitates geometrical operations. The area of normalized surfaces results directly
    from the sum of the areas of its faces. The sign depends directly on the orientation. Without normalization, the areas of all occurring intersections of the faces would have to be subtracted
    from the result. This would imply a significant increase in computation time. Computation time
    particularly increases because the mere determination of the intersection of sets with multiple
    overlaps is a complex algorithmic procedure.

    PTVGROUP

    125

    3.5.3 Sharing points between surfaces


    When does the program normalize?
    Normalized surfaces are a prerequisite for efficient use of polygons in various geometric calculation procedures. This is why this normalization is automatically performed during interactive digitalization and editing of polygons. The examples above show surfaces that can be
    inserted interactively just as they are displayed in the left column. However, when leaving the
    Edit shape mode, Visum automatically normalizes the surfaces. When loading surfaces from
    network or shape files, it is checked whether they are normalized or not. If required, the input
    data is then normalized. If polygons have already been normalized or the data is not required
    for geometrical calculation procedures (e.g. POI layers that merely serve as a background),
    you can optionally leave out the normalization check and so reduce import time.
    Note: However, if non-normalized surfaces that were originally only meant for background display are later on used in calculation procedures, this can lead to erroneous
    results, as normalization is required for such operations. If you are not sure whether a surface has been normalized or not, make sure you normalize it, if required (see User
    Manual: Chpt. 15.10.6 , page 1052).
    How accurate is the normalization (for experts)?
    The order in which the faces of a surface are defined is crucial to the normalization. In the network file, this order is defined by table Surface items.
    The polygon of a face needs to be preprocessed if its boundary intersects (see table 39, example 5). In this case, the face is split into non-intersected segments. This segmentation is done
    in such a way that the components do not intersect either. The orientations of the segments do
    not change, i.e. a scroll like the one in table 39 , example 5 is interpreted as a negative face.
    The positive and the negative polygons determined in this way are merged with the intermediate result of the faces considered before. If no boundaries intersect, segmentation is not
    necessary. The specified polygon and the intermediate result of the faces considered before
    can be merged directly.
    During this aggregation, faces sometimes have to be merged. This is, for example, the case in
    table 39, example 2, where two positive faces are merged. It can however also happen if faces
    are omitted and other faces change their shape. This is, for example, the case in table 39 ,
    example 4.
    This approach particularly implies that the first face must not have a negative orientation.
    Should this be the case, criterion 1 b) immediately takes effect, i.e. the face is dismissed.
    The question whether the orientation of the polygon of a face matches the enclave attribute of
    its surface item needs special attention. Here, information might be inconsistent when reading
    networks. In this case, the enclave feature wins, i.e. the orientation of the polygon is inverted
    where required. The advantage of this rule is that by editing just one attribute in the network
    file, a positive polygon face can be turned into a negative one and vice versa.

    3.5.3

    Sharing points between surfaces


    Besides normalization, which is used to eliminate intersecting polygon parts, there is another
    procedure used for surfaces (see "Multi-part surfaces" on page 124) It is called harmonization.
    During harmonization, several points, edges or polygon faces are identified that represent the

    126

    PTVGROUP

    3.5.4 Fuzzy surface alignment


    same object. These can be now combined to one object for the polygons and managed
    together. This concept is illustrated in the following simple example:
    Let us assume a study area and its surrounding are modeled in a Visum network. Both areas
    are modeled as territories, so they are assigned territory indicators. The edge of the study area
    normally corresponds to the hole in the surface of the surrounding. There are two options for
    modeling this:
    The study area is a one-piece surface. The surrounding consists of two surface areas,
    the outer, positive outline and a hole. The gap has the same edge points as the study
    area, but its own face object, edges, points and intermediate points. This is because
    during digitization of the surrounding, the existing edge points of the study area are
    snapped, but the option Merge snapped points has not been activated. If one of the
    two surfaces is digitized again later on, this does not affect the other surface. The
    edges of the two surfaces do not remain congruent, but a gap or an overlapping area
    (or both) is created.
    The study area consists of a one-piece surface that is also used as its negative face.
    This is because during digitization of the surrounding, the existing edge points of the
    study area are snapped and the option Merge snapped points has been activated. If
    one of the two surfaces is digitized again later on, this will affect the other surface in
    terms of the face that is used by both. The edges of the two surfaces still remain congruent, even after changes have been made.
    Which type of modeling is best suited depends on the individual case. However, it is always
    helpful to combine points of the same coordinates into an object, if the surfaces have the same
    borders. If you are working with larger models, the aspect of saving memory space may also
    play a role. Since if points (intermediate points, edges, faces) are combined into an object,
    less memory space is required.
    You can also combine all points with identical coordinates of an existing network later on (see
    User Manual: Chpt. 15.10.7 , page 1053).

    3.5.4

    Fuzzy surface alignment


    When importing surfaces from different sources, incorrect overlaps and gaps may occur between the surfaces.

    Illustration 47: Surfaces after import


    You can compensate for these deviations by performing a fuzzy alignment of the surfaces. The
    points of the surfaces are shifted within a defined tolerance in this case. The adjustment is possible for the following polygon objects:
    Zones, Main zones
    Main nodes
    Territories

    PTVGROUP

    127

    3.5.4 Fuzzy surface alignment


    polygonal Points of Interest (POI)
    Toll systems
    You can call the function at various points in the program:
    Via the context menu for the aforementioned polygon objects
    Shapefile import (see User Manual: Chpt. 22.4.1 , page 2221)
    Network settings of surfaces (see User Manual: Chpt. 15.10 , page 1042)
    The procedure is as follows:
    1. Define reference surfaces in the existing network
    2. Define number of surfaces to be imported
    3. Define tolerance values for fuzzy alignment
    The definition of the tolerance values determines the result of the fuzzy alignment.
    If tolerance values >0 are specified for existing surfaces and imported surfaces, the surfaces
    are adjusted to each other.

    Illustration 48: Blue and red surfaces were adjusted to each other
    If you define a surface as a reference surface by setting its tolerance value to 0, the second surface adjusts itself to the reference surface.

    Illustration 49: Blue surface is the reference surface, red surface adjusts itself to the blue surface

    128

    PTVGROUP

    4 Demand model

    Demand model
    One of the main uses of Visum is modeling transport demand. Demand modeling deals with
    traffic conditions. The most common travel forecasts analyze the daily travel behavior of people. These forecasts provide answers to the questions, when, how often, where and how do
    people travel.
    Visum offers three demand modeling procedures.
    Standard 4-step model (see "Standard 4-step model" on page 136)
    EVA (see "EVA model for passenger demand" on page 142)
    Tour-based model (see "Activity chain based model (tour-based model)" on page 174)
    The result of these procedures are matrices, which contain trips between the origin and destination zones of the network. These matrices are assigned to one or more demand segments.
    Assignment takes place on the basis of demand segments (see "User model PrT" on page 226
    and "User model PuT" on page 449).
    It is not mandatory to create a separate demand model in Visum, which calculates the matrices
    for the assignment. You can also use and assign matrices from external sources. Therefore, a
    complete demand description in Visum (that of course allows you to calculate an assignment)
    first only consists of the following elements:
    the transport demand in form of a matrix (see "Matrices" on page 130)
    temporal distribution of the transport demand by specifying a time series (see "Time
    series" on page 131). Specifying a time series is, however, only necessary for dynamic
    PrT assignments and PuT assignments. The demand distribution is ignored in the case of
    static PrT assignments.
    the allocation of matrices to one or more demand segments (see "Demand segments" on
    page 130)
    There are several demand objects that allow you to display the demand within the Visum data
    model (see "Demand objects" on page 129). Which of these demand objects are applied in
    your model, depends on the type of demand modeling in your network.
    Subjects
    Demand objects
    Demand modeling procedures
    Displaying and editing matrices
    Matrix correction

    4.1

    Demand objects
    A demand model consists of a set of demand objects which contain all relevant demand data,
    for example, the origin and destination of demands and the number of them in demand matrices. The demand object types in Visum are described below.
    Matrices
    Demand segments
    Time series
    Demand models

    PTVGROUP

    129

    4.1.1 Matrices
    Person groups
    Activities, activity pairs, activity chains
    Demand strata
    In addition, the EVA and tour-based demand models also contain the demand structural properties (see "Structural properties" on page 143 and "Tour-based data model" on page 175).

    4.1.1

    Matrices
    Matrices are one of the most important components of demand models. There are several
    matrix types:
    Demand matrices are used to show the transport demand between origin and destination
    zones.
    Skim matrices show the origin-destination zone skims, e.g. the travel time.
    Weighting matrices are only used to calculate the Weighting step of EVA-P demand
    models (see "EVA model for passenger demand" on page 142).
    In OD matrices, the demand is coded (by the number of trips) from origin zone i to destination
    zone j. The temporal distribution of travel demand within the analysis period is described by a
    start time and a time series that is considered during PuT assignment and dynamic PrT assignments (see "Time series" on page 131). The demand distribution is ignored in the case of
    static PrT assignments.
    The Matrix editor integrated in Visum allows you to process existing matrix data and perform
    calculations based on the gravity approach (see "Gravity model calculation" on page 188).
    In Visum, OD matrices and time series are independent objects which can freely be allocated
    to demand segments for assignment. This means that you can also use a matrix for more than
    one demand segment.
    Note: It is not mandatory to create a separate demand model in Visum, which calculates
    the matrices for the assignment. You can also use and assign matrices from external
    sources.

    4.1.2

    Demand segments
    A demand segment is a demand group or class, which is allocated in one step to a network,
    because the demand is homogeneous to the group. Examples for a demand segment could
    be pupils or commuters. The journey times from origin zones to destination zones are calculated per demand segment (see "Demand segments" on page 48).
    Demand segments are different from demand strata (see "Demand strata" on page 134).
    Demand strata contain demand groups for the steps trip generation, trip distribution and mode
    choice of the Standard 4-step model. Another important difference is that each demand segment is assigned to exactly one mode (for example PrT or PuT).
    The demand strata of a mode are generally aggregated to create demand segments. These
    aggregated demand segments are then assigned to the network. Aggregation is possible
    since the variables used to differentiate between the demand strata have no effect on the assignment. Demand strata, for instance, are often distinguished by employment, e.g. employees
    with a car and non-employees with a car. If the study area has no toll roads, the employee

    130

    PTVGROUP

    4.1.3 Time series


    status plays no role for route choice during the assignment. In other words: Everyone chooses
    the same route between the origin and destination zone, irrespective of their income level. So
    demand strata can be aggregated to a demand segment for assignment.
    To calculate an assignment, the system needs to assign each demand segment exactly one
    matrix (see "Matrices" on page 130). For dynamic PrT assignments and all PuT assignments, a
    demand time series must also be assigned to each demand segment (see "Time series" on
    page 131). Visum establishes the link between demand and transport supply.
    Notes: A possibly specified time series is ignored in the case of static PrT assignments.
    A matrix can also be assigned to several demand segments. The same applies to time
    series.

    4.1.3

    Time series
    The temporal distribution of trip demand over the evaluation period is described using a start
    time and a demand time series. The demand time series is considered for PuT assignment
    and dynamic PrT assignment. The demand distribution is ignored in the case of static PrT assignments (see "Temporal distribution of travel demand" on page 19 and "Time reference of the
    demand (time series)" on page 96).
    Note: A time series can also be assigned to several demand segments.
    There are two types of standard time series:
    Time series of matrix numbers, i.e. selection of several matrices that form the time series.
    proportional time series of one demand matrix
    with distribution of travel demand in time intervals (in percent)
    if required modified per pair of zone type relation

    4.1.4

    Demand models
    Demand models are a particular kind of Visum demand objects to which the other demand
    objects (person groups, activities, activity pairs and activity chains, demand strata, structural
    properties) are assigned and which allow to define and store various calculation models for
    demand modeling in Visum(see "Transport demand model" on page 17).
    A demand model has the following attributes:
    Attribute

    Description

    Code (Key)

    Code (any string), for example EVA-P

    Name

    Name of the demand model, for example EVA-P model

    Type

    Type of calculation model (Standard 4-step, EVA passenger demand


    or Tour-based model)

    Mode codes

    Abbreviation of the modes of the demand model

    PTVGROUP

    131

    4.1.5 Person groups

    4.1.5

    Person groups
    The population living in the planning area is broken down into so-called "behavior- homogenous" groups. The traffic behavior of the different groups should be clearly different, but
    within the individual groups it should be as homogenous as possible.
    This documentation uses examples in which the person groups are normally broken down
    according to the criteria employment/education and motorization. The following table shows a
    division into groups with homogenous behavior and their codes (Schmiedel 1984).
    Employees with car available

    E+c

    Employees without car

    E-c

    Not-employed with car available

    NE+c

    Not-employed without car

    NE-c

    Apprentices

    Appren

    Students 18 yrs and older

    Stud

    Pupils from secondary school

    SPup

    Primary school pupils

    PPup

    Children under six

    Child

    The demand object person group is described by the following attributes:


    Attribute

    Description

    Code (Key)

    Code (any string), for example Stud

    Name

    Name of person group, for example students

    DemandModelCode

    Abbreviation of the demand model the person group belongs to (any


    string), e.g. DEFAULT

    When using the Standard 4-step model, generally only one single person group is required,
    i.e. there is a 1:1 relation between activity chain and demand stratum.

    4.1.6

    Activities, activity pairs, activity chains


    The demand model is based on the assumption that trip purposes or external activities cause
    mobility. The examples given in this manual use the activities listed in the table below. They
    are derived from traffic surveys, e.g. from KONTIV 89, whereby the activity of education has
    been differentiated.

    132

    Work

    Shopping

    Education: vocational school

    Education: university

    PTVGROUP

    4.1.6 Activities, activity pairs, activity chains


    Education: secondary school.

    Education: primary school

    Recreation

    Home

    The demand object activity is described by the following attributes:


    Attribute

    Description

    Code (Key)

    Code (any string), for example W

    Name

    Name of the activity, for example housing

    IsHomeActivity

    This Boolean attribute is true (= 1) if the activity is the starting point


    and end point of an activity chain. This is typically the case for the
    activity Home.

    DemandModelCode

    Abbreviation of the demand model the activity belongs to (any


    string), e.g. EVA-P.

    Note: Activities are optional and can be defined interactively only for EVA and tour-based
    models. In case of Standard 4-step models one activity corresponds to exactly one activity pair.
    An activity pair corresponds to the trip between two successive activities in the daily routine of
    a person.
    The demand object activity pair is described by the following attributes:
    Attribute

    Description

    Code (Key)

    Code (any string), for example HW

    Name

    Name of the activity pair, for example home - work

    DemandModelCode

    Abbreviation of the demand model the person group belongs to (any


    string), for example DEFAULT.

    The following attributes describing activity pairs are only relevant for EVA models.
    Attribute

    Description

    OrigActivityCode

    Code of the activity where the trip starts, for example H (home)

    DestActivityCode Code of the activity where the trip ends, for example W (work)

    PTVGROUP

    133

    4.1.7 Demand strata


    Attribute

    Description

    OD type

    Direction of the activity pair in terms of the home activity


    The following values are possible.
    1 - Origin activity is home activity (for example home- work)
    2 - Destination activity is home activity (for example shoppinghome)
    3 Neither origin nor destination activity are home activity (for example others others).
    By default the value of the attribute is determined by the attribute
    IsHomeActivity of origin and destination activity, but can also be
    overridden manually. It has an influence on the calculation in trip
    generation and trip distribution (see "EVA trip generation" on page
    146 and "EVA trip distribution and mode choice" on page 165).

    An activity chain describes a sequence of typified activity pairs. For example, the chain home
    work shopping home (HWOH). Such a sequence of activity pairs implies trips, in this example here three different trips (HW, WO, OH).
    The following attributes describe the demand object activity chain.
    Attribute

    Description

    Code (Key)

    Code (any string), for example HWH

    Name

    Name of the activity chain, for example home work home

    ActivityCodes

    Comma-separated list of activity codes

    DemandModelCode

    Abbreviation of the demand model the person group belongs to (any


    string), for example DEFAULT.

    In the tour-based demand model, the average mobility program of persons is described by activity chains. The Standard 4-step model and the EVA model allow single- element activity
    chains only. So an activity chain corresponds directly, i.e. 1:1, to the activity pair.

    4.1.7

    Demand strata
    The demand stratum constitutes the basic demand object for calculating trip generation, trip
    distribution and mode choice. It links an activity chain with one or several person groups (in
    the tour-based model with exactly one person group). The pointers to activity chains and person groups in the Standard 4-step model are optional.
    The correlations between demand objects can be depicted graphically as follows (see " Correlations between different demand objects" on page 135).

    134

    PTVGROUP

    4.1.7 Demand strata

    Illustration 50: Correlations between different demand objects


    The demand object demand stratum has the following attributes.
    Attribute

    Description

    Code (Key)

    Code (any string), for example HWH Stud

    ActChainCode

    Activity chain code (optional)

    DemandGroupCodes

    Person group codes (optional)

    Name

    Name of demand stratum, for example student-shopping


    or employee+car home-shopping-home

    DemandModelCode

    Abbreviation of the demand model, for the respective


    demand stratum, for example DEFAULT

    DistribMatrixNumber

    Number of demand matrix to which the result of the distribution for this demand stratum is stored (optional)

    DemandTimeSeriesNumber

    Number of demand time series for temporal distribution of


    demand (optional).

    The following attributes describing demand strata are only relevant for EVA models.
    Attribute

    Description

    Origin Structural Property


    Codes

    Origin of the structural property codes

    Destination Structural Property Codes

    Destination of the structural properties codes

    Balancing

    Indicates the demand stratum (origin-destination type 3)


    in which balancing takes place

    Quantity as potential

    This Boolean attribute describes whether the productions


    or attractions of the demand stratum impact as potentials

    PTVGROUP

    135

    4.2 Demand modeling procedures


    Attribute

    Description
    in Trip distribution/Mode choice (=1) or only have to meet
    the constraints (=0).

    4.2

    Constraint type origin


    Constraint type destination

    Type of marginal totals of the constraint on origin or destination side

    Constraint min factor origin


    constant
    Constraint max factor origin
    constant
    Constraint min factor destination constant
    Constraint max factor destination constant

    This Boolean attribute describes, whether the lower or


    upper limit of the production and attraction is constant
    (=1) or zone-dependent (=0).

    Constraint min factor origin


    Constraint max factor origin
    Constraint min factor destination
    Constraint max factor destination

    Factor for the upper or lower limit of production or attraction.

    Demand modeling procedures


    Information on the demand within a planning area is required for the analysis of transportation
    networks. Demand matrices can be determined partially through surveys. That is why mathematical models are used to reproduce real demand ratios, which calculate the traffic flows between the zones of the planning area on the basis of the structure and behavior data, the
    spatial utilization structure and the transport system. Another function of such a model is the
    provision of prognoses and scenarios.
    Visum currently offers three procedures for demand modeling:
    Standard 4-step model
    EVA model for passenger demand
    Activity chain based model (tour-based model)
    There are also the following functions available to calculate the transportation demand:
    Estimate gravitation parameters (KALIBRI)
    Gravity model calculation
    Iterative repetition

    4.2.1

    Standard 4-step model


    The first three steps of the 4-step model, trip generation, trip distribution and mode choice, are
    usually carried out sequentially in the Standard 4-step model successively. As illustration 51
    shows, skim matrices resulting from assignment are incorporated into the model stages of Trip
    distribution and Mode choice. Due to this cyclical dependence the process covering all four
    steps (including Assignment) is repeated until the result fulfills the stop criterion, which usually

    136

    PTVGROUP

    4.2.1 Standard 4-step model


    is the stability of the demand matrices or the impedances in the network. You can call the procedure run manually or use Go to the Procedure (see "Go to the procedure" on page 196).

    Illustration 51: Integrated 4-step demand model in Visum


    Moreover, the convergence speed can be improved by averaging matrices or impedances
    after the assignment by means of several iterations before using them for the next iteration of
    the demand model. This can be done with the operations Method of successive averages over
    matrices and Method of successive averages over attributes (see "Method of successive averages (MSA) over matrices" on page 198 and "Method of Successive Averages over attributes"
    on page 198).
    As variant of the classical 4-step model Mode choice can be calculated in several steps instead of one step (Nested Logit). You can optionally add a departure time after mode choice.
    The illustration 52 shows as an example the procedure in an extended demand model.

    PTVGROUP

    137

    4.2.1.1 Trip generation

    Illustration 52: Extended 4-step model


    In the normal case carry out each of the operations trip generation, trip distribution and mode
    choice for all demand strata of the model. For special purposes, however, they can also be carried out for individual demand strata if the required input attributes are known.
    If necessary, operations on matrices may be fitted in between the individual stages, for example in order to prepare skim matrices (e.g. setting the values on the matrix diagonal) or to add
    externally predetermined demand data (e.g. through-traffic) (see "Displaying and editing matrices" on page 199).
    4.2.1.1

    Trip generation
    In that stage for each zone and each demand stratum the production and attraction rates are
    calculated. These parameters are also called productions and attractions. The productions either correspond to the actual origin traffic of the zone i.e. the number of trips starting there, or
    the attractiveness of the zone for the demand stratum, meaning they have an influence on the
    probability of trips starting in that zone with the next Trip distribution procedure. Which of the
    two cases applies can be determined by a procedure parameter of Trip distribution. The same
    holds for destination traffic.
    The productions of a demand stratum in a zone depend on its structural or demographical indicators describing the intensity of the production activity. For the production activity Home the
    number of inhabitants of a zone, if necessary, disaggregated into age, income and/or car
    availability can be used. For the production activity Work the number of jobs may be appropriate, perhaps broken down into different sectors. For such skims user-defined zone attributes
    are the best. First, production Qi of zone i is calculated with the help of a formula,

    whereby SGg is summed up across all structural properties. SGg(i) designates the value of SGg
    in zone i. The coefficient g is a production rate which describes how many trips per structural
    property unit occur. They specify the production rates per demand stratum and zone attribute
    used. The same calculation is performed for the attraction Zj.
    In most applications the total production of a demand stratum (added up over all zones) corresponds to the total attraction.
    138

    PTVGROUP

    4.2.1.2 Trip distribution

    If equality has not already been the outcome of the attributes and production rates used, it can
    be set by means of a procedure parameter whether all productions and attractions have to be
    scaled so that their totals are equal. As reference values you can predetermine total productions, total attractions or the minimum, maximum or mean value of both parameters.
    You can limit calculation to the active zones. This might be useful in cases where the network
    model covers both the actual planning area and its surrounding sub network cordon zones. If
    you only want to calculate planning area-internal trips by means of the demand model, first of
    all define a filter for the zones of the planning area only. Proceed in a similar way if the production rates are not uniform for all zones. Break the zones down into groups of homogeneous
    production rates and insert the operation trip generation for each of the groups into the process. Prior to each such operation set a filter for the zones of that group (operation Read filter
    (see User Manual: Chpt. 15.7.5.2 , page 1025) ) and calculate trip generation only for the
    respective active zones.
    For each zone the results of trip generation are stored per demand stratum in the zone attributes productions and attractions.
    4.2.1.2

    Trip distribution
    The productions and attractions calculated in the operation trip generation only determine the
    constraints of the total demand matrix of a demand stratum. The elements of the matrix themselves are calculated in the operation trip distribution. On the one hand, the allocation of a certain destination zone to a given origin zone is based on its attractiveness for the demand
    stratum (measured by its destination demand = attractions), on the other hand the impedance
    of the trip from origin to destination zone is vital (measured by the skim matrices for journey
    time, fares and other elements of generalized costs).
    These input data being available, a gravity model is formulated and solved (see "Gravity
    model calculation" on page 188).
    Notes:
    Origin and destination traffic of the individual zones have to be available per
    demand stratum as zone attributes productions and attractions.
    To each demand stratum for which Trip distribution is to be calculated a demand
    matrix has to be allocated into which the results are stored.
    The parameters for the gravity model can be estimated beforehand (see "Estimate
    gravitation parameters (KALIBRI)" on page 187).

    4.2.1.3

    Mode choice
    The operation Mode choice breaks down the total demand (total demand matrix) into the individual transport modes per demand stratum (for example PrT, PuT) based on mode-specific
    impedance skims (for journey time, costs, etc.).
    First of all for each mode m the utility is calculated as a linear combination of the impedance
    parameters.

    PTVGROUP

    139

    4.2.1.4 Nested Mode Choice

    Whereby
    cijmg

    The impedance of the cost type g for the trip from zone i to zone j by mode m.

    The respective shares of the trips of each relation result from the utilities of the different modes.
    Hereby, you can choose between several distribution functions (see "Gravity model calculation" on page 188). As an example see below the calculation for the Logit model.

    whereby Tij is the total number of trips of the demand stratum in the relation i-j, Tijm is the number of trips made by mode m and c is a procedure parameter.
    There are two types of demand strata.
    Those referring directly to a demand matrix allocated to one single demand segment
    or several demand segments
    Those whose demand matrix is not related to any demand segment
    No mode choice will be calculated for demand strata referring directly to a matrix with demand
    segment(s).
    For demand strata whose demand matrix is not related to any demand segment it is determined per mode to which demand matrix the demand allocated to that mode has to be added
    in mode choice.
    4.2.1.4

    140

    Nested Mode Choice


    For nested mode choice, the total demand (total demand matrix) per demand stratum is distributed to the transport modes defined in the network (for example car PrT, bus PuT), using
    mode-specific skims of several stages (illustration 53).

    PTVGROUP

    4.2.1.5 Time-of-day choice

    Illustration 53: Modeling through decision tree


    For the Logit model (mode choice), the decision model determines the utility of a leaf node as
    usual through a linear combination of skim matrices of the respective mode. For a nest node,
    the utility consists of two components:
    Nest utility that does not depend on the individual sub-node, e.g. fare.
    Summary of individual utility of all sub-nodes, e.g. travel time.
    This leads to

    As a result, the procedure calculates a demand matrix for each leaf node and - optionally also for each nest node.
    For each leaf node or nest node, the calculated result can be saved to an existing skim matrix
    for further analyses (Ortzar 2001, pages 228-235).
    4.2.1.5

    Time-of-day choice
    By trip distribution or mode choice, demand matrices can be calculated which are used by
    demand segments for assignments (see "Trip distribution" on page 139 and "Mode choice" on
    page 139). In addition to the demand matrix further entries may be required for an assignment.
    A demand segment can refer to a time series for an analysis time interval dependent assignment.

    PTVGROUP

    141

    4.2.2 EVA model for passenger demand


    With operation Time-of-Day Choice, a demand matrix of a demand segment can be spread
    over the time intervals of a standard time series. This standard time series can then be used as
    demand time series in PuT assignments or in the dynamic PrT assignments.

    4.2.2

    EVA model for passenger demand


    The EVA model developed by Lohse at Dresden Technical University constitutes an alternative approach to the first three stages of the classical traffic planning model (Lohse 1997).
    The model differs from the above-described Standard 4-step model (see "Standard 4-step
    model" on page 136) by the following features.
    If trip generation and trip distribution are calculated independently, i.e. one after the other
    and above all separately for each activity pair as in the Standard 4-step model, it often
    happens that differences occur between the origin and destination traffic of the zones. The
    EVA model links generation and distribution by an explicit constraints step to make up for
    the differences.
    In the EVA model trip distribution and mode choice are performed simultaneously, i.e. by
    applying a one-stage discrete choice model to three-dimensional utility matrices indexed
    according to origin zone, destination zone and mode.

    4.2.2.1

    EVA data model


    The data model for EVA also comprises the relevant demand object types (see "Demand
    objects" on page 129) for other models such as the additional demand object types structural
    property. Compared to the standard-4-stage model, these demand objects have some additional attributes in the EVA model. These attributes have an effect on EVA trip generation (see
    "EVA trip generation" on page 146).
    Activities and activity pairs
    In the EVA model activities and activity pairs have the following additional attributes.
    Type of
    demand object

    Attribute and range Meaning


    of values

    Activity

    IsHomeActivity
    bool (0,1)

    The value of 1 specifies the activity representing


    the road users home. Just one activity can be
    specified as such. The attribute influences the
    default setting of the OrigDestType attribute for
    the type of demand object of Activity pair.

    Activity pairs

    OD type

    1 = Origin activity is home activity

    {1, 2, 3}

    2 = Destination activity is home activity


    3 = neither origin nor destination activity are
    home activity

    Table 40: Demand object types in the EVA demand model

    142

    PTVGROUP

    4.2.2.1 EVA data model


    Structural properties
    Structural properties are used to measure the zone attractiveness as origin or destination of a
    journey. They, for example, include sales floor areas or the number of school places. Structural properties are very simple demand objects, their only attributes are a code and a name.
    Instead, you could also use user-defined zone attributes. However, defined as structural properties, they better reflect their role in the demand model.
    To each structural property SP defined in the demand model the numerical zone attribute
    ValueStructuralProp(SP) in which the values of the structural property per zone can be filed is
    created automatically.
    Demand strata
    Demand strata, too, have several additional properties, particularly in connection with their
    constraints. Moreover, demand strata refer to an activity pair having an origin-destination type.
    Since that type determines the treatment of the demand strata in the different operations and
    therefore is referred to frequently, it is called the origin-destination type of the demand stratum
    itself below.
    Attribute

    Meaning and range of values

    Origin Structural Pro- Parameters specifying the structural potential of the demand straperty Codes
    tum on the origin side.
    Range: set of structural properties
    Destination StrucAs above for destination side
    tural Property Codes Range: set of structural properties
    Balancing
    (Balancing on the
    user interface)

    Value 1 specifies the demand stratum in which the differences between total origin and destination traffic are absorbed during balancing. Just one demand stratum can be marked as such, it has to
    be of origin-destination type 3.
    Range: bool (0, 1)

    Quantity as potential 1 = productions or attractions also define the structural potential


    (attractiveness) of the zone for the demand stratum.
    0 = productions or attractions have to be kept as constraint during
    Trip distribution, but do not reflect any attractiveness. Instead all
    zones show the same structural potential.
    Range: bool (0, 1)
    Marginal totals type
    origin
    (Constraint Orig. on
    the user interface)

    Type of constraint on origin side. For origin-destination type 1 it is


    always hard, in all other cases variable.
    Range: {hard, weak, elastic, open}

    Marginal totals type


    destination
    (Constraint Dest on

    As above for destination side


    Range: {hard, weak, elastic, open}

    PTVGROUP

    143

    4.2.2.1 EVA data model


    Attribute

    Meaning and range of values

    the user interface)


    Marginal totals min
    factor origin constant
    (CF OMin Constant
    on the user interface)

    1 = ConstraintMinFactorOrig is constant, i.e. zone-independent.


    The value of the ConstraintMinFactorOrig attribute of the
    demand stratum is applicable. Select this option if the factor for the
    lower limit of the productions is equal for all zones.
    0 = ConstraintMinFactorOrig is zone-dependent. The value of the
    ConstraintMinFactorOrig(DStr) zone attribute is applicable. This
    option makes sense if you want to use the individual lower limits.
    This attribute can only be edited if the factor has not been determined by the selected type of constraint.
    Range: bool (0, 1)

    Constraints max fac- As above for the upper limit on origin side
    tor origin constant
    Range: bool (0, 1)
    (CF OMax constant
    on the user interface)
    Constraints min factor destination constant

    As above for the lower limit on destination side


    Range: bool (0, 1)

    (CF DMin constant on


    the user interface)
    Marginal totals max
    factor destination
    constant
    (CF DMax constant
    on the user interface)

    As above for the upper limit on destination side


    Range: bool (0, 1)

    Constraints min factor origin


    (CF OMin on the user
    interface)

    Factor for the lower limit of the productions if ConstraintMinFactorOrigConstant = 1


    This attribute can only be edited if the factor has not been determined by the selected type of constraint.
    Range: floating point number 0

    Constraints max fac- As above for the upper limit on origin side
    tor origin
    Range: floating point number 0
    (CF OMax on the user
    interface)

    144

    PTVGROUP

    4.2.2.1 EVA data model


    Attribute

    Meaning and range of values

    Constraints min factor destination


    (CF DMin on the user
    interface)

    As above for the lower limit on destination side


    Range: floating point number 0

    Constraints max fac- As above for the upper limit on destination side
    tor destination
    Range: floating point number 0
    (CF DMax on the user
    interface)
    Table 41: Properties of the demand strata in the EVA demand model
    Zones
    Due to the definition of the objects of the demand model several zone attributes are created.
    Attribute

    Subattribute

    Meaning and range of values

    Balance factor Productions

    Demand stratum

    Weighting of demand stratum productions


    This value can be included in and recalculated
    during trip distribution.

    Balance factor Attractions

    Demand stratum

    Weighting of demand stratum attractions


    This value can be included in and recalculated
    during trip distribution.

    Constraints min factor origin

    Demand stratum

    Factor for the lower limit of the productions if


    ConstraintMinFactorOrigConstant = 0
    This attribute can only be edited if the factor has
    not been determined by the selected type of constraint.
    Range: floating point number 0

    Constraints max fac- Demand strator origin


    tum

    As above for the upper limit on origin side

    Constraints min factor destination

    Demand stratum

    As above for the lower limit on destination side

    Constraints max fac- Demand strator destination


    tum

    As above for the upper limit on destination side

    Number of persons

    Number of inhabitants of the person group in


    zone

    Person group

    Range: floating point number 0


    Range: floating point number 0
    Range: floating point number 0

    Range: integer 0
    Structural property
    value

    PTVGROUP

    Structural property

    Value taken by the structural property in zone


    Range: floating point number 0

    145

    4.2.2.2 EVA trip generation


    Attribute

    Subattribute

    Meaning and range of values

    Mobility rate

    Demand stratum
    Person group

    Specific traffic demand of a person group for the


    demand stratum. Only effective if MobilityRateConstant(DStr) = 0 in the procedure
    parameters of EVA trip generation.
    Range: floating point number 0

    Production rate

    Demand stratum
    Structural property

    Production rate of structural property for the


    demand stratum on origin side. Only effective if
    ProductionRateConstant(DStr) = 0 in the procedure parameters of EVA trip generation.

    Attraction rate

    Demand stratum
    Structural property

    As above for destination side

    Demand stratum
    Person group

    Remaining share of home trips of the person


    group for the demand stratum. Only effective if
    StudyAreaFactorHomeConstant(DStr) = 0 in
    the procedure parameters of EVA trip generation.

    Range: floating point number 0

    Study area factor


    home

    Range: floating point number 0

    Range: floating point number 0


    Study area factor ori- Demand stragin
    tum
    Structural property

    Effective share of the structural property for the


    demand stratum (on origin side). Only effective if
    StudyAreaFactor ProductionConstant(DStr) = 0
    in the procedure parameters of EVA trip generation.
    Range: floating point number 0

    Study area factor


    destination

    Demand stratum
    Structural property

    As above for destination side


    Range: floating point number 0

    Table 42: Zone attributes for the EVA demand model


    4.2.2.2

    EVA trip generation


    In the EVA model and Standard 4-step model, productions and attractions are calculated similarly, namely based on demographic (number of inhabitants) and structural (jobs, size of retail
    sales floor) parameters as well as on mobility rates (taken from statistical surveys on traffic
    behavior). It is performed separately for each demand stratum, which means for each activity
    pair and its major person groups.
    In EVA trip generation productions and attractions normally refer to a closed time interval with
    regard to traffic (generally the average working day). The following model stages, EVA Weighting and EVA Trip distribution and Mode choice, too, refer to the overall period. The demand

    146

    PTVGROUP

    4.2.2.2 EVA trip generation


    matrices available at the end of the model chain only can be combined with an empirically
    determined or standardized daily time series (illustration 54 ) to get the shares of demand for
    the individual times of the day. The daily time series depend on the demand stratum.

    Illustration 54: Daily time series for origin-destination groups of HW and WH (SrV 1987 Dresden)
    The following table shows the allocation of activities, activity pairs, structural properties and
    person groups on demand strata. Thereby the abbreviations used stand for the following: H:
    Home; W: Work; C: Child care facility, S: School; F: Shift; P: Shopping; R: Recreation; O:
    Others.
    From/To

    H
    W

    WH

    CH

    SH

    FH

    PH

    RH

    HW

    HC

    HS

    HF

    HP

    HR

    HO
    WO

    S
    OH
    OW
    OO
    Table 43: Typical break-down of a demand stratum into 8 activities and 17 demand strata =
    activity pairs
    Demand stratum

    Structural property (S) / Person group (P) of source zone i

    HW

    Employees

    HC

    Young children

    HS

    Pupils, apprentices, students

    PTVGROUP

    147

    4.2.2.2 EVA trip generation


    Demand stratum

    Structural property (S) / Person group (P) of source zone i

    HF

    Employees

    HP

    Inhabitants

    HR

    Inhabitants

    HO

    Inhabitants

    WO

    Jobs

    WH

    Jobs

    CH

    Jobs / capacity

    SH

    Jobs / capacity

    FH

    Jobs

    PH

    Jobs / sales floor

    RH

    Jobs / capacity

    OH

    Other jobs

    OW

    Other jobs

    OO

    Other jobs

    DStr

    Structural property (S) / Person group (P) of destination zone j

    HW

    Jobs

    HC

    Jobs / capacity

    HS

    Jobs / capacity

    HF

    Jobs

    HP

    Jobs / sales floor

    HR

    Jobs / capacity

    HO

    Other jobs

    WO

    Other jobs

    WH

    Employees

    CH

    Young children

    SH

    Pupils, apprentices, students

    FH

    Employees

    PH

    Inhabitants

    RH

    Inhabitants

    OH

    Inhabitants

    OW

    Jobs

    OO

    Other jobs

    Table 44: Examples of relevant structural properties and person groups of the demand strata
    148

    PTVGROUP

    4.2.2.2 EVA trip generation


    Thus, for the demand strata HW and WH only the Employees person group (which could be
    broken down into further subgroups) is relevant, whereas for the demand strata HO and OH
    generally all person groups are relevant. The number of persons of all person groups in each
    zone make up an important part of input attributes for the trip generation of a certain demand
    stratum. Further structural properties measure the intensity of the activities at the origin or destination. An example of the allocation of certain structural properties to individual demand
    strata is illustrated by table 44.
    The person groups specified here can be broken down into further subgroups according to
    other features (car availability, age) and used for trip generation.
    For each demand stratum and each relevant person group, mobility rates have to be defined.
    The mobility rate of a person group is defined as the average number of trips per day and person.

    In most cases, the MRpc values are known from national surveys on traffic behavior and are
    assumed to be constant for all zones of the study area. If the individual zones feature different
    specific traffic demands, for example distinguishing between urban and rural areas, they can
    be used, too. Then MRepc specifies the particular demand of the person group or reference person group p in zone e (in a certain demand stratum c).
    Analogously production rates defined as the number of trips per day and structural property
    are determined for the major structural properties like number of jobs, sales floor, etc. To do
    so empirical studies or available historical values can be referred to. Here, too, a differentiation according to zones is possible. The structural potential of the zone results from the
    value of the structural property and the related production rate.
    A certain number of trips of the total production of a zone remains within the study area only,
    the rest targets destinations outside. The same holds for destination traffic. Since the EVA
    Model usually serves the calculation of study area-internal traffic (incoming and outgoing traffic as well as through-traffic are often added by other sources), the share of trips of the total origin (or destination) traffic made within the study area can be determined for all origin (or
    destination) zones.
    Example: The origin traffic of the demand stratum of Home-Work (HW) results from the number
    of persons of the person group of Employees (EP) and the mobility rate MREP,HW . In a zone R
    on the edge of a study area, however, part of the employees will commute to destination zones
    outside the study area. It is not available for a later trip distribution and mode choice. In that
    case, the study area factor UR,EP,HW is below 1, conveying that only that share of trips remains
    within the study area. For a zone Z in the center, however, all trips of the demand stratum lie
    within the study area. Therefore the following applies: UZ,EP,HW = 1. Study area factors do not
    only depend on the zone but also on the demand stratum and the person group. It is more probable that employees with car (E+c) commute over great distances and therefore to destinations outside the study area than those without car (E-c). If you differentiate these two
    person groups in the model, then would typically be UR,E-c,HW > UR,E+c,HW. And in analogy her-

    PTVGROUP

    149

    4.2.2.2 EVA trip generation


    eto would be U R,Child,HC > UR,E+c,HW , because child care facilities are rather found in the proximity of homes than jobs.
    As the mobility rate of a person group the production rate of a structural property, too, can have
    partial impacts in the study area only. So, for example, the structural potential of the demand
    stratum HW is determined by the number of jobs (structural property J) and the related production rate. On the edge of the study area part of the jobs are taken by employees living outside the study area. Therefore, these jobs are not available as potential destinations of HW
    trips of the study area. Therefore, in that case, too, the total structural potential is multiplied by
    a study area factor VR,J,HWA < 1.
    You can limit calculation to the active zones. This allows you to e.g. exclude cordon zones
    from the calculation.
    In the trip generation stage (table 45, table 46 and 4.2.2.2) from the structural data and values
    mentioned for all demand strata c, the productions Qic and attractions Zjc or the upper limits
    Qicmax and Zjcmax of these demands are calculated.
    The approach depends on the origin-destination type of the activity pair of the demand stratum. It specifies whether the activity pair affects the home activity of the road user as origin or
    destination. Three types are possible.
    Type 1: origin activity = home activity (own apartment, own work)
    Type 2: destination activity = home activity (own apartment, own work)
    Type 3: origin and destination activity home activity
    The calculation specifications can be taken from table 45, table 46 and 4.2.2.2. For the types 1
    and 2 calculation starts with the home trips (of number of persons, mobility rate, study area factor) which independently from the travel direction always occur in the origin zone. For type 1
    the number of trips corresponds exactly to the production, for type 2 to the attraction of the
    respective zone. For type 1 the total production (of all zones) is distributed onto the destination
    zones, in proportion to their potentials (taken from structural properties, production rates and
    study area factors). Type 2 is treated equally. The total attraction is distributed proportionally to
    the potentials onto the origin zones. For type 3 total volume is equally calculated on the basis
    of the total home trips. However, the sizes of the road users origin zones are relevant, which
    do not have to correspond with origin or destination of the trip. Proportionally to the potential
    the total volume is then distributed onto the origin zones on the one hand and onto the destination zones on the other hand.
    The productions and/or attractions so calculated can have various meanings.
    Hard constraints
    Traffic demand solely results from the spatial structure and has to be fully exhausted by the
    trips calculated in the model.
    Example: if the number of employed inhabitants and jobs per zone is known, hard constraints will be applicable to the demand stratum Home Work (HW), since every employed
    person necessarily has to commute to work and each job has to be destination of commutation.
    Weak constraints

    150

    PTVGROUP

    4.2.2.2 EVA trip generation


    Traffic demand does not only depend on the spatial structure but also on the convenience
    of the location and the resulting competitive conditions. In these cases traffic demands
    resulting from trip generation are like upper limits. With Trip distribution and Mode choice it
    turns out to which extent the limits will be exhausted by the actually determined origin
    and/or destination traffic.
    The structural potential of the destination zone for the demand stratum Home Shopping
    (HP) is usually calculated based on the structural property of sales floor and a production
    rate for example. It is conceivable that there may be overabundance of sales floor so that
    the shopping facilities are not used to their full potential. Therefore, the attraction calculated
    by trip generation from the potential only constitutes an upper limit for real destination traffic. Therefore, the constraint is hard on the destination side, whereas weak on the origin
    side, because each road user has to shop (somewhere).
    Elastic constraints
    Elastic constraints are a generalization of weak constraints. Additionally to upper limits
    lower limits are equally known, for the demand stratum Home - Shopping (HP), for example, from sales statistics. In this case, the structural potential of the sales floor determines an
    interval for the attraction of the respective zone.
    Open constraints
    The potential of the structure properties merely expresses the attractiveness of the zone as
    an origin or destination of the demand stratum. However, the production or attraction is not
    linked to a constraint condition.
    The attractiveness of some destinations in recreational traffic can even be measured by
    means of their attributes if capacity impacts do not play a role. For example, the structural
    potential of a nearby recreational area can be determined by its forest. During trip distribution this attractiveness is to impact as potential of the destination zone, but no constraints are linked herewith because there is neither a minimum number of persons seeking
    recreation nor do visitors go to other places, because the "capacity" of the forest is fully
    exhausted.
    In table 45, table 46 and 4.2.2.2 the calculation formulas are listed up separately for the cases
    for which they differ.
    Step 1

    Home trips H

    Step 2

    Production Q, Qmax

    Step 3

    Total volume V

    PTVGROUP

    151

    4.2.2.2 EVA trip generation

    Step 4

    Attraction Z, Zmax

    Table 45: Trip generation in EVA model: OD type 1

    152

    Step 1

    Home trips H

    Step 2

    Attraction Z, Zmax

    PTVGROUP

    4.2.2.2 EVA trip generation


    Step 3

    Total volume V

    Step 4

    Production Q, Qmax

    Table 46: Trip generation in EVA model: OD type 2


    Step 1

    Home trips H

    Step 2

    Total volume V

    Step 3

    Production Q, Qmax

    Attraction Z, Zmax

    PTVGROUP

    153

    4.2.2.2 EVA trip generation

    Table 47: Trip generation in EVA model: OD type 3


    e

    Index of a zone producing trips (origin zone)

    Index of a zone being origin of trips

    Index of a zone being destination of trips

    Index of a structural property

    Index of a person group

    Index of a demand stratum

    Number of zones in study area

    MRepc

    Mobility rate of person group p per time interval

    ERisc

    Production rate of structural property s per time interval

    BPep

    Number of persons per person group p

    SG

    Structural property

    uepc

    Factor of trips realized study area-internally

    visc

    Structural property factor effective for study area-internal traffic

    Hepc

    Home trips (expected value) of person group p

    Hec

    Home trips (expected value) total

    Qic

    Production (expected value)

    Attraction (expected value)

    jc

    Qicmax

    Maximum possible production

    Zjcmax

    Maximum possible attraction


    Factor for upper or lower limit of production
    Factor for upper or lower limit of attraction

    154

    Qicpot

    Potential for origin traffic

    Zjcpot

    Potential for destination traffic

    Vc

    Total volume (expected value)

    fc

    Factor, which takes the compliance of the total constraint

    PTVGROUP

    4.2.2.2 EVA trip generation

    for the calculation of the zones traffic volume into consideration


    Qic*, Zjc*

    Ancillary parameters for balancing (see below)

    Table 48: Explanation of variables and indexes used


    When analyzing the passenger demand flows it turns out that certain activity chains dominate
    in the course of a day. So, for example, the chain of H W P H occurs more often than the
    chain of H P W H. With this, imbalances in the respective demand stratum pairs arise (for
    example HW compared to WH) that are expressed in mobility or production rates. Consequently, when calculating the total production of a certain zone i across all demand strata,
    this sum does generally not correspond to the total attraction. This, however, should be the
    case for a period considered closed with regard to traffic. Hence, in the EVA model, the production or attraction of a selected ca demand stratum of the type 3 (mostly Others Others, OO)
    is modified, so that the total production equals the total attraction across all demand strata.
    This procedure is called balancing (see "EVA trip distribution and mode choice" on page 165).
    Balancing can either be performed after trip generation or trip distribution and mode choice. It
    takes place after trip generation if the following conditions are fulfilled.
    All constraints (except those of demand stratum ca) are hard.
    The total volume in ca is higher than the difference between production and attraction that
    needs to be balanced.
    All modes are interchangeable.
    Balancing after trip generation takes place in three steps.
    1. Calculation of total production and total attraction for all demand strata except ca.

    ;
    2. Calculation of the demand to be compensated of all zones i.
    ;
    3. Correction of traffic volume in ca, whereby
    and
    from the formulas in table 45, table 46 and 4.2.2.2.

    are "preliminary" values taken

    If there are non-interchangeable modes, you need to perform the balancing procedure for
    each of them individually. Then you perform a single balancing procedure for the sum of all
    interchangeable modes. This, however, is only possible during distribution and mode choice.

    PTVGROUP

    155

    4.2.2.2 EVA trip generation


    The following example will illustrate the method. For simplification it is limited to five demand
    strata covering all origin-destination types.
    Activity
    No.

    Code

    OD type

    Person group

    Origin

    Destination

    Origin zone

    HW

    Home

    Work

    Employees

    HO

    Home

    Others

    Inhabitants

    WH

    Work

    Home

    Employees

    OH

    Others

    Home

    Inhabitants

    OO

    Others

    Others

    Inhabitants

    Relevant structural potential


    No.

    Origin zone

    Destination zone

    Code
    HW

    OD type
    1

    Like home

    Jobs

    HO

    Like home

    Jobs in tertiary sector and


    inhabitants

    WH

    Jobs

    Like home

    OH

    Jobs in tertiary sector and


    inhabitants

    Like home

    OO

    Jobs in tertiary sector and


    inhabitants

    Jobs in tertiary sector and


    inhabitants

    Table 49: Example data for demand strata in an EVA model


    The model covers 18 zones, 10 of which belong to the actual study area (type 1) and 8 zones
    form a cordon around them (type 2). The zones of type 1 feature study area factors of 1.0,
    those of type 2 of 0.9. The relevant zone attributes are set as follows.
    Zone

    156

    Type

    Inhabitants

    Employees

    Jobs

    Jobs
    tertiary

    7,000

    3,000

    2,000

    1,100

    10,500

    5,500

    7,000

    4,500

    7,000

    3,000

    2,000

    1,300

    5,000

    2,000

    1,700

    1,000

    3,000

    1,200

    2,500

    1,600

    2,000

    900

    1,600

    1,000

    500

    200

    2,000

    1,200

    5,000

    2,000

    1,000

    600

    PTVGROUP

    4.2.2.2 EVA trip generation


    Zone

    Type

    Inhabitants

    Employees

    Jobs

    Jobs
    tertiary

    7,000

    3,100

    2,500

    1,400

    10

    5,000

    2,000

    1,500

    1,000

    11

    3,500

    1,200

    1,000

    600

    12

    3,000

    1,100

    1,000

    600

    13

    2,500

    1,000

    1,000

    600

    14

    1,500

    700

    500

    100

    15

    1,500

    600

    500

    100

    16

    2,000

    900

    1,000

    600

    17

    2,000

    800

    500

    300

    18

    2,000

    800

    500

    300

    Table 50: Example data for zone attributes in the EVA demand model (value of the structural
    properties)
    Depending on demand stratum and zone type the following mobility rates are applicable (trips
    per person in relevant person group).
    Zone type

    HW

    HO

    WH

    OH

    OO

    0.7800

    0.9000

    0.6200

    0.9000

    0.6000

    0.8100

    0.9000

    0.6400

    0.9000

    0.6000

    Table 51: Example data for mobility rates in the EVA demand model
    The production rates of the structural properties equally depend on demand stratum and zone
    type.
    Demand stratum

    Structural property

    Zone type 1

    Zone type 2

    1.00

    1.00

    0.50

    0.50

    Jobs in tertiary sector 0.50

    0.50

    1.00

    1.00

    HW
    HO

    Inhabitants

    WH
    OH
    OO

    Inhabitants

    0.50

    0.50

    Jobs in tertiary sector 0.50

    0.50

    Inhabitants

    0.50

    0.50

    Jobs in tertiary sector 0.50

    0.50

    Table 52: Example data for production rates in the EVA demand model

    PTVGROUP

    157

    4.2.2.2 EVA trip generation


    All demand strata feature hard constraints. This results in the productions and attractions of the
    demand strata displayed in the following table, from the formulas in table 45, table 46 and
    4.2.2.2. For clarification the respective step of the calculation process is indicated on top of
    each column.
    H = Home trips
    Q = Production
    Z = Attraction
    QP = Structural potential origin
    ZP = Structural potential destination
    Demand stratum

    HW

    Person groups or structural property

    Home

    Origin

    Employees

    Like home

    Destination
    Jobs

    Zone

    Zone Type

    ZP

    2,340

    2,340

    2,000

    1,578

    4,290

    4,290

    7,000

    5,523

    2,000

    1,578

    Calculation step

    2,340

    2,340

    1,560

    1,560

    1,700

    1,341

    936

    936

    2,500

    1,972

    702

    702

    1,600

    1,262

    2,000

    1,578

    156

    156

    1,560

    1,560

    1,000

    789

    2,418

    2,418

    2,500

    1,972

    10

    1,560

    1,560

    1,500

    1,183

    900

    710

    11

    875

    875

    12

    802

    802

    900

    710

    13

    729

    729

    900

    710

    14

    510

    510

    450

    355

    450

    355

    15

    437

    437

    16

    656

    656

    900

    710

    17

    583

    583

    450

    355

    18

    583

    583

    450

    355

    23,038

    23,038

    29,200

    23,038

    Total

    Table 53: Sample computation of the production and attraction rates for the demand stratum
    HW
    158

    PTVGROUP

    4.2.2.2 EVA trip generation


    Demand stratum

    HO

    Person groups or structural property


    Calculation step

    Home

    Origin

    Destination

    Inhab.

    Like
    home

    3.1

    3.2

    Jobs in tertiary sector and inhabitants

    Zone

    Zone Type

    ZP Inh.

    ZP Jobs
    tert

    ZP Total

    6,300

    6,300

    3,500

    550

    4,050

    5,796

    9,450

    9,450

    5,250

    2,250

    7,500

    10,733

    6,300

    6,300

    3,500

    650

    4,150

    5,939

    2,500

    500

    3,000

    4,293

    4,500

    4,500

    2,700

    2,700

    1,500

    800

    2,300

    3,292

    1,800

    1,800

    1,000

    500

    1,500

    2,147

    450

    450

    250

    600

    850

    1,216

    2,500

    300

    2,800

    4,007

    4,500

    4,500

    6,300

    6,300

    3,500

    700

    4,200

    6,011

    10

    4,500

    4,500

    2,500

    500

    3,000

    4,293

    11

    2,835

    2,835

    1,575

    270

    1,845

    2,640

    1,350

    270

    1,620

    2,318

    12

    2,430

    2,430

    13

    2,025

    2,025

    1,125

    270

    1,395

    1,996

    14

    1,215

    1,251

    675

    45

    720

    1,030

    15

    1,215

    1,251

    675

    45

    720

    1,030

    900

    270

    1,170

    1,674

    16

    1,620

    1,620

    17

    1,620

    1,620

    900

    135

    1,035

    1,481

    18

    1,620

    1,620

    900

    135

    1,035

    1,481

    61,380

    61,380

    34,100

    8,790

    42,890

    61,380

    Sum

    Table 54: Sample computation of the production and attraction rates for the demand stratum
    HO
    Demand stratum

    WH
    Home

    PTVGROUP

    Origin

    Like home

    Person groups or structural property


    Calculation step

    Destination

    Jobs
    3

    159

    4.2.2.2 EVA trip generation


    Zone

    Zone Type

    QP

    1,860

    1,860

    2,000

    1,253

    7,000

    4,384

    3,410

    3,410

    1,860

    1,860

    2,000

    1,253

    1,240

    1,240

    1,700

    1,065

    744

    744

    2,500

    1,566

    1,600

    1,002

    558

    558

    124

    124

    2,000

    1,253

    1,240

    1,240

    1,000

    626

    1,922

    1,922

    2,500

    1,566

    1,500

    939

    10

    1,240

    1,240

    11

    691

    691

    900

    564

    12

    634

    634

    900

    564

    13

    576

    576

    900

    564

    450

    282

    14

    403

    403

    15

    346

    346

    450

    282

    16

    518

    518

    900

    564

    17

    461

    461

    450

    282

    461

    461

    450

    282

    18,288

    18,288

    29,200

    18,288

    18

    Total

    Table 55: Sample computation of the production and attraction rates for the demand stratum
    WH
    Demand stratum

    OH

    Person groups or structural property

    Destination

    Inhab.

    Like home

    Origin
    Jobs in tertiary sector and inhabitants

    3.1

    3.2

    Zone

    Zone Type

    QP Inh.

    QP Jobs
    tert

    QP Total

    6,300

    6,300

    3,500

    550

    4,050

    5,796

    5,250

    2,250

    7,500

    10,733

    3,500

    650

    4,150

    5,939

    Calculation step

    160

    Home

    9,450

    9,450

    6,300

    6,300

    PTVGROUP

    4.2.2.2 EVA trip generation


    4

    4,500

    4,500

    2,500

    500

    3,000

    4,293

    2,700

    2,700

    1,500

    800

    2,300

    3,292

    1,000

    500

    1,500

    2,147

    1,800

    1,800

    450

    450

    250

    600

    850

    1,216

    4,500

    4,500

    2,500

    300

    2,800

    4,007

    6,300

    6,300

    3,500

    700

    4,200

    6,011

    2,500

    500

    3,000

    4,293

    10

    4,500

    4,500

    11

    2,835

    2,835

    1,575

    270

    1,845

    2,640

    12

    2,430

    2,430

    1,350

    270

    1,620

    2,318

    13

    2,025

    2,025

    1,125

    270

    1,395

    1,996

    675

    45

    720

    1,030

    14

    1,215

    1,215

    15

    1,215

    1,215

    675

    45

    720

    1,030

    16

    1,620

    1,620

    900

    270

    1,170

    1,674

    17

    1,620

    1,620

    900

    135

    1,035

    1,481

    1,620

    1,620

    900

    135

    1,035

    1,481

    61,380

    61,380

    34,100

    8,790

    42,890

    61,380

    18

    Sum

    Table 56: Sample computation of the production and attraction rates for the demand stratum
    OH
    Demand stratum

    OO
    Home

    Origin
    Jobs in tertiary sector and inhabitants

    Person groups or structural property


    Calculation step

    2.1

    2.2

    2.3

    Zone

    Zone Type

    QP Inh.

    QP Jobs
    tert

    QP Total

    4,200

    3,500

    550

    4,050

    3,864

    6,300

    5,250

    2,250

    7,500

    7,156

    4,200

    3,500

    650

    4,150

    3,959

    3,000

    2,500

    500

    3,000

    2,862

    1,800

    1,500

    800

    2,300

    2,194

    1,200

    1,000

    500

    1,500

    1,431

    300

    250

    600

    850

    811

    3,000

    2,500

    300

    2,800

    2,671

    PTVGROUP

    161

    4.2.2.2 EVA trip generation


    4,200

    3,500

    700

    4,200

    4,007

    3,000

    2,500

    500

    3,000

    2,862

    11

    1,890

    1,575

    270

    1,845

    1,760

    12

    1,620

    1,350

    270

    1,620

    1,546

    13

    1,350

    1,125

    270

    1,395

    1,331

    14

    810

    675

    45

    720

    687

    15

    810

    675

    45

    720

    687

    16

    1,080

    900

    270

    1,170

    1,116

    17

    1,080

    900

    135

    1,035

    987

    18

    1,080

    900

    135

    1,035

    987

    42,890

    40,920

    10

    Total

    40,920

    34,100

    8,790

    Table 57: Sample computation of the production and attraction rates for the demand stratum
    OO (1)
    Demand stratum

    OO
    Destination
    Jobs in tertiary sector and inhabitants

    Person groups or structural property


    3.1

    3.2

    3.3

    Zone

    Zone Type

    ZP Inh.

    ZP Jobs tert

    ZP Total

    3,500

    550

    4,050

    3,864

    5,250

    2,250

    7,500

    7,156

    3,500

    650

    4,150

    3,959

    2,500

    500

    3,000

    2,862

    1,500

    800

    2,300

    2,194

    1,000

    500

    1,500

    1,431

    250

    600

    850

    811

    Calculation step

    162

    2,500

    300

    2,800

    2,671

    3,500

    700

    4,200

    4,007

    10

    2,500

    500

    3,000

    2,862

    11

    1,575

    270

    1,845

    1,760

    12

    1,350

    270

    1,620

    1,546

    13

    1,125

    270

    1,395

    1,331

    14

    675

    45

    720

    687

    PTVGROUP

    4.2.2.2 EVA trip generation


    15

    675

    45

    720

    687

    16

    900

    270

    1,170

    1,116

    17

    900

    135

    1,035

    987

    18

    900

    135

    1,035

    987

    34,100

    8,790

    42,890

    40,920

    Total

    Table 58: Sample computation of the production and attraction rates for the demand stratum
    OO (2)
    Since all demand strata feature hard constraints, balancing can be performed immediately
    after trip generation. First of all the total origin and destination traffic of each zone and of the
    demand strata HW, HO, WH, OW is calculated and the resulting differences are compensated
    in the OO demand stratum.
    Note: Note that neither total origin and nor total destination traffic of this demand stratum
    change.

    Differences

    Total HW+HO+WH+OH

    PTVGROUP

    Zone

    16,800

    14,422

    2,378

    26,600

    31,373

    4,773

    16,800

    14,709

    2,091

    11,800

    10,993

    807

    7,080

    10,121

    3,041

    4,860

    6,558

    1,698

    1,180

    5,263

    4,083

    11,800

    9,429

    2,371

    16,940

    15,559

    1,381

    10

    11,800

    10,710

    1,090

    11

    7,236

    6,555

    681

    12

    6,296

    5,911

    385

    13

    5,355

    5,267

    88

    14

    3,344

    2,698

    646

    15

    3,213

    2,698

    515

    16

    4,415

    4,623

    208

    17

    4,284

    3,599

    685

    18

    4,284

    3,599

    685

    Total

    164,086

    164,086

    13,804

    13,804

    163

    4.2.2.2 EVA trip generation


    Table 59: Sample computation for balancing (1)
    OO before balancing

    OO after balancing

    Zone

    3,864

    3,864

    2,561

    4,938
    4,742

    7,156

    7,156

    9,515

    3,959

    3,959

    2,624

    4,715

    2,862

    2,862

    1,897

    2,704

    2,194

    2,194

    4,495

    1,454
    948

    1,431

    1,431

    2,646

    811

    811

    4,621

    537

    2,671

    2,671

    1,770

    4,141

    4,007

    4,007

    2,655

    4,036
    2,987

    10

    2,862

    2,862

    1,897

    11

    1,760

    1,760

    1,166

    1,848

    12

    1,546

    1,546

    1,024

    1,409

    13

    1,331

    1,331

    882

    970
    1,101

    14

    687

    687

    455

    15

    687

    687

    455

    971

    16

    1,116

    1,116

    948

    740

    17

    987

    987

    654

    1,339
    1,339
    40,920

    18

    987

    987

    654

    Sum

    40,920

    40,920

    40,920

    Table 60: Sample computation for balancing (2)


    The results of operation EVA trip generation are stored in zone attributes.

    164

    Attribute

    Subattribute

    Meaning and range of values

    HomeTrips

    Demand stratum

    Home trips for demand stratum


    Range: floating point number

    ProductionsTarget

    Demand stratum

    Productions for demand stratum, before taking


    account of constraints
    Range: floating point number

    AttractionsTarget

    Demand stratum

    Same for attractions


    Range: floating point number

    Productions

    Demand stra-

    Productions for demand stratum after taking

    PTVGROUP

    4.2.2.3 EVA trip distribution and mode choice


    Attribute

    Attractions

    Subattribute

    Meaning and range of values

    tum

    account of constraints and balancing


    Note
    This attribute is only available after EVA trip generation if all demand strata feature hard constraints,
    otherwise after EVA trip distribution / mode choice
    only.
    Range: floating point number

    Demand stratum

    Same for attractions


    Range: floating point number

    Table 61: Zone attributes with results of trip generation of the EVA demand model
    4.2.2.3

    EVA trip distribution and mode choice


    In gravity models, trip distribution or destination choice is made according to the bilinear
    approach (for example Kirchhoff 1970), using various evaluation or utility functions Wij.

    Hereby Tij is the number of trips from i to j, Wij is the cost function for the trip from i to j, Qi is the
    production of zone i and Zj is the attraction of zone j. The factors fqi, fzj are calculated so that
    productions and attractions are kept as marginal sums.
    The EVA model generalizes this approach of a simultaneous trip distribution and mode choice
    to a trilinear model.

    Here, index k is the mode (means of transport) and Wijk assesses the costs for the trip from i to j
    by modes k. For each demand stratum c there is a separate equation system to be solved inde-

    PTVGROUP

    165

    4.2.2.3 EVA trip distribution and mode choice


    pendently. For more clarity index c has been dropped for all variables in the problem formulations above.
    For the trilinear case, besides origin and destination traffic, the total number VK k of trips with
    mode k is required. There are two possibilities.
    If EVA trip distribution and mode choice for the analysis case is performed, which means
    without having run a pre-calculation for the same study area, specify the modal split as
    input data.
    If, however, a forecast case is calculated, the modal split of the analysis case can be reused. You thus assume that the modal split may change on single relations, but modal
    split of the whole model (including all relations), however, remains unchanged.
    The problem formulation is applicable in case of hard constraints. For weak, elastic or open
    constraints equations will be replaced by inequations in the side conditions or a side condition
    will be dropped completely. This will be dealt with when describing the problem solutions.
    The models can be justified by the probability theory using Bayesaxiom or the information
    gain minimization. Both ways lead to the same result.
    Minimizing the gain of information has the target that the deviations from a priori assessments
    of trip relations which would lead to the actually desired trips road users have to experience
    are as minor as possible, but which have become necessary due to the constraints of the system.
    The demand matrix T can be interpreted as the solution to the convex optimization task

    with
    taking account of the constraints. The solution is the trilinear equation system previously determined.
    The parameter I represents the information gained through the replacement of distribution wijk
    (solely determined by the weighting matrix) by distribution pijk (additionally derived from marginal totals).
    Weighting probabilities (impedance functions)
    In general, the total trips costs include various factors (e.g. journey time, egress/access time,
    monetary costs, number of passenger transfers etc.). In the EVA model, these are called
    assessment types. In the EVA model the different assessments of each assessment type are
    transformed separately by a utility function and then multiplied.
    If caijk is the assessment of type a of a trip from i to j by mode k, then the following applies:
    where
    166

    PTVGROUP

    4.2.2.3 EVA trip distribution and mode choice

    here M ijk stands for the availability of mode k on OD pairs (i,j) and C ijk stands for the capacity
    utilization of mode k on (i,j). a, aand aare the predefined assessment types: journey time,
    competing walk time and external weighting matrix. A is the number of user-defined assessment types.
    Mijk and Cijk are defined independently from the demand stratum as follows:
    OD type

    Definition of Mijk and Cijk

    Type 1

    Mijk = mk(i) for all j, i.e. value of zone attribute mk set for source zone i
    Cijk = ck(j) for all i, i.e. value of zone attribute ck set for destination zone j

    Type 2

    Mijk = mk(j) for all i, i.e. value of zone attribute mk set for destination zone j
    Cijk = ck(i) for all j, i.e. value of zone attribute ck set for source zone i

    Type 3

    without accounting for home zone


    Mijk = 1 for all i,j,k
    Cijk = ck(i) ck(j)
    including accounting for home zone

    Cijk = ck(i) ck(j)


    whereby hn stands for the home trips of zone n,
    represents the product
    matrix from the top, but the predefined assessment type External weighting
    matrix is not included in the product:

    Table 62: Definition of the mode availability and capacity utilization according to the OD type
    For demand strata of the origin-destination type 3 (which are calculated accounting for the
    home zone), the assessment type External weighting matrix is used to produce a specific
    weighting between zones and modes. This weighting has an immediate impact on the total
    product, since it is not part of the scaling using home zones, as in the formula for Mijk . In all
    other cases, this assessment type has the same effect as a user-defined one.
    You can use different function types as f a evaluation functions. All distribution functions of the
    gravity model can be taken, but additionally the EVA1, EVA2, Schiller and Box-Tukey functions
    (see "Gravity model calculation" on page 188)too.

    PTVGROUP

    167

    4.2.2.3 EVA trip distribution and mode choice


    EVA1
    where
    EVA2

    Schiller

    Logit
    Kirchhoff
    Box-Cox

    Box-Tukey
    where
    Combined
    TModel

    None

    f(x) = x

    Table 63: Function types for evaluation


    In practice particularly the functions EVA1 and EVA2 have proved to be suitable. The EVA1
    functions are monotonously falling with f(w)1 for w0. Some of them have been illustrated
    in illustration 55. Their parameters can be interpreted geometrically.
    a

    Parameter marking the horizontal asymptote of function (w), thus influencing


    the degree of approximation of the function f(w) to the w asymptote.

    Parameter influencing the degree of approximation to the horizontal F(w)=1 in


    the proximity of low assessment

    Parameter influencing the slope of the function f(w)

    b/c

    Position of the inflection point WP=F/G of function (w) where the function (w)
    features the greatest rise or the highest "impedance sensitivity"

    Table 64: Parameters of the evaluation function EVA1

    168

    PTVGROUP

    4.2.2.3 EVA trip distribution and mode choice


    The related elasticity functions are determined by

    The elasticity function


    is defined as the
    limit of the quotient of the relative variation of the function f and the relative variation of the
    impedance w.
    It is obvious that the elasticity functions first take values near zero for low impedances, then for
    a limited range in which the impedance sensitivityis at its highest take various values, but all
    far from zero and for high impedances approximatethe limit of -E.
    Thus, this curve very much differs from the constant or linear elasticity functions of simple
    power and exponential functions. Therefore, this type of function allows the adaptation to
    various basic weighting situations (person groups, trip purposes, means of transport etc.). In
    the range of low assessment or utility the weighting probability should be almost one, drop further in the clearly noticeable range of assessment and utility which is relevant for the respective type of traffic or purpose before asymptotically approximating zero. For example, the
    assessment in the proximity of or in smaller towns plays a minor or no role at all for the road
    users when choosing the destination or the means of transport (here mainly the random model
    with WP = 1 is applicable).

    PTVGROUP

    169

    4.2.2.3 EVA trip distribution and mode choice

    Illustration 55: EVA1 function dependent on impedance w


    The EVA2 function has the following parameters.
    a, b ...

    Exponents whose product determines the asymptotic behavior for high impedance values. For b > 1 the curve is similar to that of the EVA function (1).

    c ...

    Scale parameter for impedance values.


    applies.

    Table 65: Parameters of the evaluation function EVA2


    The illustration 56 shows the influence of a and b on the progression of the function. The two
    other parameters are both kept constant.

    170

    PTVGROUP

    4.2.2.3 EVA trip distribution and mode choice

    Illustration 56: EVA2 function dependent on the parameters a and b


    The Schiller function is a special case of the EVA2 function, however, with one parameter less.
    As the first applications in practice have shown, the function can also be adapted sufficiently
    well enough to observed data. Due to the lower number of parameters the calibration effort is
    by far lower than for EVA2.
    Problem solution 1: The trilinear FURNESS method
    The mostly investigated method for solving bilinear problems in technical literature is named
    after K. P. Furness (Furness 1962, 1965). However, in fact, Bregman had already applied this
    method in the thirties (Bregman 1967a, 1967b). It can be generalized and transferred directly
    to the trilinear case.
    After you have specified start values for the trilinear FURNESS method

    during iteration step p (p=1,2,), the system calculates approximations for fqi, fzj and fak as follows.

    (i = 1,,m)

    (j = 1,,n)

    (k = 1,,K).

    PTVGROUP

    171

    4.2.2.3 EVA trip distribution and mode choice


    For convergence of the method (towards the solution of the trilinear problem), the condition for
    unique solvability of the optimization problem is necessary and sufficient, i.e. existence of a
    matrix Tijk that matches the constraints and for which Tijk = 0 is true for all pairs (i,j) with Wij = 0.
    This condition is fulfilled when Wij > 0 is true for all (i,j), since then the matrix with elements
    (the matrix that corresponds to the random model) can be chosen as a feasible solution. For this special case A. W. Evans provided a convergence proof that also allows
    for a (however rough) estimation of the convergence rate (Evans 1970). The practical experience has shown that the method quickly converges in most application cases.
    Problem solution 2: The trilinear Multi method
    Another possibility to solve the problem is to set separate fixed point equations for the vectors
    fqi , fz j and fa k and use them to derive rules for determining successive approximations for
    these vectors (Schnabel 1997). The Multi-Procedure can also be extended to the three dimensional case (see "Projection" on page 203). Approximations for the solution of the trilinear problem then can be determined according to the following iteration rule.

    (p = 1, 2,)
    with

    172

    PTVGROUP

    4.2.2.3 EVA trip distribution and mode choice

    Strictly speaking the method presented solves the problem with hard constraints only. If some
    constraints are weak or elastic, there will be an optimization problem with inequations as side
    conditions instead of equations. At the example of weak constraints it is illustrated how the problem and correspondingly its solution alters (according to Schiller 2004). It is assumed that a
    demand stratum shows weak constraints on the destination side, which means attraction calculated by trip generation constitutes an upper limit. Thus, the trilinear problem changes into

    under the constraints

    The procedure for multi- problem solving is mostly identical with the constraint equation
    method, except that zj(p) and zzj(p) are calculated differently.

    PTVGROUP

    173

    4.2.3 Activity chain based model (tour-based model)


    If some demand strata do not feature hard constraints, not only has the method to be adapted
    but also balancing has to be made up.
    Note: Differences in marginal sums can only be balanced after trip generation if all
    demand strata feature hard constraints.
    In that case first of all the trilinear problem is solved for all demand strata except for the balancing one . This results in the total productions and attractions of the zones covering these
    demand strata and all modes. According to the formula for calculating productions and attractions (see "EVA trip generation" on page 146) the productions and attractions of the balancing
    demand stratum are modified. Finally Visum runs trip distribution and mode choice for this last
    demand stratum, too.
    The proceeding assumes that differences have to be balanced within the framework of the
    total volume. This is only true if all modes are exchangeable, which means if they can be used
    alternatively in a closed trip chain. If at least one mode cannot be exchanged, a second phase
    begins after the total balancing in which calculations are performed for each non- exchangeable mode separately and for all exchangeable modes jointly. Hereby, the productions and
    attractions of the respective modes are calculated over the non-balancing demand strata,
    their differences are compensated by an adaptation of the demand of the balancing demand
    stratum, and based on that modified demand Trip distribution and Mode choice are calculated
    for the last time. For non-exchangeable modes this last step corresponds to a simple mode
    choice.
    The implementation of the EVA model for trip distribution and mode choice has been established in two separate operations. EVA Weighting operation uses skim matrices to calculate
    the weighting matrices W ijk (one weighting matrix each per demand stratum). During EVA trip
    distribution and Mode choice, the equation systems for determining the demand matrices are
    set up according to the constraints of the demand strata and solved by applying one of the
    above-described methods. The result of the operation is one demand matrix per demand stratum and mode. You can also display the balance factors for productions and attractions fqi and
    fzj, that result from the equation system. The balance factor for mode choice fak is calculated for
    analysis, but not for forecast scenarios.
    The EVA weighting procedure can be applied to all active OD pairs or only to those OD pairs
    whose origin or destination zone are active. This allows you to perform an analysis based on
    filtering by several OD pairs with different parameters. This option is not available for combined distribution and mode choice, as for successful balancing, all traffic types need to be
    accounted for in one step.

    4.2.3

    Activity chain based model (tour-based model)


    The tour-based model is a disaggregated, behavior-oriented demand model which allows the
    planner to include all kinds of data relating to socio-demography and traffic policy issues. The
    tour-based model calculates three logical work units.
    1. Trip generation (calculating the home trip)
    2. Trip distribution (determining the trip destination)
    3. Mode choice

    174

    PTVGROUP

    4.2.3.1 Tour-based data model


    These three logical units are not processed separately in succession by the tour-based model,
    but are interlocked. Especially steps 2 and 3, Trip distribution and Mode choice are carried out
    simultaneous in a single procedure. In all three work units two important concepts have been
    implemented for the tour-based model: Calculation on the basis of groups with homogeneous
    behavior and activity chains.
    4.2.3.1

    Tour-based data model


    The tour-based model is based on the assumption that external activities cause mobility. In the
    following examples previously defined activities are being used (see "Activities, activity pairs,
    activity chains" on page 132).
    An activity chain describes a sequence of typical activities during a person's day. An example
    would be: Home Work Shopping Home (HWOH). Such a sequence of activity pairs
    implies trips, in this example here three different trips: HW, WO, OH. The average mobility program of persons is described by activity chains for the tour-based model.
    You can find the demand object activity chain attributes in the general description of the
    demand objects (see "Activities, activity pairs, activity chains" on page 132).
    Some changes in the demand objects, which are especially necessary for the tour-based
    model, are described below.
    Note: In a Visum-tour-based demand model, a demand stratum is specified by exactly
    one person group (e.g. E+c) and one activity chain (e.g. HWOH). In the other demand
    models, several person groups can be assigned to one demand stratum.
    Changes to activities in the tour-based model
    Each activity from the activity chain, apart from the home activity, has to be assigned to exactly
    one structural property, whose value flows in as target potential into the trip distribution.
    The following table shows examples for activities and respective structural properties.
    Activity

    Structural property

    Structural property value = target potential

    Work ('W')

    Jobs

    Number of jobs

    Shopping ('O')

    Shopping possibilities

    Retail sales floor

    Recreation ('R')

    Recreational facilities

    Number of mentions of the zone as recreation


    destination in a household survey

    School ('S')

    School places

    Number of school places (up to 18 years)

    University ('U')

    University places

    Number of university places

    Table 66: Examples of activities and their structural properties


    You can specify whether a possible destination-binding can be considered for trip distribution,
    per activity. If desired, a constraint for the destination side (for example hard, weak, elastic,
    open) can be defined analog to the EVA demand model using two real-valued factors ConstraintMinFactorDest and ConstraintMaxFactorDest. Depending on the constraint on origin

    PTVGROUP

    175

    4.2.3.2 Tour-based model - trip generation


    and destination side, the doubly-constrained trip distribution is calculated for each activity
    transfer.
    This results in the following new attributes:
    Type of
    demand
    object

    Attribute and range of values Meaning

    Activity

    StructuralPropertiesCodes
    Range: set of structural properties

    Reference to the activity relevant structural


    properties

    Activity

    ConstraintDest
    Range: bool {0, 1}

    Destination-sided coupling during trip distribution (yes / no). Home activity always
    =1.

    Activity

    ConstraintMinFactorDest /
    ConstraintMaxFactorDest
    Range: floating point number
    0

    Factor for the lower or upper limit of the


    constraint on destination side, if ConstraintDest = 1.
    For home activity, both factors are always
    = 1.0.

    Table 67: Activity attributes in the tour-based model


    Changes to activity pairs in the tour-based model
    The tour-based model offers a hourly calculation of the demand. This calculation requires as
    input, proportional time series which are defined separately per activity pair and person group.
    This results in the following new attribute:
    Type of demand Attribute and range of
    object
    values
    Activity pairs

    Subattribute

    TimeSeriesNo
    Person group
    Range: set of standard time
    series (see "Time series" on
    page 131)

    Meaning
    Reference to a standard time series, which
    has to be proportional

    Table 68: Attribute of an activity pair in the tour-based model


    4.2.3.2

    176

    Tour-based model - trip generation


    Trip generation uses a list of group-specific activity chains, which for example, can be determined from the sample of the KONTIV 89 (EMNID 1991) by applying a PTV company optimization procedure for activity chains. For each activity chain probabilities of your daily
    practice have to be specified for each person group. The following table (to calculate the probabilities, these values must be divided by 100) contains examples of activity chain percentages for each person group.

    PTVGROUP

    4.2.3.2 Tour-based model - trip generation


    E+c

    E-c

    NE+c

    NE-c

    Appren Stud

    SPup

    PPup

    Child

    HWH

    74.25

    62.60

    8.18

    2.82

    33.48

    11.08

    1.92

    0.30

    0.00

    HSH

    0.00

    0.00

    0.00

    0.00

    47.57

    0.00

    0.00

    0.00

    0.00

    HPH

    17.42

    25.94

    60.60

    62.93

    12.37

    23.91

    12.99

    9.08

    0.00

    HRH

    27.03

    25.32

    52.50

    39.74

    38.08

    37.33

    40.12

    38.67

    0.00

    HPH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    74.99

    0.00

    HSH

    0.00

    0.00

    0.00

    0.00

    0.00

    45.19

    0.00

    0.00

    0.00

    HOH

    0.90

    1.82

    0.96

    0.47

    0.00

    0.00

    80.48

    0.00

    0.00

    HWWH

    3.12

    0.85

    0.13

    0.06

    0.52

    0.16

    0.11

    0.00

    0.00

    HWOH

    4.67

    7.05

    0.96

    0.33

    1.79

    0.80

    0.37

    0.00

    0.00

    HWRH

    1.64

    1.46

    0.18

    0.02

    0.86

    1.56

    0.09

    0.00

    0.00

    HWOH

    0.08

    0.04

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    HSWH

    0.00

    0.00

    0.00

    0.00

    0.16

    0.00

    0.00

    0.00

    0.00

    HSSH

    0.00

    0.00

    0.00

    0.00

    0.11

    0.00

    0.00

    0.00

    0.00

    HSPH

    0.00

    0.00

    0.00

    0.00

    0.97

    0.00

    0.00

    0.00

    0.00

    HSRPH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.23

    0.00

    0.00

    0.00

    HSRRH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.55

    0.00

    0.00

    0.00

    HSRSH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.76

    0.00

    0.00

    0.00

    HSSOH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.17

    0.00

    0.00

    0.00

    HSSSH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.12

    0.00

    0.00

    0.00

    HOWWH

    0.01

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    HOWPH

    0.01

    0.04

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    HOWRH

    0.01

    0.00

    0.00

    0.00

    0.00

    0.00

    0.03

    0.00

    0.00

    HOWOH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.12

    0.00

    0.00

    HOPPH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.25

    0.00

    0.00

    HOPRH

    0.00

    0.00

    0.00

    0.03

    0.00

    0.00

    0.14

    0.00

    0.00

    HOPOH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.04

    0.00

    0.00

    HPRRH

    0.00

    0.00

    0.00

    0.01

    0.00

    0.00

    0.17

    0.00

    0.00

    HOROH

    0.00

    0.00

    0.00

    0.00

    0.00

    0.00

    0.11

    0.00

    0.00

    HOOOH
    0.00
    0.00
    0.00
    0.00
    0.00
    0.00
    0.03
    Table 69: List of the activity chains: mobility rates per person group in %

    0.00

    0.00

    The sum of the probabilities of a person group is often greater than 1.0 (or 100%), because a
    person can complete more than one activity chains one after the other in a day (for example,
    person group E+c first HWH, then HRH).
    The list displayed above, describes an average mobility for persons depending on the group
    they belong to. In the tour-based model, trip generation (i.e. determining the absolute number

    PTVGROUP

    177

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    of activity chains and thus the trips starting from any of the individual zones) is calculated by
    multiplying the inhabitants of each person group with the probabilities of all activity chains.
    Trip generation can be limited to the active zones.
    Thus, in the tour-based model, trip generation (the number of trips created with each activity in
    the activity chain) is determined together with the number of inhabitants and distribution of person groups. The result is saved in the zone attribute Home trips for each demand strata.
    Example of trip generation with the tour-based model
    2,000 employees with a car (E+c) live in zone 1. After the activity chain distribution above, run
    the activity chain HWOH per day with 4.67% probability. This is why there are 2,000 4.67%
    = 93.4 chains of the type HWOH. Consequently, home trips for the demand stratum E+c x
    HWOH add up to 93.4.
    The 2,000 persons in this activity chain produce a total of 3 93.4 = 280.2 trips, namely 93.4
    HW trips and just as many for WO and OH.
    4.2.3.3

    Tour-based model: trip distribution / mode choice combined


    Using tour-based calculation, you can save output matrices with different aggregation levels.
    The demand matrices are calculated from possible combinations of person group, mode, production and attraction activity, and time interval.
    Trip distribution: route links through destination choice according to activities
    Depending on the destination activity of a trip, the tour-based model assigns it to a destination
    zone. This destination zone is chosen depending on several factors.
    The utility matrix, which shows the separation from the origin zone (spatially and trafficwise)
    The utility is inversely proportional to impedance values, such as run times or distances, so
    that the greater the run time or distance to a destination zone, the less its utility.
    The utility matrix may also include the log sum of mode-specific use. In this way, specific
    skims (e.g. PrT journey time or PuT number of transfers) are included in the total utility with
    their share in the respective mode.
    The target potential of the zones competing as destinations
    The impact of utility defined via the utility function parameters for each group and each
    destination activity
    These parameters can be forecast (see "Estimate gravitation parameters (KALIBRI)" on
    page 187)
    This is how a multitude of trip chains is created through each activity chain. The result of trip
    distribution is not only a total traffic matrix, but also a set of all route chains.
    With the destination choice model, the tour-based model needs a target potential Zj for each
    activity. The target potential specifies the quantitative attractiveness of a zone. This target
    potential for each zone j, corresponds to the value of the structural property that belongs to the
    activity (see "Tour-based data model" on page 175).

    178

    PTVGROUP

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    The utility function f(u ij) is pivotal in the destination choice model. It specifies the probability Pij
    with which one of the zones j is selected as destination zone (from all destination alternatives)
    of origin zone i.

    where
    Fij

    Number of trips from zone i to zone j

    Qi

    Productions in zone i

    Pij

    Choice probability of destination j for origin zone i

    Zj

    Target potential in zone j

    Index of zones (with k = the smallest zone number and B = the number of zones)

    whereby uij describes the utility relation ij and the utility function f(u j)) (e.g. of the type Logit)
    can consequently be defined as
    . All other weighting functions of the EVA
    demand model can also be used as utility functions in the tour-based model (see "EVA trip distribution and mode choice" on page 165).
    In this case, the choice of parameter c for every activity is pivotal for destination choice. c
    stands for the influence of utility on the destinations of the respective activity. If c = 0, then the
    utility uij has no influence on the choice of destination. The larger c is, the larger is the impact
    of utility uij on the choice of the destination (see "Gravity model calculation" on page 188).
    Separate function parameters are defined for each combination of group of persons and target
    activity.
    To give you a better idea of what the three main model elements of destination choice, namely
    destination potential, utility function and utility matrix stand for, we will continue with the example we used for trip generation (see "Example of trip generation with the tour-based model" on
    page 178).
    Example of trip generation
    A Logit utility function (
    with parameter c = 0.4) is used to represent the changeovers from and to the individual activities.
    The 93.4 trips of the activity pattern HW have to lead from the origin (zone 1) to the potential
    destination zones, containing jobs. The tour-based model distributes these 93.4 trips to the
    destination zones, according to the previously described destination choice model.

    PTVGROUP

    179

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    To make it easier, let us assume that zone 2 is the only zone with jobs, which therefore has a
    positive destination potential for the activity work. Expressed in numbers this would be approximately Z 1 = 0, Z2 = 100, Z 3 = 0. The tour-based trip distribution formulas produce the following results P11 = 0, P12 = 1 and P13 = 0, and therefore F11 = 0, F12 = 93.4 and F13 = 0. Zone 2
    is therefore the destination of all trips of zone 1.
    Note: The definition of the utility function in this case does not influence the calculation.
    After the activity work, based on zone 2, the probability for the choice of shopping destinations
    is calculated for the subsequent trips WO. It is assumed, that the destination potentials for the
    activity "Shopping" are defined as follows: Z1 = 0, Z2 = 50, Z3 = 50. Based on travel times and
    distances, the utility defined for changeover WO, with the relation 2-2, is twice as high as the
    changeover with the relation 2-3, thus approximately u22 = 2 and u 23 = 1. The tour-based trip
    distribution formulas produce the following results P 21 = 0, P 22 0.6 and P 23 0.4, and therefore F = 0, F 56.0 and F 37.4. 40% of the trips thus lead to zone 3 and 60% to zone
    21
    22
    23
    2 (i.e. trips within the cell).
    Here, multiplication of the destination probability of the work and shopping destinations takes
    place in the system.
    For the last activity pair of the chain, namely PH, destination choice is no longer necessary,
    because zone 1 as a residential district and origin of the first trip of the chain, is also the destination of the last trip of the chain.
    This results in the following transition matrices.
    Matrix F1 for the first activity transfer (Destination activity W)
    Zone

    93.4

    93.4

    Total

    93.4

    93.4

    93.4

    Matrix F2 for the second activity transfer (Destination activity O)


    Zone

    93.4

    93.4

    Total

    56.0

    37.4

    93.4

    56.0

    37.4

    Matrix F3 for the third activity transfer (Destination activity H)

    180

    PTVGROUP

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    Zone

    93.4

    93.4

    Total

    93.4

    56.0

    56.0

    37.4

    37.4

    Summed up, the following total demand matrix applies FG.


    Zone

    280.2

    280.2

    Total

    93.4

    149.4

    37.4

    93.4

    93.4

    149.4

    56.0

    56.0

    37.4

    37.4

    37.4

    Summary of this destination choice example


    HW: 100% leave zone 1 with destination zone 2
    WO: 60% remain in zone 2 and 40% leave zone 2 to zone 3
    OH: 100% return to zone 1.
    The corresponding route chains are as follows:
    1-2-2-1: 93.4 100% 60% 100% = 56.0
    1-2-3-1: 93.4 100% 40% 100% = 37.4
    The following route chains have been created:
    56.0 route chains 1-2-2-1
    37.4 route chains 1-2-3-1
    Notes: The following behavioral aspects should be taken into consideration when you
    define the utility parameters.
    Traffic behavior analyses show, that persons with a car cover greater distances than
    persons without a car. Accordingly, the absolute value of parameter c of the Logit
    function for groups E+c and NE+c have to be smaller than for groups E-c or NE-c.
    This also complies with the empirical perception, to give activity Work a c parameter
    with a low absolute value, rather than for example activity Shopping.
    The tour-based model allows specific utility matrices to be imported for each activity. Combinations of distances and journey times can be used as a basic parameter in utility matrices.
    Note: The absolute value of a destination potential is first of all irrelevant, because it only
    flows into the destination choice model comparatively to the sum of destination potentials
    of all zones. Destination potential " jobs = 1,000" for a zone does not necessarily mean
    that the tour-based model produces 1,000 trips for destination activity work. In fact, the
    destination traffic depends on the product of destination potential and utility function
    value in relation to the other zones.
    PTVGROUP

    181

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    If, however, the absolute value of the destination potential of an activity is very important, as for
    example for the number of jobs, this can flow into the calculation via the Destination-sided
    attraction option. If there are approx. 6,000 jobs in the study area, 1,000 jobs mean there is a
    relative destination potential of 1,000/6,000 = 1/6 for the activity work. If a demand stratum has
    a total of 3,000 home trips, the absolute zone destination potential standardized to the total of
    home trips for this demand stratum is 3 1/6 = 500. This absolute value for the demand stratum
    is used as a constraint in the doubly- constrained gravity model (see "Gravity model calculation" on page 188).
    You can save your trip distribution results in an aggregated form to total demand matrices per
    person group as well as per combination of time interval, mode, origin and destination activity.
    Mode choice: discrete distribution model
    The tour-based demand model has a behavior-oriented concept, which models the following
    aspects of the decision-making of road users.
    The socioeconomic position and the mode availability of the person making the decision
    (by differentiating according to person groups)
    Different attributes of all modes (through the utility model)
    Freedom of choice restrictions within trip chains (by definition of exchangeable and nonexchangeable modes)
    This decision problem is illustrated in a discrete distribution model, which specifies the probability for mode choice in every available route link.
    To do so, the subjective use has to be calculated in dependency of the mode skims (in-vehicle
    time, access and egress times, fare, etc.). If required, you can define several utilities per destination activity.
    This model has the following functional form.

    where
    i, j

    Indices of the traffic zones

    Index of modes (M = total number)

    Pm
    um

    ij

    ij

    Probability of selecting mode m for trip from i to j


    Utility when choosing mode m for trip from i to j

    can e.g. be a Logit utility function and thus be defined as


    . As an alternative, all available types of evaluation functions can be used from the EVA demand method
    as a utility function for the tour-based mode choice (see "EVA trip distribution and mode
    choice" on page 165).

    182

    PTVGROUP

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    As a base parameter for the utility matrices any distance combinations and mode specific
    skims can be used, such as travel times, access and egress times, and fares. You can also
    use the LogSums of mode-specific use as an input parameter.
    Last but not least, we would like to explain the importance of the route chain concept for mode
    choice.
    In Visum the modes are divided into the following groups:
    exchangeable modes (generally walk, passenger and public transport)
    non-exchangeable modes (car, bike)
    The tour-based model calculates a discrete distribution model (for example Logit) when first
    calculating the trip of each route link (for a person group) and chooses one from all modes. If
    the first mode is a non-exchangeable mode, the entire trip chain is maintained independent of
    the attributes of this mode of the successive trip. If an exchangeable mode was selected for the
    first trip, mode choice is carried out for the remaining chain trips, however, only within the
    exchangeable modes.
    Example of mode choice
    We will continue with the example from the trip distribution (see "Example of trip generation"
    on page 179) and will determine the matrices for each activity transfer for the three modes Car
    (C), PuT (X) and Walk (W). Only mode P cannot be exchanged. The set of exchangeable
    (with
    modes X and W in short is also designated with A. A Logit utility function
    parameter c = 0.4) is used again to represent the changeovers from and to the individual activities. The utility matrices um for each mode m are provided by
    uC
    Zone

    Zone

    uX

    uW

    PTVGROUP

    183

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    Zone

    After analyzing the formula above, the following probability matrices apply.
    PC
    Zone

    0.472

    0.526

    0.526

    0.526

    0.472

    0.472

    0.526

    0.472

    0.472

    Zone

    0.316

    0.237

    0.237

    0.237

    0.316

    0.316

    0.237

    0.316

    0.316

    Zone

    0.212

    0.237

    0.237

    0.237

    0.212

    0.212

    0.237

    0.212

    0.212

    PX

    PW

    PA = PX + PW
    Zone

    0.528

    0.474

    0.474

    0.474

    0.528

    0.528

    0.474

    0.528

    0.528

    Interesting are also the probabilities for modes X and W within the exchangeable modes.
    PAX = PX / PA

    184

    PTVGROUP

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    Zone

    0.598

    0.5

    0.5

    0.5

    0.598

    0.598

    0.5

    0.598

    0.598

    PAW = PW / PA
    Zone

    0.402

    0.5

    0.5

    0.5

    0.402

    0.402

    0.5

    0.402

    0.402

    The matrix of the first non-exchangeable mode Car for all activity transfers is calculated. The
    matrix for the first activity transfer is the product of PC with the total demand matrix F1 of the first
    transfer.
    Total demand matrix F1 for the first activity transfer (Destination activity W)
    Zone

    93.4

    93.4

    Total

    93.4

    93.4

    93.4

    Matrix FP1 for mode C and the first activity transfer (destination activity A)
    Zone

    49.12

    49.12

    Total

    49.12

    49.12

    49.12

    With the next activity changeover, these 49.12 trips will be distributed across zones 2 and 3
    according to the distribution probabilities (P22 = 0.6 or P23 = 0.4).
    Matrix FC2 for mode C and the second activity transfer (Destination activity O)
    Zone

    49.12

    49.12

    Total

    2
    3
    PTVGROUP

    29.47

    19.65

    49.12

    29.47

    19.65

    10

    0
    185

    4.2.3.3 Tour-based model: trip distribution / mode choice combined


    Finally, the trips have to end back at the last activity transfer in their origin zone 1.
    Matrix FC3 for mode C and the third activity transfer (Destination activity H)
    Zone

    49.12

    49.12

    Total

    49.12

    29.47

    29.47

    19.65

    19.65

    Summed up, the following Car total demand matrix applies: FCT
    Zone

    147.36

    147.36

    Total

    49.12

    88.59

    19.65

    49.12

    49.12

    88.59

    29.47

    29.47

    19.65

    19.65

    19.65

    To determine the total demand matrix for non-exchangeable modes, this Car matrix is subtracted from the total demand matrix FT (from trip distribution).
    FT
    Zone

    280.2

    280.2

    Total

    93.4

    149.4

    37.4

    93.4

    93.4

    149.4

    56.0

    56.0

    37.4

    37.4

    37.4

    The difference first results in the total demand matrix for all non-exchangeable modes.
    FA
    Zone

    132.84

    132.84

    Total

    44.28

    70.81

    17.75

    44.28

    44.28

    70.81

    26.53

    26.53

    17.75

    17.75

    17.75

    For this matrix mode choice now takes place within the exchangeable modes PuT and Walk,
    to obtain the total demand matrices for modes PuT and Walk. The matrix is multiplied with the
    probabilities PAX and PAW.

    186

    PTVGROUP

    4.2.4 Estimate gravitation parameters (KALIBRI)


    PuT total demand matrix FX
    Zone

    70.75

    70.75

    Total

    22.14

    38.00

    10.61

    22.14

    22.14

    39.74

    13.27

    15.86

    10.61

    8.87

    8.87

    Walk total demand matrix FW


    Zone

    62.09

    62.09

    Total

    22.14

    32.81

    7.14

    22.14

    22.14

    31.07

    13.26

    10.67

    7.14

    8.88

    8.88

    Make sure that the Car total demand matrix has identical row and column sums for each zone,
    whereas this is not mandatory for the PuT and Walk matrices.
    The mode choice results are saved in an aggregated form to demand matrices per person
    group and mode. In addition, you can limit the usage of time interval and origin and destination activity data for matrices with disaggregated data.

    4.2.4

    Estimate gravitation parameters (KALIBRI)


    The Estimate gravitation parameters function (short KALIBRI) allows you to calibrate two different utility functions (determine parameters a, b and c) for the gravity model used for trip distribution.

    1.
    where
    Uij

    Value of the utility (for example distance or travel time) between zone i and zone
    j

    a,b,c

    Parameters to be estimated

    2.
    where

    PTVGROUP

    187

    4.2.5 Gravity model calculation


    Uij

    Value of the utility (for example distance or travel time) between zone i and
    zone j

    a,c

    Parameters to be estimated

    The KALIBRI function adjusts these utility functions to a given trip length distribution.
    Then the Trip distribution function calculates the traffic flow Fij (from zone i to zone j) with the
    aid of the gravity model and known data, namely the source traffic Qi (of zone i), destination
    traffic Zj (of zone j) and the parameters a, b, c (or a, c) specified here (see "Gravity model calculation" on page 188).
    The KALIBRI function provides two options that allow you to estimate the parameters for the
    gravity model.
    singly constrained production
    doubly constrained (Multi procedure)
    Parameters a, b, c or a, c respectively are determined in an iterative process. The utility function
    is transformed during this process; with

    or

    [2]

    [3]
    Within each KALIBRI iteration a temporary demand matrix is calculated (for example via
    Multi procedure with option doubly-constrained gravity model). The resulting values of the utility function are smoothed by linear regression until the maximum number of KALIBRI iterations is reached or the values do not change anymore. The smoothed values then describe
    a function of type [2] or [3].

    4.2.5

    Gravity model calculation


    The Gravity model is a mathematical model for trip distribution calculation (see "Trip distribution" on page 139 and "Tour-based model: trip distribution / mode choice combined" on
    page 178). It is based on the assumption that the trips made in a planning area are directly proportional to the relevant origin and destination demand in all zones and the functional values
    of the utility function between the zones (Ortzar 2001).
    The gravity model calculates a complete matrix of traffic relations Fij, using the OD pairs of marginal totals (origin and destination traffic of the individual zones). A consistent utility matrix of
    the planning region is required.
    The gravity model works with distribution parameters, therefore with values within the utility
    function, which map the reaction of road users to distance or time relations. These parameters
    are determined by comparing the demand per OD pair arising from the model, with the counted demand per OD pair (calibration).
    The capability of the models to predict future conditions (forecasting) depends on whether they
    manage to predict the behavior of road users in relation to the network impedances, as well as

    188

    PTVGROUP

    4.2.5 Gravity model calculation


    knowledge of the model input data applicable for the future (for example future travel
    demand).
    General form of the distribution formula
    where
    Logit
    Kirchhoff
    Box-Cox

    Combined
    TModel

    The distribution formula is referred to an attraction or utility function, with the following parameters.
    Uij

    Value for the utility between zones, for example distance or travel time from
    zone i to zone j

    Qi

    Origin zone i

    Zj

    Destination zone j

    kij

    Scaling factor (attractiveness factor) for OD pair zone i to zone j

    Number of zones

    Determining the scaling factor k ij and formulating the utility function f(U i j) are essential for
    various modifications and extensions.
    The scaling factor kij must be chosen so that the boundary conditions of the distribution
    models

    and

    are (at least approximately) fulfilled.

    PTVGROUP

    [4.1]

    [4.2]

    189

    4.2.5 Gravity model calculation


    Retaining only the first direction of distribution, we speak of production distribution. Retaining
    only the second direction of distribution, we speak of attraction distribution. Retaining both
    directions of distribution at the same time, we speak of doubly constrained. For coupling in
    terms of production kij only depends on i, so we write

    For logical reasons, coupling for production requires that there are as many free parameters
    as there are zones.
    This leads to the formulation

    with the following secondary conditions for zone i.

    From the n secondary conditions, all


    tribution function:

    can thus be determined by substitution in the dis-

    This results in

    for Qi 0
    This produces a destination choice model of production distribution.

    for all i, j
    The destination choice model of attraction distribution is derived analogously.

    for all i, j with


    The adjustment of the model to reality (calibration) by variation of the free parameters is very
    important.
    Since the input parameters Q i and Z j have been specified, the only free parameters that
    remain besides the scaling factors (

    and

    ) are the parameters of the utility function f(Uij).

    Since for doubly constrained calculation both directions of the distribution, [4.1] and [4.2] must
    be met at the same time, the following must also apply for the scaling factors
    190

    PTVGROUP

    4.2.5 Gravity model calculation

    and
    as well as
    =
    for i = j. In practice, however, this can seldom be achieved, so a
    true doubly-constrained calculation can only be achieved with much more complex iteration
    models.
    As an iteration model the Matrix Editor uses the so-called Multi procedure according to Lohse
    (Schnabel 1980) (see "The multi-procedure according to Lohse (Schnabel 1980)" on page
    204).
    The general form of the utility function f(Uij) is

    It is depicted for several b and c parameters in the following two figures.

    Notes: Choose a suitable specification for the utility functions, which means suitable parameters. Among other things, the specification depends on the trip purpose and the mode
    used. A trip to work is for example, on average longer than a trip for shopping. This
    means that the utility function for the trips to work, depending on the town's size, is only
    slightly dependent on the use (distance or travel time) or not at all. Shopping trips on the
    other hand, are much more dependent on the use.
    The use of a trip distribution model can therefore call for a separation of the travel
    demand based on the trip purpose. This depends essentially on the requirements in
    terms of accuracy and the demands on the matrix to be calculated. Benchmark figures for
    the percentage split based on the trip purpose can be obtained for example from the
    KONTIV 89 (EMNID 1991) or local surveys.

    PTVGROUP

    191

    4.2.5 Gravity model calculation


    The following four examples show gravity models that are differently constrained and with and
    without balancing.
    Example 1: Gravity model singly constrained in terms of production, with and without
    balancing
    The effect of the location factor on the calculation of the trip distribution according to the gravity
    model depends on the type of coupling of the gravity model.
    With the distribution method that includes coupling for EITHER attraction or production, the
    source or destination traffic is adjusted to the marginal totals in the code file. The location factor then only affects the "complementary" destination or origin demand. However, the following
    applies

    or
    whereby ki or kj are attractiveness factors of the i or j zone.
    With the distribution method that includes coupling for attraction AND production, the impact of
    the attractiveness factor on the origin and destination traffic depends on the function command
    in the code file. If for example $GQH is given as function command, the origin demand is changed by the location factor that is listed in the same line as the factor within the code file. However,

    with ki being the attractiveness factor of the i zone.


    Input file Utility
    *
    *
    *
    *
    *
    *
    *

    Zone numbers
    1
    2.66
    1
    1.00
    2
    0.33
    3
    0.33
    4
    1.00
    7.90

    2
    1.75
    2.08
    0.50
    2.33
    0.50
    1.41
    0.25
    2.08
    0.50

    3
    1.99

    4
    1.50

    0.33

    0.25

    1.00

    0.50

    0.33

    0.50

    0.33

    0.25

    Input data for calculation without balancing


    *Zone
    1
    2
    3
    4

    Production
    10.0000
    20.0000
    30.0000
    40.0000

    50.0000
    10.0000
    20.0000
    20.0000

    Attraction
    0.50000000
    1.00000000
    1.00000000
    1.00000000

    Factor

    External
    0
    0
    0
    1

    The parameters are set as follows:

    192

    PTVGROUP

    4.2.5 Gravity model calculation


    Combined utility function (exponential)
    Parameter a = 1, b = 0.5 and c = -1
    Singly-constrained for production without balancing
    Result matrix
    *
    *
    *
    *
    *
    *
    *

    Zone numbers
    1
    2
    36.76
    15.91
    1
    10.00
    3.11
    1.45
    2
    20.01
    6.76
    2.81
    3
    30.00
    9.97
    3.76
    4
    40.00
    16.92
    7.89
    100.01

    3
    30.79

    4
    16.55

    2.80

    2.64

    4.82

    5.62

    7.98

    8.29

    15.19

    0.00

    Input data for calculating balancing and scaling according to average value
    *Zone
    1
    2
    3
    4

    Production
    10.0000
    20.0000
    30.0000
    40.0000

    50.0000
    10.0000
    20.0000
    20.0000

    Attraction
    0.50000000
    1.00000000
    0.30000000
    1.00000000

    Factor

    External
    0
    0
    0
    1

    The parameters are set as follows:


    Direction of the distribution according to the production distribution with boundary sum
    balancing enforced by the multi procedure.
    Combined utility function (exponential)
    Parameter a = 1, b = 0.5 and c = -1
    Scaling according to mean value of both sums
    Max. number of iterations = 10, Quality factor = 3
    Result matrix
    *
    *
    *
    *
    *
    *
    *

    Zone numbers
    1
    2
    32.99
    13.19
    1
    8.04
    2.22
    0.94
    2
    16.10
    4.62
    1.74
    3
    24.16
    6.95
    2.38
    4
    32.19
    19.20
    8.13
    80.49

    3
    7.92

    4
    26.39

    0.56

    4.32

    0.93

    8.81

    1.57

    13.26

    4.86

    0.00

    Example 2: Gravity model singly-constrained for production, with balancing


    Input file Utility
    *
    *
    *

    PTVGROUP

    Zone numbers

    1
    2
    166.183 107.560
    165.571
    0.001
    22.700

    3
    88.972

    4
    134.710

    5
    155.725

    35.183

    50.387

    57.300

    193

    4.2.5 Gravity model calculation


    *

    107.414
    22.700
    0.001
    90.008
    35.926
    16.284
    134.633
    50.387
    31.017
    155.524
    57.169
    37.558

    15.991

    31.017

    37.705

    0.001

    15.153

    22.644

    15.153

    0.001

    38.075

    22.644

    38.152

    0.001

    653.150

    Input data
    *Zone
    1
    2
    3
    4
    5

    Production
    18990.0
    4960.0
    7110.0
    16080.0
    2300.0

    Attraction
    18990.0
    4960.0
    7110.0
    16080.0
    2300.0

    Location factor and zone property external are not specified. Default values are used.
    The parameters are set as follows:
    Direction of the distribution according to the production distribution with boundary sum
    balancing enforced by the multi procedure.
    Combined utility function (exponential)
    Parameter a = 1, b = 0.5 and c = -1
    Scaling according to the production total
    Max. number of iterations = 10, Quality factor = 3
    Result matrix
    *
    *
    *
    *
    *
    *
    *
    *

    Zone numbers
    1
    2
    18990.000 4959.951
    1
    18990.000
    18990.000
    0.000
    2
    4959.999
    0.000 4959.897
    3
    7110.000
    0.000
    0.054
    4
    16080.000
    0.000
    0.000
    5
    2300.000
    0.000
    0.000
    49439.999

    3
    4
    7109.758 16080.290

    5
    2300.000

    0.000

    0.000

    0.000

    0.102

    0.000

    0.000

    7109.426

    0.520

    0.000

    0.230 16079.770

    0.000

    0.000

    0.000

    2300.000

    Example 3: Gravity model singly-constrained for attraction, without balancing


    Input file impedances
    * Zone numbers
    1
    2
    1.00
    0.50
    0.33
    0.50
    0.33
    0.25
    1.00
    0.50

    3
    0.33
    1.00
    0.33
    0.33

    4
    0.25
    0.50
    0.50
    0.25

    Input data for marginal totals


    *Zone

    194

    Production

    Attraction

    PTVGROUP

    4.2.5 Gravity model calculation


    1
    2
    3
    4

    10
    20
    30
    40

    50
    10
    20
    20

    The parameters are set as follows:


    Singly-constrained for attraction, without balancing
    Combined utility function (exponential)
    Parameter a = 1, b = 0.5 and c = -1
    kj = 1 for all j
    This produces the following function values of utilities f(Uij)
    Zone
    1
    2
    3
    4

    1
    0,37
    0,41
    0,41
    0,37

    2
    0,43
    0,43
    0,39
    0,43

    3
    0,41
    0,37
    0,41
    0,41

    4
    0,39
    0,43
    0,43
    0,39

    and so

    F11 = 4.71
    The matrix is produced after the other 15 equations have been calculated.
    Result matrix
    *
    *
    *
    *
    *
    *
    *

    Zone numbers
    1
    2
    50.00
    10.00
    1
    9.68
    4.71
    1.03
    2
    20.47
    10.58
    2.06
    3
    31.09
    15.87
    2.80
    4
    38.74
    18.84
    4.11
    99.98

    3
    19.99

    4
    19.99

    2.04

    1.90

    3.64

    4.19

    6.13

    6.29

    8.18

    7.61

    The desired values for destination demand were very well approximated, while the values for
    origin demand were not reached so well. This circumstance is characteristic for such distribution formulas. Either the origin or the destination sums are reached close enough. If both
    boundary sums are to be aligned as closely as possible, it is necessary to use a boundary
    compensation model. The function offers doubly constrained projection (Multi-Procedure) (see
    "Projection" on page 203).

    PTVGROUP

    195

    4.2.6 Iterative repetition


    Example 4: Gravity model singly-constrained for attraction, with balancing
    Now the trip distribution in Example 3 (see "Example 3: Gravity model singly-constrained for
    attraction, without balancing" on page 194) shall be calculated using a balancing procedure
    (Multi-procedure).
    Input file impedances
    * Zone numbers
    1
    2
    1.00
    0.50
    0.33
    0.50
    0.33
    0.25
    1.00
    0.50

    3
    0.33
    1.00
    0.33
    0.33

    4
    0.25
    0.50
    0.50
    0.25

    Input data
    * ZoneNo
    1
    2
    3
    4

    Productions
    10
    50
    20
    10
    30
    20
    40
    20

    Attractions

    The parameters are set as follows:


    Direction of the distribution according to the production distribution with boundary sum
    balancing enforced by the multi procedure.
    Combined utility function (exponential)
    Parameter a = 1, b = 0.5 and c = -1
    Scaling according to mean value of both sums
    Max. number of iterations = 10, Quality factor = 3
    Result matrix
    *
    *
    *
    *
    *
    *
    *

    4.2.6

    Zone numbers
    1
    2
    50.00
    10.01
    1
    10.01
    4.87
    1.06
    2
    20.00
    10.34
    2.01
    3
    30.00
    15.32
    2.70
    4
    40.00
    19.47
    4.24
    100.01

    3
    20.00

    4
    20.00

    2.11

    1.97

    3.55

    4.10

    5.91

    6.07

    8.43

    7.86

    Iterative repetition
    Iterative repetition allows the steps in a process flow to be repeated; it provides the ability to
    feed (attribute or matrix) values that have been computed in previous steps back into one of
    the preceding stages.

    4.2.6.1

    196

    Go to the procedure
    Use the Go to procedure to carry out a convergence check. You can choose between the following checks

    PTVGROUP

    4.2.6.1 Go to the procedure


    1. It is checked whether, during the last iteration, attribute or matrix data has changed by less
    than the user-defined threshold value. To find the values that have changed, the following
    formula is used:

    where
    a

    Factor of relative deviation

    Tolerance value

    Absolute value for maximum change

    The following figure shows how the tolerance value is applied. For smaller attribute values, it
    allows for acceptance of larger relative deviations than for larger attribute values. In illustration
    57 the green curve represents the relative deviation, whereby the tolerance value was considered part of the attribute value.

    Illustration 57: Application of tolerance value in Go to procedure


    2. It is checked whether a user-defined attribute lies under a specific value. This is useful
    when you first add a script that recalculates the respective value.
    If the convergence condition has been fulfilled, Visum continues with the next step of the procedure. If not, Visum returns to the point specified as Go to target (procedure or group) and iterates the procedure from there (procedure) or from the next step (group). Independent of this,
    the convergence check is canceled as soon as a maximum number of iterations is reached.

    PTVGROUP

    197

    4.2.6.2 Method of successive averages (MSA) over matrices


    4.2.6.2

    Method of successive averages (MSA) over matrices


    Using MSA (method of successive averages), you can calculate the mean value of two matrices (demand or skim matrices).
    This function is meant to improve convergence in demand models used for feedback. You can
    add it prior to the Go to procedure if you want to use an averaged matrix of all iterations instead of a matrix of the current iteration as a GoTo criterion.
    The operation calculates

    whereby
    A

    Result matrix

    Matrix of current iteration

    Matrix average of all previous iterations

    iteration counter

    Notes: The iteration counter starts counting from iteration 0 and when Go to procedures
    are triggered it always uses the innermost loop as point of reference.
    4.2.6.3

    Method of Successive Averages over attributes


    As for matrices the average values of attributes can be determined by means of MSA (Method
    of Successive Averages), too.
    This function is meant to improve convergence in demand models used for feedback. You can
    add it prior to the Go to procedure if you want to use the average values of attributes of all iterations instead of the attribute values of the current iteration as a GoTo criterion.
    The operation calculates

    whereby
    A

    newly calculated attribute value

    Attribute value of current iteration

    Averaged attribute value of all previous iterations

    iteration counter

    Notes: The iteration counter starts counting from iteration 0 and when Go to procedures
    are triggered it always uses the innermost loop as point of reference.
    During an operation you can exchange the two weightings.

    198

    PTVGROUP

    4.3 Displaying and editing matrices

    4.3

    Displaying and editing matrices


    Visum provides various options for displaying and editing matrices or using them for calculations.
    Functions used to display and analyze matrices
    Highlighting matrix sections in color
    Showing matrix values in an aggregated form
    Filtering matrix values
    Displaying matrix values as a histogram
    Comparing matrices graphically in pairs
    Visum offers both simple and more complex operations for editing and calculating matrices.
    Most operations can be performed directly in the Matrix editor (see User Manual: Chpt. 16.3 ,
    page 1715), others are available as procedures (see User Manual: Chpt. 17 , page 1847).
    Functions for copying / replacing matrix values

    Matrix editor window

    Procedure

    Edit individual matrix values interactively

    Set values conditionally

    x*

    Form constant matrix

    x*

    Transpose

    Reflect upper or lower triangle

    Set diagonal

    x*

    Copy diagonal to clipboard


    Paste diagonal from clipboard

    Arithmetic operations on matrices

    x*

    Matrix editor window

    Procedure

    Round

    Add / subtract matrices

    x*

    Multiply / divide matrices (element-wise)

    x**

    Form reciprocal (element-wise)

    Raise to power (element-wise)

    x**

    Take logarithm (element-wise)

    Exponential function (element-wise)

    PTVGROUP

    199

    4.3.1 Displaying matrices in tabular form


    Arithmetic operations on matrices

    Matrix editor window

    Procedure

    Forming maximum or minimum

    Symmetrize matrix (calculate average values pairwise from top


    and bottom triangle)

    Combination of matrices and vectors

    Projection: various procedures

    Projection of aggregated areas

    Calculate matrix using marginal totals, i.e. trip distribution (see


    "Gravity model calculation" on page 188)
    Generate main zone matrix from a zone matrix (aggregate) and
    generate zone matrix from a main zone matrix (disaggregate)

    x
    x

    * Not a procedure of its own, but possible via Combination of matrices and vectors
    ** Possible in procedures via add-in CalculateMatrix
    Functions for structural changes to matrices
    Extend matrix (include new OD pairs in matrix for arithmetic operations)
    Aggregate (summarize rows/columns of a matrix)
    Split/Extend (rows/columns of a matrix into/to several ones)
    Form partial matrix (non-symmetric aggregation)

    4.3.1

    Displaying matrices in tabular form


    There are different ways to organize matrix data in a clear way. In Visum, in the Matrix editor
    window, you can change the data display to gain a better overview of your data (see User
    Manual: Chpt. 16.3 , page 1715):
    You can show matrix data in the matrix or list view.
    You can open several matrices in a window so that the corresponding values of the matrices are positioned side by side.
    In addition to the matrix values, it is possible to display the row and column headers as
    well as the row and columns totals.
    You can change the alignment of the values and the number of the displayed decimal places.
    You can classify the matrix values and display the values of different classes in different
    font and background colors.
    You can filter the matrix data by active zones, pairs of zones or by specific matrix values,
    so that only the rows and columns of your choice are shown.
    You can use aggregate functions to show the matrix data aggregated according to attributes of origin or destination zones, without having to change any data manually.
    You can save filtered or aggregated matrix data as a file and continue to use it in Visum
    as an external matrix.

    200

    PTVGROUP

    4.3.2 Displaying matrix values as a histogram

    4.3.2

    Displaying matrix values as a histogram


    This function allows you to classify the values of one or several matrices and to display them
    as column chart. You define intervals for the classification of the matrix values. You can determine the intervals interactively or import them from a file (see User Manual: Chpt. 16.3.13 ,
    page 1752).
    It is also possible to classify the matrix by using a comparison matrix that must include identical zones. The OD pairs are divided into the defined intervals based on the comparison
    matrix. The matrix values of the input matrix will then be summarized per interval according to
    this allocation.
    In addition to the histogram a list is displayed showing the number and the percentage of OD
    pairs for both, each interval and cumulative for all intervals. If the matrix is changed, the results
    will be updated automatically.
    This function serves for analyses of existing data for further matrix processing steps, for example aggregating data (see "Aggregating matrix objects" on page 207). The intervals can be stored and used for other applications.

    4.3.3

    Comparing matrices graphically in pairs


    In a special window, you can have the data of two matrices displayed along the x and y axis of
    a scatter plot. The plot further contains a diagonal, the regression line and the parameters of
    the regression function. The shape and position of the point cloud show similarities and deviations between the matrix values (see User Manual: Chpt. 16.3.14 , page 1756).

    4.3.4

    Transpose, reflect upper or lower triangle, apply mean value


    The Transpose function allows lines and columns of a matrix to be interchanged, which means
    that the values of the rows become the values of the columns and vice versa. The resulting
    matrix consequently contains the values of the opposite direction of the input matrix, with
    unchanged values in the diagonal. This function is used, for example, to generate a matrix of
    the outgoing traffic from a matrix of the incoming traffic (see User Manual: Chpt. 16.4.10 , page
    1774).
    The function offers the option of copying the matrix section below the diagonal into the upper
    triangle (see User Manual: Chpt. 16.4.9 , page 1773). The function offers the option of copying
    the matrix section above the diagonal into the lower triangle (see User Manual: Chpt. 16.4.8 ,
    page 1772).

    4.3.5

    Copy, paste and apply diagonal


    Note: The diagonal of a matrix runs from top left to bottom right (FromZoneNo = ToZoneNo). In demand matrices the diagonal represents the trips within the cell.
    The functions Copy diagonal into clipboard and Paste diagonal from clipboard enable the
    exchange of diagonal values between two matrices. For example, you can set a matrix value
    outside the diagonal to zero by copying the diagonal, setting all matrix values to zero and reinserting the diagonal (see User Manual: Chpt. 16.4.5 , page 1770).

    PTVGROUP

    201

    4.3.6 Round
    The function offers the option of setting the values of the diagonal with a new value, with the
    matrix values remaining unchanged for all relations FromZoneNo ToZoneNo.

    4.3.6

    Round
    With the Round function you round all matrix values to a specified precision. The matrix values
    are rounded up or down so that the new value is a multiple of the value rounded. Therefore, it
    is possible to round up to 0.1 or 0.25, for example (see User Manual: Chpt. 16.5.1 , page
    1777).

    4.3.7

    Form reciprocal, raise to power, take logarithm, exponential function


    The function offers the possibility of transferring the reciprocal of any given matrix value into
    the matrix (see User Manual: Chpt. 16.5.6 , page 1787).
    The function offers the possibility of giving an exponent for all matrix values and transferring
    the result in each case as the new matrix value (see User Manual: Chpt. 16.5.7 , page 1788).
    The Take logarithm function offers the possibility of determining the logarithm for each matrix
    value and transferring the result in each case as the new matrix value (see User Manual: Chpt.
    16.5.8 , page 1790).
    The Exponential function offers the possibility of using each matrix value as exponent for e (e
    = 2.71828183) and transferring the result in each case as the new matrix value (see User
    Manual: Chpt. 16.5.9 , page 1792).

    4.3.8

    Maximum or minimum formation


    The formation of a maximum or minimum results from the comparison of each value in the processed matrix with a user-defined value or the matrix value of the same relation in another
    matrix (see User Manual: Chpt. 16.5.10 , page 1793) and (see User Manual: Chpt. 16.5.11 ,
    page 1795).
    The result matrix then contains the following values for each relation.
    The greater of the two values at maximum formation
    The smaller of the two values at minimum formation
    Maximum or minimum formation is mostly used for symmetrization of a matrix, often in connection with Transposing (see "Transpose, reflect upper or lower triangle, apply mean value" on
    page 201).

    4.3.9

    Make symmetrical: mean value upper / lower triangle


    The Make symmetrical function calculates the mean value from the matrix values by element
    in the upper and lower triangle and replaces them by this mean value (see User Manual: Chpt.
    16.5.12 , page 1797).

    4.3.10

    Calculate the combination of matrices and vectors


    Values which result from a combination of other matrices and vectors can be assigned to a
    matrix. The values of individual input matrices and vectors can be transformed by element, multiplied by a factor and then added (see User Manual: Chpt. 16.5.13.1 , page 1799).

    202

    PTVGROUP

    4.3.11 Defining matrices as formulas


    Note: This function allows you to add exponential or Box-Cox transformed complex
    terms.

    4.3.11

    Defining matrices as formulas


    Similarly to formula attributes, matrices (see "Formula attributes" on page 113) can be defined
    as formulas. Using a combination of matrix and vector expressions, you can define a term that
    is automatically updated when changes are made to matrix data or zone attributes. This way,
    the matrix is always displayed with its current values. The data in formula matrices is only readable (see User Manual: Chpt. 16.3.4.2 , page 1727).

    4.3.12

    Projection
    The functionality is primarily used if origin or destination total values of a zone are to be multiplied by a particular value, or a particular expected value is to be attained, which can be
    necessary in some circumstances after origin-destination studies. Matrices collected are often
    just random samples and must be projected to census values.
    Matrix values can be projected per row (singly constrained projection regarding the production), per column (singly constrained projection regarding the attraction) or by row and
    column (doubly constrained projection) (see User Manual: Chpt. 16.5.14 , page 1800).
    Singly constrained projection means that each row or column is multiplied by a fixed value.
    This value can be a procedure parameter or for zone and main zone matrices an attribute
    of the zone or main zone. The complexity of doubly constrained projection is illustrated in the
    example below.
    Objective: projection of origin and destination demand as follows:
    zone 1 by 10%
    zone 2 by 20%
    Zone

    Origin demand

    20

    30

    50

    40

    50

    90

    Destination demand
    Table 70: Basic matrix

    60

    80

    140

    Line by line multiplication, therefore for purely singly constrained projection of the demand
    regarding production originating from zone 1 by 10% and zone 2 by 20%, produces the following matrix.
    Zone

    Origin demand

    22

    33

    55

    48

    60

    108

    Destination demand

    70

    93

    163

    While the origin traffic has been increased correctly, the destination traffic has not.
    PTVGROUP

    203

    4.3.12 Projection
    For the doubly-constrained projection, the Matrix editor uses an iterative process, also called a
    Multi-procedure. During this iterative procedure, a solution to how the target values are best
    reached is generated stepwise (see "The multi-procedure according to Lohse (Schnabel
    1980)" on page 204).
    The Matrix Editor thus provides the following solution which correctly projects the origin and
    destination traffic.
    Zone

    Origin demand

    21

    34

    55

    45

    62

    107

    Destination demand
    Table 71: Result matrix

    66

    96

    162

    The multi-procedure according to Lohse (Schnabel 1980)


    With the multi-procedure new traffic flows are calculated in each iteration step Fij (Schnabel
    1980).
    The iteration formula applied is as follows
    Fij(n+1) = Fij(n) qi(n) zj(n) f(n)
    with

    204

    Qip

    Desired origin traffic zone i

    Zjp

    Desired destination traffic zone j

    Gp

    Desired total traffic

    Fij(n)

    Traffic flow from zone i to zone j in iteration n

    Qi(n)

    Origin traffic zone i, iteration n

    Zj(n)

    Destination traffic zone j, iteration n

    G(n)

    Total traffic, iteration n

    PTVGROUP

    4.3.13 Projection of aggregated areas


    This iterative calculation is done repeatedly until the following conditions are met for all boundary values (origin and destination expected values).

    for all zones i

    for all zones j


    The threshold suggested by Lohse was used. It states that

    or
    QF: quality factor

    4.3.13

    Projection of aggregated areas


    You can also use this function for matrix projection. Contrary to simple projection, you do not
    specify a factor per row or column, but the rows and columns of matrices are separated into
    groups. You then define a projection factor per group or per relation between the groups (see
    User Manual: Chpt. 16.5.15 , page 1805).
    Thereby you need to distinguish between two modes:
    Singly constrained projection by territory: This largely corresponds to singly constrained projection (see "Projection" on page 203). The only difference is that for projection
    by territory the rows or columns of the matrix are separated into groups ("areas") and you
    specify a projection factor per group.
    Projection by item: For this procedure the projection factors are not defined per row or
    column, but per row/column relation. Here the rows and columns are also separated into
    groups and you specify a projection factor per "group relation".
    If you are using a matrix with network references, i.e. a zone or a main zone matrix, you can
    choose an attribute of the zone or main zone to separate the rows and/or columns into groups.
    If in this case, you e.g. select the attribute Main zone number for a zone matrix, singly constrained projection will use a specific factor per main zone for projection. Projection by item
    would use a different factor per main zone relation.
    Note: The term "territory" used here merely describes a group of rows or columns and is
    not to be confused with the network object of the same name.

    4.3.14

    Converting zone and main zone matrix into each other


    When calculating the main zone matrix from a zone matrix, you add the matrix values of zones
    that belong to the same main zone. This applies both to OD demand and skim matrices. The
    total amount of the matrix values are added to the main zone matrix, the zone matrix is kept.
    When disaggregating a main zone matrix you divide the matrix values of the main zones into
    several matrix values for the individual zones and add them to a zone matrix. The values can

    PTVGROUP

    205

    4.3.15 Extending matrices


    be equally distributed. However, you can also weight them. As weighting factors you can use
    the values of one or two zone matrices or of OD zone attributes.
    If you select two weighting factors, the new matrix values are calculated as follows:

    where
    i, j

    Zone indices

    i, j

    Main zone indices related to the zone indices

    Index(I), Index (J) Number of zone indices belonging to the main zone
    Value in the output matrix (zone matrix)

    bij

    Value in input matrix (main zone matrix)

    aij
    wij(1),

    wij(2)

    two weighting factors

    Note: If the denominator of a fraction is zero, weighting will be ignored.


    Use case
    You would like to correct a matrix or adjust it using count data. The count data available refers
    to a rougher zone structure than your network. In this case, you first aggregate the zone matrices, then perform a correction procedure (e.g. TFlowFuzzy) and finally disaggregate the matrix
    again.

    4.3.15

    Extending matrices
    You can extend external matrices during an arithmetic operation, i.e. you can add columns
    and rows. To do so, choose an arithmetic operation that allows you to combine external matrices with matrices that have different OD pairs.
    You can use any arithmetic operation that requires a second operand, e.g. the basic ones or
    forming the maximum or minimum.
    The matrix data is calculated as follows:
    The arithmetic operation is performed for the OD pairs that occur in all matrices.
    If an OD pair is not listed in all matrices, a null is entered for it before the arithmetic operation is performed. Then the arithmetic operation is performed.
    For OD pairs that are not listed in any of the matrices, a default value is set in the results
    matrix.
    Example of extending a matrix
    On the addition, the two matrices are extended. The standard value specified for new OD pairs
    is 99.

    206

    PTVGROUP

    4.3.16 Aggregating matrix objects


    Matrix in Matrix editor window
    1

    Matrix chosen as operand


    1

    Matrix extended on addition

    4.3.16

    99

    99

    99

    99

    Aggregating matrix objects


    This function allows you to group several matrix objects to create one or several new objects.
    You can use the Aggregate function to rename zones and/or group them into larger units (e.g.
    districts). The number of rows and columns of a matrix is changed through aggregation.
    The new matrix values are calculated with the aid of the following formulas:
    Arithmetic mean

    Weighted mean

    PTVGROUP

    207

    4.3.17 Splitting (extending) matrix objects


    with
    qi

    Matrix value of ith zone

    gi

    Weighting of ith zone

    Number of columns or rows

    Example of aggregating matrix objects


    The matrix values of the matrix below are aggregated.

    Zone allocations and settings:


    Zone 10 is removed from the matrix
    Zones 20 and 30 are aggregated and will form the new zone 39
    The weighted mean is used as aggregation function.
    The matrix data is weighted using the following matrix.

    Origin and destination zones of the matrix are aggregated


    The matrix values of the original matrix are used
    The following matrix results.

    Matrix values of destination zone 39 were calculated as follows:

    Note: If you aggregate a filtered matrix, only the filtered values are aggregated.

    4.3.17

    Splitting (extending) matrix objects


    Using the Split function, you can subdivide zones into smaller units. The number of rows and
    columns of a matrix is changed through splitting. This function is often used for adapting overall demand matrices to a finer zone classification in the network model.
    If you only specify one factor for an object generated during splitting, this factor applies to
    both the source and destination traffic in the demand matrix.

    208

    PTVGROUP

    4.4 Matrix correction


    If origin and destination value are to be distributed with different proportions in a zone
    generated by splitting, a destination traffic factor must also be specified after the origin traffic factor.
    For a demand matrix, the matrix value is generally distributed across the zones (1.0 = 100%)
    created through splitting. When choosing the splitting factors for zone generation, you can
    decide whether or not you want to include the expected gains (total > 1.0) or losses (total <
    1.0) per split zone.
    For a skim matrix, the matrix value per split zone is generally assigned to the new zones using
    the factor 1.0, i.e. they remain unchanged.
    Example of splitting matrix objects
    The zones of the following matrices are split and deleted.

    Thereby the following settings are made:


    Zone number old Zone number
    new

    Factor origin traf- Factor desfic


    tination traffic

    100

    1,001

    0.3

    0.1

    100

    1,002

    0.5

    0.2

    100

    1,003

    0.2

    0.7

    200

    2,001

    0.7

    0.7

    200

    2,002

    0.3

    0.3

    In addition, all trips created within the cell are set to null.
    This produces the following matrix:

    Total of matrix data for all OD pairs from/to 1,001..1.,003 equals 1,000.

    4.4

    Matrix correction
    You have different possibilities of correcting the demand matrix values with count data.
    Updating demand matrix with TFlowFuzzy
    Projecting PrT path volumes
    Calibrating a PrT matrix

    PTVGROUP

    209

    4.4.1 Updating demand matrix with TFlowFuzzy

    4.4.1

    Updating demand matrix with TFlowFuzzy


    Like all matrix correction procedures, TFlowFuzzy is meant to adjust a demand matrix, so that
    its assignment results for a supply actually match the real supply observed (source/target traffic, passenger trips unlinked or number of boarding/alighting passengers). This procedure can
    be useful in several situations:
    A demand matrix based on empirical survey data is outdated and you want to update it
    without having to conduct a new (origin-destination) survey. The update shall be
    based on based on census data only.
    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 counted simultaneously.
    A survey contains the journey distance distribution, but the model does not reflect the
    data with the level of accuracy required.
    TFlowFuzzy will solve this problem for PuT as well as for PrT. The update only affects the
    demand matrix - not the time series - and always refers to total volumes (instead of volumes
    per time interval).
    The flow of information always follows the given order.

    The workflow for the matrix calibration is as follows.

    You can choose the following count data:


    Link volumes
    Origin/destination travel demand per zone

    210

    PTVGROUP

    4.4.1 Updating demand matrix with TFlowFuzzy


    Volumes of turns at nodes and main turns at main nodes (as long as they are defined)
    Volumes via screen lines
    Volumes on lanes
    PuT passenger trips unlinked per line
    PuT passenger kilometers per line
    Boarding/alighting passengers at stop areas
    Skim data distribution, e.g. journey distance distribution
    You can also combine count data.
    A detailed example of how to use journey distance distribution is available in the folder: ...\Users\Public\Public documents\PTV Vision\PTV Visum 13\Training\TFlowFuzzy.
    It is best to work with volumes on lanes if you want to use count data that comes from stop line
    detectors. These are - other than manually collected node flows - not already assigned to a
    (main) turn, but to the lane the detector is located on. If you are using lane counts, you need to
    model the lane allocation at the respective node in the Junction editor. Visum aggregates lane
    counts to counts per lane group, i.e. the count data is added across all (main) turns that have
    at least one shared lane. TFlowFuzzy compares the count data sums to the volumes of all routes that use this lane group.
    Sometimes PuT passengers alighting/boarding at stop areas are counted separately for each
    direction. To be able to use the information content of the disaggregated count data, without
    having to separate the stop area into several parts, separate the line routes traversing the stop
    area into groups. Then specify count data and tolerances for each group.
    For the update, the specified count values are compared with the volumes, which result from a
    pre-calculated assignment of the previous demand matrix. Differences between count values
    and volumes are balanced by adjustment of the demand matrix for the assigned demand segment. The simplest case refers to a single demand segment. The volumes from the selected
    network object are then taken from the assignment result of this demand result, and the count
    values also only refer to this demand segment. TFlowFuzzy can also simultaneously update
    the demand matrices of several demand segments, if only total count values are specified for
    all demand segments. Then the count data specified is distributed proportionally to the respective demand segment share of the assignment volumes. The demand matrix for each demand
    segment is then updated individually.
    Compared to other procedures, the outstanding quality of TFlowFuzzy is
    that you can combine the following for matrix correction: origin/destination traffic, link
    volumes, turns, main turns or screen lines, passenger trips unlinked and passengers
    boarding/alighting at stop areas and distributions (e.g. journey distance).
    Count values do not have to be available for all network objects.
    The statistical uncertainty of the count figures can be modeled explicitly.
    You can specify that the distribution of the result matrix must correspond to the distribution of an existing demand matrix.
    You can use count data that only covers part of the PuT lines. In this case, only volumes or boarding/alighting passengers that refer to active line route elements are taken
    into account for calculation.

    PTVGROUP

    211

    4.4.1.1 Methodological basics of TFlowFuzzy


    4.4.1.1

    Methodological basics of TFlowFuzzy


    Since the eighties, primarily in English-speaking countries, so- called matrix correction (or
    matrix update) techniques have been used to produce a current demand matrix from an earlier
    travel demand matrix (base matrix) using current traffic count values. Based on research by
    Van Zuyten/Willumsen (1980), Bosserhoff (1985) and Rosinowski (1994) which focuses on
    matrices for private transport, PTV has extended the application of these techniques to public
    transport.
    The starting point for the classic procedure is the travel demand for the individual OD pairs fij.
    Travel demand is usually described as a matrix, but for our purposes a vector representation
    containing all non-zero OD trips is more suitable.

    While it is usually assumed, that a matrix based on an earlier time is known, only partial information is provided for the current state. Important is the situation where there are no data
    based on relations (from an origin destination survey) available, but only count values at individual positions in the network. These can be both origin / destination traffic as well as link
    volumes. We note the count values as another vector.

    The trips of any OD pair provides 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 (proportional) OD trips traveling on
    this link. In general there is a linear relation between the demand on the OD pairs and the traffic counts.
    Af=v
    whereby A is called flow matrix. ask is "the share of passengers on movement k, traversing link
    s". For origin / destination traffic count values, A is especially constant, as specified with example n = 3, m = 6.

    212

    PTVGROUP

    4.4.1.1 Methodological basics of TFlowFuzzy

    In this case, A does not depend on the timetable. However, the supply dependent trip choice
    flows into A for link volumes; the flow matrix is obtained for example, through assignment of
    any matrix (for example the old demand matrix) on the supply at the time of the count. Both
    types of count values can be also be used next to each other without a problem.
    A problem for the matrix correction is that, usually m << n 2 and therefore the new matrix is
    underdetermined by the count values. Out of the countless matrices which match the count
    values "match", only the best is selected according to a evaluation function q, thus solves
    max q(f), so that A f = v
    A combination of entropy and weighting with the proportions of the old matrix usually serves
    as an evaluation function; q is usually non-linear, which is why the problem is solved iteratively
    (for example with Newton's method).
    In this wording of the matrix correction problem there is, however, another weakness of the
    classic approach: vector v of the count values is assumed as a known parameter, free of every
    uncertainty. A q maximum is only selected from the matrices which fulfill the exact secondary
    conditions. The count values thus receive an inadequate weight, because each survey provides a snap shot, which is afflicted with a statistical uncertainty. Conventional procedures (for
    example from Willumsen) do not allow such a state, because the boundary sums are perceived as "strict" secondary conditions.
    PTV has therefore taken on the approach by Rosinowski (1994), who modeled the count
    values as fuzzy measured data according to the Fuzzy Sets Theory. If it is known that in a
    zone, the origin traffic fluctuates up to 20% from day to day, in other zones however about
    25%, this is illustrated with the respective bandwidths. In the secondary conditions of the
    matrix estimation problem, there are thus Fuzzy Sets
    widths which replace strict values.

    with sets of variables of different

    max q(f), so that A f =


    The illustration of Fuzzy Sets compared to pure limits allows the preference of central values to
    be expressed within the set of variables. This means, that values close to the mean values are
    generally preferred, but values within the margin are also accepted, if this means that a much
    better q value is achieved.
    How can the Fuzzy Sets now be treated numerically for the solution of the optimization problem? The obvious trip is, to include the membership function of the individual Fuzzy Sets in
    the evaluation function and in comparison weighted appropriately. To be able to continue
    using standard procedures of non-linear optimization, the resulting objective function must

    PTVGROUP

    213

    4.4.1.1 Methodological basics of TFlowFuzzy


    also be twice continuously differentiable, producing restrictions regarding the form of membership functions. Especially the usually partial linear triangles or trapezoids are eliminated.
    Instead we use the same mechanism as for the weighting with the original matrix, to support
    the choice of central values from the set of values. As a comparison, here the evaluation function of the weighted entropy maximization.

    If
    is already set as a demand from the original matrix, the maximization of q benefits matrices which slightly differ from the original matrix. This principle can be transferred to our new
    optimization problem:
    maxq(f, s, s), so that
    Af+s=v
    A f - s = v
    s0
    s 0
    where

    = maximum or minimum of the set of variables of the Fuzzy Sets.

    If the slack variable s, s is included in the weighted entropy maximization


    , matrices
    are favored that fulfill A f = v "best". Doubling the equation appears to be a disadvantage,
    because this has a direct effect on the calculation time of the runtime determining Gauss
    method within the Newton iteration. Symmetries in the resulting equation system however, still
    only allow to solve a system half the size and hence, deduct a solution of the entire system.
    The range of solutions of the estimate problem increases due to the Fuzzy formulation and therefore the degree of freedom for the evaluation (here: entropy maximization), so that generally
    higher target function values can be achieved. To make it clearer, the "most likely" demand
    matrix is thus estimated, which represents the count values within the bandwidths.
    Illustration of Fuzzy sets with an example
    A Fuzzy set is generally defined as a set of possible values (set of variables) and a membership function with values between 0 and 1, which specifies "how much an element of the
    set of values is perceived as related to the fuzzy set". If the membership function is 0, the element does not belong to the unclear set. For a value of 1, element "total" belongs to the set
    and interim values express the quality of approximation. If for example, you want to express
    the value "approximately 4" as a fuzzy set, the set of variables could contain the interval [3;5]
    and the membership function rises from value 0 to the interval margins to a maximum of 4.

    214

    PTVGROUP

    4.4.1.1 Methodological basics of TFlowFuzzy

    To make bandwidth modeling in TFlowFuzzy more manageable and operation easier, it is assumed that the membership function has a very special form. From value 1, which is assumed
    by the survey count values, it drops symmetrically to both sides. It thus creates a triangle,
    which is determined through the following values.

    the count value itself, where the membership function assumes its maximum

    the distance between the count value, where the membership function drops to
    value 0

    a predefined scaling factor ( >0)

    Values z , s and are entries for TFlowFuzzy (see User Manual: Chpt. 16.7.1 , page 1817). z
    and s are specified individually for each count value (link volume, origin / destination traffic,
    turn volume or main turn volume, as long as a main node is defined), whereas is a global
    parameter for the procedure.

    PTVGROUP

    215

    4.4.1.2 Numeric example for TFlowFuzzy


    4.4.1.2

    Numeric example for TFlowFuzzy


    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 link bars show the assignment result for the following matrix, which we assume 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
    * Number 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.

    216

    PTVGROUP

    4.4.1.2 Numeric example for TFlowFuzzy

    The counted values for this example are based on the assumption that the demand matrix has
    since changed as follows.
    $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
    * Number 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,
    which means a bandwidth, within which the counted values actually fluctuate from one survey
    date to another. This fuzzy value can be accepted as it is or obtained empirically by counting
    the same OD relations on different dates.
    TFlowFuzzy 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 OD 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 within the specified bandwidth.
    In the above example TFlowFuzzy, with a random sample accuracy of
    following matrix, which matches the assumed "ideal solution" very well.

    5%, calculates the

    $VN
    4
    *

    PTVGROUP

    1
    346

    2
    331

    3
    298

    4
    281

    217

    4.4.2 Projecting PrT path volumes


    *

    1:

    2:

    3:

    4:

    346
    0
    331
    148
    298
    99
    281
    99

    148

    99

    99

    100

    83

    100

    99

    83

    99

    * 1256

    4.4.2

    Projecting PrT path volumes


    The Paths projection function adjusts the demand matrix of a PrT transport system to the counted data of particular links. Thereby all movements F ij that use a selected link for a PrT
    demand segment are projected, so that the link volume corresponds to the count data (AddValue). The relations used in this process are the result of an assignment in which all used trips
    are saved along with their volumes.
    The update only affects the demand matrix - not the time series - and always refers to total volumes (instead of loads per analysis time interval).

    4.4.3

    Calibrating a PrT matrix


    The Cali procedure provides a calibration function that uses count data to calculate projection
    factors - based on assignment results - for origin and destination sums of a PrT demand
    matrix. Using a balancing procedure the matrix is then projected to the sum values.

    4.4.3.1

    General principle of the calculation procedure


    The projection of the matrix corresponds to the Increase factor model with justification, known
    in traffic planning. By comparing the calculated volume with the count data, the counted cross
    sections supply information on "adjustment factors" which need to be taken into account. Here
    it has to be taken into account that an 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.
    1. Determination of the adjustment factors
    First, the calibration function calculates an adjustment factor ki for each count value zi.
    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 using different count value adjustment factors zi..n, these factors must be averaged and balanced.
    Adjustment factors for origin and destination traffic are thus 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.
    2. Projection of the matrix using the projection factors generated as explained above

    218

    PTVGROUP

    4.4.3.2 Example: Matrix projection


    4.4.3.2

    Example: Matrix projection


    The Fij matrix of the last assignment serves as the basic matrix.
    Zone

    Origin demand

    20

    30

    50

    40

    50

    90

    Destination demand

    60

    80

    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

    Origin demand

    22

    33

    55

    48

    60

    108

    Destination demand

    70

    93

    163

    It is clear 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.
    This is why an iterative procedure, the Multi-procedure according to Lohse (Schnabel 1980), is
    used for origin and destination projection, as in an iterative process it searches for that one
    solution that is best used to reach the target values (see "The multi-procedure according to
    Lohse (Schnabel 1980)" on page 204).
    For the above example the following solution is found:
    Zone

    Origin demand

    21

    34

    55

    45

    62

    107

    Destination demand

    66

    96

    162

    PTVGROUP

    219

    5 Impact models

    Impact models
    An impact model contains all methods to calculate the impact of traffic. It calculates results on
    the basis of data and thus represents the computation kernel of the application. Components
    of the different impact models offered in Visum are in particular assignment, skim calculation,
    line blocking, line costing calculation (PuT operating indicators) and emission calculation,
    including the impedance models used in them. Each of these methods is part of at least one of
    the impact models for users, operators and the environment.
    Subjects
    The types of impact models
    Impedance functions
    Paths in PrT and PuT
    Skims / indicators

    5.1

    The types of impact models


    A transport supply system has diverse impacts which may vary because of measures. Impacts
    always refer to those actively or passively involved in traffic, for example the users or operators
    of the transport supply system, to the general public or the environment. The impact models in
    Visum are differentiated according to those involved and each comprises all methods on calculating the effects on one of the roles mentioned.

    5.1.1

    The user model


    Users of infrastructure for private transport are mostly car drivers and their passengers, but
    also non-motorized travelers such as cyclists and pedestrians. Users of public transport are
    public transport passengers. Objective of the user model is to determine the impacts of a transport supply system on travelers. Important skim data for evaluating the transport supply are the
    journey time and traveling expenses between two zones. To evaluate a public transport supply, additional skim data such as number of transfers, transfer wait time and service frequency
    must be considered.
    To determine these user-specific skims, the OD trips of travelers are modeled. A user chooses
    a route for his trip which appears convenient to him. If in addition to the route, the user also
    selects the departure time of his trip, one speaks of a connection independent of the mode. In
    addition to the spatial course, a connection thus comprises the entire temporal course: In
    public transport especially the departure and arrival times at the boarding stop, at the transfer
    stops and at the destination stop and in private transport the selected departure time, the arrival time and the transit time for each location along the route. If the temporal progression of the
    traffic situation has been explicitly modeled in this way, one speaks of a dynamic model (dynamic assignment). There is no time axis for a static model, however, so that OD trips take place
    without temporal course and have a simultaneous effect on each location in the network.
    There are static and dynamic user impact models in both PrT and PuT.
    Methods to model the travel behavior are based upon search algorithms which determine routes or connections between an origin and a destination. Procedures used as search algorithms are those which determine the best, meaning those which determine paths with the
    lowest impedance or a set of sufficient paths. Impedance can consist of times, distances, and

    220

    PTVGROUP

    5.1.2 The operator model


    costs. Depending on the search algorithm used, the paths found represent routes or connections. The trips by OD pair are distributed among the paths found. This combination of path
    search and trip distribution is called assignment. Private transport assignment assigns vehicle
    trips; public transport assignment assigns passenger trips.
    For every route or connection between two zones skims can be calculated which describe the
    service quality of the route/connection. In addition to this, an assignment produces traffic volumes for links and turns, and in PuT projects also for stops and stop points plus all objects of
    the PuT line hierarchy from the transport system down to the level of individual vehicle journeys. In contrast to a quality skim such as, for example, journey time, the volume is only an indirect skim which by itself is not suited for evaluating the transport supply system. The volume is
    rather used to deduce
    saturation of PuT lines which affects the comfort of passengers and the revenues of operators
    noise and pollution emissions which indicate the environmental impact
    Thus, the volume resulting from the user impact model serves as a basis for the procedures
    provided by the operator impact model and those of the environmental impact model as well.
    Visum offers various assignment procedures for private and public transport. They differ by the
    search algorithm and by the procedure used for distributing demand. These assignment procedures are a central part of Visum. There are PrT models and PuT models.
    PrT (see "User model PrT" on page 226)
    PuT (see "User model PuT" on page 449)

    5.1.2

    The operator model


    Transport supply operators are PuT transport companies and transport associations, in a broader sense these also include the PuT contractors of the operators. To offer public transport service, PuT operators develop line networks and timetables from which the user can then
    choose connections.
    To estimate the impacts on PuT operators, the so-called operator model is used to determine
    indicators which describe the operational and financial requirements for offering public transport supply on the one hand and on the other hand the expected revenues (see "Operator
    model PuT" on page 541). The PuT operator model comprises the following methods.
    Line blocking which determines the number of required vehicles
    Determining operational costs
    Estimating revenues
    Line costing which distributes the operational costs and revenues over PuT lines
    Compared to the PuT, the PrT network is generally operated by the state, countries or councils, but also more and more by private investors. Decisions are geared towards the impact on
    the general public, rather than on the impacts on the operators themselves, which is why in
    general a different operator model has to be used for PrT..

    PTVGROUP

    221

    5.1.3 The environmental impact model

    5.1.3

    The environmental impact model


    Visum provides three models within the environmental impact model, to calculate the environmental impacts which are noise and pollution emissions, caused by motorized private transport (see "Environmental impact model and HBEFA" on page 679).
    Noise-Emis-Rls90: Calculation of noise emission levels in accordance with the guideline
    on noise reduction for roads, edition 1990 (RLS-90), without considering immission parameters.
    Noise-Emis-Nordic: Calculation of noise emission levels in accordance with Nordic Council of Ministers (1996).
    Pollution-Emis: Calculation of air pollution emissions in accordance with emission factors
    of the Swiss Federal Office for the Environment (BAFU).

    5.2

    Impedance functions
    An impedance function generally measures the effort connected to a traffic process. All instances are summarized to this effort, which prevent participants from carrying out this process and
    therefore create an impedance. Effort examples are especially time and costs connected to the
    process. You can also enter subjective criteria in the impedance. Thus, the impedance of a certain connection in the PuT may increase, if certain comfort criteria are not satisfied.
    Impedance functions play an important role in several impact models. In the assignment, the
    impedance function assigns a route or connection an effort. In PrT, especially the journey time
    in the loaded network flows into the impedance, but it can also be additional properties such
    as traveling expenses and possible toll. For dynamic assignments, it is also the discrepancy
    between the departure time and the desired departure time. In PuT, in addition to the travel
    time, it is mainly the number of transfers and the fare which have an effect on the impedance.
    A problem for impedance functions is that completely different aspects are included and have
    to finally arise from conjoint evaluation in form of a number. These different aspects which are
    partially measured in different units, must therefore be recalculated and weighted against
    each other. In general, weighting of the factors for different groups of assessing personnel is
    different. For this reason, impedance functions for example can be defined at the assignment
    per demand segment (see User Manual: Chpt. 18.2 , page 1892) and at line blocking per
    vehicle combination (see User Manual: Chpt. 20.1.3.2 , page 2105).
    In Visum, impedance functions are used in the following contexts:
    Assignment (User model): The impedance function assigns the effort to each path, thus
    depending on the type of assignment, each route or connection, which the passenger has
    to make, if he decides to take this path. The most natural criterion is the travel time which
    has the corresponding unit time [s]. Especially in PrT, the travel time of a link is not constant, but depends on the volume, the coherence is described in a VD function.
    Demand models (User model): Within the framework of trip distribution, mode choice, as
    well as combined procedures for trip distribution and mode choice, the impedance function allocates an OD pair or the mode choice for this relation to the effort, which has to be
    overcome for this choice. In this context we are traditionally talking about utility functions.
    Although the supporting concept is identical, the benefit of it is, however, only the negative
    impedance of the process.

    222

    PTVGROUP

    5.3 Paths in PrT and PuT


    Line blocking (Operator model): The impedance function assigns each activity (vehicle
    journey, empty trip, layover, etc.) in a cycle the effort which arises, if the activity is performed by this cycle. The most natural criteria here are the costs.
    Despite these different application areas, the impedance function structure is always the
    same: Each impedance function consists of a sum, in which each summand evaluates a certain aspect of the effort and is weighted by a coefficient (see illustration 58). To calculate the
    impedance of a traffic process, the properties of the process are first determined regarding
    each aspect. Each aspect is then evaluated separately, in PrT especially by evaluating the VD
    function. This evaluation of individual aspects is then provided and summed up with the weighting factors.

    Illustration 58: Impedance calculation for a PuT connection, for clarity illustrated in the unit
    [min]

    5.3

    Paths in PrT and PuT


    All assignments in Visum in PrT as well as in PuT are path-based, meaning that possible
    paths are calculated for each OD pair and loaded with a demand share. All other results, especially the different network object volumes and the skim matrices are derived from these loaded paths. These paths are saved with the assignment result and can be analyzed after the
    assignment for flow bundle calculation, for example.

    PTVGROUP

    223

    5.4 Skims / indicators


    A path first describes the exact local course of a translocation in the network model, which
    means, that all traversed network objects such as nodes, links, turns, main nodes, connections, if applicable also stops, line routes and time profiles are known. If the departure time and
    thus the temporal course is added to the spatial course, we are taking about a connection,
    otherwise a route. For PuT paths, in addition to departure time for a connection compared to
    the route, the information on used vehicle journeys is included.
    If an assignment produces routes or connections depends on the type of assignment. Dynamic
    PrT assignments and the timetable-based PuT assignment create connections, static PrT assignments as well as the headway-based PuT assignment calculate routes. In principle, the
    user can select, whether internally calculated connections should be saved as such or only as
    routes, or not at all respectively for PrT (see User Manual: Chpt. 18.1.2 , page 1890) and PuT
    (see User Manual: Chpt. 19.1.1.2 , page 1996) . If you do not save the connections, less
    memory is required, however, posterior analyses of the connections are no longer possible,
    even if a dynamic assignment procedure was applied. Network volumes are still calculated
    and can even be output differentiated according to analysis time intervals.

    5.4

    Skims / indicators
    A skim is a measurement taken from the traffic model. Typical examples are the mean travel
    time from a zone A to a zone B, which is calculated from the travel times of all paths found, as
    well as the total PuT journey time, which is the sum of the journey times of all PuT passengers.
    Skims can be divided into global skims, which describe properties of the entire traffic model,
    and into skims gained per OD pair. The latter are stored in skim matrices, whereby the entry xij
    for the skim value, refers to the relation from zone i to zone j.
    Generally, skims measure the properties of the traffic model. In feed back models they are also
    the input data for the demand modeling procedures, especially for trip distribution and mode
    choice.

    5.4.1

    Skim matrices
    Skim matrices describe properties of each relation from an origin zone A to a destination zone
    B in the traffic model. Each individual skim (for example the travel time in a vehicle) is extracted from the path properties from A to B, which belong to a demand segment. The skim data is
    then aggregated with the relative share of demand, which the path would attract, to a skim
    value for the OD pair. This also applies, if there is no demand for the relation from A to B,
    because distribution does not depend on the demand.
    The calculation of skim matrices differs between PrT and PuT on some points. The calculation
    of PrT skim matrices is either based on present paths from a previously calculated assignment,
    or for each OD pair the optimum path with regard to the impedance is determined (in the possibly loaded network). Compared to an assignment, the network is not loaded in this case.
    Because in this case there is only one path per relation, the skim value is extracted directly
    from this path. If, however, paths from an assignment are used for skim matrix calculation, the
    value of the minimum or maximum path impedance can be output as skim value, or the weighted or unweighted mean value calculated from all paths by OD pair.
    In PuT always more than one route or connection is calculated per OD pair, and the skim
    value is derived from these. In addition to the average determination, optionally weighted with

    224

    PTVGROUP

    5.4.2 Global indicators


    the demand share, the output of properties of the path with the least perceived journey time
    (PJT, timetable-based procedure) or with the least impedance (headway-based procedure) as
    well as quantiles are available as additional aggregate functions. The skim is especially
    directly dependent on the applied search strategy. Because not only the saved, but all paths
    found are included in skim matrix calculation, the result differs from the result subsequently
    derived from the paths. This is the case, if the demand becomes zero on some paths by an
    explicitly requested rounding and the path is therefore not saved, but used for skim matrix calculation. If demand and volume rounding is switched off, such differences cannot occur.

    5.4.2

    Global indicators
    In addition to the skims by OD pair and demand segment, which are available in skim matrices
    and are only calculated on demand, Visum automatically calculates a specified set of global
    indicators with each assignment. These are properties of the overall assignment result, i.e., of
    the traffic model itself. Typical values are the mean travel time in the network, the total vehicle
    impedance in PrT, the total journey time of all PuT passengers, as well as the number of passenger trips by PuT line. The global values are displayed via lists (see "Evaluation lists" on
    page 750).
    If several assignments are carried out subsequently, the global values represent the properties of all paths in these assignment results. Compared to the skim matrices, these values
    orientate themselves towards the loaded paths contained in the result. They are thus consistent with properties of the saved paths.

    PTVGROUP

    225

    6 User model PrT

    User model PrT


    The User model PrT calculates the effect of private transport supply on all car drivers and passengers, but also on non-motorized road users, such as cyclists and pedestrians.
    Subjects
    Overview of PrT assignment procedures
    Example network for PrT assignment procedures
    PrT paths
    Impedance and VD functions
    Impedances at node
    PrT skims
    Distribution of traffic demand across PrT connectors
    Blocking back model
    Convergence criteria of assignment quality
    Distribution models in the assignment
    Incremental assignment
    Equilibrium assignment
    Linear User Cost Equilibrium (LUCE)
    Equilibrium_Lohse
    Assignment with ICA
    Stochastic assignment
    TRIBUT
    Dynamic User Equilibrium (DUE)
    Dynamic stochastic assignment
    NCHRP 255
    Assignment analysis PrT

    6.1

    Overview of PrT assignment procedures


    Visum provides several assignment procedures for the PrT. There are static assignment procedures without explicit time modeling as well as procedures which use a time dynamic traffic
    flow model.
    The Incremental assignment divides the demand matrix on a percentage basis into
    several partial matrices. These partial matrices are then successively assigned to the network. The route search accounts for impedance resulting from the traffic volume of the previous step (see "Incremental assignment" on page 336).
    Equilibrium assignment distributes the demand according to Wardrop's first principle:
    "Every road user selects his route in such a way that the travel time on all alternative routes is the same, and that switching to a different route would increase personal travel
    time." The state of equilibrium is reached through a multi-step iteration process based on
    an incremental assignment as the starting point. 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 (see "Equilibrium assignment" on page 342).

    226

    PTVGROUP

    6.1 Overview of PrT assignment procedures


    The Equilibrium assignment LUCE uses the LUCE algorithm, which was conceived by
    Guido Gentile. He collaborated with PTV to produce a practical implementation of the
    method in Visum. Exploiting the inexpensive information provided by the derivatives of the
    arc costs with respect to arc flows, LUCE achieves a very high convergence speed, while
    it assigns the demand flow of each OD pair on several paths at once (see "Linear User
    Cost Equilibrium (LUCE)" on page 351).
    The Equilibrium_Lohse assignment models the "learning process" of road-users in the
    network. Starting with an "all or nothing assignment", drivers consecutively include information gained during their last journey for the next route search (see "Equilibrium_Lohse"
    on page 366).
    The Assignment with ICA brings the impedances at junctions into focus. It explicitly
    regards lane allocations and further details. Especially the interdependencies between
    the individual turns at a node are considered. With other assignment procedures, the
    detailed consideration of node impedances usually leads to an unfavorable convergence
    behavior. The assignment with ICA uses turn-specific volume-delay functions which are
    continuously re-calibrated by means of the ICA. This leads to a significantly improved convergence behavior (see "Assignment with ICA" on page 374).
    The Stochastic assignment takes into account the fact that skims of individual routes
    (journey time, distance, and costs) that are relevant for the route choice are perceived subjectively by the road users, in some cases on the basis of incomplete information. Additionally, the choice of route depends on the road user's individual preferences, which are
    not shown in the model. In practice, the two effects combined result in routes being chosen which, by strict application of Wardrop's first principle, would not be loaded, because
    they are suboptimal in terms of the objective skims. Therefore, for stochastic assignment,
    an alternative quantity of routes is initially calculated and the demand is distributed across
    the alternatives on the basis of a distribution model (e.g. Logit) (see "Stochastic assignment" on page 385).
    The TRIBUT procedure, which was developed by the French research association
    INRETS, is particularly suitable for modeling road tolls. Compared to the conventional procedures which are based on a constant time value, TRIBUT uses a concurrent distributed
    time value. A bicriterial multipath routing is applied for searching routes, which takes the
    criteria time and costs into account. Road tolls are modeled as transport system-specific
    road toll value, either for each Visum route or for link sequences between user-defined
    nodes (non-linear toll systems) (see "TRIBUT" on page 397).
    In co-operation with the University of Rome, Visum provides the Dynamic User Equilibrium (DUE). Additionally, the algorithm includes a blocking-back model, can account
    for time-varying capacities as well as road tolls and provides a departure time choice
    model (see "Dynamic User Equilibrium (DUE)" on page 410).
    The Dynamic Stochastic assignment differs from all the previously named procedures
    as a result of the explicit modeling of the time axis. The assignment period is divided into
    individual time slices, with volume and impedance separated for each such time slice. For
    each departure time interval, the demand is distributed across the available connections
    (= route + departure time) based on an assignment model as in the case of the stochastic
    assignment. With this modeling, temporary overload conditions in the network are displayed, a varying choice of routes results in the course of the day, and possibly also a shift

    PTVGROUP

    227

    6.2 Example network for PrT assignment procedures


    of departure time with respect to the desired time (see "Dynamic stochastic assignment"
    on page 439).
    For each of the mentioned assignment procedures any number of demand matrices can be
    selected for assignment.
    One demand matrix of one PrT transport system, for example, a car demand matrix is assigned.
    Multiple demand matrices which contain the demand for one or multiple PrT transport systems, for example, a car demand matrix and a HGV demand matrix are assigned simultaneously.
    Abbreviations used in the User Model PrT are listed in table 72.
    v0

    Free flow speed [km/h]

    t0

    Free flow travel time [s]

    vCur

    Speed in loaded network [km/h]

    tCur

    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)

    qmax

    Capacity [car units/time interval]

    Sat

    Volume/capacity ratio

    F ij

    Number of trips [veh/time interval] for relation from zone i to zone j.

    Demand matrix which contains the demand for all OD pairs.


    Table 72: Abbreviations used in the User model PrT.

    6.2

    Example network for PrT assignment procedures


    The effectiveness of PrT assignment procedures is illustrated in the example in illustration 59.
    The example analyzes the relation between traffic zone "village A" and traffic zone "city X". The
    following assumptions apply:
    Access and egress times are not considered, that is, they are set to 0 minutes.
    Turn penalties are not considered.
    Capacity and demand refer to one hour.
    The traffic demand between A-Village and X-City is 2,000 car trips (car.fma matrix) during
    peak hour.
    To explain simultaneous assignment of multiple demand matrices 200 additional HGV
    trips (hveh.fma matrix) are considered. One HGV corresponds to two car units.
    On federal roads (link type 20) there is a speed limit of 80 km/h for HGVs.

    228

    PTVGROUP

    6.2 Example network for PrT assignment procedures


    The example network contains three routes which connect A-Village and X-City. The routes
    run via the following nodes:
    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 mainly 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 long is an alternative route which only makes sense if the federal
    road is congested.

    Illustration 59: Example network


    LinkN- From
    o
    Node

    To Node

    Type

    Length
    [m]

    Capacity [car
    units/h]

    v0-PrT
    [km/h]

    10

    11

    20 Federal
    road

    5,000

    1,200

    100

    11

    20

    20 Federal
    road

    5,000

    1,200

    100

    20

    21

    20 Federal
    road

    5,000

    1,200

    100

    20

    40

    90 Rail track

    10,000

    21

    30

    20 Federal
    road

    5,000

    1,200

    100

    30

    31

    20 Federal
    road

    5,000

    1,200

    100

    31

    40

    20 Federal
    road

    5,000

    1,200

    100

    PTVGROUP

    229

    6.3 PrT paths


    LinkN- From
    o
    Node

    To Node

    Type

    Length
    [m]

    Capacity [car
    units/h]

    v0-PrT
    [km/h]

    11

    41

    30 Country
    road

    16,000

    800

    80

    40

    41

    30 Country
    road

    5,000

    800

    80

    10

    10

    12

    40 Other roads 10,000

    500

    60

    11

    12

    21

    40 Other roads 5,000

    500

    60

    Table 73: Example network


    The example network in table 73 is saved to the folder ...Users\Public\Public documents\PTV
    Vision\PTV Visum 13\Example_net.
    Version file: Example.ver
    Assignment parameters file: Auto.par

    6.3

    PrT paths
    All assignments in Visum in the PrT as well as in the PuT are route based. This means that possible paths in the assignment are calculated for each origin-destination relation and loaded
    with a demand share. All other results, especially the different network object volumes and the
    skim matrices are derived from these loaded paths. Paths are therefore the central result of the
    assignment procedure.
    table 74 shows a link-based display of the PrT paths obtained through equilibrium assignment
    in Example.ver.
    Origin zone Destination Path index Index
    zone
    100

    100

    100

    230

    200

    200

    200

    Link

    From node To node

    1
    1

    10

    11

    11

    20

    20

    21

    21

    30

    30

    31

    31

    40

    10

    11

    11

    41

    41

    40

    10

    10

    12

    PTVGROUP

    6.4 Impedance and VD functions


    Origin zone Destination Path index Index
    zone

    Link

    From node To node

    11

    12

    21

    21

    30

    30

    31

    31

    40

    Table 74: Link-based PrT paths of a PrT assignment


    For private transport, you can edit paths manually, as paths are then available as network
    objects (see "Paths" on page 63).

    6.4

    Impedance and VD functions


    Subjects
    Impedance of a PrT route
    Predefined VD functions
    Example of link impedance calculation
    User-defined VD functions

    6.4.1

    Impedance of a PrT route


    All assignment procedures are based on a short-route algorithm that determines low impedance routes. The impedance of a PrT route is volume-dependent and consists of the following impedances:
    Impedances of used links (see "Impedances of links" on page 232)
    Impedances of turns used, also called 'node impedance' (see "Impedances at node" on
    page 241)
    Impedances of the connectors used(see "Impedances of connectors" on page 232)
    Impedances of the main turns used (see "Impedances of main turns" on page 233)
    The route choices of travelers depend on objective and subjective factors. The route choice is
    particularly determined by the following skims:
    The anticipated travel time for the route
    Route length
    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. Impedance is therefore defined for each transport system and can be customized
    by the user. By default, it depends on the following variables:
    Transport system-specific travel time, in loaded network tCur [s]
    Link length [m]
    Transport system-specific road tolls [money units]

    PTVGROUP

    231

    6.4.1 Impedance of a PrT route


    User-defined AddValues
    Link type factor [-]
    You can also define the impedance in detail. You are then provided with all direct and indirect
    numerical attributes of the network objects links, turns, connectors and main turns, for the definition of the impedance of a route (see User Manual: Chpt. 18.2.2 , page 1908).
    When composing the impedance summands, it can be differentiated between two basic components:
    Summands, which apply depending on the traffic volumes (for example value calculated
    tCur with a VD function)
    Summands, which are not dependent on the network object volume (for example, toll or
    link length)
    The time tCur of a network object is calculated with capacity restraint functions (VD functions).
    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
    modeled (see "Predefined VD functions" on page 233).
    Because the variables have different units (seconds, meters, money units), impedance cannot
    be written in a universally applicable unit. For a combination of the variables, travel time, and
    road toll, it may be convenient to express impedance in terms of money units. In this case, travel times are converted into money units using a "value of time" factor.
    Impedances of links
    For every PrT-transport system of a link, a TSys-specific travel time (t0_TSys) for free flow is defined which is calculated from:
    link length
    permitted speed (v0_PrT) of the link used
    maximum speed of the transport system (v0_PrTSys)
    A capacity-dependent impedance function continuously adjusts this basic travel time depending on the current traffic volume (see "Predefined VD functions" on page 233).
    Impedances of turns (Impedances at node)
    Visum calculates turn impedances for every turn permitted at a node. A turn impedance includes an impedance time penalty t 0 which increases in dependence on volume and capacity.
    Because the turns are positioned at the node, the impedances at turns are often described as
    impedances at node (see "Impedances at node" on page 241).
    Impedances of connectors
    Connector impedances are regarded as follows:
    Absolute connectors are regarded as being volume-dependent. This means, that the
    TSys-specific connector time (t0_TSys) does not represent actual impedance which is
    volume-independent.

    232

    PTVGROUP

    6.4.2 Predefined VD functions


    For connectors defined by percentage, they are considered volume-dependent, if the
    option Connector weights apply to total trips (MPA off) is active. This means that with
    increasing volume, the actual connector time tCur_TSys will exceed the connector time t0_
    TSys of each connector (see "Predefined VD functions" on page 233). With a high value for
    parameter b in the VD function and usage of the equilibrium assignment, a relatively exact
    distribution of traffic onto the connectors can be achieved.
    Note: The impedance of turns and connectors in contrast to links only depends on the
    variable tCur and possibly on the AddValue. Because the impedance of a connector is
    not capacity-dependent, the following applies to the access and egress impedance: tCur
    = t0. The proportional distribution 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 then recalculated from the summed
    up volume total and the demand to be assigned in the current assignment, e.g. Vol(carbusiness) + Vol(car-private) + Demand(HGV) = 100% Connector capacity.
    Impedances of main turns
    Just like turn impedances, in Visum main turn impedances are calculated for each main turn
    permitted at a main node based on the volume and selectively a VD function, TModel or ICA.
    Preloaded volume
    When impedances are determined, preloaded volumes can be considered. Preloaded volumes can be either user-defined additional values or volume values which result from the assignment of a different matrix.

    6.4.2

    Predefined VD functions
    Travel times for PrT are determined by the saturation of links and turns which result from the
    traffic volume and the capacity of these network objects. Due to this, PrT travel times vary in
    contrast to PuT journey times, and can only be anticipated to a certain degree before a trip.
    The PrT travel time of a route between two zones consists of the following components:
    Access and egress times
    Travel time on links
    Turn time 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 turns at an intersection, the turn time t 0 is specified directly. In loaded
    networks, the link travel time and the turn time is determined by a so-called volume-delay function (or VD function). This capacity restraint function describes the correlation between the current traffic volume q and the capacity qMax. The result of the VD function is the travel time in the
    loaded network tcur. Visum provides several function types for the volume-delay functions:
    1. the BPR function in the Traffic Assignment Manual of the United States Bureau of Public
    Roads (illustration 60)
    2. a modified BPR function with a different parameter b for the saturated and unsaturated state
    (table 77)

    PTVGROUP

    233

    6.4.2 Predefined VD functions


    3. a modified BPR function, for which an additional supplement d per vehicle can be specified
    in the saturated state (table 78)
    4. the INRETS function of the French Institut National de Recherche sur les Transports et leur
    Scurit (illustration 61)
    5. a constant function where the capacity does not influence travel time (tCur= t0)
    6. and several functions for turning processes (i.e. t0 is added, not multiplied) as well as function type linear bottleneck which are used by turn type
    7. another modified BPR function (LOHSE) with a linear rise in the oversaturated section, in
    accordance with the queuing theories, in order to achieve more realistic times in the oversaturated section and a better performance in assignments since small changes to the
    volume do not result in disproportionate travel time changes. The function is monotonic,
    continuous, and differentiable even where sat = satcrit
    Note: In addition to the volume-delay functions provided in Visum, you can also specify user-defined VD functions (see "User-defined VD functions" on page 240).
    table 75 shows the variables used in the descriptions of the VD functions.
    sat

    Volume/capacity ratio
    satcrit

    Degree of saturation at which the linear section of the volume-delay function


    starts

    tcur

    Current travel time on a network object in loaded network [s] (tCur)

    t0

    Travel time on a network object with free flow time [s]

    Current volume = sum of volumes of all PrT transport systems including preloaded volume [car units/time interval]

    qmax

    Capacity [car units/time interval]


    Table 75: Variables used in VD functions
    The parameters mentioned in table 76 apply to all VD functions. Function-specific parameters
    are listed with the respective VD function.

    a, b, c

    User-defined parameters

    a [0.00;), b {0.00...10.00}, c [0.00;)


    Table 76: Parameters for all VD functions

    234

    PTVGROUP

    6.4.2 Predefined VD functions

    Illustration 60: VD function type BPR according to the Traffic Assignment Manual

    satcrit

    satcrit = 1

    Parameters a [0.00;), b, b {0.00...10.00}, c [0.00;)


    Table 77: VD function type BPR2 - modified BPR
    a, b, b, c

    , where
    satcrit

    satcrit = 1

    a [0.00;), b {0.00 ...10.00}, c [0.00;), d {0.00...100.00}


    Table 78: VD function type BPR3 - modified BPR
    a, b, c, d

    with
    a, c

    a [1.1;100), c [0.00;100)

    Table 79: VD function type CONICAL (Spiess)

    PTVGROUP

    235

    6.4.2 Predefined VD functions

    with
    a, c

    , where

    a [1.1;100), c [0.00;100)

    Table 80: VD function type CONICAL_MARGINAL


    A marginal-cost version of the CONICAL function, suggested by Spiess to calculate a system
    optimum instead of user optimum in equilibrium assignment.

    , where
    satcrit

    satcrit [0.00;10]

    a, b, c, d
    a [0,0001;100], b [0,0001;10000], c [0.00;100], d [0,0001;10000]
    Table 81: VD function type EXPONENTIAL

    The function models queuing at entry legs whose inflow is restricted by ramp metering signals.

    , where
    satcrit

    satcrit = 1

    current volume = sum of volumes of all PrT demand segments [car units/time
    unit] including basic volume (preloaded volume)

    user-defined parameter a {0.00..1.10}

    user-defined capacity parameter c [0;)


    Table 82: VD function type INRETS
    c

    236

    PTVGROUP

    6.4.2 Predefined VD functions

    Illustration 61: VD function type INRETS


    The impedance functions listed in table 83 are particularly suited to the modeling of turn impedances. A capacity-dependent wait time is thus added to each basic wait time t0.
    LOGISTIC
    QUADRATIC
    SIGMOIDAL_MMF_NODES (formerly SIGMOIDAL_MMF)
    SIGMOIDAL_MMF_LINKS (previously SIGMOIDAL_
    MMF2)
    Unlike SIGMOIDAL_MMF_NODES, the wait time term is
    not added to t0 but multiplied by it.
    a, b, c, d [0.00100.00}, f {0.00...10.00}.
    The value of parameter f of VD function types SIGMOIDAL_MMF_NODES and
    SIGMOIDAL_MMF_LINKS ranges from 0..100.
    Table 83: VD function types LOGISTIC, QUADRATIC, SIGMOIDAL_MMF_NODES,
    SIGMOIDAL_MMF_LINKS
    a, b, c, d

    PTVGROUP

    237

    6.4.2 Predefined VD functions


    AKCELIK
    The function describes delays at nodes with
    a = duration in hours
    b = family parameter
    d = capacity of lane per hour
    Table 84: VD function type AKCELIK

    AKCELIK2
    a = duration in hours
    b = family parameter
    d = 1 / Number of lanes (of the link)
    qmax = capacity of the network object (of the link)
    Unlike AKCELIK, the denominator of this function references directly to the capacity of the
    network object. Besides, AKCELIK2 is no wait time function at a node but models the
    speed reduction on a link. Value d is intentionally a free parameter, although alternatively
    the link attribute 'Number of lanes' could be evaluated directly. By removing this attribute
    which should always carry the physically existing number of lanes (for example for the Vissim export), a suitable value of d for example, can model the frictional loss by pulling in
    and out events for parking. d = 0.6 would therefore correspond to a slightly lower capacity
    than two lanes.
    Table 85: VD function type AKCELIK2

    satcrit

    satcrit [0.00;10]

    [(a + 1) t0] represents tCur with sat = 1


    a [0.00;1000]

    Determines the value of the increasing rise up to sat = satcrit


    b [0.00;10]

    Scaling parameter for the determination of the dimensions of q and qmax

    c [0.00;100]
    Table 86: VD function type LOHSE

    238

    PTVGROUP

    6.4.3 Example of link impedance calculation

    Illustration 62: VD function type LOHSE


    Linear bottleneck

    This function type stems from Metropolis and should not be used in static assignments, as
    it rises strongly when reaching the saturation while the previously augmenting VolCapRatio is unaccounted for.
    Table 87: VD function type Linear Bottleneck
    Some projects may require non-standard VD functions, e.g. because they include further link
    attributes or because the conversion of volumes to passenger car units (PCUs) is project-specific. In this case, you can add your own functions to the pre-defined volume-delay functions
    (see "User-defined VD functions" on page 240).

    6.4.3

    Example of link impedance calculation


    table 88 to table 91 shows an example in which link impedance consists of the 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.
    Link length

    10,000 m

    Permitted maximum speed v0 car

    130 km/h

    Permitted maximum speed v0


    HGV

    100 km/h

    PTVGROUP

    239

    6.4.4 User-defined VD functions


    Road toll for cars

    Road toll for HGV

    Capacity

    3,000 car units/h

    Car volume

    1,000 cars/h = 1,00 car units/h

    HGV volume

    100 HGV/h = 200 car units/h

    Value of time VOTCar

    18 /h = 0.005 /s

    Value of time VOTHGV

    36 /h = 0.010 /s

    VD function according to BPR

    with a = 1, b = 2, c = 1

    Table 88: Input data for link impedance calculation


    Car travel time in unloaded network

    t0 car = 10,000 3.6 / 130 = 277s

    Car travel time in loaded network

    tCur car = 277 (1+(1,200/3,000)) = 321s

    Car speed in loaded network


    vCur car = 10,000 3.6 / 321 = 112km/h
    Table 89: Car travel times and speeds

    HGV travel time in unloaded network

    t0 HGV = 10,000 3.6 / 100 = 360s

    HGV travel time in loaded network tCur HGV = MAX (321s; 360s) = 360s
    HGV speed in loaded network

    vCur HGV = 100 km/h

    HGV speed declines with a volume exceeding 1644 car units/h, if


    tcur = 277 (1+(1644/3000)) = 360s
    Table 90: HGV travel times and speeds

    Car impedance in loaded network

    RCar = 1 + 0.005 321 = 2.61

    HGV impedance in loaded network RHGV = 5 + 0.010 360 = 8.60


    Table 91: Calculation of link impedance for HGVs and cars

    6.4.4

    User-defined VD functions
    You can set up user-defined VD functions for the following use cases:
    To include further attributes for links, turns and connectors in the calculation
    To calculate PCUs in a non-standard way
    To define separate volume-delay functions for different transport systems
    Volume-delay functions are very often evaluated within the assignment methods, so computational efficiency is a key consideration. Therefore Visum adopts a compiled rather than an
    interpreted approach to user-defined volume-delay functions. Users program their functional

    240

    PTVGROUP

    6.5 Impedances at node


    forms as a dynamic-link library (DLL) following a given template. Then copy all *.dll files created to the following project directory, which by default is created during the installation and is
    scanned by Visum at start-up: %APPDATA%\PTV Vision\PTV Visum 13\UserVDF-DLLs (see
    User Manual: Chpt. 18.2.1.6 , page 1899).
    Note: A *.bmp file with identical file name which is stored in the same folder will be displayed for VDF selection.

    6.5

    Impedances at node
    Intersections are modeled as nodes or as main nodes in Visum. Intersections of roads and/or
    railway tracks are bottlenecks in an urban transport network. At the intersections, conflict
    points have to be passed in succession by the non-compatible traffic flows. The order in which
    the flows traverse the conflicting areas depends on the type of control:
    To choose the route within an assignment procedure, the impedance on alternative routes is
    decisive, which results in the sum of impedances of all traversed network objects. The bottleneck effect of a node is thus displayed for all variants of the traffic control by the impedance
    of the turn used. The impedance of turns usually corresponds exactly to the travel time tCur ,
    thus the time required to traverse the node in the turning direction of the route.
    For calculating tCur per turn Visum offers three different models that represent the different compromises between data entry and computing time on the one hand and accuracy and real-life
    situations on the other.
    Turns VDF (see "Node impedances of turns VD function" on page 243)
    Nodes VDF (see "Node impedance of nodes VD function" on page 243)
    Intersection Capacity Analysis ICA (see "Intersection Capacity Analysis according to the
    Highway Capacity Manual (ICA)" on page 244)
    To use ICA during assignment, select the method Node impedance calculation
    (ICA).
    Alternatively you can based on an assignment result select method From previous assignment with ICA.
    Comparing advantages and disadvantages in table 92 is to help you choose the appropriate
    calculation model for your project.
    Model

    Advantage

    Disadvantage

    Turns VDF (see


    "Node impedances
    of turns VD function" on page 243)

    Little input complexity (per


    turn merely capacity and t0)
    Calculation fast
    Assignment fast convergence

    Time required for the turning


    movement only takes the turning volume into account, not
    the amount of possible conflicting volumes (separable
    cost functions)

    Nodes VDF (see


    "Node impedance
    of nodes VD function" on page 243)

    Input complexity only slightly


    larger than for turn VD functions (additionally capacity
    and t0 for the node itself as

    Assignment convergence
    slower due to the inseparable
    penalty
    Compared to ICA, taking con-

    PTVGROUP

    241

    6.5 Impedances at node


    Model

    Advantage

    Disadvantage

    well as designating subordinated links)


    Calculation fast
    For subordinate turns at twoway stop nodes, the time
    required due to its own
    volume increases by an additional penalty, which
    depends on the total volume/capacity ratio of the node
    and therefore on the volumes of conflict flows.

    flicting volumes into account


    is extremely simpler due to
    the fixed penalty

    Node impedance
    calculation (ICA)
    (see "Intersection
    Capacity Analysis
    according to the
    Highway Capacity
    Manual (ICA)" on
    page 244)

    Impedance calculation precisely considers lane allocation and signal control.


    Special turn pockets for
    example, are capacity-increasing and dependent on the
    entered signal timing, protected and permitted turns
    are calculated correctly

    Input complexity considerably


    higher: Instead of capacity
    and t0, model the lane allocation at the node and where available - the signal
    control in detail
    Calculation more time consuming
    Assignment convergence
    slow due to the inseparable
    impedance model, sometimes without additional measures not at all

    From previous
    assignment with
    ICA (see "Assignment with ICA"
    on page 374)

    In the Assignment with ICA,


    convergence is reached by
    regular adjustment of the
    Turns VDFs to the wait times
    and capacities calculated by
    ICA.
    The HCM 2000 method used
    for ICA regards the lane allocation and conflicting turn
    flows in detail.

    Increased efforts required for


    the comprehensive modeling
    of geometry and control at the
    nodes to be regarded.
    Comparably computation
    time-consuming.

    Table 92: Advantages and disadvantages of the node impedance model


    Due to the reasons mentioned we recommend the following for the selection.
    For comprehensive models, modeling with VD functions for turns or nodes is appropriate.
    ICA cannot be recommended here, because the input complexity for the detailed supply
    of nodes with geometry and control data is usually too high. Furthermore, the result after
    each acceptable computing time due to the slow convergence of the assignment still contains approximation errors, which are around the same size as the accuracy gained
    through ICA.

    242

    PTVGROUP

    6.5.1 Node impedances of turns VD function


    ICA however, is the method of choice if you want to subsequently calculate and analyze
    the performance of one or more nodes of an existing assignment result. This is how you
    can determine which aspects of the node contribute to a high impedance. It is therefore
    sufficient to only model those nodes completely which have to be analyzed.
    With a classical assignment method (Equilibrium or Equilibrium_Lohse, for example), ICA
    is only conditionally recommended due to the known convergence difficulties, and it should
    only be applied to small-scale analyses with some 100 nodes. To avoid these problems,
    the Assignment with ICA method is recommended.
    With an equilibrium assignment, best results can be achieved with either the Equilibrium_
    Lohse method (see "Equilibrium_Lohse" on page 366) or the From previous assignment
    with ICA method (see "Assignment with ICA" on page 374), since these are more robust
    towards impedance variations.
    In most cases you will globally decide on a calculation model. You can however also combine
    different calculation methods within a network, (for example, Turns VD functions as standard
    model and ICA simply for very important nodes with complex lane allocation or large conflicting flows).
    All calculation models are based on turn volumes in car units per hour, which are determined
    through the user's settings, either from the assigned volume or from counted data via a factor.

    6.5.1

    Node impedances of turns VD function


    In the simplest calculation model t Cur, the time requirement of a turning vehicle is calculated
    from the turning time t 0 in the unloaded network and the saturation of turns using a VD function. You can use one of the pre-defined functional forms (see "Predefined VD functions" on
    page 233) as VD functions or select a user-defined functional form (see "User-defined VD functions" on page 240). Typical Turn VD functions make up the sum (not the product) of t0 and a
    saturation-dependent term. Examples are the VD functions Akcelik, Exponential, Constant,
    Logistic, Quadratic and TMODEL_Nodes.
    The attributes listed in table 93 are considered for the calculation.
    Network
    object

    Attribute

    Description / Effect

    Turn

    Capacity
    PrT

    The capacity of the turn in PCUs/hour

    Turn

    t0 PrT

    The time required for a turning movement in unloaded state

    Turn
    Type
    Usually specifies the direction of the turn
    Table 93: Attributes for impedance calculation based on turns VD function

    6.5.2

    Node impedance of nodes VD function


    In this model, turn delays are calculated in two steps. First, a node delay is calculated by applying a VD function to the vol/cap ratio of the node. Each turn penalty is the sum of node delay
    and the turn-specific time (calculated with VD function set for turns). Node delay only has an
    affect on turns from a non-prioritized approach. These approach links have to be marked with
    the attribute TModelSpecial (see User Manual: Chpt. 15.40 , page 1435).

    PTVGROUP

    243

    6.5.3 Intersection Capacity Analysis according to the Highway Capacity Manual (ICA)
    The attributes listed intable 94 are considered for the calculation.
    Network
    object

    Attribute

    Description / Effect

    Turn

    Capacity PrT The capacity of the turn in PCUs/hour

    Turn

    t0 PrT

    The time required for a turning movement in unloaded


    state

    Turn

    Type

    Usually specifies the turning direction

    Node

    Capacity PrT The total capacity of the node in PCUs/hour

    Node

    t0 PrT

    The additional time required for a non-prioritized turning


    movement (all the same) in unloaded state

    Table 94: Attributes for impedance calculation based on node VD function


    Turn time penalties are calculated according to the following formulas:
    vol(n)=vol(t)
    delay(n)=VDF (cap(n), vol(n))
    delay(t)=VDF (cap(t), vol(t))
    IF n has no link with TModelSpecial = 1, THEN
    tCur(t)=delay(t) + delay(n) for all turns t via node n
    IF n has at least one link with TModelSpecial = 1, THEN
    tCur(a)=delay(t) for all turns t with a 'from link' to which TModelSpecial = 0 applies
    tCur(a)=delay(t) + delay(n) for all turns t with a 'from link' to which TModelSpecial=1 applies

    6.5.3

    Intersection Capacity Analysis according to the Highway Capacity Manual (ICA)


    VD functions are usually used to model volume-dependent travel times on links (see "Impedance and VD functions" on page 231). They can also be used to model volume-dependent
    wait times for turns or complete nodes (see "Node impedances of turns VD function" on page
    243 and "Node impedance of nodes VD function" on page 243).
    By contrast the Highway Capacity Manual (HCM) published by the US Transportation Research Board contains internationally recognized guidelines on calculating the level of service
    and other performance indicators for intersections, based on the detailed junction geometry
    and various control strategies. Visum computes performance indicators such as capacity,
    delays or LOS either according to the guidelines defined in the operation model HCM 2000 or
    according to HCM 2010 guidelines.
    Note: In the following the implementation of the HCM 2000 in Visum is described. For
    most of the control types (except for signalized nodes), the HCM 2010 differs from the
    HCM 2000 in only a few aspects. The deviating portions are highlighted in the text. Since
    the HCM is provided in English only, certain English expressions and descriptions have
    not been translated for a better traceability in the original document.

    244

    PTVGROUP

    6.5.3.1 Uncontrolled nodes


    For intersection points of the same level, the calculation differentiates between the following
    control types (attribute Effective control type at node):
    Uncontrolled nodes (see "Uncontrolled nodes" on page 245)
    Signalized intersections (see "Signalized nodes" on page 246)
    Static priority rules using the traffic signs StVO 306 or 301 (German road traffic regulations) for the main road and StVO 205 or 206 for the subordinate road (see "Two-way
    stop nodes" on page 268)
    All-Way stops (only for North America) (see "All-way stop" on page 279)
    Roundabouts
    Visum offers two different models for the analysis of roundabouts:
    The method developed by R. M. Kimber, (Kimber 1980), (Kimber, Hollis 1979), (Kimber, Daly 1986), which is also described in the British guideline TD 16/93 "The Geometric Design of Roundabouts", is based on the empirical study of numerous
    roundabouts and the statistical adjustment of a model which estimates capacities in
    dependency of the geometry (see "Roundabouts according to the TRL/Kimber
    method" on page 293).
    The method described in the Highway Capacity Manual 2010, chapter 21 (see "Roundabouts according to the HCM 2010 method" on page 287).
    The method according to TRL/Kimber has the advantage of taking comprehensive empirical results on the influence of geometry on the permeability of a roundabout into consideration and has been successfully implemented for nearly three decades.
    The method according to HCM is recommended, if in theory you prefer consistency for all
    control types (roundabouts also according to HCM like signalized and two-way stop nodes)
    within a project. Furthermore, the method is not dependent on observations which were
    only obtained through driving behavior studies in Great Britain.
    Not the control type, but the effective control type is decisive for the calculation. These two
    values differ, as signalized nodes are considered yield-controlled node, if no SC is allocated
    to them or if the SC has been switched off (signal control attribute Turned off).
    Notes: Throughout the model description, special provision for right or left turns relates to
    right-hand traffic. For Visum models with left-hand traffic, the roles of right and left turns
    are reversed (see User Manual: Chpt. 14.5 , page 864).
    U-turns are never considered in HCM 2000. In Visum it is possible to treat U-turns as far
    left turns through the corresponding setting in the procedure parameters for intersection
    impedance analysis (in left-hand traffic accordingly as far right turns). This calculation is
    then no longer HCM conform. HCM 2010 regards U-turns at two-way stop nodes. Here,
    the processing is performed according to HCM 2010 in Visum. Other control types are
    processed according to HCM 2000.
    6.5.3.1

    Uncontrolled nodes
    For uncontrolled nodes the impedance of a turn is calculated using a VD function from the
    node volume (= Sum of turn volumes) and the node capacity, therefore exactly like calculating
    the model Nodes VD function (see "Node impedance of nodes VD function" on page 243),
    however without a term for each turn.

    PTVGROUP

    245

    6.5.3.2 Signalized nodes


    The Visum attributes listed in table 95 are considered for calculation.
    Network
    object

    Attribute

    Description / Effect

    Node

    Capacity
    PrT

    The total capacity of the node in PCUs/hour

    Node

    t0 PrT

    The time required in a turning movement (all equal) in unloaded


    state

    Table 95: Attributes for calculation of uncontrolled nodes


    6.5.3.2

    Signalized nodes
    Notes: In the HCM 2000, chapter 16 describes signalized nodes. In HCM 2010, find the
    descriptions in the chapters 18 and 31.
    Instead of the method described here for signalized nodes, the method for yield-controlled nodes is applied to nodes and main nodes of the signalized control type, to which
    no SC has been allocated or whose SC has been turned off.
    The basic flow chart for performing capacity analyses for signalized intersections is displayed
    in illustration 63 . You input the intersection geometry, volumes (counts or adjusted demand
    model volumes), and signal timing. The intersection geometry is deconstructed into lane (or
    signal) groups, which are the basic unit of analysis in the HCM method.
    A lane (or signal) group is a group of one or more lanes on an intersection approach having
    the same green stage. For example, if an approach has just one pocketed exclusive left turn
    and one shared through and right turn, then there are usually two lane groups the left and
    the shared through/right.
    Note: According to HCM 2010, the lane allocation follows different rules. Here, shared
    lanes always form a separate lane group. For more details, please refer to HCM 2010,
    page 18-33.
    The volumes are then adjusted via peak hour factors, etc. For each lane group, the saturation
    flow rate (SFR), or capacity, is calculated based on the number of lanes and various adjustment factors such as lane widths, signal timing, and pedestrian volumes. Having calculated
    the demand and the capacity for each lane group, various performance measures can be calculated. These include, for example, the v/c ratio, the average amount of control delay by
    vehicle, the Level of Service, and the queues.

    246

    PTVGROUP

    6.5.3.2 Signalized nodes

    Illustration 63: Capacity analysis process for signalized nodes


    Note: For HCM 2010, the corresponding flow diagram can be found in HCM 2010, page
    18-32.
    If you use the HCM 2000 or HCM 2010 operations model for signalized nodes, the Visum attributes in table 96 aufgefhrten Visum will show effect. Make sure that they are set to realistic
    values prior to running the analysis.
    Alternatively to the calculation method according to HCM, you can apply one of the following
    methods:
    ICU1
    ICU2
    Circular 212 Planning
    Circular 212 Operations
    From the HCM, these procedure differ in just three issues:
    Definition of the ideal saturation flow rate
    Calculation of the final saturation v/s (volume/saturation flow rate) for the node
    Determination of the Level of Service (LOS)
    Steps step 6, step 9, and step 13 below describe the calculation variants in detail.

    PTVGROUP

    247

    6.5.3.2 Signalized nodes


    Note: Visum allows for control access to RBC and Vissig controllers. Vissig controllers
    provide fixed-time control strategies. RBC controllers provide pre-timed or actuated control strategies (also fully or semi-actuated). HCM 2010 provides a computation method
    for fixed-time strategies and for traffic-actuated strategies as well. Visum uses fixed-time
    strategies for Vissig controllers. The strategy used for RBC controllers depends on the
    type of traffic actuation. For a description of this method, please refer to HCM 2010, chapters 18 and 31. Prior to the computation, Visum imports the signal control data for the control strategy from the corresponding control file.

    248

    Network
    object

    Attribute

    Description / Effect

    Link

    ICAArrivalType

    Level of platooning in traffic arriving at the ToNode,


    subsequently used in steps step 10 + step 14a

    Link

    ShareHGV

    Proportion of heavy goods vehicles, used in step


    6b. One value applies to all turns originating from
    the link

    Link

    Space per PCU

    Used in step 6 for calculation of the number of


    vehicles that fit on a pocket lane

    Link

    Slope

    Used in step 6

    Node

    ICAPHFVolAdj

    Factor for adjustment of initial volumes to peak volumes. Volumes are divided by both node and turn
    adjustment factors.

    Node

    ICALossTime

    Used in step 9. Only required for SG-based signal


    control. For other types of signal control the value is
    inferred automatically.

    Node

    ICAUsePresetLossTime

    Decides whether the node attribute ICALossTime


    or an automatically calculated value is to be used
    for loss time computation in step step 9.

    Node

    ICAIsCBD

    Is the node located in the Central Business


    District?; used in step 6e

    Node

    ICASneakers

    Number of vehicles which can line up in the node


    area during a cycle. The value in [veh] applies to all
    movements at the node The cycle time is used for
    the minimum capacity calculation for each movement.

    Node

    SC number

    Points to the signal control

    Geometry

    All

    Geometry data of lanes, lane turns and crosswalks

    Turn

    ICAPHFVolAdj

    Initial volume adjustment to peak period; volumes


    are divided by both node and turn adjustment factors

    Turn

    ICA Preset saturation


    flow rate

    Overwrites optionally the global saturation flow rate


    in the procedure parameters. Can be overwritten

    PTVGROUP

    6.5.3.2 Signalized nodes


    Network
    object

    Attribute

    Description / Effect
    by the specific lane value of this attribute, if applicable.

    Turn

    ICAUpstreamAdj

    Adjustment factor for upstream filtering / metering,


    used in steps step 10b +step 14b

    Signal Con- All


    trol

    Definition of signal groups, stages (where applicable), and signal timing

    SC

    Used intergreen
    method

    Is used in step 9 for loss time calculation

    SC

    Turned off

    If an SC is marked as 'turned off', the node will be


    calculated according to the yield controlcontrol
    type.

    Signal
    group

    ICA loss time adjustment

    Is added to the actual green time. The actual green


    time and ICA loss time adjustment sum up to the
    green time on which all computations are based.

    Signal
    group

    ICA start-up loss time

    affects calculation of effective green time according


    to HCM formula

    Leg

    ICA bus rate

    Number of stops in Veh/h, used to calculate the


    adjustment factor for the saturation flow rate in
    order to account for bus stops according to HCM formula.

    Leg

    Has on-street parking


    on right/left

    Describes whether parking is allowed on the right


    or left side of the street, is used to calculate the
    adjustment factor of the saturation flow rate in order
    to account for parking according to the HCM formula.

    Leg

    On-street parking
    Number of parking maneuvers / h on the right or left
    maneuver rate right/left side of the street, is used to calculate the adjustment factor of the saturation flow rate in order to
    account for parking according to the HCM formula.

    Leg

    Bicycle volume

    Number of bicyclists per hour for the determination


    of the adjustment factor for the saturation flow rate.

    Lanes

    Number of vehicles

    User-defined number of vehicles 0.0 the pocket


    accommodates. This attribute is only regarded if
    the attribute Use number of vehicles is true and if
    the global procedure parameter 'Regard pocket
    length for saturation flow rate calculation' is active.

    Lanes

    Use number of vehicles

    Decision, whether Number of vehicles of the lane


    shall be used. If this attribute is not true, the number
    of vehicles is determined from the pocket length
    and the attribute Space per PCU.

    PTVGROUP

    249

    6.5.3.2 Signalized nodes


    Network
    object

    Attribute

    Description / Effect

    Lanes

    Length

    Lane length if pockets are concerned. This attribute


    is only regarded if the attribute Use number of
    vehicles is not true and if the global procedure
    parameter 'Regard pocket length for saturation flow
    rate calculation' is active. The number of vehicles is
    calculated from the length of the pocket and the
    attribute Space per PCU.

    Lanes

    Width

    Width of the lane. On this basis, the saturation flow


    rate is calculated for the lane group to which the
    lane belongs. The calculated lane group width is
    the mean value derived from the width values of all
    lanes of this group.

    Lanes

    ICA Preset saturation


    flow rate

    Saturation flow rate for the lane after consideration


    of all adjustment factors. Use this attribute to set the
    saturation flow rate directly, if the HCM-based
    adjustment factors do not reflect the actual circumstances of the lane. This value overwrites the
    procedure parameter value and also turn-related
    values, if applicable.

    Lane

    ICA Use preset saturation flow rate

    Decision, whether the internally calculated saturation flow rate shall be replaced by the ICA Preset
    saturation flow rate value.

    Lanes

    ICA user-defined utilization share

    Utilization share of the lane within a multi-lane


    group. The sum of the input shares is automatically
    scaled to 100%, thus you can enter relative weights
    per lane. This value is used in step step 6.

    Lanes

    ICA use user-defined


    utilization share

    Decision, whether the internally calculated utilization share shall be replaced by the ICA userdefined utilization share value.

    Crosswalk

    Pedestrian volume

    Number of pedestrians per hour for the determination of the adjustment factor for the saturation
    flow rate.

    Table 96: Input attributes for signalized nodes


    Notes: The link attribute Turn on red is not regarded for calculation.
    Output is possible through the attributes listed in table 97.

    250

    PTVGROUP

    6.5.3.2 Signalized nodes


    Network
    object

    Attribute

    Description / Effect

    Node

    Turn tCur maximum


    Turn tCur mean
    Turn tCur total

    Sum, average, max of turn tCur. Now obsolete,


    since available as indirect attributes, but retained for backward compatibility.

    Node

    Design volume capacity ratio The volume/capacity ratio based on the design
    PrT
    volume

    Node

    Design volume PrT [veh]

    The volume in [veh/h] passed into the HCM calculation, as defined in the procedure parameters

    Node

    Design volume PrT [PCU]

    The volume in [PCU/h] passed into the HCM calculation, as defined in the procedure parameters

    Node

    Level of service

    Node

    Level of service mean delay

    Turn

    Design volume PrT [veh] ...

    The volume in [veh/h] passed into the HCM calculation, as defined in the procedure parameters

    Turn

    Design volume PrT [PCU]...

    The volume in [PCU/h] passed into the HCM calculation, as defined in the procedure parameters

    Turn

    ICA final volume

    After all adjustments

    Turn

    ICA final capacity

    Effective capacity, taking into account all opposing flows etc.

    Turn

    ICA final saturation flow rate

    After all adjustments

    Turn

    ICA average back of queue

    Average queue length

    Turn

    ICA back of queue for defined percentile

    Percentile of queue length. Specify in the procedure parameters which percentile is calculated.

    Turn

    Level of service

    Level of service of the turn

    Turn

    tCur-PrTSys

    TSys-specific travel time tCur in loaded network

    Table 97: Output attributes for signalized nodes


    Step 1: Lane volume calculation based on movement volumes
    This step distributes the movement volumes to lanes according to the user-defined geometry.
    The basic distribution rule is to distribute the volumes uniformly to the lanes while taking the
    input movement volumes into account. The implemented method is the same as in the All-Way
    stop method (see "All-way stop" on page 279). You can overwrite a lane's utilization share
    within its lane group, if applicable (lane attribute ICA user-defined utilization share).
    Here, HCM 2010 and HCM 2000 differ significantly. According to HCM 2010, the calculation is
    much more complex. In HCM 2010, lane volume calculation is an iterative process taking the

    PTVGROUP

    251

    6.5.3.2 Signalized nodes


    saturation flow rates into account. For a description, please refer to HCM 2010, pages 31-30 to
    31-37.
    Step 2: Volume adjustments by means of peak hour factors
    The input lane volumes are adjusted to represent the peak hour volumes through the peak
    hour factor (phf). The phf is defined as:
    vi = vg / PHF
    where
    vi

    adjusted volume for lane group i

    vg

    unadjusted (input) volume for lane group g

    PHF

    peak hour factor (0 to 1.0)

    Step 3: Calculation of de facto lane groups left/though/right


    De facto lane groups are shared lanes with 100% of their volume making one movement. For
    example, if a lane group is a shared left and through lane, and 100% of the lane volume is
    making a left movement, then the lane group is converted to a de facto exclusive left lane
    group.
    In the HCM 2010, the set of lane groups is not affected by the volumes of turning movements.
    As described above, shared lanes always form a lane group of its own, even if only a single turning direction is used actually.
    Step 4: Calculation of the types of left turns
    The type of left turn needs to be determined in order to calculate the left turn adjustment factor.
    The left turn type is set as follows:
    Fully controlled if all turns of an approach are conflict free during their green times.
    Fully secured if the left turns are conflict free during green time.
    Fully secured + permitted if during green time left turns are first fully secured and then permitted.
    Permitted + fully secured if during green time left turns are first permitted and then fully
    secured.
    Without left turn stage, all other cases.
    Step 5: Proportions of left turning and right turning vehicles calculation by lane group
    The proportion of right and left turn volume by lane group needs to be calculated.
    PLT = vLT / vi
    PRT = vRT / vi
    where

    252

    PLT

    proportion left turn volume by lane group

    PRT

    proportion right turn volume by lane group

    PTVGROUP

    6.5.3.2 Signalized nodes


    vi

    adjusted volume by lane group

    vLT

    volume of left turning vehicles by lane group

    vRT

    volume of right turning vehicles by lane group

    In HCM 2010, the iterative method mentioned in step 1 is used for the calculation of the turning
    movement proportions on shared lanes. For the description in detail, please refer to HCM
    2010, page 31-30 et seqq.
    Step 6: Saturation flow rate calculation by lane group
    The saturation flow rate is the amount of traffic that can make the movement under the prevailing geometric and signal timing conditions. The saturation flow rate starts with an optimum
    capacity, which is usually is 1,900 vehicles per hour, per lane (vphpl), according to HCM 2000
    and HCM 2010.
    For calculation variants ICU1 and ICU2, however, the ideal saturation flow rate is 1,600 vehicles per hour, per lane. For the Circular 212 variant, it is taken from the table below:
    Method

    2 stages

    3 stages

    4+ stages

    Planning

    1,500

    1,425

    1,375

    Operations

    1,800

    1,720

    1,650

    This number decreases due to various factors. The SFR is defined as:
    si = (so)(N) (fw)(fHV)(fg)(fp)(fa)(fbb)(fLu)(fRT)(fLT)(fLpb)(fRpb)
    where
    si

    saturation flow rate of lane group i

    so

    ideal saturation flow rate per lane (generally 1,900 vphpl)

    Number of lanes in lane group

    fw

    factor for lane width adjustment

    fHV

    HGV adjustment factor

    fg

    adjustment factor for approach grade

    fp

    adjustment factor for parking

    fa

    adjustment factor for the position of the link to city center (CBD true/false)

    fbb

    adjustment factor for bus stop blocking

    fLu

    adjustment factor for lane usage

    fRT

    adjustment factor for right turns

    fLT

    adjustment factor for left turns

    PTVGROUP

    253

    6.5.3.2 Signalized nodes


    fLpb

    adjustment factor for pedestrians and bicyclists on left turns

    fRpb

    adjustment factor for pedestrians and bicyclists on right turns

    First the description of the main calculation is described and then the various SFR adjustment
    factors are calculated.
    If an ICAIdealSatFlowRate is specified for a turn, it will replace the final result of step 5. All
    adjustment calculations are then bypassed.
    The calculations according to HCM 2000 or HCM 2010 are similar. The set of factors taking
    effect on the saturation flow rate is the same. Merely the calculations of the factors fw (HCM
    2010, page 18-36), f Lpb and f Rpb differ. The latter are calculated by means of the iterative
    method, which is described in HCM 2010, pages 31-30 to 31-37.
    Deviating from HCM, the optimal saturation flow rate so of pocket lanes can also be calculated
    by the number of vehicles which can be accommodated there. The number n of vehicles can
    be set by lane. Alternatively, it results from the division of the pocket lane length by the standard vehicle length which is set by link.
    The alternative calculation method using lane length data is only applied, if the lane group consists of one or more straight through lane (s) and exactly one pocket lane. The pocket lane
    must be of a straight through lane or a through-left type or a through-right type lane. If these
    conditions are not satisfied, the regular HCM calculation method will be applied.
    The optimal saturation flow rate so of a two-lane group, which consists of a through lane and a
    pocket, where there is space for n vehicles, then is as follows:

    Here, s o is the ideal saturation flow rate, n is the number of vehicles which can be accommodated on the pocket, gi is the effective green time and sf is the resulting saturation flow rate
    of the lane group.
    For shared lanes, the calculation is more complex. Taking a through lane with only straight
    turns and a shared left/straight pocket, then the resulting saturation flow rate sf is as follows:

    Here, vLT and v ST are the volumes of the left and the straight turns, s LT is the ideal saturation
    flow rate of the left turn - therefore 1,900 vphpl - and s ST is the ideal saturation flow rate of the
    through lanes which results from the first equation.
    Step 7: Calculation of actual green times
    The effective green time (or actual green time for a lane group) needs to be calculated next.
    The effective green time results as follows:
    gi = Gi + li
    where
    254

    PTVGROUP

    6.5.3.2 Signalized nodes

    gi

    effective green time per lane group

    Gi

    green time per lane group

    li

    loss time adjustment per signal group

    Step 8: Capacity calculation per lane group


    Related to the SFR is the capacity. The saturation flow rate is the capacity if the movement has
    100% of the green time (this means, the signal is always green for the movement). The capacity, however, accounts for the fact that the movement must share the signal with the other
    movements at the intersection, and therefore scales the SFR by the percent of green time in
    the cycle. The capacity of a lane group is then defined as follows:
    ci = si (gi / C)
    where
    ci

    capacity i

    si

    saturation flow rate i

    cycle time

    gi / C

    green ratio i

    Step 9: Calculation of the critical vol/cap ratio for the entire intersection
    The critical v/c ratio of nodes is defined below. The HCM method is concerned with the critical
    lane group for each signal stage. The critical lane group is the lane group with the largest volume/capacity ratio unless there are overlapping stages. If there are overlapping stages, then
    the maximum of the different combinations of the stages is taken as the max. For the description of this method, please refer to HCM 2000, page 16-14, or HCM 2010, page 18-41.
    Only if the intergreen method Amber and allred is used for the signal control, loss times will
    be determined at all. Per signal group, the loss time results from the amber time and allred
    time total minus loss time adjustment.

    where
    Xc

    critical saturation (v/c ratio) per intersection


    volume/capacity ratios for all critical lane groups

    cycle time

    loss time total of the signal groups of all critical lane groups

    Below is an example calculation of critical lane group per signal stage with overlap.

    PTVGROUP

    255

    6.5.3.2 Signalized nodes


    For computation variant ICU1, Xc is defined as follows:

    For computation variant ICU2, Xc is defined as follows:

    Step 10: Mean total delay per lane group


    In addition to calculating the critical v/c per intersection, the mean delay per vehicle is calculated by the HCM method. The mean total delay is defined below.
    di = dUiPF + dIi + dRi
    where
    di

    mean delay per vehicle for lane group

    dUi

    uniform delay

    dIi

    incremental delay (stochastic)

    dRi

    delay residual demand

    PF

    permanent adjustment factor for coordination quality (see "Signal coordination


    (Signal offset optimization)" on page 302)

    In HCM 2010, the equation looks likewise. However, factor PF has been implemented in factor
    dUi. For the description of the calculation procedure, please refer to HCM 2010, page 18-45.

    where
    fPA

    lookup value (HCM attachment 16 12) based on arrival type

    RP

    lookup value (HCM attachment 16 12) based on arrival type

    Step 10a: Calculation of the uniform delay for each lane group
    The uniform delay is the delay expected given a uniform distribution for arrivals and no saturation. It is calculated as follows:

    256

    PTVGROUP

    6.5.3.2 Signalized nodes

    where
    dUi

    uniform delay for lane group i

    gi
    Xi = v/c
    Step 10b: Calculation of the incremental delay for each lane group
    The incremental delay is the random delay that occurs since arrivals are not uniform and some
    cycles will overflow. It is calculated as follows:

    where
    dIi

    incremental (random) delay for lane group i

    ci

    capacity for lane group i

    Xi = v/c

    volume/capacity ratio

    duration of analysis period (hr) (default 0.25 for 15 min)

    ki

    lookup value (HCM attachment 16 13) based on the controller type

    Ii

    upstream filtering / metering adjustment factor (set to 1 for isolated intersection)

    Step 10c: Delay calculation for the residual demand per lane group
    Residual demand delay is the result of unmet demand at the beginning of an analysis period.
    It is only calculated if an initial unmet demand is entered for the beginning of the analysis
    period (Q). It is set to 0 in the current implementation. It is calculated as follows:

    where
    dRi

    residual demand delay for lane group i

    Qbi

    initial unmet demand at the start of period T in vehicles for lane group (default 0)

    ci

    Capacity

    PTVGROUP

    257

    6.5.3.2 Signalized nodes


    T

    Duration of analysis time slot (hr) (default 0.25 for 15 min)

    ui

    delay parameter for lane group (default 0)

    ti

    duration of unmet demand in T for lane group (default 0)

    Step 11: Delay calculation for the approach


    The total delay per vehicle for each lane group can be aggregated to the approach and to the
    entire intersection with the following equations. The approach delay is calculated as the weighted delay for each lane group.

    where
    dA

    mean delay per vehicle for approach A

    di

    delay for lane group i

    Vi

    volume for lane group i

    Step 12: Delay calculation for the intersection


    The intersection delay is calculated as the weighted delay for each approach.

    where
    dI

    mean delay per vehicle for intersection I

    dA
    VA
    Step 13: Level of Service calculation
    For the computation variant HCM 2000, the level of service is defined as a value which is
    based on the mean delay of the node.
    LOS Mean delay/vehicle

    258

    0 10 sec.

    10 20 sec.

    20 35 sec.

    35 55 sec.

    55 80 sec.

    80 + sec.
    PTVGROUP

    6.5.3.2 Signalized nodes


    In HCM 2010, the level of service is automatically classified as F, if v/c (volume/capacity ratio)
    exceeds the value 1.
    For the variants ICU 1, ICU2, and Circular 212, the level of service is defined through the saturation v/s (volume/saturation flow rate) of the node:
    LOS volume/saturation flow rate
    A

    0.000 - 0.600

    0.601 - 0.700

    0.701 - 0.800

    0.801 - 0.900

    0.901 - 1.000

    >1.000

    Step 14: Mean queue length calculation per lane group


    Queue lengths are also calculated by the HCM 2000 method. In HCM 2010, the method differs. For this description, please refer to section 31-4, page 31-67 et seqq.
    The equation for the calculation of the mean queue length is as follows:
    Q = Q1 + Q2
    where
    Q

    mean queue length maximum distance measured in vehicles the queue


    extends on average signal cycle

    Q1

    mean queue length for uniform arrival with progression adjustment

    Q2

    incremental term associated with random arrival and overflow to next cycle

    Step 14a: Calculation of the number of residual vehicles after the first cycle
    Q1 represents the number of vehicles that arrive during the red stages and during the green
    stages until the queue has dissipated.

    where
    PF2

    progression factor 2

    vi

    volume of lane group i per lane

    cycle time

    PTVGROUP

    259

    6.5.3.2 Signalized nodes


    gi

    effective green time of lane group i

    Xi

    volume/capacity ratio of lane group i

    where
    PF2

    progression factor 2

    vi

    volume of lane group i per lane

    cycle time

    gi

    effective green time of lane group i

    si

    saturation flow rate for lane group i

    RP

    platoon ratio based on lookup table for arrival type

    Step 14b: Calculate second-term of queued vehicles, estimate for mean overflow queue

    where
    T

    Analysis period (usually 0.25 for 15 minutes)

    adjustment factor for early arrival

    Qb

    initial queue at start of period (default 0)

    ci

    capacity for lane group i

    k = 0.12 I (sigi / 3,600) 0.7 for fixed-time signal


    k = 0.10 I (sigi / 3,600) 0.6 for demand-actuated signal
    I

    upstream filtering factor (set to 1 for isolated intersection)

    Step 15: Calculation of the queue length percentile


    After calculating the mean back of queue, the percentile of the back of queue is calculated as
    follows:

    260

    PTVGROUP

    6.5.3.2 Signalized nodes


    where
    Q

    mean back of queue

    percentile

    pre-timed signal

    70%

    P1

    P2

    P3

    actuated signal
    P1

    P2

    P3

    85%

    1.2

    0.1

    1.1

    0.1

    40

    90%

    1.4

    0.3

    1.3

    0.3

    30

    95%

    1.5

    0.5

    1.4

    0.4

    20

    98%

    1.6

    1.0

    1.5

    0.6

    18

    1.71.7

    1.5

    1.71.7

    1.0

    13

    Saturation flow rate adjustment factors


    We now return to the calculation of the saturation flow rate (see "Saturation flow rate calculation by lane group" on page 253), which involves several adjustment factors.
    Step 6 a: Calculate lane width adjustment factor

    where
    fw

    lane width adjustment factor

    mean lane width ( 8) (ft)

    This method differs in HCM 2010. For a description, please refer to HCM 2010, page 18-36.
    Step 6b: Calculate heavy goods vehicle factor

    where
    fHV

    adjustment factor for heavy goods vehicles

    %HV

    percentage of HGV per lane group

    EP

    passenger car equivalent factor (2.0 / HV)

    Step 6c: Calculate approach grade adjustment factor

    PTVGROUP

    261

    6.5.3.2 Signalized nodes


    where
    fg

    adjustment factor for approach grade

    %G

    approach grade as percentage (-6% to +10%)

    Step 6d: Calculate parking adjustment factor


    fP is calculated as follows:

    where
    fp

    parking adjustment factor (1.0 if no parking, otherwise 0.050)

    number of lanes in lane group

    Nm

    number of parking maneuvers per hour (only for right turn lane groups) (0 to
    180)

    In Visum, enter f P which is calculated by the formula, as attribute ICA parking directly at the
    node leg.
    Step 6e: Calculate adjustment factor for position to city center
    fa = 0.9 if link is in the city center (CBD), otherwise 1.0
    where
    fa

    adjustment factor for position

    CBD

    indicates a central business district

    Step 6f: Calculate bus stop blocking factor

    where

    262

    fbb

    bus stop blocking adjustment factor ( 0.05)

    number of lanes in lane group

    NB

    number of bus stop events per hour (does not apply to left turn lane groups) (0
    to 250)

    PTVGROUP

    6.5.3.2 Signalized nodes


    In Visum, enter fbb which is calculated by the formula, as attribute ICA bus blockage directly at
    the node leg.
    Step 6g: Calculate lane utilization adjustment factor

    where
    fLu

    adjustment factor lane utilization

    vg

    unadjusted (input) volume for lane group g

    vgl

    unadjusted (input) volume for lane with highest volume in lane group (veh per
    hour)

    For this adjustment factor, an HCM lookup-table is regarded (HCM 2000: table 10-23 on page
    10-26; HCM 2010: table 18-30 on page 18-77). Alternatively, lane attribute values can be
    used (ICA user-defined utilization share and ICA use user-defined utilization share).
    Step 6h: Calculate right turn adjustment factor

    where
    fRT

    right turn adjustment factor ( 0.05)

    PRT

    proportion of right turn volume for lane group

    The calculation according to HCM 2010 differs. For shared lanes, the adjustment factor is no
    longer explicitly calculated. For more details, please refer to HCM 2010, page 18-38.
    Step 6i: Calculate left turn adjustment factor
    The left turn adjustment factor is the most complex of the factors. Here, HCM 2000 and HCM
    2010 differ significantly. For the description, please refer to HCM 2010, page 18-38 and pages
    31-30 to 31-37.
    The calculation is simple for protected left turns. However, if there is permitted phasing, then
    the equation is quite complex. It is as follows:

    PTVGROUP

    263

    6.5.3.2 Signalized nodes

    where
    fLT

    adjustment factor for left turns

    PLT

    proportion of left turn volume for lane group

    For permitted staging, there are five cases. When there is protected-plus-permitted staging or
    permitted-plus-protected staging, the analysis is split into the protected portion and the permitted portion. The two are analyzed separately and then combined. Essentially this means
    treating them like separate lane groups. Refer to the HCM for how to split the effective green
    times among the protected and permitted portions.
    1. Exclusive lane with permitted phasing use the general equation below
    2. Exclusive lane with protected-plus-permitted phasing use 0.95 for the protected portion
    and the general equation below.
    3. Shared lane with permitted phasing use the general equation below
    4. Shared lane with protected-plus-permitted phasing use the equation above for protected
    phasing portion and the general equation below for the permitted portion
    5. Single lane approach with permitted left turns use the general equation below
    The general equation for calculating fLT for permitted left turns is listed below. Note that this is
    not the exact HCM 2000 equation since there are a few different versions depending on the
    situation shared/exclusive lane, multilane/single lane approach, etc. But the equation is similar regardless of the situation. This general equation is the equation for an exclusive left turn
    lane with permitted phasing on a multilane approach opposed by a multilane approach.
    The equation is basically the percentage of the time when lefts can make the turn times an
    adjustment factor. The adjustment factor is based on the portion of lefts in the lane group and
    an equivalent factor for gap acceptance time that is based on the opposing volume. The calculation of the percentage of the time when lefts can make the turn is a function of the opposing volume and their green time. The equation is as follows:

    fLTmin = 2 (1 + PL) / g

    gu = g - gq (if gq 0, else gu = g)

    264

    PTVGROUP

    6.5.3.2 Signalized nodes

    where
    fLT

    Global adjustment factor for left-turns

    Minimum value for adjustment factor

    Effective non-protected green time for left-turn lane group

    gu

    Effective non-protected green time for left-turns crossing a conflicting flow

    PL

    Share of left-turns using lane L

    EL1

    Through equivalent for non-protected left-turns (veh/hr/lane) (look-up value


    depends on conflict flow volume)

    gq

    Effective non-protected green time, while left-turns are blocked completely and
    the spill-back of the conflict flow is reduced

    go

    Effective green time for conflict flow

    Number of lanes in lane group

    LTmin

    volc
    Corrected conflict flow per lane per cycle =
    No

    Number of lanes in the lane group of the conflict flow

    vo

    Corrected conflict flow

    fLUo

    Lane utilization factor for conflict flow

    qro

    Opposing queue ratio = max[1 - Rpo (go / C), 0] (Rpo = look-up value depends on
    ArrivalType)

    tl

    Loss time for left-turn lane group

    The opposing volume is calculated from the signal groups that show green while the subject
    lane group has green. To calculate the opposing volume for a subject lane group, the entire
    opposing volume is used even if there is an overlap.
    The permitted left movement calculation does not need to be generalized to 4+ legs since only
    one opposing approach is allowed. If more than one opposing approach is coded, an error is
    written to the log file.
    Step 6j: Calculate pedestrian adjustment factors for left and right turns
    Computation of the factors for left-turning and right-turning pedestrians and bicyclists is a considerably complex operation. It is performed in four steps. For the computation, the bicycle volumes of the legs are regarded and the pedestrian volumes of the crosswalks. A traffic flow has
    potential conflicts with two crosswalks on the outbound leg. These two crosswalks head for the
    opposite directions.

    PTVGROUP

    265

    6.5.3.2 Signalized nodes


    Note: At a leg which is a channelized turn no conflicts occur between right turn movements and pedestrians.
    Step 1: Determination of the pedestrian occupancy rate OCCpedg.
    The pedestrian occupancy rate OCCpedg is derived from the volume. The following applies:

    Here, vpedg is the pedestrian flow rate, v1pedg and v2pedg are the pedestrian volumes of the
    crosswalks, C is the cycle time of the signal control and g1p and g2p indicate the duration of
    the green for the pedestrians.
    Note: In the HCM2000 it is implicitly assumed, that the green for the left turn movements and the green for the pedestrians start at the same time. In Visum, this is not the
    case, however. Thus, the following distinction of cases applies in Visum: If the pedestrian green time overlaps (or touches) the green or amber stage for vehicles, an existing conflict is assumed. In this case, the duration of the green of the pedestrian signal
    group is fully charged. Otherwise it is assumed, that there is no conflict. In this case, gp
    = 0 is assumed.
    Step 2: Determination of the relevant occupancy rate of the conflict area OCCr
    Here, three cases are distinguished:
    Case 1: Right turn movements without bicycle conflicts or left turn movements from
    one-way roads
    In this case, the following applies:
    OCCr = OCCpedg
    Decisive for left turns from one-way roads is, that there is no opposite vehicle flow.
    Case 2: Right turn movements with bicycle conflicts
    Here, straight turns of bicyclists are assumed.

    OCCbicg = 0.02 + vbicg / 2700


    OCCr = OCCpedg + OCCbicg - (OCCpedg)(OCCbicg)
    Here, vbicg is the bicycle flow rate, vbic is the bicycle volume, C is the cycle time of the signal
    control, g is the effective green time of the lane group, and OCCbicg is the conflict area's
    occupancy rate caused by bicyclists.
    Case 3: Other left turn movements
    These are left turn movements which do not originate from a one-way road. Here, a distinction of cases is made for the values gq and gp. gq is the clearing time of the vehicle flow
    266

    PTVGROUP

    6.5.3.2 Signalized nodes


    on the opposite leg, and gp is the green time for the conflicting pedestrians. The following
    applies:
    gp = max(g1p, g2p)
    Case 3a: gq gp
    In this case, the calculation is shortened and the following applies
    fLpb = 1.0
    Pedestrians and bicyclists are irrelevant here, since the left turn movements have to wait
    until the vehicle flow on the opposite leg is cleared.
    Case 3b: gq < gp
    The following applies:

    Here, OCCpedu is the occupancy rate of pedestrians after the clearance of the vehicle flow
    on the opposite leg, and OCCpedg is the pedestrians occupancy rate.
    Step 3 : Determination of the adjustment factors for pedestrians and bicyclists on permitted
    turns ApbT
    Here, two cases are distinguished with regard to the values Nturn which is the number of
    lanes per turn and Nrec, which is the number of lanes per destination leg.
    Case 1: Nrec = Nturn
    Here applies ApbT = 1 - OCCr
    Case 2: Nrec > Nturn
    Here, vehicles have the chance to give way to pedestrians and bicyclists. The following applies:
    ApbT = 1 - 0.6 OCCr
    Step 4 : Determination of the adjustment factors for the saturation flow rates for pedestrians
    and bicyclists fLpb und fRpb.
    fLpb is the adjustment factor for left turns, and fRpb is the adjustment factor for right turns. The
    following applies:
    fRpb = 1 - PRT (1 - ApbT) (1 - PRTA)
    fLpb = 1 - PLT (1 - ApbT) (1 - PLTA)
    PRT and PLT represent the proportions of right turn and left turn movements in the lane
    group, and PRTA and PLTA code the permitted shares in the right and left turn movements
    (each referring to the total number of right turn and left turn movements of the lane group).

    PTVGROUP

    267

    6.5.3.3 Two-way stop nodes


    6.5.3.3

    Two-way stop nodes


    Notes: For the description of this control type, please refer to HCM 2000, chapter 17, in
    HCM 2010 refer to chapter 19. In most instances, the calculation complies with HCM
    2000. Especially the explicit U-turn handling has been added.
    In Visum, two-way nodes are modeled by the control types two-way stop and two-way
    yield. In the HCM, the description refers to two-way stop nodes. Basically, the computation is the same. The only difference is the calculation of wait times in step 4.
    Nodes of the signalized control type are also calculated according to the method for
    yield-controlled nodes, if no SC has been allocated or the SC has been turned off.
    The two-way stop analysis method is based on the gap acceptance theory. The basic idea is
    to calculate potential capacities for all movements, and then subtract capacity from these movements based on movement rank (priority). The calculation flow chart looks similar to illustration
    64.

    Illustration 64: Method of calculation at two-way stops


    If you use the HCM 2000 operations model for two-way stop nodes, the Visum attributes in
    table 98 will show effect. Make sure that they are set to realistic values prior to running the analysis.

    268

    PTVGROUP

    6.5.3.3 Two-way stop nodes


    Network
    objects

    Attribute

    Description / Effect

    Link

    Share of HGV

    HGV share is used in step 3 + step 1. A value which


    applies to all turns originating from this link.

    Link

    Slope

    Used in step 3

    Node

    ICA peak hour factor volume adjustment

    Factor for the initial volume adjustment to peak


    volume; volumes are divided by both node and turn
    adjustment factors

    Geometry

    All

    Geometry data of lanes, lane turns and crosswalks

    Turn

    ICA peak hour factor volume adjustment

    Factor for the initial volume adjustment to peak


    volume; volumes are divided by both node and turn
    adjustment factors

    Turn

    ICA Preset critical


    gap

    Critical gap value of your choice

    Turn

    ICA Use preset critical gap

    Optionally, you can overwrite the critical gap used in


    step 3.
    Activate this option, to use the critical gap set.

    Turn

    ICA Preset followup time

    Follow-up time value of your choice

    Turn

    ICA Use preset follow-up time

    Optionally, you can overwrite the follow-up time


    used in step step 1
    Activate this option, to use the follow-up time set.

    Turns

    Preset critical gap


    stage 1

    This attribute takes effect on subordinate traffic flows


    together with the attributes Use two stage gap
    acceptance (leg) and Use preset critical gap (turns).
    The value entered replaces the critical gap default
    value in Phase 1 of the HCM, when the so-called "2stage gap acceptance" method is applied.

    Turns

    Preset critical gap


    stage 2

    This attribute takes effect on subordinate traffic flows


    together with the attributes Use two stage gap
    acceptance (leg) and Use preset critical gap (turns).
    The value entered replaces the critical gap default
    value in Phase 2 of the HCM, when the so-called "2stage gap acceptance" method is applied.

    Leg

    Is Channelized

    There is a separate right turn

    Leg

    Channelized Control

    This attribute takes effect in conjunction with the attribute Is Channelized in step 2 and in accordance
    with the regulations specified in the HCM.

    Leg

    Compute flared
    lane effects

    This attribute takes effect in conjunction with the attribute Flared storage size and according to the HCM
    formulas for shared lane capacity calculation.

    PTVGROUP

    269

    6.5.3.3 Two-way stop nodes


    Network
    objects

    Attribute

    Description / Effect

    Leg

    Flared storage size According to the HCM formulas, the flared storage
    size in number of vehicles takes effect during shared lane capacity calculation.

    Leg

    Use two stage gap


    acceptance

    This attribute takes effect in conjunction with the attribute Number of storage spaces in median refuge
    area, when the so-called "2-stage gap acceptance"
    method is applied according to the formulas of the
    HCM.

    Leg

    Number of storage
    spaces in median
    refuge area

    This attribute defines the number of spaces in the


    median refuge area and takes effect when the socalled "2-stage gap acceptance" method is applied
    according to the HCM formulas.

    Lanes

    ICA Preset critical


    gap

    Critical gap value of your choice

    Lanes

    ICA Use preset critical gap

    Optionally, you can overwrite the critical gap used in


    step step 3. The analogous value of the turn is not
    used.
    Activate this option, to use the critical gap set.

    Lanes

    ICA Preset followup time

    Follow-up time value of your choice

    Lanes

    ICA Use preset follow-up time

    Optionally, you can overwrite the follow-up time


    used in step step 1. The analogous value of the turn
    is not used.
    Activate this option, to use the follow-up time set.

    Table 98: Input attributes for the calculation of two-way stops


    Output is available through the same attributes as for signalized nodes (table 97). Additionally,
    the calculated critical gap and follow-up time data is provided.
    The method works with movements (Left, Through and Right) at each approach. Each movement is ranked according to table 99.
    Rank

    270

    Major Through
    Major Right
    Pedestrian passage minor flow

    Major Left
    Minor Right
    Pedestrian passage major flow
    Major Left priority to gaps in the opposing flow
    Minor Right priority to gaps in the flow of the right-most lane of the major flow

    PTVGROUP

    6.5.3.3 Two-way stop nodes


    Rank
    Pedestrians Priority to any other flow
    3

    Minor Through

    Minor Left

    Table 99: Ranking of movements


    Note: HCM 2010 also regards U-turns on major flows. They are given rank 2. If the calculation is based on HCM 2010, the U-turn related setting in the procedure parameters
    will not affect these U-turns.
    Step 1: Flow rate (volumes) calculation for each movement
    The 15 min peak flow rates (as calculated from the PHF adjustment) are used as the adjusted
    movement volumes.
    Step 2: Conflicting flows for each movement
    In addition to calculating the volumes for each movement, the conflicting volumes for each
    movement for each approach must be calculated.
    Notes: Rank 1 movements do not have conflicting flows since they have the highest priority. Mainly, rank1 movements are excluded from the analysis, with the exception of one
    additional evaluation (see "Calculation of the critical vol/cap ratio for the entire intersection" on page 255).
    According to HCM 2010, pocket lanes for left turns (rights for left-hand traffic accordingly)
    in the major flow are dealt with separately.
    Only nodes with three or four legs are described in the HCM. In Visum, also multi-leg
    nodes can be calculated. The 'Uncontrolled' rule is applied to conflicting flows between
    minor legs which are not separated by a major leg.
    For left-hand traffic, the right-hand calculation is performed symmetrically.
    For right-hand traffic, the following example models the conflict flow of a left turn on a major
    flow:
    Volume through traffic in opposing direction + volume right turns in opposing direction
    (does not apply, if right turns in opposing direction are separated by a channelized turn
    and need to attend a yield sign or a stop sign) + pedestrian volumes minor flow crossing
    table 100 shows the equations for conflicting volumes.
    Movement

    Conflicting flows

    Major Left

    OT + OR* + ToP

    Minor Right

    JT/N + 0.5JR* + FrP + ToP

    Minor Through
    2JL + JT + 0.5JR* + FrP + ToP + 2JLF + JTF + JRF*
    Table 100: Calculation of conflicting volumes

    PTVGROUP

    271

    6.5.3.3 Two-way stop nodes


    where
    O

    Opposite direction

    Through

    Right

    Left

    Number of through lanes

    Major

    Minor

    Far (for minor through/left turns the second major flow encountered)

    ToP

    Approach (to) with pedestrian crosswalk

    FrP

    Exit (from) with pedestrian crosswalk

    There is a number of cases where the conflicting volume is adjusted:


    If the major flow (right) is separated by a channelized turn and needs to attend a yield sign
    or a stop sign then this flow will not be considered in the conflicting volume calculation for
    other flows..
    If the major flow has more than one lane, only the right lane volume of the major flow (=
    vol / num through lanes) applies as conflicting, for minor right and minor left turns.
    If the major flow has a right turn lane, then the right turns of the major flow do not count for
    the conflicting volume.
    For left turns from the minor flow, the right turn volume of the opposing direction does not
    count for the conflicting flow, if the destination link of the two turns has more than one
    lane.
    Notes: Apart from the U-turns, the HCM 2010 differs from HCM 2000 in subtle differences. For the determination of conflicting flows, please refer to HCM 2010, pages 199 to 19-14.
    The HCM does not regard bending two-way stop/yield cases. In this case, conflicting
    flows are determined according to Brilon and Weinert, 2002.
    Step 3: Critical gap calculation for each movement
    The critical gap is the time an average driver would accept in order to merge with traffic.
    Example
    Sarah needs 4 seconds of space between vehicles to make her left turn and merge with other
    traffic safely.
    The critical gap equation is:
    tcx = tcb + (tcHVPHV) + (tcGG) - tcT - t3LT
    where

    272

    PTVGROUP

    6.5.3.3 Two-way stop nodes


    tcx

    critical gap for movement x

    tcb

    base critical gap (see table 101)

    tcHVPHV

    adjustment factor for heavy vehicles percent heavy vehicles

    tcGG

    adjustment factor for grade grade (as a decimal)

    tcT

    two stage adjustment factor (currently set to 0 for one stage modeling)

    t3LT

    Critical gap adjustment factor for geometry

    The other adjustment factors are:

    The base values for the critical gap are calculated as shown in table 101.
    Movement

    Base critical gap value tcb


    < 4 lanes major flow

    4 + lanes major flow

    Major Left

    4.1

    4.1

    Minor Right

    6.2

    6.9

    Minor Through

    6.5

    6.5

    Minor Left
    7.1
    Table 101: Base values for the critical gap

    7.5

    If the calculated values differ from the observed values, manually set values per turn can be
    used.
    Step 1: Follow-up time calculation for each movement
    The follow-up time is the extra time needed for a second car to also take the gap.
    Example
    Suppose Frank was waiting behind Sarah in the intersection. If he turns just after Sarah, he
    would need a follow-up time of 2 seconds, rather than another 4 seconds to be able to merge
    safely with other traffic. So, if the gap between vehicles was at least 6 seconds, both Sarah
    and Frank could safely make their turns.
    The follow-up time equation is:

    PTVGROUP

    273

    6.5.3.3 Two-way stop nodes


    where
    tfx

    follow-up time for movement x

    tfb

    base follow-up time (table 102)

    tfHVPHV

    follow-up time adjustment factor for heavy vehicles percent heavy


    vehicles

    The other adjustment factors are:

    Follow-up times are calculated according tor table 102.


    Movement

    Base follow-up time value tfb

    Major Left

    2.2

    Minor Right

    3.3

    Minor Through

    4.0

    Minor Left
    Table 102: Follow-up times

    3.5

    If the calculated values differ from the observed values, manually set values per turn can be
    used.
    Step 1: Calculate the potential (or ideal) capacity for each movement
    The potential capacity is the capacity which is achieved if this movement uses all potential
    gaps (i.e. no higher ranking movements take up the gaps). Furthermore, it is assumed that
    each movement is made from an exclusive lane. The potential capacity is defined as follows:

    with
    cpx

    potential capacity for movement x (veh/hr)

    vcx

    conflicting flow for movement x (conflict/hr)

    tcx

    critical gap for movement x

    tfx

    follow-up time for movement x

    Step 2: Calculate movement capacity taking into account impedance effects


    Higher ranking movements impede lower ranking movements capacities since vehicles
    making higher ranked turns can use the available gap space before the lower ranked

    274

    PTVGROUP

    6.5.3.3 Two-way stop nodes


    movements. Therefore, we adjust the potential capacity by an adjustment factor to yield the
    movement capacity. The movement capacity equation is as follows:

    where
    cmx

    movement capacity for movement x (veh/hr)

    cpx

    potential capacity for movement x (veh/hr)

    = probability impeding vehicle movement i is not blocking subject movement

    = probability impeding ped movement j is not blocking subject movement


    vi

    volume movement i

    vj

    volume pedestrian flow j (peds/hr)

    lane width (ft), standard value 12 ft.

    SP

    pedestrian walking speed (ft/s), standard value is 4 ft/s

    Since the calculation depends on higher rank movement capacities the calculation proceeds
    from the top down (from rank 1 to rank 4 movements). Impeding vehicle and pedestrian movements for each subject movement are listed in table 103 aufgelistet.
    Movement

    Rank

    Impeding movements

    Major Through

    None

    Major Right

    None

    Major Left

    ToP

    Minor Right

    FrP, ToP

    Minor Through

    JL, JLF, FrP, ToP

    JL, JLF, OT, OR, FrP, ToP

    Minor Left
    Table 103: Impeding movements
    where
    J

    Major

    Minor

    PTVGROUP

    275

    6.5.3.3 Two-way stop nodes


    O

    Opposite direction

    Through

    Right

    Left

    Far (for minor through/left turns the second major flow encountered)

    ToP

    Approach (to) with pedestrian crosswalk

    FrP

    Exit (from) with pedestrian crosswalk

    Step 2a: Calculate adjustment for impeding major left turns


    There is also an adjustment factor for major left if it does not operate from an exclusive lane.
    The equation uses a default saturation flow rate. It is as follows:

    where
    pvJL

    modified probability of impeding maJor left

    pvJL

    unmodified probability of impeding maJor left

    vJT

    volume major through

    vJR

    volume major right (0 if exclusive right turn lane)

    sJT

    sat flow major through (1700 standard)

    sJR

    sat flow major right (1700 standard)

    Note: Please refer to HCM 2010 page 19-20, for the description of a short pocket lane on
    the major flow scenario.
    Step 2a: Calculate adjustment for minor left turns
    In addition, there is a special adjustment for minor lefts (rank 4). The equation is below. Basically the major lefts and the minor through is precalculated and then adjusted. The adjusted
    value is then used in conjunction with the remaining minor right and pedestrian probabilities.

    276

    PTVGROUP

    6.5.3.3 Two-way stop nodes


    where
    pvJL

    probability of impeding maJor left near

    pvJLF

    probability of impeding maJor left far

    pvIT

    probability of impeding minor through

    pvR4

    probability minor left (rank 4)

    pvIR

    probability minor right (rank 2)

    ppIP

    probability minor pedestrian

    ppJP

    probability major pedestrian

    Step 3: Capacities for movements that share lanes


    The calculations so far assume that each minor movement operates out of an exclusive lane.
    When there is a shared lane, a combined capacity is calculated for those movements which
    share a lane.

    where
    CSH

    shared lane capacity

    vi

    volume minor street movement i

    cm

    movement capacity minor street movement i

    Note: Note that the upstream signal and platoon flow adjustments are currently omitted
    from the calculation. The same applies for the two-stage gap acceptable adjustment, as
    well as for the flared approach adjustment.
    Step 4: Calculate wait time
    The calculation of control delay is defined as follows:

    where

    PTVGROUP

    277

    6.5.3.3 Two-way stop nodes


    dx

    mean delay per vehicle for movement x

    cmx

    capacity for movement (shared lane x, CSH)

    duration of analysis period (hr) (default 0.25 for 15 min)

    vx

    movement volume (shared lane x, VSH)

    A similar formula is used for the calculation of either two-way control type (yield or stop):

    Control delay per movement is aggregated to approach with a weighted (by volume) mean of
    all approach movements/shared lanes. Mean approach delay is then aggregated to the entire
    intersection with a weighted mean as well. The equations are the same as the ones for signalized intersections.
    Note that rank 1 movements get no delay. If, however, there is no exclusive left turn pocket,
    then rank 1 movements may experience delay. There is therefore, an additional delay equation for rank 1 movements when there are no left turns pockets on the major approaches. The
    equation is as follows:

    [5]

    where
    dR1

    delay rank 1 vehicles (s/veh)

    number of through lanes per direction of the major flow

    pvJL

    probability for an adjustment factor impeding major left [5]

    dJL

    delay to major left (s/veh)

    vT

    shared through lane volume (for multilane sites, only the volume in the shared
    lane)

    vR

    shared right turn lane volume (for multilane sites, only the volume in the shared
    lane)

    This delay is then substituted by the zero delay of rank 1 movements when calculating
    approach and/or intersection delay.
    Step 5: Level of service
    Level of Service is then simply defined as displayed in table 104 based on intersection delay.
    278

    PTVGROUP

    6.5.3.4 All-way stop

    LOS

    Mean delay/vehicle

    0 10 sec.

    10 15 sec.

    15 25 sec.

    25 35 sec.

    35 50 sec.

    50 + sec.

    Table 104: Allocation of a LOS to the mean delay per vehicle


    Note: For LOS analyses, HCM 2010 additionally takes into consideration whether the
    capacity was exceeded. If this is the case, always level F of service will be allocated
    (HCM 2010, page 19-2).
    The intersection queue length calculation is:

    where

    6.5.3.4

    Q95x

    queue length 95th percentile for movement x (veh)

    cmx

    capacity for movement (shared lane x, CSH)

    duration of analysis period (hr) (default 0.25 for 15 min)

    vx

    movement volume (shared lane x, VSH)

    All-way stop
    Note: For the description of this control type, please refer to HCM 2000, chapter 17, in
    HCM 2010 refer to chapter 20. The calculations described in HCM 2010 and HCM 2000
    are identical.. HCM 2010 additionally includes the guidelines for queue length calculations (HCM 2010, page 20-17), which is missing in HCM 2000. Furthermore, the volume/capacity ratio is regarded for the LOS calculation. In case of overload, automatically
    level F is assigned.
    The HCM 2000 All-Way stop controlled (AWSC) capacity analysis method is an iterative
    method. The model looks at all possible scenarios of a vehicle either being at an approach or
    not being at an approach. Based on the input volumes the probability of each scenario occurring is calculated as well as the mean delay. The v/c ratio is calculated for each scenario which
    in turn impacts the others. Therefore, an iterative solution is needed to find the capacity of
    each approach.

    PTVGROUP

    279

    6.5.3.4 All-way stop


    Unlike the signalized method, which works with signal groups, or the TWSC method, which
    works with movements, the AWSC model works with lanes by approach.
    The basic calculation is described in the flow chart in illustration 65 . The user inputs intersection geometry and volumes, along with a couple of additional attributes such as PHF and
    %HGV. The volumes are adjusted and allocated to the lanes. The next step is to calculate the
    saturation (capacity) follow-up time adjustment factors. Then the departure follow-up times (i.e.
    the mean time between departures for a lane at an approach) are calculated based on all the
    combinations of the probability states. This departure follow-up time for each lane for each
    approach is dependent on the other approaches and so it is calculated in an iterative manner.
    Once a converged value is found, then the service time, mean delay and LOS can be calculated.

    Illustration 65: Calculation process for an all-way stop node


    If you use the HCM operations model for all-way stop nodes, the following Visum attributes, listed in table 105 , will show an effect. Make sure that they are set to realistic values prior to running the analysis.

    280

    PTVGROUP

    6.5.3.4 All-way stop


    Network Attribute
    object

    Description / Effect

    Link

    ShareHGV

    Proportion of heavy goods vehicles, used in follow-up times


    adjustment. A value which applies to all turns originating from
    this link.

    Node

    ICAPHFVolAd- Initial volume adjustment to peak period. Then, volumes are


    j
    divided by both node and turn adjustment factors.

    Geometry

    All

    Turn

    ICAPHFVolAd- Initial volume adjustment to peak period. Then, volumes are


    j
    divided by both node and turn adjustment factors.

    Turn

    ICA average Average queue length


    back of queue

    Geometry information on lanes, lane turns and crosswalks

    Table 105: Input attributes for an all-way stop node


    Output is available through the same attributes as for signalized nodes (table 96).
    The first step is to PHF adjust the volumes by lane by movement by approach. In addition the
    % heavy goods vehicles by lane by movement by approach are also input if available. Since
    in Visum volumes are specified by movement and not by lane by movement, they are first disaggregated per lane according to a standard method.
    The next step is to calculate the follow-up time adjustment factors for each lane. The calculation applies as follows:
    hadj = hLTadj pLT + hRTadj pRT + hHVadj pHV
    where
    hadj

    follow-up time adjustment

    hLTadj

    follow-up time adjustment for left turns

    hRTadj

    follow-up time adjustment for right turns

    hHVadj

    follow-up time adjustment for heavy vehicles

    PLT

    proportion of left-turning vehicles on approach

    pRT

    proportion of right-turning vehicles on approach

    pHV

    proportion of heavy vehicles on approach

    The adjustment factors are listed in table 106.

    PTVGROUP

    281

    6.5.3.4 All-way stop


    Number of lanes of the subject
    approach
    1
    2
    Table 106: Adjustment factors

    Adjustment factor

    Saturation

    Mean follow-up
    time

    LT

    RT

    HV

    0.2

    -0.6

    1.71.7

    0.5

    -0.7

    1.71.7

    After calculating the follow-up time adjustment factor the departure follow-up time is calculated
    in an iterative manner. It involves five steps.
    Step 1: Calculate combined probability states probability

    where
    P(i)

    probability for combination i

    P(aj)

    probability of degree-of-conflict (DOC) for combination i lane type j

    aj

    1 or 0, depending on lane type j (siehe table 107)

    This probability states calculation has a few parts. For each lane type j the P(aj) is calculated. P
    (aj) is calculated based on a lookup table (table 107).
    aj

    Vj (volume conflicting approach)

    P( aj)

    >0

    Xj

    0
    >0
    Table 107: Calculation of probability of degree of conflict

    1 - Xj

    Notes:
    If iteration is 1, then Xj = (Vj hd) / 3,600
    If iteration is > 1, then Xj = min(1,(Vj hd) / 3,600)
    Initial value hd = 3.2 s
    Value aj is adopted from the DOC table (table 108). This table contains all the combinations of
    0 and 1 per lane for each approach. For two lanes per approach, this looks as depicted in
    table 108 (see exhibit 17-30 in the HCM 2000 for the full table).

    282

    PTVGROUP

    6.5.3.4 All-way stop


    Opposing
    approach

    Left
    (approach examined)

    Right
    (approach examined)

    L1

    L2

    L1

    L2

    L1

    L2

    DOC case (Ck) Number of


    vehicles

    3
    4

    64 There are 64 combinations for 4 legs each with 2 lanes.


    Table 108: Excerpt of DOC table for two lanes per approach
    The combined probability states probability P(i) is then calculated for each row (i) for each
    column (lane type) (j). To calculate P(i), we use the product of all probabilities of each opposing lane and each conflicting lane P(aj) . The result P(i) = P(aj) is the probability state for row
    (i).
    Step 2: Calculate probability state adjustment factors
    After calculating P(i) for each case (i), an adjustment for each DOC case needs to be calculated. The adjustment accounts for serial correlation in the previous calculation due to related conflict cases. For DOC case (Ck), the adjustment equations are:

    where

    PTVGROUP

    283

    6.5.3.4 All-way stop


    a

    0.01 (or 0.00 if no serial correlation)

    number of non-zero cases (i) for each DOC case (at most n = 1 for C1, 3 for C2, 6 for
    C3, 27 for C4 and C5)

    Step 3: Calculate adjusted probability


    P(i) = P(i) + adjP(i)
    where
    P(i)

    adjusted probability for case i

    P(i)

    probability of degree-of-conflicts for case i

    adjP(i)

    probability adjustment factor case i

    Step 4: Calculate saturation follow-up time


    hsi = hadj + hbase
    where
    hsi

    saturation follow-up time by DOC case i

    hadj

    follow-up time adjustment by lane

    hbase

    base follow-up time by DOC case i

    For each DOC case i, the base follow-up time h base is adopted from a lookup table which is
    based on the particular DOC case (1 5) and geometry group (table 109).

    Number of lanes
    Subject
    approach

    Opposing
    approach

    Unpermitted
    approach

    Intersection type

    Geometry group

    4 leg or T

    4 leg or T

    4 leg or T

    3a / 4a

    3b

    4 leg

    4b

    1-2

    1-2

    4 leg or T

    1*

    1*

    4 leg or T

    4 leg or T

    3
    3
    3
    Table 109: Lookup table base follow-up time

    Note: * If the approach examined has 3 lanes and the opposing or conflicting approach
    has 1 lane, then geometry group 5 applies, else geometry group 6.

    284

    PTVGROUP

    6.5.3.4 All-way stop


    The model is generalized for 3+ lanes in order to apply it to 4+ leg intersections. The extension
    is that these 4+ leg cases are geometry group 6.
    table 110 shows the saturation follow-up time base values.

    DOC case

    Geometry
    group

    Number of
    0
    vehicles (Sum
    of the [0,1] for
    the case)

    1
    2
    >=3

    1
    2
    >=3

    2
    3
    4
    >=5

    3
    4
    5
    >=6

    3.9

    4.7

    5.8

    7.0

    9.6

    3.9

    4.7

    5.8

    7.0

    9.6

    3a

    4.0

    4.8

    5.9

    7.1

    9.7

    3b

    4.3

    5.1

    6.2

    7.4

    10.0

    4a

    4.0

    4.8

    5.9

    7.1

    9.7

    4b

    4.5

    5.3

    6.4

    7.6

    10.2

    4.5

    5.0

    6.4

    7.6

    9.7

    6.2

    7.2

    7.8
    9.0

    9.7
    10.0
    11.5

    6.0
    6.8
    7.4

    6.6
    7.3
    7.8

    8.1
    8.7
    9.6
    12.3

    10.0
    11.1
    11.4
    13.3

    4.5

    Table 110: Base values for the saturation follow-up time


    The DOC case is dependent on the 64 types of a 4 leg intersection. Nodes with more than 4
    legs are first collapsed to four legs.
    Step 5: Calculate departure follow-up time

    where
    hd

    departure follow-up time for lane

    hsi

    saturation follow-up time for each i in I

    P(i)

    adjusted probability for each i in I

    Row of table 1

    PTVGROUP

    285

    6.5.3.4 All-way stop


    These five steps are repeated until the departure follow-up time values converge (change is <
    0.1). Now, the calculated departure follow-up time h d differs from the original value. Thus, the
    next iteration will return a different result.
    Now that the departure follow-up time for each lane is calculated, service time and capacity
    can be calculated. The service time is calculated as follows:
    t = hd - m
    where
    t

    Service time

    hd

    Departure follow-up time

    move up time (2.0 s for geometry groups 1-4 and 2.3 s for groups 5-6)

    The capacity is calculated as follows: the volume of the subject lane is incremented until its
    degree of utilization (vjhd)/ 3,600 is 1.0. The volume of the other approaches is held constant.
    At this point, the subject lanes volume value is taken to be the subject lanes capacity. Capacity is therefore dependent on the input volumes for each approach.
    The search for capacity is slow in a linear implementation. Thus a binary search is performed
    with an upper bound of 1,800 vphpl.
    Mean delay per lane is calculated from the equation below. The weighted mean delay for an
    approach is calculated based on lane volume weights. Intersection average delay is calculated based on the weighted mean by approach volumes. The equations are the same as
    the ones for signalized intersections.

    where
    dx

    Mean delay per vehicle for lane x

    Service time

    Duration of analysis time slot (hr) (default 0.25 for 15 min)

    x
    Utility rate
    hd

    Departure follow-up time

    Level of Service is defined as a lookup, based on intersection delay (table 111).

    286

    PTVGROUP

    6.5.3.5 Roundabouts according to the HCM 2010 method


    LOS

    Mean delay/vehicle

    0 10 s

    10 15 s

    15 25 s

    25 35 s

    35 50 s

    F
    50 + s
    Table 111: Determining the LOS based on mean wait time per vehicle
    The proposed extension to 4+ legs is to combine multiple lefts or rights into one left or right by
    adding the number of lanes when calculating conflicting flows. For example, when there are
    two conflicting lefts for an examined approach, one with one lane and one with two lanes,
    these are merged into one conflicting left with three lanes. This allows the existing framework
    to be used. It probably slightly understates the delay, but it will work within the existing framework and will result in additional delay for additional legs.
    6.5.3.5

    Roundabouts according to the HCM 2010 method


    For this analysis method, please refer to HCM 2010, chapters 21 and 33. It is similar to the one
    for two-way stop nodes and mainly differs from it in the following points:
    Determining the conflict flows follows the geometry of the roundabout.
    The standard values for gaps differ due to changed visibility conditions. Also this calculation is performed on the basis of lanes, not on the basis of turns.
    This method is available for one- and two-lane approaches (plus one optional bypass
    lane). The Visum method used for three- or multiple-lane approaches is not described in
    the HCM. Visum distributes the volume across the lanes as for two-way stop nodes.
    The calculation process is illustrated in illustration 66.

    PTVGROUP

    287

    6.5.3.5 Roundabouts according to the HCM 2010 method

    Illustration 66: Calculation process for roundabouts according to HCM 2010


    If you use the HCM 2010 operations model for roundabout nodes, the Visum attributes listed in
    table 112 will show efect. Make sure that they are set to realistic values prior to running the
    analysis.

    288

    Network
    objects

    Attribute

    Description / Effect

    Geometry

    All

    Geometry data of lanes, lane turns and crosswalks

    Node

    ICAPHFVolAdj

    Turn

    ICAPHFVolAdj

    Factor for adjustment of initial volumes to peak volumes. Then, volumes are divided by both node and
    turn adjustment factors.

    Leg

    Center island
    length

    Leg

    Center island width Width of center island

    Leg

    Channelized turn
    length

    Length of channelized turn

    Leg

    Has splitter Island

    Indicates whether a leg has a splitter island (yes/no)

    Leg

    Length of splitter
    island

    Length of the splitter island


    Note
    Value entered is used if the Has splitter island attribute is activated.

    Leg

    Splitter island width Wdith of splitter island


    Note
    Value entered is used if the Has splitter island attri-

    Length of center island

    PTVGROUP

    6.5.3.5 Roundabouts according to the HCM 2010 method


    Network
    objects

    Attribute

    Description / Effect

    Leg

    Has bypass lane

    Indicates whether the leg has a bypass lane


    (yes/no)

    Leg

    Share of bypass
    volume

    Proportion of right turns (left-hand traffic: left turns),


    which use a bypass lane for the turn movement.
    Note
    This information is used, if the Has bypass lane attribute is activated.

    Lanes

    ICA Preset critical


    gap

    Critical gap value of your choice

    Lanes

    ICA Use preset critical gap

    Optionally, you can overwrite the critical gap, used


    in step step 5. The analogous value of the turn is not
    used.
    Activate this option, to use the critical gap set.

    Lanes

    ICA Preset followup time

    Follow-up time value of your choice

    Lanes

    ICA Use preset follow-up time

    Optionally, you can overwrite the follow-up time


    used in step step 6. The analogous value of the turn
    is not used.
    Activate this option, to use the follow-up time set.

    bute is activated.

    Table 112: Input attributes for roundabout nodes according to HCM 2010
    Output is available through the same attributes as for signalized nodes (table 97).
    The calculation method according to HCM 2010 consists of twelve consecutive steps. Here,
    the description is reduced to the most important steps.
    Step 1: Calculate flow rates (volumes) for each turn
    The turn volumes are converted by multiplying them with the peak hour factors of the turns and
    the node in values for the 15 minute peak.
    Step 2: Calculating traffic flows for each lane and conflicting volumes for each approach
    All calculations are based on the traffic flows and conflicting volumes at each approach. These
    flows are derived from the turn volumes (in illustration 67 ) for a roundabout with four approaches (v1 to v12).

    PTVGROUP

    289

    6.5.3.5 Roundabouts according to the HCM 2010 method

    Illustration 67: Approaching flows at a four-leg roundabout


    For the distribution of the volumes to the lanes please refer to HCM 2010, pages 21-14 and
    21-15.
    Example
    The flow from the south is the sum of turn volumes v7 + v8 + v9. The conflicting flow which applies to this flow is however the sum v1 + v2 + v10. This approach can be applied to roundabouts
    with a countless number of approaches. U-turns can also be considered in the same way, if
    you want to integrate them in the ICA calculation.
    If an approach has more than one lane, the total inflow is distributed on lanes.
    1. If only one lane is permitted for left turns, its volume is the sum of all volumes of left turns.
    2. If only one lane is permitted for right turns, its volume is the sum of all volumes of right turns.
    3. The remaining volume is distributed to all lanes in such way, that they all have the same
    volume if possible.
    Step 4: Capacity
    The capacity of each lane is assigned to all turns, for which lane turns are defined starting from
    the lane. The result is saved in PCU/h in the turn attribute ICA final capacity.
    For each of the cases, predefined formulas can be used (HCM 2010, equations 21-1 to 21-7).
    This is the basic formula:

    290

    PTVGROUP

    6.5.3.5 Roundabouts according to the HCM 2010 method

    Here B equals 0.001 for one-lane and two-lane entry roads to single-lane roundabouts. For single-lane approaches to two-lane roundabouts B equals 0.0007. Two-lane approaches to twolane roundabouts use the following values for B: 0.00075 for the inner-most (let) lane, and
    0.0007 for the right lane. For bypass lanes, with one conflicting exit lane, B is assumed to be
    0.001. 0.0007 is used if there are two conflicting exit lanes.
    Users with detailed knowledge of critical gaps and follow-up times can replace these formulas.
    For the control type 'roundabout', critical gap and follow-up time are set by lane. Turn-related
    values of this attribute are not regarded. For the extended computation, the capacity is derived
    from the following data (HCM 2010, page 33-3):

    where
    c

    capacity in PCU/h

    conflicting flow in PCU/h

    gapc

    critical gap in s

    gapf

    follow-up time in s

    Visum uses the following standard values: 4s for the critical gap and 3s for the follow-up time.
    You can optionally overwrite both values by lane.
    Pedestrians have a bearing on the capacity. For a detailed description, please refer to HCM
    2010, pages 21-16 and 21-17.
    To the turns, the approach capacity is distributed in proportion to the volume. The result is stored in the turn attribute ICA final capacity.
    Step 5: Delays
    The mean wait time on a lane of an approach arises from the following values:

    PTVGROUP

    291

    6.5.3.5 Roundabouts according to the HCM 2010 method


    d

    mean delay in s/PCU

    lane capacity in PCU/h

    lane volume in PCU/h

    observation period in h

    The mean delay of a turn is the volume weighted mean of the mean delay of lanes used. The
    result is saved in the turn attribute tCur.
    Note: For turns with lane turns without allocated signal group, tCur is set to zero.
    Step 6: Queue lengths
    The mean queue length on a lane of an approach arises from the following values:

    where
    Q95

    95% percentile of queue length in PCU

    lane capacity in PCU/h

    lane volume in PCU/h

    observation period in h

    The attribute ICABackOfQueueForDefPerc is the maximum of the Q95 percentiles for the
    lanes used.
    Step 7: Level of Service (LOS)
    LOS per lane of an approach is defined as a classification of the mean delay (table 113).
    LOS

    Mean Delay [s / PCU]

    0 - 10

    >10 - 15

    >15 - 25

    >25 - 35

    >35 - 50

    >50

    Table 113: LOS per lane based on the mean delay


    The HCM does not determine the calculation of the LOS per approach, turn or node. In these
    cases Visum calculates the LOS on the basis of the volume weighted mean delay. If the
    volume exceeds the capacity, the LOS is automatically set to F.

    292

    PTVGROUP

    6.5.3.6 Roundabouts according to the TRL/Kimber method


    6.5.3.6

    Roundabouts according to the TRL/Kimber method


    This analysis method regards approach capacity as a function of geometry and the conflicting
    volume in roundabouts. On the basis of numerous observations, this function was calibrated to
    British roundabouts.
    illustration 68 shows the calculation process for roundabouts according to the TRL/Kimber
    method.

    Illustration 68: Calculation process for roundabouts according to the TRL/Kimber method
    In Visum, the geometry of the roundabout is described through leg attributes. These attributes
    are only important, if the node is a roundabout and if TRL/Kimber is selected as analysis
    method. In all other cases, the parameters are ignored at ICA calculation. The meaning of the
    parameter is illustrated in illustration 69 which has been taken from the DMRB guideline TD
    16/93. For a better comparison with this guideline, the common English original attributes and
    abbreviations are specified in the tabular overviews. Another parameter describes the temporal variability of the inflow.

    PTVGROUP

    293

    6.5.3.6 Roundabouts according to the TRL/Kimber method

    Illustration 69: Description of the node geometry for the TRL/Kimber model
    table 114 shows the additional input attributes at legs for calculation according to TRL/Kimber.

    294

    Name

    DMRB definition

    Value Value
    type range
    (Default
    value)

    Meaning

    ICA inscribed circle


    diameter

    ICAInscribedCircleDiameter
    (D)

    Lengt- 10 - 200 m External diameter of


    h
    (40 m)
    the roundabout. For
    asymmetric roundabouts specify the
    radius related to the
    environment of the
    respective approach.

    ICA entry width

    ICAEntryWidth (e)

    Lengt- 3 - 20 m (7 Width of the entry


    h
    m)
    directly at roundabout

    ICA approach half


    width

    ICAApproachHalfWidth
    (v)

    Lengt- 2 - 15 m
    h
    (3.5 m)

    Road width of the


    approach link without
    pocket

    ICA flare length

    ICAFlareLength (L)

    Lengt- 1 - 100 m

    Half length of the

    PTVGROUP

    6.5.3.6 Roundabouts according to the TRL/Kimber method


    Name

    DMRB definition

    Value Value
    type range
    (Default
    value)
    h

    (20 m)

    Meaning

    approach between the


    points where ICAEntryWidth and
    ICAApproachHalfWidth are measured.

    ICA entry radius

    ICAEntryRadius (r)

    Lengt- 1 - 1,000 m Circle radius which


    h
    (35 m)
    tangentially approximates to the outer
    circle of the roundabout and the outer
    boundary of the
    approach.

    ICA entry angle

    ICAEntryAngle ()

    Integer

    ICA grade separation

    ICAGradeSeparation
    (SEP)

    Lengt- 0 - 100 m
    h
    (0 m)

    ICA Kimber Hollis c- ICAKimberHollisC


    factor

    Double

    0..180
    (45)

    see illustration 69
    Distance between
    approach and exit of
    the same node leg.
    For regular roundabouts specify 0 m.
    This implies the roundabout is not gradeseparated. With
    values > 0 you describe the approaches
    of grade-separated
    expanded roundabouts, where the
    entry is far away from
    the exit of the same
    leg.

    0 .. 10 (1.0) In the queue length formula by Kimber-Hollis, the c-factor


    describes the variability of the inflow

    Table 114: Input attributes for calculation according to the TRL/Kimber method
    These attributes are only important, if the ToNode of the link has the controller type roundabout, i.e. the link represents an approach to a roundabout. In all other cases the attributes
    are ignored.
    The output attributes correspond to those for signalized intersections (table 97).
    PTVGROUP

    295

    6.5.3.6 Roundabouts according to the TRL/Kimber method


    Step 1: Traffic flows and conflicting volumes for each approach
    All calculations are based on the traffic flows and conflicting volumes at each approach. These
    traffic flows are derived from the turn volumes. All volumes are expressed in PCUs.
    Step 2: Approach capacities
    For roundabouts with RDistanceExit = 0, the following applies:

    where
    Cap

    approach capacity in PCU/h

    qc

    conflicting flow in PCU/h

    1 - 0.00347 ( - 30 ) - 0.978 [(1/r) - 0.05]

    303 x

    0.21 t (1 + 0.2 x)

    1 + 5 / (1 + M)

    e(D - 60)/10

    v + (e - v) / (1 + 2 S)

    1.6 (e - v) / L

    The remaining variable descriptions refer to the attributes of the geometry description.
    Different from the above mentioned, the following applies for roundabouts with RDistanceExit
    > 0:
    Cap =1.004F - 0.036SEP - 0.232 qc + 14.35 - f qc(2.14 - 0.023 qc)
    where all sizes as above, however Cap and qc in PCU/min.
    The capacity of each lane is distributed proportionally to the volume of the turns. The result is
    saved in PCU/h in the turn attribute ICAFinalCapacity.
    Step 3: Queue lengths
    The queue length of an approach results from the Kimber and Hollis formula (Kimber, Hollis
    1979), (Kimber, Daly 1986).

    296

    PTVGROUP

    6.5.3.6 Roundabouts according to the TRL/Kimber method


    where
    L

    expected queue length at the end of the observation period in PC units

    approach capacity in PCar units/h

    length of the observation period in h

    L0

    initial queue length (in Visum always 0)

    Variation factor KVKimberHollisC

    approach volume in PCar units/h

    = v / = Saturation

    Visum uses the formula modified in (Kimber, Hollis 79) for increased accuracy.
    The mean queue length of each turn is equal to the mean queue length of its approach and is
    saved to the turn attribute ICA mean queue length.
    Step 4: Delays
    The mean control-based wait time per approach results from the Kimber and Hollis formula
    (Kimber, Hollis 1979), (Kimber, Daly 1986).

    where
    d

    mean permitted delay in the observation period in h

    approach capacity in PCar units/h

    length of the observation period in h

    L0

    initial queue length (in Visum always 0)

    Variation factor KVKimberHollisC

    approach volume in PCar units/h

    = v / = Saturation

    The mean permitted delay of a turn is equal to the mean permitted delay of its approach and is
    saved in the turn attribute tCur.
    As in step 3 , Visum evaluates.the formula modified by Kimber and Hollis for increased accuracy.
    Step 5: Level of Service (LOS)
    PTVGROUP

    297

    6.5.4 Signal time optimization


    The concept of a LOS is not mentioned in the Kimber model. To create consistency within ICA
    and because the RFC (Ratio Flow to Capacity) skim was criticized as being insufficient, Visum
    still defines a LOS per approach as a classification of the mean delay (table 115).
    LOS

    Mean Delay [s / PCU]

    0 - 10

    >10 - 15

    >15 - 25

    >25 - 35

    >35 - 50

    F
    >50
    Table 115: LOS for calculation based on the mean delay, according to Kimber
    Visum calculates the LOS of the entire node accordingly, on the basis of the volume weighted
    mean delay of all approaches.

    6.5.4

    Signal time optimization


    Within the scope of the intersection capacity analysis using ICA, you can optimize the signal
    times for individual signal controls in two ways:
    Green time optimization (see "Green time optimization" on page 299)
    Cycle and green time optimization (see "Signal cycle and green time optimization" on
    page 302)
    In addition, using signal coordination, you can optimize the time intervals between more than
    one light signal control in the network (see "Signal coordination (Signal offset optimization)" on
    page 302).
    Note: Optimization regards only those nodes (main nodes), whose effective control type
    = signalized. Optimization does not regard those nodes (main nodes) whose SC has
    been turned off or to which no SC has been allocated.

    6.5.4.1

    Data model for SC cycle and green time optimization


    The following attributes of network objects are relevant for the cycle and green time optimization:
    Network object
    type

    298

    Attribute

    Description

    Signal control and All attributes which


    subordinate objects describe signal times

    Signal times and stage distribution in the


    initial state

    SC

    At cycle time optimization with procedure


    parameters UseCycleTimeFamily=True, only
    one member of the cycle time family of the

    Reference to signal
    coordination groups

    PTVGROUP

    6.5.4.2 Green time optimization


    Network object
    type

    Attribute

    Description

    Signal coordination Cycle time family


    group

    coordination group is selected as a new


    cycle time.

    SC

    ICA maximum cycle


    time for optimization
    ICA minimum cycle
    time for optimization

    At cycle time optimization with procedure


    parameter UseCycleTimeFamily=False the
    new cycle time is selected from the interval
    between these two attributes.

    SC

    Optimization method

    0 = no signal time optimization for the signal


    control at this node
    1 = only green time optimization
    2 = cycle and green time optimization

    SC

    Turned off

    If the SC has been turned off, no signal time


    optimization will be calculated for the node
    (main node).

    Turn

    The attribute for the


    design hourly volume
    set in the procedure
    parameters

    Turn volumes

    Node model and


    All geometry attributes Lane allocation at node
    subordinate objects
    Optimization is controlled by the following procedure parameters (components of the procedure parameters for intersection capacity analysis):

    6.5.4.2

    Procedure parameter

    Data type (Stan- Description


    dard)

    Automatic green
    time optimization

    Boole (False)

    Are the signal times always optimized within the


    ICA calculation? If yes, it depends on the SC attribute Optimization method which optimization
    method is applied to which SC.

    UseCycleTimeFamily

    Boole (True)

    At cycle time optimization with procedure parameters UseCycleTimeFamily=True, only one


    member of the cycle time family of the coordination group (if available) is selected as a new
    cycle time.

    Precision of computation

    Seconds or
    tenths of a
    second

    Via this parameter you can decide whether


    seconds or tenths of a second are permitted as
    green time start and end.

    Green time optimization


    For pure green time optimization, the cycle time specified is definite.

    PTVGROUP

    299

    6.5.4.2 Green time optimization


    Green time optimization for stage-based signal controls
    The following steps are necessary for calculating the green time split:
    1. Deconstruct approaches into lane groups (already calculated for capacity analysis).
    2. Calculate adjusted volume and saturation flow rate for each lane group (already calculated
    for capacity analysis).
    3. For each stage in the signal timing plan, determine the critical lane group.
    4. Allocate green time based on critical lane group volume/saturation flow rate ratios.
    5. Check that the allocated green times meet all the constraints.
    Green time split is calculated as follows:

    where
    Gi

    effective green time for stage i

    (v/s)ci

    ratio of volume v and saturation flow rate s for critical lane group ci in stage i

    Gte

    total effective green time for cycle

    The total effective green time for a cycle is the same as the cycle time deducting all intergreens
    between consecutive stages. The intergreen between two stages is zero, if the stages share
    signal groups. Otherwise, intergreen is given by the attribute Default intergreen of the signal
    control.
    Each stage must also maintain the minimum green time, which is given by the Minimum green
    time attribute of the signal control. If the calculated green time for a stage is less than the minimum green time, then the green time split equation is rerun with the stage below its minimum
    green time omitted. The omitted stage is assigned the minimum green time. That minimum
    green is subtracted from the total effective green time and the green time split is recalculated.
    As a result of optimization, new values are assigned to the attributes Green time start and
    Green time end of the stages.
    Green time optimization for signal group-based signal controls
    The optimization of signal group based signal controls results from the following steps of the
    procedure for stage-based signal controls:
    1. Fictitious stages are generated from the current greentimes of the signal groups.
    Visum first defines set T of all switching points from the attributes Green time start and
    Green time end of all signal groups and sorts these in ascending order. For each interval
    between consecutive times ti and ti+1 in T generate a stage which contains all signal
    groups which have been released during [ti ; ti+1).

    300

    PTVGROUP

    6.5.4.2 Green time optimization


    2. The fictitious stage-based signal control is optimized as above (see "Green time optimization for stage-based signal controls" on page 300).
    3. The signal group green times are read from the optimal stage distribution.
    Green time for each signal group results from the green time of all stages which contain the
    signal group. Because all of these are neighboring stages due to construction, there is only
    one green time for the signal group.
    Green time optimization for external signal controls and RBC
    Visum can be used to optimize Vissig signal controls. Stages have to be defined for this signal
    control. Optimization of non-stage based Vissig controls or controls of the RBC type will be
    made available later.
    To exclude selected stages from the optimization to keep their lengths as set in the original
    signal timing plan, select 'true' for the attribute Pseudo stage of these stages.
    Visum executes the following steps to calculate the green time split:
    1. With the current signal timing plan, execute an ICA calculation and determine both saturation flow rate and volume for each lane group.
    2. Solve the linear optimization problem:

    whereby
    L

    set of all lane groups

    cycle time

    sl

    saturation flow rate of lane group l

    ql

    volume of lane group l

    tP

    green time duration of stage P


    minimum greens of stage P

    The first secondary condition expresses that the share z of the volume per lane group
    depends on the green times of the stages provided for this group. The share z is maximized.
    3. With the optimized signal timing plan, execute another ICA calculation.

    PTVGROUP

    301

    6.5.4.3 Signal cycle and green time optimization


    4. If the total mean wait time has not improved, cancel the calculation and continue with step
    5. If the saturation flow rates have changed, go to 2. Otherwise also go to 5.
    5. Assign the Green time start and Green time end attributes of the stages the values of the
    latest optimum solution.
    6.5.4.3

    Signal cycle and green time optimization


    If you select signal cycle and split optimization for a node, Visum calculates an optimal cycle
    time for the signal control at the node and at the same time an optimal green time split for this
    cycle time. If several (main) nodes belong to a signal control, then automatically all (main)
    nodes of this signal control will be optimized.
    The calculation includes the following steps:
    1. Determine the set T of permitted cycle times at the SC. If the procedure parameter Use
    cycle times of coordination groups is active and if the SC belongs to a coordination
    group, then only cycle times of the coordination group's cycle time family are permitted.
    Otherwise, any cycle time (integer [in seconds]) from the interval between the SC attributes
    ICA minimum cycle time for optimization and ICA maximum cycle time for optimization
    is permitted
    2. To each permissible cycle time t from T the following applies:
    Specify optimal green times g*(t) for predefined cycle time t.
    Use ICA to calculate the total wait time at the node for g*(t).
    3. As an optimal cycle time t* select the t with minimum total wait time. In addition, set the optimal green time split g*(t*).
    The ICA calculation of the total wait time at the node only provides valid values, if the sum of
    critical v/s ratios is smaller than or equal to 1. To greater sums always t* = max(T) applies. If
    the sum of the minimum green time and intergreens for all stages or signal groups are larger
    than the calculated t*, t* is set to the smallest t of T which is larger or equal to this sum. If no
    such t exists, t* is set to the sum independently of T.

    6.5.4.4

    Signal coordination (Signal offset optimization)


    Signal cycle and split optimization always refer to individual signal controls. Signal offset optimization, however, is used to optimize the offset between the signal times of neighboring
    nodes in such a way, that vehicles can pass several consecutive signal controls on green. The
    general aim is to minimize the total wait time for all vehicles at the signal control.
    Notes: The method does not regard the attributes of the node geometry. In particular, the
    stop line position per lane is not taken into consideration.
    Signal coordination dos not include signalized nodes or main nodes to which no SC has
    been allocated or whose SC has been turned off.
    Example
    We will demonstrate the task with the help of the example network displayed in illustration 70

    302

    PTVGROUP

    6.5.4.4 Signal coordination (Signal offset optimization)

    Illustration 70: Example network for signal coordination


    In the network in illustration 70, the six inner nodes have signal controls and the outer nodes
    are only there to connect the four zones. Link and turn volumes result from an assignment.
    Lane allocation is usually selected, so that at each approach of a node, a shared lane exists
    for the straight and right turns and a 100m long pocket for left turns additionally. Additional
    lanes are only located at individual approaches with an especially large traffic volume. All SC
    have the same signal times (illustration 71).

    PTVGROUP

    303

    6.5.4.4 Signal coordination (Signal offset optimization)

    Illustration 71: Green time split at all nodes with succeeding left turns
    With a cycle time of 80s, straight and right turns each have a green time of 30s. Signal groups
    for left turns have 5s more and are protected within this time.
    Signal times and lane allocation are selected in such a way that the resulting capacity is sufficient for all turns. Wait times can occur if neighboring SCs are badly coordinated. For this
    example we first assume an offset time of 0s for all SC. The assignment result illustrated by
    link bars results as overlapping of seven paths and one of these is highlighted in illustration
    72.

    304

    PTVGROUP

    6.5.4.4 Signal coordination (Signal offset optimization)

    Illustration 72: A path through the example network passes SCs at nodes 7003, 8003, 8002
    and 9002
    This route passes the signalized nodes 7,003, 8,003, and 9,002. Vehicles exiting node 7,003
    in direction 8,003 form a group that starts at the beginning of the green time, i.e. at second 0.
    Travel time tCur, on the link between 7,003 and 8,003, is 38s. Without accounting for dispersal
    of the group, the first vehicles reach node 8,003 at second 38. The distribution of the actually
    driven speed by vehicles leads to a resolution of the original compact platoon (illustration 73).

    Illustration 73: Progression quality for approach West at node 8003

    PTVGROUP

    305

    6.5.4.4 Signal coordination (Signal offset optimization)


    On the left, the diagram shows the arrival rate by cycle second. The first vehicles arrive at
    second 30. The arrival rate then steeply increases and decreases as of second 52. The signal
    group to continue the journey also has a green time between second 0 and 30. The major part
    of the platoon therefore reaches the node at red. The second diagram shows the corresponding development of the queue length and the third diagram the resulting wait time in
    vehicle seconds dependant on the arrival second. The total wait time across all arrivals is
    19,069 vehicle seconds, which corresponds to a mean value of 39.20 s per vehicle. This is an
    example for bad coordination.
    At node 8002, the situation is much more favorable (illustration 74).

    Illustration 74: Progression quality for approach North at node 8002


    The vehicle group again starts driving at second 0. The travel time on link 8,003 - 8,002, with
    tCur =41 s, is similar to before. However, the continuing signal group 4 for left turns, at node 8,
    has a green time from second 40 to second 75. Most of the vehicle group arrives during green
    time. The queues are distinctly shorter and the total wait time is only 1,608.80 vehicle seconds
    (mean: 4.37 s per vehicle).
    In this simple example, the aim of signal coordination would be to change the offset between
    nodes 7,003 and 8,003, so that the entire vehicle group arrived at 8,003 during green time. At
    the same time, however, you would want to maintain the favorable offset between 8,003 and
    8,0002. Because a convenient coordination should be achieved not only for one but several
    paths (in the example, seven) simultaneously, signal coordination usually minimizes the total
    wait time of all SCs by changing the offset times.
    Model
    Signal coordination in Visum can be used for optimizing SCs in a network, not only along a
    linear corridor, as it corresponds with the traditional optimization of the progressive signal system. This section describes how the optimization model is set up, which Visum solves by using
    a standard procedure for mixed integer linear optimization. All attributes that describe input
    and output of the procedure are summarized in the following section (see "Input attributes with
    effect at signal coordination" on page 309).
    Good coordination requires the SCs either have the same cycle times or that the cycle times
    are at least in a simple ratio (for example 2:1). Furthermore, SCs have to be located close to
    each other, otherwise the platoon will have broken up so heavily by the time it has reached the
    next SC, that the arrivals will virtually be uniformly distributed and the wait time cannot be influenced through the choice of the offset. It is therefore generally not sensible to coordinate all

    306

    PTVGROUP

    6.5.4.4 Signal coordination (Signal offset optimization)


    SCs in one network. You determine which SCs should be coordinated by defining signal coordination groups and assigning them SCs (see User Manual: Chpt. 15.40.14 , page 1497). By
    default, SCs are not assigned to any signal coordination group and are not coordinated.
    For each signal coordination group define the set of the cycle times which are permitted for the
    corresponding SCs. Please make sure that the cycle times actually make coordination possible. Two SCs with cycle times of 60 s and 65 s can generally not be coordinated because the
    platoon in each cycle takes place at a different cycle second. Suitable cycle times therefore
    have a small LCM (least common multiple), for example, the family {60 s, 80 s, 120 s } with
    LCM = 240 s. Signal coordination optimizes offset times for each signal coordination group
    separately and takes those SCs into consideration with cycle times belonging to the permitted
    cycle times of the group. SCs with deviating cycle times are ignored and logged in the message file.
    Important for coordination is the behavior of the vehicle platoon during the journey from one
    SC to another. Visum determines platoons by analyzing the assignment results for one or
    more selected PrT demand segments. From the saved paths of the assignment, Visum determines how many vehicles on their way first pass signal group SG1 of the SC SC1 and then
    signal group SG2 of the SC SC2. We call such a combination of two consecutive signal groups
    with one volume a coordination path leg or shorter path leg.
    A path leg is relevant for the coordination, if the following properties apply.
    Path leg starts and ends at SC of the same coordination group
    Path leg contains no nodes of controller type All-way stop
    Path leg passes through node of controller type two-way stop only in the direction of the
    major flow
    Path leg does not pass through other signalized nodes
    Travel time on the path leg is short enough, so that a significant platoon remains (specification below)
    No link along the path leg exceeds a threshold for the saturation
    All conditions except for the first one are aimed at a platoon remaining along the path leg.
    Optimization treats the traffic flows on all path legs interdependently. In each case it is assumed that within a cycle all vehicles start as a platoon at the beginning of the green time. This
    means, that beginning with the green time start, outgoing vehicles flow off with the saturation
    flow rate qmax, until the volume per cycle has been exhausted. The following applies:

    Here, N is the effective number of lanes for the turn. If the green time duration is insufficient
    and does not allow the volume allocated to a cycle from the assignment to exit with q max ,
    Visum ignores the excess volume and logs this in the message file.
    The platoon resolution, solely caused by different vehicle speeds, describes the platoon development formula according to Robertson. This model discretely divides the time in increments
    (in Visum of 1 s) and displays the number at time t, at which a vehicle arrives at the end of a
    path leg as a function of the number at time t < t, at the beginning of the path leg departing
    vehicle.
    PTVGROUP

    307

    6.5.4.4 Signal coordination (Signal offset optimization)

    where
    qt

    the number of vehicles arriving at the end of the path leg in time step t

    qt

    the number of vehicles departing at the beginning of the path leg in time step t

    F
    with specified constants and
    T

    travel time tCur on the path leg

    For calculating queue lengths it is presumed that separate lanes of sufficient length exist for
    separate signal groups at an approach. Visum generally assumes "vertical" queues for signal
    coordination and does therefore not consider spillback upstream over several links or have an
    effect on the capacity of the turns of other signal groups.
    For the evaluation of the progression quality, Visum calculates a number of skims which are
    used throughout literature. In the subsequent formulas CT determines the cycle time, GT the
    green time and qt the number of vehicles arriving at a node in time step t.

    Platoon index =

    with

    This size measures the "distance" of a volume profile of an equal distribution. The value varies
    from 0 (equal distribution) to 2 (for a distinct platoon). A high value means that coordination is
    worthwhile at this node, because the arriving vehicles are focused on part of the cycle time, so
    that there is a chance of moving the green time there, by changing the offset time.

    Vehicles at green =

    This size directly measures how well coordination works. It calculates which part of the volume
    passes the node without stopping at the SC.

    Platoon ratio =
    The size also measures how well coordination works, whereas high values imply good coordination. Especially high values are achieved when a large share of arrivals enter at green, although the green ratio itself is smaller.
    The platoon ratio PR is the basis for the important ArrivalType parameter in waiting time calculations according to HCM.
    308

    PTVGROUP

    6.5.4.4 Signal coordination (Signal offset optimization)

    ArrivalType =
    Queue length queue t at a signal group to cycle second t results from the difference of cumulative inflows and exit flows. For this calculation, Visum also calculates the delays of travel
    times with specified arrival time in the queues and hence, the mean and total wait time.
    Input attributes with effect at signal coordination
    Signal coordination accesses the network objects and the input attributes displayed in table
    116.
    Note: Node geometry attributes such as the stop line position, for example, are not regarded for signal coordination.
    Network object

    Attributes

    Note

    PrT paths

    Volume

    From assignment

    Links, turns, main


    turns

    A freely selectable
    attribute

    Is interpreted as travel time and will be summed up for travel time calculation per path
    leg

    SC with all components

    All

    Signal timing, cycle time, mapping of signal


    groups and lane turns, selection of a reference SC that has offset = 0.

    Signal coordination
    Cycle time family and Grouping of the SCs to be coordinated colgroups
    assigned SC
    lectively
    Table 116: Input attributes with an effect on signal coordination
    Output attributes at signal coordination
    The effect of the signal coordination lies mainly in assigning the attribute offset of the coordinated SC with an optimal value.
    Alongside that, all skims listed above can be calculated for measuring the progression quality.
    Their definitions first of all refer to a single path leg. In order to easier display results in a network model, Visum aggregates the values of all skims on links and saves the results as link
    attributes. Visum allocates the attributes at all approach links to signalized nodes which have
    a volume of > 0. All link attributes for signal coordination results are contained in table 117.

    PTVGROUP

    309

    6.5.4.4 Signal coordination (Signal offset optimization)


    Name

    Value
    type

    Value
    range

    Meaning

    SC coord vehicles on
    green

    Double

    0.0 .. 100.0

    Number of vehicles which arrive


    during green time [%]

    SC coord platoon index

    Double

    0.0 .. 2.0

    Definition see above

    SC coord platoon ratio

    Double

    0.0 ..

    Definition see above

    SC coord arrival type

    Integer

    1 .. 6

    Definition see above

    SC coord wait time

    Time

    0 s ..

    Total wait time [Vehicle seconds]


    Note: For links to overloaded signal
    groups, this value is set to 100,000 h.

    SC coord maximum queue Double


    length

    0.0 ..

    Max. number of queued vehicles over


    all cycle seconds [Veh]
    Note: For links to overloaded signal
    groups, this value is set to 100,000.
    Table 117: Output attributes of links for results of signal coordination
    Note: By the name component 'SC coord', the attribute SC coord arrival typeis indicated
    as signal coordination output attribute. It is not identical to the ICA arrival type attribute,
    which is used as entry for ICA calculation. If you want to calculate the ICA impedance
    with an arrival type which corresponds with the given offset time intervals, first perform
    the Signal offset analysis and then copy the SC coord arrival type values to the ICA
    arrival type attribute.
    Procedure parameters
    Besides the network object attributes, the procedure parameters listed in table 118 control
    signal coordination.

    310

    Name

    Value range (Standard)

    Meaning

    Automatic Analysis

    Boole (True)

    After signal coordination, the output link


    attributes are automatically updated.

    Coordination group set Set of coordination


    groups (all)

    Coordination is only carried out optionally for selected signal coordination


    groups.

    Demand segments set

    Set of assigned PrT_


    DSeg (all assigned
    PrT_DSeg)

    Optionally, path legs are only determined


    from the assignment paths of selected
    demand segments.

    MaxSaturation

    Double > 0 (80%), in


    percent

    If this saturation is exceeded on a path


    leg link, the path leg is ignored for coordination, because no platoon is retained
    with too high saturation.

    MinPlatoonIndex

    Double > 0 (0.4)

    If the platoon index is below this threshold at the end of the path leg, the path

    PTVGROUP

    6.6 PrT skims


    Name

    Value range (Standard)

    Meaning
    leg is ignored for coordination, because
    the platoon is not distinct enough.

    RobertsonAlpha

    Double > 0 (0.35)

    Parameter for the platoon progression formula according to Robertson

    RobertsonBeta

    Double > 0 (0.8)

    Parameter for the platoon progression formula according to Robertson

    TravelTimeLinkAttr

    numeric link attribute


    (AddValue1)

    TravelTimeLinkFac

    Double > 0 (1.0)

    When calculating the path leg travel time,


    for each traversed link, TravelTimeLinkFac TravelTimeLinkAttr is
    summed up

    TravelTimeTurnAttr

    Numeric turn attribute When calculating the path leg run time,
    (AddVal1)
    for each traversed turn, TravelTimeTurnFac TravelTimeTurnAttr is
    Double > 0 (1.0)
    summed up

    TravelTimeTurnFac
    TravelTimeMainTurnAttr

    Numeric main turn


    attributes (AddVal1)

    TravelTimeMainTurnFac

    Double > 0 (1.0)

    MaxCalculationTime

    Time

    When calculating the path leg run time,


    for each traversed turn, TravelTimeMainTurnFac TravelTimeMainTurnAttr is summed up
    Calculation time for the solution of the
    optimization problem is restricted. The
    best solution found up to the specified
    time limitation, is assigned.

    Table 118: Procedure parameters for signal coordination


    Problem solution
    To determine an optimal set of offset times per SC, Visum sets up a mixed integer linear optimization problem. The deciding variables in this problem are the differences of the offset times
    of neighboring SCs, the objective function is an in sections linearized approximation of the
    wait time in dependency thereof. Secondary conditions express that the differences between
    the offset times of adjacent SCs along each circle in the network have to be added to an integer multiple of the cycle time.
    A detailed description of the method is found in Mhring, Nkel, Wnsch 2006.

    6.6

    PrT skims
    With the Calculate PrT skim matrix procedure, the PrT skims listed in table 119 can be calculated (see User Manual: Chpt. 18.8 , page 1984). The abbreviations in parentheses indicate
    the file extensions which are used by default for skim matrix output in version files.

    PTVGROUP

    311

    6.7 Distribution of traffic demand across PrT connectors


    t0-PrTSys (TT0)

    TSys-specific travel time t0 in unloaded network

    tCur-PrTSys (TTC)

    TSys-specific travel time tCur in loaded network

    AddValue1..3 (AD1 - AD3) Sum of AddValue


    Trip distance (DIS)

    Distance covered from origin to destination

    Direct distance (DID)

    Direct distance between origin and destination zone

    Speed v0-PrTSys (VP0)

    TSys-specific speed v0 in unloaded network

    Speed vCur-PrTSys (VPC) TSys-specific speed vCur in loaded network


    Toll (TOL)

    Toll of traversed links

    Impedance-PrTSys (IMP)

    TSys-specific impedance in unloaded network

    AddValue-TSys (ADS)

    Sum of TSys-AddValue data

    User-defined (UDS)

    Flexible calculation of a mean attribute value per OD pair,


    also allows for the linkage of attributes of different traversed
    network objects (see User Manual: Chpt. 18.8.1.2 , page
    1986)

    Table 119: PrT skims


    Calculating skims is either done via the best path as regards to the set criterion or via aggregation from the paths of an assignment result calculated beforehand. In this case you can
    select one of the aggregation functions listed in table 120.
    Minimum impedance

    Skim value calculated from the path with minimum impedance

    Maximum impedance

    Skim value calculated from the path with maximum impedance

    Mean over paths

    Skim value calculated as a mean over all paths

    Mean over path volume

    Skim value calculated as a mean over all paths weighted with


    the corresponding path volume
    Table 120: Aggregation functions for skim data calculation
    Moreover, the set of origin-destination relations for skims can be calculated, and also restricted like the type of network objects which are included in the skim calculation.

    6.7

    Distribution of traffic demand across PrT connectors


    PrT origin and destination demand can be distributed across PrT connectors freely or proportionally. In the case of proportional distribution, there are again two variants: distribution of
    the total demand or distribution per OD pair (see "Distribution of demand of a zone to the
    connectors" on page 59).
    Free distribution
    During route search, only the connector time is considered and traffic demand is distributed
    without further constraints onto the routes with the lowest impedance.

    312

    PTVGROUP

    6.7 Distribution of traffic demand across PrT connectors


    Proportional distribution of total traffic
    Before the route search is carried out, the share of total origin and destination traffic is calculated for every zone whose demand is to be distributed proportionally. From this, a virtual
    connector capacity (= proportion origin/destination demand) can be deduced for every
    connector 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 VD function for connectors. A steep VD 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. When using this option, it should be noted, that the distribution may have
    very different effects on the individual OD pairs. If the link impedance equals the displayed
    lengths, practically all trips from zone 1 to zone 3 lead via node 2. The vast majority of trips
    from zone 1 to zone 2 however are made via node 1.

    Illustration 75: Example network for proportional distribution of the traffic demand
    Example: Connector capacity determination for proportional distribution of the total traffic
    (illustration 75)
    Zone 1 has proportional distribution
    Zone 2 has proportional or absolute distribution
    Zone 3 has proportional or absolute distribution
    Travel demand from zone 1 to zone 2: 1,000 trips
    Travel demand from zone 1 to zone 3: 400 trips
    Origin demand zone 1: 1,400 trips
    Connector zone 1 node 1: 40 % proportion
    Connector zone 1 node 2: 60 % proportion
    Capacity of connector zone 1 node 1: 40 % x 1400 = 560 trips
    Capacity of connector zone 1 node 2: 60 % x 1400 = 840 trips
    Steep VD function for connectors, for example BPR function with a = 1, b 4, c 1
    Proportional distribution of each individual relation (MPA)
    Alternatively, the proportional distribution can be applied to each OD pair. This leads to the following distribution in the example above:
    Example: determination of connector capacity for proportional distribution per OD pair:

    PTVGROUP

    313

    6.8 Blocking back model


    Zone 1 node 1 zone 2: 40 % 1000 = 400 trips
    Zone 1 node 1 zone 3: 40 % 400 = 160 trips
    Zone 1 node 2 zone 2: 60 % 1000 = 600 trips
    Zone 1 node 2 zone 3: 60 % 400 = 240 trips

    6.8

    Blocking back model


    The blocking back model (pseudo-dynamic assignment, pa) fills the gap between merely static
    procedures, which do not have any temporal reference and cannot determine congestion-related wait times, and dynamic procedures that require long computation times. The procedure is
    much faster than any dynamic assignment, requires less memory capacity and can furthermore deliver information on congestion phenomena. The procedure can be applied in conjunction with static assignment in order to estimate queue lengths and wait times in
    oversaturated networks. In contrast to dynamic-stochastic assignment, it is suitable for networks with > 50,000 links and only requires few additional data for temporal distribution of the
    demand.
    The general idea is to re-assign route volumes that were calculated with any static assignment
    at an earlier stage. Output data of the procedure:
    new volumes on links, connectors, (main) turns and (main) nodes
    queue lengths on links and connectors
    wait times on links
    The original volumes of links, connectors and (main) turns resulting from the assignment are
    stored with the following attributes:
    Volume demand PrT with base
    Volume demand DSeg
    Volume demand PrT
    Original node volumes can be found in the following attribute:
    Volume demand PrT
    The blocking back model is divided into two phases, the second phase is optional.
    Phase 1 (congestion calculation)
    Along a route, the demand share is passed on from one link to the next until a restricting capacity has been reached. The following rules apply in this process.
    1. The volume passing from one link to the next cannot exceed the capacity (PrT) of the link,
    the capacity of the To node, and the capacity of the turn. For links, the amount of traffic leaving the link counts (bottleneck at end of link).
    2. The queue on a link can never exceed the stocking capacity of the link.
    3. As soon as a queue forms on a link in some direction, no traffic can pass the link even if the
    respective route does not lead across the bottleneck that is causing the congestion.
    The fourth rule which limits the inflow of a link, directly results from this.

    314

    PTVGROUP

    6.8.1 General notes on the blocking back model


    4. The inflow of traffic on a link is limited to the amount resulting from capacity plus stocking
    capacity.
    Phase 2 (precise wait time calculation)
    Already in phase 1, wait times are calculated from the resulting queue lengths and the duration of this phase. In the optional phase 2, more precise wait times are calculated by simulating also the discharge of the congestion. New traffic is not imported, but rather the traffic
    stored in the local queue lengths is distributed along the routes according to the same rules as
    in the first phase. This is done in small time steps, where the capacities still limit the inflow.
    After each step, the level of congestion is stored The second stage ends, when all local congestion is zero and thus no traffic remains in the network. This results in a series of snap shots
    of the level of congestion at different times which are then used to calculate a delay.

    6.8.1

    General notes on the blocking back model


    The blocking back model is no independent assignment procedure, but it modifies the results
    of previously run assignments or of the running assignment. As an option, the blocking back
    model can be carried out together with an assignment (see User Manual: Chpt. 18.5 , page
    1925).
    The blocking back model only applies to PrT transport systems. Assuming that PuT transport
    systems are either not affected by any congestion or that the timetables used already regard
    the wait times. PuT-caused congestion on commonly used links can be neglected or can be
    considered by a basic volume.
    Since volumes of different PrT demand segments are summed up before entering the queue
    length, all volumes are invariably converted into car units.
    The following two operating modes are possible:
    You can calculate the blocking back model post-processed following an assignment. It therefore does not influence the route choice.
    Alternatively, you can execute the blocking back model in the external iteration of an assignment procedure. The results are then included in the link impedance and therefore in
    the route choice. This modus operandi is not recommended, since it significantly downgrades the convergence of the particular assignment procedure. To account for blocking
    back effects on the route choice during assignment, it is best to use the proceure "Assignment with ICA" (see "Assignment with ICA" on page 374).
    In either case it can be combined with the following assignment procedures: Incremental, Equilibrium, Equilibrium_Lohse, TRIBUT and any stochastic procedure. However, it cannot be combined with a dynamic assignment procedure.
    If an assignment has already been calculated for at least one demand segment, which is not to
    be recalculated, the blocking back model is calculated prior to the execution of the assignment of the already assigned demand segments. This is to ensure that the values for t cur
    and t w are consistent with the current network status and to avoid that assignments with a
    blocking back model share and those without are combined.
    If the blocking back model is integrated into and executed within other procedures, we must
    distinguish between iterative procedures (Incremental assignment, Equilibrium_ Lohse and

    PTVGROUP

    315

    6.8.1 General notes on the blocking back model


    Stochastic assignment) and balancing procedures (Equilibrium assignment and TRIBUT).
    With iterative procedures, after volume calculation, a corrected volume and wait times are
    determined with help of the blocking back model. Using the corrected volume, in the i iteration,
    the program calculates a new value for the current travel time ticur and adds the wait time tiw to
    it.

    As new value, the arithmetic mean Ti of all former t i is used, which is also considered in the
    subsequent route search.

    Here, t0Cur = t0 and t0w = 0 applies.


    The consideration of earlier values guarantees the necessary attenuation and enforces the
    procedures convergence. If only the current value would be taken into account when calculating the impedances in the next iteration, the total traffic volume would shift back and forth
    between alternative routes without converging towards a result.
    The value returned for the wait time t w at links however, is just the wait time value determined
    during the previous calculation of the blocking back model. In the case of convergence, it is
    consistent with the times used in the assignment. The following applies:
    For the calculation of the travel time tCurNew, using the corrected volume is necessary,
    since the increase of the travel time above the capacity limit is no longer determined by
    volume-delay functions but modeled by explicitly calculated wait times.
    If there is neither any congestion nor a decrease in the volume due to a flow-rate loss, tCur
    = tCurNew and tw=0 apply in any case. The impedance is unchanged compared to a conventional assignment in this case.
    If the blocking back model is integrated into an equilibrium assignment (not recommended),
    the selected procedure is calculated first and the blocking back model is calculated subsequently in an outer loop. Both methods are based on the fact that the volume of a link equals
    the total volume of all routes traversing that link. For that reason a link-related modification of
    the volume, as performed by the blocking back model would have no effect.
    Instead, the result of the calculation of the blocking back model is used to modify the VD functions of each link temporarily so that identical travel times result for unchanged network volumes and for the changed network volumes with the original VD functions. These modified VD
    functions can then be used for another iteration of an equilibrium assignment. If the network
    volume has not changed, an equilibrium state has been reached which regards the modified
    travel times tCur that result from the blocking back model. Otherwise a further iteration is carried
    out, that includes blocking back model and assignment. As is the case with other methods, the
    modified VD functions are averaged over several iteration steps in order to suppress the alternation of the route choice between several alternatives.

    316

    PTVGROUP

    6.8.2 Procedure of the blocking back model


    The equilibrium state that is reached by this integrated calculation procedure is characterized
    as follows: in due consideration of the changes to the travel times (and thus to the impedances) which result from the volume calculated by means of the blocking back model, the travel time (the impedance) is the same for each route of an OD pair.
    Limiting capacity
    According to rule 1, the traffic flow from link to link along a route is limited by the capacity of the
    link and the capacity of the link's ToNode and the capacity of the turn during the blocking back
    model calculation. In the blocking back model parameters you can select individually, whether
    link and turn and node capacities are to be regarded. The settings have the following meaning:
    Link capacity restricts the outflow per link. As threshold, either the link attribute Capacity
    PrT can be used or the summed up Capacity PrT of the outgoing turns. The latter option
    is only provided for compliance with out-dated versions. It is no longer recommended. It is
    recommended to use the option Turn capacity instead.
    Node capacity restricts the flow per node (sum of all turn volumes) to the node attribute
    Capacity PrT. These node capacities are only regarded for traffic flows on secondary
    links (tmodelspecial = true) towards the node. Traffic flows on major legs therefore also
    have an effect on crossing routes via secondary links.
    Turn capacity restricts the flow per turn to the turn attribute Capacity PrT.
    These three options can be combined at will.
    Furthermore you can decide by node, whether the global blocking back model parameter settings are to be regarded; alternatively, a node-specific setting (node attribute Use preset
    blocking back capacity settings = activated) can be used instead. The node-specific setting
    is regarded for all turns via this node and for all links leading into this node. To regard the turn
    capacity only at particular nodes, for example, then exclude the consideration of turn capacities in the global blocking back model parameters and activate the attributes Use preset
    blocking back capacity settings and Use turn capacity in blocking back at the particular
    nodes.

    6.8.2

    Procedure of the blocking back model


    The procedure is divided into the following steps:
    Determining the excess congestion factor
    Formation of congestion (phase 1)
    Relief of congestion (phase 2) optional
    Determining the wait times
    Determining the excess congestion factor
    Prior to the actual simulation of the queuing up, the excess congestion factor is calculated for
    the network. In this process, the volumes and capacities of the links, nodes and turns for which
    you have preset that they are to be regarded are taken into account.
    For a single link L, the excess congestion factor Link(L) is given by

    PTVGROUP

    317

    6.8.2 Procedure of the blocking back model

    .
    Here, VolDem(L) is the link volume resulting from assignment, Cap(L) is the PrT capacity of the
    link, and ScalingFactor is the scaling factor for capacities from the blocking back model parameters. Furthermore, VolBasic volume (L ) is a basic link volume. You can select it in the general
    procedure settings via PrT settings > Assignment.
    Analogously, for turns T and nodes N, excesss congestion factors Turn(T) and Node(N) are defined. Since in Visum you can only set basic volumes for turns and links, the basic volume total
    of turns at the node is used as the basic volume for nodes. Network excess congestion factor
    is the maximum of excess congestion factors for all links, nodes, and turns whose capacities
    are to be taken into account. It indicates by which factor the (remaining) capacity in the network is exceeded at most.
    The percentage of traffic corresponding to the reciprocal of this number can pass through the
    network without any congestion. If 1, the procedure is not carried out. In this case, the corrected volumes (Vol) equal the volumes calculated in the assignment (VolDem), thus no congestion occurs.
    If the denominator in the formula for the excess congestion factor calculation falls below 0 or
    becomes 0 for a link or node or turn, there is no more free capacity available and the procedure terminates.
    Simulation phase 1 Formation of congestion
    In phase 1, queue lengths on links and connectors are calculated and also the reduced (compared to the original values) volumes of links, connectors and nodes. Thereto, we let traffic
    flow into the network step by step along the routes resulting from assignment, and in contrast
    to the previous assignment, the rules 1 to 3 are observed here. However, rule 3 is weakened
    by the permeability factor P which determines the share that can pass existing congestions. If P
    = 0, rule 3 is satisfied.
    Let N be the number of shares for the volume distribution in phase 1. You can specify this parameter in the procedure parameters for the blocking back model. In order to enforce rules 1 to
    3, we iteratively propagate the N-th part of the route volume from the origin to the destination
    until we reach a link on which a queue or another bottleneck (link, node, or turn) has already
    formed for which the capacity is exceeded. This is carried out N times until all of the traffic has
    flown into the network. In this case, that part of the volume is not added to the link volume, but
    to the queue length.
    Find below a detailed description of the procedure in phase 1. These are the most important
    abbreviations used in this section:

    318

    VolDem

    Volume demand: volumes from the assignment without consideration of withheld vehicles in the blocking back model (i.e. if no blocking back model is calculated or no congestion occurs, VolDem equals the volume Vol)

    Vol

    (reduced) volume calculated in phase 1

    PTVGROUP

    6.8.2 Procedure of the blocking back model


    Cap

    PrT capacity of a link, a turn or a node

    Stocking capacity of a link

    Queue length of a link (or connector)

    Permeability of a link, describes the share of the flow that can pass existing
    queues

    Excess congestion factor

    Firstly, the network is loaded with that portion of demand which does not cause congestions
    yet. Then, the remaining demand flows into the network step-by-step. At first, the greatest natural number n is determined that satisfies n/N 1/. The general is then as follows:
    Initialize Vol for all links, turns, nodes and connectors by entering 0.
    Initialize Q or all links and connectors by entering 0.
    For all links L and connectors C, load Vol(L)*n/N or Vol(C)*n/N, respectively.
    For j = n+1 to N
    For each demand segment
    For each route R of the demand segment
    Load route R with VolDem(R) / N.

    Loading a volume flow to a route R with the n-th part of VolDem (flow) is performed as follows.
    Let L0, L1, ..., Lk be the generalized links of a route, i.e. L0 is the origin connector, Lk is the destination connector, and the real links are in between. Now, the traffic from the origin zone flows
    via L0 , L 1, ..., Lk to the destination zone, at which the traffic flow is always limited by the capacities of the links and turns and nodes and by congestions that might have formed.
    Capacities bear limiting effects as described below. Let toNode(L) be the To node of a link L
    and let Turn(Lj, Lj+1,T) be the turn from L to Lj+1 for the links L and T. Now, the flow from Lj to
    Lj+1 is limited by the capacity of Lj, and by the capacity of the To node of Lj, and by the capacity of the turn from Lj to Lj+1.
    Note: If you have decided that a particular capacity should not have an effect, then the calculation assumes an infinite capacity. Connectors have an infinite capacity by definition.
    The maximum volume maxFlow from Lj to Lj+1 then is
    maxFlow(Lj, Lj+1) = min{Cap(Lj) ScalingFactor - VolGrundbelastung(Lj),
    Cap(toNode(Lj)) ScalingFactor - VolGrundbelastung(toNode(Lj)),
    Cap(Turn(Lj, Lj+1)) ScalingFactor - VolGrundbelastung(Turn(Lj, Lj+1))}
    If the amount of in-flowing traffic on a link of the route exceeds the amount, that can flow off to
    the next link, then the portion of traffic that keeps flowing depends on the remaining free capacity:

    PTVGROUP

    319

    6.8.2 Procedure of the blocking back model


    Function Load(R, flow):
    Fr j = 0 bis k-1
    propagatingFlow = flow
    Falls Q(Lj) > 0
    propagatingFlow:= propagatingFlow * Permeability(Lj)
    propagatingFlow:= min(propagatingFlow, maxFlow(Lj, Lj+1))
    Vol(Lj) := Vol(Lj) + propagatingFlow
    Vol(toNode(Lj)) := Vol(toNode(Lj)) + propagatingFlow
    Vol(Turn(Lj, Lj+1)) := Vol(Turn(Lj, Lj+1)) + propagatingFlow
    Q(Lj) := Q(Lj) + (flow - propagatingFlow)
    Propagate queue backwards

    Traffic that cannot flow into the next link is added to the queue length. If the queue on a link
    exceeds the maximum stocking capacity K, then backups will arise on previous links of the
    route. In that process, the backup has to be subtracted from the volume(s) of the previous link
    (s) again (also nodes and turns are concerned), since this flow actually cannot have reached
    the congested link being located ahead in the route course:
    Function PropagateQueue(R):
    propagatingQ = 0
    Fr j = k-1 bis 1
    Falls Q(Lj) > K(Lj)
    propagatingQ := Q(Lj) - K(Lj)
    Q(Lj) := K(Lj)
    Q(Lj-1) := Q(Lj-1) + propagatingQ
    Vol(Lj-1) = Vol(Lj-1) - propagatingQ
    Vol(toNode(Lj-1)) := Vol(toNode(Lj-1)) - propagatingQ
    Vol(Turn(Lj-1, Lj)) := Vol(Turn(Lj-1, Lj)) - propagatingQ

    After phase 1, nodes require a special treatment for the following reason: Though there are no
    turns at connectors, connector nodes are loaded in the process. To achieve the state, that the
    node volume = sum of all turn volumes at connector nodes after phase 1, the node volume of
    connector nodes is recalculated from the turn volumes after the procedure.
    We use a simple example with two routes to illustrate the procedure. Route1 leads from A to
    D, route2 from B to C. Both routes have a volume VolDem of 200vehicles. The volume is distributed to the routes in four iteration steps with 50vehicles each. The number of iteration
    steps is based on the procedure parameter Number of shares for flow distribution in phase
    1. For reasons of simplification, only the link capacity is considered as limiting capacity in the
    example. Route1 is always charged first. There is a bottleneck on route1. On route 2, a
    backup arises though this route does not traverse the bottleneck link.

    320

    PTVGROUP

    6.8.2 Procedure of the blocking back model

    Illustration 76: Blocking back model, phase 1: Formation of congestion Iteration steps 1 and 2.
    In the first two iteration steps, each of the two routes is loaded with 50 vehicles. Queues do not
    form yet (illustration 76).

    Illustration 77: Blocking back model, phase 1: Formation of congestion Iteration step 3, route 1
    Route1: On the highlighted link, a bottleneck is located in iteration step 3. Due to the insufficient stocking capacity of this link, the queue propagates to the preceding link (illustration
    77).

    PTVGROUP

    321

    6.8.2 Procedure of the blocking back model

    Illustration 78: Blocking back model, phase 1: Formation of congestion Iteration step 3, route 2
    Since there is now a congestion on the middle link, the vehicles following route 2 also get
    stuck in the queue (illustration 78).

    Illustration 79: Blocking back model, phase 1: Formation of congestion Iteration step 4, route 1
    Another 50 vehicles are added to route 1 in iteration step 4. As the stocking capacity of the
    middle link is fully exhausted, vehicles continue to propagate backwards (illustration 79).

    322

    PTVGROUP

    6.8.2 Procedure of the blocking back model

    Illustration 80: Blocking back model, phase 1: Formation of congestion Iteration step 4, route 2
    The 50 vehicles with route 2 cannot even reach the middle link; they all get stuck in the congestion on the first link (illustration 80).
    Simulation phase 2: Relief of congestion
    During the simulation phase 1, the local queue length of each link and corrected volumes
    have been determined. If phase 2 is not calculated (optional), the wait times for phase 1 are
    calculated directly. If the relief of congestion is simulated, too, further wait times arise which
    are determined on the basis of the continued simulation without further inflow of traffic until all
    queue length reach zero. Any traffic passing through the network in phase 2 thus originates
    from the queues determined in phase 1. The maximum transfer flow in each iteration equals
    the Mth share of the capacity. M describes the procedure parameter Number of shares for
    flow distribution in phase 2 and determines the number of iterations in this phase. Accordingly, the M-th portion of the interval length of the first simulation phase elapses per step.
    After each iteration, the queue lengths on all links are recorded.
    We analyze the relief of congestion in the example first and then describe the procedure in
    detail.

    Illustration 81: Blocking back model, phase 2, relief of congestion. Initial situation

    PTVGROUP

    323

    6.8.2 Procedure of the blocking back model


    illustration 81 shows the initial situation prior to relief of congestion in phase 2. Only the queue
    lengths from phase 1 are regarded, there is no further influx. For congestion relief, four portions are used (M = 4).

    Illustration 82: Blocking back model, phase 2, relief of congestion. Iterations step 1, route 1
    On route1, the maximum congestion efflux is limited by the link capacity Cap = 100. Thus, Cap /
    M = 25 vehicles can flow off in iteration step1 (illustration 82).

    Illustration 83: Blocking back model, phase 2, relief of congestion. Iteration step 1, route 2
    On route2, the maximum congestion efflux is limited by the capacity of the link in the middle.
    Since two routes traverse the link in the middle, only a certain portion of the capacity is available for route 2 for this iteration, (Cap / M = 100); this portion is (Cap / M) (VolDem(Route 2) /
    VolDem(link in the middle)) = 100 (200 / 400) = 50 (illustration 83).

    324

    PTVGROUP

    6.8.2 Procedure of the blocking back model

    Illustration 84: Blocking back model, phase 2, relief of congestion. Iteration step 2, route 1
    During iteration step 2, again 25 vehicles flow off via route 1 (illustration 84).

    Illustration 85: Blocking back model, phase 2, relief of congestion. Iteration step 2, route 2
    Again, 50 vehicles flow off via route 2 (illustration 85).

    Illustration 86: Blocking back model, phase 2, relief of congestion. Iteration step 3, route 1

    PTVGROUP

    325

    6.8.2 Procedure of the blocking back model


    During iteration step 3 only some (12.5) vehicles flow off via route 1 which are part of the remaining queue on the link in the middle (like in iteration1 for route2). The link on the right, however, is traversed by only one route; that's why for this iteration the total capacity is provided for
    flow off of the congestion (Cap / M = 25) (illustration 86).

    Illustration 87: Blocking back model, phase 2, relief of congestion. Iteration step 3, route 2
    On the middle link (12.5 vehicles), the remaining congestion can flow off via route 2 (illustration 87).
    The congestion efflux in phase 2 thus works in a similar way as the formation of the congestion
    in phase 1, save that the traffic does not enter the network via the connectors, as usual, but
    exists at the links with congestion in the network. In each iteration, we let flow off a portion of
    the traffic which is restricted by the capacities of the links and nodes and turns; thus, new
    queue lengths will be obtained. This is repeated until either the maximum number of iterations
    set for phase 2 is reached (user-defined parameter for the blocking back model) or until the
    congestion is no longer available. More accurately, the procedure is described as follows.
    Initialize prevQ with queue lengths on links and connectors after phase 1
    For j = 1 until (max. number of iterations in Phase 2) or until any prevQ = 0
    For each demand segment
    For each route R of the demand segment
    Calculate the congestion flow off for R based on M and the capacities
    and thus obtain currQ
    Calculate wait time
    prevQ:= currQ

    In detail, the relief of congestion goes like this: In each iteration step, the M-th portion of the
    capacity of links, nodes and turns is available. Thus, the maximum traffic that can flow off of
    link L due to the link's capacity, is Cap(L) / M per iteration. To each route R, that traverses link L,
    a certain share in the capacity is provided; this share equals the route's share in the original
    total link volume, i.e. VolDem(R) / VolDem(L). For a link L that belongs to a route R, the maximum
    outflow of a congestion results from the following formula:
    maxOutflow(L) = (Cap(L) / M) (VolDem(R) / VolDem(L))

    326

    PTVGROUP

    6.8.2 Procedure of the blocking back model


    Furthermore, the outflow is restricted by the capacity of the To-Node and by the turn capacity.
    Let L0, L 1, ..., Lk again be the generalized terms for links of a route, i.e. L0 is the origin connector, Lk is the destination connector, and the real links are in between. Thus, the maximum outflow from Lj to Lj+1 results as follows:
    maxOutflow(Lj, Lj+1) = min{(Cap(Lj) / M) (VolDem(R) / VolDem(Lj)),
    (Cap(toNode(Lj)) / M) (VolDem(R) / VolDem(toNode(Lj))),
    (Cap(Turn(Lj, Lj+1)) / M) (VolDem(R) / VolDem(Turn(Lj, Lj+1)))}
    The traffic flow that actually flows out comes from the existing queues. For each route R, the
    volume originating from the queue on link Lj is as follows:
    sourceVolQ(Lj) = prevQ(Lj) (VolDem(R) / VolDem(Lj))
    The origin traffic of a link (limited by the maximum outflow maxOutflow) flows to the next link.
    This traffic is then added to the origin traffic on the next link. If maxOutflow is smaller than the origin traffic, queues will form again. The following therefore applies:
    Function QueueOutflow(R, M):
    arrivedFlow = 0
    For j = 0 to k-1
    totalSourceVol := sourceVolQ(Lj) + arrivedFlow
    propagatingFlow:= min(totalSourceVol, maxOutflow(Lj, Lj+1))
    currQ(Lj) := currQ(Lj) - propagatingFlow
    arrivedFlow := propagatingFlow
    Propagate queue backwards

    As in phase 1, the queue is propagated backwards:


    Function PropagateQueue2(R):
    propagatingQ = 0
    For j = k-1 to 1
    If currQ(Lj) > K(Lj)
    propagatingQ := currQ(Lj) - K(Lj)
    currQ(Lj) := K(Lj)
    currQ(Lj-1) := currQ(Lj-1) + propagatingQ

    Please note that the results of the blocking back model may depend on the order of routes that
    are processed. However, the more shares you choose for the distribution of the traffic flow, the
    smaller the possible differences will be. If the blocking back model is applied to the same network for example, on the one hand with an equilibrium assignment and with LUCE on the
    other hand, then the results might differ slightly even if all routes are identical.
    This is due to the fact, that - in contrast to other assignment procedures - LUCE does not
    directly provide routes, but bushes in the first instance, which represent multiple routes at the
    same time. In conjunction with LUCE, the blocking back model calculations are performed
    directly on the bush level. Since the bushes can include various from-links and to-links for
    each link, the traffic flows need to be distributed appropriately. This is performed in a way as if

    PTVGROUP

    327

    6.8.2 Procedure of the blocking back model


    several routes were processed simultaneously. From this, slightly deviating results may be the
    outcome.
    Determining the wait times
    Resulting from the second simulation stage are the values for the local queue length of each
    link after each measuring section (iteration). These values together with the queue length after
    the first simulation stage are used to form an integral of the total wait time over the measured
    queue length.
    illustration 88 shows an example of displaying the overall wait time as an integral via the interpolated measured queue lengths.

    Illustration 88: Overall wait time as an integral via the interpolated measured queue lengths
    This is expressed by the following formula:

    with I being the duration of the first simulation interval in seconds. The sum extends over the
    measured values with Q L(0) indicating the queue length Q L after the first simulation phase. If
    the second phase is not calculated, the second term in the bracket is omitted and the wait time
    results in the duration of the simulation interval for phase 1 and the queue length at the end of
    the first phase.
    This results in a mean wait time per vehicle unit as follows

    328

    PTVGROUP

    6.9 Convergence criteria of assignment quality


    On inks with traffic jams, the effective capacity results from the minimum of link capacity attribute Cap and reduced volume Vol, created through spillback congestion.

    6.9

    Convergence criteria of assignment quality


    To assess the convergence speed Visum traces the convergence criteria for each iteration, for
    all static assignment procedures (apart from incremental assignment). Stochastic assignment
    only logs the internal iterations within the last external iteration (see "Stochastic assignment"
    on page 385).
    These criteria are output in a list as indicators of the goodness of a PrT assignment (see User
    Manual: Chpt. 18.7.1 , page 1982). They are initialized prior to each assignment and stored
    with the version file.
    Among others, the following criteria are calculated:
    Hypothetic vehicle impedance
    Minimum impedance value calculated hypothetically for the next iteration step on the assumption that all vehicles based on the current impedances in the network use the best
    path.
    Gap = (Veh.Imp.- hypothet. Veh. Imp.) / hypothet. Veh. Imp.
    Degree of convergence for the network.
    The value is the weighted volume difference between the vehicle impedance of the network
    of the current iteration and the hypothetical vehicle impedance.
    Total Excess Cost TEC (Total Excess Cost)

    where
    TEC

    Difference between total impedance in the charged network and the hypothetical impedance resulting if all vehicles took the shortest path per OD pair.

    Pij

    Number of routes from i to j

    Rij

    min

    minimum impedance among all routes from i to j

    Average Excess Cost AEC (Average Excess Cost)


    AEC = Excess cost per vehicle

    The following applies:


    n = Number of trips: Total demand in the demand matrix minus the diagonal, thus the sum
    of demand contributing to the assignment, no internal traffic.

    6.10

    Distribution models in the assignment


    In Visum, several assignment procedures are structured as follows: First, a number of alternatives (routes or connections) is determined. Then the total demand per OD pair is distributed

    PTVGROUP

    329

    6.10.1 The Kirchhoff model in the assignment


    across these alternatives. These are the (static) stochastic PrT assignment, the dynamic-stochastic PrT assignment and the timetable-based PuT assignment. PrT assignment procedures
    use alternative routes from origin zone to destination zone, whereas the PuT assignment procedure provides alternative connections (routes with detailed departure times). For simplification, we will only mention routes below in this section.
    A distribution model determines the share of demand which is assigned to a certain route. This
    portion depends on the impedance of a route. In all cases, percentage Pia , of route i, is determined based on the demand of an OD pair within time interval a, so that impedance Ria is applied in a distribution function, allowing the program to calculate utility Uia of the route. For this
    distribution function the Kirchhoff, Logit, Box-Cox, Lohse models and Lohse with variable Beta
    are available. The following approach applies to all models:
    1. Impedance Ria is converted to the utility Uia of route i in the time interval a:
    Uia = f(Ria)
    2. From this utility Uia the percentage of demand Pia is calculated (where n is the total number
    of routes).

    The models reveal differences in the functional relation f of impedance and utility.

    6.10.1

    The Kirchhoff model in the assignment


    The utility is as follows:

    The percentage of demand is calculated as follows:

    The sum of all routes j is taken and is used as a parameter for modeling the impedance sensitivity. In this distribution method, the ratios of the various impedances are decisive. It does
    not matter, therefore, whether two routes have impedances of 5 and 10 minutes, for example,
    or 50 and 100 minutes the distribution is the same. illustration 89 shows the parameterization of the Kirchhoff distribution model on the interface.

    330

    PTVGROUP

    6.10.2 The Logit model in the assignment


    Illustration 89: Parameterization of the Kirchhoff distribution model

    6.10.2

    The Logit model in the assignment


    In this model, instead of the ratio between the impedances, their difference is used for the distribution rule. The impedance is additionally divided by a scaling divisor.
    The utility is as follows:

    The percentage of demand is as follows:

    Parameter describes the sensitivity of passengers towards increased impedances. As in this


    case the differences rather than the ratios of the impedances are considered, it does not matter whether two routes have impedances of 5 and 10 minutes, for example, or 95 and 100
    minutes. illustration 90 shows the parameterization of the Logit distribution model on the interface.

    Illustration 90: Parameterization of the Logit distribution model

    6.10.3

    The Box-Cox model in the assignment


    This distribution model is based on the Box-Cox transformation. For the given 0, the BoxCox transformation is explained as follows:

    When calculating the utility, b(t)(R ia) is now included in the Logit model instead of Ri a, thus the
    result is

    PTVGROUP

    331

    6.10.4 The Lohse model in the assignment


    The percentage Pia of the route i in terms of the demand for time interval a is then calculated as
    follows:

    The importance of the Box-Cox model is illustrated by the two special cases below.
    =0 (leads to the Kirchhoff distribution)
    With these parameter settings, b(0)(Ria)=log(Ria) applies, thus the following applies to the
    choice:

    This is precisely the Kirchhoff model.


    =1 (leads to the Logit distribution)
    With these parameter settings, b(1)(Ria)=(Ria-1) applies, thus the following applies to the
    choice:

    This is identical to the Logit distribution.


    illustration 91 shows the parameterization of the Box-Cox distribution model on the interface.

    Illustration 91: Parameterization of the Box-Cox distribution model

    6.10.4

    The Lohse model in the assignment


    In this model, the impedances are put in relation to each other in an even more differentiated
    way.

    332

    PTVGROUP

    6.10.5 Lohse model with variable beta in the assignment

    applies.
    Here, Rmin :=
    is the smallest occurring impedance, and is again a parameter to control the impedance sensitivity. When calibrating, do not forget that is squared.
    a

    minjRja

    In this case, the impedance of a route is related to the minimum impedance, which therefore
    measures the relative difference from the optimum. 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. illustration 92 shows the parameterization of the Lohse distribution model on the interface.

    Illustration 92: Parameterization of the Lohse distribution model

    6.10.5

    Lohse model with variable beta in the assignment


    The model is described in Schnabel and Lohse (1997) and differs from the Lohse model in
    that the distribution parameter is determined depending on the value of the minimum impedance Rmina. The calculation can be calibrated in more detail when using three additional parameters , and .
    The following approach applies:

    The following therefore applies:

    is calculated according to the following formula:

    PTVGROUP

    333

    6.10.5 Lohse model with variable beta in the assignment

    The impedance is additionally divided by a scaling divisor.


    The variable distribution parameter improves the modeling of the impedance sensitivity. Identical ratios of impedances are considered differently for short routes compared to long routes.
    In the case of two routes with impedances of 5 and 10 minutes or 50 and 100 minutes, the distribution is not the same.
    The following example illustrates the effect of the distribution model Lohse with variable beta.
    In illustration 93, different best paths (10 min, 50 min, 150 min, 300 min) are compared with
    "detour" alternatives. The distribution to the routes is done on the basis of the sumptuary ratio
    and the absolute value of the best path.
    For shorter best paths and their alternatives lower detour sensitivity is assumed than for longer
    best paths.

    Illustration 93: Distribution with variable beta according to the modified Kirchhoff rule
    (see Schnabel / Lohse)
    The parameters in illustration 93 are described in table 121.

    Rmina

    10

    0.800

    0.010

    10 min

    3.32

    10

    0.800

    0.010

    50 min

    4.26

    10

    0.800

    0.010

    150 min

    6.68

    10
    0.800
    0.010
    300 min
    Table 121: Parameters for distribution with variable beta in illustration 93

    9.00

    illustration 94 shows the parameterization of the Lohse distribution model with variable beta
    on the interface.

    334

    PTVGROUP

    6.10.6 Comparison of the distribution models for the assignment

    Illustration 94: Parameterization of the Lohse distribution model with variable Beta

    6.10.6

    Comparison of the distribution models for the assignment


    The effects of the four distribution models (Kirchhoff, Logit, Box-Cox and Lohse) are illustrated
    in a simple example. table 122 to table 124 show three simple cases of a choice between two
    alternatives which represent either routes or connections. The model parameters used can be
    found in table 125.
    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 doubled, 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 difference 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 ratio of the impedances and thus generates the same distribution values for examples 1 and 3. The Box-Cox model allows a combination 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 (table 122), or 105
    or 110 minutes (table 123 ). 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 the example in
    table 124, where one can expect all passengers to choose 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 road-user.

    PTVGROUP

    335

    6.11 Incremental assignment


    No.

    R
    1

    Kirchhoff
    5

    94 %

    Logit
    78 %

    Box-Cox
    86 %

    2
    10
    6%
    22 %
    14 %
    Table 122: Distribution for two alternatives with impedance 5 and 10

    No.

    R
    1

    Kirchhoff

    Logit

    Box-Cox

    Lohse

    2
    110
    45 %
    22 %
    38 %
    Table 123: Distribution for two alternatives with impedance 105 and 110

    49 %

    Kirchhoff
    50

    94 %

    78 %

    0%

    51 %

    55 %

    100 %

    62 %

    No.

    105

    Lohse

    Logit
    100 %

    Box-Cox
    100 %

    2
    100
    6%
    0%
    0%
    Table 124: Distribution for two alternatives with impedance 50 and 100

    Lohse
    100 %
    0%

    Kirchhoff = 4
    Logit

    = 0.25

    Box-Cox

    = 1, = 0.5

    =4
    Table 125: Model parameters
    Lohse

    6.11

    Incremental assignment
    The incremental assignment procedure models how a network continuously fills up. At 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, turns and connectors. Because of the changed impedance, alternative
    shortest routes may be found in every step.
    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 (maximum 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 OD-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.

    336

    PTVGROUP

    6.11.1 Example of incremental assignment


    Subsequently, the new network impedances resulting from these volumes are calculated
    via the VD functions.
    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.

    6.11.1

    Example of incremental assignment


    table 126 shows the procedure of incremental assignment for the example network (see
    "Example network for PrT assignment procedures" on page 228). The 2,000 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 the car trips, i.e. 1,000 car trips.
    Iteration step 2
    The shortest route in the unloaded network 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:50min. It is again loaded with 25% of the car trips, i.e. with another 500 car trips. It now
    has a total of 1,000 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
    the route. Additional impedances for connectors and turns are not considered. In addition to
    this, it is assumed that impedance results from current travel time t Cur, and that current travel
    time in turn results from the BPR function with a=1, b=2 and c=1.

    LinkNo

    PTVGROUP

    Type

    Length [m]

    v0 [km/h]

    Capacity

    t0 [min]

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    30

    16,000

    80

    800

    12.00

    30

    5,000

    80

    800

    03:45

    10

    40

    10,000

    60

    500

    10:00

    11

    40

    5,000

    60

    500

    5.00

    337

    6.11.2 The procedure of incremental assignment


    Route

    Links of the route Length [m]

    1+8+9

    2
    3

    LinkNo

    t0 [min]

    26,000

    18:45

    1+2+3+5+6+7

    30,000

    18:00

    10+11+5+6+7

    30,000

    24:00

    Volume

    tCur

    Step 1 (50%)

    Volume

    tCur

    Step 2 (25%)

    Volume

    tCur

    Step 3 (25%)

    1,000

    05:05

    1,500

    07:41

    2,000

    11:20

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    1,000

    05:05

    12.00

    500

    16:41

    1,000

    30.45

    03:45

    500

    05:13

    1,000

    09:37

    10

    10:00

    10:00

    10:00

    11

    5.00

    5.00

    5.00

    Route

    Volume

    tCur

    Step 1 (50%)

    Volume

    tCur

    Step 2 (25%)

    Volume

    tCur

    Step 3 (25%)

    20:50

    500

    29:35

    1,000

    51:42

    1,000

    30:30

    1,000

    33:06

    1,000

    36:45

    3
    0
    30:15
    0
    30:15
    0
    Table 126: Example of incremental assignment (BPR function a=1, b=2, R=tCur)

    6.11.2

    30:15

    The procedure of incremental assignment


    illustration 95 depicts the procedure of incremental assignment.

    338

    PTVGROUP

    6.11.3 Input and output attributes of incremental assignment

    Illustration 95: The procedure of incremental assignment

    6.11.3

    Input and output attributes of incremental assignment


    To execute the incremental assignment, certain entries have to be made. After calculation, the
    results are available in the output attributes and can be displayed in the list view (see User
    Manual: Chpt. 24.1 , page 2299) or in the network editor (see User Manual: Chpt. 24.2 , page
    2337). table 127 provides an overview of the input attributes that must be maintained. table
    128 lists the output attributes to which the procedure results are saved.

    PTVGROUP

    339

    6.11.3 Input and output attributes of incremental assignment

    Table 127: Input attributes for incremental assignment


    The abbreviations represent the following:

    340

    PTVGROUP

    6.11.4 Evaluation of incremental assignment


    x1

    The toll by PrTSys has to be inserted manually in the impedance function

    (X)

    Can be used optionally

    (*)

    Apart from the parameters which are directly set in the assignment
    procedure

    Table 128: Output attributes of incremental assignment

    6.11.4

    Evaluation of incremental assignment


    Lohse (1997) lists the following decisive disadvantages of the incremental assignment procedure.
    The number and the size of layers (partial matrices) mainly decide on the goodness of the
    results. However, there is no procedure to specify optimal layers.
    The calculation ends after the specified number of steps has been executed without
    checking correspondence between the resulting traffic volume and link impedances.

    PTVGROUP

    341

    6.12 Equilibrium assignment

    6.12

    Equilibrium assignment
    The Equilibrium assignment distributes the demand according to Wardrop's first principle.
    "Every road user selects his route in such a way, that the impedance on all alternative routes is
    the same, and that switching to a different route would increase personal travel time (user optimum)."
    This behavioral hypothesis underlies the unrealistic assumption that every road user is fully
    informed about the network state. In transport planning this hypothesis is approved of given a
    fundamental methodical advantage of the equilibrium assignment - with quite general requirements, the existence and uniqueness of the assignment result (expressed in volumes of the
    network object) is guaranteed. Moreover, measures for the distance of an approximation solution from the equilibrium exist, from which an objective termination criterion can be derived for
    the procedure, which generally is an iterative problem solution.
    The equilibrium assignment determines a user optimum which differs from a system optimum,
    as shown in table 129 and table 130.
    A user optimum means that the same impedance results for all routes of a traffic relation
    between zones i and j (within the scope of calculation accuracy). This results directly from
    the condition, that changing to another route is not profitable for any road user (table 129).
    A system optimum, however, means that the total impedance in the network, which is the
    product of route impedance and route volume, is minimized for all OD pairs. On average,
    this procedure leads to shorter journey times per road user, but there are (few) road users
    which use routes to serve the general public, with an impedance above average (table
    130).
    Route

    Links

    Volume

    tCur [min]

    Volume tCur

    1
    2

    1+8+9

    736

    38:19

    470:05:53

    1+2+3+5+6+7

    995

    38:21

    636:01:21

    10+11+5+6+7

    269

    38:20

    171:50:02

    Total
    2,000
    Table 129: Calculation of the user optimum for the example network

    Route

    Links

    Volume

    tCur [min]

    Volume tCur

    1+8+9

    734

    37:43

    461:46:27

    1+2+3+5+6+7

    919

    37:13

    569:58:45

    10+11+5+6+7

    347

    41:13

    238:11:24

    Total
    2,000
    Table 130: Calculation of the system optimum for the example network

    6.12.1

    1277:57:17

    1269:56:36

    Evaluation of the equilibrium assignment


    Because the procedure only terminates when all routes of any OD pair are in the balanced state, the procedure provides more realistic results than the incremental procedure.

    342

    PTVGROUP

    6.12.2 Introductory example of equilibrium assignment


    For a lower volume/capacity ratio, 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 Equilibrium_Lohse procedure.
    The computation time required by the equilibrium assignment depends on the volume/capacity ratio in the network. Because new routes are found in every iteration step for
    a strongly saturated network, more computation time is required in this case.
    Compared to stochastic assignment procedures (see "Stochastic assignment" on page
    385 and "Dynamic stochastic assignment" on page 439), equilibrium assignment provides
    distinct network volumes. Compared to the number of calculated iterations, the gap is a
    more objective termination criterion.

    6.12.2

    Introductory example of equilibrium assignment


    The effectiveness of the equilibrium assignment is described in the example in table 131 und
    illustration 96. The example analyzes the relation between traffic zone "village A" and traffic
    zone "city X".
    The total impedance of a route, for the sake of simplicity, results from the sum of link impedances of the route (see "Impact models" on page 220). Impedances for connectors and turns
    are not considered in the route search. In detail, the following assumptions apply:
    The impedance of the links is determined from the current travel time tCur. The current travel time tCur is in turn calculated using the capacity restraint function BPR with a=1, b=2
    and c=1.
    The access and egress times for the connectors are not considered, that is, they are set to
    0 minutes.
    Turn penalties are not considered.
    With regard to the traffic demand the following applies.
    The traffic demand between A-Village and X-City is 2,000 car trips during peak hour.
    Capacity and demand refer to one hour.
    The example network contains three routes which connect village A and city X.
    Route 1 via nodes 10 11 41 40
    Route 2 via nodes 10 11 20 21 30 31 40
    Route 3 via nodes 10 12 21 30 31 40
    Route 1 mainly 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 long is an alternative route which only makes sense if the federal
    road is congested.

    PTVGROUP

    343

    6.12.2 Introductory example of equilibrium assignment

    Illustration 96: Example network for equilibrium assignment


    LinkN- From
    o
    Node

    To Node

    Type

    Length
    [m]

    Capacity [car
    units/h]

    v0-PrT
    [km/h]

    10

    11

    20 Federal
    road

    5,000

    1,200

    100

    11

    20

    20 Federal
    road

    5,000

    1,200

    100

    20

    21

    20 Federal
    road

    5,000

    1,200

    100

    20

    40

    90 Rail track

    10,000

    21

    30

    20 Federal
    road

    5,000

    1,200

    100

    30

    31

    20 Federal
    road

    5,000

    1,200

    100

    31

    40

    20 Federal
    road

    5,000

    1,200

    100

    11

    41

    30 Country
    road

    16,000

    800

    80

    40

    41

    30 Country
    road

    5,000

    800

    80

    10

    10

    12

    40 Other roads

    10,000

    500

    60

    11

    12

    21

    40 Other roads

    5,000

    500

    60

    Table 131: Example network for equilibrium assignment


    As a result, the assignment provides values of table 132 for the three routes (PrT paths).

    344

    PTVGROUP

    6.12.3 Input and output attributes of equilibrium assignment


    Route

    tCur

    Impedance

    Volume(AP)

    46min
    39s

    2,798

    1,157.488

    46min 34s

    2,794

    618.079

    3
    46min 12s
    2,772
    Table 132: Assignment results for the three PrT paths

    224.432

    The most important assignment results for links are displayed in table 133.
    Lin- tCur
    k

    Impedance

    Volume
    (AP)

    Saturation PrT VehicleHr


    (AP)
    (tCur)

    VehKmTravelled PrT

    11min
    40s

    700

    1,908

    170

    370h 54min
    19s

    9,537.839

    5min
    47s

    347

    1,157

    96

    111h 43min
    15s

    5,787.442

    5min
    47s

    347

    1,157

    96

    111h 43min
    15s

    5,787.442

    7min
    48s

    468

    1,450

    126

    188h 29min
    38s

    7,249.603

    7min
    48s

    468

    1,450

    126

    188h 29min
    38s

    7,249.603

    7min
    48s

    468

    1,450

    126

    188h 29min
    38s

    7,249.603

    26min
    35s

    1,595

    750

    110

    332h 23min
    38s

    12,001.270

    8min
    19s

    499

    750

    110

    103h 52min
    23s

    3,750.397

    10

    15min
    12s

    912

    292

    72

    74h 3min 56s

    2,924.321

    11

    7min
    36s

    456

    292

    72

    37h 1min 58s

    1,462.161

    Table 133: Assignment result at the links

    6.12.3

    Input and output attributes of equilibrium assignment


    To execute the equilibrium assignment, certain entries have to be made. After calculation, the
    results are available in the output attributes and can be displayed in the list view (see User
    Manual: Chpt. 24.1 , page 2299) or in the network editor (see User Manual: Chpt. 24.2 , page
    2337). table 134 provides an overview of the input attributes that must be maintained. table
    135 lists the output attributes to which the procedure results are saved.

    PTVGROUP

    345

    6.12.3 Input and output attributes of equilibrium assignment

    Table 134: Input attributes of equilibrium assignment


    The abbreviations represent the following:

    346

    x1

    Toll PrTSys has to be inserted manually in the impedance function

    Generally possible, however not recommended

    (*)

    Apart from the parameters which are directly set in the assignment
    procedure

    PTVGROUP

    6.12.4 The procedure of equilibrium assignment


    Table 135: Output attributes of equilibrium assignment
    If you use metric units, enter the long lengths for kilometers and speeds in km/h. For imperial
    units enter the long lengths in miles and speeds in mph.

    6.12.4

    The procedure of equilibrium assignment


    The equilibrium state calculation can be formulated as an optimization problem with a convex
    objective function and linear secondary conditions.

    The following applies:


    E

    the set of all edges in a network and a one of these edges

    qa

    volume of object a

    Ra(x)

    the impedance of object a with volume x (monotonically increasing in x)

    qij

    the total demand (number of trips) from zone i to zone j

    qijr

    volume of route r from zone i to zone j

    Pijr

    route r from zone i to zone j

    E+u

    the set of the incoming edges at node u

    E-u

    the set of the outgoing edges at node u

    Du

    destination traffic at node u

    Ou

    origin traffic at node u

    In Visum, edges are all links, turns and connectors, whereas nodes are zones and network
    nodes.
    The objective function shows that the sum of impedances of all edges is minimized. The secondary conditions indicate the following (from top to bottom).
    All path volumes have to be positive.
    The volumes of all paths from zone i to j have to add up from the total demand from i to j.

    PTVGROUP

    347

    6.12.4 The procedure of equilibrium assignment


    The volume of an edge results from the sum of volumes of all paths, which contain this
    edge.
    Flow conservation applies at each node. When a node corresponds with a zone, the difference between the volumes of all incoming edges and the volumes of all outgoing
    edges have to correspond exactly with the difference between the destination and origin
    traffic. There is no origin and destination traffic at network nodes, thus the difference must
    be zero.
    Due to the non-linear objective function, the optimization problem is not solved directly but iteratively. Because of the monotonicity of the impedance function, the minimum is reached, so
    that starting with a starting solution between the alternative paths, a movement i-j is shifted, so
    that the paths all have the same impedance.
    During equilibrium assignment, the steps shown in illustration 97 are made.

    Illustration 97: The procedure of equilibrium assignment


    Based on an assignment result from a previously calculated assignment or an incremental
    assignment (by default) as a starting solution, the state of balance is reached by multiple step
    iteration. In the inner iteration step, two routes of a relation are brought into a state of equilibrium 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 step checks if new routes with lower impedance can be found as a result of
    the current network state. If this is the case for at least one relation, another state of balance
    must be calculated.

    348

    PTVGROUP

    6.12.4 The procedure of equilibrium assignment


    The following termination condition applies. 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 external
    iteration step.
    The convergence criterion Gap can also be used as termination criterion.
    Network balancing
    The procedure of network balancing is depicted in illustration 98.

    Illustration 98: The procedure of network balancing for an OD pair during equilibrium assignment
    Termination criterion
    Visum cancels the iteration process for calculating the equilibrium, if one of the following conditions has been fulfilled:
    Network balancing has been achieved, this means a permitted deviation of impedances
    of the routes compared in pairs was reached or undercut.
    The specified number of external iterations was reached without a network balancing
    being reached (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).
    The convergence criterion Max. gap is reached or undercut.
    For equilibrium assignment with a blocking back model, the maximum deviation has been
    reached or undercut (see "Blocking back model" on page 314). The procedure is

    PTVGROUP

    349

    6.12.5 Calculation example for the equilibrium assignment


    cancelled if the congestion volume values and the congestion wait times of two external
    iterations deviate by the max. rel. difference or less.

    6.12.5

    Calculation example for the equilibrium assignment


    Route

    Volume

    tCur [min]

    Starting solution

    1,000

    51.42

    Routes 1 + 2 are known

    1,000

    36.45

    30.15

    Network balancing 0

    776

    41:54

    Routes 1 + 2

    1,224

    41:56

    33:22

    Iteration step 1: route search finds route 3


    Network balancing 1

    649

    36:25

    Routes 1 + 3

    1,224

    42:58

    127

    36:23

    Max. imp. route = 2, Min. imp. route = 3


    Network balancing 2

    649

    35:15

    Routes 2 + 3

    1,067

    40:17

    284

    40:15

    Max. imp. route = 2, Min. imp. route = 3


    Network balancing 3

    734

    38:09

    Routes 1 + 2

    982

    38:10

    277

    38:51

    Max. imp. route = 3, Min. imp. route = 1


    Network balancing 4

    741

    38:27

    Routes 1 + 3

    982

    38:07

    277

    38:31

    Max. imp. route = 3, Min. imp. route = 2


    Network balancing 5

    741

    38:30

    Routes 2 + 3

    990

    38:14

    269

    38:15

    Max. imp. route = 1, Min. imp. route = 2


    Network balancing 6

    736

    38:19

    Routes 1 + 2

    995

    38:21

    269

    38:20

    Table 136: Example equilibrium procedure (BPR function a=1, b=2)

    350

    PTVGROUP

    6.13 Linear User Cost Equilibrium (LUCE)


    table 136 shows how the equilibrium procedure works for the example network (see "Example
    network for PrT assignment procedures" on page 228). The volume determined with the incremental procedure is used here as the initial solution (see "Example of incremental assignment" on page 337). This starting solution encompasses two routes, each loaded with 1,000
    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 the routes 1 and 2 are changed in such way that the deviation of the two
    route impedances is below the specified deviation. With a volume of 776 respectively 1,224
    vehicles for routes 1 and route 2, this is guaranteed.
    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 one of both conditions applies:
    The absolute deviation between maximum and minimum impedance is smaller than 5
    seconds.
    The relative deviation between the maximum and minimum impedance is less than
    0.1%.
    Network balancing by pairs 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.

    6.13

    Linear User Cost Equilibrium (LUCE)


    Similarly to origin-based methods, the problem is partitioned by destinations in the LUCE procedure. The main idea is to seek at each node a user equilibrium for the local route choice of
    drivers directed toward the destination among the arcs of its forward star.. The travel alternatives that make up the local choice sets are the arcs that belong to the current bush. A bush
    is an acyclic sub-graph that connects each origin to the destination at hand. The cost functions
    associated to these alternatives express the average impendence to reach the destination
    linearized at the current flow pattern.
    The unique solutions to such local linear equilibria in terms of destination flows, recursively
    applied for each node of the bush in topological order, provide a descent direction with
    respect to the classical sum-integral objective function. The network loading is then performed
    through such splitting rates, thus avoiding explicit path enumeration.

    6.13.1

    Mathematical formulation and theoretical framework


    he transport network is represented through a directed graph G = (N, A), where N is the set of
    the nodes and A NN is the set of the arcs. In the graph, the nodes represent the zone

    PTVGROUP

    351

    6.13.1 Mathematical formulation and theoretical framework


    centroids and the road intersections (Visum network nodes), while the arcs represent the links
    and the connectors. When turns with impendence or restrictions are introduced in the network
    model, then the node is properly exploded, so that such turns are associated to specific or no
    arcs of the graph.
    We adopt the following notation:
    fij

    Total flow on arc ijA, generic element of the (|A|1) vector f

    cij

    Cost of arc ijA, generic element of the (|A|1) vector c

    cij(fij)

    Cost function of arc ijA

    ZN

    Set of the zone centroids

    Dod

    Demand flow between origin oZand destinationdZ, generic element of the


    (|Z|21) vector D, that is the demand matrix in row major order

    Kid

    Set of the acyclic paths between node iN and destination d Z

    K
    ijk

    K = oZ dZ Kod is the set of paths available to road users


    ijk = 1, if arc ijA belongs to path k, and 0, otherwise for kK, this is the
    generic element of the (|A||K|) matrix

    odk

    odk is 1, if path kK connects origin oZ to destination dZ (i.e. kKod) and


    otherwise 0, the generic element of (|Z|2|K|) matrix

    Fk

    Flow on path kK, generic element of the (|K|1) vector F

    Ck

    The cost of path k for kK this is the generic element of the (|K|1) vector C

    Wi d

    Minimum cost to reach destination dZ from node iN

    Set of real numbers

    |S|

    Cardinality of the generic set S

    There are two fundamental relations between flow variables. The flow on arc ijA is the sum of
    the flows on the paths that include it:
    fij = kK ijk Fk
    The travel demand between origin oZ and destination d Z must be equal to the sum of the
    flows on the paths that connect them:
    kKod Fk = Dod
    Moreover, all path flows must satisfy non-negativity constraints.
    As usual, we assume additive path costs, i.e. the impendence C k associated by users to a
    given path k is the sum of the costs on the arcs that belong to it:
    Ck = ijA ijk cij

    352

    [6]

    PTVGROUP

    6.13.1 Mathematical formulation and theoretical framework


    By definition, the minimum cost to reach destination dZ from node iN is the cost of any shortest path that connects them:
    Wid = min{Ck : kKid}
    In this case, the traffic assignment problem can be formalized through the following program:

    [7]

    [8]

    where

    {f |A|: f = F, F} is the set of feasible arc flows

    {F |K|: F 0, F = D} is the set of feasible path flows

    To ensure the existence and uniqueness of the solution to problem [8] we assume that:
    cij(fij) is non-negative, continuous, strictly monotone increasing;
    Kod is non-empty;
    Dod is non-negative.
    Problem [8], which is convex, can also be expressed in terms of path flows as follows:

    [9]
    where, although the solution uniqueness does not hold anymore, the convexity of the
    mathematical program is preserved, implying that any descent algorithm in the space of path
    flows will provide one of the global solutions, which then make up a convex set.
    The relevance of equation [9] for traffic assignment is due to the fact that in the case of additive
    path costs, its first order (necessary) conditions coincide with the following formulation of the
    deterministic user equilibrium based on Wardrop's Principles, for each oZ and dZ:
    Fk (Ck - Wod) = 0, kKod
    Ck Wod, kKod
    Fk 0, kKod
    kKod Fk = Dod
    Based on [10.1] to [10.4]

    [10.1]
    [10.2]
    [10.3]
    [10.4]

    all used paths (Fk > 0) incur the minimum costs (Ck = Wod);
    any unused path(Fk = 0) does not incur lower costs (Ck Wod).

    PTVGROUP

    353

    6.13.2 Local user equilibrium


    A user equilibrium is obtained, if conditions [10.1] to [10.4] hold jointly for each OD couple,
    while considering that each path cost C k is a function (potentially) of all the path flows F
    through the arc cost function:
    Ck = ijA ijk cij( kK ijk Fk), in short C = T c(F)
    Since the gradient of (F) C = T c(F) , for X F, by linearizing the objective function
    of problem [9], at a given point F, we obtain:

    [11]

    (X) = (F) + CT(X-F) + o(||X-F||).


    [12]

    From equation [12] we can see that a direction E-F is descent if:
    CT(E-F) < 0.

    [13]
    In other words, to decrease the objective function and maintain feasibility we necessarily
    have to shift path flows getting a lower total cost with respect to the current cost pattern, i. e.
    move the current solution from F towards an E, so that CT E < CT F, where C = Tc( F).
    The necessity derives from the convexity of the problem, since in this case at any point X with
    CT(X-F) > 0 we have: (X) > (F).
    This approach to determine a descent direction can be applied to each OD pair separately, to
    each destination, or to the whole network jointly. Based on the above general rule, setting the
    flow pattern E by means of an all-or-nothing assignment to shortest paths clearly provides a
    descent direction. If we adopt such a direction for all OD pairs of the network jointly, and apply
    along it a line search, we obtain the well known Frank-Wolfe algorithm. However, at equilibrium each OD pair typically uses several paths, implying that any descent direction that
    loads a single path is intrinsically myopic; in fact such algorithms tail badly.
    Once we obtain an admissible descent direction E-F, as is convex, we can move the current
    solution along segment F+ (E-F) and take a step (0,1] , so that the objective function of problem [9], defined as () = (F+ (E-F)), is sufficiently lower. Since is C1 and convex, and
    thus also , several methods are available to determine an that minimizes (). Visum uses
    an Armijo-similar search and determines the largest step = 0.5k for all non-negative integers
    k,, so that
    (0.5k)/ < 0.
    This method requires to compute the directional derivative of the objective function:

    [14]

    ( )/ = [c((F+ (E-F)))]T[(E-F)],
    [15]
    which implies to evaluate the arc costs at the candidate flows F+ (E-F) and then the difference between the corresponding total costs obtained with the flows E and F. If these total
    costs with E are lower than with F, then ()/ is negative, so that the optimal solution lies
    towards E, and vice versa.

    6.13.2

    Local user equilibrium


    In this section we present a new method to determine a descent direction, which is based on
    local shifts of flows that satisfy the total cost lowering rule and exploits the inexpensive information provided by the derivatives of the arc costs with respect to arc flows.

    354

    PTVGROUP

    6.13.2 Local user equilibrium


    To grasp the underlying idea, we can refer to the simplest network where one OD pair with
    demandD is connected by two arcs with cost function c 1(f1) and c 2(f2), respectively. At the current flow pattern f = (D /2, D /2) it is c1 < c 2 (see illustration 99 ),so that an all or nothing
    approach would lead to a descent direction (D, 0), which is far away from equilibrium f* (gray
    circle in the figure). The LUCE approach instead accounts for the first order approximations of
    the cost functions at the current flow pattern, i.e. ca + ca(f a)/fa (fa - fa) and determine a user
    equilibriume among these lines (white circle in the figure): This descent direction efficiently
    approaches equilibrium f*. In most cases, you can even use the maximum step size a=1.

    Illustration 99: Linear User Cost Equilibrium between two paths


    To reach a destination dZ, only shortest paths are used for the equilibrium. Given that the arc
    cost functions are strictly monotone increasing, they make up an acyclic [*1] sub-graph of G ,
    i.e. a (reverse) bush rooted at d. At strict monotonicity, any arc cost can be null only if its flow is
    such. However, in Visum links and connectors may have null impedance, producing twofold
    consequences: a) the corresponding arc cost functions loose strict monotonicity, so that uniqueness is not guaranteed anymore. b) The sub-graph made-up by arcs with positive destination flows at some of the possible equilibria may be cyclic. The implementation of LUCE in
    Visum specifically addresses this issue and converges to one among the possible equilibria
    by forcing an acyclic solution and equally splitting the flow among all alternatives with minimum cost in presence of uncongested sub-paths. This special case is not further dealt with
    below.
    On this base, when seeking a descent direction, in the following we will limit our attention to
    the current bush B(d) and introduce an updating mechanism to make sure that eventually any
    shortest path will be included into it; equilibrium is actually only attained this way. Let us focus
    on the local route choice at a generic node iN for road users directed to destination dZ.
    For the topology of the bush we will use the following notation:
    FSB(i, d) = {jN: ijB(d)} the forward star of node i N made-up by nodes that can be reached from it through arcs belonging to the current bush B(d) of
    destination d Z
    BSB(i, d) = {jN: ijB(d)} the backward star of node i N made-up by nodes that can reach

    PTVGROUP

    355

    6.13.2 Local user equilibrium


    it through arcs belonging to the current bush B(d) of destination
    d Z
    For the flow pattern we will use the following notation:
    fijd

    current flow on arc ijA directed to destination dZ


    By construction, the following applies: fijd = 0 for each jFSB(i, d);
    In addition, the following clearly applies : fij = d

    Z ij

    fid = jFSB(i, d) fijd current flow leaving node iN to destination dZ


    yijd

    yijd = fijd / fid current flow proportion on arc ijA directed to destination
    dZ, if fid>0, yijd = 0 else

    eijd

    descent direction, in terms of flow on arc ijA directed to destination


    dZ

    eid

    descent direction, in terms of flow leaving node iN directed to destination dZ

    eijd = eijd / eid

    descent direction, in terms of flow proportion on arc ijA directed to


    destination dZ

    For the cost pattern we will use the following notation:


    Ci d

    average cost to reach destination dZ from node iN

    gij

    Cost derivative of arc ijA

    Gi

    Derivative of the average cost to reach destination dZ from node iN

    The average cost Ci d is the expected impendence that a user encounters by travelling from
    node iN to destination dN. Here it is defined recursively based on the current flow pattern:
    If fid > 0, then Cid = jFSB(i, d) yijd (cij + Cjd), otherwise

    [16.1]

    Cid = min{cij + Cjd: jFSB(i, d)},


    as if drivers utilize paths accordingly with the current flow proportions. In the following
    we assume that the cost function cij(fij) is continuously differentiable for each arc ijA:

    [16.2]

    gij = cij(fij) / fij

    [17]
    Under the assumption that an infinitesimal increment of flow leaving node iN directed
    towards destination dZ would diverge accordingly with the current flow proportions, we have:
    If fid > 0, then Gid = Cid / fid = jFSB(i, d) yijd

    (gij + Gjd), otherwise

    Gid = jFSB(i, d) [Cid = cij + Cjd] (gij + Gjd) / jFSB(i, d) [Cid = cij + Cjd],

    356

    [18.1]
    [18.2]

    PTVGROUP

    6.13.2 Local user equilibrium


    Where the derivatives gij + Gjd are scaled by the shareyijd of f id utilizing arc ij and then passing through node j, that jointly with the flow proportion involved in the averaging yields the
    square yijd 2.
    The average costs and their derivatives can be computed by processing the nodes of the bush
    in reverse topological order according to d, starting fromCdd = Gdd = 0.
    We now address the local user equilibrium for the e i d drivers directed to destination d Z ,
    whose available alternatives are the arcs of the bush exiting from node iN. To each travel
    alternative we associate the cost function:
    vijd(eijd) = (cij + Cjd) + (gij + Gjd) (eijd - yijd eid),
    resulting from a linearization at the current flow pattern of the average cost encountered
    by a user choosing the generic arc ij, with jFSB(i, d).

    [19]

    Similar to [10.1] to [10.4], this problem can be expressed by the following system of inequalities:
    eijd [vijd(eijd) - Vid] = 0, jFSB(i, d),
    vijd(eijd) Vid, jFSB(i, d),
    eijd 0, jFSB(i, d),
    jFSB(i, d) eijd = eid,
    where we denote:
    Vid
    vij

    [20.1]
    [20.2]
    [20.3]
    [20.4]

    local equilibrium cost to reach destination dZ from node iN;

    Cost of the local alternative jFSB(i, d), to reach destination dZ from node iN
    via j .

    If e id = 0, the solution to the above problem is trivially: e ijd = 0, for each jFSB(i, d). Consider
    then the case where eid > 0. To improve readability, we rename the following in [20.1] to [20.4]:
    xj (aj + bj xj - v) = 0, jJ,
    aj + bj xj v, jJ,
    xj 0,jJ,

    [21.2]
    [21.3]

    j xj = 1,

    [21.4]

    where:
    J

    {(i, j, d): jFSB(i, d)}

    aj

    (cij + Cjd) - (gij + Gjd) eid yijd

    bj

    (gij + Gjd) eid

    xj

    eijd / eid

    Vid

    PTVGROUP

    [21.1]

    357

    6.13.3 Descent direction


    Applying the usual Beckmann approach, we can reformulate the equilibrium problem [21.1] to
    [21.4] as the following quadratic program:
    min{

    j J 0

    xj (a

    + b x) dx: x X} = min{
    j

    a xj + 0.5 bj xj2: x X},

    j J j

    [22]
    where X is the convex set of all vectors satisfying the feasibility conditions [21.3] and
    [21.4]. The gradient of the objective function is a vector with generic entry a j + bj xj, and then
    the Hessian of the objective function is a diagonal matrix with generic entry bj. Therefore, if all
    entries bj are strictly positive, the Hessian is positive definite and problem [22] has a unique
    solution. In order to ensure such a desirable property we assume without loss of generality
    that the derivates gij are strictly positive for all arcs ijA. Since the arc cost functions are strictly
    monotone increasing, g ij can be zero only if also fijd is zero. Therefore, at the equilibrium bj =
    0 implies xj = 0. In practice we will substitute any gij = 0 with a small .
    To solve problem [21.1] to [21.4], we suggest using the following simple method. In order to
    satisfy condition [21.1], it is either xj = 0 (and in this case the condition requires [21.2] aj v),
    or it isaj + bj xj = v. Let J0 J be the set of alternatives with zero flow, that is J0 = {jJ: xj = 0}.
    For any given J 0 the solution is immediate, since from [21.4]it is j (v - a ) / b = 1; therefore
    J
    j
    j
    we have:
    v = (1 + jJ\J0 aj / bj) / ( jJ\J0 1 / bj),
    xj = (v - aj) / bj, jJ\J0,
    xj = 0, jJ0.

    [23.1]
    [23.2]

    [23.3]
    The flow proportions provided by [23.1] to [23.3] implicitly satisfy [21.4]. But to state that
    the chosen J0 yields the solution of problem [21.1] to [21.4], we must still ensure that the following conditions are kept: aj < v, for eachjJ\J0 (as required by [21.3], since xj = (v - aj) / bj >
    0), and aj v, for each jJ0 (as required by [21.2], since xj = 0). This implies that for the solution of value v, resulting from [23.1], set J is divided into two sub-sets: the set J0 , made up by
    alternatives j , so that aj v; and its complement J\J0, made up by the alternatives j, so that aj <
    v.
    At a first glance the problem to determine the set J0 of alternatives with zero flow may seem to
    be combinatorial. However, this is not the case. The equation [23.1] can be rewritten as a recursive formula. It then shows the effect of removing an alternative k from the set J0:
    v[J0\{k}] = (v[J0] jJ\J0 1 / bj + ak / bk) / ( jJ\J0 1 / bj + 1 / bk) .

    [24]
    The right-hand side of [24] can be interpreted as an average between v[J0] and ak, with the
    positive weights j J\J0 1 / b j und 1 / b k . Therefore, the local equilibrium cost increases by
    removing from J0 any alternative kJ\J 0, for which ak is higher than the current value v[J0]. Vice
    versa it decreases by adding such alternatives to J0 . Consequently, the correct partition set J0
    can be simply obtained by adding iteratively to an initially empty set each alternative jJ\J0 so
    that aj > v, i.e. each alternative for which [23.2] yields a negative flow proportion.

    6.13.3

    Descent direction
    To obtain a complete pattern of arc flows ed for a destination dZ consistent with the local user
    equilibrium, we simply have to solve problem [20.1] to [20.4] at each node i N\{d}, proceeding

    358

    PTVGROUP

    6.13.3 Descent direction


    in topological order, where the node flow is computed as follows:
    eid = jBSB(i, d) ejid + Did

    [25]
    We have shown that a given direction is descent if [13] only applies (see "Mathematical formulation and theoretical framework" on page 351). In terms of arc flows directed to destination
    dZ, the following applies:
    ijA cij (eijd - fijd) < 0,

    [26]
    expressing that the shift of flow from f d to e d must entail a decrease of total cost with
    respect to the current cost pattern. The proof that the proposed procedure provides a descent
    direction goes beyond the scope of this description. For more detailed information, please
    refer to Gentile G., 2009.
    In the following we present an example showing the computation of the descent direction provided by the LUCE algorithm. We consider the graph of the Braess paradox, with 4 nodes and
    5 arcs.

    Illustration 100: Numerical example of the procedure of how to obtain the descent direction
    The arc cost function is cij = Tij + Qij fij2, so that its derivative is gij = 2 Qij fij.
    There is only one destination d = 4, and two origins with travel demand D 14 = 9 and D24 = 2.
    We consider an initial flow pattern where all available paths, the 3 routes from 1 to 4 and the 2
    routes from 2 to 4, are equally used by each OD pair. In this case it is fij = f ijd and the bush is
    the entire network.
    After evaluating the current flow pattern, the arc costs, and their derivatives, we can compute
    for each node i the average cost Ci d and its derivative G id , iteratively starting from the destination, where Cd d = G d d = 0, and proceeding in reverse topological order. To this aim we
    apply the formulas:
    Cid = jFSB(i, d) yijd (cij + Cjd), Gid = jFSB(i, d) yijd2 (gij+ Gjd).
    While the computation for node 3 is trivial, since its forward star is a singleton, for node 2 we
    have:
    C24 = y234 (c23 + C34) + y244 (c24 + C44) = 0.5 (21 + 52) + 0.5 (42 + 0) = 57.5,
    PTVGROUP

    359

    6.13.3 Descent direction


    G24 = y234 2 (g23 + G34) + y244 2 (g24 + G44) = 0.52 (8 + 14) + 0.52 (16 + 0) = 9.5,
    and for node 1 it is:
    C34 = y134 (c13 + C34) + y124 (c12 + C24) = 0.33 (29 + 52) + 0.66(41 + 57.5) = 92.7,
    G34 = y134 2 (g13 + G34) + y124 2 (g12 + G24) = 0.332(12 + 14) + 0.662(12 + 9.5) = 12.4.

    Illustration 101: Numerical example of the procedure of how to obtain the descent direction
    Now we can compute for each node i the node flows eid and the arc flows eijd iteratively by proceeding in topological order.
    To this aim we shall focus on the local route choice of the e i d users, whose available alternatives are the arcs of the bush exiting from node i. To each travel alternative we associate the
    cost function:
    vij(eijd) = (cij + Cjd) + (gij + Gjd) (eijd - yijd eid),
    resulting from a linearization at the current flow pattern of the average cost encountered by a
    user choosing arc ij, and we look for an equilibrium. We have shown that the latter can be
    determined using the following formulas:
    Vid = (1 + j a d / b d) / ( 1 / b d), e d = e d (V d - a d) / b d,
    J ij
    ij
    j J
    ij
    ij
    i
    i
    ij
    ij
    whereby: aijd = (cij + Cjd) - (gij + Gjd ) eid yijd, bijd = (gij + Gjd) eid. J is set initially to the forward
    star FSB(i, d); if some eijd results to be negative, then it is set to zero, j is removed from J and the
    computation is repeated.
    We start with node 1, whose node flow is e14 = D14 = 6:
    a134 = (c13 + C34) - (g13 + G34) e14 y134 = (29 + 52) - (12 + 14) 9 0.33 = 3,
    a124 = (c12 + C24) - (g12 + G24) e14 y124 = (41 + 57.5) - (12 + 9.5) 9 0.66 = -30,5,
    b134 = (g13 + G34) e14 = (29 + 14) 9 = 387.
    b124 = (g12 + G24) e14 = (41 + 9.5) 9 = 454.5,
    V14 = (1 + a134/b134 + a124/b124) / (1/b134 +1/b124) = (1+ 3/387-30.5/454.5) / (1/387+1/454.5) = 196.6,
    e134 = e14 (V14 - a134) / b134 = 9 (196.6 - 3) / 387 = 4.5,
    360

    PTVGROUP

    6.13.4 Assignment algorithm


    e124 = e14 (V14 - a124) / b124 = 9 (196.6 + 30.5) / 454.5 = 4.5.
    We continue with node 2, whose node flow ist e24=e124 + D24= 4,50 + 2 = 6,5 ist:
    a234 = (c23 + C34) - (g23 + G34) e24 y234 = (21 + 52) - (8 + 14) 6.5 0.5 = 1.5,
    a244 = (c24 + C44) - (g24 + G44) e24 y244 = (42 + 0) - (16 + 0) 6.5 0.5 = -10,
    b234 = (g23 + G34) e14 = (8 + 14) 6.5 = 143,
    b244 = (g24 + G44) e14 = (16 + 0) 6.5 = 104,
    V24 = (1 + a234/b234 + a244/b244) / (1/b234 +1/b244) = (1 +1.5/143 -10/104) / (1/143+1/104) = 55.1,
    e234 = e24 (V24 - a234) / b234 = 6.5 (55.1 - 1.5) / 143 = 2.43,
    e244 = e24 (V24 - a244) / b244 = 6.5 (55.1 + 10) / 104 = 4.07.
    We finally look at node 3, whose node volume e34=e134+e234+D34= 4,5 + 2,43 + 0 = 6,93 is:
    Since there is only one alternative, the following applies: e 344=e34 = 6 ,93. We compute V3 4 for
    completeness only:
    V34 = (c34 + C44) + (g34 + G44) (e344 - e34 y344) = (52 + 0) + (14 + 0) (6.55 - 6.93 1) = 46.7.
    The flow pattern we have just found is a descent direction because we have:
    ijA fijd cij = 949 > ijA eijd cij = 897.
    The illustration 100 represents the AON assignment to shortest paths (marked by *). illustration
    101 depicts the equilibrium flow and cost pattern (marked by *). It can be seen that one single
    iteration of the proposed descent direction allows a substantial step towards the solution.

    6.13.4

    Assignment algorithm
    Below we provide a pseudo code of the procedure within the framework of an assignment
    algorithm.
    function LUCE
    f = 0

    initialize the solution flows to zero

    for k = 1 to n

    perform n iterations

    for each dZ

    for each destination d

    for each ij A

    compute arc costs and their derivatives

    c = cij(fij)

    ij

    gij = max{cij(fij)/fij, }
    if fid > 0 then yijd = fijd / fid else yijd = 0
    B(d) =B(B(d), c, f)
    Cdd = 0

    initialize or modify the current bush


    the average cost of the destination is zero

    Gdd = 0

    so its derivative

    for each i:ijB(d) in reverse topological order

    for each node i d in the bush

    if fid > 0 then


    Cid = j

    y d
    FSB(i, d) ij

    PTVGROUP

    (cij + Cjd)

    compute the node average cost to d

    361

    6.13.4 Assignment algorithm


    Gid = j

    y d2
    FSB(i, d) ij

    (gij + Gjd)

    and its derivative

    else
    Cid = min{cij + Cjd: j FSB(i, d)}
    Gid= j

    FSB(i, d)

    ed

    [Cid = cij + Cjd] (gij + Gjd) / j

    [Cid = cij + Cjd],

    reset the arc and node flows to d

    = 0

    for each oZ
    eod

    FSB(i, d)

    load on the origins the demand to d

    = Dod

    for each i:ijB(d) in topological order


    J = FSB(i, d)

    for each node i d in the bush

    initialize the set of arcs with positive flow

    = 0
    until = 1 do

    =1
    V id = [eid + j

    (cij + Cjd) / (gij + Gjd) - eidyijd] / j

    1/(gij + Gjd)

    for each jJ
    eijd = V id / (gij + Gjd) - (cij + Cjd) / (gij + Gjd) + eidyijd
    if eijd < 0 then
    eijd = 0
    J = J \ {j}

    =0

    remove ij from the set of arcs with positive flow


    then repeat the procedure

    for each jJ
    ejd = ejd + eijd

    propagate the arc flows to the head node flows

    = 1
    if k > 1 then
    until ij

    c (fij + (eijd - fijd)) (eijd - fijd) < 0 do = 0.5

    A ij

    for each ijA

    armijo step

    update arc flows

    fij = fij + (eijd - fijd)

    fijd = fijd + (eijd - fijd)

    The bush of each destination d Z is initialized with the set of efficient arcs that bring closer to
    the destination, whereby the minimum costs are evaluated at zero flow. At the generic iteration, any non-efficient arc on the bush carrying no destination flow is removed from it, while
    any arc that would improve shortest paths on the bush is added to it, if its reverse arc does not
    carry destination flow. If the resulting sub-graph is acyclic, then it is substituted to the current
    bush of that destination. Since the LUCE algorithm tends to an equilibrium on the bush, eventually the flow on non-efficient paths disappears and the bush can be properly modified.
    Note that, beside the initialization of the bushes, the LUCE algorithm does not require shortest
    path computations, but only simple visits of the bushes.

    362

    PTVGROUP

    6.13.5 Input and output attributes of equilibrium assignment (LUCE)

    6.13.5

    Input and output attributes of equilibrium assignment (LUCE)


    For equilibrium assignment (LUCE), the same input attributes are required as for equilibrium
    assignment (table 134).
    After calculation, the results are available in the output attributes and can be displayed in the
    list view (see User Manual: Chpt. 24.1 , page 2299) or in the network editor (see User Manual:
    Chpt. 24.2 , page 2337).
    Tip: This hint might help to reduce the LUCE run time by means of specific network modeling. Internally, LUCE has to explode a node to generate several sub-nodes and connecting links between these sub-nodes, if the turns via the node have different impedances
    of if some of these turns are not open. Due to this, the graph on which the procedure
    works will be extended which again means an increase in the run time. If you do not want
    to model the turns explicitly in your network model, make sure that also the U-turns are
    permissible for all private transport systems. Otherwise, Visum has to explode all nodes
    because of the blocked U-turns. In Visum, all turns, including u-turns, are opened by
    default. If your network contains closed u-turns, open them if there is no specific reason
    for keeping them closed. To recalculate the transport system set at turns and main turns,
    refer to (see User Manual: Chpt. 15.13.6.4 , page 1096) and (see User Manual: Chpt.
    15.20.6.4 , page 1192). This will not have any negative effect on the created routes, since
    U-turns are never included in loaded routes as long as none of the turns has been modeled explicitly.

    6.13.6

    Persistent storage of bushes


    For each demand segment, the routes and route volumes are stored as bushes in the version
    file.
    Bushes are regarded for the following operations on paths:
    Skim matrix (also for a freely definable skim) in case of route-based assignments:
    for the Minimumweight, always the shortest path is used for calculation
    for the Mean over route volumesweight, the shortest path is used only if the OD pair
    is not in the bush; otherwise, the skim data is weighted with the volumes of the edges
    from the origin to the destinations.
    Flow bundle
    TFlowFuzzy
    COM: TFlowMatrix
    OD pair filter
    Blocking back
    Generate demand matrix from paths
    Furthermore, they are regarded for the following operations:
    Paths list output
    Draw paths
    COM (Paths interface)
    Route export
    Subnetwork generation

    PTVGROUP

    363

    6.13.7 Start from an initial assignment


    ANM export
    Demand matrix calibration
    Optimization of the signal timing coordination
    The following operations cannot be applied to LUCE paths:
    Conversion into PrT paths or vice versa
    Changes to the course or the volume of a path
    Route import

    6.13.7

    Start from an initial assignment


    Like other PrT assignment methods, also LUCE can use an existing assignment result as
    initial solution to save computation time during the next run if supply and demand had changed only slightly. Prerequisite: The existing assignment needs to be a LUCE result and the
    path information (bushes) must have been stored. Different PrT assignments cannot start with
    a LUCE result as initial solution and vice versa.

    6.13.8

    Optimizing the proportionality in the route distribution


    According to Wardrop's equilibrium condition the link volumes are determined explicitly, but
    the path volumes are not necessarily. This is clearly illustrated in the example in illustration
    102.

    Illustration 102: Example for the proportionality with balanced link volumes
    The zones 1 and 2 are connected to node A, the zones 3 and 4 are connected to node B. A
    and B are connected by the two links x and y, which have the same VDF. Demand is 500 trips
    each from 1 to 3 and from 1 to 4. The image shows the resulting link volumes in the balanced
    state. But the link volumes can result from the various route volumes overlaying on the links.
    Three of them are listed in the table:
    Volume

    Variant 1

    Variant 2

    Variant 3

    1-x-3

    200

    500

    250

    1-y-3

    300

    250

    1-x-4

    300

    250

    1-y-4
    200
    500
    250
    Table 137: Variants of route volumes for the link volumes in illustration 102

    364

    PTVGROUP

    6.13.8 Optimizing the proportionality in the route distribution


    illustration 102

    With regard to the impedance balance, all variants are equivalent, though variant 3 has the
    advantage that the route distribution at node A is proportional for the relations to the zones 3
    and 4. Since the links x and y have the same impedance one cannot assume that at node A
    road users on their way to the destination x will not distribute to the links in the same way as
    those heading to destination y.
    Due to the separate handling of the OD pairs, the path-based equilibrium procedure could
    generate any of the indefinite number of path volume variants arbitrarily, whereas LUCE
    always charges the paths proportionally as shown in variant 3. But this advantage is based on
    the fact, that LUCE simultaneously balances all path volumes to an origin zone. Identical turn
    proportions can therefore be generated within an origin zone only, they are not reached for the
    routes of various origin zones.
    This is illustrated by the extended example in illustration 103 , now with 500 trips each between zones 2 and 3, and 2 and 4. Again, the image shows balanced link volumes.

    Illustration 103: Extended example for the proportionality with balanced link volumes
    Even though the route distributions to the paths within an origin zone show consistent shares,
    this does not apply to the paths of different origin zones. Again various volume variants can be
    generated:
    Volume

    Variant 1

    Variant 2

    Variant 3

    1-x-3

    200

    500

    250

    1-y-3

    300

    250

    1-x-4

    200

    500

    250

    1-y-4

    300

    250

    2-x-3

    300

    250

    2-y-3

    200

    500

    250

    2-x-4

    300

    250

    2-y-4
    200
    500
    250
    Table 138: Variants of route volumes for the link volumes in illustration 103
    For the same reason as above, variant 3 is the preferable variant, since there is no need for
    unequal loading of the routes. However, this balancing procedure cannot be performed in a
    PTVGROUP

    365

    6.14 Equilibrium_Lohse
    purely origin-based way. LUCE provides the option to harmonize the path volumes over all origin zones subsequently to the determination of meshes of the same impedance (compare
    mesh A-B in the example) which is based on the paths that were calculated during the actual
    assignment. This is always the case, since in an isolated view the mesh is in a balanced state;
    thus, volumes can be shifted between the path alternatives from different origin zones without
    any changes to the link volumes or impedances. Thus, the equilibrium state can be retained.
    Since mesh finding and route choice optimization are time-consuming this procedure is provided as an option which can additionally be activated in the LUCE procedure parameters. For
    the reliable detection of balanced meshes the assignment should have finished with a gap of
    10-6 or better. In this case, the optimization of the route distribution will additionally take another 20% - 50% of the assignment run time.
    The optimization of the route distribution is highly recommended if route volumes shall be analyzed or used in further computations. This applies to the following operations:
    Matrix estimation though TFlowFuzzy
    Flow bundles (especially flow matrix analyses)
    Blocking back model
    But if primarily link-related assignment results are required (volumes, travel times), then optimization is not required, since this would not improve the given results.

    6.14

    Equilibrium_Lohse
    The Equilibrium_ Lohse procedure was developed by professor Lohse and is described in
    Schnabel (1997). This procedure models the learning process of road users using the network. Starting with an "all or nothing assignment", drivers consecutively include information
    gained during their last journey for the next 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. 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 (like 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 n is based on the impedances calculated at n-1.
    The assignment of the demand 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 behavior 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 actual travel time of n (calculated
    from the VD functions) and the estimated travel time of n. This difference is then multiplied by
    the value DELTA (0.15...0.5) which results in an attenuated sine wave.

    366

    PTVGROUP

    6.14.1 Example of the Equilibrium_Lohse procedure


    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.

    6.14.1

    Example of the Equilibrium_Lohse procedure


    The Equilibrium_Lohse procedure is demonstrated below with a calculation example. table
    139 shows the parameter settings of Equilibrium_Lohse and the impedance for links and routes in the unloaded network. table 140, table 141 , and table 142 show three iterations of the
    calculation process.
    LinkNo Type

    Length [m]

    v0 [km/h]

    Capacity [car units] R0* [min]

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    20

    5,000

    100

    1,200

    3.00

    30

    16,000

    80

    800

    12:00

    30

    5,000

    80

    800

    03:45

    10

    40

    10,000

    60

    500

    10:00

    11
    40
    5,000
    60
    500
    05:00
    Table 139: Impedance in unloaded network, input parameters of Equilibrium_Lohse procedure

    Route

    Links

    Length [m]

    R0* [min]

    1+8+9

    26,000

    0:18:45

    1+2+3+5+6+7

    30,000

    0.18

    10+11+5+6+7

    30,000

    0:24:00

    Input parameters:
    BPR function with a = 1, b = 2, c = 1
    LowerLimit = 0.15
    UpperLimit = 0.5
    V1 = 2.5
    V2 = 4
    V3 = 0.002

    PTVGROUP

    367

    6.14.1 Example of the Equilibrium_Lohse procedure


    LinkN- Volume 1 [car
    o
    units]

    R1 [min]

    TT1

    f(TT1)

    Delta 1

    R1* [min]

    2,000

    11:20

    2.78

    0.0452

    0.4796

    07:00

    2,000

    11:20

    2.78

    0.0452

    0.4796

    07:00

    2,000

    11:20

    2.78

    0.0452

    0.4796

    07:00

    2,000

    11:20

    2.78

    0.0452

    0.4796

    07:00

    2,000

    11:20

    2.78

    0.0452

    0.4796

    07:00

    2,000

    11:20

    2.78

    0.0452

    0.4796

    07:00

    12:00

    0.00

    0.0450

    0.5000

    12:00

    03:45

    0.00

    0.0450

    0.5000

    03:45

    10

    10:00

    0.00

    0.0450

    0.5000

    10:00

    11

    05:00

    0.00

    0.0450

    0.5000

    05:00

    Route Volume 1

    R1

    R1 *

    0:27:05

    0:22:45

    2,000

    1:08:00

    0:41:59

    3
    0
    0:49:00
    Table 140: Example of Equilibrium_Lohse: 1st iteration step

    368

    0:35:59

    LinkN- Volume 2 [car


    o
    units]

    R2 [min]

    TT2

    f(TT2)

    Delta 2

    R2* [min]

    2,000

    11:20

    0.62

    0.0450

    0.4925

    09:08

    1,000

    05:05

    0.27

    0.0450

    0.4962

    06:03

    1,000

    05:05

    0.27

    0.0450

    0.4962

    06:03

    1,000

    05:05

    0.27

    0.0450

    0.4962

    06:03

    1,000

    05:05

    0.27

    0.0450

    0.4962

    06:03

    1,000

    05:05

    0.27

    0.0450

    0.4962

    06:03

    1,000

    30:45

    1.56

    0.0451

    0.4855

    21:06

    1,000

    09:37

    1.56

    0.0451

    0.4855

    06:36

    10

    10:00

    0.00

    0.0450

    0.5000

    10:00

    11

    05:00

    0.00

    0.0450

    0.5000

    05:00

    PTVGROUP

    6.14.1 Example of the Equilibrium_Lohse procedure


    Route Volume 2

    R2

    R2 *

    1,000

    0:51:42

    0:36:50

    1,000

    0:36:45

    0:39:22

    3
    0
    0:30:15
    Table 141: Example of Equilibrium_Lohse: 2nd iteration step

    0:33:08

    LinkN- Volume 3 [car


    o
    units]

    R3 [min]

    TT3

    f(TT3)

    Delta 3

    R3* [min]

    1,333

    06:42

    0.27

    0.0450

    0.4963

    07:56

    667

    03:56

    0.35

    0.0450

    0.4953

    05:00

    667

    03:56

    0.35

    0.0450

    0.4953

    05:00

    1,333

    06:42

    0.11

    0.0450

    0.4984

    06:22

    1,333

    06:42

    0.11

    0.0450

    0.4984

    06:22

    1,333

    06:42

    0.11

    0.0450

    0.4984

    06:22

    667

    20:20

    0.04

    0.0450

    0.4994

    20:43

    667

    06:21

    0.04

    0.0450

    0.4994

    06:28

    10

    667

    27:47

    1.78

    0.0451

    0.4842

    18:37

    11

    667

    13:53

    1.78

    0.0451

    0.4842

    09:18

    Route Volume 3

    R3

    R3 *

    667

    0:33:23

    0:35:07

    667

    0:34:40

    0:37:03

    3
    667
    1:01:47
    Table 142: Example of Equilibrium_Lohse: 3rd iteration step

    0:47:02

    table 139, table 140, table 141, and table 142 illustrate the first three iteration steps of the Equilibrium_Lohse procedure for the example network.
    Iteration step 1, n = 1
    Volume 1
    The volume of the first iteration step results from an "all or nothing" assignment onto the
    lowest impedance route in the unloaded network. For impedance R0*, this is route 2 loaded
    with 2,000 car trips.
    Current impedance R1
    The current impedance R1 of every link results from the BPR capacity function (a =1, b = 2,
    c= 1). For link 1, for example, the following can be calculated:
    R1 (link 1) = 3min x (1+(2000/1200)) = 11min 20s
    Estimated impedance R1*

    PTVGROUP

    369

    6.14.1 Example of the Equilibrium_Lohse procedure


    The estimated impedance R1* of every link consists of the current impedance R1 and the
    estimated impedance R0* of the last iteration step. The result is obtained via learning factor
    . To determine R1* for link 1, the following calculations are necessary:
    R0* = 3min = 180s
    R1 = 11min 20s = 680s
    TT1 = |R1 - R0*| /R0* = |680s - 180s| / 180s = 2.78

    R1* = R0* + 1 (R1 - R0*) = 180s + 0.4796 (680s - 180s) = 420s


    Iteration step 2, n = 2
    Volume 2
    The lowest impedance route for R1* is route 1. Now two routes exist, route 1 and 2. Each
    route is loaded with 1/n, i.e. the demand, so that each route is used by 1,000 cars.
    Current impedance R2
    The current impedance R2 of every link increases on newly loaded links 8 and 9, and it
    decreases on links 2, 3, 5, 6 and 7.
    Estimated impedance R2*
    The estimated impedance R2* of every link consists of the current impedance R2 and the
    estimated impedance R1* of the last iteration step.
    Iteration step 3, n = 3
    Volume 3
    The lowest impedance route for R2* is route 3. 2,000 car trips are now equally distributed
    across routes 1, 2 and 3.
    Current impedance R3
    The current impedance R3 again results from the current volume 3 via the VD function.
    Estimated impedance R3*
    The estimated impedance R3* of every link consists of the current impedance R3 and the
    estimated impedance R2* of the last iteration step.
    Iteration step 4, n = 4
    The concluding route search based on R3* determines route 1 as the shortest route. Thus, the
    following route volumes result:
    Volume route 1 = 2/4 2,000 = 1,000 trips
    Volume route 2 = 1/4 2,000 = 500 trips
    Volume route 3 = 1/4 2,000 = 500 trips

    370

    PTVGROUP

    6.14.2 Input and output attributes of the Equilibrium_Lohse procedure

    6.14.2

    Input and output attributes of the Equilibrium_Lohse procedure


    To execute the Equilibrium_Lohse procedure, certain entries must be made. After calculation,
    the results are available in the output attributes and can be displayed in the list view (see User
    Manual: Chpt. 24.1 , page 2299) or in the network editor (see User Manual: Chpt. 24.2 , page
    2337). table 143 provides an overview of the input attributes that must be maintained. table
    144 lists the output attributes to which the procedure results are saved.

    PTVGROUP

    371

    6.14.2 Input and output attributes of the Equilibrium_Lohse procedure

    Table 143: Input attributes of the Equilibrium_Lohse procedure


    The abbreviations represent the following:

    372

    PTVGROUP

    6.14.3 The procedure of Equilibrium_Lohse assignment


    x1

    Toll PrTSys has to be inserted manually in the impedance function

    (X)

    Can be used optionally

    (*)

    Apart from the parameters which are directly set in the assignment
    procedure

    Table 144: Output attributes of the Equilibrium_Lohse procedure

    6.14.3

    The procedure of Equilibrium_Lohse assignment


    The succeeding steps in the Equilibrium_Lohse procedure are illustrated in illustration 104.

    PTVGROUP

    373

    6.14.4 Evaluation of the Equilibrium_Lohse procedure

    Illustration 104: The procedure of Equilibrium_Lohse assignment

    6.14.4

    Evaluation of the Equilibrium_Lohse procedure


    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 Equilibrium_Lohse 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 assignment. This results in
    longer computing times.

    6.15

    Assignment with ICA


    Compared to other procedures, using volume-delay functions by lane which are permanently
    re-calibrated by means of ICA causes a significantly improved convergence behavior, since
    the lane geometry and interdependencies between the individual turns via a node are regarded in detail.

    6.15.1

    Fundamental principle
    In Visum, any variant of the equilibrium assignment uses volume-delay functions for links and
    turns to model the impedance that increases with increasing volumes. In urban network

    374

    PTVGROUP

    6.15.1 Fundamental principle


    models, the Turn VDFs are of particular importance, since the nodes affect the network performance to a much greater extent than links do. The mathematical formulation of the assignment problem assumes, that the impedance which is calculated by the VDFs depends only
    on the volume and the capacity of the individual network object (link, turn). Volume delay functions with this property are called separable VDFs. In reality, this holds approximately for links,
    but it does not apply to turns via nodes. Typical counter-examples are the permitted turns at
    signalized nodes or turns from minor approaches at two-way nodes. In these cases, the impedance does not only depend on the volume of the turn itself, but also from the volumes of the
    conflicting flows, i.e. the volumes of other turns via this node. Thus, the associated volumedelay functions can no longer be separable. This is a problem for the mathematical solution of
    the assignment problem, since existence and uniqueness of the equilibrium solution require
    separable volume-delay functions.
    Two requirements can be derived from this analysis:
    Realistic impedance modeling for nodes premises that nodes are modeled in detail in a
    way that conflicts between turns can be identified correctly. Transferred to Visum this
    means, that for these nodes the geometry and control have to be modeled in the junction
    editor. Subsequently, precise impedances and capacities of the turns can be calculated
    using the Intersection Capacity Analysis (ICA).
    For lack of separability, the values calculated by means of ICA may not directly be used to
    replace the volume-delay functions in the assignment procedure, since the convergence
    would get lost then.

    Illustration 105: ICA-based impedance calculation


    Visum by-passes the separability problem by an approximation approach. The procedure consists of an interaction between an equilibrium assignment procedure (using conventional
    VDFs) and node impedance calculation (ICA). First, equilibrium assignment is used to calculate the turn volumes. After the assignment, blocking back calculation ensures that the volumes used for ICA are realistic, i.e. do not lie in the overloaded range. ICA is then used to
    calculate the turn capacities and turn wait times for volumes. Subsequently, the volume of
    each turn is varied, while volumes of the other turns at the same node are retained in order to
    calculate wait times for other volume conditions. The wait times calculated for the individual
    turns are interpolated to estimate a CR function. These turn-specific VD functions are used in
    the next equilibrium assignment. They model the dependence of the impedance on only the

    PTVGROUP

    375

    6.15.2 Evaluation of the Assignment with ICA


    turn volume while the conflicting flows are regarded as if being constant. From the assignment's point of view, the effect of conflicting flows is "frozen" thereby until (after more equilibrium iterations) these flows are also updated in the next ICA calculation. In this way, the
    volume-delay functions are stabilized for some iterations in each case to favor convergence.
    Blocking back calculation after the assignment leads to additional wait times on links with traffic jams. And due to traffic jams, less traffic moves downstream (downstreaming metering).
    Both effects must have an impact on route search and route choice with the following equilibrium assignment. On links with a traffic jam, the VD function is adjusted so that the wait time
    due to blocking back calculation is reproduced in the VD function. To do so, first the effective
    capacity for these links is calculated. In contrast to link capacity, effective capacity accounts for
    the actual flow through rate of a link, which might lie below capacity due to spillback congestion, i.e. the capacity used in the VD function is decreased. The impact of traffic held back
    through a traffic jam is shown through a horizontal shift of the VD functions. The feedback loop
    between assignment and ICA ends, as soon as the impedances calculated with the VD function (including turns) or ICA do no longer significantly differ. For connectors and links that are
    not impacted by spillback congestion, assignment with ICA uses the VD functions defined.
    Their parameters do not depend on individual network objects, but (as for links) on the link
    type only.

    6.15.2

    Evaluation of the Assignment with ICA


    The assignment with ICA is a static and accounts for detailed node impedances.
    Specific advantage: Normally ICA cannot be applied properly while an assignment is running,
    since the VD functions are not separable. In the approach described, turn VD functions are
    made "roughly separable" by "freezing" the conflicting flows in equilibrium assignment. Normally, convergence is reached in this way. Simultaneously, the Turn VDFs are continuously
    adjusted to the wait times and capacities calculated by ICA. The HCM 2000 method (HCM
    2000 or HCM 2010) used in ICA is one of the worldwide recognized analyses methods for
    node performance calculations and accounts for lane distribution and conflicting turns down to
    detail level.
    The disadvantage is the significantly higher time and effort for modeling and calibration, since
    nodes whose impedances are to be calculated by ICA have to be modeled in detail. If you do
    not want to model all nodes in detail in your network model you should make sure that for the
    other nodes volume-delay functions are used which provide impedance data in a comparable
    scale. The route choice will be distorted if mixed impedances are produced by ICA turns and
    non-ICA turns systematically: Then, for example, only routes are chosen that do not traverse
    ICA nodes.
    Using the iterative approach, assignment with ICA requires more computation time than a conventional equilibrium assignment. Additional spillback and ICA calculations are required.
    Adaptation of the turn VD functions after subordinate equilibrium assignment mostly leads to a
    setback in convergence, which must be offset through recalibration.
    As in other assignment procedures, you can use existing assignment results as a starting point
    for an assignment with ICA in order to save time. The assignment results used must stem from
    an assignment with ICA. Only then is it guaranteed that the attributes used at turns and links
    have been calculated. This procedure can be used to calculate scenarios in which the network

    376

    PTVGROUP

    6.15.3 Input and output attributes of assignment with ICA


    basis and demand data do not radically change. The parameters previously estimated thus
    form a good basis for recalibration.
    For the assignment with ICA, one of the subordinate assignment procedures you can use is
    LUCE equilibrium assignment. You might prefer this procedure for assignment with ICA for the
    following reasons:
    Stable route distribution, especially with option Optimization of the proportionality of
    route volumes at meshes.
    Calculation of the blocking back model, using so-called bushes, is considerably faster
    than conventional calculation methods.
    Due to the stable routes, also the blocking back result is more stable and thus convergence can be reached sooner.

    6.15.3

    Input and output attributes of assignment with ICA


    Prior to the calculation of an assignment with ICA, certain attributes of network objects and
    also procedure parameters have to be set. After calculation, the results are available in the output attributes and can be displayed in the list view (see User Manual: Chpt. 24.1 , page 2299)
    or in the network editor (see User Manual: Chpt. 24.2 , page 2337). table 145 provides an overview of the input attributes that must be maintained. It is important that for those nodes whose
    turn impedances you want to calculate in detail using ICA, you select the Node impedance calculation (ICA) option for the Method for impedance at node attribute and set the Use preset
    method for impedance at node attribute to TRUE. table 146 lists the most important output
    attributes of the procedure for turns.
    The following prerequisites are required for the assignment with ICA:
    Prior to the assignment with ICA calculation, the geometry and control need to be modeled correctly for the nodes the ICA impedance calculation has been activated for. To
    check whether the calculation can be performed correctly for all nodes, from the
    Calculatemenu, choose >Network check and check the Viability for ICA option.
    For turns, the design volume PrT needs to be a volume-representing attribute (Volume
    PrT or Volume PrT with base). Enter the settings via menu Calculate> General procedure settings> navigator entry PrT settings> Node impedances. For the design
    volume PrT, only factor 1.0 is permitted. This is due to the fact, that the calibration of the
    VDFs by turn would fail otherwise. The VD function used for turns is based on the hourly
    capacities output by ICA. This means that you can only perform assignment with ICA for
    assignment periods of 1h. As a result, hourly values for link and turn capacities must be
    defined.

    PTVGROUP

    377

    6.15.3 Input and output attributes of assignment with ICA

    Table 145: Input attributes of assignment with ICA

    378

    PTVGROUP

    6.15.3 Input and output attributes of assignment with ICA


    The abbreviations represent the following:
    x1

    Toll-PrTSys has to be inserted manually in the impedance function to have an


    effect

    x2

    Takes effect in the framework of the blocking back model

    (x)

    Can be used optionally

    For the output of results, the following options are provided:


    There are different output variants: Primarily, the assignment with ICA fills the usual attributes
    of the various network object types (link, turn, etc.) with the calculated volumes and impedances. In addition to the common volume and travel time attributes, there are the following
    output attributes at (main) turns and links that are only filled through assignment with ICA:
    Attribute

    Meaning

    Is ICA turn in ICA assignment

    Indicates whether the ICA-Turn function is to be used for this


    turn in the assignment with ICA.

    Final capacity for assignment with ICA

    Last capacity used during assignment with ICA. The Capacity


    PrTV attribute is not used for turns at (main) nodes calculated
    with ICA.

    Final t0 for assignment


    with ICA

    t0 that was recently used with ICA assignment. The t0 PrT attribute is not used for (main) turns at nodes calculated with ICA.

    Final smoothed volume


    for assignment with ICA

    Smoothed volume resulting from recent iteration.

    tCur-PrTSys for assignment with ICA

    tCur of the turn-specific VD function, including the final VD


    function parameters. In contrast, the attribute tCur-PrTSys stores the result calculated in the recent ICA calculation.

    Final A for assignment


    with ICA

    Final VD function parameter A for the turn-specific VDF

    Final B for assignment


    with ICA

    Final VD function parameter B for the turn-specific VDF

    Final capacity for assignment with ICA

    corresponds to smoothed capacity of (main) turns calculated


    with ICA

    Deterred upstream
    Deterred volume refers to the part of the volume that, accorvolume in assignment
    ding to blocking back calculation, is held back at bottlenecks
    with ICA
    upstream from the (main) turn and so does not reach it.
    Table 146: Additionally calculated turn/main turn attributes for assignment with ICA

    PTVGROUP

    379

    6.15.4 The procedure of assignment with ICA


    Attribute

    Meaning

    Effective capacity for assi- On uncongested links, effective capacity corresponds to link
    gnment with ICA
    capacity or the Capacity PrT attribute. On congested links, it
    corresponds to the traffic volume exiting the link.
    Deterred upstream
    volume in assignment
    with ICA

    Deterred upstream volume refers to the part of the volume that,


    according to blocking back calculation, is held back at bottlenecks upstream from the (main) turn and so does not reach
    it.
    Table 147: Additionally calculated link attributes for assignment with ICA
    Furthermore, numerous diagnostic outputs are provided which can be used for convergence
    check. If the procedure converges either slowly or not at all, the outputs provide useful information, e.g. which turns show significant differences when calculated with ICA impedance calculation or the VD function.
    As long as the procedure is running, you can watch the process in the "Goodness of PrT
    assignment with ICA" list.
    *.csv files are created to which the program saves turn attribute data after each iteration.
    These files are helpful when you want to compare the development of attribute values of
    individual turns during the course of assignment with ICA.
    Some result attributes of the assignment with ICA are saved to user-defined attributes, if
    required. This data can be used for the comparison of the convergence reached in different runs of the assignment with ICA. To do so, first copy the values of the user-defined
    attributes, before they are overwritten during the next calculation.
    Optionally, an Excel report is created which contains the results of the recent ICA calculation. From the report it is to be seen, which volumes were used for the calculation and
    which capacities resulted from that. For nodes of the all-way stop type, the v/c value is output the same way as for nodes of the two-way stop type.
    The precise times when attribute data is stored in an iteration are listed here (see "The procedure of assignment with ICA" on page 380).

    6.15.4

    The procedure of assignment with ICA


    The assignment with ICA is based on the iterative solution for the user optimum with volumedelay functions for all network objects. The distinctive feature is that the parameters of turn VD
    functions can be set by turn ("turn-specific) and might change during the calculation due to the
    adjustment of the ICA calculation results, as described with the fundamental principle (see
    "Fundamental principle" on page 374).
    If the assignment with ICA is not based on existing assignment results, the parameters
    used in the VD function for turns and links are first initialized. For turns, the input values
    are used that you have specified in the Procedure parameters dialog (Input tab). Depending on the control type used, additional signal times and geometric data are considered.
    The values initialized for turn capacities, t0, and VD function parameters A and B are used
    to perform the first subordinate assignment. Initialization of the link attribute Effective
    capacity for assignment with ICA depends on the settings for blocking back calculation.
    If link capacities are taken into account, the value is initialized with Capacity PrT or the

    380

    PTVGROUP

    6.15.4 The procedure of assignment with ICA


    total of turn capacities in the link capacity model. If this is not the case, the initial value is
    infinite. If your assignment with ICA is based on existing assignment results, the parameters are available from the last assignment with ICA and initialization is skipped.
    First the subordinate assignment procedure is performed. Choose one of the following
    assignment procedures: Equilibrium assignment, Equilibrium_Lohse or Equilibrium assignment (LUCE). For nodes, for which ICA calculation has been activated, use turn-specific VD functions. In this case, no ICA calculations are carried out during the subordinate
    assignment procedure.
    The turn-specific VD functions used illustration 106 (see "Used turn VDF" on page 383)
    and the adaptation of link VD functions are described in different paragraphs (see "Adjusting the VD functions used" on page 384).
    After completion of the subordinate assignment procedure, the blocking back model is
    applied. For calculation of the blocking back model, the turn capacities at nodes calculated with ICA are taken into account.. Optionally, you may additionally use the capacities defined in the link capacity model. As a result of blocking back calculation, link
    impedances are adjusted, as traffic jams cause additional wait times on links, and with
    congested traffic run time can be reduced.
    Notes: By applying the blocking back model, only phase 1 is calculated.
    The blocking back model is not applied while the subordinate assignment procedure
    is performed.
    During finalization of the ICA assignment, the global parameters of the blocking back
    model are adjusted to the procedure parameters of ICA assignment, i.e. settings that
    differ are first ignored during ICA assignment and then overwritten.
    Prior to the ICA calculation, the current values are determined for volume and impedance
    and also the parameters of the VDFs are recorded (according to the settings: in attribute
    files, as user-defined attributes and in the Goodness of PrT assignment with ICA list).
    Then, the turn volumes calculated in the recent iteration and in the current iteration are
    smoothed, i.e. the weighted mean is calculated.
    Using ICA, the program calculates turn impedances and capacities. For this ICA calculation, the design volume used is the smoothed turn volume (including the basic
    volume, depending on the design volume set).
    Calculation of the new, turn-specific VD functions is performed in two steps and separately for each turn. In the first step, the parameters of the VD function are determined
    through interpolation of three sampling points. One sampling point is given by the smoothed turn volumes and the respective impedance (see previous step). To determine two
    additional sampling points, reduce or increase the volume of the turn currently being processed, while maintaining the other turn volumes passing via the node. The impedance of
    the current turn is then recalculated with ICA. Since the VD function to be interpolated possesses three free parameters (t0, A, B), it is clearly defined by the three sampling points. In
    the second step, these parameters and also the capacity are smoothed by means of the
    values resulting from the previous iteration. In the procedure parameters, a minimum capacity per turn can be set. If the smoothing result is below the minimum capacity, the minimum capacity will be used instead. The convergence check is performed after the

    PTVGROUP

    381

    6.15.4 The procedure of assignment with ICA


    determination of the new VDFs. If the convergence constraints are satisfied, the parameters of the VDF will be reset to the value of the recent iteration. This means the VD functions are in accordance with the subordinate assignment last performed.
    If the convergence test is failed, the attributes Deterred upstream volume in assignment
    with ICA, for links and turns, and Effective capacity in assignment with ICA, for links,
    are updated. These values are required for application of the VD function during the next
    subordinate assignment (or for an assignment based on existing assignment results).

    Illustration 106: The procedure of assignment with ICA

    382

    PTVGROUP

    6.15.5 VD functions in assignments with ICA

    6.15.5

    VD functions in assignments with ICA


    The following sections describe the turns VD function and adjustment of the links VD function
    during assignment with ICA

    6.15.5.1

    Used turn VDF


    The turns VD function is used for assignment with ICA of all opened turns whose nodes
    include a Node impedance calculation (ICA).

    where
    tcur

    Turn attribute corresponds to tCur of the turn-specific VD function, including the


    VD function parameters. Attribute tCur_PrTSys for assignment with ICA contains the value calculated at the end of the assignment with ICA.

    A and B

    Attributes of the respective turns.


    The attributes Final A for assignment with ICA and Final B for assignment with
    ICA include the values calculated at the end of the assignment with ICA.

    Turn volume in subordinate assignment (without spillback congestion)

    t0

    Turn attribute
    Attribute Final t0 for assignment with ICA contains the value calculated at the
    end of the assignment with ICA.

    cap

    Turn attribute that corresponds to smoothed capacity in the assignment with


    ICA.
    Attribute Final capacity for assignment with ICA contains the value calculated
    at the end of the assignment with ICA.

    Turn attribute calculated as the difference between demand volume and


    volume. Deterred volume refers to the part of the volume that, according to
    blocking back calculation, is held back at bottlenecks upstream from the turn
    and so does not reach it.
    Attribute Deterred volume upstream in assignment with ICA contains the
    value calculated at the end of the assignment with ICA.

    During the assignment, the factors A and B are updated with each ICA impedance calculation
    per turn. You can find the values of the last iteration in the turn attributes Final A for assignment with ICA and Final B for assignment with ICA. The following data are also saved to
    turn attributes: t0 values (Final t0 for assignment with ICA), the capacity (Final capacity for
    assignment with ICA ), and the difference between demand volume and current volume
    (Deterred volume upstream in assignment with ICA).

    PTVGROUP

    383

    6.15.5.2 Adjusting the VD functions used


    6.15.5.2

    Adjusting the VD functions used


    During ICA assignment, turn and link VD functions are modified. This is done in two ways:
    horizontal shift of the curve due to lower volumes (downstream metering)
    adjusting the curve progression for volumes exceeding effective capacity, triggered by
    additional traffic jam waiting times
    The first adjustment is made for both turn and link VD functions via the attribute Deterred upstream volume . The second adjustment is only made for links on which a traffic jam is observed. Both effects are depicted in the following figure of a modified link VD function.

    Illustration 107: Adjustment of the link VD function


    Generally, link VD functions are conventionally assigned during the assignment with ICA, so
    you can define link VD functions based on the link type. The following equation shows the
    adjustments, where vdfbase refers to the link VD function you defined.

    where

    384

    tcur

    Link run time in loaded network

    vdfbase

    VD function defined (depends on link type)

    Link volume in subordinate assignment (without spillback congestion)

    cap

    Link capacity

    effcap

    Link attribute calculated in each iteration after spillback calculation


    Attribute Effective capacity in assignment with ICA contains the value calculated at the end of the assignment with ICA.
    The effective capacity corresponds to the link capacity on uncongested links.
    On congested links, effective capacity is given by the minimum of capacity and
    link volume.

    PTVGROUP

    6.16 Stochastic assignment


    q

    Link attribute that represents the difference between demand volume and
    volume plus queue length. Deterred volume refers to the part of the volume
    that, according to blocking back calculation, is held back upstream and so
    does not reach the link.
    Attribute Deterred volume upstream in assignment with ICAcontains the value
    calculated at the end of the assignment with ICA.

    T = 1,800, i.e. T corresponds to half the assignment period [in sec]

    By adjusting the VD functions, you ensure that the impedances changed through blocking
    back calculation have an impact on route search and route choice in the subordinate assignment.

    6.16

    Stochastic assignment
    Stochastic assignment procedures assume that traffic participants in principle select the best
    route, but evaluate the individual routes differently due to incomplete and different information.
    In addition, in a stochastic PrT assignment the demand is distributed to the found routes as for
    a PuT assignment using a distribution model (e.g. Logit, Kirchhoff, Box-Cox, Lohse or Lohse
    with variable beta) (see "Distribution models in the assignment" on page 329).
    In order to take the spatial similarities of the routes into account during the distribution, a similarity measure is determined from overlapping routes (analogous to independence during timetable-based PuT assignment) it is called the Commonality Factor (C- Logit) or the
    independence of each route (according to Ben Akiva) is determined.
    This results in the following sequence:
    1. Route search for all traffic cells for current impedance.
    2. Commonality Factor or independence calculated from overlapping of all routes of an origin/destination pair.
    3. Distribution of demand to the routes of each OD pair, taking the Commonality Factor or independence into account.
    4. Repeat from step 3 until demand for all OD pairs is in equilibrium.
    5. Repeat steps 1 4 until no new routes are found or until the change in the link volumes between two iteration steps is very small.
    During the route search, the number of possible routes can be increased in that it is not just
    the shortest route that is found, but a number of alternatives are found using a multiple best
    path search and a variation in the link impedances.

    6.16.1

    Evaluation of stochastic assignment


    Compared with the equilibrium assignment, there are more routes loaded even in a poorly loaded network in the case of the stochastic assignment, because a (small) part of the demand is
    also assigned to suboptimal routes due to the distribution model. In all cases, this property is
    closer to reality than the strict application of Wardrops first principle.

    PTVGROUP

    385

    6.16.2 Input and output attributes of stochastic assignment

    6.16.2

    Input and output attributes of stochastic assignment


    To execute the stochastic assignment, certain entries have to be made. table 148 provides an
    overview of the input attributes that must be maintained. After calculation, the results are available in the output attributes and can be displayed in the list view (see User Manual: Chpt. 24.1 ,
    page 2299) or in the network editor (see User Manual: Chpt. 24.2 , page 2337). table 149 lists
    the output attributes to which the procedure results are saved.

    386

    PTVGROUP

    6.16.2 Input and output attributes of stochastic assignment

    Table 148: Input attributes for stochastic assignment


    The abbreviations represent the following:

    PTVGROUP

    387

    6.16.3 The procedure of stochastic assignment


    x1

    Toll PrTSys has to be inserted manually in the impedance function

    (x)

    Can be used optionally

    (*)

    Apart from the parameters which are directly set in the assignment
    procedure

    Table 149: Output attributes for stochastic assignment

    6.16.3

    The procedure of stochastic assignment


    The procedure is broken down into an external and an internal iteration (illustration 108).
    The external (global) iteration with iterator n is used for the route search. This loop is
    repeated until either n = N or until no new shortest routes are found.
    The internal iteration with iterator m is used to assign the volume to the routes. This loop is
    repeated until either m = M or until the deviations of the impedances on the network elements and the deviation of the volumes on the routes between two iteration steps is very
    small.

    388

    PTVGROUP

    6.16.3 The procedure of stochastic assignment

    PTVGROUP

    389

    6.16.3 The procedure of stochastic assignment

    Illustration 108: The procedure of stochastic assignment

    390

    PTVGROUP

    6.16.4 Similarity of routes and commonality factor


    The alternative route search by stochastic variation of the impedances is closely related to
    other procedures used to determine k-shortest paths and shares their common drawback that
    often new routes are found that differ insignificantly from previous routes. Such routes are not
    desirable as they hardly change the volume situation in the network and only increase the
    route quantity, which leads to extended computing time and higher memory requirements. For
    this reason a detour test is offered as part of the stochastic assignment that discards a route r2
    if a route r1 already exists that matchesr 2, with the exception of a subsection, and if this subsection in r2 is significantly longer than in r1. More precisely, r2 is discarded in favor of r1, if the
    following applies (illustration 109):
    r1 = AT1B
    r2 = AT2B
    Length(T2) > Factor Length(T1)

    Illustration 109: Discarding routes


    The route sections A and B can be empty if the subsection is at the start or the end of the routes.

    6.16.4

    Similarity of routes and commonality factor


    In the case of the stochastic assignment, alternative routes are generated - based on another
    assignment as initial solution - for an OD pair by varying the impedances of the network
    objects based on a distribution, in order to model the incomplete information supplied to the
    road-users and their individual differences in terms of perception and preferences. In this way,
    it is possible to calculate in one step not only the shortest route in terms of impedance, but also
    alternative routes with higher impedances. After completion of the route search, depending on
    the route impedance based on an assignment model (Logit, Box-Cox, Kirchhoff, Lohse or
    Lohse with variable beta), the demand is distributed across the alternatives. The similarity of
    the routes is to be taken into account during the distribution process. The problem of similarity
    is illustrated in the example below (illustration 110):
    Whereas the independence of the routes is given in cases 1 and 2, there is a dependence of
    routes 1 and 3 in case 3, since there is some degree of overlap. This overlapping must be
    taken into consideration in the route choice.

    PTVGROUP

    391

    6.16.4 Similarity of routes and commonality factor


    Case 1

    Share
    expected

    Logit

    Route 1

    50%

    50%

    Route 2

    50%

    50%

    Case 2

    Share
    expected

    Logit

    Route 1

    33%

    33%

    Route 2

    33%

    33%

    Route 3

    33%

    33%

    Case 3

    Share
    expected

    Logit

    Route 1

    approx.
    28%

    33%

    Route 2

    approx.
    44%

    33%

    Route 3

    approx.
    28%

    33%

    Illustration 110: Example of similarity of routes


    The C-Logit approach proposed by CASCETTA is a suitable way of overcoming this problem.
    To do this, a so-called commonality factor C is introduced to measure the overlapping of the
    two routes r and s as follows:

    or
    with

    392

    Crs

    Similarity of the routes r and s (Commonality factor)

    t0rs

    Time t0 of the common sections of the routes r and s

    t0r

    Time t0 of route r

    PTVGROUP

    6.16.5 Example of stochastic assignment


    lrs

    Length l of the common sections of the routes r and s

    lr

    Length l of route r

    Thus, Crs equals 1, if the two routes are identical, and will be 0, if the two routes do not overlap.
    The commonality factor Crs is determined for all route combinations. Then, the correction factor
    CFr of a route r compared to any other route s is defined as follows:

    The correction factor of a route r is 1 if the commonality factors Crs for all routes s have the
    value 0, i.e. the route has no overlap with another route. In any other case it is below 1. The
    correction factor CFr is then accounted for in the Logit model as follows:

    In the case of Box-Cox, Kirchhoff, Lohse or Lohse with variable beta, its inclusion is also carried out in the same way.
    Alternatively, the correction factor CFr can be determined with a simpler approach according to
    Ben Akiva. It is then defined as:

    or

    with

    6.16.5

    t0a

    Time t0 of link a

    t0r

    Time t0 of route r

    la

    Length l of link a

    lr

    Length l of route r

    Nija

    Number of routes of the OD pair ij that lead across link a

    Example of stochastic assignment


    The table 150 shows the key input data used in the example network. If the following parameters are chosen for the search, then in a single external iteration, all 3 conceivable routes
    will be found:

    PTVGROUP

    393

    6.16.5 Example of stochastic assignment


    Number of search iterations = 5
    = 8 R0.5
    Compared to the "objective" impedances (resulting from impedance definitions and
    VDFs), the impedances of the network objects are changed for alternative shortest path
    searches. They are drawn randomly from a normal distribution which has the objective
    impedance R as mean value and whose standard deviation is given as a function of R.
    LinkNo Type v0 [km/h]

    Length [m]

    Capacity [car units] R0* [min]

    R0* [s]

    20

    100

    5,000

    1,200

    3.00

    180

    20

    100

    5,000

    1,200

    3.00

    180

    20

    100

    5,000

    1,200

    3.00

    180

    20

    100

    5,000

    1,200

    3.00

    180

    20

    100

    5,000

    1,200

    3.00

    180

    20

    100

    5,000

    1,200

    3.00

    180

    30

    80

    16,000

    800

    12.00

    720

    30

    80

    5,000

    800

    03:45

    225

    10

    40

    60

    10,000

    500

    10:00 AM
    a.m.

    600

    11

    40

    60

    5,000

    500

    5.00

    300

    Length [m]

    R0* [min]

    R0* [s]

    Route Links
    1

    1+8+9

    26,000

    0:18:45

    1,125

    1+2+3+5+6+7

    30,000

    0.18

    1,080

    10+11+5+6+7

    30,000

    0:24:00

    1,440

    Input parameters
    BPR function with a = 1, b = 2, c = 1
    Bottom = 0.5, Top = 0.5 = 0.5
    Distribution with Logit, = 0.001
    Table 150: Impedance in unloaded network, input parameters for stochastic assignment
    After completing the search, the correction factor for the independence of each route is determined according to Cascetta. It is based on the similarity of the individual route pairs with reference to time t0 or to the length. table 151 shows the commonality factors C. These are used to
    calculate the correction factor CFr of route r.
    Route 1

    Route 2

    394

    PTVGROUP

    6.16.5 Example of stochastic assignment

    Route 3

    Route pair

    t0ij

    t0i

    t0j

    Cij

    1.1

    1,125

    1,125

    1,125

    1.00

    1.2

    180

    1,125

    1,080

    0.16

    1.3

    1,125

    1,440

    0.00

    2,1

    180

    1,080

    1,125

    0.16

    2.2

    1,080

    1,080

    1,080

    1.00

    2,3

    540

    1,080

    1,440

    0.43

    3,1

    1,440

    1,125

    0.00

    3,2

    540

    1,440

    1,080

    0.43

    3.3
    1,440
    1,440
    1,440
    Table 151: Calculation of commonality factor C for all route pairs

    1.00

    The share by route is calculated from the correction factor according to Cascetta and from the
    impedance Rmin0 in the unloaded network.
    For Route 1, the portion is calculated using the Logit model as follows:

    In the same way, the shares for routes 2 and 3 shown in table 152 are calculated. The product
    of share P and demand F is the volume of each route qr1 in the first iteration step. For Route 1,
    the calculation is as follows: 0.425 2000 = 849.4 PCU. Based on the route volumes, the link
    volumes and thus the network impedances can be calculated (illustration 111). This results in
    the impedances R1 of the routes. These interim results can be verified in Visum if the maximum
    number of internal iterations are set to M = 1 in the assignment parameters.
    Route

    R min0

    exp(Rmin0)E Portion P

    qr1

    R1

    0.8596

    1,125

    0.27907904- 0.425
    9

    849.4

    2,470

    0.6264

    1,080

    0.21273756- 0.324
    1

    647.5

    1,961

    PTVGROUP

    395

    6.16.5 Example of stochastic assignment


    Route

    R min0

    exp(Rmin0)E Portion P

    qr1

    R1

    0.6978

    1,440

    0.16533542- 0.252
    1

    503.2

    2,848

    0.65715203- 1.000
    2

    2,000.0

    Total

    Table 152: Volumes in the first internal iteration step m = 1

    Illustration 111: Volumes and link run times after the first internal iteration step m=1
    For the route choice in the second iteration step, an estimated impedance R min1 is calculated.
    Since = 0.5, the impedance results from the formation of the mean value of R min0 and R1. On
    the basis of Rmin1, as in the first iteration step, the assignment is then made for the 3 routes. For
    each route, the interim result is q r2. To smooth the volumes between two iteration steps, the
    MSA method (Method of Successive Averages) is used.

    For m = 2, this results in the following for the volume of Route 1:

    This route volume then leads to the link volumes and impedances of the second iteration step
    (table 153). The iterations are repeated until the termination criteria are met.
    Route

    Rmin1

    exp(R)E

    qr2

    R2

    0.8596

    1797.6

    0.142432 0.3944

    788.8

    819.1

    2,405.2

    0.6264

    1,520.7

    0.136919 0.3791

    758.3

    702.9

    2,016.0

    0.6978

    2,144.0

    0.081775 0.2264

    452.9

    478.0

    2,785.6

    Portion P qr2

    Total
    0.361126
    Table 153: Volumes in the second internal iteration step m = 2
    396

    2,000

    PTVGROUP

    6.17 TRIBUT

    6.17

    TRIBUT
    Taking road toll into consideration, a constant value of time is set in conventional procedures,
    which in principle can be used to convert the costs (toll) into time and the conventional monocriterial assignment procedures are directly applicable.
    Compared to the conventional approach, TRIBUT uses a concurrent distributed time value.
    Accordingly, TRIBUT calculates in the route search as well as in the route choice with two
    separate criteria, namely with time and costs (bicriterion).
    This method has been used for many years in France, for the evaluation of privately financed
    freeways with toll management. Compared to the conventional approach, this approach is a
    more realistic price elasticity when using toll roads.
    Road tolls are transport system-specific and can either be defined for a link or a link sequence.
    Using link sequences allows modeling of non-linear toll systems.
    Road toll modeling is an add-on which basically can be used with any equilibrium assignment
    procedure. Visum provides two extensions of this kind: TRIBUT-Equilibrium (as extension to
    the "Equilibrium" method) and TRIBUT-Learning procedure (as extension to the "Equilibrium_
    Lohse" method).

    6.17.1

    Input and output attributes of the TRIBUT procedure


    To execute a TRIBUT procedure, certain entries must be made. table 154 provides an overview of the input attributes that must be maintained. After calculation, the results are available
    in the output attributes and can be displayed in the list view (see User Manual: Chpt. 24.1 ,
    page 2299) or in the network editor (see User Manual: Chpt. 24.2 , page 2337). table 155 lists
    the output attributes to which the procedure results are saved.

    PTVGROUP

    397

    6.17.1 Input and output attributes of the TRIBUT procedure

    Table 154: Input attributes for TRIBUT


    The abbreviations represent the following:
    0

    398

    Generally possible, however not recommended

    PTVGROUP

    6.17.2 Basics of assignment with toll consideration

    Table 155: Output attributes for TRIBUT

    6.17.2

    Basics of assignment with toll consideration


    The decisive feature of an assignment procedure is the impedance definition for route evaluation and route choice. With all toll-regarding assignment procedures, the impedance Rr of a
    route r consists of travel time tr and monetary costs cr:

    Here, VT is the value of time in [/h], for example. Though this equation applies to all toll-regarding assignment procedures, the TRIBUT procedure differs from other procedures in two properties:
    Monetary route costs can be calculated in different ways.
    The value of time VT is no constant value per demand segment, but VT is modeled as stochastic parameter that varies according to a particular probability distribution.
    Link toll
    In the simplest case, the route's monetary costs result from summing up the toll amounts by
    link along the route.
    The following applies:

    PTVGROUP

    399

    6.17.2 Basics of assignment with toll consideration


    tL = t(VolL)

    Travel time on a link L as a function of the volume

    VolL

    Volume of link L

    CL

    Toll value for using link L

    VT

    Value of time in [/h], for example

    This toll type applies to the HGV toll in Germany, for example: On parts of the network
    (highways), heavy goods vehicles have to pay a toll amount which is precisely proportional to
    the covered distance. Thus to each link of the highway link type the product from the link
    length x constant km cost multiplication can be allocated as toll amount. For any other link and
    for any other transport system, the toll amount = 0. The total of these amounts summed up
    along a route represents the cost resulting from the distance traveled on highway links for the
    transport system HGV.
    For link toll, no toll system has to be defined. It is not necessary either to include the link attribute Toll- PrTSys in the impedance definition, since TRIBUT regards this amount automatically.
    Note: The TRIBUT-Equilibrium assignment always regards the link-specific toll values.
    The TRIBUT-Learning procedure only regards the link-specific toll values of links which
    do not belong to any toll system.
    Area toll
    Especially toll systems for inner city areas often use a different type. For the area toll, a geographically coherent section of the network is stated as toll area. A fixed amount, independent
    of the distance, is charged if a route leg runs through the toll zone:

    400

    PTVGROUP

    6.17.2 Basics of assignment with toll consideration

    Illustration 112: Example for area toll: The London Congestion Charging Zone
    At first view, the monetary costs of a route do not depend on the individual links being traversed, but on the route course as a whole in this case. Basically this is right, however,
    TRIBUT - like any other assignment procedure - is based on shortest path searches via links
    and requires the impedances by link therefore. That is why TRIBUT puts the area toll down to
    the link toll case. For that, define the toll area first by creating a network object 'toll system' of
    the area toll type and then allocating the toll area's number to all links which are located in the
    area as value for the attribute Toll system number . The toll system additionally stores the
    fixed toll amount for each transport system. For the clear definition of the figure described
    below, all connector nodes of a zone need to be located either within the toll area or outside of
    it.
    On this basis, TRIBUT defines the toll amounts for links, turns, and connectors as follows:
    cL = 0 for all links L
    cC = 0 for all connectors C

    for all turns T, with T =1, if turn T leads from a link inside the toll area to a link
    outside or vice versa, i.e. if the toll area border is crossed. Otherwise, T = 0.

    PTVGROUP

    401

    6.17.2 Basics of assignment with toll consideration

    for all transitions X from connectors to links, where X =1, if the transition X leads
    to a link in the toll area or originates from there. Otherwise, X = 0.
    illustration 113 illustrates the principle:

    Illustration 113: Reducing area toll to link toll


    (For reasons of clarity, turns without toll are not displayed)
    Summing up the toll amounts along a route results in an amount null for routes that do not
    touch the toll area at all. Any other route (origin traffic, destination traffic, through traffic, internal
    traffic of the toll area) is charged with the toll amount of c, since they traverse exactly two network objects with toll amount = c/2 each.
    In a Visum model, you can define multiple toll systems of the area toll type. Then, the definitions for turn and connector cost are applied to each toll system with the associated fixed toll
    amount. For turns between two toll areas the two toll amounts are charged.
    Please note the two characteristics. For routes, that cross the border of the toll area multiple
    times the toll amount is charged multiple times. This might not correspond to reality, however it
    cannot be avoided for the required reduction to additive toll amounts per network object. Furthermore, the internal traffic within the toll area can be excluded from toll calculations in reality.
    For the TRIBUT route choice it is no problem that these flows are nevertheless charged with
    toll amounts, since the toll comparably refers to all route alternatives and thus this additive constant value does not modify the equilibrium solution. But when calculating a skim matrix of the
    impedance for future use in a demand model for example, you need to perform an additional
    matrix operation after skim matrix calculation to subtract the toll amount from the internal traffic
    OD pairs data.
    Note: Only the TRIBUT-Learning procedure takes the area toll into consideration.
    For links that belong to a toll system the link attribute Toll-PrTSys is not regarded.
    Matrix toll
    Another type of toll models is often applied to arterial highways. A subset of links is designated
    as a toll zone with a small number of connections (entries and exits) to the rest of the network
    (illustration 114).

    402

    PTVGROUP

    6.17.2 Basics of assignment with toll consideration

    Illustration 114: Toll station at highway exit


    Toll amounts are not defined as the sum of toll amounts by link, but arbitrarily as fee by pair
    (entry, exit). Using such a fee matrix, the operator has more flexibility since the toll amounts for
    longer routes can be defined irrespectively of the toll amounts for shorter sections of a longer
    route. Usually, those tariffs are on a diminishing scale, thus the rate per kilometer declines with
    increasing total distance.
    As a matter of principle, such a matrix toll (which is named according to the fare matrix) cannot
    be reduced to summing up the toll amounts by link. Let's have a look at the example in illustration 115:

    Illustration 115: Example of a matrix toll


    The links 1-2 and 2-3 form a highway corridor with matrix toll. For that, define the toll area first
    by creating a network object 'toll system' of the matrix toll type and then allocating the toll
    area's number to all links which are located in the area as value for the attribute Toll system
    number. The toll system additionally stores a matrix for each transport system which contains
    the toll amounts between all border nodes of the toll area. In this example, these are the nodes
    1, 2, and 3. The toll amounts are listed in table 156.
    from / to node

    3
    3
    2
    Table 156: Toll amounts for the example network

    Please note, that the toll amount for the overall link is less compared to the two individual links.
    For each pair (entry, exit) in the toll area, TRIBUT generates a virtual link with the toll amount
    from the matrix in the network and uses these virtual links for the shortest path search. In contrast, the original links in the toll area are not regarded for the shortest path search. For travel

    PTVGROUP

    403

    6.17.2 Basics of assignment with toll consideration


    time computation, the volumes by virtual link are transferred back to the original links. This allocation is always based on the route with the minimum time (regarding t0) required between
    'from node' and 'to node' of the virtual link. illustration 116 shows the graph that is generated
    for the shortest path search in the example.

    Illustration 116: Shortest path search graph with matrix toll


    This modeling approach assumes a degressive toll matrix, i.e. if there are three nodes A, B,
    and C, always c A-C cA-B + c B-C. Furthermore, the number of virtual links that are added to the
    search graph exhibits quadratic growth proportionally to the toll area's number of border
    nodes. Thus you should use a toll matrix only in those cases where the toll area is connected
    to the surrounding network by a manageable number of nodes.
    In a Visum model, you can define several toll systems of the matrix toll type. Nevertheless,
    each link may belong to just one toll system.
    Notes: Only the TRIBUT-Learning procedure takes the matrix toll into consideration.
    For links that belong to a toll system the link attribute Toll-PrTSys is not regarded.
    The Value of Time as stochastic parameter
    Additionally, the TRIBUT procedure features the definition of the value of time (VT) and the
    impact of this definition (table 157). This description is reduced to the link toll case, since the
    basic principle does not differ by toll type.
    "Conventional" toll assignment

    TRIBUT

    VT is constant for all vehicles.

    VT is concurrent distributed, which means


    that each vehicle of the matrix specifies an
    individual VT for route choice.

    monocriterial
    bicriterial
    In the full course of the assignment, only
    During the assignment, both criteria (tR and
    one criterion is used, because the costs cR
    cR) must always be available for each path.
    of a route are converted into a constant time
    penalty.
    Table 157: Comparison of conventional toll assignment and TRIBUT
    The complexity of a bicriterial route choice procedure is illustrated in a time-cost diagram (illustration 117).

    404

    PTVGROUP

    6.17.3 LogN distribution of the random variable VT

    Illustration 117: Time-cost diagram


    Each point on the diagram, for example A = (tA,cA), corresponds with a route of the same
    origin destination relation.
    A certain time value VT corresponds with a family of parallel straight lines with a negative
    slope.
    If two routes lie on one VT straight, they are equally good (for a user with the same VT).
    This VT is also characterized as a critical VT for two routes.

    6.17.3

    LogN distribution of the random variable VT


    The TRIBUT procedure is based on the assumption, that each vehicle has its individual VT .
    This is displayed by a random variable and the corresponding probability distribution. TRIBUT
    uses a LogNormal distribution for the random variable VT.

    The two distribution parameters apply:

    Position parameter, corresponds with the Median of

    Dispersion parameter
    This parameter corresponds to the standard deviation of the associated standard normal variable.

    has the following properties:


    The probability is equal to zero for negative values.
    The position parameter

    corresponds with the Median of

    means that the distribution function adopts the value of 50% for VT=

    PTVGROUP

    , which
    .

    405

    6.17.4 Efficient routes - exclusion criterion in route search


    The figures show the density function (illustration 118) and the distribution function (illustration
    119).
    Logarithmic normal distributions

    Illustration 118: Density function

    Illustration 119: Distribution function

    6.17.4

    Efficient routes - exclusion criterion in route search


    Whereas a unique best path (shortest path) can always be determined for all monocriterial
    (conventional) methods, for TRIBUT, many (several) best paths have to be specified in the
    route search as well as kept in RAM, because the VT which is not unique. Hence, the resulting
    complexity of the route search can, however, be limited with critical values of time (as shown in
    illustration 120).

    406

    PTVGROUP

    6.17.5 Route split

    Illustration 120: Efficient routes


    illustration 120 shows a route search with six routes. It can be verified graphically or analytically, that there is no VT for which route X or Y would be preferred over A, B, C or D.
    Generally spoken, the VT-straight lines A-B, B-C, C-D form a convex front. All routes which lie
    to the right of this convex front no longer have to be observed, because they cannot be optimal for any user (for no VT).
    The relevant routes on the convex front are also designated as set of the efficient routes. Only
    these efficient routes are saved for further search and later distribution.
    There are two aspects:
    For bicriterial procedures you can also discard most alternatives from a multitude of possible routes, so that the route search can be calculated with the finite time spent and
    memory used.
    The bicriterial procedure has to memorize and save several paths at the same time, whereas during and after a monocriterial search always one solution (best path) is found for
    each source destination relation.

    6.17.5

    Route split
    The result of a route search only comprises the efficient routes. Under these, the demand for
    an OD relation is set. The critical VT are decisive for every neighboring routes on the efficient
    front. In the example, there are three critical values of time - A/B, B/C and C/D.
    As illustrated in illustration 121 the demand shares of the four efficient routes can be derived
    from the probability distribution of the VT.

    PTVGROUP

    407

    6.17.6 Route balancing in the equilibrium iteration

    Illustration 121: Distribution of traffic demand across the routes

    6.17.6

    Route balancing in the equilibrium iteration


    Similar to equilibrium assignment (see "Equilibrium assignment" on page 342), each new
    TRIBUT iteration starts with a route search. If new routes are found which fall on the convex
    front, they are included in the set of relevant routes. The equilibrium formation is then executed
    by a coupled demand equalization between the routes (illustration 122). The following steps
    are carried out:
    Balance between the route of a toll level
    Balance between the neighboring toll levels
    Constant correction of the course of the convex front and adjustment of the critical values
    of time.

    408

    PTVGROUP

    6.17.7 Route distribution in the iteration of the TRIBUT Equilibrium_Lohse

    Illustration 122: Equilibrium formation with TRIBUT

    6.17.7

    Route distribution in the iteration of the TRIBUT Equilibrium_Lohse


    The TRIBUT Equilibrium_Lohse is a modified version of the conventional French procedure,
    where procedural steps of the Equilibrium_Lohse method are used.
    Route search is also executed at the beginning of the iteration of the Equilibrium_ Lohse (see
    "Assignment with ICA" on page 374). For all resulting efficient paths, the percentage is determined via the critical values of time. All efficient paths are added to the list of best paths from
    the preceding iterations including their current percentage. For existing paths all percentages
    are added.

    6.17.8

    List outputs
    The lists Toll matrices and Toll systems are available (see User Manual: Chpt. 24.1.1 , page
    2299) that allow for the following attribute selection:

    Illustration 123: Attribute selection for the Toll systems list

    PTVGROUP

    409

    6.18 Dynamic User Equilibrium (DUE)

    Illustration 124: Attribute selection for the Toll matrices list

    6.18

    Dynamic User Equilibrium (DUE)


    The quantitative analysis of road network traffic performed through static assignment models
    yields the transport demand- supply equilibrium under the assumption of within- day stationarity. This implies that the relevant variables of the system (i.e. user flows, travel times,
    costs) are assumed to be constant over time within the reference period. Although static assignment models satisfactorily reproduce congestion effects on traffic flow and cost patterns,
    they do not allow to represent the variation over time of the demand flows (for example,
    around the rush hour) and of the network performances (for example in presence of time varying tolls, lane usage, signal plans, link usage permission). Most importantly, they cannot reproduce some important dynamic phenomena, such as the formation and dispersion of vehicle
    queues due to the temporary over-saturation of link sections, and the spillback, that is queues
    propagation towards upstream links. For these use cases, dynamic models are available.

    6.18.1

    Fields of application of dynamic equilibrium assignment


    The Within-Day Dynamic Traffic Assignment (WDDTA) models allow us to overcome the limits
    of static models. Among them, the Dynamic User Equilibrium (DUE) model embedded in
    Visum presents several new and unique features, yielding an algorithm highly efficient both in
    terms of memory usage and computing time. Thus, this model can be applied to large networks (hundreds of zones and up to one hundred thousand links and nodes) with long periods
    of analysis (possibly the entire day). It is particularly suitable for the following application
    fields.
    Simulation of heavily congested urban and extra urban networks, where oversaturation
    conditions and the back propagations of congestion among adjacent roads are present
    over a large part of the network for several hours each day.
    Simulation of networks with transient congestion effects, leading to route choice varying
    during the assignment period.

    410

    PTVGROUP

    6.18.2 Overview of the dynamic equilibrium assignment model


    Simulation of networks in presence of dynamic management and/or time varying access
    policies, such as time varying tolls, signal timing plans, lane usage permission.
    Simulation of incident effects and incident management
    Simulation of evacuation plans, in particular when the maximum evacuation time is required.
    Below you can find a complete overview of the model underlying the Dynamic User Equilibrium procedure implemented in Visum. However, in order to improve readability, any bibliographic reference is omitted, along with many analytic proofs. The bibliography contains
    references to scientific papers, underlying theories, and approaches on which this model is
    based (see "Literature" on page 784).

    6.18.2

    Overview of the dynamic equilibrium assignment model


    This model is aimed at solving the Within-Day Dynamic Traffic Assignment (WDDTA) on link
    networks addressing explicitly the simulation of queue spillovers. It is based on a macroscopic
    approach, the Dynamic User Equilibrium (illustration 125).

    Illustration 125: The dynamic user equilibrium problem


    Apart from the temporal dimension, the main difference between the static and the dynamic
    user equilibrium relates to the consistency constraints between arc and path model variables.
    While in the static case these constraints involve only the spatial dimension of the system, in
    the dynamic case they concern the temporal dimension also. More specifically, for given path
    flows, the determination of the arc flows, which in the static case requires only the arc-path incidence matrix, in the dynamic case involves also the travel times on the network; that is, the
    PTVGROUP

    411

    6.18.2 Overview of the dynamic equilibrium assignment model


    network flow propagation model depends also on the path performances (diagonal arrow in
    illustration 125).
    The present formulation of the WDDTA has three essential innovations compared to existing
    WDDTA methods:
    1. Instead of a simulation approach, it adopts a temporal profile approach, where the value of
    a given variable of the problem is determined as a function of time for the entire period of
    analysis, based on the temporal profiles of the other variables of the problem, which are
    assumed to be fixed to their current value; This approach, depicted on the right of illustration 126, has an iterative nature, since each variable has to be recalculated until a convergence is achieved.

    Illustration 126: Time slice approach (left) and time profile approach (right) to the Continuous
    Dynamic Network Loading problem
    2. Spill-back can be modeled explicitly simply by switching between two alternative network
    performance models. Without spillback, arc performance (the relationship between arc
    inflow and outflow time series) depends on the properties of that arc only; with spillback,
    capacities upstream of bottlenecks are reduced so that arc storage capacities are not exceeded (illustration 127).

    412

    PTVGROUP

    6.18.3 Mathematical framework of the Dynamic User Equilibrium


    Illustration 127: Scheme of the fixed point formulation for WDDTA with spillback congestion
    3. The path choice model can adopt either a deterministic view where only objectively leastcost paths are loaded, or a Probit view where impedances are perturbed stochastically to
    reflect subjective user perceptions.
    This approach presents several advantages:
    Consistency between path and link flows (network loading) is achieved in the same iteration as the equilibration between demand and supply. Nested loops are avoided.
    An implicit path approach generates rational path probabilities without the need to enumerate all paths.
    A major advantage of the temporal profile approach, is that the assignment period may be
    subdivided into long time intervals (typically 5-15 minutes), instead of a few seconds for
    the simulation approaches, saving computation time and memory. This allows overcoming the difficulty of solving WDDTA instances on large networks and long periods of
    analysis.
    The complexity of the algorithm is roughly equal to that of a static assignment multiplied
    by the number of (long) time intervals introduced.
    For queue spillover modeling, the interaction among the flows on adjacent arcs is propagated
    in terms of time-varying arc exit capacities. The approach is then to reproduce the spillback
    phenomenon as a hypercritical flow state, either propagating backwards - from the final section of an arc - and reaching its initial section, or originating on the latter that reduces the capacities of the arcs belonging to its backward star and eventually influences their flow states.
    The description of the dynamic user equilibrium has the following structure. First, the main
    variables underlying the continuous model are introduced, along with some significant results
    of the traffic flow theory underlying the presented model (see "Mathematical framework of the
    Dynamic User Equilibrium" on page 413). Subsequently, the network performance model and
    its submodels are described (see "Network performance model" on page 417). Then, the display of the network loading map (see "Assignment of network demand (network loading)" on
    page 427) is followed by a description of the overall Dynamic User Equilibrium model, both for
    the deterministic and Probit case (see "The overall model" on page 429). A numeric example
    including the analysis rounds off the procedure description (see "Example of dynamic user
    equilibrium" on page 431).

    6.18.3

    Mathematical framework of the Dynamic User Equilibrium


    As the analysis is carried out within a dynamic context, the model variables are temporal profiles, here represented as piecewise continuous functions of the time variable t.
    Users trips on the road network are modeled through a strongly connected oriented graph G =
    (N, A), where N is the set of the nodes and A N N is the set of the arcs. Each link, turn, and
    connector in the Visum network corresponds to an arc. Each Visum network node and zone
    corresponds with a node from G.
    Each arc a is identified by its start node (FromNode) TL(a) and by its end node (ToNode) HD
    (a).
    Thus a = (TL(a), HD(a)).

    PTVGROUP

    413

    6.18.3 Mathematical framework of the Dynamic User Equilibrium


    Example
    For an arc a representing a link in the Visum network, TL(a) would correspond to its FromNode
    and HD(a) to its ToNode. The forward and backward star of node xN are denoted, respectively, FS(x) ={aA: x = TL(a)} and BS(y) = {aA: y = HD(a)}. The zones constitute a subset Z N
    of nodes.
    When traveling from a node o N to a node dZ users consider the set K od of all the paths
    connecting o and d on G. We are interested in the n:1 many-to-one shortest path problem from
    each node oN to a given destination dZ . Graph G is assumed to be strongly connected, so
    that Kxd with xN dZ is non-empty.
    Path topology is described through the following set notation:
    A(k) = concatenated sequence of arcs constituting the path kKod from oN to dZ.
    The following notations are adopted for the network volumes.
    Dod()

    Vehicle demand, which are moving from origin oN to destination d Z and are
    departing at time

    fa()

    Vehicle flow, which at time is traversing arc aA

    Fa()

    cumulated vehicle flow, which at time is traversing arc aA

    ua()

    Exit flow from arc aA at time

    The following applies by definition:

    For the calculation of network performance, travel times are introduced through inflow-outflow functions, and the following notation is adopted.
    ca()

    Cost of traversing arc aA for vehicles entering it at time

    ta()

    Outflow time of arc aA for vehicles entering it at time

    fa

    -1()

    [27]

    Inflow time of arc aA for vehicles exiting it at time

    Ck()

    Cost of path kKod from oN to dZ for vehicles departing from node o at time

    Tk()

    Outflow time of path kKod from oN to dZ for vehicles departing from o at time

    Due to the presence of time-varying costs, it may be convenient to wait at nodes in order to
    enter a given arc later. In the following, it is assumed that vehicles are not allowed to wait at
    nodes, but instead paths with cycles may seem the better option. However, the shortest paths
    include at most a finite number of cycles.
    Since waiting at nodes is not allowed, the path exit time Tk() is the sum of the travel times of its
    arcs A(k), each of them referred to the instant when these vehicles enter the arc when traveling
    along the path. Moreover, assuming that path costs are additive with respect to arc costs, its

    414

    PTVGROUP

    6.18.3 Mathematical framework of the Dynamic User Equilibrium


    cost C k() is the sum of the costs of its arcs A(k). The outflow time or the cost, respectively, of
    path k can then be retrieved through the following recursive equations:

    [28]

    where a = (o, x)A is the first arc of k and hKxd is the remainder of path k (illustration 128).

    [29]

    Illustration 128: Recursive expressions of path exit time, entrance time and cost
    The strict First In First Out (FIFO) rule holds if the following property is satisfied for each arc
    aA:
    , for all
    t> t
    The monotonicity expressed by [30] ensures that the temporal profiles of the arc exit times
    are invertible. Moreover, the FIFO rule applies also to the entrance times.

    [30]

    , for all
    t> t
    [31]
    Any arc aA consists of a homogeneous channel with two bottlenecks located at the beginning and at the end. The flow states along the arc are determined on the basis of the Simplified Theory of Kinematic Waves (STKW), assuming the concave parabolic- trapezoidal
    fundamental diagram depicted in illustration 129, expressing the vehicle flow qa(x,) at a given
    section x of the arc and instant t, as a function of vehicle density ka(x,) at the same section and
    instant.
    The arc is then characterized by:
    La

    Length of arc a

    Qa

    Capacity of the initial bottleneck and of the homogeneous channel associated with

    PTVGROUP

    415

    6.18.3 Mathematical framework of the Dynamic User Equilibrium


    arc a, called in-capacity;
    Sa

    Capacity of the final bottleneck associated to arc a, simulating the average effect of
    capacity reductions at road intersections (i.e. due to the presence of traffic lights),
    called out-capacity Sa Qa;

    Va

    Maximum speed allowed on arc a, called free flow speed in Visum

    KJa

    Maximum density on arc a called jam density

    Wa

    propagation speed of hypercritical flow states on arc a, called hypercritical kinematic wave speed.

    Within this framework, for links the in-capacity corresponds to the physical mid-block capacity,
    whereas out-capacity reflects the bottleneck capacity imposed by the signal control or priority
    rules at the downstream junction. Exit connectors (x, d)A: xN \ Z, dZ are arcs with infinite incapacity, entry connectors (o, y) A: o Z, y N \ Z are arcs with infinite out-capacity. Turns ,
    however, are represented by arcs having zero length and in-capacity equal to their out-capacity.

    Illustration 129: The adopted parabolic-trapezoidal fundamental diagram, expressing the relation among vehicular flow, speed, and density along a given arc.
    In illustration 129, k2a k1a is assumed, implying the following relation among the above parameters:

    Based on the fundamental diagram, it is possible to identify two families of flow states.
    Hypocritical flow conditions corresponding to uncongested or slightly congested traffic.
    Under these conditions, if vehicular density increases, the vehicular flow increases also.

    416

    PTVGROUP

    6.18.4 Network performance model


    Hypercritical flow conditions corresponding to heavily congested traffic. Queues and
    stop and go phenomena occur. Under these conditions, if vehicular density increases,
    the vehicular flow decreases.
    Then, koa(q) and voa (q) express the density and the speed as functions of the flow in presence
    of hypercritical flow conditions, while ku a(q) and vua (q) express the density and the speed as
    functions of the flow in presence of hypocritical flow conditions.
    When modeling arcs with low speed limits, i.e. representing urban roads, it may be assumed
    that the vehicle speed under hypocritical flow conditions is constant and equal to the speed
    limit, until capacity is reached. In this case, the simpler trapezoidal fundamental diagram depicted in illustration 130 may be adopted, whereby in order to guarantee k2 a k1a , the following
    relation must apply:

    Illustration 130: The trapezoidal fundamental diagram suggested for urban links
    In order to implement the proposed models, the period of analysis [0, Q] is divided into n time
    intervals identified by the sequence of instants = {0, , i, , n}, with 0 = 0, i < j for all 0
    i < j n, and n = Q. For computational convenience, we introduce also an additional instant
    n+1 = .
    In the following we approximate the temporal profile g() of any variable through either a piecewise linear or a piecewise constant function, defined by the values g i = g(i ) taken at each
    instant i. This way, any temporal profile g() can be then represented numerically through
    the vector g = (g0, , gi, , gn).

    6.18.4

    Network performance model


    To represent the spillback phenomenon, we assume that each arc is characterized by two
    time-varying bottlenecks, one located at the beginning and the other one located at the end,
    called entry capacity and exit capacity respectively.
    The entry capacity, bound from above by the in-capacity, is meant to reproduce the effect of
    queues propagating backwards on the arc itself, which can reach the initial section and can
    thus induce spillback conditions on the upstream arcs. In this case the entry capacity is set to
    limit the current inflow at the value which keeps the number of vehicles on the arc equal to the
    storage capacity currently available. The latter is a function of the exit flow temporal profile,

    PTVGROUP

    417

    6.18.4 Network performance model


    since the queue density along the arc changes dynamically in time and space accordingly
    with the STKW. Specifically, the space freed by vehicles exiting the arc at the head of the
    queue takes some time to become actually available at the tail of the queue, so that the jam
    density times the length is only the upper bound of the storage capacity, which can be reached
    only if the queue is not moving.
    The exit capacity, bound from above by the out-capacity, is meant to reproduce the effect of
    queue spillovers propagating backwards from the downstream arcs, which may generate
    hypercritical flow states on the arc itself. For given arc inflows, arc outflows, and intersection
    priorities, which are here assumed proportional to the mid-block capacities, the exit capacities
    are obtained as a function of the entry capacities based on flow conservation at the node.
    The network performance model is specified here as a circular chain of three models, namely
    the exit flow and travel time model for time-varying capacities, the entry capacity model, and
    the exit capacity model, which are solved iteratively. The three models show illustration 131
    in context. The journey times which result from the solution of the three feedback model components, are combined with the monetary costs to generalized costs by an Arc Cost Model.

    Illustration 131: Scheme of the fixed point formulation for the NPM
    Exit flow and travel time models for time-varying exit capacity
    Under the condition that the FIFO rule applies and vehicles are therefore not able to overtake,
    an arc performance model with time-varying exit capacity is introduced in this section. The exit
    flow is achieved by propagating the inflow temporal profile along the arc and thus calculating
    the corresponding time-series of the travel time.
    Assuming that the capacity at the end of a given edge a A is not reduced due to spillback
    effects, for a vehicle entering the edge at time , the hypocritical exit time ra() can be expressed, dependent of the previous part of the inflow time series, which corresponds to the inflow fa
    () at any time .

    Equation [32] is described below.

    418

    [32]

    PTVGROUP

    6.18.4 Network performance model


    for the trapezoidal fundamental diagram (hypocritical exit time model for a trapezoidal fundamental diagram) (illustration 130)
    for the parabolic fundamental diagram (hypocritical exit time model for a parabolic fundamental diagram) (illustration 129)
    If, however, at the end of the edge there is a bottleneck with a time-varying capacity a() Sa
    for each time , the time series of the cumulative outflow is determined, whose value Ea() at
    time t is defined as follows:

    Where a() denotes the cumulative exit capacity at time t .

    [33]

    This means that a() - a() vehicles can exit the edge between times and .

    [34]

    The above expression [33] is based on the following specification of the FIFO rule, stating that
    the cumulative exit time at the exit instant ta() of a vehicle that enters the arc at t is equal to the
    cumulative inflow at time t. This means the following:

    [35]
    Then, equation [33] can be explained as follows: If there is no queue at a given time t, the
    travel time is equal to the hypocritical travel time, so that, based on the FIFO rule [35], the cumulative exit flow is equal to the cumulative inflow at time ra-1() when a vehicle that enters the arc
    at time ra-1() is leaving it at t. If a queue develops at time s < t, the exit flow from this point of
    time to the time where the queue breaks up, then corresponds to the exit capacity. Based on
    the FIFO rule, this results in a cumulative exit flow E a() from the cumulative inflow at time ra-1
    () plus the integral value of the exit capacity between and t, which is a()- a().
    By definition, the exit flow ea() from arc a at time t is:

    By definition, ea() a() applies at any time hypercritical exit flows occur if ea()=a().

    [36]

    Knowing the cumulative inflow and exit flow temporal profiles, the FIFO rule [35] yields an implicit expression for the arc exit time temporal profile.

    illustration 132 depicts a graphical interpretation of equation [37], where the time profile of
    the cumulative exit flow Ea() complies with the lower envelope of the following curves:

    [37]

    a) the cumulative inflow Fa(), shifted forward in time by the hypocritical travel time ra()-
    thus yielding the temporal profile Fa[ra-1()]. This represents the rate at which vehicles entering the arc arrive at its end.

    PTVGROUP

    419

    6.18.4 Network performance model


    b) for every time s, the cumulative time series of the exit capacity is shifted vertically so that
    it goes through the point (,Fa[ra-1()]). This represents the rate of vehicles that can exit the
    arc following time s. No queue is present when curve a) prevails. Queuing starts, when the
    cumulative exit flow curve falls below the time-shifted cumulative entry flow curve, this
    means that more vehicles arrive at the final section of the arc than can exit. In the diagram,
    therefore, the queue arises at time s''. In illustration 132, calculation of the exit time based
    on the cumulative time series of inflows and outflows is illustrated by thick arrows.

    Illustration 132: Arc with time-varying capacity


    Hypocritical exit time model for a trapezoidal fundamental diagram
    If the trapezoidal fundamental diagram is adopted to represent flow states on the arc, the hypocritical speed on the link is constant, and thus equation [28] is simply specified as follows.

    In this case, using [33] equation [38] can be made explicit as follows:

    [38]

    [39]
    Hypocritical exit time model for a parabolic fundamental diagram
    If the parabolic fundamental diagram is adopted, the situation becomes more complicated
    because vehicles may travel at different speeds even at hypocritical densities. If the arc inflow
    temporal profile is piecewise constant, the running link exit time can be determined at least
    approximately from the STKW. The general idea is to trace out the trajectory of a vehicle entering arc a at time t, observing the different speeds it will encounter along the arc, and determining its exit time t a(). Further below you will first find a description of the precise model. In
    cases where it might require large computational effort, it can be replaced by a simpler model
    that averages traffic conditions and thus limits the number of traffic situations encountered by
    vehicles on arc. Readers who would like to get a general feel for the model as a whole may
    just note the general idea and skip to the conclusion of this section (see "Input and output attributes of dynamic user equilibrium" on page 433).
    420

    PTVGROUP

    6.18.4 Network performance model

    Illustration 133: Flow pattern given by the Simplified Theory of Kinematic Waves
    Based on the STKW, vehicles change their speeds instantaneously. As depicted in illustration
    133, when the inflow temporal profile is piecewise constant, vehicle trajectories are piecewise
    linear. Furthermore, the space-time plane comes out to be subdivided into flow regions characterized by homogeneous flow states and delimited by linear shock waves. The slope Waij of
    the shockwave separating the two hypocritical flow states (fai) and (faj) is:

    [40]
    In theory, given a piece-wise constant inflow time series, it is possible to determine the trajectory of a vehicle entering the arc at instant t, and thus its hypocritical exit time ra (). illustration 133 shows that it may actually be extremely cumbersome to determine these
    trajectories.
    Many shockwaves may be active on the arc at the same time.
    Shockwaves may be generated either at the initial section by flow discontinuities at times
    i, 0 i n-1, or by shockwave intersections on any arc section at any time.
    A vehicle may cross many shockwaves while traveling on the arc, and all the crossing
    points have to be explicitly evaluated in order to determine its trajectory.
    In order to overcome these difficulties, as depicted in illustration 134, we assume that at each
    instant r i, 0 i n-1, a fictitious shockwave is generated on the initial arc section separating
    the actual flow state (fai+1) from a region with the average speed i=L/(rai- i) of the vehicle
    that reaches the arc at time i.
    Fictitious shockwaves are very easy to deal with due to the following reasons:
    They never meet each other, and thus are all generated on the current initial link section
    only at time i, 0 i n-1.

    PTVGROUP

    421

    6.18.4 Network performance model


    Each vehicle meets at the most the last generated fictitious shockwave, so that its trajectory is very easy to be determined.
    Based on [36], slope Wai of the fictitious shockwave is as follows:

    [41]

    Illustration 134: Flow pattern given by the Averaged Kinematic Wave model
    Note that the trajectory of a vehicle entering the current link at time (i-1, i] is directly influenced only by the mean trajectory of the vehicle entered at time i-1, which synthesizes the previous history of flow states on the link.
    The approximation introduced has little effect on the model efficacy. Moreover, it satisfies the
    FIFO rule, which is still ensured between the arc initial and final sections, while local violations
    that may occur within intermediate sections are of no interest.
    Based on the above, the hypocritical travel time a i= a()i, 0in-1 can be specified as follows:
    a) If a vehicle entered at time i does not meet the fictitious shockwave Wai-1 before the end
    of the arc, its hypocritical exit time is simply:
    .
    Here, fai is the arc inflow during time interval (i-1,i].
    b) Otherwise, its hypocritical exit time is determined on the basis of the two speeds it assumes before and after crossing the fictitious shockwave.
    .
    where i is the travel time of the vehicle before it reaches the fictitious shockwave (illustration 135).
    .

    422

    PTVGROUP

    6.18.4 Network performance model

    Illustration 135: Determination of the arc hypocritical exit time


    Then, the hypocritical travel time ra() specifying [32] is:

    [42]
    Entry capacity model
    In this section we propose a new approach to represent the effect on the entry capacity of
    queues that, generated on the arc final section by the exit capacity, reach the arc initial section, thus inducing spillback conditions. This part of the model is used only if DUE is run with
    the spillback option activated (see User Manual: Chpt. 18.5 , page 1925). If the option is turned off, the storage capacity of an arc is assumed to be infinite, and the entry capacity of a link
    is never reduced below the in-capacity.
    To help understand let us assume, for the moment, that the queue is uncompressible, that
    means, only one hypercritical density exists. Then, the kinematic wave speed is infinitive
    from either illustration 129 or illustration 130 it is clear that wa = with KJa =k2a so that any
    hypercritical flow state occurring at the final section would back-propagate instantaneously.
    This circumstance does not imply that the queue reaches the initial section instantaneously.
    There, the exiting hypercritical flow state does actually not affect the entering hypocritical flow
    state until the arc has filled up completely. This means, that the cumulative number of vehicles
    that have entered the arc equals the number of vehicles that have exited the arc plus the storage capacity. The latter in this case is constant in time and given by the arc length multiplied
    by the maximum queue density. As soon as the queue exceeds the arc length, the entry capacity becomes equal to the exit capacity, that means, all vehicles on the arc move as one rigid
    object.
    In reality, hypercritical flow states may actually occur at different densities. Their kinematic
    wave speeds are not only lower than v0, implying that the vehicles will reach the first arc section with a delay when starting from the final section, but also somewhat different from each
    other, which generates a distortion in their forward propagation in time. Notice that the fundamental diagrams adopted here are capable of representing the dominant delay effects but
    not the distortion effects, since all backward kinematic waves have the same slope.

    PTVGROUP

    423

    6.18.4 Network performance model


    The spillback effect on the entry capacity is investigated by exploiting the analytical solution of
    the STKW. The flow state occurring on an arc section is the result of the interaction among
    hypocritical flow states coming from upstream and hypercritical flow states coming from downstream. Specifically, on the initial section, the one flow state coming from upstream is the
    inflow, while the flow states coming from downstream are due to the exit capacity and can be
    determined by back-propagating the hypercritical portion of the cumulative exit flow temporal
    profile, thus yielding what we refer to as the maximum cumulative inflow temporal profile.
    According to the Newell-Luke minimum principle, the flow state consistent with the spillback
    phenomenon occurring at the initial section is the one implying the lowest cumulative flow.
    Therefore, when the cumulative inflow equals or overcomes the maximum cumulative inflow,
    so that spillback actually occurs, the derivative of the latter temporal profile may be interpreted
    as an upper bound to the inflow. This enables the determination of the proper value of the
    entry capacity that maintains the queue length equal to the arc length.
    The instant a() when the backward kinematic wave generated at time on the final section of
    arc aA by the hypercritical exit flow ea()=a() would reach the initial section is given as follows.

    [43]
    By definition the points in time and space constituting the straight line trajectory produced
    by a kinematic wave are characterized by a same flow state. Moreover, illustration 136 shows
    that the number of vehicles encountered by the hypercritical wave relative to the exit flow q for
    any infinitesimal space ds traveled in the opposite direction is equal to the time interval d s
    multiplied by that flow. Therefore, integrating along the arc from the final
    to the initial section, we obtain the maximum cumulative flow Ha() that would be observed at
    time a() in the initial section as:
    ( )=
    Ha

    [44]

    Illustration 136: Trajectories of a hypercritical kinematic wave and of the intersecting vehicles

    424

    PTVGROUP

    6.18.4 Network performance model


    In the fundamental diagrams adopted here, the hypercritical branch is linear and therefore a
    () is invertible. Since wa (q)=w a is the time at a () = , based on[43], =- L a/w a . Furthermore, Ha() = Ea() + La KJa results, based on [44] q/va(q)=KJa- q/wa. Therefore, the maximum cumulative inflow G a ( ) that could have entered the arc at time t due to the inflow
    volume is given by the following equation:

    [45]
    If the cumulative inflow Fa() at time t equals or exceeds the maximum cumulative inflow
    Ga(), so that spillback occurs at that instant, then the entry capacity a() is given by the derivative dGa()/d of the latter; otherwise, it is equal to the in-capacity Qa.
    Differentiating Ga() implies the following:
    =
    From ea(-La/wa), the following applies:

    [46]
    illustration 137 shows how, based on equation [45], the time series of the maximum cumulative inflow can be obtained graphically through a rigid translation (thick arrows) of the cumulative exit flow time series for L a / wa in time and for L a KJa in value. Moreover, it points out
    that, if Ga() is greater than Fa(), the queue is shorter than La and a() = Qa.
    Otherwise spillback occurs and a()=a(- La/wa).

    PTVGROUP

    425

    6.18.4 Network performance model

    Illustration 137: Graphical determination of the time series of the inflow capacity in the case of
    triangular fundamental diagram, piecewise constant inflow, and constant exit capacity
    Exit capacity model
    In this section we present a model to determine, for a given node, the exit capacities of the upstream arcs, on the basis of the entry capacities of the downstream arcs and of the turn volumes. Only two node forms occur in the graph that is formed on the basis of the Visum network.
    These are joining links and diverging links. In this case, the model can be described by the
    inflows and outflows of edges.
    When considering joining links xN, that is an intersection with a singleton forward edge, the
    problem is to split the entry capacity b () of the edge b = FS(x) available at time t among the
    edges belonging to its backward edge, whose outflows compete to get through the intersection. In principle, we assume that the available capacity is distributed proportionally to the
    out-capacity Sa of each arc aBS(x) . But this way it may happen that on some arc a the outflow
    a() is lower than the share of entry capacity assigned to it, so that only a lesser portion of the
    latter is actually exploited. The rest of the entry capacity is then partitioned among the other
    arcs. Moreover, when no spillback phenomenon is active, the exit capacity () is set equal to
    a
    the out-capacity Sa.
    When considering diverging links x N, that is an intersection with a single backward edge,
    the exit flow of this edge a = BS(x) is determined by the most restrictive entry capacity among
    the forward edges. If no arc is spilling back, the exit capacity is set equal to the out-capacity. If
    426

    PTVGROUP

    6.18.5 Assignment of network demand (network loading)


    only one arc bFS(x) is spilling back, that is fb () b(), then the exit capacity a() scaled by
    the share of vehicles turning on arc b is set equal to the entry capacity of b in order to ensure
    capacity conservation at the node while satisfying the FIFO rule a()fb()/a()=b () applied to the vehicles exiting from arc a. If more than one arc bFS(x) is spilling back, the exit
    capacity is the most penalizing among the above values. On this basis, the following equation
    is derived:

    [47]
    Note that, in contrast with the models presented in the previous two sections, this model is
    spatially non-separable, because the exit capacities of all the arcs belonging to the backward
    star of a same node are determined jointly, and temporally separable, because all relations
    refer to a same instant.
    It is assumed that vehicles do not occupy the intersection if they cannot cross it due to the presence of a queue on their successive arc, but wait until the necessary space becomes available. Indeed, this model is not capable of addressing the deterioration of performances due to a
    misusage of the intersection capacity.
    Arc Cost Model
    The cost for vehicles entering arc a at time t is given as follows:

    Here, ma() describes the monetary costs, and represents the value of time.

    6.18.5

    [48]

    Assignment of network demand (network loading)


    In this section we develop a formulation for the dynamic Network Loading Map with implicit
    path enumeration in the case of deterministic route choice model. To this end, we will firstly
    define and address the continuous dynamic shortest path problem, which lies at the heart of
    the route choice model.
    Continuous dynamic shortest path problem
    Contrary to the static case, in the dynamic context the shortest path problem involves explicitly
    the time dimension, since the costs of the arcs constituting a path are to be evaluated at different instants, consistently with the travel times experienced along the path, as induced by the
    recursive equation [29]. Then the minimum cost wo d() between each node oN and a given
    destination dZ are determined for users departing at time t.
    wod() = min{Ck(): k Kod}
    It can be proven that the following dynamic version of the Bellman relation for each node
    oN (illustration 138) is equivalent to problem [49].
    ( ) = min
    wo d

    PTVGROUP

    [49]

    [50]

    427

    6.18.5 Assignment of network demand (network loading)

    Illustration 138: Dynamic version of the Bellman relation


    The set of Bellman relations [50] can be solved using a dynamic programming approach described below.
    Path choice and network flow propagation models
    Under the assumption that users are perfectly informed rational decision-makers, the resulting
    behavior is such that only shortest paths are utilized. The deterministic route choice model for
    users traveling at time t from origin oN to destination dZ can then be formulated through the
    following extension of the dynamic case of Wardrops first principle:
    If path k Kod is used, i.e., its choice probability Pk() is positive, then its cost Ck() is equal
    to the minimum cost wod(), to travel from o to d departing at time t.
    Vice versa, if path k is unused, i.e., its choice probability is zero, then its cost may not be
    smaller than the minimum cost.
    This can be formally expressed as follows:

    Moreover, the choice probabilities must be non-negative and amount to 1.

    [51]

    We now develop a formulation based on implicit path enumeration for the route choice model
    and for the corresponding network flow propagation model adopting the temporal- layer
    approach, where the temporal perspective is the exit time from the current node.
    If the shortest paths from oN to dZ for users departing at time t involve more than one arc exiting from an intermediate node x, then the conditional probabilities of these arcs at time t for
    users directed to d could depend, in general, on the sub-path utilized from each o to x.
    Because of the additive nature of arc costs, we assume instead that the arc conditional probabilities at each node are equal for all users directed to the same destination regardless of
    the sub-path so far utilized.
    Under this assumption, the choice probability Pk () of a path k Kod from oN to dZ for users
    departing at time t is equal to the product of the conditional probabilities of its arcs A(k), each of
    428

    PTVGROUP

    6.18.6 The overall model


    them referring to the time when these users enter the arc when traveling along the path. The
    choice probability of k can be then retrieved through the following recursive expression:

    where (o, x) is the first arc of k and h Kxd is the rest of path k.

    [52]

    The dynamic Wardrop condition is satisfied when the conditional probabilities of the edges are
    calculated as follows.

    [53]

    [54]
    [55]
    Equation [49] states that road users exiting node oN at time t and are heading toward
    d Z, among the forward stars FS(o), may only choose an arc (o, x) for which the total of arc
    costs Cox() and minimum costs wxd(tox()) correspond to the minimum costs wod() for the remaining path to the destination. In x, the passage time is tox() here.
    The flow fox d() of vehicles directed to destination dZ that enter the arc (o, x)A at time t is
    given by the arc conditional probability poxd() multiplied by the flow exiting from node o at time
    t. The latter is given, in turn, by the sum of the outflow uyod() from each arc (y, o)BS(o) entering
    o, and of the demand flow Dod() from o to d. This results in the following equation:

    Applying the FIFO and flow conservation rules, the outflow from y at time can be expressed in terms of the inflow at a at time tyo-1().

    [56]

    [57]
    where the weight dtyo()/d stems from the fact that travel times vary over time, so that users
    exit from y at a certain rate and, in general, enter in o at a different rate, which is higher than
    the previous one, if the arc travel time is decreasing, and lower, otherwise.
    The total inflow and outflow of arc (o, x)A at time t are then:

    [58]

    6.18.6

    The overall model


    All the components of the dynamic user equilibrium procedure have been introduced. Here we
    formulate the user equilibrium, where no user can reduce his perceived travel cost by uni-

    PTVGROUP

    429

    6.18.6 The overall model


    laterally changing paths, described as a fixed point problem in the temporal profiles of the arc
    inflows and outflows.
    The deterministic case
    Formulation of the implicit path enumeration yields the model depicted in illustration 139.

    Illustration 139: Variables and models of fixed point formulations for the network performance
    model (left) and for dynamic assignment with spillback (right)
    In analogy with the static case, the Network Loading Map (NLM) is a functional relation yielding, for given demand flows D, an arc flow pattern f consistent with the arc performances t,
    and c , through the deterministic route choice model p (w(c, t), t, c), and the network flow propagation model (p, t; D). The assignment uses an implicit path enumeration and is based on
    the minimum costs w from each node to destination, as well as on the resulting conditional probabilities p of the edges. In turn, the arc performance model yields the arc exit time pattern t,
    and the arc cost pattern c , consistent with the arc inflows f and arc outflows u. The deterministic equilibrium results from the feedback of network loading map and arc performance
    model.
    The Probit case
    In the Probit route choice model, which is based on the random utility theory, the arc costs perceived by users are not known with certainty and are thus regarded as independent random
    variables. We extend the Probit model to the dynamic case, assuming that the arc cost a () of
    arc aA perceived by users at timet is equal to the sum of the arc cost ca() yielded by the arc
    performance model and of a time-varying random error, whose value at time t is distributed as
    430

    PTVGROUP

    6.18.7 Example of dynamic user equilibrium


    a normal variable. Its variance is assumed proportional to a time-varying cost term a () > 0
    and independent of the load case.
    The arc flow pattern resulting from the evaluation of the Probit NLM for given arc performances
    is obtained through the well-known Montecarlo method as follows:
    1. Get a sample of H perceived arc cost patterns.

    Applies in compact form

    [59]
    where each a() is extracted from a standard normal variable N[0,1] and h = 1, , H.
    2. For each perceived arc cost pattern of the sample, determine with the deterministic NLM a
    consistent arc inflow pattern.
    3. Calculate the mean of the resulting deterministic arc inflow patterns, thus obtaining an
    undistorted estimation of the Probit arc inflow pattern.
    Note that according to equation[59], the entire time series a h() is disturbed with one random
    number. This means the estimation error of road users does not depend on the time of day.
    This is consistent with the behavior of users, who perceive the arc cost temporal profile as a
    whole. On the contrary, the travel times that underlie the network flow propagation, are considered as constant throughout the simulation.

    6.18.7

    Example of dynamic user equilibrium


    In order to investigate the behavior of the proposed model and to show the effect of spillback
    on path choice, we analyze a simple example which presents intuitive solutions. The example
    is provided with Visum and is located in the Training folder, under DUE, as Braess_without_
    spillback.ver and Braess_with_spillback.ver.
    The following refers to the Braess network depicted in illustration 140 . Links have the characteristics reported in the corresponding table, and are all modeled with a parabolic- trapezoidal fundamental diagram. All link out-capacities are set equal to the corresponding incapacities. The turn capacities are QAC =Q AE=Q ED =2000veh/h and Q BD=Q CF =QDF =
    1000 veh/h.
    Link

    La[km]

    Qa [veh/h]

    Va [km/h]

    Wa [km/h]

    1 / Ka[m]

    0,4

    2,000

    50

    15

    7.0

    0.6

    2,000

    50

    15

    7.0

    0.6

    2,000

    50

    15

    7.0

    0,4

    2,000

    50

    15

    7.0

    0,4

    2,000

    50

    15

    7.0

    0.1

    4,000

    50

    15

    3.5

    PTVGROUP

    431

    6.18.7 Example of dynamic user equilibrium


    The assignment period is constituted by 100 intervals of 1 minute. For the first 33 minutes of
    simulation, constant demand flow from node 1 to node 5 is assumed, which equals D 15 =
    2,300 veh/h.

    Illustration 140: Example network


    The results of two assignment runs, one without and the other with spillback congestion, are
    presented in illustration 141 . Without spillback, the congestion is evenly located only on turns
    CF and DF (which can be gathered observing turn travel times), so that on all the paths between node 1 and node 5 the queue is about equal, and path A-E-D-F has fewer users since it
    is clearly not convenient. With spillback, however, the queue propagates from turn CF to arc C
    and up to arc A, and from turn DF to arc D and up to arcs B and E. Moreover, the spillback
    effect is greater on arc B than on arc E because of the different capacities of turn ED and turn
    BD. Then, after an initial growth, the travel time on arc D remains constant, since congestion is
    propagated upward, while the travel time on arc B grows faster than the travel time on arc E,
    so that path A-E-D now becomes competitive, as it implies a longer route but a lower travel
    time. That is why the flow on arc E increases from around 150 veh/h to 670 veh/h approximately.

    432

    PTVGROUP

    6.18.8 Input and output attributes of dynamic user equilibrium

    Illustration 141: Results of dynamic equilibrium assignment with and without spillback

    6.18.8

    Input and output attributes of dynamic user equilibrium


    This method computes an equilibrium assignment over a given assignment period, given both
    time-varying demand and time-varying supply.
    Input Supply
    The available network is defined as usual by nodes, links, turns, zones, and connectors (optionally also main nodes and main turns). The attributes listed in table 158 are relevant for DUE.
    Network
    object

    Attribute

    Optionally timevarying

    Link

    TSysSet

    Length

    v0 PrT

    Capacity PrT

    Toll_PrTSys

    DueVWave

    DueFunDiag

    SpacePerPCU

    LinkSpacePerPCU

    Comment

    in [veh/h]
    See below for explanation of link impedance

    Out capacity PrT

    in [veh/h]

    Link type

    vMax_PrTSys

    Maximum speed per


    transport system on
    any link of this type

    Turn

    TSysSet

    t0 PrT

    Main turn

    Zones

    PTVGROUP

    Capacity PrT

    TSysSet

    in [veh/h]

    t0 PrT

    Capacity PrT

    in [veh/h]

    SharePrTOrig/Dest*)

    Do connectors have
    shares{Yes/No}

    433

    6.18.8 Input and output attributes of dynamic user equilibrium


    Network
    object

    Attribute

    Optionally timevarying

    Connectors

    t0_TSys

    Weight*)

    Comment

    Connector share, if
    enabled for zone

    Table 158: Input attributes for the DUE procedure


    *) MPA only: affecting each OD pair
    Some of the attribute can be temporarily restricted. These attributes will then have a default
    value, but may assume a different value during a given interval within the assignment period.
    The transport system set and the connector shares have the same meaning as in all other assignment methods.
    Impedances are handled in a special way in DUE (see "Network performance model" on page
    417). In particular, link travel time is the sum of t0 with free flow and a wait time at the bottleneck which is assumed to be located at the end of the link. The free-running travel time t0
    depends on a flow-density fundamental diagram. The fundamental diagram can have one of
    two different shapes which differ in the sub-critical branch, this means, where density is less
    than the critical density (at which maximum flow is reached). The shape is defined by the link
    attribute DueFunDiag.
    In the case of urban links, a trapezium shaped fundamental diagram is recommended. In this
    type of diagram, the hypocritical branch is linear, which means that vehicles travel at free-flow
    speed v0 (on the free-running part) until capacity is reached. illustration 142 illustrates how the
    shape of the diagram is determined by the link attributes.

    Illustration 142: Shape of the fundamental diagram based on link attributes


    Notice that the jam density is the maximum number of vehicles per 1 km of link length. For a
    single-lane link a typical value for SpacePerPCU would be around 7 m, resulting in a jam density of ~140 vehicles / km.
    In order for the fundamental diagram to be well-defined, the sub-critical and hyper-critical branches must not overlap. Therefore the link attributes must satisfy the condition:
    Capacity PrT (1 / v0 + 1 / DueVWave) 1000 / LinkSpacePerPCU
    For freeway links, the assumption of constant sub-critical speed is not always justified, and an
    approach similar to volume-delay functions appears more suitable.

    434

    PTVGROUP

    6.18.8 Input and output attributes of dynamic user equilibrium


    In this type of diagram, the sub-critical branch is parabolic (illustration 143), speed decreases
    from v0 at free flow to 0.5 v0 at capacity, and the flow-density curve reaches capacity with zero
    derivative. The validity condition for the attributes then becomes
    Capacity PrT (2 / v0 + 1 / DueVWave) 1,000 / LinkSpacePerPCU.
    All other properties are identical to the sub-critical linear case.

    Illustration 143: Parabolic sub-critical branch in the fundamental diagram


    The wait time at the end of the link is a function of the bottleneck capacity. This is defined for
    each turn by turn attribute Capacity PrT. To work correctly with DUE, turn capacities should be
    determined in the following way:
    First, determine the saturation capacity of each lane of the upstream arc, as the lane capacity multiplied by the green time fraction (g/c) corresponding to that lane in the case of a
    signalized intersection, or by some suitable multiplier in case of non-prioritized approach
    at a non-signalized intersection.
    Then, determine each turn capacity as the sum of the capacities of lanes allowed for the
    corresponding maneuver.
    Note: In case of lanes allowed for more than one maneuver, the corresponding lane
    capacity is not to be split among the corresponding turns, but is to be entirely assigned to
    each turn corresponding to the allowed maneuvers. In this case in fact, DUE will, based
    on the turn flows resulting from WDDTA, internally identify the actual capacity to be assigned to each turn.
    Example

    Illustration 144: Signalized intersection in reality

    PTVGROUP

    435

    6.18.8 Input and output attributes of dynamic user equilibrium


    The signalized intersection in illustration 144 , with lane capacities = 1,800 veh/h, a signal
    cycle = 90 s, and green fractions, should be implemented in Visum as shown at the bottom of
    illustration 145. The turns approaching from the West have the following capacities:
    turn 1 (1 lane allowed): Q1 = 1,800 30 / 90 = 600 veh/h
    turn 2 (2 lanes allowed): Q2 = 1,800 45 / 90 + 1,800 45 / 90 = 1 veh/h
    turn 3 (1 lane allowed): Q3 = 1,800 45 / 90 = 900 veh/h
    Whereas the capacity of the right lane, which can be used to go either straight or right, is
    added both to the straight turn capacity and to the right turn capacity.

    Illustration 145: Diagram of the signalized node in Visum


    For the compensation of the turn capacity overestimation due to shared lanes the out capacity
    PrT of the incoming link from the West can be set, by adding up the saturation flow rate and the
    green ratio by lane for example:
    S = 1,800 30/90 + 1,800 45/90 + 1,800 45/90 = 2,400
    Note: For the PrT lane capacities and/or the link out capacity you can define time-varying
    values. In this way, you can model the effects of various green time splits depending on
    the time of day.
    Input Demand
    DUE accepts a description of time-varying demand. Like elsewhere in Visum, this description
    can take two possible forms:
    Total demand matrix with a demand time profile which assigns percentage shares of the
    total matrix to time intervals.
    A demand time profile in which each time interval refers to a different demand matrix.
    If the assignment time interval including the extension exceeds one day you need to use the
    calendar add-on.
    DUE is a multi-class assignment method, this means, multiple demand segments, each with its
    own demand description, can be assigned in a single run.
    Overview of all input attributes
    table 159 shows an overview of all relevant input attributes for DUE.

    436

    PTVGROUP

    6.18.8 Input and output attributes of dynamic user equilibrium

    Table 159: Input attributes for dynamic user equilibrium


    The abbreviations represent the following:
    x2

    Toll-PrTSys has to be inserted manually in the impedance function (part of the


    procedure parameters) to have an effect

    x3

    Optionally time-varying

    Output attributes of the Dynamic user equilibrium


    The results of the operation are available through link, turn, main turn and connector attributes
    for volume and impedance. In particular, volumes are available as totals or by demand segment or transport system, and in vehicles, PCU, or persons. Both volumes and impedances
    are given by analysis time interval.
    The definition of queue lengths as a measure of oversaturation is not easily defined, as in the
    DUE model queues may move and only gradually approach the situation where traffic is at a
    standstill at queue density. Because queues move (at a speed depending on the hyper-critical
    PTVGROUP

    437

    6.18.9 References to the appropriate modeling for a DUE assignment


    branch of the fundamental diagram), and separation between vehicles (density) is not constant, it would furthermore be misleading to speak of queue length in meters. Therefore we
    adopt a definition which is similar to congestion hits in more microscopic simulations. The
    value of the queue length (for a given link and time interval) is the number of vehicles experiencing hyper-critical delay, i.e. spend more time on the link than the free-running link travel
    time resulting from v0 plus the sub-critical wait time at the bottleneck (e.g. waiting for the next
    green time in the cycle).
    table 160 provides an overview of all DUE output attributes.

    Table 160: Output attributes of the Dynamic user equilibrium


    The abbreviations represent the following:
    x1

    6.18.9

    Totals for assignment period and values per time interval

    References to the appropriate modeling for a DUE assignment


    Since incorrect network modeling might lead to dramatic effects in the dynamic user equilibrium procedure you should be aware of the following:
    Link capacity = Saturation flow rate. The lane-specific value has to be multiplied by the
    number of the link's lanes.
    Bottle-necks at nodes due to control strategies, for example, have to be modeled as turn
    capacities. On the one hand, the latter allow for congestion modeling by overloaded turns,
    on the other hand, the inflow in overloaded links upstream can be controlled.
    The out capacity of links can be used to correct the impact of shared lanes on turn capacities. Shared lanes are neglected when turn capacities are defined which causes an

    438

    PTVGROUP

    6.19 Dynamic stochastic assignment


    overestimation in the sum of the capacities of the link's exit turns. If the turn capacities are
    not modeled in detail, the out capacities should be defined in any case.
    Zones have to be connected in the subordinate network. To avoid unwanted network
    inflow effects it is even recommended to add links and thus make it possible to connect
    zones to one-leg nodes.
    For the assignment, time intervals of only 5 - 15min are recommended. This also applies
    if you are interested in hourly values for the analysis. In this case, different intervals can
    be defined the assignment time interval and the analysis time intervals.
    The assignment time interval and the time extension have to be defined appropriately, all
    vehicles need to be able to reach their destinations within this time range. When the assignment comes to an end, at least in the last interval, the volumes of all network objects
    should be zero.
    It is recommended to activate the option Blocking back model not until plausible results
    without spill-back could be reached. Even if this option has not been checked, queue
    length data is calculated and displayed, but these lengths represent vertical congestions,
    which do not spill back. This data can help to identify possible network modeling deficiencies. Also spill-backs on connectors over several time intervals identify shortcomings
    in network or demand modeling which have to be corrected by the user.
    We recommend to adjust the standard parameter settings for the termination conditions,
    since the early termination of the assignment could return incorrect results.
    With extensive models, the storage of paths is not recommended. This will reduce the
    memory requirements and furthermore the run time will be improved.

    6.19

    Dynamic stochastic assignment


    The dynamic stochastic assignment differs from all other PrT assignment procedures as a
    result of the explicit modeling of the time required to complete trips in the network. For dynamic
    stochastic assignment - capacity has to be set as an hourly value - not regarding the length of
    the time interval the demand is available for.
    The dynamic stochastic assignment takes time-varying attributes of traversed links, turns,
    main turns and connectors into account (t0, tCur, VolCapRatio per time interval, that
    result from their temporary attributes, for example, Capacity and v0 or t0).
    The dynamic stochastic assignment provides the calculated results, for example volume
    or impedance of the connections (routes in time interval) and of their traversed network
    objects, which means links, turns, main turns and connectors, for each user-defined time
    interval. Since the impedance equals the congested travel time in most applications, time
    profiles for the assignment period can be generated this way. For the routes, tolls and
    AddValues are additionally issued for each time interval.
    In contrast, all trips are completed in the case of static assignment procedures with no indication of the time required, capacities have to be specified according to the length of the time
    interval demand data is available for, and the volumes of all trips and the resultant impedances are superimposed upon each other at the individual network objects. Road-users subsequently only have to choose from a number of different routes for each journey. The
    departure time is irrelevant.

    PTVGROUP

    439

    6.19 Dynamic stochastic assignment


    In the case of the dynamic assignment on the other hand, an assignment period T (e.g. 24
    hours) is specified and divided up into time slices Ti of equal length (e.g. 15 minutes). Only the
    search for (alternative) routes for each journey is made with no reference to a specific time. As
    in the case of the static stochastic assignment, several shortest path searches are completed
    with network impedances that vary at random. All other operations explicitly include a time
    dimension. As with stochastic assignment, further random searches may be carried out (see
    User Manual: Chpt. 18.6.10.2 , page 1978).
    From the entire demand and its temporal distribution curve, the portion with a desired departure time is determined for each time slice within this time interval. On the supply side, there
    are pairs to choose consisting of route and departure time interval, which, using PuT assignment terminology, are also called connections. The impedance of a connection is composed of its network impedance and the difference between the actual and desired departure
    time slice (temporal utility). To determine the network impedance, the volume and the capacity-dependent travel time for each network element are stored separately for every time slice.
    The progress time of the trip through the network is decremented along the route, whereby for
    each network element the travel time of the time slice (s) in which the network element is traversed is relevant.
    illustration 146 shows qualitatively the procedure for calculating impedances along the timepath line of the connection.
    In this case, S (= faSt) and L (= sLow) represent the capacity-dependent speed of the network
    element in the relevant time slice. The correct path of the trip and thus the correct network
    impedance of the connection results only when the travel time on each link (B in particular in
    this case) is included with respect to the time slice reached at this moment.

    Illustration 146: Example of impedance calculation of a connection


    After assignment to individual connections, the network elements are loaded with the demand
    for each time slice as in the case of the impedance calculation, which results in new network
    element impedances. It is assumed that the departure times of the individual trips are equally
    distributed within the time slice, this means, instead of a single time-path line, a volume range
    is decremented (example illustration 147).

    440

    PTVGROUP

    6.19.1 Evaluation of dynamic stochastic assignment

    Illustration 147: Example of network volume along a connection

    6.19.1

    Evaluation of dynamic stochastic assignment


    The dynamic assignment permits the analysis of the analysis of temporary overload effects in
    the network. Depending on the time-dependent capacity, not only are different routes chosen
    at different times, but if necessary the actual departure time is shifted with respect to the desired departure time. The procedure is therefore ideal for calculating distribution curves of the
    volume on network objects.
    On the other hand, the use of the procedure requires a temporal layering of the demand using
    a distribution curve over the assignment period.

    6.19.2

    Input and output attributes of dynamic stochastic assignment


    To execute the dynamic stochastic assignment, certain entries have to be made. Die table 161
    provides an overview of the input attributes that have to be maintained. After calculation, the
    results are available in the output attributes and can be displayed in the list view (see User
    Manual: Chpt. 24.1 , page 2299) or in the network editor (see User Manual: Chpt. 24.2 , page
    2337). table 162 lists the output attributes to which the procedure results are saved.

    PTVGROUP

    441

    6.19.2 Input and output attributes of dynamic stochastic assignment

    Table 161: Input attributes of dynamic stochastic assignment

    442

    PTVGROUP

    6.19.3 The procedure of dynamic stochastic assignment

    Table 162: Output attributes of dynamic stochastic assignment


    The abbreviations represent the following:

    6.19.3

    x1

    Totals for assignment period and values per time interval

    x2

    Toll-PrTSys has to be inserted manually in the impedance function (part of the


    procedure parameters) to have an effect

    x3

    Optionally time-varying

    Generally possible, however not recommended

    (X)

    Can be used optionally

    (*)

    Apart from the parameters which are directly set in the assignment procedure

    The procedure of dynamic stochastic assignment


    The procedure in illustration 148 maintains the sequence of static stochastic iteration and differs essentially in the use of substeps for connections instead of for routes. It is broken down
    into an external iteration for the connection search and an internal iteration for the connection
    choice and network loading.

    PTVGROUP

    443

    6.19.3 The procedure of dynamic stochastic assignment

    444

    PTVGROUP

    6.20 NCHRP 255

    Illustration 148: The procedure of dynamic stochastic assignment

    6.20

    NCHRP 255
    This postprocessor for PrT assignments is an add-on module used to correct assignment volumes on links and turns of the forecast by means of a correction factor, which is calculated on
    the basis of the differences between traffic counts and an assignment, both representing the
    same time slice, as is described in Report 255 (National Cooperative Highway Research Program).
    The procedure comprises the following steps:
    1. The count values of the incoming link at the node result from totaling the turn count values
    for the corresponding From Link.
    2. Calculate the difference between the link base count (as input by the user) and the value of
    the link base assignment value.
    3. Calculate the adjusted link volumes as the future link assigned value + the adjustment factor.

    PTVGROUP

    445

    6.21 Assignment analysis PrT


    4. Furness (balance) the new link adjusted volumes to match the counted turn volumes. The
    result is turns that add up to the new link volume totals, but that have the percentage split
    (or distribution) found in the turn counts. The Furness process is iterative.
    5. The postprocessed link and turn volumes are stored in a user-specified link or turn attribute.

    6.21

    Assignment analysis PrT


    Assignment analysis is used for calculating the correlation (Goodness-of-Fit Report) between
    calculated and observed attribute values of a selected network object type.
    The calculated value is derived from the assignment or the network model.
    The observed value may be count data or measured data.
    Here are some examples:
    Travel time comparisons between PrT and PuT
    Travel time comparisons of different scenarios
    Calculated and counted volumes (links, turns or main turns)
    Calculated and measured speeds
    Any numeric input or output attributes of the following network objects can be selected:
    Links
    Node
    Turn
    Main nodes
    Main turns
    Lines
    Line routes
    Screenlines
    Time profiles
    Paths
    Prerequisite is, that the observed values must be >0 for the selected network object type.
    You can select which objects you want to include in the assignment analysis. There are three
    possibilities:
    All objects of the selected network object type
    Only active objects
    Only objects with observed value > 0
    For the assignment analysis, as an option, you can consider user-defined tolerances for userdefined value ranges of the calculated attribute.
    The quality of the correlation can be determined and issued in two ways:
    in groups (for each value of the classification attribute)
    collectively for all included network objects
    For the output, the data model of the network object types above has been supplemented with
    the calculated attribute Assignment deviation (AssignDev ) of type real. Alike all other Visum

    446

    PTVGROUP

    6.21 Assignment analysis PrT


    attributes, the attribute can be graphically displayed and issued in lists of the respective network object.
    In addition, Visum calculates various indicators (per group or collectively) that can be issued in
    a list or in a chart.
    Note: An assignment result is no longer necessary in order to calculate the correlation
    coefficient.
    table 163 shows the calculation rules for the output attributes of assignment analysis. To the
    formulas applies:
    Z

    Observed value (counts or measures)

    Calculated value (assignment or network model)

    Number of objects with observed value > 0

    AbsRMSE
    Abs RMSE

    Absolute root of mean square deviation


    Significant differences between counted and modeled values have
    a higher impact according to

    Intercept
    Intercept

    Coefficient b in linear regression


    Cf. Excel, linear regression (y = ax + b)

    ShareAccGEH
    Share with acceptable GEH

    Percentage objects with acceptable GEH value (per network


    object)

    ShareAccRelErr
    Share with acceptable relative errors

    Percentage objects within tolerance

    NumObs
    Number of observations

    Number of observations per class (objects with observed value >


    0)

    NumClass
    Number in class

    Total number (=observed + not observed) objects per class

    ClassVal

    Value of classification attribute (or blank, if not classified)

    Corr

    Correlation coefficient (cf. Excel function Pearson)

    PTVGROUP

    447

    6.21 Assignment analysis PrT


    Notes
    The value range lies between -1 and 1, where the following applies:
    -1 = observation opposed to modeling
    0 = no correlation (at random)
    +1 = very good correlation
    The observed/modeled value ratio should be as close to 1 as possible.
    If only 2 values > 0 are used, the correlation coefficient is -1 or 1.
    From the value of the correlation coefficient, one cannot determine
    whether all observed values are higher (or lower) than the calculated values or upward and downward deviations exist.
    AvgAbsErr

    Mean absolute error


    Mean deviation of absolute values ( )
    a
    (Difference between observed and modeled values)

    AvgObs
    Mean observed value
    AvgRelErr

    Mean relative error


    Mean deviation of absolute values in % ( ) according to
    p

    R2

    Coefficient of determination r2
    Cf. Excel function RSQ

    RelRMSE

    Relative root of mean square deviation

    StdDev

    Standard deviation

    Slope

    Coefficient a in linear regression


    Cf. Excel, linear regression (y = ax + b)

    Table 163: Calculation rules for the output attributes of assignment analysis

    448

    PTVGROUP

    7 User model PuT

    User model PuT


    The PuT user model calculates the effect of PuT supply on PuT passengers.
    Subjects
    Overview of PuT assignment procedures
    Example network for the PuT assignment procedures
    PuT paths
    PuT skims
    PuT impedance functions
    Distribution of the travel demand to PuT connectors
    Allocation of skims with reference to lines/links
    Transport system-based assignment
    Headway-based assignment
    Timetable-based assignment
    Assignment analysis PuT
    PuT passenger survey

    7.1

    Overview of PuT assignment procedures


    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 transport system-based procedure, which is based on a PuT-specific "all or
    nothing" assignment, provides an overview of the transport demand structure. This procedure does not require a line network. For rough-cut planning purposes it helps to determine the "ideal line network" where each passenger chooses the fastest route in the
    network without any restrictions caused by PuT line routes or timetables (see "Transport
    system-based assignment" on page 471).
    The headway-based procedure is ideal for urban networks with short headways and for
    long-term conceptual planning, as long as the timetable for the period being analyzed is
    still unknown. The headway-based procedure determines the transfer wait time at transfer
    stops from the mean headway of the succeeding lines. If necessary, co-ordination in the
    case of transfers between lines and also between the timetables of multiple lines are
    taken into consideration on sections with shared services, and then specified deviating
    transfer wait times are valid. Doing without the timetable on the level of individual trips
    ensures short computing times even for large networks (see "Headway-based assignment" on page 473).
    The timetable-based procedure should be used if the PuT supply has long headways
    and coordination of the timetable is important for transfers. It takes the accurate timetable
    into consideration and is therefore particularly suitable for rural areas or train networks.
    There are two variants of the timetable-based procedure, which differ only in terms of the
    connection search procedure (see "Timetable-based assignment" on page 498).
    In large networks, a distinction can often be made between a main network, which is the most
    important one to be analyzed, and a subordinated network, which provides feeder functions
    for the main network. Examples for this are national rail networks with subordinated regional

    PTVGROUP

    449

    7.2 Example network for the PuT assignment procedures


    or urban bus networks, which also include cars or taxis for access and egress. For modeling
    the subordinated network, there are basically two alternatives.
    Traffic zones that are not served by the main network are nevertheless connected to stops
    of the main network by long connectors. This alternative means that planners are required
    to estimate the route choice in the subordinated network accurately when selecting and
    setting attributes for the connectors. The route choice can also change in the case of supply changes in the main network.
    With regard to modeling accuracy, it is instead recommended to also model the subordinated network as a PuT supply. In addition to the considerable effort required to
    obtain the timetable data, memory requirements and computing time for the assignment
    are also greater. Especially in the case of short headways in the subordinated network,
    the number of connections explodes.
    A compromise solution involves modeling the entire main network and performing either a
    headway or a timetable-based assignment. The subordinated PuT supply in comparison is
    only modeled as a used link network and in the course of either the headway or timetablebased assignment it is treated as in the transport system-based procedure (best path search,
    see illustration 149).

    Illustration 149: Different modeling options for main and subordinated networks
    For this kind of modeling, the used links and turns in the subordinated network are opened for
    transport systems of the special PuT-Aux type and provided with specific run times for these
    connections. If PuT auxiliary transport systems are not available for all demand segments (for
    example car for P+R access), this is expressed by targeted inclusion in the appropriate
    modes. The mode for the demand segment Employed with car contains the PuT auxiliary
    transport system P+R, but the demand segment Employed without car does not.
    The PuT assignment procedures are mainly used for the following applications.
    To determine volumes, for example line volumes, link volumes, and the number of passengers who board, transfer or alight at stops.
    To calculate passenger-specific PuT skims, for example journey time, number of transfers,
    service frequency.
    As a timetable information system which provides information on the departure and arrival
    times of individual connections.

    7.2

    Example network for the PuT assignment procedures


    The different procedures are described below using an example (illustration 150, illustration
    151, illustration 152, table 164 and table 165). Find the connections between A-Village and XCity on the basis of the example's PuT supply.
    The following assumptions apply.

    450

    PTVGROUP

    7.2 Example network for the PuT assignment procedures


    The calendar is not used.
    Access and egress times are not considered, that is, they are set to 0 minutes.
    The analyzed 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 (Tables $MATRIX and
    $MATRIXSINGLELISTITEM in demand data file PuT.dmd).
    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.
    (Tables $TIMESERIES and $TIMESERIESITEM in demand data file PuT.dmd).
    The table 164 contains example data of the PuT.dmd file which is provided in English.
    $VISION
    * VisumInst
    * 04/11/07
    *
    * Table: VERSION
    $VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
    4,000;Demand;ENG;KM
    * Table: ODMATRIX
    $ODMATRIX:NO;CODE;NAME;CONTENT;ROUND;NUMDECPLACES
    1;C;Car;;0;0
    2;H;HVeh;;0;0
    3;P;PuT;;0;0
    * Table: MATRIXSINGLELISTITEM
    $MATRIXSINGLELISTITEM:MATRIXNO;FROMZONENO;TOZONENO;VALUE
    1;100;200;2000.000
    2;100;200;200.000
    3;100;200;90.000
    * Table: TIMESERIESDOMAINTYPE
    $TIMESERIESDOMAINTYPE:NO;DESCRIPTION;UNITYSTRING;NUMDECPLACES;MAXVALUE;MINVALUE
    1;Time series by percentages;%;2;9999999999.000;0.000
    2;Time series of matrix numbers;No;0;999999999.000;0.000
    * Table: Time series
    $TIMESERIES:NO;NAME;TYPENO;UNITX;NUMINTERVALS;LENGTHINTERVAL;USEVALUELIST;VALUELISTTYPE; VALUEREFTYPE;DECSEPARATOR;VALUESEPARATOR
    1;;1;;86400;1;0;0;2;;
    * Table: Time series items
    $TIMESERIESITEM:TIMESERIESNO;STARTINTERVALINDEX;ENDINTERVALINDEX;VALUE
    1;1;19800;0.000
    1;19801;23400;33.000
    1;23401;27000;67.000
    * Table: Demand time series
    $DEMANDTIMESERIES:NO;CODE;NAME;TIMESERIESNO
    1;;;1
    * Table: Demand descriptions
    $DEMANDDESCRIPTION:DSEGCODE;DEMANDTIMESERIESNO;MATRIXNO;STARTDAYINDEX;STARTTIME
    C;0;1;1;12:00 AM:00
    H;0;2;1;12:00 AM:00
    P;1;3;1;12:00 AM:00

    Table 164: Demand matrix and temporal distribution of demand for the example

    PTVGROUP

    451

    7.2 Example network for the PuT assignment procedures


    The example network is saved to the directory ... Users\Public\Public documents\PTV
    Vision\PTV Visum 13\Example_net.
    Version file: Example.ver
    Graphic parameters PuT.gpa
    Demand matrix and demand distribution PuT.dmd
    Procedure parameters PuT.par

    Illustration 150: Timetable

    Illustration 151: Line map


    Timetable Bus 1

    452

    Timetable Train

    A Village

    06:10
    a.m.

    06:55
    a.m.

    07:25
    a.m.

    Station

    06:25
    a.m.

    07:05
    a.m.

    07:45
    a.m.

    Station

    06:22
    a.m.

    07:07
    a.m.

    07:37
    a.m.

    X City

    06:41
    a.m.

    07:21
    a.m.

    08:01
    a.m.

    B Village

    06:42
    a.m.

    07:27
    a.m.

    07:57
    a.m.

    X City

    06:55
    a.m.

    07:40
    a.m.

    08:10
    a.m.

    PTVGROUP

    7.3 PuT paths


    Timetable Bus 1

    Timetable Train

    Connections
    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
    Table 165: PuT supply of the example with connections from A-Village to X-City

    7.3

    PuT paths
    Paths are the central result of an assignment (see "Paths in PrT and PuT" on page 223). In the
    timetable-based assignment (see "Timetable-based assignment" on page 498) a PuT path is
    described through a sequence of path legs which each represent one of the following activities.
    Change of location from one stop point to another by using a specific vehicle journey
    Change of location from origin zone via a connector and links to a stop point or from there
    to destination zone with a PuT-Walk TSys
    Transition from one stop point to another with a PuT-Walk TSys
    Change of location by using a PuT-Aux TSys
    Because each of the used vehicle journeys is known, the path has a time reference (see "Network objects of the line hierarchy" on page 68). Each of its path legs starts and ends at a precise time. This is called a connection.
    If the option Save paths as connections has been selected for the assignment (see User
    Manual: Chpt. 19.1.1.2 , page 1996), these connections become visible in the PuT path leg
    list.
    Alternatively, a path can be described without specifying vehicle journeys in detail. In this case
    only the time profile is known, which was used for a change of location via a PuT line (see "Network objects of the line hierarchy" on page 68). The departure and arrival times of each path
    leg are then relative times relating to the beginning of the path, completely analog to the difference between vehicle journey and time profile. Such a path described by the used time profiles and relative times is called a route.
    Naturally, routes are suitable especially to aggregate display of recurring connections at regular timetables. Two connections at different headway times which otherwise run the same, are
    combined to the same route. This usually requires considerably less memory space.
    When executing the timetable-based assignment with option Save paths as routes (see
    User Manual: Chpt. 19.1.1.2 , page 1996), individual connections are still determined and loaded internally. These are, however, only saved as aggregated routes after the assignment.
    Reference is lost to the individual vehicle journeys as well as their exact departure times. The
    PuT path leg list then shows the relative times for departure and arrival, and the optional relations to the first and after the last vehicle journey item are empty. Because the network ele-

    PTVGROUP

    453

    7.3 PuT paths


    ments are loaded prior to discarding the connections, time-based volumes can still be determined.
    The third option Save paths do not save (see User Manual: Chpt. 19.1.1.2 , page 1996)
    results in that no path information is saved after ending the assignment. Only the derived
    values of the network object volumes and also skim matrices are retained after the assignment. This way, path-based post-assignment analyses are not possible especially no flow
    bundle calculation. PuT path list and PuT path leg list also remain empty, however, time-based
    volume values are also possible with this option.
    Due to its differing user model, headway-based assignment (see "Headway-based assignment" on page 473) not even internally determines connections but routes. The option Save
    paths as connections can be selected, however, but at headway-based assignment routes
    are saved in either case (or nothing). These are formally equal to those routes determined by
    the timetable-based assignment and can be output in the same way as PuT path list or PuT
    path leg list.
    The table 166 shows the path legs which result from a timetable-based assignment in example Example.ver. In this case, the paths were saved as connections.
    Origin Deszone tination
    zone
    100

    200

    Path Path
    inde- leg
    x
    index
    1

    Passenger
    trips
    25000

    From
    stop
    point
    10

    100

    200

    454

    200

    40

    Departure
    06:10:00
    a.m.

    10

    OrigConn

    06:10:00
    a.m.

    10

    20

    BUS1 1_H > 1 06:10:00


    a.m.

    20

    20

    Transfer

    06:22:00
    a.m.

    20

    40

    TRAIN 1_H >


    1

    06:25:00
    a.m.

    40

    DestConn

    06:41:00
    a.m.

    Time profile
    ID

    14,000

    10

    100

    To
    stop
    point

    10

    40
    18,000

    10

    40

    06:10:00
    a.m.

    10

    OrigConn

    40

    BUS1 1_H > 1 06:10:00


    a.m.
    DestConn

    40

    06:10:00
    a.m.

    06:55:00
    a.m.
    06:55:00

    PTVGROUP

    7.3 PuT paths


    Origin Deszone tination
    zone

    Path Path
    inde- leg
    x
    index

    Passenger
    trips

    From
    stop
    point

    To
    stop
    point

    Time profile
    ID

    Departure
    a.m.

    100

    200

    10

    40

    16,000

    10

    100

    200

    10

    OrigConn

    40

    BUS1 1_H > 1 06:55:00


    a.m.
    DestConn

    40

    06:55:00
    a.m.

    07:40:00
    a.m.
    07:25:00
    a.m.

    10

    OrigConn

    07:25:00
    a.m.

    10

    20

    BUS1 1_H > 1 07:25:00


    a.m.

    20

    20

    Transfer

    07:37:00
    a.m.

    20

    40

    TRAIN 1_H >


    1

    07:45:00
    a.m.

    40

    DestConn

    08:01:00
    a.m.

    17,000

    10

    1
    2

    10

    40

    40

    07:25:00
    a.m.

    10

    OrigConn

    40

    BUS1 1_H > 1 07:25:00


    a.m.
    DestConn

    07:25:00
    a.m.

    08:10:00
    a.m.

    Table 166: Path legs after a timetable-based assignment (paths saved as connections)
    For the same assignment, 7.3 shows the path legs, if the paths were saved as routes.
    Origin Deszone tination
    zone
    100

    200

    Path Path
    inde- leg
    x
    index
    1

    25,000
    1

    PTVGROUP

    Passenger
    trips

    From
    stop
    point
    10

    To
    stop
    point

    Time profile
    ID

    40
    10

    Departure
    00:00:00
    a.m.

    OrigConn

    00:00:00
    am.

    455

    7.4 PuT skims


    Origin Deszone tination
    zone

    100

    200

    Path Path
    inde- leg
    x
    index

    Passenger
    trips

    From
    stop
    point

    200

    Time profile
    ID

    Departure

    10

    20

    BUS1 1_H >


    1

    00:00:00
    a.m.

    20

    20

    Transfer

    00:12:00
    a.m.

    20

    40

    TRAIN 1_H > 00:15:00


    1
    a.m.

    40

    49,000

    10

    100

    To
    stop
    point

    10

    40

    16,000

    10

    DestConn
    40

    00:31:00
    a.m.
    00:00:00
    a.m.

    10

    OrigConn

    00:00:00
    am.

    40

    BUS1 1_H >


    1

    00:00:00
    a.m.

    DestConn

    00:45:00
    a.m.

    40

    00:00:00
    a.m.

    10

    OrigConn

    00:00:00
    am.

    10

    20

    BUS1 1_H >


    1

    00:00:00
    a.m.

    20

    20

    Transfer

    00:12:00
    a.m.

    20

    40

    TRAIN 1_H > 00:20:00


    1
    a.m.

    40

    DestConn

    00:36:00
    a.m.

    Table 167: Path legs after a timetable-based assignment (paths saved as connections)

    7.4

    PuT skims
    By means of the Calculate PuT skim matrix procedure or during an assignment the skim data
    can be calculated (see User Manual: Chpt. 19.4 , page 2073) for the PuT skims of the various
    skim categories (see "PuT skim categories" on page 457).
    Since there are numerous routes or connections for an OD pair usually, the skims gained per
    route or connection are aggregated to relation-based skim data by OD pair. Apart from the service frequency which results from the number of connections, all skims are provided on the
    level of connections as well as on the level of OD pairs.

    456

    PTVGROUP

    7.4.1 PuT skim categories

    7.4.1

    PuT skim categories


    The skims can be divided into six categories.
    1. Skims of time (see "Skims of time" on page 457)
    2. Skims of length (see "Skims of length" on page 459)
    3. Monetary skims (see "Monetary skims" on page 459)
    4. Frequency skims (see "Skims of frequency" on page 459)
    5. Skims of attribute data (see "Skims of attribute data" on page 460)
    6. Derived skims (see "Derived skims" on page 460)

    7.4.1.1

    Skims of time
    In Visum, skims of time (table 168) are administered in seconds. For skim matrices you can
    select the unit minutes or seconds.
    Skim

    Definition

    Access time (ACT)

    Time required for covering the origin connector

    Egress time (EGT)

    Time required for covering the destination connector

    Origin wait time


    (OWT)

    Wait time at the start stop point (applies to the headway-based assignment only, as for the timetable-based procedure OWT = 0 is assumed)
    Note:
    For the timetable-based procedure, an adapted origin wait time can
    be calculated (see "Adapted skims of time for the timetable-based
    assignment" on page 458).

    Weighted origin
    wait time

    Product from the origin wait time and the weighting factor of the origin wait time in the settings for the impedance of the headwaybased assignment. This skim is only available in the headwaybased assignment.

    Transfer wait time


    (TWT)

    Wait time between arrival and departure at a transfer stop point


    Note
    For the timetable-based procedure, the adapted transfer wait time
    can be calculated additionally (see "Adapted skims of time for the
    timetable-based assignment" on page 458).

    Weighted transfer
    wait time

    Product from the transfer wait time and the weighting factor of the
    transfer wait time in the settings for the impedance of the headwaybased assignment. This skim is only available in the headwaybased assignment.

    Extended transfer
    wait time (XTWT)

    Extended wait time according to the settings for the transfer wait time
    in the perceived journey time definition for the timetable-based assignment.

    PTVGROUP

    457

    7.4.1.1 Skims of time


    Skim

    Definition

    In-vehicle time (IVT) Time spent inside PuT vehicles including dwell times at stops.
    In-vehicle time by
    TSys (IVTT)

    Time spent inside PuT vehicles of a certain public transport system.

    PuT-Aux time (XZ)

    Time spent in a vehicles of public transport systems of the PuT-Aux


    type.

    Walk time (WKT)

    Walk time for transfer links between two stop points within a stop
    area or between different stop areas of a stop

    Journey time (JRT)

    Time between the departure from the origin zone and the arrival at
    the destination zone
    JRT = ACT + OWT + IVT + TWT + WKT + EGT
    Note:
    For the timetable-based procedure, the adapted journey time can be
    calculated additionally (see "Adapted skims of time for the timetablebased assignment" on page 458).

    Ride time (RIT)

    Time between the departure from the origin stop point and the arrival at the destination stop point
    RIT = IVT + TWT + WKT
    Note:
    For the timetable-based procedure, the adapted journey time can be
    calculated additionally (see "Adapted skims of time for the timetablebased assignment" on page 458).

    Perceived journey
    time (PJT)

    Perceived journey time (see "Perceived journey time" on page 467)


    PJT = f(ACT, EGT, OWT, TWT, NTR, IVT, WKT, XZ)

    Adaptation time
    (ADT)

    Difference DeltaT between desired departure time and actual departure time

    Extended adaptation time (XADT)

    User-defined adaptation time. Variant of the adaptation time which


    assumes that the entire demand of each time interval is assigned to
    the connection with the minimum impedance.

    Table 168: Skims of time


    Adapted skims of time for the timetable-based assignment
    The skims OWT, TWT, JRT and RIT in the form described above always refer to the real origin
    wait time and the real transfer wait time.
    For the timetable-based assignment, the adapted variants of these skims are also available,
    which contain the terms that are currently set up in the perceived journey time definition (PJT)
    instead of the real origin and transfer wait times.
    Unlike the real origin wait time which is constantly = 0 in the timetable-based procedure, the
    adapted origin wait time can differ from 0 because it depends on the number of connections
    provided in the assignment interval. The adapted transfer wait time depends on the user settings for transfer wait time and can thus be limited. Furthermore, it can be transformed
    458

    PTVGROUP

    7.4.1.2 Skims of length


    implicitly by a polynomial for stronger weighting of extremely short wait times and for the definition of a certain wait time (for example five minutes) as the optimum.
    7.4.1.2

    Skims of length
    You can select the metric units meters or kilometers (alternatively: imperial feet/miles) for skim
    matrices. The table 169 shows all skims of the length provided in Visum. The abbreviations in
    parentheses indicate the file extensions which are used by default for skim matrix output in version files.
    Skim

    Definition

    Access distance (ACD)

    Length of the access route on the footpath from the origin


    zone to the origin stop point

    Egress distance (EGD)

    Length of egress route from destination stop point to destination zone

    In-vehicle distance (IVD)

    Distance covered in vehicle without transfer walk links

    In-vehicle distance per


    TSys (IVTD)

    Travel distance inside vehicles of a specific public transport


    system

    PuT-Aux distance (AXD)

    In-vehicle distance for a PuT-Aux transport system

    Walk distance (WKD)

    Length of a transfer link between the two stop points

    Journey distance (JRD)

    Distance covered between origin and destination zone


    Journey distance = Access distance + In-vehicle distance +
    Walk distance + Egress distance

    Ride distance (RID)

    Covered distance from origin stop point to destination stop


    point
    Ride distance = In-vehicle distance + Walk distance

    Direct distance (DID)


    Table 169: Skims of length
    7.4.1.3

    Direct distance between origin and destination zone

    Monetary skims
    The table 170 shows the monetary skims available in Visum.
    Skim

    Definition

    Fare (FAR)

    Fare for the PuT ride between origin and destination zone (see
    "Fares" on page 468)
    Table 170: Monetary skims [Currency units]
    7.4.1.4

    Skims of frequency
    The table 171 shows the available frequency skims.

    PTVGROUP

    459

    7.4.1.5 Skims of attribute data


    Skim

    Definition

    Number of transfers Number of transfers between origin and destination stop point (per
    (NTR)
    connection). Service frequency
    (SFQ)

    For the timetable-based procedure, the service frequency is defined


    as the number of different arrival times for connections departing
    within the assignment time interval or in the succeeding extension
    period past the end of the assignment time interval yet before a possible second occurrence of the start of the assignment period. The
    latter especially means that the succeeding period is not considered, if you do not use a calendar and define a 24-hour assignment time interval covering the whole day.
    To the headway-based assignment, the following applies: On the
    graph of all determined routes, a flow problem is solved. Service frequency thus depends on the "weakest" part in the transport supply.

    Number of operator Number of transfers with different operators of previous and next
    changes (NOC)
    path leg. Number of fare
    zones

    Number of traversed fare zones. The skim depends of the ticket type
    (s) used for the connection and returns zero if no zone-based ticket
    type is used. Table 171: Skims of frequency
    7.4.1.5

    Skims of attribute data


    The table 172 lists the provided skim that results from the values of the selected attribute.
    Skim

    Definition

    Path leg attribute


    Throughout the entire path aggregated value of the selected (direct
    (PLA)
    or indirect) path leg attribute, for example Line route\AddValue1.
    Table 172: Skims of attribute data
    7.4.1.6

    Derived skims
    Derived skims (table 173) result from a combination of the above listed skims.
    Skim

    Definition

    Impedance in a time Impedance of a connection = f (perceived journey time, fare, teminterval (IPD)
    poral utility). For the skim matrix you can select whether the temporal
    component should flow into the impedance in minutes or seconds.
    Journey speed
    (JRS)

    Ratio of the journey distance and the journey time between origin
    and destination zone [km/h]
    Journey speed [km/h] = journey distance [m] / 1,000) / journey time [min] / 60)

    Direct distance
    speed (DIS)

    Ratio of the direct distance and the journey time between origin and
    destination zone [km/h]

    In-vehicle distance

    Distance covered in the TSys as a percentage of the total in-vehicle

    Direct distance speed [km/h] = direct distance [m] / 1,000) / journey time [min] / 60)

    460

    PTVGROUP

    7.4.1.6 Derived skims


    Skim

    Definition

    as percentage by
    TSys (IVTP)

    distance of the connection

    Equivalent journey
    time (EJT)

    Skim value which results from a user-defined formula according to


    the set parameters. The unit of the journey time equivalent of the calculated skims is determined by the user-defined formula.

    Extended impedance (XIMP)

    The extended impedance is a component of the perceived journey


    time (PJT). It can be defined in the settings for the impedance of the
    timetable-based assignment and is thus only available in the timetable-based assignment.

    PTVGROUP

    461

    7.4.1.6 Derived skims


    Skim

    Definition

    Utility (UTL)

    The Utility is based on the following:


    On the one hand, the utility is based on C, which is the set of
    connections determined for an OD pair.
    On the other hand, the utility is based on the set of time intervals
    T = (t1, ..., tn) resulting from the time series relevant to the OD
    pair or from refined time series intervals, if applicable.
    Per time interval t in T, each connection c in Chas an impedance wt
    (c), which depends on t, since the impedance may contain the time
    intervals distance from the connections departure time.
    Using an antitone utility function f, the respective utility ut(c) is calculated from the impedance wt(c) according to ut(c) = f (wt(c)).
    In case of the Logit model f(x) = e-bx.
    The share of a connection c of the demand per interval t is then derived according to the following formula.

    The denominator U is the overall utility of the time interval.


    t

    Compared to skims representing a mean value, U improves with


    t
    every new connection that is added to the current transport supply.
    For that reason the averaged U calculated over all time intervals is
    t
    accounted for as a separate skim.

    Here, d is the total demand within time interval t.


    t

    Discomfort due to
    capacity overload
    (DISC)

    Time during which a passenger has no seat in the course of this journey.
    The skim is calculated as journey time weighted by vehicle journey
    item. Its weight is a function of the volume/seat capacity ratio.
    For each individual PuT path C, the discomfort E(C)is defined as follows.

    Here

    462

    PTVGROUP

    7.4.1.7 Examples for skims


    Skim

    Definition
    a = Index over all vehicle journey items of a PuT path C
    F = Journey time of the vehicle journey item a (known from its time
    a
    profile)
    P = Number of passengers on vehicle journey item a (over all
    a
    paths, determined by assignment)
    S = Number of seats on vehicle journey item a (based on the total of
    a
    the seats of all vehicle journey sections which traverse the vehicle
    journey item on the respective calendar day)
    A,B =free parameters
    Path legs covered by a TSys of the PuT-Walk or PuT-Aux type in the
    PuT path are ignored.
    Note
    The discomfort due to capacity overload is only calculated with a
    timetable-based assignment.

    Table 173: Derived skims


    7.4.1.7

    Examples for skims


    The illustration 152 and the table 174 illustrate a few skims for the connections of an OD pair.

    Illustration 152: Example network


    Connection 1

    Connection 2

    Used sequence of lines /


    route

    Bus1

    Bus1, Train

    Access distance [m]

    300

    300

    Access time [min]


    Run time [min]
    Transfer wait time [min]
    Egress distance [m]
    Egress time [min]
    Ride time [min]

    PTVGROUP

    45

    28

    500

    500

    45

    36

    463

    7.4.1.8 Availability of the skims in the PuT assignment procedures


    Connection 1

    Connection 2

    Journey time [min]

    53

    44

    Journey distance [m]

    27,500

    20,000

    Direct distance [m]

    18,385

    18,385

    Journey speed [km/h]

    31.1

    27.3

    Direct distance speed [km/h]

    20.8

    25.1

    Number of transfers [-]


    Table 174: Example of the connection skims of an OD pair
    7.4.1.8

    Availability of the skims in the PuT assignment procedures


    The table 175 shows which skims can be calculated per PuT assignment procedure.
    Skim output by procedure

    Default ext.

    TSysbased

    HWaybased

    Timetablebased

    JRT

    IVT

    PuT-Aux time

    AXT

    Origin wait time

    OWT

    Journey time
    Journey time adapted
    Ride time
    Ride time adapted
    In-vehicle time

    RIT

    RITA

    X
    X

    Origin wait time adapted

    OWTA

    Weighted origin wait time

    WOWT

    TWT

    Transfer wait time

    464

    JRTA

    X
    X

    Transfer wait time adapted

    TWTA

    Weighted transfer wait time

    WTWT

    Extended transfer wait time

    XTWT

    Walk time

    WKT

    Access time

    ACT

    Egress time

    EGT

    Perceived journey time

    PJT

    Number of transfers

    NTR

    Service frequency

    SFQ

    X
    X

    Direct distance

    DID

    Journey distance

    JRD

    Ride distance

    RID

    Trip distance

    IVD

    PTVGROUP

    7.4.1.9 Aggregation to mean skims per OD pair


    Skim output by procedure

    Default ext.

    TSysbased

    HWaybased

    Timetablebased

    PuTAux distance

    AXD

    Walk distance (transfer walk links)

    WKD

    Access distance

    ACD

    Egress distance

    EGD

    Journey speed

    JRS

    Direct distance speed

    DIS

    Fare

    FAR

    Number of fare zones

    NFZ

    Number of operator changes

    NOC

    In-vehicle distance per TSys

    IVTD

    In-vehicle distance percentage per


    TSys

    IVTP

    In-vehicle time per TSys

    IVTT

    Impedance

    IPD

    Utility

    UTL

    Path leg attribute

    PLA

    Adaptation time

    X
    X

    ADT

    Extended adaptation time

    XADT

    Extended impedance (XIMP)

    XIMP

    Equivalent journey time (user-defined)


    Discomfort due to capacity overload
    (only calculated during assignment)

    EJT

    DISC

    Table 175: Availability of the skims in the PuT assignment procedures


    7.4.1.9

    Aggregation to mean skims per OD pair


    Depending on the chosen search procedure there are different possibilities to aggregate the
    skim values (Skim) of the connections to mean skim data (mSkim) by OD pair (table 176):
    Aggregation functions

    HWaybased

    TTbased

    Unweighted quantile
    For 0 z 1 the z-quantile of a finite, classified series of values (x1, ...,
    xn) is defined as smallest number y, to which applies that # is {i : xi y }
    / n z.

    Weighted quantile
    The connections are weighted with the volume at the calculation of the
    quantile.

    PTVGROUP

    465

    7.4.1.9 Aggregation to mean skims per OD pair


    Aggregation functions

    HWaybased

    TTbased

    Unweighted mean

    Weighted mean

    Unweighted mean restricted to paths of sufficiently low impedance

    Weighted mean restricted to paths of sufficiently low impedance

    mSkim = skim value for route with minimum impedance

    mSkim = skim value for route/connection with minimum perceived journey time

    Table 176: Combination of skim data to the mean skim value per OD pair
    Note: For calculation of a weighted mean, by default, the weights of skim matrix calculation are used. In this case, the demand in the time series intervals is set in relation to
    the total demand in the assignment period. If the weights of a percentage time series or
    the demand of a matrix time series for an OD relation equals 0, a fixed demand is assumed and the respective time interval is weighted with its length in relation to the assignment period.
    The skim service frequency SFQ does not refer to a particular route or connection, but to an
    OD pair.
    For the timetable-based procedure, the service frequency results from the number of different
    arrival times.

    466

    PTVGROUP

    7.4.2 Perceived journey time


    Example
    For an OD pair, three connections are determined:
    Connection

    Volume

    50 %

    20 %

    30 %

    Number of transfers

    By means of the different aggregation functions, the number of transfers by OD pair is calculated as follows:
    Mean value

    7.4.2

    50% quantile

    unweighted

    weighted

    unweighted

    weighted

    (1 + 3 + 2) / 3
    =2

    1 0.5 + 3 0.2 + 2
    0.3
    = 1.7

    Values: (1, 2, 3)
    50% quantile = 2

    Values:
    (1,1,1,1,1,2,2,2,3,3)
    50% quantile = 1

    Perceived journey time


    The perceived journey time PJT results from the weighted components of the journey time and
    further components.
    Perceived journey time PJT [min]
    = In-vehicle time FacIVT (in)direct time profile item attribute 2)
    + PuT-Aux time FacAXT 1)
    + Access time FacACT
    + Egress time FacEGT
    + Transfer walk time FacWT
    + Origin wait time FacSZ
    + Transfer wait time FacTWT
    + Number of transfers FacNTR
    + Number of operator changes FacOC 1)
    + other impedance elements FacXIMP 1)
    1) timetable-based assignment only
    2) headway-based assignment only, (in)direct vehicle journey item attribute in the timetable-based assignment
    The perceived journey time is used for the headway-based procedure and timetable-based
    procedure, to evaluate individual connections during the connection choice. Weighting the
    number of transfers strongly, for example, results in passengers preferring minimum transfer
    connections.
    In both procedures, boarding events and transfers can be evaluated in addition.
    Headway-based assignment does not yet regard PuT-Aux times.
    For the timetable-based assignment, the following options are provided:
    Number of operator changes can be taken into account
    PuT-Aux time can be weighted with a TSys attribute
    extended impedance can be defined

    PTVGROUP

    467

    7.4.3 Fares
    Moreover, for each component a Lambda value can be entered and/or the option BoxCox transformation can be activated.

    7.4.3

    Fares
    Visum can be used to calculate fares (see "PuT fare model" on page 605). The fare per
    connection results from the used ticket type(s). It includes the specific supplement by transport
    system (for ICE, for example). These fares are calculated for each connection. Except for the
    impedance definitions of both the headway-based and the timetable-based assignment procedures, the fares can also be output as skim matrix and can be taken into account for the revenue calculation which is performed by the PuT operating indicators procedure.

    7.4.4

    Temporal utility
    For the timetable-based assignment, the temporal utility of a connection is included as a further skim value in the definition of impedance (see "PuT impedance functions" on page 468).
    The temporal utility of a connection depends on the following parameters:
    Desired departure time, which is indicated by the temporal distribution of demand
    Time difference T between provided time of departure and desired time of departure
    Tolerance to differences between the provided time and the desired time of departure,
    which is called the sensitivity to earlier or later departures
    In this way it can be modeled that also the temporal position of a connection 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.
    The timetable-based method includes the temporal utility in the impedance definition in different ways either by using a function N = f(DT) or by using T directly. In either case, the sensitivity of passengers to early or late departures can be set by parameter.
    For both variants, the following applies.
    The shorter the period between the actual and the desired departure time, the higher the temporal utility of the connection and the lower its impedance.
    Time series with hourly intervals
    T (6-7) = 07:20 a.m. 07:00 a.m. = 20 min
    T (7-8) = 0 min
    T (8-9) = 08.00 a.m. 07.20 a.m. = 40 min
    Table 177: Example for the determination of the time difference T

    7.5

    PuT impedance functions


    Like PrT assignment procedures (see "Impedance and VD functions" on page 231) the PuT
    assignment procedures derive the impedance of a connection from several skims of this
    connection or route (see "PuT skims" on page 456). Thus, the impedance is a user-defined

    468

    PTVGROUP

    7.6 Distribution of the travel demand to PuT connectors


    combination of various skims. According to requirements, a malus or a bonus can be specified
    for various properties of a connection. The general rule is "The lower the impedance of a
    connection, the higher its share of the transport demand".
    In contrast to PrT, however, the impedance is used not only for the connection search, but also
    to evaluate the connections during the connection choice by some of the PuT procedures.
    Impedance can consist of times and fares. Due to the impedance dependency on the temporal
    utility (see "Temporal utility" on page 468) at the connection choice of the timetable-based procedure (see "Timetable-based assignment" on page 498), the impedance of a connection can
    be different from time interval to time interval.
    The actual definition of impedance differs in the various assignment procedures. The timetable-based procedure actually uses different approaches in two of the calculation-internal
    work steps. An overview is given in table 178 . All factors can be set freely and also be set to
    zero, so that they are not considered in the assignment.
    Procedure

    Definition of impedance

    Timetablebased
    Branch&Bound
    search

    IMP = JRT Fac1 + NTR Fac2 + TSysIMP Fac3

    IMP = JRT
    Timetablebased Shortest path search
    IMP = PJT Fac1 + Fare Fac2 + DTearly Fac3 + DTlate Fac4
    Timetablebased Choice

    Headway-based IMP = IVT + TWT Fac1 + NTR Fac2,


    Search
    here TWT stands for the expected wait time for the line to which one
    transfers.
    Headway-based IMP = PJT Fac1 + Number of fare points or fare Fac2
    Choice
    Table 178: Comparison of the impedance functions in the PuT assignments

    7.6

    Distribution of the travel demand to PuT connectors


    Similar to the PrT origin and destination demand, the PuT origin and destination demand can
    also be distributed to PuT connectors either arbitrarily or by percentage (see "Distribution of
    demand of a zone to the connectors" on page 59). Contrary to PrT, PuT does not provide two
    variants for the proportional distribution but always uses the model "Each single OD pair
    (MPA)". For PuT, the distribution by percentage may be used, for example, to assign the transport demand to all stops which are located within a community (modeled as one zone).
    The proportional distribution of the PuT is effected similar to the distribution by percentage of
    PrT. All origin and destination demand of the zone is distributed onto all connectors of the
    zone proportionally to their respective current connector weights. During the assignment, a
    temporary virtual zone is generated for each connected node. The virtual zone's total demand

    PTVGROUP

    469

    7.7 Allocation of skims with reference to lines/links


    complies with the connector's original share in the total demand of the original zone. The assignment calculation is based on the virtual zones. After the assignment, the temporary zones
    are deleted and the results are allocated to the original zones.
    Example
    Two zones with the following connectors are given.
    Zone 100 with distribution by percentage, connected nodes 1, 2 and 3
    Zone 200 with distribution by percentage, connected nodes 4 and 5
    The connector weights for origin and destination are set according to table 179.
    Connector node

    Weight (origin)

    Weight (destination)

    20

    30

    80

    50

    20

    40

    90

    60

    10

    5
    Table 179: Connector weights for the example

    Transport demand from zone 100 to zone 200 = 1000 trips


    Transport demand from zone 200 to zone 100 = 500 trips
    For the assignment, this leads to the temporary demand matrix displayed in table 180.
    Virtual zone

    180

    20

    270

    30

    450

    50

    160

    40

    5
    0
    240
    60
    Table 180: Temporary demand matrix for the assignment in the example

    The value of the temporary OD pair 1 4 is calculated from 1,000 0.2 0.9 = 180.

    7.7

    Allocation of skims with reference to lines/links


    Certain attributes, for example the line network length of a transport system or the attributes
    number of service trips or PuT volume of a link are in an intermediate position, because spatially their definition refers to a link and also to a line route. Since stop points may optionally be
    placed on links, and both line routes and vehicle journeys extend from stop point to stop point,
    only certain sections of links may be traversed by line routes or vehicle journeys.
    In most cases, proportional allocation of these indicator values to the link does not make
    sense, which is why the definition for those indicators has been standardized:

    470

    PTVGROUP

    7.8 Transport system-based assignment


    A link is regarded as being used (completely) by an object of the line hierarchy if the link section traveled accounts for at least half of the link length ( 0.5). For indicators that relate to sections between stop points (for example, volume ), the following applies. Each stop point on a
    link is assigned the nearest node (either the From node or the To node of the link). The indicator value of the section between the last stop point, to which the FromNode is assigned, and
    the first stop point, to which the ToNode is assigned, is regarded as the indicator value for the
    (entire) link. The illustration 153 shows skim calculation example for such partially traversed
    links.

    Illustration 153: Example for skim calculation for partially traversed links
    Line route 1 touches the links 2, 3, and 4 (because the section traveled accounts for at least
    half of the link), not link 1 however, because the traversed section is < 0.5 on link 1. Vehicle
    journey 1 only touches link 3. The volume between the stop points B and C is regarded as the
    PuT volume of link 2, while for link 3, volume C D applies and for link 4, the volume between
    D and E.

    7.8

    Transport system-based assignment


    The transport system-based assignment does not differentiate between individual PuT lines.
    Modeling the transport supply only considers the links of a basic network with their specific run
    times. The basic network can comprehend the following sets of links.
    All road and rail links of the link network
    Only those links which are traversed by PuT lines
    Only those links which are traversed by active PuT lines
    From the links of this basic network a graph is constructed which is the basis for a best-route
    search.
    Because individual lines are not distinguished, transfer stops with their respective transfer
    times cannot be included in the search. It is possible, however, to include transition times between different transport systems (transfer penalties for transport system changes, for example
    between bus and train).
    The transport system-based assignment calculates exactly one route for each pair of origin
    zone and destination zone, which consists of one origin connector and one destination
    connector for the PuT as well as of links and turns, which are permitted for a public transport
    system. Transfers are changes of the transport system which are considered in the form of a
    time penalty in the route search.
    For links, t-PuTSys is considered
    A transport system change can only take place at selected nodes

    PTVGROUP

    471

    7.8.1 Evaluation of the transport system-based assignment


    At nodes, where a transport system change is necessary, a transfer time penalty TP is assigned
    TP = node type-specific time penalty + penalty per transfer
    At nodes, at which no turn for the public transport system is permitted between the links,
    the time penalty TP is also added if option Consider prohibited turns is active.

    7.8.1

    Evaluation of the transport system-based assignment


    The transport system-based assignment is characterized 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 the same transport system which run in parallel but have different PuT run times
    (for example bus 1 and bus 2) can only be represented by a mean PuT run 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 volume flows represent the "desired
    line network" of the passengers.
    The volumes resulting from the timetable-based assignment and the headway-based assignment will differ significantly from the results calculated by the transport system-based assignment. Under no circumstances neither a timetable-based nor a headway-based calculation
    should be replaced by the transport system-based procedure.

    7.8.2

    Example for the transport system-based assignment


    For the PuT supply in the example (see "Example network for the PuT assignment procedures"
    on page 450), the procedure determines the following shortest route given a transfer penalty
    of 10 minutes for the transfer from bus to train.
    12 minutes from A-Village to Station with transport system Bus
    16 minutes from Station to X-City with transport system Train
    With a 10-minute transfer penalty, this results in a ride time of 38 minutes. All 90 trips from AVillage to X-City are assigned onto this route.
    This results in the volumes shown in illustration 154.

    Illustration 154: Network volume after transport system-based assignment (parameters file
    TSys1.par)

    472

    PTVGROUP

    7.8.3 Steps of the transport system-based assignment


    From a transfer time of 18 minutes onward, the TSys bus is used instead of the train for the section between the Station and X-City (illustration 155).

    Illustration 155: Network volume after transport system-based assignment (parameters file
    TSys2.par)

    7.8.3

    Steps of the transport system-based assignment


    On the links, connectors and turns which are permissible for public transport systems in the network, the transport system-based assignment determines the routes with the minimum impedance for each OD pair.

    7.8.3.1

    Route search
    The impedance of a route consists of the following components.
    Run times of traversed links
    Transfer penalty for every transport system transfer
    Node type-specific or stop-specific transfer penalties
    For links which may be used by several public transport systems with different run times, the
    minimum run time is used.

    7.8.3.2

    Route loading
    The total demand of an OD pair is assigned to the route with the lowest impedance.
    The transport system-based procedure carries out exactly one best-path search for every OD
    pair.

    7.9

    Headway-based assignment
    For the headway-based procedure, each line is described by the line route, the run times between line stops, and the headway. Actually, it is the time profile which comprises this information and the headway-based procedure works on this model level (see "Network objects of
    the line hierarchy" on page 68). In the following sections the term line is used for the sake of
    convenience. This emphasizes that the timetable of the individual vehicle journeys is not regarded.
    Transfer wait times are usually regarded globally, which means that the departures of different
    lines are independent of each other. As a standard, a timetable coordination is not taken into
    consideration. By explicit modeling, however, it can be expressed that lines operate with the
    same headway each on a shared section, or rather a fixed transfer wait time exists between

    PTVGROUP

    473

    7.9.1 Evaluation of the headway-based assignment


    two lines (see "Matched transfers" on page 496). TSys of the PuT-Aux type are not yet regarded.
    The headway-based assignment procedure includes the three operational steps.
    1. Headway calculation (see "Headway calculation" on page 475)
    2. Route search and route choice (see "Route search" on page 492 and "Route choice" on
    page 493)
    3. Route loading
    In the combination of search and choice, the headway-based procedure differs from the timetable-based assignment. In this second step, possible paths between two traffic zones are
    detected and simultaneously a distribution is specified between them. The paths do not represent connections, but routes (see "PuT paths" on page 453), as the calculation is not done on
    the time axis, but merely regards travel times and headways. In the third step, the routes found
    in the search are loaded with the demand from the demand matrix and stored in memory (if
    desired).

    7.9.1

    Evaluation of the headway-based assignment


    The headway-based procedure is characterized by the following features:
    The procedure, as is the case with the timetable-based assignment, not only determines
    the optimum routes, but also those that are good enough. However, the transfer wait time
    goes in only globally here.
    A coordination of the timetable is taken into consideration only if the coordination has
    been modeled explicitly (see "Coordination" on page 495).
    The number of transfers, journey time and the ride time can be estimated with sufficient
    accuracy if all lines have short headways.
    The bandwidth of various choice models offers the big advantage of being able to configure the procedure in such a way, that it precisely reflects the available passenger information provided in the analyzed network. Accordingly, you can apply different models to
    make an estimate of the benefit, which can be achieved by investing in passenger information systems.
    Compared to the timetable-based procedure, the headway-based procedure shows a considerable reduction of computing time for most PuT networks, this is especially the case
    for networks with regular headways (fixed-time rhythm). In networks in which many lines
    consist of only one trip, however, time savings are low.
    Because the headway-based procedure normally 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 exist yet. This procedure is not suited for PuT supply planning in rural areas or for long-distance transport, because in these cases long
    headways occur, and it is an elementary planning task to provide connections.
    Using the headway-based procedure, the fares can be regarded in the impedance calculation. For that purpose, the full range of the Visum fare model is provided. Due to the
    complexity of the fare model, taking fares into account in an assignment might increase
    the required computation time. With less complex fare structures, the variant using fare

    474

    PTVGROUP

    7.9.2 Headway calculation


    points should be favored. Note that the fare is not computed for the complete path but per
    path leg during an assignment (see "Generalized costs as impedance" on page 476).

    7.9.2

    Headway calculation
    You can define the headway of a line in three different ways (see User Manual: Chpt. 19.2.3.1
    , page 2011).
    from a (usually user-defined) time profile attribute
    from the mean headway according to the timetable
    from the mean wait time according to the timetable (default setting)
    Each of the three methods can be applied separately by time interval. That way you can model
    that the transport supply varies within the assignment period for example, because of the higher demand during morning peak hours.
    From time profile attribute
    In the simplest case, directly enter the headway as an attribute of the respective time profile.
    The specification of a timetable is then dispensable. An existing timetable is ignored.
    From mean headway according to timetable
    Visum can also automatically calculate the headway from the timetable of the time profile. For
    that purpose, the number of departures n is determined for each time interval l=[a,b) within the
    assignment time interval. The headway results as the quotient.

    In the case of networks with short headways and sufficiently broad time intervals, this simplified approximation is acceptable. Generally speaking, however, this approach is problematic for two reasons.
    On the one hand, the definition is too sensitive to shiftings of individual departures across the
    interval limits. This will cause discontinuities in the result. This problem always occurs if the
    real headway of a PT line is no divisor of the length of the demand time interval. For a line with
    a 40-minute headway, for example, and the time interval l=[06:00 a.m., 07:00 a.m.), different
    headways are calculated for the particular departure times (table 181).
    Departure times
    05:55 a.m., 06:35 a.m., 07:15
    a.m., ...

    Trips in the time interval


    1

    Calculated headway
    60 minutes

    06:05 a.m., 06:45 a.m., 07:25


    2
    30 minutes
    a.m., ...
    Table 181: Example for headway calculation from mean headway according to timetable
    On the other hand, this approach cannot reflect the following fact: For the passenger who arrives at random, trips spread evenly throughout the time interval generally mean less wait time
    than trips that are piled up. The following third definition, therefore, is used as the default setting for the headway-based procedure.

    PTVGROUP

    475

    7.9.3 Generalized costs as impedance


    From mean wait time according to timetable
    The headway a,b of a line is defined as double the expected wait time for the next departure of the line in the case of random access in the time interval [a,b).
    Fl={x 1, x 2, ..., xn} is the set of departure times of the line in interval l=[a,b). The first departure
    after time b is indicated as x. Since such a departure does not have to exist or can occur later,
    the fictitious departure x=x1 + (b-a), which results from the cyclical continuation of the timetable in l, is also considered. For the calculation of the wait time at the end of l the departure
    xn+1=min{x,x} is used.
    The headway is then defined as follows.

    Here applies:
    ,
    and
    remaining {1, ..., n-1}. i is in each case the expected wait time in a sub-interval.

    to the

    If you now look again at the example with the 40-minute headway and the interval l =
    [06:00,07:00), you get a much more balanced picture.
    Departure times

    Trips in the time interval

    05:55 a.m., 06:35 a.m., 07:15 1


    a.m.

    Calculated headway
    43 20

    06:05 a.m., 06:45 a.m., 07:25 2


    33 20
    a.m., ...
    Table 182: Example for headway calculation from mean wait time according to timetable
    Using the example in the first row, the calculation can be briefly explained as follows.
    In this case n = 1, x1 = 06:35 a.m. and x2 = 07:15 a.m. apply.
    Therefore follows
    and
    Overall this results in

    minutes.

    Compared to the case of the naive approach


    , this example shows that the calculated
    values vary far less when shifting the specific departure times.

    7.9.3

    Generalized costs as impedance


    For route search and choice (see "Route search" on page 492 and "Route choice" on page
    493), paths are assessed by their impedance or generalized costs respectively (see "PuT
    impedance functions" on page 468). They include a perceived journey time PJT and a farebased component (fare or share of fare points).
    IMP = PJT FacPJT + NumberFarePoints or Fare FacFare

    476

    PTVGROUP

    7.9.3 Generalized costs as impedance


    Perceived journey time (PJT)
    The perceived journey time PJT, has the unit "Minutes" and consists of the following times:
    PJT [min] =
    In-vehicle time FacIVT weight attribute of the time profile item
    + PuT-Aux time FacAXT
    + Access time FacACT
    + Egress time FacEGT
    + Transfer walk time FacWT
    + Origin wait time FacOWT (here, the origin wait time is computed according to a formula)
    +Transfer wait time FacTWT weight attribute of the stop area
    + Number of transfers FacNTR
    + Boarding penalty PuT (time profile attribute)
    + Boarding penalty PuT-Aux (transport system attribute)
    + Mean delay (time profile item attribute)
    Here, journey times, costs, etc. are deterministic. The origin wait time and the transfer wait time
    result from the previously specified headway of the PuT line which the passenger boards at
    the origin stop or at the transfer stop. Within the limits of their headways, they depend in a random way on the transfer lines' relative position to each other, except in the case of coordination (see "Coordination" on page 495).
    The run time can be multiplied by a user-selected time profile item attribute in order to model
    the vol/cap ratio (for example the availability of seats) or other aspects of usability (for example
    the level of comfort) of a line.
    Other individual time penalties and weighting factors for boarding events or transfers can be
    taken into consideration as follows (see User Manual: Chpt. 19.2.3.4 , page 2019).
    Wait time factors and penalties on the origin wait time from any attribute of stop areas
    and/or time profiles
    The wait time factor for the transfer wait time from any stop area attribute
    A boarding penalty of any time profile attribute (for PuT lines) or transport system attribute
    (for transport systems of the PuT-Aux type)
    A mean delay from any time profile item attribute
    With the time penalties you can for example model, that some lines are favored by the passengers because of their better quality of traveling, or because they are usually punctual. Via
    the wait time factors and penalties you can model that the passengers prefer waiting at some
    stops than others.
    Via the origin wait time in combination with time profile-based weighting factors you can model
    that passengers do not randomly arrive at the stop but have a profound knowledge of the timetable in the case of long headways. In other words, you can restrict the origin wait time to the
    maximum value X via the weighting factor, for example: For all time profiles with headway T >
    PTVGROUP

    477

    7.9.3 Generalized costs as impedance


    X, enter X / T as the origin wait time weighting factor. In this case, the weighting factor 1 will be
    used for the time profiles with headway T < X.
    Using PuT-Aux transport systems means no wait times, since the permanent availability of
    PuT-Aux TSys is assumed. Using boarding penalties for transport systems of the type PuTAux, you can still model a delay during transition.
    Number of fare points
    The Number of fare points is the total of all fare points that are traversed along the route. Fare
    points can be defined either for a time profile or by transport system for a link. For time profiles,
    four attributes are provided: Fare points per time profile item, fare points for boarding, for passing through, and for alighting at a stop.
    Fare
    As an alternative to fare points, the fare derived from the Visum fare model can also be used.
    There are no restrictions applicable in terms of number or properties of the fare systems or
    ticket types.
    In contrast to the timetable-based variant, which includes the fare of the complete path as impedance component in the choice model, the impedance of the headway-based assignment
    includes the total of the fares by path leg. To reach precise correspondence to the real fare
    model, the property Fare applies to = each path leg separately is required for each of the
    used fare systems, i.e. each boarding passenger has to purchase a new ticket. In other cases,
    in particular for degressive fares over several path legs, the fare total included in the impedance can differ from the fare per total path.
    The example below illustrates how fares are applied in the headway-based procedure.
    The demand from A to B is 100 trips. The supply-side provides two alternative bus connections. The model consists of 5 fare zones, and for the tickets, a zone-based fare has been chosen as fare structure. The table lists the fares depending on the number of traversed fare
    zones.

    478

    PTVGROUP

    7.9.3 Generalized costs as impedance

    Fare zones

    Fare [CU]

    >2

    10

    Example 1
    Either line runs through from A to B, one in the North and one in the South. Either line runs
    regular services every 10 minutes. The North line traverses two fare zones, the fare in the
    impedance function is 5 CU. The South line traverses five fare zones, the fare is 10 CU. With
    an impedance definition of 1 journey time + 2 journey time, the volumes of the south and
    north lines are the same.
    North

    South

    Journey time [min]

    20

    10

    Fare zones (-)

    Ticket fare (CU)

    10

    IMP = 1 Origin wait time+1 Journey randomly in [0,10]+1


    time+ 2 Fare
    20+2 5 = randomly in
    [30,40]

    randomly in [0,10]+1
    10+2 10 = randomly in
    [30,40]

    Volume

    50

    50

    Note: For the description of the volume distribution process in the headway-based assignment please refer to the particular section in this manual (see "Example for the headway-based assignment" on page 492). Since both the headways and fixed impedance
    components of either route are identical, identical volumes are calculated.

    Example 2
    Now, the North variant consists of two separate lines providing coordinated connections with a
    journey time of 10 minutes each. Neither transition times nor transfer penalties are regarded.
    As the headway-based procedure's impedance calculation calculates the fares by path leg, a
    different impedance will be returned compared to the case mentioned above: For the first section, the fare is 5 CU (2 fare zones), for the second section, the fare is 3 CU (1 fare zone), thus
    the fare sums up to 8 CU in the impedance calculation. The volume distribution changes accordingly:

    PTVGROUP

    479

    7.9.4 Choice models for boarding decisions


    North

    South

    JT [min]

    20

    10

    Fare zones (-)

    Ticket fare (CU)

    5+3 = 8

    10

    IMP = 1*Origin wait time+1*Journey time+2*Fare

    randomly in [0,10]+1
    20+2 8 = randomly in
    [36,46]

    randomly in [0,10]+1
    10+2 10 = randomly in
    [30,40]

    Volume

    92

    Remarks on the volume distribution: In the impedance range between 30 and 36, the South
    variant accounts for all shares. In the range between 36 and 40, the probability is
    For the South variant, the resulting probability is

    Summing up the path leg fares in the impedance of example 2 corresponds to the situation,
    where a ticket has to be bought on each path leg. If a different fare system applied in reality
    (because the passenger has the right to use just a single ticket for the trip from origin to destination, for example), an inaccuracy turns out here. For compensation purposes, "transfer discounts" can be defined: Use the Transfer fares function which is provided with the Visum fare
    model for the definition of discounts that balance the fare amount charged too much in the
    case of fare system transfers. To correct the fare taking effect in the impedance formula, the following transfer fare had to be defined in this example: 5 CU - 8 CU = -3 CU.
    Note: The only difference is how fares in the impedance function are taken into account.
    Finally, always the real fare is regarded, which is not the path leg fare total. This is particularly applicable to list outputs and skim calculations. In other words, for assignment
    analyses the real fare is returned by passenger trip.
    Taking fares into account might significantly increase the computation time required for the
    assignment, it actually depends on the complexity of the fare model. Instead of using a fare
    model which mainly consists of proportional (e.g. distance-based) fares the usage of fare
    points is recommended.

    7.9.4

    Choice models for boarding decisions


    In the headway-based assignment it is usually assumed that passengers know line headways
    and times.
    Which additional information they have, is decisive for their choice behavior when boarding or
    transferring. Visum offers four different models:
    No information and exponentially distributed headways
    No information and constant headways
    Information on the elapsed wait time
    Information on the next departure times of the lines from the stop

    480

    PTVGROUP

    7.9.4.1 No information and exponentially distributed headways


    The latter applies for example, when dynamic passenger information systems have been
    installed at stops. The passengers can then see which of the departing lines in the current
    situation offer the least remaining travel time to their destination. As a result, they will for example not board a line if the information system gives them the information, that shortly after this
    line there will be another much faster line.
    The individual choice models for the situation of a passenger waiting at a stop are introduced
    below. To describe the mathematical basis, we still require a few terms.
    Notation
    L = {1, ..., n} describes the set of available PuT lines. Each line i L has a certain remaining
    of the line is derived from the latjourney time si 0 and a headway hi > 0. The frequency
    ter. The term "remaining" should make it clear that we are talking about the remaining journey
    time from the currently considered stop to the destination zone. Only for the choice situation at
    the origin zone we are talking about the journey time of the entire path.
    For the purpose of a more simple modeling we assume additionally that the lines are sorted in
    ascending order according to their remaining journey time. Thus the following applies s1 s2
    ... sn. The set of the first i lines is coded as follows: Li = {1, ..., i}.
    Note, that the remaining journey time s i in fact stands for the generalized costs of line i, which
    contain transfer penalties and further impedance components. For a better understanding we
    will still be talking about "Times".
    On the basis of the available information the different choice models calculate the optimal set
    L* L and for each line i L* a demand share 0.
    i

    It is clear that a line i must be part of L*, if another line j is contained in L * and if si < sj applies
    for the remaining journey times. From sorting the times it can be deducted that i* exists, as a
    consequence L* = Li*.
    The wait time which applies when choosing any set L before boarding, is designated as WL.
    The respective remaining costs are given as follows.

    The parameters are random variables because they depend on the random arrival of lines at
    the stop.
    For the optimal set L* the following also applies: E(CL*) E(CL) for any L L.
    7.9.4.1

    No information and exponentially distributed headways


    If the passenger does not have additional information, he has to decide ad hoc whether to
    board the arriving line or not. The choice model determines the optimal set of lines, and the
    optimal strategy of the passenger is to choose the line in the set that arrives first.
    In addition to the missing passenger information, the model introduced in this section is most
    notably characterized by the fact that the headway (the temporal gap between two departures
    of a line) is not assumed to be a constant, but rather exponentially distributed. The expected

    PTVGROUP

    481

    7.9.4.1 No information and exponentially distributed headways


    gap value is exactly the same as for constant headways 1 / i, therefore the "Frequency" of the
    line. In contrast to constant headways, however, the headway times strongly scatter around
    this value.
    Fundamental characteristic of the exponential distribution which is taken as a basis is that the
    wait time which has already elapsed since the last departure of the line, does not state how
    long the passengers have to wait for the next departure. This property is called "Memorylessness". Thus, the greatest possible irregularity of the timetable is assumed.
    The optimal set under these model assumptions is composed as follows. The following is set
    first:

    Then, the optimal set of lines is achieved by L* = Li*, where i*=max{i:si ui-1}.
    It can be proved that the i* composed in such a way reduces the expected remaining costs.
    A line i thus exactly belongs to the optimal set, if its remaining travel time (without wait time) is
    not higher than the expected remaining travel time plus wait time of the combined lines Li-1 =
    {1, ..., i-1}. This procedure has the effect, that comparatively few lines are used, because with
    this comparison the lines Li-1 are treated in such a way, as if they were perfectly coordinated.
    Coordinated here means, that they are arranged so evenly, that they appear as a single line
    with frequency
    tribution.

    . Such an additivity is only given in the case of exponential dis-

    The share of the lines i L* are equal to the probability, that they depart first, as can be taken
    from the following formula.

    Note, that the remaining travel times of the lines do not appear in the share definition. If lines
    are adequate enough to be contained in the optimal line set, their shares only depend on their
    headways. This property illustrates the heavily simplified construction of this choice model.
    The resulting expected wait time is as follows.

    This choice model should only be used, if the line headways are extremely irregular, in other
    words, if the passengers face a high level of uncertainty.

    482

    PTVGROUP

    7.9.4.2 No information and constant headways


    7.9.4.2

    No information and constant headways


    With the same level of information, however, constant headways, the strategy of a passenger
    is in principle the same. From an optimal line set L* = Li* he or she selects the line which arrives first. The determination of i* now follows the following different approach.
    You can recalculate that it is insufficient in this case, to regard the result (L 1, L2, ..., Ln) of potentially optimal line sets and to cancel exactly at that point when for the first time the following
    applies: EC Li > EC Li-1 . This is caused by the fact, that there can be more than one local miniguarantees, that the optimal line set
    mum in the sequence (L i). Therefore
    is composed exactly from those lines, which reduce the expected remaining costs if being
    included in the selection.
    The shares assigned to the individual lines again correspond with the possibility of arriving
    first.

    is the minimal occurring headway. This results in the following expected wait
    time.

    If the timetable in the analyzed network is regular and only slightly irregular, and the passengers do not have any information on departure times, this choice model is more realistic
    than the model considered before.
    7.9.4.3

    Information on the elapsed wait time


    If - in case of constant headways - the passenger makes use of the information on how long he
    has been waiting already at the stop, he will be able to reduce his expected remaining costs in contrast to the previously described models. The passenger knows for example, that after
    waiting eight minutes, a line with 10 minutes headway has to arrive within the next two minutes. The passenger can make use of this information and ignore potentially earlier arriving
    lines, which are, however, at least two minutes slower.
    The passenger has this information independently of the external infrastructure. To assume
    this is therefore not a strong assumption.
    In this case, the optimal line set L* depends on the elapsed wait time and is therefore no longer constant. Determining the set is more difficult than in the previous cases. It can be proven
    that L* has the following shape.

    PTVGROUP

    483

    7.9.4.4 Information on departure times


    Given are i* n and an orderly sequence of times 0 t i* ... tl. This means that in time interval Ij= (tj+1 ,tj] just Lj = {1, ..., j} forms the optimal line set. tj is here the exact point in time t, from
    which onward the remaining journey time of line j is greater than or equal to the expected
    remaining costs (including wait time according to t) of the lines Lj-1. In other words, tj is the unique solution for t in

    The optimal strategy is as follows. If the passenger observes an arrival of a line from Ij ,
    after wait time Lj, he will board that line. Other lines he will ignore.
    One can show that this strategy reduces the expected remaining costs. As illustrated in the following, it corresponds more with the real behavior of passengers than its abstract definition.
    Because the passenger knows the headways of all lines, his knowledge on which available
    lines are still worth taking, increases the longer he is waiting. Comparable slower lines may
    still be reasonable options at the beginning of the wait time. There is a time, however, when
    the evaluation topples. At a certain time, the expectancy for the remaining wait time for the
    faster j-1 lines is less than the difference between their remaining travel time and the remaining travel time of the line j. Exactly as of this time is it no longer worth it to take line j even if
    it arrives immediately. The times t j mentioned above are exactly those moments when a line j
    is no longer included in the optimal line set L* for this reason.
    Example
    Let us regard the following simple situation of two lines.
    Line

    Run time

    Headway

    10

    15

    2
    13
    15
    Table 183: Considering elapsed wait time
    The passenger waits maximum 15 minutes to continue his journey. After t minutes the expected remaining travel time for line 1 is exactly 10 + (15 - t) / 2 minutes. To determine the point of
    time as of which this expected value is less than the run time of line 2, you resolve 10 + (15 - t)
    / 213 according to t which results in t 9, thus t2 = 9.
    In other words, a vehicle of line 2 can be ignored after 9 minutes, because the three minutes
    longer run time of line 2 is not made up by the mean remaining wait time for line 1.
    7.9.4.4

    Information on departure times


    This model is based on the assumption that a passenger does not only know the times and
    headways of all lines, but can (at least at the stop) also get information on precise departure
    times. The optimal strategy can thus be formulated as follows.
    A passenger boards the line that offers the least remaining costs given the actual departure times.
    Unlike in previous cases, the passenger does not simply board the first arriving line of a certain (possibly time dependent) set. Because all wait times wi are known, the passenger's deci-

    484

    PTVGROUP

    7.9.4.4 Information on departure times


    sion is not subject to stochastic influences. He or she rather selects exactly that line whose
    remaining costs si+wi are at a minimum.
    The optimal line set thus consists of all lines, which have the least costs in some timetable positions.
    and
    The optimal set of lines are those, which are optimal in border cases, since they arrive without
    a wait time, whereas all other lines have to be waited for by a complete headway.
    The calculation of shares is as follows.

    [60.1]

    [60.2]

    [60.3]

    [60.4]

    [60.5]

    [60.6]
    Explanation of the derivation
    In row [60.1], the entire passenger information is used. Line i is selected if its remaining costs
    Ci are lower than those of the other lines. Row [60.2] reformulates the expression, by using the
    density function of the random variable Ci . Due to constant headways Ci is equally distributed
    in [s i,s i + hi). (If the wait time is weighted with a factor, this should be put in front of hi, the calculation otherwise does not change.)
    In row [60.3] we take advantage that the departures of the lines are independent of each other.
    In all choice models this is a basic assumption of the headway-based assignment. To avoid
    case differences, the integration range in [60.5] is separated into sections, in which the inner

    PTVGROUP

    485

    7.9.5 The complete choice model


    product is extended over a constant set of lines. It has to be noted that for j > k and x [sk,sk+1)
    the following must apply: P(Cj > x) = 1. This is due to the sorting of the lines at the beginning,
    because the costs of line j > k sum up to at least s k+1. In the last step [60.6] we then apply the
    distribution function of Cj which again is an equal distribution. At the end of the invoice, the
    result is a sum of polynomials with a maximum degree of i*.
    The expected wait time is achieved analogously.

    To assume passenger information is no extremely strict requirement. Many places already


    have information systems which display the next departure times on the basis of real-time operating data. Alternatively, timetables could be hung up at stops. There are also no limits regarding other technical resources.

    7.9.5

    The complete choice model


    The choice models for boarding decisions all apply to the situation of a passenger, who is waiting at a stop for departures of suitable lines (see "Choice models for boarding decisions"
    on page 480). Even if the assumed level of information varies strongly between the models, it
    always applies that the passenger decides for one of the different lines, due to observations
    (arriving vehicles).
    In general, there may also be other situations:
    The passenger is still at the start of the journey (at origin zone).
    The passenger is on board a line.
    The passenger can choose between transfer stops which may only be reached by a footpath.
    In such cases, the choice has to be modeled in a different way, because it generally is not
    based on observations, but on estimates . However, when passengers rely on estimates or
    not again depends on the passenger information available in the network. Below it is described briefly under which conditions observations are not restricted to the departures of the
    lines at the current boarding stop.

    7.9.5.1

    486

    Extended applicability of the departure time model


    With a suitable infrastructure, a stop-based departure display can also be seen by passengers
    in arriving lines before alighting. In this case, the choice model Information on departure
    times (see "Information on departure times" on page 484) is not just applied to the possible
    transfer lines, which are available after alighting. In fact, it already refers to the decision of the
    passenger still on board, because by acknowledging the departure times early enough, the
    passenger can judge whether continuing the journey on the same line is more profitable than
    getting off. This also applies, if information on connections provided at the next stop is displayed in the vehicles.

    PTVGROUP

    7.9.5.2 Modeling the choice on the basis of estimates


    Another relevant difference in cases is the question, whether passenger information systems
    at a stop only display departure times of those lines which depart from just this stop. In some
    places, displays are used which also include the departures of other lines, departing at stops
    close-by. An example of this is the display of departures of subway lines in the concourse.
    Are both of these features provided, also a passenger who is still on board of a line knows the
    next departure times of all potential transfer lines at the current stop and at those which can be
    reached by foot from this stop. The model is then applied to the total set of available lines. The
    technical realization of such a level of information can for example be a service, which provides via cell phone the information on the current timetable and - on the basis of operational
    real-time data - a recommendation for the passenger. A completely different model assumption, which nevertheless leads to the same level of information, is the passenger's knowledge of the timetable.
    The border case of complete passenger information is provided, if the situation described
    above is also assumed, when the passenger is still at the starting point (thus in the origin
    zone) of his journey. In order to observe also the departure times of the possible boarding
    lines from there, again a mobile information service or complete knowledge of the timetable
    have to be assumed.
    7.9.5.2

    Modeling the choice on the basis of estimates


    Apart from the case of complete passenger information, there always are also decisions which
    are made on the basis of estimates. The simplest example is the choice between several boarding stops at the start of the journey or at a transfer. If passengers do not have any information
    on departure times on board, the decision on continuing the journey or getting off, in this case
    depends on the expected remaining journey time after alighting.
    Such decisions can be modeled in two ways:
    By a discrete choice model
    By a 0/1 decision in favor of the best alternative
    The second case reduces the expected remaining costs, however, does not reflect the fuzziness of the passengers' behavior. That is why a discrete choice model should be favored normally. If the flexibility parameter goes towards infinity, the result comes close to the 0/1
    decision in favor of the alternative with the lowest expected remaining costs anyway.

    7.9.5.3

    Hierarchical structure of the choice


    In general, we can now model a passenger's decision as a sequence of separate decisions.
    Each of them is either based on estimates or observations. In the first case, we use a discrete
    choice model to obtain a distribution between the alternatives. In the second case, one of the
    choice models for boarding decisions is applied (see "Choice models for boarding decisions"
    on page 480).
    The result of the decision made on a lower level becomes part of the decision on a higher
    level, in form of expected remaining travel time.
    The different levels of information and the various decision situations produce different hierarchical structures for the passenger's decision as a whole. Three examples illustrate the procedure in principle (see "Example for the choice models" on page 488).

    PTVGROUP

    487

    7.9.5.4 Example for the choice models


    7.9.5.4

    Example for the choice models


    Let us look at the following network.

    Illustration 156: Example network for choice models


    We analyze the decision of a passenger, who is on board of line 1 and arrives at stop A. First,
    we will look at how the structure of the choice made changes, if the available information
    varies.
    The analyzed scenarios are the following.
    1. No information, constant headways
    2. Departure time information per stop, not available on board.
    3. Departure time information per stop, also available on board.
    4. Departure time information for all stops, not available on board.
    5. Departure time information for all stops, also available on board.
    Hierarchical structure
    In the first example we are looking at the situation in scenario 1.

    Illustration 157: Structure of the choice in scenario 1 (no information)

    488

    PTVGROUP

    7.9.5.4 Example for the choice models


    In the illustration, circles represent lines and rectangles indicate stops.
    Here the passenger first decides between continuing the journey or getting off, though the
    remaining journey time resulting from the second alternative can only be estimated. After alighting a decision is made for the boarding stop (A, B or C), which again is only based on expected values. Only after having arrived at this stop the passenger can make a definite decision
    on the boarding line, on the basis of observations (of the arriving vehicles).
    In the second example we assume that departure times are displayed at stops. The decision
    structure then changes as follows.

    Illustration 158: Structure of the choice in scenario 2 (local information)


    In contrast to the example above, the passenger identifies the next departure times of line 2
    directly after getting off at stop A. The passenger is thus able to determine exactly what the
    wait time and the remaining journey time will be, if he continues his journey from there. Compared to that, the passenger knows only expectations for the boarding stops B and C.
    In the third example, let us assume that already on board the line the passenger can find out
    which connections are available from stop A. The decision tree then looks as follows.

    PTVGROUP

    489

    7.9.5.4 Example for the choice models

    Illustration 159: Structure of the choice in scenario 3 (information in the vehicle)


    The characteristic of the first decision now changes, because continuing the journey with line
    1 and a transfer to line 2 or 3 now represent alternatives on the same level, as all wait times
    are known.
    Comparison of the calculated shares
    It is informative to know what influence the applied choice model has on the shares of the lines
    and the mean remaining costs. Let us take the following definition of generalized costs to simplify the calculation.
    Costs = 1.0 In-vehicle time + 1.0 Walk time + 1.0 Wait time + 1min Number of transfers
    Travel times and headways of the lines in the example network are illustrated in table 184.
    Line

    Run time

    Headway

    Start -> A 5
    A -> Destination 8

    10

    15

    5
    3
    10
    Table 184: Travel times and headways of the
    lines in the example network
    The passenger's situation on board line 1 arriving at stop A is interesting, because there are
    several transfer options which assure a shorter remaining journey time. The table 185 shows,
    that the passenger can derive a much bigger advantage from these transfer alternatives, the
    more information he has on the arising wait times.

    490

    PTVGROUP

    7.9.6 The search in general


    Scenario 1

    Scenario 2

    Scenario 3

    Scenario 4

    Scenario 5

    60.1

    59.7

    32.3

    45.4

    28.2

    Share of Line 2 [%]

    9.0

    9.0

    11.7

    13.8

    22.7

    Share of Line 3 [%]

    10.3

    6.8

    12.1

    9.6

    9.2

    Share of Line 4 [%]

    10.3

    14.4

    25.7

    22.4

    27.6

    Share of Line 5 [%]

    10.2

    10.2

    18.2

    8.8

    12.4

    Mean costs [min]


    1839
    1838
    1820
    1736
    1700
    Table 185: Line shares and the mean costs depending on the information available
    The mean costs in the last row refer to the entire route.
    The difference between scenario 1 and 2 is very small, because information on departures at
    the local stop is only an advantage if thereby one is able to ignore a line with a longer journey
    time in favor of a more appropriate line arriving shortly after. In this network, this case only
    occurs with a low probability and only at stop B.
    If the same information is already provided on board (scenario 3), the shares of the individual
    lines already change considerably, the mean costs, however, only a little. The reason being,
    that the most attractive transfer lines in this example do not depart from stop A.
    Because of this, the expected remaining costs are then reduced when information on departure times are not only provided for the local lines of a stop, but for all the lines of all stops
    nearby (scenario 4). From the resulting relatively large set of possible lines, the passenger can
    choose the line with the least remaining journey time. The effect becomes more clear if the passenger can already make such a decision on board line 1 (Scenario 5). The mean costs
    savings in this example equals 139 minutes - which means considerable 14 percent on this
    path leg from A to destination.

    7.9.6

    The search in general


    The travel demand of an OD pair is entered at the origin zone. Several alternatives having different headways and impedances may be available with the choice of the first line already.
    The entire demand is now split up as is the case at all later decision points - between all reasonable alternatives. How this happens exactly depends on the choice model used (see
    "Choice models for boarding decisions" on page 480 and "The complete choice model" on
    page 486).
    Stochastic fuzziness becomes involved here in that all used lines possess a headway and the
    wait time for a line is thus random. Even a line which is less attractive due to its larger impedance can be given a certain percentage of the demand. If passenger information on departures is available, this may occur exactly then for example, if the line with positive probability
    departs so much earlier than other, qualitatively better alternatives that this time advantage
    makes up for with its higher impedance.
    As a result of this fundamental model assumption, the route search in the headway-based assignment is not based on shortest path searches, but creates a directed decision graph for each
    destination zone. Stops at which passengers are provided with several alternatives represent

    PTVGROUP

    491

    7.9.7 Example for the headway-based assignment


    the nodes of this decision graph, these are known as decision points . The paths in this graph
    represent the various options to reach the destination zone.
    The decisive factor is the assumption that, from the various options available, the passengers
    will make their choice for the continuation of their journey at each stop on the basis of this probability graph regardless of how they reached this stop.
    Consequently, search and choice in the headway-based procedure are organized so that, working backwards from each destination zone, all options are calculated to allow passengers to
    move from the stops of the network towards the destination zone. The mean impedances of
    the decision points for which a distribution has already been calculated are then used for the
    iterative calculation of the distribution for more distant decision points.
    In the course of this search, only such routes are maintained (this means only those paths are
    loaded in the decision graph), which are positively assessed by the selected choice model. In
    the case of passenger information, this means that a path at each traversed decision point is
    probably the best option amongst all available alternatives. Similar statements apply for the
    other choice models.
    Optionally, all dominated paths can be singled out from these. A path is dominated by another
    path if it applies to the same OD pair, uses the same sequence of time profiles (in the same
    order), has the same start stop and end stop, yet has a longer total journey time (usually due to
    the selection of less convenient transfer stops).

    7.9.7

    Example for the headway-based assignment


    Headway calculation
    For the PuT supply displayed in illustration 160 the headway-based procedure determines the
    headways for the analyzed time interval from 05:30 a.m. to 07:30 a.m. (120 minutes) illustrated
    in table 186 if these are calculated according to the method from mean headway (see "Headway calculation" on page 475).
    Line

    Mean follow-up time

    Headway

    Bus 1

    120 / 3 * = 40 min

    40 min

    Train

    120 / 2 ** = 60 min

    60 min

    * 3 departures in analyzed interval (6:10, 6:55, 7:25) from A-Village


    ** 2 departures in analyzed interval (6:25, 7:05) from Station
    Table 186: Headway calculation for the example
    Route search
    The case is, that passenger information on departure times exists and is also available on
    board of the bus line. At route search, the procedure then determines two routes from A-Village to X-City, if each of the two alternatives is with (even low) positive probability better than
    the respective other one.
    Route 1 (bus 1, no transfer) and
    Route 2 (bus 1 and train, 1 transfer)

    492

    PTVGROUP

    7.9.7 Example for the headway-based assignment


    Probability becomes involved in that the wait time for the train in the case of a transfer is within
    a range of between 0 and 60 minutes and no fixed transfer time has been assumed in
    advance.
    If no extremely high transfer time penalty is used, some of the passengers will certainly use the
    transfer option. This is because the train will leave (with a certain level of probability) only
    shortly after the bus arrives and the passengers will thus arrive at their destination more
    quickly.
    Because the probability of obtaining an unfavorable connection in this case is significantly higher, however, the majority of the passengers will continue their journey by bus.
    The decisive factor is thus not only the mean wait time for the train in the example given, this
    is 30 minutes but the complete range of possible wait times. Due to the existing passenger
    information, each of the two routes thus receives precisely that portion of the demand that corresponds to the chance of being the better of the two options.
    Route choice
    In order to determine a distribution in the example given, specific impedance parameters have
    to be used. These are set as follows.
    Imp = PJT 1.0 + number fare points 0.0
    Perceived journey time PJT = in-vehicle time 1.0
    + Access and egress time 1.0
    + Walk time 1.0
    + Origin wait time 1.0
    + Transfer wait time 1.0
    + Number of transfers 2 min
    In this way, the impedances listed in table 187 are calculated for a passenger arriving at the
    railway station on Bus 1 for the remaining route legs.
    Route 1

    Route 2

    Egress time, walk time

    0 min

    0 min

    Run time

    33 min

    16 min

    Transfer wait time

    0 min

    randomly in [0 min, 60 min]

    Transfer time penalty

    0 2 min = 0 min

    1 2 min = 2 min

    IMP = PJT 1.0


    33 min
    randomly in [18 min, 78 min]
    Table 187: Impedance calculation for the routes in the example
    From the impedances Imp1 and Imp2, the following percentages P1 and P2 of the OD demand
    (in this case: 90 trips) result and thus the absolute number of trips on both routes (M1 or M2).
    This occurs as follows.
    The decision as to which of the routes is more attractive depends on whether the random variable Imp2 is greater or smaller than the constant variable Imp1. Because Imp2 is uniformly dis-

    PTVGROUP

    493

    7.9.7 Example for the headway-based assignment


    tributed in the interval [18, 78[ and Imp1 is equal to 33, the probability for choosing Route 2 is
    thus 0.25 according to the formula below.

    This means that 90 0.25 = 22.5 passengers decide to travel by train and 90 0.75 = 67.5 passengers to continue their journey by bus.
    This results in the volumes shown in illustration 160.

    Illustration 160: Volume for headway-based assignment, transfer penalty 2 min


    With any variation in the transfer penalty, this portion changes as shown in table 188. For other
    impedance parameters, the same applies.
    Transfer time penalty

    Portion of Route 1

    Portion of Route 2

    0 min

    0.717

    0.283

    1 min

    0.733

    0.267

    2 min

    0.750

    0.250

    5 min

    0.800

    0.200

    10 min
    0.883
    Table 188: Changes to shares with variation of the transfer penalty

    0.117

    The skim values for the relation from A-Village to X-City are shown in table 189. These values
    are the mean skim data of both routes which weighted with the number of passengers are
    summarized for the impedance parameters used here.
    Route Set

    Pass. In-veh.
    time

    Pass. TWT

    Pass. Ride time

    67.5

    67.5 45 min

    67.5 0 min

    67.5 45 min

    67.5 0

    22.5

    22.5 28 min

    22.5 7.5 min

    22.5 35.5 min

    22.5 1

    Total

    90

    3 667.5 min

    168.75 min

    3 836.25 min

    22.5

    Mean

    3,667.5 / 90
    168.75 / 90 =
    3,836.25 / 90 =
    = 40.75 min
    1.875 min
    42.625 min
    Table 189: Mean skim values for the headway-based assignment

    494

    Pass. NTR

    22.5 / 90 =
    0.25

    PTVGROUP

    7.9.8 Coordination
    Please pay particular attention to the transfer wait time of 7.5 minutes for Route 2. In this case,
    the figure is not 60 / 2 = 30 minutes even though the train's headway is 60 minutes. This is due
    to the fact that passengers will only take the train if the transfer wait time is short enough to
    be precise, when this time (as seen above) is within a range of zero and 15 minutes. In all
    other cases, there is no benefit in transferring. The 7.5 minutes transfer wait time in the choice
    of Route 2 therefore represents a conditional expectancy value it is the mean wait time for
    those passengers for whom Route 2 is in fact the best alternative.

    7.9.8

    Coordination
    In Visum, the coordination can be used for the headway-based assignment. This is realized by
    so-called coordination groups.

    7.9.8.1

    Function of coordination groups


    A coordination is defined between two or more lines to indicate that, for the passengers' benefit, the trips of these lines are equidistant in terms of time on a shared route section. As a consequence, the relevant line bundle is treated at the shared stops throughout the entire
    procedure as a single line that operates with greater frequency. This results in a shorter mean
    wait time than is the case with the (by default) assumed stochastic uniform distribution of the
    relative position of the lines to each other.
    A coordination group is a bundle of time profiles on a conjointly used passage. Two stops
    mark the boundaries of the section. The significance of a coordination group lies in the calculation of the mean wait time in the context of the headway-based assignment. In this assignment procedure, it is usually assumed that the time interval between departures on different
    line routes (strictly speaking: time profiles) is coincidental. With the aid of coordination groups,
    you can display that certain line routes run in a rhythm of equal intervals to the advantage of
    the passengers just like it is often the case in real life.
    Note: In the timetable-based assignment, coordination groups bear no meaning as departure times can be gathered from the timetable here. In contrast, the headway-based assignment calculates with average wait times only. Coordination groups come into play
    when it ought to be expressed that those wait times are shorter than those arising from a
    coincidental arrangement of the line routes.
    Please note that splitting up a line into two new lines, each with half the supply, does therefore
    not lead automatically to the same result in calculation. It must not be assumed in advance
    that a coordination exists. Coordinations have to be explicitly specified. The illustration 161
    shows an example.

    PTVGROUP

    495

    7.9.8.2 Matched transfers

    Illustration 161: Coordination of lines


    Considering only the red-blue line, a passenger arriving randomly has a mean wait time of 5
    minutes precisely half the headway.
    If this line is split up into a blue and a red portion without defining a co-ordination, a mean wait
    time of 6:40 minutes results after the headway calculation. This is the expected value of the offset to the next departure of one of the two lines and, depending on the relative position of the
    two lines to each other, this offset can be somewhere between 0 and 20 minutes.
    Defining a coordination indicates that the interval between departures of the red and the blue
    line remains constant at 10 minutes. As in the initial situation, this results in a mean wait time
    of 5 minutes.
    7.9.8.2

    Matched transfers
    The transfer time between two lines at a stop is normally a combination of the transfer walk
    time taken from the transfer walk time matrix (see User Manual: Chpt. 15.24.2 , page 1238)
    and the random wait time for a trip of the successor line. This results from the fundamental
    model assumption that passengers a priori have no information on the exact departure times
    of the lines, but only know their in-vehicle times and headways.
    In some cases, however, it is desirable to model that the transfer time between two lines is not
    stochastic, but assumes a fixed value. This is particularly important in networks with longer
    headways, in which the existence of coordinated connections is nevertheless assumed.
    In this case, for a pair of time profiles at a stop, a so-called matched transfer can be defined.
    Transfers from one time profile (see User Manual: Chpt. 15.24.2 , page 1238) to the other then
    require precisely the specified duration each time (see User Manual: Chpt. 19.2.3.2 , page
    2014).

    7.9.8.3

    Example for the coordination


    For a passenger, a single line route with headway of 20 minutes means a mean wait time of
    10 minutes. Whether the introduction of a second line route of the same headway means that
    the wait time will be reduced to 50% depends on its concrete temporal position. A sequence
    like 8:00 8:02 8:20 8:22 - ... for example does not yield a noteworthy improvement.
    If, however, two such line routes are coordinated, the headway-based assignment assumes
    that the departures are of equal intervals and thus timed like this: 8:00 8:10 8:20 8:30 - ....
    As a result, the average wait time is reduced to 5 minutes. Without coordination, all positions in

    496

    PTVGROUP

    7.9.8.4 Assume coordinated time profiles to be undistinguishable


    the timetable are considered equally probable. The expected value for the wait time is then
    6:40 minutes.
    Coordination only acts on those stops (on the section marked by the start point and end point)
    at which the coordinated time profiles actually stop. If only a subset of the coordinated bundle
    stops at a stop, only the time profiles that stop are considered coordinated at that stop.
    Note: The coordination of time profiles ends at the ToStop, that is, the arrival times of the
    time profile are still coordinated at that stop but the departure times are not.
    If there is an overlap between the coordination groups to be defined, only the first coordination
    group of each time profile item is considered. In this case, a warning is triggered at the beginning of the assignment.
    Note: If a network-wide coordination is assumed for a headway-based assignment,
    option Coordination everywhere can be used during the assignment. Coordination
    groups are then redundant.
    7.9.8.4

    Assume coordinated time profiles to be undistinguishable


    For identical headways, the coordination's mechanisms of action is clearly defined. Since coordination groups can be defined for arbitrary time profiles in Visum, however, there is not
    always a natural definition of the aggregate headway.
    The approach implemented so far, which corresponds with the procedure in the program
    VIPS, is based on the assumption that the passengers can differentiate between the individual
    time profiles in a coordinated bundle and also make their choice against attributes of the
    respective time profile.
    The new approach, which is realized in the program via the option Assume coordinated time
    profiles to be undistinguishable , is based on the following algorithm. Ti are the headways of
    the coordinated time profiles.
    In the first step, the aggregate headway T is set as follows for the coordination group.
    T := 1 / (1 / T1 + ... + 1 / Tm)
    This is the harmonic mean of the given Ti. The number of services corresponding to this
    headway is equal to the sum of the number of services of the individual time profiles.
    Example: T1 = 6', T2 = 7.5 (i.e. 10 + 8 services per hour) yields an aggregate of T = 10/3,
    which also corresponds to 18 services per hour.
    For each time profile, the proportion of the total number of services is given by i = T / Ti.
    This fraction is also used as the relative share of the demand within the time profile
    bundle, i.e. pi := i. The aggregate impedance is again set to C := c1 p1 + + cm pm with
    ci = impedances of the time profiles.
    Using the standard algorithm, the virtual aggregate time profile m* with headway T and
    impedance C is compared with the other time profiles (see "Route search" on page 492
    and "Route choice" on page 493).

    PTVGROUP

    497

    7.10 Timetable-based assignment


    Model approach
    Here, the general assumption is that the time profiles in the coordinated time profile bundles
    are not distinguishable. The time profile attributes headway and impedance are irrelevant. Instead, the headway is calculated with the focus on the number of services.
    As a consequence, each time profiles proportion of the total number of services can be used
    as demand share per time profile. Passengers that cannot differentiate between the different
    time profiles of a time profile bundle will automatically board the first service available. Therefore, the passenger volume of each contained time profile is proportional to the alternative's
    number of services.
    Furthermore, the aggregate impedance is defined as the weighted mean of the single time profiles impedances, this time using the service frequency shares i as weights. This makes
    sense because the resulting aggregate is the mean impedance of all services. For the passenger, this is the expected impedance when boarding the first available service of the TP
    bundle.
    Example
    The example illustrates the difference between the already existing approach and the new
    one:
    For the undistinguishable approach, the aggregate headway T is equal to 6/7, i.e. only 46
    seconds. The aggregate impedance is C = 22.77. This value is much larger than before since
    the high-impedance time profile 1 plays a more significant role now.

    7.10

    TP

    Impedance Headway

    Distinguishable (Standard) Undistinguishable

    24

    0.0166

    0.7692

    20

    0.3366

    0.1538

    16

    10

    0.6466

    0.0769

    Timetable-based assignment
    A search method is called timetable-based if all services of PuT lines are taken into account
    with their precise departure and arrival times.
    Timetable-based methods are suitable for assignments and the calculation of indicators, when
    a line network plan and a detailed timetable are available for the PuT supply analyzed. They
    take the coordination of the timetable into account and thus ensure very precise results of the
    indicator data calculation.
    The timetable-based method calculates connections for each OD pair. In the Search it is assumed 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 search impedance. For the connection
    search, two variants (branch & bound search and shortest path search) are offered that represent the different compromises between the number of alternatives on the one hand and the
    memory and computing time requirements on the other.

    498

    PTVGROUP

    7.10.1 Evaluation of the timetable-based assignment


    During preselection of connections, the connections yielded by the search algorithm are reanalyzed by means of general criteria as to whether some of them are of a significantly lower
    quality and can thus be deleted.
    During the choice, 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.

    7.10.1

    Evaluation of the timetable-based assignment


    The timetable-based assignment is characterized by the following features.
    Using the Branch & Bound option (see "Connection search using Branch and Bound" on
    page 499), the procedure calculates all suitable connections throughout the entire analysis period. This also includes the calculation of several connections with different impedances (for example shortest time and minimum transfer connections) for a departure
    time. In the case of a monocriterion shortest path search (see "Connection search using
    shortest path search" on page 501), only one connection is calculated for each departure
    time, as this reduces the memory and computing time requirements. The search can be
    influenced by means of the search impedance definition.
    Branch & Bound search is suitable for the analysis of a period - for example the whole day
    or several hours (see "Connection search using Branch and Bound" on page 499). When
    performing a search at a specific Time (e.g. in the case of a graphical route search), the
    shortest path search is recommended (see "Connection search using shortest path
    search" on page 501).
    The actual transfer wait time, and thus the coordination of the timetable, is taken into
    account.
    All indicators in the analyzed time interval can be calculated.
    The decision model for the connection choice (see "Connection choice" on page 505)
    models the actual decision behavior 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 choice).

    7.10.2

    Connection search
    Two methods are provided for the connection search: Shortest path search and Branch &
    Bound.

    7.10.2.1

    Connection search using Branch and Bound


    For each origin zone, a search tree of suitable partial connections is generated which stores
    all sufficiently suitable connections from this origin zone. This means that not only the best
    connection is found for an OD pair, but a large number of good connections. In this way, a very
    selective distribution of travel demand is possible.
    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 = JRT FacJRT + NTR FacNTR + TSys-Imp FacTSys-Imp + VehJ-Imp FacVehJ-Imp

    PTVGROUP

    499

    7.10.2.1 Connection search using Branch and Bound


    Besides the journey time and the number of transfers, also TSys-specific penalties are as
    TSys-Imp among others. That is, how common distance-based fares can already be considered during the search. The complete Visum fare model will take effect during the
    connection choice. However, this is no restriction, since the approximate fare calculation
    during the search is sufficient for the distinction between reasonable routes and useless
    ones.
    Via VehJ-Imp, also the vehicle journey-specific impedance is added. It results from two
    freely selectable attributes of the vehicle journey items as boarding supplement and as
    general discomfort term. In this way, individual vehicle journeys can be favored or penalized.
    (Partial) connections to a destination or intermediate node are evaluated and compared
    with any other (partial) connection to the same point. Then it can efficiently be decided
    which branches of the search tree can be continued ("branch") and which have to be cut
    ("bound") (see "Dominance" on page 500 and "Bounding" on page 501).
    It is possible to specify an upper limit for the number of transfers in a connection.
    Dominance
    Pairwise comparisons are helpful for the identification of useless connections.
    If a connection is in no respect more appropriate than another connection in the same temporal position, then this connection is called dominated and will be discarded. This means in
    detail:
    A connection c dominates a connection c, if
    c lies within the time interval of c
    NumTransfers (c) NumTransfers (c)
    SearchImp (c) SearchImp (c)
    and real inequality applies to at least one of the three criteria.
    To compare two connections without defined temporal position (that means: without path legs
    of the 'PuT line' type) the first rule is changed to the following: Journey time (c) journey time
    (c).
    Example:
    Connection 1 dominates connection 2, since it is really located in the time interval of
    connection 2 and because other indicators of connection 1 are either as good as those of
    connection 2 or even better.
    Connection 1 does not dominate connection 3, since the temporal positions differ, nevertheless connection 1 might be useful for those passengers who want to depart later though
    the indicators of connection 1 are worse.
    Connection 1 does neither dominate connection 4, since connection 4 does not require
    as many transfers as connection 1 which might be acceptable for some passengers
    though this means a longer journey time.

    500

    PTVGROUP

    7.10.2.2 Connection search using shortest path search


    Criterion

    Connection 1

    Connection 2

    Connection 3

    Connection 4

    Temporal position

    6:00 - 7:00

    6:00 - 7:10

    6:10 - 7:20

    5:30 - 7:20

    Number of trans- 1
    fers

    SearchImp

    4,000

    4,200

    4,300

    5,400

    Dominance

    ---

    Dominated by
    conn. 1

    ---

    ---

    Bounding
    Besides the temporal position, the following rules are applied to exclude connections which differ considerably from the optimum in one or several criteria:
    A (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
    Number of transfers of the connection > minimum number of transfers + constant.
    As a matter of principle, connections which are optimal in one of the three dimensions will not
    be deleted in this step, even if they violated the rule of another dimension.
    7.10.2.2

    Connection search using shortest path search


    This option uses 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 this data calculates the best
    connection between two traffic zones for a particular departure time. For different times of
    departure, various "best" connections may be calculated which may differ by the used PuT
    lines and/or transfer stops. To determine all "best" connections within the analyzed time interval the shortest path algorithm is performed several times for all possible departure times
    within the analysis time interval.
    Since in some cases several connections are possible for a given time of departure, a definition of "best connection" is required for these search procedures. For this purpose Visum provides an impedance function which increases the impedance of a connection for each transfer
    by the transfer penalty. A low penalty has the result that connections which take the least time
    are favored, while a high transfer penalty gives priority to connections with a lower number of
    transfers.
    Determination of all possible start times for trips which originate in traffic zone i. The start
    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 one of the two following steps is executed.

    PTVGROUP

    501

    7.10.3 Connection preselection


    Either a monocriterion shortest path search is carried out which searches for the "best"
    path from traffic zone i to traffic zone j starting at the given time. The search procedure
    identifies the path with the lowest impedance as the best path. The impedance of the path
    is measured in minutes and is a linear combination of journey time and number of transfers. It consists of the following time components.
    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] (adjustable).
    This lowest impedance path 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.
    Or the connection with the minimum journey time (so-called bicriterion shortest path
    search) is calculated for each permitted number of transfers (for all integer values 0 and
    max. number of transfers). If the calculation returns identical journey times for different
    numbers of transfers, the program only stores the connection with the lowest number of
    transfers (dominance).

    7.10.3

    Connection preselection
    The preselection of connections compares and evaluates all found connections. This includes
    the check, whether a connection could be replaced by a more suitable one and thus can be
    deleted. Only convenient connections are offered to the passengers for the connection choice.
    In order to identify inconvenient connections, the following exclusion rules are applied in turn.
    Search impedance of the connection > minimum search impedance factor + constant
    (unrestricted; only Branch & Bound)
    Journey time of the connection > minimum journey time factor + constant
    (unless the connection is optimal with respect to the number of transfers)
    Number of transfers of the connection > minimum number of transfers + constant
    (unless the connection is optimal with respect to the journey time)
    The factors and constants can be set by the user.

    7.10.4

    Impedance and Perceived journey time (PJT) of a connection


    The impedance is a linear combination of perceived journey time (see "Perceived journey
    time" on page 502), fare, T(early) and T(late). T(early) and T(late) thus express the temporal utility of a connection (see "Temporal utility of a connection" on page 504).

    7.10.4.1

    Perceived journey time


    PJT [min] =
    In-vehicle time FacIVT any (in)direct attribute of vehicle journey items
    + PuTAux time FacAXT (in)direct TSys attribute
    + Access time FacACT
    + Egress time FacEGT

    502

    PTVGROUP

    7.10.4.1 Perceived journey time


    + Transfer walk time FacWT
    + Origin wait time FacOWT
    + Transfer wait time FacTWT
    + Number of transfers FacNT
    + Number of operator changes FacOC
    + Extended impedance Factor
    Notes
    PuT-Aux time
    The time spent in a transport system of the PuT-Aux type enters the PJT as a separate
    value and can be weighted by any transport system attribute. It is furthermore required as
    a skim value.
    Bonus-malus modeling
    The in-vehicle time can be multiplied by an attribute of the vehicle journey items (and the
    PuT-Aux time by a TSys attribute respectively) in order to model the vol/cap ratio (for example the availability of seats) or other aspects of usability (for example the level of comfort).
    Number of transfers
    The PuT line TSys and the PuT-Aux TSys enter the calculation of the number of transfers
    on a par.
    Number of operator changes
    Operator changes cannot occur due to PuT-Aux path legs.
    Origin wait time
    With the following equation, the origin wait time, OWT, can be determined from the service frequency of all connections.
    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 the case of low service frequency.
    The origin wait time is the same for all connections of an OD pair. Including them in the PJT is
    therefore just like a constant supplement. The OWT output as a skim matrix, however, can be
    important for the network analysis.
    Transfer wait time
    The transfer wait time models smooth transfers in zero time or slightly more than zero time.
    The extended transfer wait time models that transfers are ideal not in zero time (or slightly
    more) but if they take a few minutes. A lot of timetable information retrieval systems also do not
    offer connections that contain "smooth" transfers.
    With the extended transfer wait time, the user can also "penalize" transfers in Visum that are
    too short. For this, the program uses a non-linear function which calculates a weighted wait
    time that depends on the user-defined ideal transfer wait time, which then enters the perceived
    journey time. Instead of the regular transfer wait time, the extended transfer wait time can enter
    the PJT calculation. But it can also be saved as a separate skim.

    PTVGROUP

    503

    7.10.4.2 Temporal utility of a connection


    The used weighting function f takes the following shape.
    As an argument, the actual transfer wait time t is set, which is the time that passes between the arrival of the passenger at the stop point and the departure of the vehicle journey.
    The weighted wait time f(t) is thus defined as
    (t - t0)n + c, if t<t1, and
    f(t) = t, if tt1.
    t1 and c result from the boundary conditions f(t1)=t1 and f'(t1)=1, that is from the differentiable composition of both parts of the function at position t1.
    Essential is: t0 is the transfer wait time considered ideal. For the extended transfer wait
    time, this variable may depend on the required walk time and thus needs to be parameterized as follows:
    Factor times walk time plus constant
    Due to the polynomial shape of f, the weighted wait time f(t) is the least precisely at the position t=t0.
    Around t0, f(t) increases symmetrically.
    With increasing t, function f(t) approaches the linear asymptote t.
    Example
    By default, n = 2 and t0 = 5 is set.
    Due to the boundary conditions f(t1)=t1 and f'(t1)=1, t1=5.5 and c=5.25 results from these
    parameters.
    If a transfer takes place in time t=0 the following weighting is calculated, i.e. a very high
    penalty term:
    f(0) = t02 + c = 25 + 5.25 = 30.25
    A transfer in time t=3 results in a significantly lower value:
    f(3) = (3 - t0)2 + c = 22 + 5.25 = 9.25
    A transfer in time t=5 achieves the optimum:
    f(5) = (5 - t0)2 + c = 02 + 5.25 = 5.25
    If t continues to rise, the weighting worsens again, for example, when t=10:
    f(10) = (10 - t0)2 + c = 25 + 5.25 = 30.25
    7.10.4.2

    Temporal utility of a connection


    With the timetable-based procedure, the temporal utility of a connection is modeled as follows.
    TaiEarly = amount of time that connection i departs earlier than desired for departure interval a (time series); = zero, if i departs within a or after a.

    TaiLate = amount of time that connection i departs later than desired for the departure
    interval a ( time series); = zero, if i departs within a or before a.

    504

    PTVGROUP

    7.10.4.3 Fare

    TaiEarly FacTearly + Tailate FacTlate = temporal distance between connection i and


    interval a. The first factor controls the sensitivity of passengers towards earlier departures,
    the second the sensitivity of passengers towards later departures.
    This temporal distance is included as a further summand in the definition of impedance, in
    order to impede lower utilities.
    Note: For connections with no temporal position, T is always zero.
    The table 190 shows an example for the calculation of Tearly and T late in the time interval
    [06:00 a.m. ; 07:00 a.m.].
    Departure

    Tearly

    05:30 a.m.

    30

    30

    06:00 a.m.

    06:40 a.m.

    07:00 a.m.

    10

    07:10 a.m.
    10
    Table 190: Calculation of the temporal distance
    7.10.4.3

    7.10.5

    Tlate

    Fare
    If a zone-based ticket type is used, PuT-Aux path legs are disregarded. Distance-based ticket
    types are evaluated analogously to the TSys of PuT lines, because fare points can also be
    assigned to PuT-Aux (see "Revenue calculation using the fare model" on page 663).

    Connection choice
    The connection choice distributes the demand 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 a connection (see "Impedance and Perceived journey time (PJT) of a connection" on page 502). For the distribution models, these impedances
    serve as an input for calculating the shares of the connections in the travel demand (see "Distribution models in the assignment" on page 329). The independence can also be included in
    the distribution rule, if required (see "Independence of connections" on page 506).

    7.10.5.1

    Distribution of trips over connections


    The impedance of a connection i used in the connection choice in a time interval a is calculated as follows.

    PTVGROUP

    505

    7.10.5.2 Independence of connections


    Optionally, each skim value which goes in the impedance can be individually Box-Cox transformed. This does not affect the actual choice model. Any utility function can thus still be applied to the total impedance even when using the Box-Cox transformation.
    The impedance calculation is not linked to the actual connection choice, that is, even when calculating the Box-Cox transformation, Logit does not necessarily have to be used. Any other utility function can be selected instead.
    The impedance calculation is as follows:
    For i = 1, ..., n are xi the different path attributes. Here, the first m of them without restrictions are
    to be Box-Cox-transformed (namely each into parameter i ). i stands for the respective coefficient. Then the following applies

    where

    By including this impedance in one of the distribution models Kirchhoff, Logit, Box-Cox or
    Lohse (see "Distribution models in the assignment" on page 329), 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 (see
    "Independence of connections" on page 506).
    As before, the proportion of a connection i of the total demand is calculated as follows:

    Here, g is the selected utility function (always antitonic). In the case of Logit thus g(x)=e-bx applies.
    Notes: As can be seen from the definition, when using the Box-Cox transformation for xi
    generally xi 0 needs to apply. In case of i = 0, even xi > 0 needs to be true. If this rule is
    violated during the run time, the assignment is terminated with an error message.
    Due to a Box-Cox transformation or caused by negative coefficients, Ri itself can be negative. In that case, only the Logit utility function can be used, otherwise the assignment is
    terminated with an error message.
    7.10.5.2

    506

    Independence of connections
    All distribution models presented (see "Distribution models in the assignment" on page 329)
    cannot, in their basic form, take into account interactions between different connections in a

    PTVGROUP

    7.10.5.2 Independence of connections


    timetable-based assignment. However, ignoring this aspect can be a drawback.
    In order to model interactions, one defines functions w i , which describe the impact of other
    connections on a connection i. The value range of 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, meaning it is always wi(j) = 1.
    The following values are used to calculate wi(j).
    The temporal proximity of the connections with regard to departure and arrival

    The advantage of i over j in terms of the perceived journey time


    yi(j) := PJTj - PJTi
    The advantage of i over j in terms of the fare
    zi(j) := Farej - Farei
    Thus, wi is defined as follows:

    where

    and

    s > 0 are internal parameters for controlling the influence of the three values. c is a constant
    that controls the absolute effect of the second value. It is user-defined within [0.1].
    The first value describes the temporal proximity of i and j. If the times are the same, then xi(j) =
    0, so that this value is equals to 1. If the time difference is xi(j) sx, the value becomes zero and
    wi(j) = 0 also applies. Thus, sx is the maximum temporal distance in which j can effect i.
    The second value 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.
    With regard to the fare, the same applies to sz. The default setting leads to the following relation of s y- = 2s y+ and s z- = 2s z+ . As a result of this asymmetry, in the case of two connections
    with temporal proximity, the better is favored, because its influence on the worse alternative is
    greater than vice versa. In principle, users should always specify Independency coefficients for
    high or low quality in the form of IndCoeffQualityHigh (ECQH) < IndCoeffQualityLow (ECQL).
    When violating this rule, a warning appears at the start of the assignment (or an error message
    in the window).
    Overall, the following applies:
    sx = min (2 mean wait time of a random passenger between the first and the last departure, maximum time
    slot)

    PTVGROUP

    507

    7.10.5.2 Independence of connections


    sy+ = ECQH mean PJT in the total assignment period
    sy- = ECQG mean PJT in the total assignment period
    sz+ = ECQH mean fare in the total assignment period
    sz- = ECQL mean fare in the total assignment period
    Note: Only the temporal positions, the PJT values and the fares are compared; service
    trip item data is not evaluated.
    If no fares are available (i.e. FPi = 0 for all i), then sz = 1 is set.
    The attribute independence of a connection is now defined as follows:

    o
    Here, n is the total number of connections.
    Distribution models with independence
    If independence is used for connection choice, then this attribute must be integrated in the distribution model. In the version described above, for each time interval a the utility U i a of a
    connection i was calculated. From this, its percentage in terms of the demand was determined
    per time interval. If independence is applied, Uia INDi replaces Uia, i.e. the following applies:

    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). As a result, the total of its weights in the distribution formula is equal
    to the weight of a single, non-multiplied connection of the same kind.
    Comparison of the choice models with independence
    In table 192 to table 196 the different choice models are compared with each other, with and
    without independence. The procedure parameters are chosen as in table 191.

    508

    Kirchhoff

    =4

    Logit

    = 0.25

    Box-Cox

    = 1 and = 0.5

    PTVGROUP

    7.10.5.2 Independence of connections


    Lohse

    =4

    PJT formula

    PJT = JT + 2 TWT + 2 NTR

    IMP formula

    IMP = PJT + 4 fare

    IND parameter
    c=1
    Table 191: Procedure parameters for the comparison of the distribution models
    Connection data that differs from the respective previous example is highlighted bold in table
    192 to table 196. All assignment shares are given as percentages.
    Connection data

    Distribution without IND

    Distribution with IND

    No. Dep Arr

    PJ- Fare
    T

    Kirchhoff

    Logit BoxCox

    Lohs- Kirche
    hoff

    Logit BoxCox

    Lohse

    10

    30

    20

    3.00

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    30

    50

    20

    3.00

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    3
    50 70
    20 3.00 33.3
    33.3
    Table 192: Example 1 Initial situation

    33.3

    33.3

    33.3

    33.3

    33.3

    33.3

    Connection data

    Distribution without IND

    No. Dep Arr

    PJ- Fare
    T

    Kirchhoff

    Logit BoxCox

    Lohs- Kirche
    hoff

    Distribution with IND


    Logit BoxCox

    Lohse

    10

    30

    20

    3.00

    25

    25

    25

    25

    33.3

    33.3

    33.3

    33.3

    30

    50

    20

    3.00

    25

    25

    25

    25

    16.7

    16.7

    16.7

    16.7

    30

    50

    20

    3.00

    25

    25

    25

    25

    16.7

    16.7

    16.7

    16.7

    33.3

    33.3

    33.3

    4
    50 70
    20 3.00 25
    25
    25
    25
    33.3
    Table 193: Example 2 Isochronous, identical pair of connections

    Connection data

    Distribution without IND

    No. Dep Arr

    PJ- Fare
    T

    Kirchhoff

    Logit BoxCox

    Lohs- Kirche
    hoff

    Logit BoxCox

    Lohse

    10

    30

    20

    3.00

    25

    25

    25

    25

    32.7

    32.7

    32.7

    32.7

    30

    50

    20

    3.00

    25

    25

    25

    25

    17.3

    17.3

    17.3

    17.3

    32

    52

    20

    3.00

    25

    25

    25

    25

    17.3

    17.3

    17.3

    17.3

    4
    50 70
    20 3.00 25
    25
    25
    25
    32.7
    32.7 32.7
    Table 194: Example 3 Identical pair of connections with high temporal proximity

    32.7

    PTVGROUP

    Distribution with IND

    509

    7.10.5.3 Example for the connection choice


    Connection data

    Distribution without IND

    Distribution with IND

    No. Dep Arr

    PJ- Fare
    T

    Kirchhoff

    Logit BoxCox

    Lohs- Kirche
    hoff

    Logit BoxCox

    Lohse

    10

    30

    20

    3.00

    25.9

    26.7

    26.2

    25.1

    31.9

    32.6

    32.2

    31.2

    30

    50

    20

    3.00

    25.9

    26.7

    26.2

    25.1

    20.2

    20.7

    20.4

    19.8

    32

    47

    20

    3.30

    22.3

    19.8

    21.3

    24.6

    16.0

    14.1

    15.2

    17.8

    4
    50 70
    20 3.00 25.9
    26.7 26.2 25.1 31.9
    32.6 32.2 31.2
    Table 195: Example 4 Similar pair of connections with high temporal proximity (connection 3 now includes transfer)

    Connection data

    Distribution without IND

    No. Dep Arr

    PJ- Fare
    T

    Kirchhoff

    Logit BoxCox

    Lohs- Kirche
    hoff

    Distribution with IND


    Logit BoxCox

    Lohse

    10

    30

    20

    3.00

    23.5

    21.9

    22.8

    24.6

    26.5

    24.9

    25.8

    27.7

    30

    50

    20

    3.00

    23.5

    21.9

    22.8

    24.6

    20.1

    18.9

    19.6

    21.0

    32

    44

    17

    3.30

    29.6

    34.3

    31.5

    26.1

    26.9

    31.4

    28.7

    23.6

    4
    50 70
    20 3.00 23.5
    21.9 22.8 24.6 26.5
    24.9 25.8 27.7
    Table 196: Example 5 - Differing pair of connections with moderate temporal proximity
    The fact that, without IND being applied the connections 1, 2 and 4 have the same number of
    passengers in all cases shows, that the interactions between different alternatives ought to
    be taken into account to a higher degree in this case. It becomes apparent that then better
    results are achieved with all distribution models.
    7.10.5.3

    Example for the connection choice


    The effect of the connection choice for the timetable-based method is shown with the results of
    the connection search regarding a 10-minute transfer penalty. The branch & bound search is
    used. This search returns the five connections shown in table 197 . A monocriterion shortest
    path search however would only find the connections 1, 3 and 5, as they have the lowest impedance of all the connections of their departure times. The impedance (= perceived journey
    time) results from the weighted sum of the following skims: journey time (JRT ), transfer wait
    time (TWT) and number of transfers (NTR).
    Conn. i Dep.

    JRT

    06:10
    a.m.

    28 min

    3 min

    28 + 3 2 + 1 2 = 36

    06:10
    a.m.

    45 min

    0 min

    45 + 0 2 + 0 2 = 45

    TWT

    NTR

    PJT = JRT + TWT Fac


    + NTR
    i
    i
    i
    TWT
    i
    Fac
    NTR

    510

    PTVGROUP

    7.10.5.3 Example for the connection choice


    Conn. i Dep.

    JRT

    06:55
    a.m.

    45 min

    0 min

    45 + 0 2 + 0 2 = 45

    07:25
    a.m.

    28 min

    8 min

    28 + 3 2 + 1 2 = 36

    07:25
    a.m.

    45 min

    0 min

    45 + 0 2 + 0 2 = 45

    TWT

    NTR

    PJT = JRT + TWT Fac


    + NTR
    i
    i
    i
    TWT
    i
    Fac
    NTR

    Fac

    TWT

    = 2, Fac

    NTR

    =2

    Table 197: Result of connection search (transfer penalty 10 min, parameter file
    TIMETAB1.PAR)
    The table 198 shows the impedances of the connections. As T depends on the desired departure time of the passengers, different impedance values result for the various time slices of travel demand. 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 in such a way, that the following applies:
    Ria = PJTi 1.0 + Tiaearly 1.0 + Tialate 1.0
    Conn. i Dep.

    Ti1
    05:30 06:30 a.m.

    Ri1
    Ti2
    06:30 - 07:30 a.m. 05:30 - 06:30
    a.m.

    Ri2
    06:30 - 07:30
    a.m.

    06:10
    a.m.

    0 min

    20 min

    36 0 = 36

    36 20 = 56

    06:10
    a.m.

    0 min

    20 min

    45 0 = 45

    45 20 = 65

    06:55
    a.m.

    25 min

    0 min

    45 25 = 70

    45 0 = 45

    07:25
    a.m.

    55 min

    0 min

    46 55 = 101

    46 0 = 46

    07:25
    55 min
    0 min
    45 55 = 100
    45 0 = 45
    a.m.
    Table 198: Temporal distances T and impedances R of the connections for the two analyzed intervals of travel demand
    Then, a distribution rule (here Kirchhoff with = 3) is used to calculate the shares Pia which are
    allocated to the individual connections. The independence is ignored in this formula. As
    shown in table 199 , all five connections are assigned non-zero percentages of the travel
    demand per time interval.

    PTVGROUP

    511

    7.10.6 Handling of public transport systems of the PuT-Aux type


    Conn. i Dep.

    Pi1
    Pi2
    05:30 - 06:30 06:30 a.m.
    07:30 a.m.

    Vehicle journeys Mi1


    05:30 06:30 a.m.

    Vehicle journeys Mi2


    Vehicle jour06:30 neys
    07:30 a.m.
    05:30 - 07:30
    a.m.

    06:10 57%
    a.m.

    13%

    30 0.57 =
    17

    60 0.13 = 8

    25

    06:10 30%
    a.m.

    8%

    30 0.30 = 9

    60 0.08 = 5

    14

    06:55 7%
    a.m.

    27%

    30 0.07 = 2

    60 0.27 =
    16

    18

    07:25 3%
    a.m.

    25%

    30 0.03 = 1

    60 0.25 =
    15

    16

    07:25 3%
    a.m.

    27%

    30 0.03 = 1

    60 0.27 =
    16

    17

    S
    100%
    100%
    30
    60
    Table 199: Distribution of trips to the connections (Kirchhoff, = 3)

    90

    This results in the volumes shown in illustration 162.

    Illustration 162: Network volume for timetable-based assignment (parameter file timetab1.par)

    7.10.6

    Handling of public transport systems of the PuT-Aux type


    The following applies for transport systems of the type PuT-Aux:
    They are considered in the timetable-based assignment and also via the menu
    Graphics> Shortest path search.
    They are convenient for modeling inferior transport supply without timetables. These are
    for example
    Park & Ride
    Local public transport with dense headway within a network that is otherwise timetable-based
    Taxis

    512

    PTVGROUP

    7.10.7 Opening of the timetable-based assignment: Export/Import of connections


    They are only relevant on links and turns. By defining permissions of PuT-Aux TSys to
    these objects, the subnetwork which is enabled per PuT-Aux TSys is defined. This information is not relevant for connectors, nodes or stop points.
    Alike PuT-Walk TSys, PuT-Aux TSys are permitted for PuT modes. In case of assignments of
    demand segments of such modes, passengers can use path legs with the PuT- Aux, too,
    namely those between two nodes that are connected by links for which the PuT-Aux transport
    system is permitted. These nodes need to be accessed by walk links however, or be directly
    connected to a zone or stop area.
    During the assignment, a change to a PuT-Aux path leg counts as a transfer.
    The extended modularized procedure can be used for example, to export and import fares
    (see "Opening of the timetable-based assignment: Export/Import of connections" on page
    513).
    Pre-calculation of path legs
    The set of PuT-Aux TSys permitted in an assignment directly affects the path legs to be calculated because every start node of PuTAux paths represents a potential target of PuT walk
    links. This is taken into account when pre-calculating the walk links and PuT-Aux paths.
    Adjustment of the connection search
    Analogous to walk links, a path leg is created for each PuT Aux path. In any case, the trivial
    PuT-Aux transfers at nodes appear as individual path legs in any case. Path legs are sorted
    separately by type: PuT-Line, PuT-Walk, and PuT-Aux.
    Analogous to the reference to the index of the first walk link path leg for an origin, a reference
    to the index of the first PuT-Aux path leg is logged.
    For path legs with PuT-Aux TSys, too, journey time, number of transfers and the impedance by
    transport system are clearly defined. In particular the link attributes Imp/km , Imp/FarePoint
    and Imp/AddVal are available for PuT-Aux TSys.

    7.10.7

    Opening of the timetable-based assignment: Export/Import of connections


    For some projects particularly in connection with demand modeling (see "Demand model" on
    page 129) a (time-consuming) timetable-based assignment is carried out several times within
    the same procedure sequence.
    The PuT skims are determined first, for example, then the mode choice is calculated and
    finally the actual PuT assignment is performed. Since during the PuT skim calculation all
    connections are already determined, it is reasonable to use them in the PuT assignment. Thus
    the assignment includes only the step connection choice (see "Connection choice" on page
    505).
    The timetable-based assignment has such a modular structure that search and choice can be
    performed independently of each other and the found connections can be stored for later use.
    This provides the following advantages:
    Replacing a connection search by a pre-calculated path file or by paths taken from an
    already existing assignment saves lots of time. In many networks, the search is the most
    time-consuming step of the computation. Possibly the peak memory requirements can be

    PTVGROUP

    513

    7.10.7 Opening of the timetable-based assignment: Export/Import of connections


    reduced during the assignment.
    Paths from external sources can be taken as inputs to the Visum assignment. This allows
    for a user-defined heuristic during search and choice without resigning other advantages
    of the Visum assignment.
    Variants of assignment results can be stored via connection export and later be read in for
    post-assignment analyses, if required. It is no longer necessary to use several version
    files.

    Illustration 163: Flow chart of a timetable-based assignment


    The illustration 163 indicates when paths can be read in from file or output to file in the timetable-based assignment. The following options are provided:
    (1) External choice / Connection import
    Connections with volumes are imported from file and stored like an assignment result, therefore as paths and network volumes (see "Use case (1): External choice / Connection
    import" on page 515).
    (2) Connection export
    In order to provide the external choice with data, connections can also be exported. You
    can do so with or without volumes and optionally choose fare points, fares or user-defined
    attributes (see "Use case (2): Connection export" on page 515).
    (3) Using existing connections for the search
    Instead of the connection search in Visum, the procedure can also use existing connections
    as a basis. These connections can be the result of a previous assignment or be stored in a
    connection file. This feature is of major interest if the search parameters have not been
    modified, but a choice is to be carried out with different settings (see "Use case (3): Using
    existing connections for the search" on page 516).
    It is possible, but not necessary, to deactivate the option Calculate assignment for the connection export. As for a pure skim calculation, neither paths not volumes are stored in this case.
    Existing assignments of the selected demand segments are retained.

    514

    PTVGROUP

    7.10.7.1 Use case (1): External choice / Connection import


    7.10.7.1

    Use case (1): External choice / Connection import


    The objective of the external choice is to assign volumes to a given number of connections
    according to variable user-defined rules for later re-import of the connections in Visum so that
    a usual assignment result will be available (see User Manual: Chpt. 25.3 , page 2560).
    In the chart in illustration 163 this is scheduled above the network loading. The paths contained in the connection file are converted into the internal data structure and therefore no longer differ from paths calculated within Visum. Thus, connection import has the same effect as
    an assignment.
    This means the following:
    By default, the program deletes assignment results for demand segments to which connection import is applied.
    From the imported connections, paths are generated in Visum according to the current setting of the option Save paths (as connections / as routes / do not save) (see User Manual:
    Chpt. 19.1.1.2 , page 1996).
    The procedure setting Save paths as connections includes an option that allows you to
    sum up the volumes of existing connections.
    At the same time the path volumes read in are transferred into network volumes.
    If the volumes of a demand segment that has been selected for the import are to be saved
    with another demand segment according to the current general procedure settings, then
    this parameter will be reset to the default (Do not save with a different demand segment).

    7.10.7.2

    Use case (2): Connection export


    Using the connection export you create connection files to save computation time during future
    assignments. You can also import this data in external tools in which you have set up your specific heuristics for the connection choice.
    The connection export can be performed with or without volumes. Volumes are required for
    the connection import procedure. When exporting connections without volumes you can select
    one of the following options for the export: Connections are to be searched on either all relations or only on those relations with demand > zero.
    The option Regard all relations should be used if the demand by relation is not known when
    the export is performed. Typically this is the case during the PuT skim calculation at the beginning of the Standard-4-step model calculation. Increasing computation time and growing size
    of the connection file are the disadvantages of this option.
    Independently of this option, exported connection files can also store the following data:
    Fare points of the path legs (cannot be imported) and/or
    Fares per path or path leg for a single or all demand segments (can be imported)
    User-defined attribute for PuT paths
    For fare calculations in the context of the external choice, the option with fare points has to be
    enabled since the fare is mostly based on the number of fare points per path leg of the connection.
    For connection export without volumes the following assignment parameters are relevant:

    PTVGROUP

    515

    7.10.7.3 Use case (3): Using existing connections for the search
    Origin zone interval
    Assignment time interval with extension
    All search parameters
    All pre-selection parameters
    All other parameters are only effective if an assignment is actually performed, a skim matrix stored or a connection export carried out.
    7.10.7.3

    Use case (3): Using existing connections for the search


    At the beginning of the assignment you can re-use existing connections instead of a complete
    connection search calculation. This will significantly speed-up the assignment and allows for
    subsequent usage of external tools for the connection search.
    The import can use data from various sources:
    from a connection file
    from an existing assignment result in the network
    Once the import is finished the assignment will continue in the same way as after the internal
    connection search. The source especially does not have an impact on the connection choice
    (see "Connection choice" on page 505).
    Imported connections have preset times of arrival and departure which depend on the assignment time interval that was set for their calculation. For the import, you can modify the assignment time interval. In this case the temporal distance of the connections from the new
    assignment time interval is T in the impedance as usual. In general this ensures, that there is
    almost no demand for connections which are far outside. And they do not have a significant
    impact on the skim calculation. Please note that the skim service of frequency, however,
    always takes into consideration the absolute number of connections not taking into consideration their temporal position. For this skim, identical assignment time intervals are recommended for the export and import of connections.
    Import from an existing assignment result
    The usage of paths which were calculated in a previous assignment is similar to the PrT assignment option Use current assignment result as initial solution (see User Manual: Chpt.
    18.6.2.2 , page 1935). However, unlike PrT, the path search may be dropped completely for
    public transport. You need to enter a demand segment for which an assignment has already
    been calculated.
    The existing assignment needs to satisfy the following recommendations, otherwise the paths
    resulting from the assignment cannot be re-used:
    A timetable-based assignment is required.
    For the calculation, the option 'Save paths as connections' needs to be selected. Please
    note that this setting differs from the default (see User Manual: Chpt. 19.1.1.2 , page
    1996).
    The demand segment has to belong to the same mode as the demand segments which
    are currently to be assigned.
    Import from a connection file
    Alternatively, you can read connections from a file.

    516

    PTVGROUP

    7.10.7.4 File format for connection import and export


    For this purpose, use the same connection files as for the connection import procedure (see
    "Use case (1): External choice / Connection import" on page 515). In contrast to this procedure, the import from a connection file ignores the stored volumes, only the paths are read
    from file.
    Connection files can be applied to any demand segment. Make sure that the paths from the
    connection file and the mode of the currently to be assigned demand segments match.
    The import automatically identifies the level of the stored fare information (see "File format for
    connection import and export" on page 517). Please note that the current option setting Save
    imported fare data (see User Manual: Chpt. 19.1.1.2 , page 1996) determines whether and
    how these fares are imported.
    7.10.7.4

    File format for connection import and export


    Import and export of paths use a uniform data format which is binary due to the huge amount
    of data.
    Since the assignment is carried out per OD pair, the connection files have to be structured in
    the same way, that is, all connections of the same relation have to be read or written in one go,
    ordered according to zone numbers.
    As soon as the size of the connection file exceeds the given size limit, another connection file
    is created. The size limit ensures that even a connection export including a huge number of
    paths (> 4 GB) can be read in later.
    A connection file contains the following data in the following order:
    1. A version number is written, which later allows the format to be modified
    2. Number of path files so that Visum identifies when re-importing whether or which additional
    files need to be searched for
    3. Indication on whether the file contains the number of fare points at the path leg
    4. Level of fare data contained in the file (0 = no fares)
    5. Indication on whether the file contains fares for all demand segments
    6. Indication on whether the file contains connector nodes
    7. Indication on whether the file contains volumes Number and codes of the assigned
    demand segments for future allocation of volumes and fares when reading them in again. If
    you import connections without volumes and fares per demand segment, no demand segments are saved and their number is set to 0.
    8. The keys of all public transport systems and time profiles of the network in assorted order.
    Thus, later (generally numerous) references to public transport systems of time profiles no
    longer require the output of the complete key string, but the index can be used instead.
    Important is the congruence of public transport systems and time profiles in the network and
    the connection file. The term PuT transport systems comprises all PuT-Line TSys, PuT-Walk
    TSys and PuT-Aux TSys.
    9. Definition of user-defined attributes on PuT paths
    10. All connections are stored separately per OD pair.

    PTVGROUP

    517

    7.10.7.4 File format for connection import and export


    Each connection consists of several PuT path legs.
    Pure walk link connections only have zero PuT path legs.
    A path leg is either of type PuT-Line or PuT-Aux. In the first case it connects time profile
    items, in the second case nodes.
    Example: Connection file in binary data format
    BinaryVersionNo (4 byte-integer)
    NumberOfFiles (4 byte-integer)
    ContainsFarePoints (1 byte-integer)
    LevelOfFareInformation (1 byte-integer)//value in {0,1,2}
    FaresForEachDemandSegment (1 byte-integer)
    ContainsConnectorNodes (1 byte-integer)
    ContainesVolumes (1 byte-integer)
    NumDemandSegments (4 byte-integer)
    for each contained DemandSegment in key order:
    {
    DemandSegment.Code (string)
    }
    NumPuTTSys (4 byte-integer)
    for each contained PuTTSys in key order:
    {
    TSys.Code (string)
    }
    NumTimeProfiles (4 byte-integer)
    for each contained TimeProfile in key order:
    {
    Line.Name (string)
    LineRoute.Name (string)
    Direction.Code (string)
    TimeProfile.Name (string)
    }
    NumUserDefinedAttributes (4 byte-integer)
    for each contained UserDefinedAttribute:
    {
    ID (string)
    ShortName (string)
    LongName (string)
    Comment (string)
    ValueType (4 byte-integer)
    HasDefaultValue (1 byte-integer)
    DefaultValue (8 byte-real)
    MinimumValue (8 byte-real)
    MaximumValue (8 byte-real)
    NumDecPlaces (4 byte-integer)
    MaxStringLength (4 byte-integer)
    DefaultStringValue (string)
    }
    for each contained OD relation in key order:
    {
    SourceZoneNo (4 byte-integer)
    DestZoneNo (4 byte-integer)
    for each contained Connection:
    {

    518

    PTVGROUP

    7.10.7.4 File format for connection import and export


    ConnectionDepartureTime (4 byte-integer)
    NumLegs (1 byte-integer)
    for each contained ConnectionLeg in logical order:
    {
    DepartureTime (4 byte-integer)
    LegIsPuTLine (1 byte-integer)
    if LegIsPuTLine
    {
    TimeProfileIndex (see above) (4 byte-integer)
    FromTimeProfileItem.Index (2 byte-integer)
    ToTimeProfileItem.Index (2 byte-integer)
    }
    else // 2nd case, leg is of type PuTAux
    {
    TSysIndex (see above) (4 byte-integer)
    FromNodeNo (4 byte-integer)
    ToNodeNo (4 byte-integer)
    }
    if ContainsFarePoints (4 byte-integer)
    {
    NumFarePoints (4 byte-integer)
    }
    if LevelOfFareInformation = 2
    {
    if(FaresForEachDemandSegment){
    for each contained DemandSegment in key order:
    {
    LegFare (8 byte-double)
    }
    }
    else {
    LegFare (8 byte-real)
    }
    }
    }
    for each contained DemandSegment in key order:
    {
    Volume (8 byte-double)
    }
    if LevelOfFareInformation = 1
    {
    if(FaresForEachDemandSegment){
    for each contained DemandSegment in key order:
    {
    ConnectionFare (8 byte-double)
    }
    }
    else {
    ConnectionFare (8 byte-real)
    }
    if ContainsConnectorNodes
    {
    FromNodeNo (4 byte-integer)
    ToNodeNo (4 byte-integer)

    PTVGROUP

    519

    7.10.7.4 File format for connection import and export


    }
    for each contained UserDefinedAttribute:
    {
    HasValue (1 byte-integer)
    if HasValue
    {
    Value (1 byte-integer/4 byte-integer/8 byte-double/string)
    }
    }
    }
    -1 (4 byte-integer)
    }
    -1

    With regard to semantics the following has to be taken into account.


    If transfer walk links are used between two PuT path legs, these are not contained in the
    file. They result from the beginning and end of the path (zone or stop area) and the
    TSysSet of the assignment.
    In contrast to the internal connection search it will not be checked whether the PuT vehicle
    journey sections used in the connections read from file are active.
    With regard to the exact format the following has to be considered:
    The Intel order ("Little Endian") has to be kept.
    There is no alignment, which means 4+1+2 bytes are actually exported as 7 bytes.
    Strings are written as follows:
    Length as 2-byte integer
    Signs as sequence of characters (each 1 byte)
    For user-defined attributes the following applies:
    The attribute values of a connection are saved in the same sequence as the attributes are
    defined in the header.
    The values permitted for ValueType correspond to those listed in the COM documentation
    (cf. 2.1 INetObjCollection: AddUserDefinedAttribute). Formula attributes must not be defined in the connection file. The corresponding data types are listed in the table below.

    520

    Identifier

    Numeric value

    Data type

    ValueType_Int

    4 byte-integer

    ValueType_Real

    8 byte-double

    ValueType_String

    string

    ValueType_Duration

    4 byte-integer

    ValueType_TimePoint

    4 byte-integer

    ValueType_Filename

    string

    ValueType_Bool

    1 byte-integer

    ValueType_LongLength

    12

    8 byte-double

    ValueType_ShortLength

    13

    8 byte-double

    PTVGROUP

    7.10.7.5 Consistency check during connection import

    7.10.7.5

    Identifier

    Numeric value

    Data type

    ValueType_StringLong

    62

    string

    ValueType_LongDuration

    165

    4 byte-integer

    Consistency check during connection import


    If a data conflict is detected, the procedure will be aborted. Conflicts can occur in the following
    cases:
    Unknown keys in the network
    DSegCode
    Combined time profile ID
    Zone number
    Time profile item index
    Different sets of transport systems or time profiles in network and connection file
    Improper time profiles (TSys not in TSysSet of the assigned mode)
    Invalid departure times (no trip on time profile at indicated time(s) or only outside
    the assignment time interval plus extension)
    Invalid transitions (transfer walk time exceeds the difference between departure
    and last arrival)
    Negative volumes

    7.10.8

    Capacity restriction
    By default, the timetable-based assignment determines a connection's attractiveness without
    taking the demand into account. Accordingly, the demand is distributed onto possible connections without consideration of the vol/cap ratios of these connections. Regarding also the vol/cap ratio can return those connections as attractive alternatives which in the standard case
    seemed to be not attractive. Thus, the enhancement with this criterion might change the set of
    possible connections.
    Basically, neglecting the capacities is a simplification, which unsatisfactorily reflects reality in
    highly loaded public transport systems. Capacity restrictions in practice can take effect in different ways:
    Absolute vehicle capacity: The vehicle can hold only as many passengers as preset by its
    capacity.
    Discomfort in the vehicle: Passengers feel rather uncomfortable when travelling in a heavily loaded vehicle. This effect will increases if all seats are occupied.
    Discomfort outside of the vehicle: Passengers feel rather uncomfortable when transferring
    at highly frequented stops. Besides unpleasant effects due to overcrowding also delays
    may occur.
    The timetable-based procedure's capacity restriction aims to model possible discomfort for passengers in the vehicle. This approach approximately includes the fact that certain quantities of
    the passengers have to use different connections if the vehicle capacity is saturated. However,
    exceeding the vehicle capacity is not prevented as such. Capacity-restricting effects at stops
    are not considered.

    PTVGROUP

    521

    7.10.8.1 How the procedure works


    7.10.8.1

    How the procedure works


    Using the capacity restriction, the timetable-based assignment works as follows:
    1. Connection search and preselection are calculated as usual.
    2. If the option In the loaded network, search a second time has been checked, also the
    connection choice is calculated and then both search and pre-selection will be executed a
    second time. This second search will take the calculated volumes into account which result
    from the choice: These volumes will be added to the search impedance. The purpose of the
    second search is to find alternative connections, which could be dominated by other
    connections in the first search. If this option is not checked, step 4 will follow (see User
    Manual: Chpt. 19.2.4.7 , page 2042).
    3. If the option Merge the results of 1st search and 2nd search is checked, both sets of
    connections will be summarized. If this option is not checked, the following steps will use
    only the connections that were returned by the second search (see User Manual: Chpt.
    19.2.4.7 , page 2042).
    4. Based on this set of connections, all impedances which do neither depend on the vol/cap
    ratio nor on the time interval will be calculated, since this set of connections will not change
    in the subsequent loop.
    5. This step is the start of the actual loop: First, vol/cap ratio-depending impedances are calculated (see User Manual: Chpt. 19.2.4.8 , page 2044). The following three options are
    available (see "Calculation of Vol/Cap ratio-dependent impedances" on page 523).
    6. Optionally, the calculated impedances are smoothed (see User Manual: Chpt. 19.2.4.7 ,
    page 2042). Here, you can choose from two methods (see "Smoothing of impedances" on
    page 524).
    7. Steps 7 and 8 are to be applied alternatively.
    The volumes of connections are now determined with the distribution model. Since this computation is performed by time interval, the time interval-depending impedances are included. The latter are then added to the other impedance components.
    If the option Shift volumes among adjacent connections has been checked, the new volumes result from volume shifting from overloaded connections to alternatives (see User
    Manual: Chpt. 19.2.4.8 , page 2044). This is done without differentiation by time interval
    (see "Distribution of volumes onto alternatives" on page 526).
    8. In order to prevent oscillations between heavily loaded connections, optionally the changes
    to the volumes are smoothed (see "Smoothing of the vol/cap ratios" on page 525). This step
    is performed as an alternative to the impedance smoothing, cf. step 6.
    9. Various measures are calculated and returned which describe the distance from the balanced state.
    10. The termination conditions are verified. The procedure will be canceled, if one of the criteria is satisfied, otherwise the calculation will continue with step 5.
    Supplementary remarks about the modified procedure:
    During the choice, vol/cap ratio-depending impedances are added to the other impedance components, i.e. they also go into the skim Impedance.

    522

    PTVGROUP

    7.10.8.2 Calculation of Vol/Cap ratio-dependent impedances


    Also connections can be exported in combination with the capacity restriction. If connections are exported without volumes, the export will start after the second search is finished. If connections are exported with volumes, the export will start after the final choice.
    Skim matrices and other output data will be calculated after the final choice.
    Taking the capacity restrictions into account causes further restrictions with regard to three
    points:
    The optional second search is only possible with the Branch & Bound method.
    If volumes are shifted between connections, the calculation of relevant skims will not take
    time interval-specific volumes into account. This notably means that neither the skim Adaptation time nor the skim Extended adaptation time can be calculated and output if this
    option has been selected. Since the volumes are not directly derived from the choice
    model if volumes are shifted between connections, even the skim Utility cannot be calculated. For the skim Impedance, the DeltaT portion (which is the difference between desired departure time interval and actual departure time) cannot be calculated.
    Information on the calendar day level is neglected, since just a single vol/cap ratio is determined per vehicle journey item. In reality, however, vehicle journeys could actually run on
    several valid days, and their capacities and volumes might differ. Thus the applied vol/cap
    ratio definition represents a simplification of the information provided with the Visum data
    model, if a calendar is used.
    7.10.8.2

    Calculation of Vol/Cap ratio-dependent impedances


    With each of the three options, the vol/cap ratio Av of vehicle journey item v is calculated as follows:

    The capacity v corresponds to the value of the attribute, which has been selected by the user
    for the capacity of a vehicle journey item. The pre-set default amounts across all vehicle journey sections, which service the vehicle journey item without regard to the calendar day. Thus
    the volume of a vehicle journey item sums up from the volumes of all connections using this
    item:

    Path legs covered with PuT-Aux are not regarded for the vol/cap ratio-dependent impedance
    calculation.
    Calculation from the assumed standing minutes (German Rail (DB))
    The assumed standing minutes (E) are the mean value of the time, a passenger expects to
    find no seat during his ride if passengers have random access to the seats on each stop-stop
    relation. The latter is due to the fact, that it cannot be distinguished between passengers who
    are already on board before the overloaded route section is reached and passengers who
    board in this route section. This interpretation of the standing minutes applies to the capacity of

    PTVGROUP

    523

    7.10.8.3 Smoothing of impedances


    a vehicle journey item definition with regard to the number of seats. More generally, this is a
    discomfort which increases with the vol/cap ratio.
    For a vehicle journey item v, the standing probability is approximated by a potentially asymptotical function:

    The user has to set the parameters a and b, and Av is the vol/cap ratio.
    The expected standing minutes of a connection V correspond to a volume-dependent impedance and result from adding the product of standing probability and run time across all
    vehicle journey items of the connection:
    :
    Using a penalty function for computation (Swiss Rail (SBB))
    The impedance of a vehicle journey item v is defined as follows:

    The parameters a, b, c, l1 and l2 have to be entered by the user, Av is the vol/cap ratio of vehicle
    journey item v. Thereof, the parameters r, , and result due to the function which can be constantly differentiated here l1 and here l2.
    Thus, the impedance of a connection V is calculated as follows:

    Using a linear penalty function for computation (Linear)


    The impedance of a vehicle journey item v is defined as follows:

    a and b are user-defined parameters, Av is the vol/cap ratio of a vehicle journey item v.
    Thus, the impedance of a connection V is calculated as follows:

    7.10.8.3

    524

    Smoothing of impedances
    For smoothing of vol/cap ratio-dependent impedances, one of these methods can be chosen:
    Exponential smoothing or Method of Successive Averages (MSA). After smoothing of impedances, subsequent steps will use the smoothed impedances instead of the real impedances.

    PTVGROUP

    7.10.8.4 Smoothing of the vol/cap ratios


    Exponential smoothing
    According to this formula, the smoothed vol/cap ratio-dependent impedance of connection V in
    iteration i is derived from both the calculated impedance and the smoothed impedance of the
    previous iteration:

    Parameter a has to be defined by the user, the value range is 0..1.


    Method of Successive Averages (MSA)
    According to this formula, the smoothed vol/cap ratio-dependent impedance of connection V in
    iteration i is derived from the impedances of the previous iterations:

    This procedure forces convergence of impedances and of volumes, accordingly.


    7.10.8.4

    Smoothing of the vol/cap ratios


    To prevent heavy oscillations of volumes between some connections, the vol/cap ratios of
    vehicle journey items can be smoothed. Actually, the vol/cap ratio of a vehicle journey item in
    iteration i is derived as follows:

    The smoothed vol/cap ratio of a vehicle journey item in iteration i is derived from the calculated
    and the smoothed vol/cap ratios of the two previous iterations:

    This formula describes the interpolation in the event of different signs for
    and
    .

    Illustration 164: Smoothing of the vol/cap ratio in iteration i


    In the image, the following applies:

    PTVGROUP

    and

    etc.

    525

    7.10.8.5 Distribution of volumes onto alternatives


    If both terms have the same sign, an extrapolation will be performed. Using the same formula
    slows down the convergence for the extrapolation, thus the following formula is used in this
    case (smoothing with constant factor 0.5):

    The smoothed vol/cap ratios are then regarded by the impedance calculation within this iteration and by the final impedance calculation.
    For a network with smoothed vol/cap ratios of vehicle journey items it cannot be assumed, that
    a path set can be generated which could generate the corresponding volumes.
    7.10.8.5

    Distribution of volumes onto alternatives


    In order to prevent volumes from being distributed too often to connections which are unattractive in terms of time, instead of the choice model a procedure can optionally be applied,
    which shifts volumes between connections.
    In this case, for each pair of connections (V, V') it is calculated to which extent the volumes of
    connection V are shifted to connection V'. The particular formula is:

    PvB is the volume of connection V before shifting, W is the set of possible alternative connections. The function d is defined as follows:

    c and are user-defined parameters. This function has the effect, that connections which are
    outside of a tolerance in terms of time are not regarded as alternatives. For permitted connections, however, the readiness to change connections (alternating standby) increases with an
    alternative's decreasing temporal distance from the original connection.
    The diagram below shows an example of the function d for a connection V with
    and c = 10:

    526

    PTVGROUP

    7.10.8.6 Distance of the current solution from the balanced state

    Illustration 165: Readiness to change dependent on the alternative's departure time


    Then, the new volume of connection V results from:

    Shifting volumes between connections also means new volumes for all vehicle journey items.
    This method does not take the independence of connections into account.
    Note: Optional shifting of volumes between adjacent connections is only provided with
    the DB impedance function.
    7.10.8.6

    Distance of the current solution from the balanced state


    Depending on the applied smoothing method, the differences can be computed between
    smoothed and non-smoothed impedances or vol/cap ratios. The skims below describe the gap
    between the current solution and a balanced state. Using these skims it becomes obvious,
    whether and to which degree the balanced state has been reached.
    With smoothed impedances, the following skims are calculated:

    Accordingly, in case of vol/cap ratio-based smoothing:

    PTVGROUP

    527

    7.10.8.7 Termination criteria

    Here, N is the number of connections.


    7.10.8.7

    Termination criteria
    The procedure will terminate if at least one of the following criteria is satisfied:
    The number of iterations exceeds the user-defined maximum number of iterations.
    The changes to all vehicle journey item volumes in total do not reach a given maximum
    threshold. For the evaluation, the following inequality is used:

    a and b are user-defined parameters. Satisfying the second criterion does not automatically
    mean that the equilibrium state has been reached. It just means that volumes and thus also
    impedances will no longer change. Usually, this condition is forced by the smoothing methods.

    7.11

    Assignment analysis PuT


    Assignment analysis is used for calculating the correlation (Goodness-of-Fit Report) between
    calculated and observed attribute values of a selected network object type.
    The calculated value is derived from the assignment or the network model.
    The observed value may be count data or measured data.
    Here are some examples:
    Journey time comparisons between PrT and PuT
    Journey time comparisons of different scenarios
    Calculated and counted volumes (links, turns or main turns)
    Calculated and measured speeds
    Any numeric input and output attributes of the following network objects can be selected:
    Links
    Nodes
    Turns
    Main nodes
    Main turns
    Lines
    Line routes
    Screenlines
    Time profiles
    Paths
    Prerequisite is, that the observed values must be >0 for the selected network object type.
    You can select which objects you want to include in the assignment analysis. There are three
    possibilities:
    All objects of the selected network object type
    Only active objects
    Only objects with observed value > 0

    528

    PTVGROUP

    7.11 Assignment analysis PuT


    For the assignment analysis, as an option, you can consider user-defined tolerances for userdefined value ranges of the calculated attribute.
    The quality of the correlation can be determined and issued in two ways:
    in groups (for each value of the classification attribute)
    collectively for all included network objects
    For the output, the data model of the network object types above has been supplemented with
    the calculated attribute Assignment deviation (AssignDev ) of type real. Alike all other Visum
    attributes, the attribute can be graphically displayed and issued in lists of the respective network object.
    In addition, Visum calculates various indicators (per group or collectively) that can be issued in
    a list or in a chart.
    Note: An assignment result is no longer necessary in order to calculate the correlation
    coefficient.
    The table 200 shows the calculation rules for the output attributes of the assignment analysis.
    The following applies to the formulas:
    Z

    Observation (count or measurement)

    Calculation (assignment or network model)

    Number objects with an observed value > 0

    AbsRMSE
    Abs RMSE

    Absolute root of mean square deviation


    Significant differences between counted and modeled values have
    a higher impact according to

    Intercept
    Intercept

    Coefficient b in linear regression


    Cf. Excel, linear regression (y = ax + b)

    ShareAccGEH
    Share with acceptable GEH

    Percentage objects with acceptable GEH value (per network


    object)

    ShareAccRelErr
    Share with acceptable relative errors

    Percentage objects within tolerance

    PTVGROUP

    529

    7.11 Assignment analysis PuT


    NumObs
    Number of observations

    Number of observations per class (objects with observed value >


    0)

    NumClass
    Number in class

    Total number (=observed + not observed) objects per class

    ClassValue

    Value of classification attribute (or blank, if not classified)

    Corr

    Correlation coefficient (cf. Excel function Pearson)


    Notes
    The value range lies between -1 and 1, where the following applies:
    -1 = observation opposed to modeling
    0 = no correlation (at random)
    +1 = very good correlation
    The ratio observed/modeled value should be as close to 1 as possible.
    In case of only 2 values > 0, the correlation coefficient is -1 or 1.
    From the value of the correlation coefficient, one cannot determine
    whether all observed values are higher (or lower) than the calculated values or upward and downward deviations exist.

    MeanAbsE

    Mean absolute error


    Mean deviation of absolute values(a)
    (Difference between observed and modeled value)

    MeanObs
    Mean observed value
    MeanRelE

    Mean relative error


    Mean deviation of absolute values in % (p) according to

    530

    R2

    Coefficient of determination r2
    Cf. Excel function RSQ

    RelRMSE

    Relative root of mean square deviation

    PTVGROUP

    7.12 PuT passenger survey


    StdDev

    Standard deviation

    Slope

    Coefficient a in linear regression


    Cf. Excel function, Linear Regression (y = ax + b)

    Table 200: Calculation rules for the attributes of the assignment analysis

    7.12

    PuT passenger survey


    Passenger sample surveys - interviews and counts - are essential for public transport supply
    planning. Usually the passengers route within the PuT line network is not described completely by interview data. This applies especially to passengers who have to transfer several
    times or those who need to walk for transfers.
    Survey personnel usually count the passengers boarding the surveyed line at the boarding
    stop and ask for the following details of the trip.
    Boarding stop of passenger trip where passenger enters the survey line, which means
    where the passenger is interviewed by the survey personnel,
    Alighting stop of passenger trip where passenger will leave the survey line,
    Origin and destination of the passenger trip.
    After reading passenger data from file, it has to be verified and completed, if necessary. Also
    the time of departure from either the boarding stop or the origin terminal of the survey line
    have to be recorded in a questionnaire.
    The Visum add-on Passenger onboard survey contains the following basic functions.
    Read survey data
    Loading data from file and conversion of data records into PuT paths (see User Manual:
    Chpt. 7.12.3 , page 535).
    Note: From each survey data record (which means per questionnaire or per ticket,
    respectively), a passenger trip is generated and stored as PuT path.
    Plausibilization of survey data
    Verification and completion of the survey data records which contain the basic passenger
    trip data (see "Plausibilization of survey data" on page 535).
    Direct assignment
    Assignment of the survey data records (calculating network volumes from path volumes),
    optionally OD matrices and skim matrices can be generated (see "Assignment of survey
    data" on page 540).
    Note: Subsequently, indicator data on path level (by survey data record) is automatically provided in the PuT paths list.
    After direct assignment of the survey data, the full range of the Visum functionality for analysis
    and display of results is available, e.g. flow bundle display (see "Interactive analyses" on page
    716) or PuT operating indicators (see "PuT operating Indicators" on page 629).

    PTVGROUP

    531

    7.12.1 Basic data of a passenger trip

    7.12.1

    Basic data of a passenger trip

    Attribute

    Description

    Survey line

    Designation of the line, where the passenger is encountered

    Preceding/Succeeding

    Path legs traveled by passenger which are before or after the survey line
    A path leg is the transfer-free part of a passenger trip on a line,
    from boarding to alighting (number of path legs = number of transfers + 1)

    532

    Origin terminal

    First stop of a vehicle journey

    Destination terminal

    Last stop of a vehicle journey

    OrigStop

    Starting stop (origin) of a passenger trip: first boarding stop entering a PuT line per PuT path

    DestStop

    Destination stop of a passenger trip: last alighting stop leaving a


    PuT line per PuT path

    BoardStop

    Boarding stop of the survey line = stop at which the passenger


    enters the survey line

    AlightStop

    Alighting stop of the survey line: stop at which the passenger leaves the survey line

    PTVGROUP

    7.12.2 Passenger onboard survey: Basic approach


    Standard questionnaire

    Illustration 166: Standard questionnaire


    The replies obtained in a passenger survey are noted down in questionnaires. Such a questionnaire form usually consists of parts.
    Features which identify the questionnaire are entered in the header, such as the interviewer's number, vehicle class and service trip number.
    In the main section, codes for the boarding and alighting stops of the survey line are entered, plus information on any preceding or succeeding lines.
    The illustration 166 displays a schematic example for a survey. With this questionnaire, up to 5
    path legs (2 preceding legs + survey line + 2 succeeding legs) can be recorded.

    7.12.2

    Passenger onboard survey: Basic approach


    The general procedure for the PuT passenger onboard survey is as follows. The illustration
    167 illustrates this procedure schematically.
    1. Visum first reads from a text file a set of survey records which closely resemble the information in the PuT Path Legs list. For each surveyed trip, the following information is supplied:
    Vehicle journey, boarding and alighting stop point for the surveyed leg of the trip
    Origin and destination of the complete trip
    Information on the legs taken between origin stop and surveyed boarding stop and between surveyed alighting stop and destination stop (if present).
    2. The second operation tries to complete each survey record by filling in plausible values for
    all missing fields.
    Numerous validity checks are carried out on the survey data, and the user can specify
    rules for substituting by plausible values (for example, for the lines or the departure
    times of the services), if the stated values do not form part of a valid connection.
    A comprehensive log file tags each survey record with a status describing which substitutions were performed and how reliable the resulting information is.

    PTVGROUP

    533

    7.12.2 Passenger onboard survey: Basic approach


    A new version of the survey file is written which contains all the additional information
    that could be determined automatically.
    Users can review the survey records which are flagged as inconsistent and decide
    whether to discard or to manually correct them.
    The operation Plausibilization of survey records can then be repeated.
    3. As step three, survey data that succeeded during plausibilization are directly assigned to
    the Visum network.
    Volumes of connections, all network object volumes and related indicators are set.
    Furthermore a demand matrix can be created containing the surveyed trips.
    PuT skim matrices of the connections can be created.
    Any of the post-assignment analysis tools can then be applied to the assignment result
    generated from survey data.

    Illustration 167: Processing of PuT passenger surveys


    Note: The same functionality can be applied to data extracted from e-ticketing applications, if the data contain at least check-in information per path leg with line route, stop
    point, and departure time. In this case, a path leg needs to be marked as surveyed path
    leg.

    534

    PTVGROUP

    7.12.3 Read survey data

    7.12.3

    Read survey data


    This method loads survey data records from text files (one file per PuT demand segment) into
    Visum for future plausibilization. Since Visum stores survey data records as PuT paths, the
    data can be accessed via listings as well as via COM interface or flow bundle analysis and
    other Visum functionalities provided for PuT paths (see User Manual: Chpt. 19.3.2 , page
    2055).

    7.12.4

    Plausibilization of survey data


    For plausibility purposes the correctness of the path stated by the passenger is verified for
    each survey record. By comparing each survey record with the timetable information of the
    Visum network model it is possible to identify and correct survey records which state an incorrect path. Incorrect lines or line routes or time profiles are replaced by correct lines or line routes or time profiles. Furthermore, additional data is added to each data record, such as times of
    departure and of arrival, travel time and trip distance, used lines and walk links.
    Note: 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. If one of these stops is deleted after reading survey data from file, all paths
    from/to these stops will get lost.
    Plausibilization: Basic approach
    As a rule, the plausibilization includes the following steps.
    1. Validity check of the survey path leg (illustration 168)
    2. Validity check of the preceding section (illustration 169)
    3. Validity check of succeeding section
    For each of 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.
    Note: In single-row survey data records, the preceding section as well as the succeeding
    section may consist of one or two path legs each (see User Manual: Chpt. 19.3.1.1 , page
    2052).
    Inner path leg leading from PreStop to BoardStop and from AlightStop to SucStop
    respectively.
    Outer path leg leading from OrigStop to PreStop and from SucStop to DestStop,
    respectively.
    In multi-row survey data records, the previous section as well as the succeeding section
    may consist of any number of path legs (see User Manual: Chpt. 19.3.1.2 , page 2053).

    PTVGROUP

    535

    7.12.4 Plausibilization of survey data


    Validity check of the survey path leg

    Illustration 168: Validity check of the survey path leg


    * In case of multiple vehicle journeys, the one with the minimum sum of run time and wait
    time is chosen.

    536

    PTVGROUP

    7.12.4 Plausibilization of survey data


    Validity check of prec. section (Example with 1 or 2 prec. path legs)

    Illustration 169: Validity check of the preceding section


    * In case of multiple vehicle journeys, the one with the minimum sum of run time and wait
    time is chosen.
    Validity check of succeeding section
    The validity check of the succeeding path leg(s) is performed accordingly (illustration 169).

    PTVGROUP

    537

    7.12.4 Plausibilization of survey data


    Status IDs for the plausibilization quality
    In a result file and also in lists (PuT paths and PuT path legs), a status ID (range 0...9) describes the quality determined by validity check and plausibilization for each survey record:
    for the surveyed path leg E in (table 201)
    for the preceding section V in (table 202)
    for the succeeding section N in (table 203)
    for the entire survey data record G in (table 204)
    Status indicators for the surveyed path leg (E)
    0

    Not yet checked

    Plausible
    1

    A vehicle journey could be found in the surveyed time profile (or surveyed line
    route or line, depends on preciseness of input data), which connects boarding
    stop and alighting stop of the surveyed path leg and starts within the time tolerance interval defined for the time of departure from the boarding stop.

    A vehicle journey could be found in another time profile (or line route) of the surveyed line, which connects boarding stop and alighting stop of the surveyed path
    leg and starts within the time tolerance interval defined for the time of departure
    from the boarding stop.

    A vehicle journey could be found in a time profile (or line route) of another line,
    which connects boarding stop and alighting stop of the surveyed path leg and
    starts within the time tolerance interval defined for the time of departure from the
    boarding stop.

    For the surveyed path leg, an indirect connection could be found by timetablebased search (shortest path search) which departs from the boarding stop within
    the tolerance interval defined for the departure time from this stop and includes at
    least one transfer (and walk links, if applicable).

    Not plausible
    7

    Implausible, because none of the line routes (which are valid due to current parameter settings) connects boarding stop and alighting stop and connection search
    is not permitted either.

    Implausible, because the time profiles of the line routes (which are valid due to current parameter settings) connecting boarding and alighting stop do not include a
    departure within the time tolerance interval defined for the time of departure from
    the boarding stop and connection search is not permitted either.

    Implausible, because no connection from boarding to alighting stop starting in the


    given time frame could be found during connection search calculation.
    Table 201: Status indicators for the surveyed path leg

    538

    PTVGROUP

    7.12.4 Plausibilization of survey data


    Status indicators for the preceding section (V)
    0

    Does not exist

    Plausible
    1

    A vehicle journey could be found in the preceding time profile (or preceding line
    route or line, depends on preciseness of input data), which meets the condition
    defined for the permitted time span.

    A vehicle journey could be found in another time profile (or line route) of the preceding line, which meets the condition defined for the permitted time span.

    A vehicle journey could be found in a time profile (or line route) of another line,
    which meets the condition defined for the permitted time span.

    A direct vehicle journey from OriginStop to BoardStop with a shorter journey time
    (Factor Journey time of Direct connection + constant < Journey time of preceding
    section) compared to the plausible (multi-part) preceding section could be found
    and is used instead.

    Replacing at least one of the preceding path legs by an indirect connection which
    was found by timetable-based connection search (incl. transfer(s) and walk link
    (s), if applicable).

    Replacing the implausible (multi-part) preceding section from OriginStop to


    BoardStop by a connection with an arrival time matching the departure time of the
    survey line from the BoardStop.

    Not plausible
    9

    Implausible, because no path leg (or sequence of path legs) could be found meeting the given validity check criteria.
    Table 202: Status indicators for the preceding section

    Status indicators for the succeeding section (N)


    0

    Does not exist

    Plausible
    1

    A vehicle journey could be found in the succeeding time profile (or succeeding
    line route or line, depends on preciseness of input data), which meets the condition defined for the permitted time span.

    A vehicle journey could be found in another time profile (or line route) of the succeeding line, which meets the condition defined for the permitted time span.

    A vehicle journey could be found in a time profile (or line route) of another line,
    which meets the condition defined for the permitted time span.

    A direct vehicle journey from AlightStop to DestStop with a shorter journey time
    (Factor Journey time of Direct connection + constant < Journey time of succeeding section) compared to the plausible (multi-part) succeeding section could
    be found and is used instead.

    Replacing at least one of the succeeding path legs by an indirect connection

    PTVGROUP

    539

    7.12.5 Assignment of survey data


    Status indicators for the succeeding section (N)
    which was found by timetable-based connection search (incl. transfer(s) and
    walk link(s), if applicable).
    6

    Replacing the implausible (multi-part) succeeding section from AlightStop to


    DestStop by a connection with a departure time matching the arrival time of the
    survey line at the AlightStop.

    Not plausible
    9

    Implausible, because no path leg (or sequence of path legs) could be found meeting the given validity check criteria.

    Table 203: Status indicators for the succeeding section


    Status indicators for the entire survey data record (G)
    0

    Not processed

    Plausible
    1

    All of the sections (preceding leg(s), succeeding leg(s) and/or survey leg) are
    plausible.

    Not plausible
    9

    Implausible because of one (or more) implausible sections (preceding leg(s),


    succeeding leg(s) and/or survey leg).
    Table 204: Status indicators for the entire survey data record

    7.12.5

    Assignment of survey data


    Direct assignment means assignment of a demand segments plausible paths to the network
    (see User Manual: Chpt. 19.3.4 , page 2071).
    Subsequently, any of the post-assignment analyses provided for public transport can be carried out.
    Volume display as bars along links (see "Tabular and graphical display" on page 744)
    Flow bundle calculations (see "Flow bundles" on page 716)
    Skim matrix calculation on the basis of directly assigned paths (if not already calculated at
    the direct assignment) (see "PuT skims" on page 456)
    Calculation of PuT operating indicators, for example for the line costing and revenue calculation (see "PuT operating Indicators" on page 629)

    540

    PTVGROUP

    8 Operator model PuT

    Operator model PuT


    The PuT operator model in Visum comprises the PuT operating indicators and the PuT line
    blocking procedure.
    Subjects
    Application areas and scope of operations
    Network objects in the Operator model
    Typical work flow in the PuT operator model
    Line blocking
    PuT fare model
    PuT operating Indicators
    Calculation of the fare revenues (revenue calculation)

    8.1

    Application areas and scope of operations


    The results of the procedures PuT operating indicators and Line blocking are saved in attributes, which are overall designated as operating indicators. These can be divided into the following categories:
    General indicators for bundling line data (for example the number of vehicle journeys per
    line route) [Attribute: Number of service trips])
    Indicators for the measurement of the operating performance (for example the service kilometers to be run by an operator)
    Indicators for the measurement of the transport performance (for example the passenger
    hours for a vehicle journey)
    Indicators for the calculation of the operating costs (for example the stop point costs per
    line). The cost model permits modeling of vehicle type-based costs as well as infrastructure costs.
    Indicators for the calculation of fare revenues (revenue calculation). Zone-based fares,
    distance-based fares as well as further fare structures can be modeled for fare calculation
    in Visum.
    Indicators of vehicle requirement and of line blocking
    Typical application areas of the operator model are:
    Assessment of the economic efficiency of an existing PuT supply and derivation of improvement potentials
    Analysis of the effects of supply changes on the economic result (cost coverage)
    Comparison of costs for establishment and maintenance of PuT supply and fare revenues
    Calculation of the cost coverage on different aggregation levels of the line hierarchy (for
    example cost coverage per line, line route or vehicle journey)
    Distribution of the fare revenues onto operators of a PuT supply
    Distribution of the fare revenues onto local authorities (counties, municipalities)
    Performance check down to the trip and vehicle level
    The second module of the operator model is line blocking. A line block contains all vehicle
    journeys that are run successively by one vehicle combination (see User Manual: Chpt. 20.1 ,
    page 2091) or by several similar vehicle combinations. The objective of line blocking is to

    PTVGROUP

    541

    8.1.1 Calculation of indicators on different aggregation levels


    assign the total number of trips to vehicles, so that costs are reduced. Also line blocking provides indicators such as empty kilometers of a line block. In the following, these are designated as indicators of the vehicle requirement and line blocking. In most cases line blocking
    is carried out prior to the calculation of PuT operating indicators in the procedure flow,
    because it provides input attributes for cost analyses (determination of the number of vehicles,
    which has an effect on the vehicle costs in the PuT operating indicators). The procedure PuT
    interlining matrix is provided in addition to the line blocking procedure. It calculates transport
    system-specific skim matrices for interlining trips between stop points of a transport system.

    8.1.1

    Calculation of indicators on different aggregation levels


    Visum allows indicators to be calculated in different granularity. Passenger kilometers, costs,
    and revenues, for example, can be calculated for vehicle journeys of specific line using lowfloor buses between 6 and 7 a.m. in the municipal territory. Or have the passenger kilometers
    calculated for each operator in your model, to divide the fare revenues between the operators.
    The indicators can be calculated as follows.
    Differentiated according to territory, for example local authorities such as counties or districts (see User Manual: Chpt. 20.3.1 , page 2156)
    According to operating companies
    Temporal distinction through freely adjustable time intervals within a day, or if a calendar is used within a week or a year. This is independent of the PuT operating indicators
    procedure (see User Manual: Chpt. 17.2 , page 1860)
    Differentiated according to the objects of the line hierarchy. These include main lines,
    lines, line routes, line route items, time profiles, time profile items, vehicle journeys and
    vehicle journey items
    There are different levels of detail for breaking down indicators to territories. To calculate indicators on these levels of detail, apply the procedure PuT operating indicators (see User
    Manual: Chpt. 20.3 , page 2156). The results of the procedure can be found in the Territories PuT detail list. In detail, the indicators can be calculated for territories on the following levels
    (this concerns indicators from the PuT assignment as well as from the procedure PuT operating indicators and the line blocking procedure):
    Territory
    Territory x Transport system
    Territory x Main line
    Territory x Line
    Territory x Line route
    Territory x Time profile
    Territory x Vehicle journey
    Territory x Transport system x Vehicle combination
    Territory x Main line x Vehicle combination
    Territory x Line x Vehicle combination
    Territory x Line route x Vehicle combination
    Territory x Time profile x Vehicle combination
    Territory x Vehicle journey x Vehicle combination

    542

    PTVGROUP

    8.1.2 Introductory examples for PuT indicators


    If a Visum model has two territories (west, east) and three transport systems (bus, tram, train),
    indicators are calculated for each combination of territory and transport system on the level territory x transport system.
    Territory

    TSys

    ServiceKm

    East

    Bus

    2,776.88

    East

    Train

    1,611.57

    21,094.72

    East

    Tram

    6,796.78

    187,312.42

    West

    Bus

    538.57

    9,671.80

    West

    Train

    323.14

    5,803.08

    5,703.52

    214,538.25

    West
    Tram
    Table 205: Level Territory x Transport system

    PassengerKm
    17,219.58

    Note: Not every indicator is available for all aggregation levels. In the IndicatorAvailability.xls, under ...Program files\PTV Vision\PTV Visum 13\Doc\Eng, you can
    find tables specifying the aggregation levels on which the indicators are available.

    8.1.2

    Introductory examples for PuT indicators


    For several indicators, the computation of indicator data with spatial reference to a territory,
    with temporal reference to a time slice, by operator and for the elements of the line hierarchy is
    described below. The examples are there to give an impression on the application possibilities and the performance of the PuT operator model. The documentation also contains
    example calculations for the individual indicators (see "PuT interlining matrix procedure" on
    page 604). The files IndicatorSource.xls and IndicatorAvailabilityxls, listed under ...Program
    files\PTV Vision\PTV Visum 13\Doc\Eng, specify which indicators are available on which evaluation level. The values were created with the example KA_dyn.ver, which is provided in your
    Visum installation, and can thus be reproduced.

    8.1.2.1

    Indicator data by territory


    Using territory-related evaluations, you can calculate indicator data for territories which represent fare zones, urban districts, municipalities or counties for example. The territory polygon is
    decisive for the calculation; and the indicator's share, which applies to the polygon will be returned (see "Territories" on page 63). The example network of Karlsruhe contains six territories
    (illustration 170 ). In the example, the territories correspond to the PuT fare zones created in
    the Visum fare model. This means, that the polygons (territory boundaries) were modeled in
    such a way, that they contain exactly those stops of the respective PuT fare zones. Each PuT
    fare zone thus corresponds to exactly one territory and the indicators can be calculated by fare
    zone. Some examples for possible territory-based analyses are introduced below.

    PTVGROUP

    543

    8.1.2.1 Indicator data by territory

    Illustration 170: Territories in the example


    Using the indicators Number of stop points Total, Line network length (directed) and the Number of service trips, information can be obtained on the line routes and the timetable of the
    model for each territory. Within the territory polygon Center there are 182 stop points. The line
    network length is calculated per transport system. The directed line length (the total link length
    of the links traversed via line routes) of the bus network in the city center is 54km. In the analysis period of one day, 3154vehicle journeys (number of vehicle journeys with at least one
    stop within the territory polygon) stop in this territory. Using these indicators as a basis, the first
    statements regarding the PuT connectivity of the territories can be made.
    Territory
    Center

    Stop points total

    Line network length directed


    (Bus) [km]

    182

    54.015

    3,154

    North
    East

    53

    34.993

    814

    South

    14

    8.716

    350

    East

    73

    90.188

    1,776

    West

    157

    66.749

    1,779

    58.474

    1,888

    Suburbs
    96
    Table 206: Indicators for line route analysis by territory

    544

    Number of service trips


    (AP)

    PTVGROUP

    8.1.2.2 Territory-based evaluation on different aggregation levels


    The performance indicators represent the efforts required for the PuT supply provision in
    length units or in time units. The most used indicator is called service kilometers or service
    miles, if applicable. These are the main drivers for costs, which arise for the operator of a line
    The ratio between the service miles and the revenues, which are generated in a territory, can
    provide information on how efficient the performance is in this territory. In the example, this
    ratio is stored in the user-defined attribute Revenue_ per_ServiceKM. For that purpose, the
    value of this formula describing the ratio was stored in the user-defined attribute. In this way,
    also territories can be identified, where it is also very appealing for a PuT operator, to provide
    transport performance. In the outer regions of the example (suburbs), where fewer passengers
    have to be transported, however, longer distances have to be covered, less revenues probably accumulate than in the center. Such a view is useful, if no costs have been modeled in
    Visum and simply tendency statements on the cost-effectiveness in a territory are desired.
    Territory
    Center

    ServiceKm(AP) [km]

    Revenue length-proportional (AP) [CU]

    Revenue per ServiceKM [CU/km]

    16,648

    143,945.75

    8.65

    North East

    2,918

    8,674.07

    2.97

    South

    1,379

    7,416.01

    5.38

    East

    6,615

    24,371.61

    3.68

    West

    6,328

    40,159.07

    6.35

    Suburbs
    11,191
    4,736.75
    0.42
    Table 207: Territory-based indicator data for transport performance and revenue analysis
    8.1.2.2

    Territory-based evaluation on different aggregation levels


    The indicator data can be refined even more, if the territory is evaluated on different aggregation levels. Indicators can for example, be calculated like this for each line within a territory.
    In the field of transport performance, the indicator Passenger kilometers of a line within a territory is often used for analyses. On attainable PuT revenues, the passenger kilometers permit
    statements by trend, especially in case there are no data on the exact revenues and these are
    therefore not modeled in Visum. The table 208 shows the passenger kilometers and the number of passenger trips (number of passengers boarding) for line 2 in the territories, which are
    traversed (illustration 171 ). For this evaluation, the aggregation level Territory x Line was
    selected (see User Manual: Chpt. 20.3 , page 2156). This is how you can determine how many
    passenger kilometers of the line apply to the fare zones.

    PTVGROUP

    545

    8.1.2.3 Indicators at the line hierarchy

    Illustration 171: Line 2 traverses several territories


    Territory

    Line

    PassengerKm(AP)
    [km]

    Passenger trips unlinked

    Center

    80,590

    30,533

    East

    21,021

    9,479

    West
    2
    4,356
    Table 208: Territory-based analysis on aggregation level Territory x Line
    8.1.2.3

    546

    6,021

    Indicators at the line hierarchy


    If you are not interested in the territory-based evaluation of indicators, you can also carry out
    evaluations directly at the line hierarchy levels. For a PuT operator it is important to know for
    example, what the volume/capacity ratio of the vehicles is along the course of the line routes.
    Based on this, the operator can decide to lengthen or shorten a line route. The table 209
    shows the beginning and the end of the line route course of line 002 and the saturation of
    seats between stops. Between Siemensallee and Lassallestrae, the average volume/capacity ratio is only 4%, so that shortening the line may be a possibility.

    PTVGROUP

    8.1.2.3 Indicators at the line hierarchy


    Index

    Line route Direction


    name
    code

    Node number Stop point name

    Vol/Cap
    ratio Seats
    [%]

    2_H

    >

    105497581

    2_H

    >

    105224474

    2_H

    >

    105224473

    2_H

    >

    105497580

    2_H

    >

    105497579

    10

    2_H

    >

    105226816

    10

    2_H

    >

    105226814

    10

    2_H

    >

    105226812

    10

    2_H

    >

    105222467

    10

    2_H

    >

    105497578

    ...

    ...

    ...

    ...

    106

    2_H

    >

    100521

    Kussmaulstrasse

    41

    107

    2_H

    >

    100522

    Hertzstrasse

    26

    108

    2_H

    >

    100523

    Feierabendweg

    21

    109

    2_H

    >

    100524

    Neureuter Strasse

    110

    2_H

    >

    105496077

    111

    2_H

    >

    100525

    Wolfartsweier Nord

    8
    8
    8

    Durlach Zndhtle

    10

    10
    Aue Friedhof / Steiermrker Str.

    11

    ...

    ...

    9
    9

    Siemensallee

    112
    2_H
    >
    100526
    Lassallestr
    Table 209: Analysis of the Vol/Cap ratio of seats on the line route level

    The service kilometers are often taken into account for the distribution of the calculated operating costs between an infrastructural operator and the provider of the PuT supply. In this
    example, Line S3 uses the infrastructure of the Deutsche Bahn (German Rail). In the Lines list,
    the service kilometers can be displayed per line.
    Line name

    Transport system

    R92

    TRAIN

    243.612

    S1

    TRAM

    2,468.828

    S11

    TRAM

    1,080.146

    S2

    TRAM

    3,273.128

    S3

    TRAM

    835.176

    S31

    TRAM

    577.254

    S4

    TRAM

    2,129.673

    S5

    TRAM

    4,074.132

    S8

    TRAIN

    53.920

    PTVGROUP

    Service kilometers [km]

    547

    8.1.2.3 Indicators at the line hierarchy


    Table 210: Service kilometer analysis on the level of lines
    Visum supports you when making a decision on the line bundle to be run by a bus operator
    ("To which operator, which of the lines are allocated?"). For each line, typical indicators such
    as costs, total revenue, revenue per passenger trip, total cost coverage and cost coverage per
    passenger trip are calculated. The table shows the values for the analysis horizon of one year.
    Lines with a cost coverage deficit have a negative amount of coverage. In terms of balancing
    the high-profit lines and low-profit lines as fair as possible, this data can be used to form line
    bundles, for which PuT operators then can apply in the framework of a tender.

    548

    Line
    name

    TransCosts [CU] Revenue


    port systotal [CU]
    tem

    Revenue Cost cov.


    PTrip
    total [CU]
    [CU]

    Cost
    cov. /
    PTrip
    [CU]

    Cost
    cov. [%]

    21

    BUS

    433,831.31

    773,477.34

    0.56

    339,646.03

    0.25

    178.29

    22

    BUS

    254,736.07

    314,551.88

    0.53

    59,815.80

    0.10

    123.48

    23

    BUS

    487,624.88

    214,824.83

    0.55

    -272,800.05

    -0.70

    44.06

    30

    BUS

    515,029.0- 1,818,301.42
    6

    0.63

    1,303,272.44

    0.45

    353.05

    31

    BUS

    705,276.05

    872,187.83

    0.59

    166,911.78

    0.11

    123.67

    32

    BUS

    452,384.95

    425,354.17

    0.44

    -27,030.78

    -0.03

    94.02

    42

    BUS

    361,669.22

    868,201.73

    0.52

    506,532.51

    0.30

    240.05

    43

    BUS

    276,488.08

    215,746.49

    0.50

    -60,741.59

    -0.14

    78.03

    44

    BUS

    333,456.14

    54,659.89

    0.53

    -278,796.26

    -2.69

    16.39

    45

    BUS

    429,574.91

    330,818.45

    0.61

    -98,756.46

    -0.18

    77.01

    46

    BUS

    188,345.74

    261,343.71

    0.51

    72,997.98

    0.14

    138.76

    47

    BUS

    339,342.42

    189,913.11

    0.71

    -149,429.31

    -0.56

    55.97

    50

    BUS

    509,071.08

    988,980.88

    0.58

    479,909.80

    0.28

    194.27

    51

    BUS

    88,748.77

    195,342.70

    0.57

    106,593.93

    0.31

    220.11

    52

    BUS

    328,666.8-

    335,666.87

    0.52

    7,000.01

    0.01

    102.13

    PTVGROUP

    8.1.2.4 Evaluation of indicators on the operator level


    Line
    name

    TransCosts [CU] Revenue


    port systotal [CU]
    tem

    Revenue Cost cov.


    PTrip
    total [CU]
    [CU]

    Cost
    cov. /
    PTrip
    [CU]

    Cost
    cov. [%]

    5
    55

    BUS

    60

    BUS

    0.00

    0.00

    62

    BUS

    0.00

    0.00

    0.00

    0.00

    70

    BUS

    717,616.4- 1,375,946.76
    9

    0.53

    658,330.33

    0.25

    191.74

    71

    BUS

    83,309.71

    0.52

    88,093.79

    0.27

    205.74

    73

    BUS

    384,722.0- 1,809,097.33
    7

    0.52

    1,424,375.34

    0.41

    470.23

    74

    BUS

    265,425.2- 1,151,942.67
    8

    0.53

    886,517.42

    0.40

    434.00

    75

    BUS

    52,673.44

    243,368.34

    0.47

    190,694.90

    0.37

    462.03

    107

    BUS

    231,821.70

    77,805.81

    0.52

    -154,015.89

    -1.04

    33.56

    108

    BUS

    59,030.88

    0.00

    0.00

    -59,030.88

    0.00

    0.00

    123

    BUS

    397,079.54

    40,164.47

    0.99

    -356,915.07

    -8.76

    10.11

    151

    BUS

    216,990.34

    41,625.77

    25,569.0- -175,364.57
    0

    -7.16

    19.18

    222

    BUS

    244,624.05

    23,291.90

    2.16

    -221,332.15

    -20.56

    9.52

    551

    BUS

    142,190.73

    306,929.17

    0.59

    164,738.44

    0.32

    215.86

    337,039.9- 2,004,260.24
    8
    0.00

    0.00

    171,403.50

    0.00
    0.51

    0.00
    1,667,220.34

    0.00

    0.00

    0.43

    594.67

    Table 211: Cost and revenue computation on the level of lines


    8.1.2.4

    Evaluation of indicators on the operator level


    Splitting up the revenues from fares to various operators of a transport association often
    regards the service kilometers or the seat kilometers as a basis. Visum returns this data by operator. For the three operators in the Karlsruhe example, the following values apply.
    Operator name

    Service kilometers [km]

    Seat kilometers [km]

    TOK Tram Operator

    12,071

    1,092,238

    DB German Rail

    23,906

    2,165,751

    KBB Bus Operator


    9,096
    454,811
    Table 212: Evaluation of transport performance indicators on the level of operators

    PTVGROUP

    549

    8.1.2.5 Indicator data by time slice


    8.1.2.5

    Indicator data by time slice


    If you are working with analysis time intervals (see User Manual: Chpt. 17.2 , page 1860), you
    can evaluate most indicators broken down in time slices (see "PuT operating Indicators" on
    page 629). This means, that the share of an indicator value which falls in a time interval, is calculated. In the example KA_ dyn.ver, this is used to determine the service kilometers for 1hour-intervals. In this way, the bus operator can determine operational performance peaks
    and has an indicator for the evaluation, how evenly the vehicle fleet is utilized in the course of
    the day. The example shows time intervals of one hour from 5:00 a.m. to 10:00 p.m. For the
    bus operator, the operator-related evaluation via all time intervals returns the following service
    kilometer values.
    Operator name: KBB Bus Operator

    550

    ServiceKm (05:00
    a.m.)

    227.0

    ServiceKm (06:00
    a.m.)

    622.2

    ServiceKm (07:00
    a.m.)

    689.9

    ServiceKm (08:00
    a.m.)

    602.4

    ServiceKm (09:00
    a.m.)

    487.2

    ServiceKm (10:00
    a.m.)

    443.0

    ServiceKm (11:00
    a.m.)

    461.7

    ServiceKm (12:00
    a.m.)

    537.2

    ServiceKm (01:00
    p.m.)

    604.5

    ServiceKm (02:00
    p.m.)

    541.9

    ServiceKm (03:00
    p.m.)

    608.7

    ServiceKm (04:00
    p.m.)

    710.2

    ServiceKm (05:00
    p.m.)

    695.7

    ServiceKm (06:00
    p.m.)

    626.8

    ServiceKm (07:00
    p.m.)

    406.1

    PTVGROUP

    8.2 Network objects in the Operator model


    Operator name: KBB Bus Operator
    ServiceKm (08:00
    p.m.)

    263.1

    ServiceKm (09:00
    p.m.)

    203.1

    Table 213: Evaluation of service kilometers per time interval for the bus operator
    If the operator additionally compares the passenger kilometers, the statements by trend can be
    derived, for example the efficiency level by time interval. The time intervals 9 to 12p.m. and
    after 6p.m. show very low values for this indicator. Thus, in opposition to a relatively high transport supply performance (ServiceKm) there is a relatively low passenger demand.
    Time interval

    Service kilometers
    [km]

    Passenger kilometers [km]

    05:00 a.m.

    227.0

    3,101.9

    13.7

    06:00 a.m.

    622.2

    14,034.9

    22.6

    07:00 a.m.

    689.9

    24,411.3

    35.4

    08:00 a.m.

    602.4

    15,663.0

    26.0

    09:00 a.m.

    487.2

    4,785.9

    9.8

    10:00 a.m.

    443.0

    5,518.6

    12.5

    11:00 a.m.

    461.7

    7,902.9

    17.1

    12:00 a.m.

    537.2

    7,785.6

    14.5

    1:00 p.m.

    604.5

    13,961.9

    23.1

    2:00 p.m.

    541.9

    14,275.4

    26.3

    3:00 p.m.

    608.7

    12,241.2

    20.1

    4:00 p.m.

    710.2

    11,603.5

    16.3

    5:00 p.m.

    695.7

    7,215.4

    10.4

    6:00 p.m.

    626.8

    4,747.2

    7.6

    7:00 p.m.

    406.1

    1,731.9

    4.3

    8:00 p.m.

    263.1

    672.1

    2.6

    9:00 p.m.

    203.1

    258.4

    1.3

    Table 214: PassengerKm-to-ServiceKm ratio for the Bus operator

    8.2

    Network objects in the Operator model


    In connection with the operator model, the following network objects are of particular importance: operator, vehicle combination and vehicle unit. Relations among these network objects
    and their relations to other network objects are illustrated by illustration 172.

    PTVGROUP

    551

    8.3 Typical work flow in the PuT operator model

    Illustration 172: Allocation of vehicles and operators in the line hierarchy


    An operator can be allocated as the standard operator to a complete line. When creating
    a new vehicle journey for this line later, the standard operator will be pre-set.
    Apart from that, you can select an operator for particular vehicle journeys for example in
    the timetable editor.
    A vehicle combination can be allocated as the standard vehicle combination to a complete line or an entire time profile. When creating a new vehicle journey later, the standard
    vehicle combination will be pre-set.
    Apart from that, you can select a vehicle combination for particular vehicle journey sections for example in the timetable editor.
    One or more units of a vehicle unit make up a vehicle combination. In this way the trains
    can be more accurately modeled, because they can be made up of different coaches. The
    making-up means creating or editing a vehicle combination.

    8.3

    Typical work flow in the PuT operator model


    Typically, the following steps have to be carried out for analyses by means of the PuT operator
    model. Depending on the indicators to be calculated, not all of the steps are always
    necessary.
    1. Parameterization and calculation of PuT assignment procedures (see User Manual: Chpt.
    19.2 , page 2006).
    2. Creating PuT vehicles (see User Manual: Chpt. 15.28 , page 1282) and allocating vehicle
    journeys (vehicle combinations, vehicle units).
    3. Creating a fare model (ticket types, fare zones, fare points) (see User Manual: Chpt. 20.6 ,
    page 2169).
    4. Definition of a cost model (hourly costs, kilometer costs, vehicle costs, stop point costs, link
    costs, operator costs) (see User Manual: Chpt. 20.2 , page 2153)

    552

    PTVGROUP

    8.4 Line blocking


    5. Parameterization and calculation of the PuT line blocking procedure (see User Manual:
    Chpt. 20.1 , page 2091).
    6. Definition of the reference frameworks for evaluations
    Definition of territories (see User Manual: Chpt. 15.22.1 , page 1206) and selection of
    the aggregation level for evaluations by territory (see User Manual: Chpt. 20.3.2 , page
    2156).
    Definition of analysis time intervals for evaluations by time slice (see User Manual:
    Chpt. 17.2 , page 1860).
    Definition of operators (see User Manual: Chpt. 15.27.1 , page 1281) and allocation to
    vehicle journeys.
    Definition of the projection factor (see User Manual: Chpt. 15.42 , page 1511).
    7. Calculation of the Territory indicators procedure (see User Manual: Chpt. 17.4.3 , page
    1885).
    8. Calculation of the PuT operating indicators procedure for the desired indicator classes (see
    User Manual: Chpt. 20.3 , page 2156).

    8.4

    Line blocking
    Subjects
    Introduction to the line blocking procedure
    Line blocking application example
    Data model
    Line blocking description without vehicle interchange
    Line blocking description with vehicle interchange
    Vehicle requirement and line blocking indicators
    PuT interlining matrix procedure

    8.4.1

    Introduction to the line blocking procedure


    Application areas
    One of the main tasks of strategic PuT planning is to determine the number of vehicles, which
    are required to run a predefined timetable. The accumulated costs are thus to be minimized.
    To solve this task use the line blocking procedure in Visum.
    Another task of strategic planning is, planning the vehicle use dependant on the capacity of
    the individual vehicle combinations and the demand on vehicle journey level. To do so, the
    line blocking procedure with vehicle interchange can be used.
    If Visum is applied within an overall context of a PuT operating line costing and revenue calculation, the line blocking results can then provide a cost model module. With the vehicle
    demand, line blocking provides an input parameter for determining the vehicle type dependent costs, more precisely, the vehicle demand flows into the attribute Cost Vehicle . Furthermore, line blocking also determines the required empty trips. The empty time thus flows
    into the attribute Cost Time , the empty kilometers into the attribute Cost Distance. An overview on the PuT cost and revenue model can be found in illustration 200.

    PTVGROUP

    553

    8.4.1 Introduction to the line blocking procedure


    Fundamental terms
    The basis of the line blocking efforts is the timetable with the vehicle journeys, which are to be
    run by the blocks (Visum creates the blocks on the level of vehicle journey sections). Blocks
    are created by linking individual trips to trip chains, which can each be serviced by a vehicle
    combination. In the simplest case, a vehicle journey is concatenated at its last stop with a subsequent service which starts at the same stop. If such a linkage is not possible nor useful, an
    Empty Trip can transfer the vehicle combination to another stop point. Only the empty trips
    with a real change of location between two stop points count as interlining. If a vehicle changes from one stop point to the depot, at the same stop point or vice versa, this is referred to as
    pull-in or pull-out. This difference is important when selecting the option Interlining permissible
    (see User Manual: Chpt. 20.1.3.2 , page 2105). For pull-in or pull-out without change of location, neither empty trips nor empty kilometers accumulate.
    As displayed in the illustration 173, the following times are included.
    Interlining times
    Time required for interlining trips between two vehicle journeys which end/start at different
    stop points.
    Layover
    Layover time at a stop until next vehicle journey departure time.
    In Visum, those unproductive empty times without passenger transport can be calculated by
    means of the line blocking calculation and will then be considered during cost calculation for
    lines. The same applies to empty kilometers or empty miles.
    Once line blocking has been calculated, the empty times and empty kilometers/miles of each
    line block are known and can be displayed in the Line Blocks list.

    Illustration 173: Example line block with pull-out trip, interlining trip and pull-in trip
    No. Action

    554

    FromStop ToStop Dep

    Arr

    Line

    Time

    Length

    Pull-Out

    Stop3

    06:00
    a.m.

    06:30
    a.m.

    30 min

    10 km

    Vehicle jour- Stop3


    ney

    Stop1

    06:30
    a.m.

    07:15
    a.m.

    BUS1-1> 45 min

    30 km

    PTVGROUP

    8.4.1 Introduction to the line blocking procedure


    No. Action

    FromStop ToStop Dep

    Arr

    Interlining

    Stop1

    Stop2

    07:15
    a.m.

    Layover

    Stop2

    Stop2

    Vehicle jour- Stop2


    ney

    Layover

    Time

    Length

    07:30
    a.m.

    15 min

    10 km

    07:30
    a.m.

    08:00
    a.m.

    30 min

    0 km

    Stop1

    08:00
    a.m.

    08:15
    a.m.

    BUS1-2> 15 min

    Stop1

    Stop1

    08:15
    a.m.

    08:30
    a.m.

    15 min

    Vehicle jour- Stop1


    ney

    Stop3

    08:30
    a.m.

    09:15
    a.m.

    BUS1-1> 45 min

    Layover

    Stop3

    Stop3

    09:15
    a.m.

    09:30
    a.m.

    15 min

    Vehicle jour- Stop3


    ney

    Stop1

    09:30
    a.m.

    10:15
    a.m.

    BUS1-1> 45 min

    30 km

    10

    Pull-In

    10:15
    a.m.

    10:45
    a.m.

    30 min

    10 km

    Stop1

    Line

    10 km
    0 km
    30 km
    0 km

    Table 215: Example line block with pull-out trip, interlining trip and pull-in trip
    Optimization problem
    For the optimization task of line blocking, there is always a conflict between the number of
    empty trips (or more so the sum of empty kilometers covered on the empty trips) and the number of vehicles to be used. By creating empty trips, the number of required vehicles can
    usually be reduced, however, costs accumulate for the additional empty trips (illustration 174
    bottom). On the other hand, empty trips can be saved when implementing more vehicles (illustration 174 top). Depending on how costs are assessed by the user regarding empty trips on
    the one hand and additional vehicles on the other side, line blocking can return various optimum solutions. In addition to these two basic parameters, Visum offers more indicators which
    can be integrated into the cost function. The detailed cost function which is minimized in this
    context can be found in the line blocking procedure description (see "Construction of the
    graph" on page 586). The solution principle of line blocking in Visum, which includes creating
    a graph and the solution as a flow problem, is also described here.

    PTVGROUP

    555

    8.4.1 Introduction to the line blocking procedure

    Illustration 174: Conflict between empty trips and vehicle demand


    Line blocking evaluation
    The line blocking model and line blocking procedure allow you to analyze complex problems
    regarding line blocks and the resulting number of vehicles required. In the following section,
    the advantages of the line blocking procedure are evaluated.
    The solution as a graph flow problem now makes it possible to include long-lasting downtimes of vehicle combinations for example in depots - in the process. There is no maximum dwell time, as a vehicle is permitted to stay in the depot or anywhere else for any
    desired period. The dwell time can now be evaluated by a cost rate freely defined by the
    user and can thus be included in the objective function of the optimization problem (see
    "Construction of the graph" on page 586).
    The estimate of the number of vehicles required to run the blocks is more precise.
    If closed blocks are created, the empty trips can be determined which are required to
    return those vehicles shifted from one location to another, to their starting point. The
    non-consideration of the time required to return the vehicles would lead to an underestimation of the empty kilometers and empty times.
    The duration of blocks is limited by the assignment period that can be one or several
    calendar days. This allows the program to calculate the correct number of vehicles.

    556

    PTVGROUP

    8.4.2 Line blocking application example


    Minimum layover times have a major impact on possible transfers. As common in practice, you may use minimum layover times to interpret the restrictions during the assignment period as soft. You can thus balance the effects of minimum layover time and
    vehicle deployment.
    Blocks can be reedited manually. For that purpose, you can also create user-defined
    block item types. This is how you can manually include maintenance tasks or washing
    cars in block planning, for example.
    You can change various parameters per block version in order to easily compare several
    line blocking scenarios.
    At any time, a line block is consistent with its vehicle journey sections. Possible inconsistency only applies to reduced pre and post preparation times or empty trips in the case
    of changes to the network after line blocking.
    Blocks are only subject to the demand of correctness when they are being used, they do
    not necessarily have to be free of errors. This means: In many cases, you can edit the
    basic network whereupon existing line blocks are not discarded. Only when evaluating
    them in other procedures, line blocks have to be free of errors - for example as a basis for
    vehicle requirement, empty kilometers and empty trips computation for the calculation of
    vehicle-dependent costs by means of the PuT operating indicators procedure (illustration
    200). Check line block (see "Line block check" on page 582) thus helps finding and correcting potential errors.
    Several additional issues may be considered during line blocking. This includes the intended duration of the line blocks (number of blocking days), distribution of the layover times,
    scheduling of repeated stationary events (maintenance) and the consideration of the direction of travel.

    8.4.2

    Line blocking application example


    The example below illustrates the effects caused by different parameters and rules of thumb
    for planning. The simple example network is used as a basis (see "Example for PuT operating
    indicators" on page 630), into which additional bus lines were inserted. You can find the example files Example_ LineBlocking_ Closed.ver and Example_ LineBlocking_OpenClosed.ver in
    the Visum installation.

    8.4.2.1

    Closed blocks according to different criteria


    The first example is based on a symmetrical timetable.

    PTVGROUP

    557

    8.4.2.1 Closed blocks according to different criteria

    Illustration 175: Line network of the example with three bus lines (red, blue and yellow)

    Illustration 176: (Graphical) timetable of the example, color codes as above


    Line blocking is performed three times. For each run, different criteria are set. In either case,
    closed blocks are created. The results are stored in three block versions in parallel.
    Line blocking by line
    Only the trips of the same line are joined in a block. Vehicle demand is thus 5vehicles.
    Line comprehensive with expensive empty trips
    All bus trips can be linked jointly in blocks, but empty trips are expensive compared to the
    costs for an additional vehicle. 3 vehicles are required for this solution, whereby the solution can do without empty trips.
    Line comprehensive with inexpensive empty trips
    For this solution only 2vehicles are required, whereby 2empty trips are necessary.
    558

    PTVGROUP

    8.4.2.1 Closed blocks according to different criteria

    Block
    no.

    Block version code

    Number of
    blocking days

    Mean operating Mean operating


    time
    km

    NoLineInterchange

    1h 30min

    55

    NoLineInterchange

    1h 30min

    55

    NoLineInterchange

    21min

    26

    NoLineInterchange

    56min

    40

    LineInterchange_Expen- 2
    sive

    1h 51min

    81

    LineInterchange_Expen- 1
    sive

    56min

    40

    LineInterchange_
    Cheap

    2h 32min

    111

    LineInterchange_
    Cheap

    2h 32min

    111

    Table 216: Block data of the three approaches


    Below, the resulting blocks are illustrated graphically and in tabular form.
    Line blocking by line
    For this planning variant, the option "Same line" was selected for line blocking. Because there
    are two trips running at the same time, lines BUS1 and BUS2 each require 2vehicles, another
    one is required for line BUS3.

    PTVGROUP

    559

    8.4.2.1 Closed blocks according to different criteria


    Illustration 177: Covering the timetable through pure line blocks

    560

    Block
    no.

    Index

    Blockin- Block
    g day
    item
    type

    Line
    name

    Vehicl- Start
    e jour- time
    ney no.

    From
    Stop
    Point
    name

    End time ToStop


    Point
    name

    Layover

    00:00:00 X City

    07:20:00 X City

    Vehicle BUS1
    journey

    07:20:00 X City

    08:05:00 A Village

    Layover

    08:05:00 A Village

    08:40:00 A Village

    Vehicle BUS1
    journey

    08:40:00 A Village

    09:25:00 X City

    Layover

    09:25:00 X City

    00:00:00 X City
    am.

    Layover

    00:00:00 A Village

    06:59:00 A Village

    Vehicle BUS1
    journey

    07:10:00 A Village

    07:55:00 X City

    Layover

    07:55:00 X City

    08:50:00 X City

    Vehicle BUS1
    journey

    08:50:00 X City

    09:35:00 A Village

    Layover

    09:35:00 A Village

    00:00:00 A Vilam.
    lage

    Layover

    00:00:00 X City

    08:05:00 X City

    Vehicle BUS2
    journey

    22

    08:05:00 X City

    08:26:00 A Village

    Layover

    08:26:00 A Village

    00:00:00 A Vilam.
    lage

    Layover

    00:00:00 A Village

    08:15:00 A Village

    Vehicle BUS2
    journey

    21

    08:15:00 A Village

    08:36:00 X City

    Layover

    08:36:00 X City

    00:00:00 X City
    am.

    Layover

    00:00:00 A Village

    06:25:00 A Village

    Vehicle BUS3

    31

    06:25:00 A Vil-

    06:53:00 B Vil-

    PTVGROUP

    8.4.2.1 Closed blocks according to different criteria


    Block
    no.

    Index

    Blockin- Block
    g day
    item
    type

    Line
    name

    Vehicl- Start
    e jour- time
    ney no.

    journey

    From
    Stop
    Point
    name
    lage

    End time ToStop


    Point
    name
    lage

    Layover

    06:53:00 B Village

    10:00:00 B Village

    Vehicle BUS3
    journey

    32

    10:00:00 B Village

    10:28:00 A Village

    Layover

    10:28:00 A Village

    00:00:00 A Vilam.
    lage

    Table 217: Block items of the line blocks in block version 1


    Line blocking without empty trips
    This planning option assumes, that empty trips are more expensive compared to the costs for
    using another instance of the vehicle combination. This was achieved by increasing the factor
    for the cost shares (which result from empty time and empty km) in the evaluation function. In
    return, the restriction to pure line blocks was dropped.
    The line blocking procedure uses the possibility of switching from line to line to run a BUS2 service between each two BUS1 services. This is how both lines can be covered by two vehicles
    simultaneously.

    Illustration 178: Covering the timetable through blocks without empty trips

    PTVGROUP

    561

    8.4.2.1 Closed blocks according to different criteria


    Bloc- Index Blockin- Block
    k no.
    g day
    item
    type

    562

    Line
    name

    Vehicl- Start
    e jour- time
    ney
    no.

    FromSto- End
    p
    time
    Point
    name

    ToStop
    Point
    name

    Layover

    00:00:00 A Village

    06:25:00 A Village

    Vehicl- BUS1
    e journey

    07:10:00 A Village

    07:55:00 X City

    Layover

    07:55:00 X City

    08:05:00 X City

    Vehicl- BUS2
    e journey

    22

    08:05:00 X City

    08:26:00 A Village

    Layover

    08:26:00 A Village

    08:40:00 A Village

    Vehicl- BUS1
    e journey

    08:40:00 A Village

    09:25:00 X City

    Layover

    09:25:00 X City

    00:00:00 X City
    am.

    Layover

    00:00:00 X City

    07:20:00 X City

    Vehicl- BUS1
    e journey

    07:20:00 X City

    08:05:00 A Village

    10

    Layover

    08:05:00 A Village

    08:15:00 A Village

    11

    Vehicl- BUS2
    e journey

    21

    08:15:00 A Village

    08:36:00 X City

    12

    Layover

    08:36:00 X City

    08:50:00 X City

    13

    Vehicl- BUS1
    e journey

    08:50:00 X City

    09:35:00 A Village

    14

    Layover

    09:35:00 A Village

    00:00:00 A Vilam.
    lage

    Layover

    00:00:00 A Village

    06:25:00 A Village

    Vehicl- BUS3

    31

    06:25:00 A Village

    06:53:00 B Vil-

    PTVGROUP

    8.4.2.1 Closed blocks according to different criteria


    Bloc- Index Blockin- Block
    k no.
    g day
    item
    type

    Line
    name

    Vehicl- Start
    e jour- time
    ney
    no.

    FromSto- End
    p
    time
    Point
    name

    e journey

    ToStop
    Point
    name
    lage

    Layover

    06:53:00 B Village

    10:00:00 B Village

    Vehicl- BUS3
    e journey

    32

    10:00:00 B Village

    10:28:00 A Village

    Layover

    10:28:00 A Village

    00:00:00 A Vilam.
    lage

    Table 218: Block items of the line blocks in block version 2


    Line blocking with empty trips
    This planning approach permits line changes and also empty trips since they are attractive
    with regard to cost evaluation. Accordingly, the services of line BUS3, which has a diverging
    end point, can each be integrated in the line blocks resulting from the second variant by interlining (empty) trips. The vehicle demand is thus reduced to only two vehicles. This matches the
    theoretical minimum, because there are (repeatedly) two vehicle journeys running at the same
    time.

    Illustration 179: Covering the timetable through line comprehensive blocks with empty trips

    PTVGROUP

    563

    8.4.2.1 Closed blocks according to different criteria


    Note: Empty trips inillustration 179 run from B Village to X City following the first trip of the
    day, and in reverse direction before starting the last trip of the day. They are not graphically displayed.

    Block Inde- Blockin- Block


    no.
    x
    g day
    item
    type

    564

    Line Vehicl- Start


    nam- e jour- time
    e
    ney

    FromStopPoi- End
    nt name
    time

    ToStop
    Point
    name

    Layover

    00:00:00 A Village

    06:25:00 A Village

    Vehicl- BUS- 1
    e jour- 1
    ney

    07:10:00 A Village

    07:55:00 X City

    Layover

    07:55:00 X City

    08:05:00 X City

    Vehicl- BUS- 22
    e jour- 2
    ney

    08:05:00 X City

    08:26:00 A Village

    Layover

    08:26:00 A Village

    08:40:0- A Vil0
    lage

    Vehicl- BUS- 3
    e jour- 1
    ney

    08:40:0- A Village
    0

    09:25:0- X City
    0

    Empty
    trip

    09:25:0- X City
    0

    09:38:0- B Vil0
    lage

    Layover

    09:38:0- B Village
    0

    10:00:0- B Vil0
    lage

    Vehicl- BUS- 32
    e jour- 3
    ney

    10:00:0- B Village
    0

    10:28:0- A Vil0
    lage

    10

    Layover

    10:28:0- A Village
    0

    00:00:0- A Vil0 am.


    lage

    Layover

    00:00:0- A Village
    0

    06:25:0- A Vil0
    lage

    Vehicl- BUS- 31
    e jour- 3
    ney

    06:25:0- A Village
    0

    06:53:0- B Vil0
    lage

    Empty
    trip

    06:53:0- B Village
    0

    07:06:0- X City
    0

    Layover

    07:06:0- X City
    0

    07:20:0- X City
    0

    Vehicl- BUS- 2

    07:20:0- X City

    08:05:0- A Vil-

    PTVGROUP

    8.4.2.2 Open and closed blocks


    Block Inde- Blockin- Block
    no.
    x
    g day
    item
    type

    Line Vehicl- Start


    nam- e jour- time
    e
    ney

    e jour- 1
    ney
    0

    FromStopPoi- End
    nt name
    time

    ToStop
    Point
    name

    lage

    08:05:0- A Village
    0

    08:15:0- A Vil0
    lage

    Layover

    Vehicl- BUS- 21
    e jour- 2
    ney

    08:15:0- A Village
    0

    08:36:0- X City
    0

    Layover

    08:36:0- X City
    0

    08:50:0- X City
    0

    Vehicl- BUS- 4
    e jour- 1
    ney

    08:50:0- X City
    0

    09:35:0- A Vil0
    lage

    10

    Layover

    09:35:0- A Village
    0

    00:00:0- A Vil0 am.


    lage

    Table 219: Block items of the line blocks in block version 3


    8.4.2.2

    Open and closed blocks


    Independent of the selected calendar type, open and closed blocks can be generated. Open
    blocks start on the first day of the line blocking time interval (or later) and end by the latest on
    the last day. For closed blocks, the last day is again followed by the first day of the line
    blocking time interval, so that each end of a sequence of block items is connected with a start.
    This ring closure is analog to timetable-based PuT assignment and is used to include the
    costs for creating the initial situation into the model. The creation of closed blocks assures that
    the created line block schedule "in perpetuo" can be traversed. The following example with an
    extremely unsymmetrical timetable makes this clear.

    PTVGROUP

    565

    8.4.2.2 Open and closed blocks

    Illustration 180: Unsymmetrical timetable with trips beyond 24 hours


    If open blocks are created in this example, then one vehicle is sufficient, because the trip from
    A Village to X City plus the empty trip in the opposing direction will require 66 minutes and the
    departure of this cycle in A village is every 2 hours. The vehicle can therefore reach the starting point before the start of the next trip.
    When creating closed blocks however, two vehicles are required. The reason for this lies in
    the last trip, which is scheduled for 26:05 and thus still belongs to the previous day. Only one
    hour lies between the departure of this vehicle journey and the subsequent first trip on next
    day, so that the vehicle cannot return to the starting point in the meantime. When creating
    open blocks, this transition to the following day is not regarded, which may result in underestimating the vehicle demand.
    Apart from the pure vehicle demand, the open block solution of course has one empty trip less.
    If costs are evaluated for empty trips, this solution also simulates a less expensive situation. In
    each case it has to be decided, whether the empty trip which is required to form the ring closure has to be included in the model or not.
    Note: Open blocks can be created, if the model represents the planning situation for a certain single day or period. If the line blocking time interval however, represents a longer
    cycle which is to be repeated (for example a standard day), closed blocks should be created, to correctly determine the costs for restoring the initial state in the model.

    566

    PTVGROUP

    8.4.2.2 Open and closed blocks


    Block
    no.

    Block version
    code

    Number
    of
    blocking
    days

    Block clo- Mean operating Mean operating


    sed
    time
    km

    OpenBlocks

    12h 51min

    616

    Self-Con2
    1
    6h 36min
    321
    tainedBlocks
    Table 220: Open block and closed block for the unsymmetrical example (illustration 180)

    Bloc- Index Blockin- Block item


    k no.
    g day
    type

    Line Vehicl- Start


    nam- e jour- time
    e
    ney
    no.

    FromSto- End
    p
    time
    Point
    name

    ToStop
    Point
    name

    Vehicle jour- BUS- 16


    ney
    1

    03:05:00 A Village 03:50:00 X City


    a.m.
    a.m.

    Empty trip

    03:50:00 X City
    a.m.

    Layover

    04:11:00 A Village 05:05:00 A Vila.m.


    a.m.
    lage

    Vehicle jour- BUS- 18


    ney
    1

    05:05:00 A Village 05:50:00 X City


    a.m.
    a.m.

    Empty trip

    05:50:00 X City
    a.m.

    Layover

    06:11:00 A Village 07:05:00 A Vila.m.


    a.m.
    lage

    ...

    ...

    ...

    ...

    ...

    ...

    31

    Vehicle jour- BUS- 36


    ney
    1

    11:05:00 A Village 11:50:00 X City


    p.m.
    p.m.

    32

    Empty trip

    11:50:00 X City
    p.m.

    33

    Layover

    00:11:00 A Village 02:05:00 A Vila.m.


    a.m.
    lage

    34

    Vehicle jour- BUS- 37


    ney
    1

    02:05:0- A Village 02:50:0- X City


    0 a.m.
    0 a.m.

    Layover

    00:11:0- A Village 02:05:0- A Vil0 a.m.


    0 a.m.
    lage

    Vehicle jour- BUS- 37


    ney
    1

    02:05:0- A Village 02:50:0- X City


    0 a.m.
    0 a.m.

    Empty trip

    02:50:0- X City
    0 a.m.

    PTVGROUP

    ...

    ...

    04:11:00 A Vila.m.
    lage

    06:11:00 A Vila.m.
    lage

    ...

    ...

    00:11:00 A Vila.m.
    lage

    03:11:0- A Vil0 a.m.


    lage

    567

    8.4.3 Data model


    Bloc- Index Blockin- Block item
    k no.
    g day
    type

    Line Vehicl- Start


    nam- e jour- time
    e
    ney
    no.

    FromSto- End
    p
    time
    Point
    name

    ToStop
    Point
    name

    Layover

    03:11:0- A Village 00:00:0- A Vil0 a.m.


    0 a.m.
    lage

    Layover

    00:00:0- A Village 03:05:0- A Vil0 a.m.


    0 a.m.
    lage

    Vehicle jour- BUS- 16


    ney
    1

    03:05:0- A Village 03:50:0- X City


    0 a.m.
    0 a.m.

    Empty trip

    03:50:0- X City
    0 a.m.

    Layover

    04:11:0- A Village 05:05:0- A Vil0 a.m.


    0 a.m.
    lage

    Vehicle jour- BUS- 18


    ney
    1

    05:05:0- A Village 05:50:0- X City


    0 a.m.
    0 a.m.

    10

    Empty trip

    05:50:0- X City
    0 a.m.

    11

    Layover

    06:11:0- A Village 07:05:0- A Vil0 a.m.


    0 a.m.
    lage

    ...

    ...

    ...

    ...

    ...

    ...

    36

    Vehicle jour- BUS- 36


    ney
    1

    11:05:0- A Village 11:50:0- X City


    0 p.m.
    0 p.m.

    37

    Empty trip

    11:50:0- X City
    0 p.m.

    ...

    ...

    04:11:0- A Vil0 a.m.


    lage

    06:11:0- A Vil0 a.m.


    lage

    ...

    ...

    00:11:0- A Vil0 a.m.


    lage

    Table 221: Block items of both blocks in the example Block items in the recurring rhythm
    were omitted for a better overview. Block 1 is open, block 2 is closed.

    8.4.3

    Data model
    This section describes the data for the following key points:
    Block version
    Block
    Block item and block item type
    Attributes of the line blocking cost function
    Downtimes at depots and stop points
    Line block check
    Coverage check

    8.4.3.1

    568

    Block version
    In Visum multiple line blocking results can be stored in parallel. These are stored in so-called
    block versions. In this way, alternative plans with different parameter settings can be

    PTVGROUP

    8.4.3.1 Block version


    compared easily to one another. For example, a block version where interlining is allowed and
    another one where this is not allowed, can be maintained in the model. Procedures such as
    the calculation of PuT operating indicators always refer to the current active block version.
    Important parameters of the Line blocking procedure are attributes of a block version, so that
    the parameter settings are still known afterwards, and especially the check line block can use
    them for comparisons with the same parameters after changes. The block version attributes
    are described in table 222.
    Attribute

    Description

    Start day index

    First day of the line blocking time interval. The line blocking
    time interval has to lie inside of the calendar period.

    End day index

    Last day of the line blocking time interval.

    Valid from

    Date of the start day, if a calendar is used.

    Valid to

    Date of the end day, if a calendar is used.

    Interlining permissible

    Specifies, whether the line blocking and check line block procedures should create empty trips (see "Line block check" on
    page 582).

    System routes application Specifies, whether system routes should be used for generating empty trips.
    Only use active system
    routes

    Specify, if only active system routes or all system routes should


    be used to create empty trips.

    Regard preparation times Specifies, whether pre- and post-preparation times should be
    considered for line blocking and check line block.
    Short turn permitted

    Specifies, whether short turns should be permitted for line


    blocking and check line block. This means that the layover
    time is allowed to differ from the pre- and post-preparation
    times. The short turn properties are set in the attributes for the
    maximum dwell time, the reduced pre-preparation time and the
    reduced post-preparation time.

    Attribute for maximum


    dwell time

    Specifies the stop point attribute, where the values of the maximum dwell time is contained.

    Attribute for pre short turn

    Specifies the vehicle journey section attribute, where the


    values of the reduced pre-preparation time is contained.

    Attribute for post short turn Specifies the vehicle journey section attribute, where the
    values of the reduced post-preparation time is contained.
    Link attribute for shortest
    path

    Specifies the link attribute, which is used as a criterion for the


    shortest path search for empty trips.

    Total vehicle demand

    Number of required instances of vehicle combinations for all


    blocks of the block version

    Vehicle demand (per


    vehicle combination)

    Number of required instances of a certain vehicle combination


    for all blocks of the block version

    PTVGROUP

    569

    8.4.3.2 Block
    Attribute

    Description

    Required vehicles for stan- Number of required instances of the vehicle combination "no
    dard vehicle combination vehicle combination". If no vehicle combination is specified at
    the vehicle journey section, this specification is evaluated as
    an own vehicle combination, whose required vehicle is
    accounted for by this attribute.
    Vehicle unit requirement
    (per vehicle unit)

    Number of required instances of a certain vehicle unit for all


    blocks of the block version

    Table 222: Block version attributes


    8.4.3.2

    Block
    A block means, constant application of Nvehicles throughout the entire line blocking time interval. N is the number of blocking days. It does neither depend on the line blocking time interval
    nor on the length of the calendar. The attribute Number of blocking days reflects the vehicle
    demand which arises for a block. In illustration 181 , a train travels from Hamburg to Vienna on
    blocking day1. On blocking day2 the same train is not available again to travel the same
    route, but has to travel in the opposite direction from Vienna to Hamburg first. It is therefore
    necessary to implement a second train, thus the vehicle demand is two vehicles.

    Illustration 181: Blocking days and vehicle demand


    A block possesses the attributes described in table 223.

    570

    Attribute

    Description

    Block version ID / code

    Reference to the block version, which the block belongs to.

    Vehicle combination
    number

    Vehicle combination which is used to run a block. A block can be


    run by only one vehicle combination, but possibly by several
    exemplars of this type.

    Number of blocking
    days

    Specifies, how many (similar) vehicle combinations are being


    used simultaneously for this block, how high therefore the
    vehicle demand is for the block. Closed blocks have arrived back
    at the starting position after this number of days.

    Closed

    Specifies, whether the block was generated for a closed time


    axis, if therefore after the last day of the line blocking time interval, the first day will follow analogously to the assignment.

    PTVGROUP

    8.4.3.2 Block
    Attribute

    Description

    Depot number

    Refers to a stop point, which is used as a depot for this block.

    Empty trip transport sys- Specifies which transport system should be used within check
    tem code
    line block when calculating the empty trip. The value is applied
    from the procedure parameters for line blocking. It can also be
    inserted directly for manual planning.
    Not checked

    Specifies, whether the block was checked (0) or not (1).

    Has vehicle fault

    Specifies, whether an incorrect vehicle was used in the block


    (see "Line block check" on page 582).

    Has layover time fault

    Specifies, whether pre- and post-preparation times were exceeded (see "Line block check" on page 582).

    Has blocking day fault

    Specifies, whether a blocking day without block items exists (see


    "Line block check" on page 582).

    Has time fault

    Specifies, whether a time fault exists (see "Line block check" on


    page 582).

    Has location fault

    Specifies, whether a location fault exists (see "Line block check"


    on page 582).

    Has limit fault

    Specifies, whether one of the thresholds for the length or the


    threshold for the duration of a user-defined block item was exceeded (see "Line block check" on page 582).

    Has forced chaining


    errors

    Specifies, whether a valid forced chaining which was not adhered to, exists (see "Line block check" on page 582).

    Has running direction


    fault

    Specifies, whether a running direction fault exists (see "Line


    block check" on page 582).

    Has vehicle interchange

    Specifies, whether the block was created with or without vehicle


    interchange, if therefore the vehicle combination has to be compared against the vehicle journey section attribute vehicle combination or against the attribute vehicle combination set.

    Regard running direction

    Specifies, whether the running direction is relevant for the check


    of this line block. Otherwise, the line block check cannot detect a
    running direction fault. If the running direction is not relevant
    (buses, for example), this portion of the line block check can be
    disabled via this option (see "Line block check" on page 582).

    From stop point number Specifies at which stop point the block starts. For closed blocks,
    and name
    this complies with the To stop point.
    To stop point number
    and name

    Specifies at which stop point the block ends. For closed blocks,
    this complies with the From stop point.

    Start day index

    Starting day index of the block referring to the line blocking time
    interval of the block version. For closed blocks, the value is
    always 1.

    PTVGROUP

    571

    8.4.3.2 Block
    Attribute

    Description

    Start time

    Start time of the block, therefore start time of the first block item.
    For closed blocks this is usually midnight, unless a vehicle journey block item exceeds 24 hours on the last day.

    End day index

    Ending day index of the block referring to the line blocking time
    interval of the block version. For closed blocks, the value is
    always equal to the number of days in the line blocking time interval.

    End time

    Ending time of the block, therefore end time of the last block item.
    For closed blocks this is usually midnight, unless a vehicle journey block item exceeds 24 hours on the last day.

    Empty trip time

    Cumulative time, which is accumulated by empty trips and userdefined block item types of the block.

    Empty time

    Cumulative time, which is accumulated by layovers and layover


    times, as well as by empty trips and user-defined block item
    types of the block.

    Mean empty time

    Empty time / (Number of blocking days Number of line blocking time


    interval days)

    Mean empty trip time

    Empty trip time / (Number of blocking days Number of line blocking


    time interval days)

    Empty kilometers /
    miles

    Cumulative distance, which is covered by empty trips and userdefined block item types of the block.

    Mean empty kilometers Empty kilometers / (Number of blocking days Number of line blocking
    / miles
    time interval days)

    572

    Out-of-depot time

    Cumulative time, which is accumulated by block items of a block.


    Layovers are not taken into consideration.

    Mean operating time

    Mean operating time per blocking day and calendar day (cumulative operating time divided by the number of blocking days and
    the number of days of the line blocking time interval).

    Operating kilometers /
    miles

    Summed up distances covered by all block items of a block.

    Mean operating kilometers / miles

    Operating kilometers / (Number of blocking days Number of line


    blocking time interval days)

    Service time

    Sum of run times of the vehicle journeys of a block.

    Mean service time

    Service time / (Number of blocking days Number of line blocking time


    interval days)

    Time outside depot

    Block time minus time in depot

    Mean time outside


    depot

    Time outside depot / (Number of blocking days Number of line blocking


    time interval days)

    Service kilometers /

    Sum of the length of all vehicle journey block items of a block.

    PTVGROUP

    8.4.3.3 Block item and block item type


    Attribute

    Description

    miles
    Mean service kilometers / miles

    Service kilometers / (Number of blocking days Number of line blocking


    time interval days)

    Block time

    Total block time.


    Number of days in the line blocking time interval Number of blocking
    days

    Number of lines

    Number of lines, which are used by the block.

    Number of line routes

    Number of line routes, which are used by the block.

    Number of time profiles Number of time profiles, which are used by the block.
    Number of service trips

    Number of vehicle journey block times, which are run by the


    block.

    Cost distance

    Kilometer costs of the block, which result from the traversed service and empty kilometers (illustration 200).

    Cost vehicle

    Vehicle costs, which result from the number of required vehicles


    and the fixed costs for a vehicle unit (illustration 200).

    Cost vehicle referring to Cost vehicle projected to the line blocking time interval
    the line blocking time
    interval
    Cost Time

    Hourly costs, which result from the time required for vehicle journeys and empty trips.

    Cost time with layover

    Hourly block costs which arise from the vehicle journeys and
    empty trips, as well as from downtimes within or outside of a
    depot accumulated time periods.

    Leading depot number

    Depot with the longest dwell time. For ambiguity, the depot with
    the smallest number.

    Table 223: Block attributes


    8.4.3.3

    Block item and block item type


    Each block is made up of individual sections, which are called block items. Each block item
    has a start and an end, and a start stop and an end stop. The table 224 shows the attributes of
    a block item and their meanings.
    Attribute

    Description

    Blocking day

    Specifies, to which blocking day the block item has been assigned.

    Block item type num- Number and name of the block item type of the block item. By
    ber / name
    default, the four block item types vehicle journey, empty trip, layover time and depot are defined.
    Line name

    PTVGROUP

    Line which is run by this block item. The attribute only displays a
    value, if the block item is a vehicle journey.

    573

    8.4.3.3 Block item and block item type


    Attribute

    Description

    Line route name

    Line route which is traversed by this block item. The attribute only
    displays a value, if the block item is a vehicle journey.

    Direction code

    Direction of the line route which is traversed by this block item. The
    attribute only displays a value, if the block item is a vehicle journey.

    Time profile name

    Time profile which is used by this block item. The attribute only displays a value, if the block item is a vehicle journey.

    Vehicle journey num- Vehicle journey which is run by this block item. The attribute only
    ber
    displays a value, if the block item is a vehicle journey.
    Vehicle journey section number

    Vehicle journey section which is traversed by this block item. The


    attribute only displays a value, if the block item is a vehicle journey.

    Start day index

    Specifies the calendar day for the start of the block item referring to
    the start day of the line blocking time interval (attribute start day
    index of the block version).

    Start time

    Start of the block item

    End day index

    Specifies the calendar day for the end of the block item referring to
    the start day of the line blocking time interval (attribute start day
    index of the block version).

    End time

    End of the block item

    From stop point num- Stop point where the block item starts. Complies with To stop point,
    ber / name
    if it is a block item of type layover or layover time.
    To stop point number Stop point where the block item ends. Complies with From stop
    / name
    point, if it is a block item of type layover or layover time.
    Duration

    Time period of the block item. For block items with a user-defined
    block item type (for example maintenance) this duration can be edited manually.

    Length

    Distance of the block item. For block items with a user-defined


    block item type and block items of type empty trip, you can edit the
    length manually.

    Is in depot

    Indicates a downtime (item of type layover) as taking place in


    depot. Has no effect for other block items.

    Length until next


    occurrence

    Distance until a block item of the same type appears in this block
    again. Only available for block items of a user-defined block item
    type.

    Time until next occur- Period until a block item of the same type appears in this block
    rence
    again. Only available for block items of a user-defined block item
    type.

    574

    Departure minute

    Only the minute value of the attribute start time is displayed (for
    example, start time: 07:20:00, departure minute: 20).

    Arrival minute

    Only the minute value of the attribute end time is displayed (for

    PTVGROUP

    8.4.3.4 Attributes of the line blocking cost function


    Attribute

    Description

    Chain number

    Number of the chain. A chain represents a complete run through


    the block, throughout the entire line blocking time interval. There
    are as many chains as blocking days, and the N-th chain starts on
    the first day of the line blocking time interval on blocking day N.

    Starts in forward
    direction

    Specifies whether the activity starts in forward direction or in


    reverse direction. The attribute is set during the line block check, if
    the running direction of the line block is taken into account.

    Is change of running
    direction

    Specifies whether the activity which is described by this line block


    item includes a change of the running direction. Is only regarded
    for user-defined line block items.

    example, end time: 07:20:00, arrival minute: 20).

    Table 224: Block item attributes


    Each block item is of a certain type (block item type). By default, there are the block item types
    vehicle journey, empty trip, stand (layover/depot) and layover time in Visum. You can also
    create user-defined types and manually integrate them into your blocks (for example, maintenance or washing vehicles). The table 225 shows the attributes of block item types.
    Attribute

    Description

    Created by the
    system

    Specifies, whether the block item is user-defined.

    Default duration

    Default value for the time period of block items of this type (default setting when creating such a block item).

    Default length

    Default value for the length of block items of this type (default setting
    when creating such a block item).

    Time limit

    Maximum value for the duration between two block items of this type. If
    a value >0 is specified here, the time elapsed between the occurrence
    two items of this type may not exceed this threshold. If this is not the
    case, the line block check will return a limit fault (see "Line block
    check" on page 582).

    Length limit

    Maximum value for the distance being traversed by a block between


    two block items of this type. If a value >0 is specified here, the distance
    traversed between the occurrence two items of this type may not
    exceed this threshold. If this is not the case, the line block check will
    return a limit fault (see "Line block check" on page 582).

    Table 225: Block item type attributes


    8.4.3.4

    Attributes of the line blocking cost function


    To find the optimum line block, a cost function is minimized during line blocking (see "Line
    blocking description without vehicle interchange" on page 585). This cost function accounts for
    the attributes found in table 226.

    PTVGROUP

    575

    8.4.3.4 Attributes of the line blocking cost function


    Note: Up to and including Visum 10 the different cost rates at vehicle units and vehicle
    combinations were not used in line blocking. Because of this, existing networks do not
    contain this data. For the new line blocking model this means that for each activity costs =
    0 accumulate, independent of prefactors. This thus leads to an unnecessary use of vehicles and empty trips. When changing from the old model, make sure that - at least for
    vehicle costs and empty trips - positive costs rates are set.
    Attribute

    Object

    Vehicle requirement

    Activity in the block Total number of vehicles required for the block
    (= vehicle journey,
    version.
    layover in depot,
    layover at stop point,
    pre and post preparation time, empty
    trip)

    Cost Rate Vehicle


    Unit Total

    Vehicle combination Total cost which accumulates for all vehicle


    units of the vehicle combination for each
    instance of the vehicle combination. The cost
    rate referring to the AP is projected to the duration of the line blocking time interval.

    Service time

    Activity

    Cost Rate Service


    Hour Total

    Vehicle combination Costs which accumulate for a service hour of


    the vehicle combination.

    Service kilometers Activity

    576

    Description

    Service time which accumulates during the activity.

    Service kilometers which accumulate during the


    activity.

    Cost Rate Service


    km / mi Total

    Vehicle combination Costs which accumulate for a mileaged service


    kilometer/mile of the vehicle combination.

    Empty time

    Activity

    Cost Rate Empty


    Hour Total

    Vehicle combination Costs which accumulate for an empty hour of


    the vehicle combination.

    Empty kilometers

    Activity

    Cost Rate Empty


    km / mi Total

    Vehicle combination Costs which accumulate for a mileaged empty


    kilometer of the vehicle combination.

    Number of empty
    trips

    Activity

    1 = activity is an empty trip, otherwise = 0.

    Layovers

    Activity

    Layover at stop points which are no depots for


    the vehicle combination, accumulating during
    the activity.

    Cost Rate Hour

    Vehicle combination Costs which accumulate for a layover hour of

    Empty time which accumulates during the activity.

    Empty kilometers which accumulate during the


    activity.

    PTVGROUP

    8.4.3.5 Downtimes at depots and stop points


    Attribute

    Object

    Description

    Layover total

    the vehicle combination at a stop point, which is


    not a depot for the vehicle combination.

    Layover in Depot

    Activity

    Layover in depots of the vehicle combination,


    which accumulates during the activity.

    Cost Rate Depot


    Hour Total

    Vehicle combination Costs which accumulate for a layover hour of


    the vehicle combination in a depot.

    Table 226: Attributes of the line blocking cost function


    8.4.3.5

    Downtimes at depots and stop points


    At stop points you can specify for each vehicle combination, whether the stop point should be
    used as a depot by the vehicle combination. A capacity and a minimum downtime time can be
    specified for each vehicle combination. The capacity is restricted to the number of vehicle combinations, which are allowed to stop at the same time at the stop point (as a depot), as long as
    the capacity > 0; for capacity = 0 the depot capacity is unlimited. Depots are therefore stop
    points with downtime function. The downtime in the depot is evaluated with a cost rate that is
    different (usually lower) from the cost rate for the downtime at a stop point, though both downtimes belong to the block item type layover. A difference is made between the same stop
    point in its role as a depot and as a stop point.
    Attribute

    Description

    Is Depot

    Specifies that the stop point is a depot. A stop point is a depot,


    if either at least one vehicle combination is permissible or the
    entry Default values is permissible.

    Is depot for default vehicle Specifies whether the entry Default values (No combination =
    combination
    Not vehicle combination specific) is permissible.
    Minimum Depot Layover

    Minimum downtime per vehicle combination in the depot.

    Minimum layover in the


    depot for the default
    vehicle combination

    Minimum downtime in the depot for default vehicle combination (entry Default values).

    Depot Capacity

    Capacity per permissible vehicle combination. This is the number of vehicles per combination, which is allowed to simultaneously be at the depot. For the value = 0 the capacity is not
    limited for the respective vehicle combination.

    Depot capacity for standard vehicle combination

    Capacity for the vehicle combination no combination (entry


    Default values). For the value = 0 the capacity is not limited for
    the standard vehicle combination.
    Table 227: Depot attributes of stop points

    PTVGROUP

    577

    8.4.3.6 Empty trips


    Cost Rate Depot Hour

    Cost rate for downtimes at depots

    Cost Rate Layover Hour Cost rate for downtimes at stop points, not at depots
    Table 228: Cost rates for downtimes at depots and stop points based on vehicle unit (cost
    rates as listed in table 226)

    Cost Rate Layover Hour

    Cost rate for downtimes at stop points, not at depots

    Cost Rate Layover Hour


    Units

    Sum of cost rates of the vehicle units for downtimes at stop


    points

    Cost Rate Layover Hour


    Total

    Total cost rate for downtimes at stop points (= cost rate per
    layover hour + cost rate per layover hour from vehicle units)

    Cost Rate Depot Hour

    Cost rate for downtimes at depots

    Cost Rate Depot Hour


    Units

    Sum of cost rates of the vehicle units for downtimes at depots

    Cost Rate Depot Hour


    Total

    Total cost rate for downtimes at depots (= cost rate per depot
    hour + cost rate per depot hour from vehicle units)

    Table 229: Cost rates for downtimes at depots and stop points based on vehicle combination
    (cost rates as listed in table 226)
    8.4.3.6

    Empty trips
    Empty trips are used for interlining a vehicle, if the end stop point of the vehicle journey section
    to be carried out, does not correspond with the start stop point of the vehicle journey section following in the block. The generation of empty trips is carried out according to the same principles, in the check line block and in both procedures of line blocking, and has direct effect on
    the data model.
    The generation of empty trips via the attribute Create empty trips can basically be deactivated at the block version. Line blockings for this block version, as well as the check line
    block for line blocks in this block version, can therefore not calculate empty trips. If end and
    start stop point of consecutive block items do not correspond with each other, this is characterized as a location break.
    If the generation of empty trips is generally allowed, Visum tries calculating an empty trip to
    change of location. This is always carried out with regard to the empty trip transport system of
    the block. For the line block check, this is the specified empty trip transport system (input attribute). No blocks exist a priori for line blocking. Dependent on the parameter settings for each
    configuration (see "Partitioning" on page 585) of a block which could occur, an empty trip transport system is predefined and saved to the actual generated blocks. This ensures, that with a
    later check the same empty trip transport system is used.
    With the block version attribute Use system routes it can be specified further, how the empty
    trip calculation should be carried out:
    Do not use system routes
    Empty trips are generated through shortest path search for the empty trip transport system
    in the network. The shortest paths in terms of distance or run time (t_PuTSys) are

    578

    PTVGROUP

    8.4.3.7 Regard running direction


    calculated, for example.
    Use system routes
    If there is a system route for the empty trip transport system, from the origin to the destination point, the lengths and run time are applied as values for the empty trip. If there are
    vehicle combination-specific run times, these have priority. The empty trip block item
    being generated has a relation to the system route used. System routes are not used transitive. If there is no suitable system route, a shortest path search is carried out in the network.
    Use system routes exclusively
    The possible empty trips are solely described through system routes, a shortest path
    search is not carried out. If there is no suitable system route for an OD pair, interlining is
    not possible.
    Create system routes, if required
    Actually, the computation rules for the 'Use system routes' option apply. If no matching system route can be found for an empty trip, the successful shortest path search will create a
    new system route for this pair of stop points. The empty trip will use this information. The
    resulting 'empty trip' block item has a relation to the generated system route.
    With the selection of the suitable option, the generated empty trips can be controlled in detail.
    8.4.3.7

    Regard running direction


    In many cases, the running direction of a vehicle carrying out a vehicle journey does not have
    to be regarded separately. This is the case if all vehicle journeys are carried out in the 'ahead'
    mode (one-way vehicle, especially all buses and some trams) or if the running direction is irrelevant (railcar operation in rapid transit). Anyhow, in some cases it is requested, that the running direction of the vehicle combination is always the same, for example, because the station
    wagon of a train is expected to stop at a fixed position at the platform or because the vehicle
    dynamics of push-pull trains depends on the running direction.
    Thus it is optionally possible to take the running direction into account for line block checks
    and manual line blocking Visum. For this purpose, for each turn in the network it has to be specified if this turn means a change of the running direction. Useful data can be provided by turn
    standards (see "Nodes and turns" on page 50) based of turn types.
    Thus, each movement in the network inherits information on running direction changes. Along
    a line route which means in the course of a vehicle journey a running direction change occurs
    especially where a turn with the property Is change of running direction is traversed. If a line
    block takes the running direction into account (attribute Regard running direction), these changes of the running direction will be visualized in the line block display.

    PTVGROUP

    579

    8.4.3.7 Regard running direction

    Illustration 182: Display of a change of the running direction in the course of vehicle journey
    block items. The line route makes a U-turn in the station "TFS"
    Accordingly, the empty trip block items obtain information from the network whether running
    direction changes occur in their course. If the empty trip is based on a system route, the running direction changes are located in the same manner as for vehicle journeys and will similarly be visualized in the line block display. If there is no system route, then the route search
    determines whether an even or an odd number of direction changes appears; only this is relevant to line blocking. Thus, empty trip block items with an odd number of running direction
    changes are centre-subdivided in the view.
    For user-defined block items the information whether running direction changes are included
    is explicitly stored with the attribute Is change of running direction . Hence, also a rotary journey (U-turn or triangle-shaped) can explicitly be modeled as user-defined block item.
    If the running direction has to be regarded for a line block, the line block check will verify the
    item end - item start changeovers in the sequence of line block items and define the running
    direction at the beginning of the activity for each block item. A direction fault is recorded if a
    vehicle journey section is run in either direction by this line block on different calendar days.
    For a closed line block, a direction fault is additionally recorded if the running direction changes after the closed line block has been completed.
    The line blocking procedure cannot directly evaluate the change of running direction information. Thus it cannot intentionally generate line blocks without direction faults. In the line
    blocking procedure, the parameter Regard running direction works as follows:
    Regard running direction: Subsequently to the line blocking procedure, the line blocks are
    checked for direction faults. If applicable, the appropriate fault status is set.
    Do not regard running direction: For the line blocks, the attribute Regard running direction is set to 'false'.
    .

    580

    PTVGROUP

    8.4.3.8 Forced chainings


    Attribute

    Description

    Is change of running direction

    If attribute default values from the turn standard are allocated to a


    turn, the original turn attribute values will be replaced by the allocated standard values for the selected attributes. This makes the standard value allocation easier. To all turns of the U-turn type, for
    example, the property Is change of running direction can be allocated.
    Table 230: Turn standard attributes with reference to running directions

    Attribute

    Description

    Is change of running direction

    The value of this attribute indicates, whether traversing this turn


    means a change of the running direction. This applies to line routes
    and system routes as well as to the change of direction determination
    for empty trips during the line block check. Furthermore, this attribute
    is evaluated for the item end - item start changeovers in the
    sequence of line block items within a line block.
    Table 231: Turn attributes with reference to running directions

    Attribute

    Description

    Is change of running direction

    Is true, if the line route item is located at a node, where the line route
    course traverses a turn with the property Is change of running direction.
    Table 232: Line route attributes with reference to running directions
    8.4.3.8

    Forced chainings
    For line blocking it is determined from the start, which incoming trip has to be connected to
    which outgoing trip. Especially in rail services, such pre-connections are often produced due
    to the short time between the connected trips. The reason being, that changing the vehicle
    pool between arrival and departure is not possible. Desired through-connections between
    trips are a source for such forced connections.
    Forced chaining is a relation of a vehicle journey section to a follow-up vehicle journey section
    on a calendar day. Forced chaining means that this transfer in the line blocking result has to
    be adhered to. Line blocking therefore has to treat the thus connected vehicle journey sections
    (these can be transitive whole chains) like a sole performance. Forced chainings can be different for each calendar day. They therefore connect occurrences of vehicle journey sections.
    By definition a maximum of 24h to 1s. is allowed to lie between the arrival of the vehicle journey section and the departure of the successor. The calendar of the successor is therefore
    clearly determined by the arrival time, consequently by the calendar day of the origin vehicle
    journey section. Forced chaining is valid, if the origin vehicle journey section is even operating
    on the calendar day of the forced chaining, if in the described time interval, an occurrence of
    the destination vehicle journey section starts after the occurrence of the origin vehicle journey

    PTVGROUP

    581

    8.4.3.9 Line block check


    section, and if in addition the vehicle combinations of the origin vehicle journey section and
    the destination vehicle journey section coincide (block does not have vehicle interchange) or
    the respective vehicle combination sets have a non-empty intersection (block has vehicle interchange).
    Forced chainings are optionally considered in line blocking. In this case, as long as none of
    the following conditions applies, the generated blocks meet the predefined valid forced chainings:
    The same destination vehicle journey section was defined as a destination for the same
    calendar day in different forced chainings. The forced chaining first found is then taken,
    i.e. the one with the smaller key at the origin vehicle journey section.
    The end stop point of the origin vehicle journey section does not coincide with the start
    stop point of the destination vehicle journey section, and the time between is not enough
    for an empty trip or empty trips are not allowed to be generated. The block then has a forced chaining fault.
    The first case can be determined through a network checking function.
    If valid forced chaining applies, demands are neither made for line blocking nor for the check
    line block, to comply with (potentially reduced) pre- and postpreparation times. Entering a forced chaining has priority before a possible contradicting minimum layover time. The required
    time for an empty trip has to be met. Downtimes at depots are not allowed between forced chainings connected by vehicle journey block items.
    8.4.3.9

    Line block check


    In the previous Visum version of line blocking, the blocks always had to be correct, which
    means that they were not allowed to have time or location breaks. The result was, that the
    blocks were deleted when making important changes in the network (for example at vehicle
    journeys). This cannot be tolerated, especially when blocks were edited manually and therefore cannot simply be restored by carrying out line blocking again. In the block data model
    now available in Visum, the consistency of line blocks with the network is assured and in
    return the constant correctness of the block itself is no longer required. Instead, you have the
    possibility of performing a check line block to calculate the status which codes the information
    on consistency (called error flags below) for each block. These error flags provide you with
    information on whether the blocks are error free and if not, in which respect there are inconsistencies. All together there are eight error flags.
    The state model in illustration 183 shows the possible state transitions of a block and how the
    eight error flags are set.

    582

    PTVGROUP

    8.4.3.9 Line block check

    Illustration 183: State model for line blocks


    The blocks react if the network database changes. Changes to the block version, the block
    items and the vehicle journey sections are taken into consideration. Moreover, blocks react to
    changes made to the basic network settings, in particular to calendar settings.
    LocationFault
    Two successive trips in a block do not match, because the successive trip does not start at
    the same stop point where the preceding trip ends.
    TimeFault
    Two successive trips in a block overlap in time. This means, that the preceding trip arrives
    later than the successive trip departs.
    LayoverTimeFault
    Two successive trips overlap in time only if for arriving trips the post-preparation time and
    for departing trips the pre-preparation time is included in a block. This means, that the
    planned layover time is not sufficient. In practice such an error can be ignored sometimes,
    but has to be checked manually. If both trips are connected by forced chaining, adherence
    to the pre- and post preparation time is not checked for this transfer, because the forced
    chaining has priority.
    VehicleFault
    The block includes vehicle journey sections to which a vehicle combination was allocated
    that does not match the block. This error can occur for example, if line blocking has calculated a block for a standard bus and later on the user manually assigns a low-floor bus
    to one of the trip sections. The attribute Has vehicle interchange is used for the evaluation of this error. This decides whether the comparison regards either vehicle journey
    section attribute vehicle combination or vehicle combination set.
    EmptyDayFault
    This error is set, if there is an empty blocking day. This means, that there is a blocking day
    PTVGROUP

    583

    8.4.3.9 Line block check


    without a block item on any calendar day (except for layover items). In this case, an extra
    vehicle has unnecessarily been planned.
    LimitFault
    This error can only occur, if there are user-defined block items with time or length limit
    values >0. The length limit value thus specifies the length, which is allowed to be covered
    at a maximum, between two actions of this type within a block. The time limit value is analog for time periods. If one of the thresholds are exceed in the block, this is indicated by
    this error flag.
    ForcedChainingFault
    In the block there is a vehicle journey section which is the starting point of a valid forced
    chaining. The latter, however, is not implemented in the block. The vehicle journey section
    successor is therefore not the destination vehicle journey section of the forced relation.
    DirectionFault
    The line block includes a vehicle journey section which is serviced in the opposite direction on a different day, or the vehicle's direction of travel changes after a closed line block
    has been completed. The DirectionFault check is only performed, if the line block
    attributeRegard running direction is true.
    A block that contains the flag unchecked or time fault or location fault is not allowed to be regarded by subsequent evaluations (for example in the PuT operating indicators procedure). The
    other six flags however, do not restrict usability. This is necessary to be able to transfer plans
    from other systems and use them for line performance and line costing calculations in the procedure PuT operational indicators(see "PuT interlining matrix procedure" on page 604), which
    often contains such errors (partially deliberately).
    Common and forced line block check
    Between the network basis and blocks, two types of inconsistencies can occur through subsequent changes, which are not found in common checks of line blocks. To check consistency
    in all respects, you can optionally carry out the so-called forced check (see User Manual: Chpt.
    20.1.1.5 , page 2099). These are the two inconsistencies in detail:
    When using reduced layover times, it could occur that no error flag is displayed, although
    the block contains a layover time error (LayoverTimeFault). This is the case, if the value of
    one of the three attributes describing the reduced layover time was subsequently edited
    or the selection of one of these attributes changed. These user-definable attributes of stop
    points and vehicle journey sections are: reduced pre-preparation time, reduced post-preparation time and maximum dwell time. The reason for this being, that these three attributes can be specified dynamically by the user (in particular, also indirect or user-defined
    attributes can be used). Due to calculation times, it is not efficiently possible to react to
    changes in these attributes and to automatically set the error flag. That is why you have to
    carry out the forced version of the check line block, to make sure that all layover time
    undershoots (layover time fault) are determined in the checked blocks, if subsequent changes have been made. If no reduced layover times are used (block version property), this
    problem can not occur.
    Subsequent changes to the network do not cause automatic adjustments of potentially
    concerned empty trips (for example when changing PuT run times of links or when
    blocking links for a PuT transport system). Location and time faults can thus remain undiscovered. Also in this case, it is - for calculation time reasons - not possible, that line blocks
    584

    PTVGROUP

    8.4.3.10 Coverage check


    react to network changes. That is why only a forced check can assure that the blocks do
    not contain such errors, if the network used by empty trips has been changed subsequently.
    8.4.3.10

    8.4.4

    Coverage check
    A block version can be checked for whether it covers all vehicle journey sections in a given
    time frame (from day - to day, i.e. generally within the analysis period) (see User Manual: Chpt.
    20.1.1.4 , page 2098). If there is a vehicle journey section which is - for a calendar day - not
    bound by a vehicle journey in the block of the block version to be checked, the check has failed.

    Line blocking description without vehicle interchange


    The objective of the line blocking is to determine the number of required vehicles for a given
    timetable and simultaneously minimize the resulting costs. This section describes line
    blocking without vehicle interchange. Alternatively, you can calculate line blocking with
    vehicle interchange (see "Line blocking description with vehicle interchange" on page 595).
    The solution algorithm for the line blocking procedure is based on the formulation of a graph
    flow problem. The procedure includes the following steps.
    1. Decomposition of the problem into independent subproblems (partitioning)
    2. For each subproblem, construction of a graph, where line blocking is represented as a one
    good flow problem (graph construction)
    3. Determination of the minimum cost flow in the graph (solution of the flow problem)
    4. Decomposition of the flow in the graph into chains and aggregation to blocks (decomposition)

    8.4.4.1

    Partitioning
    Line blocking regards the vehicle journey sections of the model for planning, the generated
    blocks thus successively traverse vehicle journey sections. For planning, either all or all active
    vehicle journey sections, or - orthogonally thereto - either all sections or only those not yet
    being bound in the target block version can be regarded (see User Manual: Chpt. 20.1.3.2 ,
    page 2105). Prior to the graph construction, the problem is broken down into subproblems, socalled partitions, which are to be solved separately. A partition consists of all vehicle journey
    sections to which the same vehicle combination has been assigned. The decomposition into
    these subproblems is possible, because a block is always run by exactly one vehicle combination and there is therefore no vehicle change within the block. Also the vehicle journey
    sections which do not have a vehicle combination, together form a partition. For each partition,
    all further procedure steps are carried out separately. Thus, a separate graph is constructed
    and solved for each partition and each result will be decomposed into blocks.
    As an option, line blocking can be partitioned further according to operator, transport system,
    and line (see User Manual: Chpt. 20.1.3.2 , page 2105). If for example the same operator is
    required for the next vehicle journey, operators are partitioned additionally. In this case each
    partial problem and thus each resulting block only contains vehicle journey sections of a
    vehicle combination and of an operator. Operator changes can therefore not be made within a

    PTVGROUP

    585

    8.4.4.2 Construction of the graph


    block. Within the procedure, a separate graph is set up for each combination of vehicle combination and operator, and the other procedural steps are carried out for each of these graphs.
    The illustration 184 shows an example of partitioning. These are vehicle journey sections run
    by three vehicle combinations: articulated bus, standard bus, and tram. The articulated bus
    vehicle journey sections are run by operator 1 and 2, whereas the tram vehicle journey sections are run by operator 1 only. If line blocking is additionally partitioned according to operators, five graphs will be built, for which the flow problem has to be solved separately and the
    decomposition into blocks needs to be carried out separately.

    Illustration 184: Example for partitioning according to vehicle combination and operator
    Note: Capacity restrictions in depots can only be considered, if the graph is not partitioned further than by vehicle combination, if therefore none of the options Same operator for next vehicle journey, Same transport system for next vehicle journey or Same
    line for next vehicle journey has been selected. The reason for this being, that the capacities in depots are each defined per vehicle combination. If a more detailed partitioning
    is carried out for example according to operators, the procedure does not have the possibility of distributing the capacity, even further to the level Vehicle combination x Operator.
    8.4.4.2

    Construction of the graph


    These are the basic steps for constructing the graph:
    1. For each departure and arrival of a vehicle journey section (or a sequence of vehicle journey sections connected by forced chainings) insert a node and connect both nodes with an
    edge. Below, these nodes are called 'real events'. Departure and arrival in each case is the
    time including possible pre- and post-preparation times, if these are taken into consideration (see User Manual: Chpt. 20.1.3.2 , page 2105).

    586

    PTVGROUP

    8.4.4.2 Construction of the graph

    Illustration 185: Inserting the nodes and edges for vehicle journey sections
    2. For each permissible depot for the vehicle combination as well as for each stop point,
    which is the start of a vehicle journey section of the current partition (empty trips between
    stop points), enter an arrival event for the time of arrival and an edge for the empty trip from
    the departure event of the trip to the arrival event at the stop point or depot (so-called unreal
    or "fake" arrival events are thus created). Depots are thus special stop points. In the graph,
    the events at stop points and in depots are distinguished which means, that in the graph
    there is one node for the stop point and another one for the depot, although the depot is
    represented by the same stop point in the network.

    PTVGROUP

    587

    8.4.4.2 Construction of the graph

    Illustration 186: Inserting the edges for entering the depots and for empty trips between stop
    points
    3. Analogously, insert also a departure event and an edge from there to the departure event of
    the trip, however, only for each permissible depot, not for other stop points (these mean
    moving out of the depots, so-called fake departure events are created in this way).

    588

    PTVGROUP

    8.4.4.2 Construction of the graph

    Illustration 187: Inserting the edges for leaving from depots


    Note: If interlining is prohibited (see User Manual: Chpt. 20.1.3.2 , page 2105), only
    edges from and to that depot are inserted, which is represented by the same stop point in
    the network. Thus, interlining is not possible in this case, the vehicle combination can
    however, enter a depot and subsequently return to the same stop point for the start of the
    next trip.
    4. Insert an additional edge (the so-called Timeline or Waiting edge) between each pair of succeeding events of a stop point or depot. Using this edge, it is possible to model waiting
    (downtimes) at a stop point or in a depot. Timeline edges thus make it possible, that a block
    can be continued with a new trip at the same stop point.
    For line blocking you can select whether you want to create open or closed blocks. With the
    generation of closed blocks, each timeline, therefore each sequence of timeline edges for a
    stop point or a depot, generates a closed ring. Vehicle journey edges and empty trip edges
    can also cross the transition from the last to the first day of the blocking time interval. A
    block has as many blocking days as it makes "rounds" through the calendar period, until it
    has reached its starting point again.
    Only for open line blocking it can be claimed, that blocks start and end in depots. Connecting edges are then inserted before the first node and after the last node of a timeline, from
    an auxiliary node to all depots. Inflow and outflow only takes place via this auxiliary node.
    In this case it may occur, that no flow can be determined. This happens when the total capacity of all depots is smaller than the number of vehicles required to cover all actions. In such
    a case, line blocking is canceled with an error message.

    PTVGROUP

    589

    8.4.4.2 Construction of the graph


    Also in the introductory example (see "Open and closed blocks" on page 565) you can find
    a note concerning open and closed line blocks.
    5. The graph is now simplified, by combining nodes with the same accessibility and by deleting equivalent empty trip edges (which provide access to the same departure). The graph
    after the edge reduction can be seen in illustration 188.

    Illustration 188: Example graph after inserting the timeline edges and edge reduction
    6. For the formulation as a flow problem, it is necessary to define a lower capacity limit and an
    upper capacity limit to the edges (which is the number of vehicles which can maximally or
    minimally flow via an edge). The following applies:
    The lower limit of the capacity on the vehicle journey sections is 1 (because it is mandatory that each vehicle journey section is really traversed).
    All other edges have a lower capacity limit of 0 (because traversing is not mandatory,
    for example for empty trips).
    The upper limit for the vehicle journey section edges is also 1 (because each vehicle
    journey section should only be traversed exactly no more than once).
    Empty trip edges as an upper limit have the number of empty trips, which they represent (this is only greater than 1, if in the framework of edge reduction, edges were combined).
    Edges along the timelines, if we are talking about a depot, use the depot capacity as
    upper limit. For all other timelines the upper limit is not restricted.
    7. To be able to determine a cost-efficient flow, the edges with costs have to be evaluated in
    the last step. These are described by a cost function analog to the perceived journey time
    for PuT assignments (see "Perceived journey time" on page 502). This cost function is

    590

    PTVGROUP

    8.4.4.2 Construction of the graph


    made up of summands, which each multiply one property of the edge (therefore the activity
    described by the edges) by a factor and a cost rate. The cost function is as follows:
    Cost

    = Required vehicles Coefficient Cost rate vehicle unit total


    + Service time Coefficient Cost rate hour service
    + ServiceKm/Mi Coefficient Cost rate Km/Mi service
    + Space Coefficient Cost rate hour empty
    + EmptyKm/Mi Coefficient Cost rate Km/Mi empty
    + Number of empty trips Coefficient
    + Layover Coefficient Cost rate hour layover
    + Service time depot Coefficient Cost rate hour depot

    Note: The coefficients also have an effect on the cost rate for "no vehicle combination".
    Which cost components have an effect on an edge, depends on the edge type. The cost components for the individual edge types are the following.
    Vehicle journey edges
    Service time describes the duration of the vehicle journey section (The costs for the trip
    itself are irrelevant for solving the problem, because each edge is allocated with
    exactly one flow of 1 and there is thus no alternative allocation. To display the result,
    vehicle journey edges are still evaluated with the vehicle journey cost rates of the
    vehicle combination for duration and distance.)
    ServiceKm/Mi describes the distance covered by the vehicle journey
    Layover describes the duration between the FromNode's point in time and the departure from the FromNode plus the duration between the arrival at the ToNode and ToNode's point in time.
    Empty trip edges
    Empty time describes the duration of the empty trip
    EmptyKm/Mi describes the distance covered by the empty trip
    Layover describes the duration between the FromNode's point in time and the departure from the FromNode plus the duration between the arrival at the ToNode and the
    ToNode's point in time, in case it is a normal stop point
    Depot layover describes the duration between the FromNode's point in time and the
    departure from the FromNode plus the duration between the arrival at the ToNode and
    the ToNode's point in time, in case it is a depot
    Timeline edges
    Layover and layover depot describe the length of the time period between the points in
    time of the nodes which are connected via the edge
    To evaluate the vehicle demand, for each edge which traverses a selected point in time,
    the cost rate for the vehicle combination is added to the evaluation. Because each vehicle
    combination has to traverse this evaluation point in time exactly once, the vehicle demand
    is thus counted and evaluated.
    PTVGROUP

    591

    8.4.4.3 Flow problem solution


    As an interim result, an evaluated graph is available, for which a flow with minimum costs is
    determined in the following step.
    8.4.4.3

    Flow problem solution


    With the graph constructed above including the evaluation, the cost minimum flow is now determined. The target cost function can thus be parameterized as described in the previous procedure step. The user can thus especially control modeling of the basic conflict between
    minimizing empty trips and minimizing vehicle demand, which is described in the introduction.
    The illustration 189 schematically shows such a cost minimum flow, where multiple flow units
    (vehicle combinations) are indicated on an edge with lines piled on top of each other. To make
    it easier, neither costs nor capacities are noted here. The illustration however shows, that all
    vehicle journey sections are traversed by exactly one vehicle combination. The graph also
    shows, which empty trips even have to be traversed at a minimum cost flow (i.e. all edges crossed by the flow). Altogether there are two empty trips one from C to A and one from B to C.
    The evaluation line cuts three edges, that is why the vehicle demand is 3.

    Illustration 189: Optimal cost flow in the example graph


    As a result of this step, a cost-efficient flow exists, the vehicle demand is known and which are
    the necessary empty trips. Not known yet however, are the blocks themselves, therefore at
    which stop points blocks start and end, and the routes of the blocks in the optimal flow.
    8.4.4.4

    592

    Decomposition of the flow into blocks


    The cost-efficient flow in the graph from the previous step can be displayed as blocks in different ways. Regarding the costs, each of these solutions is of equal quality and thus optimal.

    PTVGROUP

    8.4.4.4 Decomposition of the flow into blocks


    The decomposition step has to break up the flow into chains in the graph, by allocating an outgoing flow unit at each node. Each generated chain thus corresponds to one block. The illustration 190 and the illustration 191 show two possible examples, how the cost-efficient flow
    can be decomposed into blocks.

    Illustration 190: Example 1 for the decomposition into blocks

    PTVGROUP

    593

    8.4.4.4 Decomposition of the flow into blocks

    Illustration 191: Example 2 for the decomposition into blocks


    This independent optimization problem can be resolved according to different criteria. In
    Visum there are two criteria, which can also be combined with each other:
    The structure of the changeovers between vehicle journey sections in the block can be
    influenced by the following options:
    Differentiated duration of standstills: The distribution of the standstill times is as irregular as possible, in other words, there are more short and long standstills than average standstill times. The aim of this is to obtain long standstills which can be used as
    maintenance time slots.
    Even duration of standstills: The distribution of the standstill times is as even as possible. Such blocks are exceptionally resistant to disturbances.
    Line purity: It is attempted to only run trips of the same line in a block or at least avoid
    line changes within a block as often as possible.
    No specific requirements: In this dimension, no requirements are set concerning the
    result.
    Even blocks: For assignment periods of more than one day, the program aims at calculating line blocks that look as similar as possible for all calendar days.
    If closed blocks are generated, the duration of the blocks can also be influenced with the
    options
    Preferably, build long blocks: Blocks have as many blocking days as possible. This
    means that the single vehicles traverse multiple line paths. In the most extreme case,
    all vehicle journeys of a partition are covered by a single line block.
    Preferably, build short blocks: Blocks have as few blocking days as possible.
    594

    PTVGROUP

    8.4.5 Line blocking description with vehicle interchange


    No specific requirements: In this dimension, no requirements are set concerning the
    result.

    8.4.5

    Line blocking description with vehicle interchange


    Line blocking with vehicle interchange differs from that without vehicle interchange, in that the
    vehicle combination to be used is not strictly defined for each vehicle journey section. In fact,
    the procedure has the possibility of selecting the best vehicle combination specified in the attribute vehicle combination set. Different criteria are possible, which can be weighted against
    each other in a subordinate objective function:
    Selection according to costs: Different costs are involved with the selection of a vehicle
    combination, which flow into the objective function.
    Selection according to capacity: For the selection, a comparison between the trip volume
    (Assignment results or count data) can be carried out on the one hand and the (seat) capacity of the vehicle combination on the other hand. Not the covered demand provided by
    the capacity, is included in the objective function.
    Selection according to availability: The number of available vehicles can be predefined
    on the unit level. The selection is made, so that this restriction is adhered to. The number
    of vehicles used in addition to the ones available are included into the objective function.
    Line blocking with vehicle interchange thus goes beyond the application area of line blocking
    without vehicle interchange (see "Line blocking description without vehicle interchange" on
    page 585) and also covers the following application areas.
    Planning the vehicle use depending on the demand, at the same time considering blockrelated restrictions.
    Reduction of the calculated vehicle requirement by making the vehicle use more flexible,
    with the (possibility of) replacing a vehicle combination with another, for example because
    of technical restrictions.
    Consideration of different vehicle combination-specific minimum layover times
    The procedure is based on the line blocking without vehicle interchange and integrates this as
    a procedural step into its entire process. Compared to this one it is not about an analytical procedure, but an iterative search procedure which in general finds very good solutions, but
    never an optimal one regarding the objective function.
    As another distinctive feature, several complete and equal solutions of the given line blocking
    task (parameter number of solutions per iteration), exist for each time of the procedure.
    These are changed iteratively and evaluated. If there is no improvement of the objective function value (convergence) or if the defined maximum number of iterations has been reached,
    the procedure is stopped and the best solution is provided.
    The procedure includes the following steps.
    1. Initial selection of the vehicle combination from the specified vehicle combination set for
    each vehicle journey section and each solution.
    2. Line blocking without vehicle interchange for this selection for each solution
    3. Evaluation of the solution and convergence check.

    PTVGROUP

    595

    8.4.5.1 Selection principles of vehicle combinations


    4. Determining and merging selections, which have lead to good solution properties, and new
    start from step 2.), until convergence applies or the maximum number of iterations has been
    achieved.
    Because the line blocking is carried out as in the procedure without vehicle interchange (see
    "Line blocking description without vehicle interchange" on page 585), for defined selection of
    the vehicle combinations, the following additional components are necessary to understand
    the procedure:
    Selection principles of vehicle combinations
    Solution evaluation via objective function
    Parameters and convergence
    Consideration of different vehicle combination-specific minimum layover times
    8.4.5.1

    Selection principles of vehicle combinations


    The selection of vehicle combinations which can be used from the set specified for each
    vehicle journey section, is the central component of the procedure. The challenge as a search
    procedure is to produce as many different selections and to avoid such selections which lead
    to poor solutions. This task can be compared with the connection search per Branch&Bound
    within the timetable-based assignment.
    In the initial step of the procedure there are no solutions yet. Heuristic procedures play a bigger role for the selection. In all other iterations the selection is always made on the basis of a
    solution from the preceding iteration, so that this solution can be further developed. But here
    parts of the solution are also discarded and rebuilt. The selection is carried out initially, to
    create the start solutions for the first iteration according to the following criteria:
    For an individual occurrence of a vehicle journey section the selection is carried out
    randomly
    according to the volume of the vehicle journey and capacity of the vehicle combination
    - i.e. a selection which probably leads to good coverage of the demand,
    according to the specified number of vehicles, considering the vehicles already used,
    by edges without selection or already selected edges - therefore a selection which probably leads to an equal volume,
    according to the neighboring vehicle journey without selection - i.e. a selection which
    probably lead to productive blocks.
    Based on individual occurrences of vehicle journey sections, for which a selection has
    already been made, analog choices are made as far as possible
    for all vehicle journeys of a line,
    for all other occurrences of the same vehicle journey section,
    for individual neighbors or entire chains neighboring below each other,
    for the compliance of the flow conditions particular favorable occurrence of vehicle journey sections.
    The selection can be applied from the attribute Vehicle combination number of the
    vehicle journey section, alternatively for all vehicle journey sections from the specifications for the line blocking without vehicle interchange, if the vehicle combination in
    the set is included in the permitted vehicle combinations set. Without vehicle interchange,
    the line blocking solution thus becomes a starting solution.

    596

    PTVGROUP

    8.4.5.2 Solution evaluation via objective function


    If a reference solution is specified and the proximity is required, the selection can be applied from this reference solution.
    In all later iterations, each solution is generated from an existing solution. The relative inefficient parts of the solution are determined, who's selection is discarded and based on the new
    ones retained, analog choices made according to the same criteria as in the initial stage. In
    addition the following principles are available for the solution change:
    Replace empty trips of a vehicle combination, so that for this vehicle combination a suitable temporal and local vehicle journey is selected, for which another vehicle combination has so far been selected.
    Change the choice simultaneously for entire blocks, so that the configuration regarding
    the costs is convenient.
    Change the choice simultaneously for entire blocks, so that the configuration regarding
    the OD demand coverage is convenient.
    Change the choice simultaneously for entire blocks, so that the configuration regarding
    retaining the available number of vehicles is convenient.
    8.4.5.2

    Solution evaluation via objective function


    Line blocking with vehicle interchange uses an objective function for evaluating the quality of
    a solution. The objective function measures solution properties, where there is room for improvement. It comprises the objective function of line blocking without vehicle interchange (see
    "Construction of the graph" on page 586) as a component.
    The following solution properties are evaluated:
    Costs: Objective function of line blocking without vehicle interchange. This especially comprises the number of vehicles per vehicle combination as well as the service km and
    empty km and service times and empty times, as well as the layovers within and outside of
    a depot
    Number of vehicle units: Exceeding the predefined number of available vehicle units
    Consideration of volumes: Too low capacities (total or seats) regarding the OD demand
    Line purity, local definition: Number of transfers between the different lines
    Line purity, global definition: Number of different lines in a block
    Number of vehicle combinations per line: Number of different vehicle combinations used
    on the same line
    Regularity: Number of vehicle journey sections, who's vehicle journey section occurrence
    lies in at least two different blocks or blocking days
    Difference from reference solution (only when a reference solution has been specified):
    Difference to this reference solution in form of deviating transfers between vehicle journey
    sections
    The following function is used as an objective function (OF), which is based on the comparison
    between the calculated and the estimated values for each of the objective function components:

    PTVGROUP

    597

    8.4.5.2 Solution evaluation via objective function


    where
    ci

    Influential factor (Procedure parameters) for the indicator i, where c >


    i
    0

    ofi

    Objective function component for indicator i according to the upper list

    comparisoni

    Comparison value for indicator i on a comparable scale

    The individual component properties are apply as follows:


    Component

    Calculation

    Cost

    The objective function component costs evaluate the solution according


    to the same criteria as the line blocking without vehicle interchange.
    It therefore applies
    ofCosts = fe Costs(e) (fe = Flow on edge e)
    For the comparison value, vehicle combinations are randomly selected
    and thus a solution calculated. The costs are then used as a comparison
    value.

    Number of
    vehicle units

    The sum is calculated over all vehicle units, across the number of used
    but not available vehicles per vehicle unit
    The comparison value comparison
    is 1 (Note: This is how you
    vehicle
    achieve very strong penalization, because this criterion must apply
    "strongly", if it is even used)

    Consideration
    of volumes

    For the calculation, for each vehicle journey item i first the difference between its volume and its capacity (cap) is calculated as follows

    The capacity sums up from the selected capacity (seats or total) of all
    vehicle combinations of all vehicle journey sections that service this
    vehicle journey item.
    Due to the current parameter settings, a vehicle journey's value
    results from the particular formula below:
    using option Average volume

    using option Peak volume

    598

    PTVGROUP

    8.4.5.3 Parameters and convergence


    Component

    Calculation

    The value

    is the total calculated for all vehicle journeys:

    The value of this objective function component, which applies for the random solution, used for cost estimation, is used as a comparison value.
    Line purity,
    local definition

    The number of line changes between successive vehicle journeys in the


    block are measured. The benchmark is the number of occurrences of
    vehicle journey sections in total (therefore the number of all changeovers between successive vehicle journey block items).

    Line purity, glo- The number is calculated minus 1 of the line per block, summed up over
    bal definition
    all blocks.
    The comparison value is the number minus 1 of the lines per partition,
    summed up over all partitions.
    Regularity

    Dispersion of the occurrences of vehicle journey sections is measured


    for different blocks or optionally for different blocking days.
    The following applies:
    of
    = Sum of vehicle journey sections |{Blocks / blocking days
    regularity
    which contain the VJS}| - 1
    comparison
    = (Sum of occurrences of the VJS in the line
    regularity
    blocking time interval 1)

    Distance to star- The number of changeovers from vehicle journey section to vehicle jourting solution
    ney section, which differ from the comparison solution, is measured.
    The comparison value is the number of all changeovers from vehicle
    journey section to vehicle journey section in the comparison solution.
    Table 233: Objective function components for line blocking with vehicle interchange
    Note: Objective function components, which are not relevant for the specific planning
    task, can be switched off by setting the respective coefficient to 0. This is recommended,
    because optimization up until the solutions, considering the hidden properties, is thus
    suppressed. Finding good solutions regarding the remaining criteria is accelerated accordingly.
    8.4.5.3

    Parameters and convergence


    The line blocking procedure with vehicle interchange can be controlled via several parameters. The procedure is iterative, by first generating a number of solutions, which are then
    improved step by step. If there is no improvement within a specified number of iterations, convergence has been reached and the procedure is ended.

    PTVGROUP

    599

    8.4.5.4 Consideration of different vehicle combination-specific minimum layover times


    As a heuristic procedure, coincidence plays a decisive role, especially as there are many equivalent solutions. By using a random number generator, the procedure is deterministic in the
    sense, that each calculation with the same data and parameters achieve the same result. You
    can however modify the procedure by changing the parameter Random seed and thus for
    otherwise identical data calculate alternative solutions.
    These are the following parameters for controlling the procedure run:
    Parameters

    Meaning and notes

    Use reference solu- A reference solution is a block version containing blocks. If this
    tion
    option is selected, a solution is searched which can be compared
    with this reference solution. A different block version should be selected as reference solution, than the current one used.

    8.4.5.4

    Maximum number
    of iterations

    Number of iterations, after the procedure is ended, if convergence


    occurs. This value should be a multiple of the number of iterations
    without improvement.

    Number of iterations without


    improvement

    If for N iterations no improvement of the target function value is determined, the procedure regarded as converged and is ended. Reasonable values depend on the task size, however, they should not be
    less than 10 - 20.

    Number of solutions per iteration

    Number of simultaneous existing solutions per iteration. The more


    freedom the planning task offers, the greater this value should be.
    The minimum permissible value is 10, generally however 20 to 100.

    Random seed

    By changing this value, the random item of the procedure can be


    influenced to achieve, with otherwise same data and parameters, a
    different procedure und thus a different result.

    Consideration of different vehicle combination-specific minimum layover times


    Between two vehicle journeys, different vehicles require efforts of a different extent. There are
    various reasons:
    Changing the running direction for a long train requires more time than changing it for a
    short train. This is because it takes longer to get to the other driver's cabin at the end of the
    train.
    The length in time required by boarding and alighting passengers at scheduled stops
    depends on the configuration of the vehicle doors.
    Various final and cleaning services are required, also supply and disposal services.
    Due to the various minimum layover times of different vehicle combinations, certain changeovers between vehicle journeys are only possible for some of the provided vehicle combinations, whereas the time slot is insufficient for others. Thus, these differences should be
    regarded for the efficient vehicle use, and a vehicle should be chosen where it can be used
    best.
    Line blocking with vehicle interchange can take the different minimum layover times into
    account. For that purpose, the attributes Use specific pre preparation time and Use specific

    600

    PTVGROUP

    8.4.6 Line block display and editing in the timetable editor


    post preparation time have to be set to true for the concerned vehicle journey sections. Then,
    via the attributes Specific pre preparation time und Specific post preparation time - each
    with sub-attribute vehicle combination - the values for the pre and post preparation times can
    be set for each vehicle combination. This data is automatically regarded by the procedure line
    blocking with vehicle interchange. Even the line block check will take the different pre and post
    preparation time values into account for the vehicle combination of the line block which will
    then be determined.

    8.4.6

    Line block display and editing in the timetable editor


    In Visum blocks are displayed as Gantt charts (block view). Compared to the time-distance diagram, which only displays blocks in as far as the bound trips can be illustrated on the stop
    sequence, a natural view on a block as a whole is possible. All block actions are displayed as
    well as all other information such as header data, etc., but also all empty trips and layovers.
    The display can be restricted according to different filter criteria, to increase the clarity, and can
    be configured extensively with graphic parameters in the usual way.
    Alongside the pure display, block display also allows blocks to be edited. Besides the block
    actions, vehicle journey sections are also displayed, which can be inserted or removed from a
    block via drag&drop. It is thus possible, to reedit the blocks, generated with one of the two line
    blocking procedures, or completely manually generate blocks. All other block-related functions
    such as check line block, coverage check and definition of forced chainings can be initiated
    from the line block view.

    Illustration 192: Example for block display of a block with 5 blocking days
    The line block display is included in the timetable editor. There you can find detailed information on display and editing (see User Manual: Chpt. 20.1.5 , page 2119).

    8.4.7

    Vehicle requirement and line blocking indicators


    The vehicle requirement and line blocking indicators, are also used to asses the economic efficiency of an existing PuT supply and to derive improvement potentials for the operator.

    PTVGROUP

    601

    8.4.7.1 Vehicle requirement


    8.4.7.1

    Vehicle requirement
    The vehicle demand can be returned in the length proportional and in the time proportional
    mode. It is output for the objects of the line hierarchy as well as for territories precisely broken
    down to boundaries. Fr the following network objects, both sets of indicators can be calculated
    for the analysis period, the analysis horizon and by analysis time interval.
    Vehicle journeys
    Time profiles
    Line routes
    Lines
    Main lines
    Operators
    Transport systems
    Territories
    Territory PuT detail
    Indicator

    Description

    Number of Vehic- Length of the vehicle journey section divided by the total length of all
    les (in proportion vehicle journey block items in the block, multiplied by the number of
    to length)
    blocking days of the block.
    Number of vehicles (in proportion
    to time)

    Length of the vehicle journey section divided by the total length of all
    vehicle journey block items in the block, multiplied by the number of
    blocking days of the block.

    Table 234: Line blocking and vehicle requirement indicators


    The allocation of the indicator value for the precise calculation by territory is performed as follows.
    The time proportion of a vehicle journey section in the total time of all vehicle journey sections of the block (called NumBlocksVJS below) is determined.
    For each link that - after a temporal intersection of the vehicle journey section with analysis period or time interval - is identified as traversed, the proportional number of vehicles
    is determined according to the time proportion of the link at the VJS NumBlocksVJS.
    This value is then summed up in the line hierarchy and hence called
    NumBlocksVJSOnLink.
    For the precise calculation by territory, Visum multiplies the length proportion of the link
    in a territory NumBlocksVJSOnLink per link. Here, Visum always uses the length-oriented proportion since the precise link calculation by territory is always based on this criterion. The "error" resulting from this is minimal however, because it only affects links that
    lead across a territory border. The proportion of all other links is 1.0.
    Note: To get a result for the indicators number of vehicles (length proportional) and number of vehicles (time proportional), you have to first calculate the line blocking procedure
    and then the procedure PuT operating indicators.

    602

    PTVGROUP

    8.4.7.2 Distribution of empty trips and empty times to vehicle journeys


    8.4.7.2

    Distribution of empty trips and empty times to vehicle journeys


    As line costing is based on vehicle journeys, empty times and empty kilometers of a line block
    have to be allocated to the vehicle journeys served by the block. Based on this, costs can be
    calculated by the PuT operating indicators procedure.
    The example below illustrates the impact of the four variants provided for distribution of empty
    times and empty distances to service trips. The operating time is calculated from empty time
    and service time. Similarly, the operating distance results from empty distance and service
    distance. Operating time and operating distance are required for cost calculation.
    Hourly costs= Operating time Vehicle-Hour cost rate
    Kilometer costs= Operating distance Vehicle-Kilometer cost rate
    Variant 1: EmptyTime from Pre+PostPrepTime (2+3 min) of veh. journey / no
    EmptyKm
    Vehicle journey

    ServTime Empty
    time

    OpTime

    ServKm

    EmptyKm

    OpKm

    1st

    6:30 7:15

    0:45:00

    0:05:00

    0.50

    30 km

    0 km

    30 km

    2nd 8:00 8:15

    0:15:00

    0:05:00

    0.20

    10 km

    0 km

    10 km

    3rd

    8:30 9:15

    0:45:00

    0:05:00

    0.50

    30 km

    0 km

    30 km

    4th

    9:30 10:15

    0:45:00

    0:05:00

    0.50

    30 km

    0 km

    30 km

    2:30:00

    0.20

    2:50:00

    100 km

    0 km

    100 km

    Total

    Variant 2: From EmptyTime/EmptyKm of line block weighted by vehicle journeys


    Vehicle journey

    ServTime Empty
    time

    OpTime

    ServKm

    EmptyKm

    OpKm

    1st

    6:30 7:15

    0:45:00

    0:33:45

    1:18:45

    30 km

    7.5 km

    37.5 km

    2nd 8:00 8:15

    0:15:00

    0:33:45

    0:48:45

    10 km

    7.5 km

    37.5 km

    3rd

    8:30 9:15

    0:45:00

    0:33:45

    1:18:45

    30 km

    7.5 km

    37.5 km

    4th

    9:30 10:15

    0:45:00

    0:33:45

    1:18:45

    30 km

    7.5 km

    37.5 km

    2:30:00

    2:15:00

    4:45:00

    100 km

    30 km

    130 km

    Total

    Variant 3: From EmptyTime/EmptyKm of line block weighted by service time


    Vehicle journey

    ServTime Empty
    time

    OpTime

    ServKm

    EmptyKm

    OpKm

    1st

    6:30 7:15

    0:45:00

    0:40:30

    1:25:30

    30 km

    9 km

    39 km

    2nd 8:00 8:15

    0:15:00

    0:13:30

    0:28:30

    10 km

    3 km

    13 km

    3rd

    8:30 9:15

    0:45:00

    0:40:30

    1:25:30

    30 km

    9 km

    39 km

    4th

    9:30 10:15

    0:45:00

    0:40:30

    1:25:30

    30 km

    9 km

    39 km

    2:30:00

    2:15:00

    4:45:00

    100 km

    30 km

    130 km

    Total
    PTVGROUP

    603

    8.4.8 PuT interlining matrix procedure

    Variant 4: From EmptyTime/EmptyKm 50% before and 50% after vehicle journey
    Vehicle journey

    ServTime Empty
    time

    OpTime

    ServKm

    EmptyKm

    OpKm

    1st

    6:30 7:15

    0:45:00

    0:52:30

    1:37:30

    30 km

    15 km

    45 km

    2nd 8:00 8:15

    0:15:00

    0:30:00

    0:45:00

    10 km

    5 km

    15 km

    3rd

    8:30 9:15

    0:45:00

    0:15:00

    1:00:00

    30 km

    0 km

    30 km

    4th

    9:30 10:15

    0:45:00

    0:37:30

    1:22:30

    30 km

    10 km

    40 km

    Total
    2:30:00
    2:15:00
    4:45:00
    100 km
    30 km
    130 km
    Table 235: Example illustrating different variants of distribution of empty time and empty kilometers on individual vehicle journeys.

    8.4.8

    PuT interlining matrix procedure


    The procedure PuT interlining matrix calculates transport system specific skim matrices for
    interlining trips between the stop points of a transport system. For each relation generated between two stop points, the specific value calculated for the shortest path between the stop
    points is returned for the indicator selected. Relations are created for the selected type of
    pairs: between two stop points, between two active stop points or only between the stop
    points, which are start or end stop point of a vehicle journey of the transport system. Optionally,
    system routes can be considered. In this case, the indicator values for a relation are determined from the best system route, which leads directly from the start stop point to the destination stop point and which is permissible for the transport system. Transitive search via the
    system routes is not carried out. For each relation it is thus possible, to individually overwrite
    the O-D value, determined from the network.
    In the line blocking procedure (see User Manual: Chpt. 20.1.3 , page 2104), the interlining
    matrix is used to determine the duration and length for each empty trip between stop points.
    The PuT interlining matrix procedure is also provided as a separate procedure, so that the output matrices can be imported in external timetable or crew scheduling systems, as interlining
    matrices for line blocking.
    table 236 shows an example of a PuT interlining matrix, where the values of the shortest path
    (determined on the basis of the attribute t-PuTSys ) between all relations between two stop
    points are listed. If in a cell the value is 999999, this means, that there is no path between the
    two stop points.
    SP20

    604

    SP21

    SP22

    SP24

    SP50

    SP56

    SP71

    SP74

    SP86

    SP20

    16

    36

    61

    34

    73

    121

    108 999999

    SP21

    16

    20

    45

    50

    89

    137

    124 999999

    SP22

    36

    20

    25

    70

    109

    157

    144 999999

    SP24

    61

    45

    25

    95

    134

    182

    169 999999

    SP50

    34

    50

    70

    95

    39

    87

    74 999999

    PTVGROUP

    8.5 PuT fare model


    SP56

    73

    89

    109

    134

    39

    SP71 999999 999999 999999 999999 999999 999999

    48

    35 999999

    0 999999 999999

    SP74

    108

    124

    144

    169

    74

    35

    13

    SP86

    121

    137

    157

    182

    87

    48 999999

    0 999999
    13

    Table 236: PuT interlining matrix with t-PuTSys between stop points

    8.5

    PuT fare model


    The Visum fare model is based on fare systems and ticket types.
    A fare system is a set of lines, for which a joint fare system exists. Each PuT operator often
    has his own fare system, in transport associations a fare system can also include lines of different operators.
    A ticket type describes how the fare is calculated for a PuT connection or part of a connection.
    Each ticket type obeys one of four calculation methods ("Fare structure"):
    Distance fare: The fare is conform with the distance covered, which is measured by fare
    points.
    Zone-based fare: The fare is conform with the number of traversed fare zones.
    From-to zone-based fare: The fare is only dependent on initial fare zone and target fare
    zone, this is therefore a matrix fare.
    Short-distance fare: A special fare for paths, which do not exceed the specified threshold
    regarding distance, run time and/or the number of stops.
    The four fare structures are described in detail as follows (see "Base fare calculation" on page
    609).
    The illustration 193 offers an overview of the network objects which belong to the fare modeling in Visum.

    PTVGROUP

    605

    8.5 PuT fare model

    Illustration 193: Possibilities of fare modeling in Visum


    For each demand segment you can determine which ticket types are used in a fare system. In
    particular for each demand segment, several ticket types may exist for each fare system.
    With the allocation of lines (and PuT-Aux transport systems) to fare systems, each path leg of a
    PuT connection belongs to one or more fare systems.
    Fare systems are generally independent. The total fare for a connection is normally the sum of
    the fares to be paid for the individual fare systems. With specific transfer fares you can however model, that a change between fare systems costs extra or a reduction is given (see "Transport system-specific supplements" on page 615).
    Determining the ticket to be used for each fare system
    Within the fare systems, the possibilities of fare modeling are very versatile.
    A basic property of a fare system is the "Fare-reference". This expresses, whether a ticket has
    to be bought for each individual path leg or if it can be used for successive or even all path
    legs of a connection. All three cases are more often found in practice.
    As mentioned, several ticket types (per demand segment) may be available within a fare system. Let's take for example, a fare system is composed of fare zones and the normal fare
    depends on the number of traversing fare zones. For trips of maximum ten minutes, an inexpensive short-distance ticket applies independent of the fare zones. For trips from and to the
    airport, a special airport ticket has to be bought.

    606

    PTVGROUP

    8.5 PuT fare model


    Generally speaking the crucial question is when creating a fare system, which ticket types are
    allowed to be used for which connections and how much freedom does the passenger have
    when selecting a ticket.
    The applicability of the different ticket types plays an important role. If the defined conditions in
    the ticket type have been breached, the ticket cannot be used and another ticket has to be
    used. In the example, the short-distance ticket is invalid if the maximum run time of 10 minutes
    has been exceeded and the airport ticket only applies for paths from and to the airport.
    Distance-based or zone-based ticket types can be modeled so that they are only valid on certain connections. You can thus define where the applicability limits of the ticket lie.
    Ticket types have ranks , which can be used to express a hierarchical order within a fare system. In combination with the previously described applicability of tickets, a logic thus applies
    for determining tickets to be used, for a given connection or its path leg(s): Amongst all applicable ticket types it is the one with the highest rank.
    In the example shown, the special airport ticket must have the highest rank, because it has to
    be used for all connections, whose start or target is the airport. For all other connections the airport ticket cannot be used after construction, which is why the ticket type with the second highest rank is regarded, in this case the short-distance ticket. This applies if the connection
    fulfills the requirements of the short-distance ticket. If not, the normal zone-based fare with the
    lowest rank is applied.
    Do you want to illustrate that the passenger has the free choice between several ticket types,
    then allocate the same rank. The most inexpensive ticket with the highest rank is selected
    amongst all applicable tickets.
    Ranking order of fare systems
    It may occur, that lines do not just belong to one fare system, but are part of several fare systems. A regional train can for example, be used both within the urban network area with a network ticket and beyond the boundaries of the transport association with a long-distance ticket.
    Urban network and long-distance transport are separate fare systems with completely different
    fare structures, the regional train line however, belongs to both.
    If a line belongs to several fare systems, a fare within each of these fare systems can generally
    be determined according to the procedure described above. However, in reality the passenger
    cannot freely select between the two different fare systems, in each case. A typical fare condition would be for example, that the regional train on trips within the transport association
    area can only be used with ticket types of the urban network fare system and long-distance
    transport tickets only have validity, if used beyond the transport association boundary (see
    "Procedure for ambiguous fare systems" on page 624).
    To express such ranking, you can define fare system ranks. These ranks are only relevant if in
    your network model, lines belong to several fare systems, because otherwise the fare systems
    are evident for all path legs of a PuT connection.
    In general the line of each path leg of a PuT connection belongs to several fare systems. A set
    of allocated fare systems therefore exists for each path leg. The entire connection can principally be "covered" by any combination of items of these fare system sets. The fare system
    ranks then define a logical order within the combinations: all combinations with the smallest

    PTVGROUP

    607

    8.5.1 Ticket types


    maximal fare system rank are considered first, and thus the one selected which can be applied
    and provides the lowest fare. If none is applicable, all other combinations with the next highest
    rank follow. If there are no valid fare system combinations, the global fall-back fare of the fare
    model is charged.
    Because you can allocate ranks both on the ticket type level and the fare system level to
    model specific fare conditions, all together great flexibility is achieved for fare modeling.
    Subjects
    Ticket types
    Fare systems
    Fare calculation
    Application of fares

    8.5.1

    Ticket types
    A ticket is valid for a path leg of a PuT connection, for several path legs of a connection or
    even the entire connection. Validity depends on the properties of the fare system (see ""Fare
    reference" of a fare system" on page 620) . This section first talks about applicability, calculation logic and other ticket type properties. To make it easier, this chapter does not always
    explicitly point out that a ticket type, if necessary, only applies to individual path legs of a
    connection, but talks about "connections" or "paths".
    A ticket type describes how the fare should be calculated. The fare components of a ticket type
    include the base fare and TSys-specific supplements:
    Fare component

    Description

    Base fare

    The base fare is calculated from the fare structure of the ticket type.
    Four fare structures can be selected:
    Distance-based fare
    Zone-based fare
    From-to zone-based fare
    Short-distance fare

    Transport systemspecific supplements

    Supplements are defined separately per ticket type for each PuT
    transport system and include the following components:
    Distance-based supplements
    Like distance-based fares, these are based on fare points.
    Fixed supplements
    These can be charged per path leg or once per transport system
    or only for the TSys with the highest rank.

    Essential characteristic of a ticket type is the fare structure, which defines the calculation
    method for the base fare:
    The distance-based fare is based on distance-based fare items: The base fare is calculated based on the number of traversed fare points.

    608

    PTVGROUP

    8.5.1.1 Base fare calculation


    The zone-based fare is based on the zone-based fare items: The base fare is calculated
    based on the number of fare zones traversed.
    The From-to zone-based fare is based on From-To zone-based fare items: The base fare
    is the entry of the pair, initial fare zone and target fare zone from the connection of a fare
    matrix, which is indicated by (From-fare zone, To-fare zone).
    The short-distance fare is based on short-distance fare items: The base fare applies for
    tickets whose length, duration and number of stops does not exceed the defined thresholds.
    The following section describes the four fare structures in detail.
    For fare modeling it is important to know which ticket types can be applied for which connections. In the case of the fare structure "Short-distance fare" the restricted applicability is clear,
    however, the other three fare structures may also have restrictions: Zone-based fares generally cannot be applied to connections, which lie outside of the considered fare zones. Both
    the from-to zone-based fares, as well as distance-based fares may refer to certain pairs of fare
    zones only or certain distance classes.
    The rank defines the ticket type hierarchy within a fare system and is relevant if a fare system
    comprises several ticket types. The definition of the rank is illustrated by several examples
    (see "Ticket selection in a fare system" on page 622).
    Via the utility rate the conversion factor is specified for a single trip. It is included in the calculation of the fare of a PuT path.
    8.5.1.1

    Base fare calculation


    The calculation of the base fare is based on the fare structure of the ticket type, of which there
    are four different occurrences:
    Fare structure "Distance-based fare"
    Distance-based fares are used to model fares, which directly depend on the distance covered.
    "Distance" however, does not mean the link length or the line route length itself. In fact, the calculation of a distance-based fare is based on the number of fare points on the considered
    path. The number of fare points is a property of the links and time profile items. Because, compared to the length, this attribute is TSys-specific on links, you can allocate a different fare to
    the traversing of a link for different PuT-TSys.
    The traversed fare points of the links and time profile items of the path are summed up, and the
    fare is looked up in the table of the fare items.
    The fare between two consecutive fare items can be interpolated to model a linear course.
    A distance-based fare is not applicable, if the fare stage does not offer a fare for the determined number of fare points, but is "empty".
    Example: Fare structure "distance-based fare"
    Let's look at a ticket type with the following properties:
    Fare constant 10 CU for trips from 1 fare point through 5 fare points,
    Fare constant 16 CU for trips from 6 fare points through 10 fare points,

    PTVGROUP

    609

    8.5.1.1 Base fare calculation


    linear increase of the fare from 16 CU to 24 CU between the range of 10 fare points and
    20 fare points,
    Fare constant 24 CU for trips through 30 fare points,
    Ticket cannot be used fro trips with more than 30 fare points.
    Expressed in a graph:

    Illustration 194: Example for a distance-based fare with 5 fare stages


    In Visum you model this fare as the following distance-based fare stages:
    Number of fare
    points

    Interpolate

    Fare [CU]

    No

    10

    10

    No

    16

    20

    Yes

    24

    30

    No

    24

    [Empty field]
    > 30
    --Table 237: Fare stages for the example on distancebased fare

    Fare structure "Zone-based fare"


    Zone-based fares are used in situations where the fare depends on the number of traversed
    fare zones.
    A ticket type with zone-based fare refers to a specific fare zone type. Not all fare zones play a
    general role for the tickets, but only those whose "type" corresponds to the fare zone type of
    the ticket. This is how you can especially model independent fare zones belonging to different
    fare systems, which can still overlap in space.
    By default, a zone-based ticket is only applicable for paths which only include stops, which
    belong to fare zones of the ticket type's fare zone type. To replicate the calculation logic up to

    610

    PTVGROUP

    8.5.1.1 Base fare calculation


    and including Visum 11, you can optionally ignore stops without fare zone. For the creation of
    new models, this setting however is not recommended.
    A stop can lie in several fare zones and one fare zone generally has several stops. However, it
    is often clear which fare zones the passenger traverses on his path. This results in the number
    of traversed fare zones and thus the fare. More complex overlapping fare zones could provide
    several possibilities of covering a path by fare zones. Visum then selects the minimum number
    of overlapping fare zones and thus the most inexpensive fare.
    A zone-based fare is still not applicable, if the fare stage does not offer a fare for the determined number of fare zones, but is "empty".
    Fare zones do not all have to be equivalent, but can be included with a cardinality into the
    count. To do so, select a numeric, integer attribute and allocate the required values. A city center zone counts twice in many fare systems for example. It then has to receive cardinality two.
    Initial fare zones and end fare zones of a path can explicitly be excluded from the application
    of cardinality.
    You can specify the method of counting fare zones which have been traversed on a path
    several times. Either each traversed fare zone is counted exactly once, or each entering into a
    fare zone causes it to be counted again.
    Example: Fare structure "Zone-based fare"

    Illustration 195: Example for a zone-based fare with three overlapping fare zones and six
    stops.
    The fare zones in this example have different cardinalities - fare zone 2 is to be counted twice:

    PTVGROUP

    611

    8.5.1.1 Base fare calculation


    Fare zone

    Cardinality
    1

    The following base fare is charged for the respective fare zones:
    Number of fare
    zones

    Base fare [CU]


    2.00
    3.00
    3.50
    >3

    4.00

    The result being, the traversed fare zones and thus also the fare for all the paths in the example network:
    Path

    Traversed fare
    zone numbers

    Number of counted fare


    zones (considering the cardinalities)

    Base fare
    [CU]

    Stop 1 - Stop 2

    2.00

    Stop 1 - Stop 3

    2.00

    Stop 1 - Stop 6

    1 and 3

    3.00

    Stop 1 - Stop 4

    1 and 2

    3.50

    Stop 1 - Stop 5 via 3 and


    4

    1 and 2

    3.50

    Stop 1 - Stop 5 directly


    via 2

    1 and 2 or 1 and 3

    2 (for the path through 1 and


    3)

    3.00

    Stop 1 - Stop 6 via 2, 3,


    4, 5

    1 and 2 and 3

    4.00

    Stop 1 - Stop 2
    1
    1
    Table 238: Example network: Fare zones that have been traversed and fare

    2.00

    Fare structure"From-to zone-based fare"


    From-to zone- based fares illustrate a matrix fare between fare zones. The fare thus only
    depends on the start and end fare zones of the path. En route traversed fare zones do not play
    a role.
    You can generate a complete fare matrix between all fare zones. From-to zone-based fares
    are also suitable for the definition of exceptions: If trips from or to specific fare zones underlie a

    612

    PTVGROUP

    8.5.1.1 Base fare calculation


    different fare structure, you can define the fares of these relations with a From-to zone-based
    fare, which exceed the standard ticket type by its rank.
    A From-to zone-based fare is not applicable, if the matrix for the pair of start and end fare zone
    of the path does not have an entry.
    To define a fare from a fixed fare zone x to all other fare zones, you can create an entry for the
    fare zone numbers (x, 0), thus using the value 0 as a wildcard for the end fare zone. Analog
    entries for (0, y) are possible. Specific entries overwrite general entries, this means a fare defined for (x, y) applies to trips from fare zone x to fare zone y, independent of whether fares for
    (x, 0), (0, y) or (0, 0) also exist.
    If the start stop or the end stop of the connection lie within more than one fare zone, several
    fare zone pairs have to be considered; the fare is then defined as a minimum of all entries.
    Example: Fare structure "From-to zone-based fare"
    For the example in illustration 195 the following From-to zone-based fare can be modeled as
    an alternative to the zone-based fare:
    to fare zone
    from fare zone

    2.00

    3.50

    (*) 3.00

    3.50

    3.00

    3.50

    3.00

    3.50

    2.00

    A comparison with the zone-based fare defined above gives the following differences:
    The fare does no longer depend on the exact course of the path; a comparison between
    direct and indirect path from stop 1 to stop 6 is no longer possible here, see cell (*).
    However, different fares can be determined for paths with an identical number of fare
    zones if required - these fares can even be asymmetrical. For example, trips from fare
    zone 3 to fare zone 1 could cost 2.80 CU instead of the standard fare for two fare zones.
    Only the entry at position (3, 1) would have to be changed. This could not be expressed in
    a zone-based fare.
    In Visum, the above matrix can be modeled as follows:
    from FZ

    PTVGROUP

    to FZ

    Fare [CU]

    2.00

    3.00

    2.00

    3.00

    3.00

    3.50

    613

    8.5.1.1 Base fare calculation


    The last entry is a wildcard for all fare zone pairs which were not mentioned explicitly before.
    You can also express, that the ticket type is not applicable for certain pairs of fare zones:
    from FZ

    to FZ

    Fare [CU]

    All

    2.70

    All

    [Empty field]

    According to this definition, the ticket cannot be used for all trips to the new fare zone 4 - but for
    trips in the opposite direction, for the fare of 2.70 CU.
    Fare structure "Short-distance fare"
    The short-distance fare is a standard fare for trips below certain threshold values for run time,
    trip distance and/or number of stops. Short-distance fares can therefore only be applied to
    paths which meet these threshold values.
    A short-distance ticket type can also contain more than one set of threshold values (shortdistance fare items). You can express for example, that there are specific fares for certain run
    times, for example 1 CU up to 10 min, 2 CU up to 30 min, etc.
    A short-distance ticket is applicable, as soon as the threshold values of at least one of its fare
    items are fulfilled. The fare is defined as the minimum fares of all fare items, whose threshold
    values are met.
    Example: Fare structure " Short-distance fare"
    Fare item 1: Trips to the next stop only cost 0.50 CU:
    max. run time

    unlimited

    max. distance

    unlimited

    max. number of stops

    Fare

    0.50 CU

    Fare item 2: as above, but only for trips with a maximum of 5 min run time. The fare is then only
    0.30 CU.
    max. run time

    5 min

    max. distance

    unlimited

    max. number of stops

    Fare

    0.30 CU

    The fare for fare item 2 can in principle also be selected higher than the fare for fare item 1.
    This however, would not be reasonable because for trips up to the next stop with maximum 5
    minutes run time, both threshold values are satisfied, i.e. the fare is the minimum of both fares.

    614

    PTVGROUP

    8.5.1.2 Transport system-specific supplements


    This minimum would then be 0.50 CU, the second fare item therefore ineffective. This is an
    example for the following aspect:
    Consistency of fare stages
    The fare stages of a ticket type (more precisely the fares at the fare items of the ticket type) can
    be freely defined. In principle this also makes contradicting entries possible. For example, the
    fare for a greater distance can be smaller than the fare for a shorter distance, or a shortdistance fare for a trip up to three stops can be more expensive than a short-distance fare for
    up to five stops. It is recommended however, that such contradicting definitions should be avoided.
    8.5.1.2

    Transport system-specific supplements


    Each ticket type has its own supplement regulations. These include PuT transport system
    distance supplements and fixed supplements, whereas for the latter a transport system rank
    can also be set. Furthermore, you can define a minimum fare for each transport system.
    Supplements are imposed for each application independently. This also applies if the same
    ticket type is purchased several times on one connection.
    You can define supplements for all PuT transport systems of the network in each ticket type. Of
    course, only the settings for those transport systems, whose lines are connected with the fare
    system of the ticket type are effective, which means for passengers are able to use the ticket
    type in the first place.
    Minimum fare
    The minimum fare for each transport system is charged instead of the calculated total fare for
    the ticket type, in case
    the transport system appears on the path legs covered by the ticket and
    the total fare is less than the minimum fare.
    The minimum fare is thus not a component you can add, but a minimum value for the total fare
    to be charged. As the regulation applies to all transport systems, the most expensive minimum
    fare of all transport systems used, is the lower limit for the total fare of the ticket type.
    Below you will find a simple example on minimum fares (see "Example: Calculation of fixed
    supplements" on page 616).
    Fixed supplements
    Fixed supplements are constant additional charges which are added to the base fare of the
    ticket type. Each PuT transport system has its own fixed supplement. For which of the path legs
    covered by the ticket type, a fixed supplement can be imposed, is a central feature of the ticket
    type. Select one of the following options:
    Raise supplement once per transport system,
    Raise supplement only for the top-ranking transport system,
    Raise supplement per path leg.
    In the first case, exactly one fixed supplement is incurred for each occurring transport system independent of how many path legs are being used with lines of the transport system.

    PTVGROUP

    615

    8.5.1.2 Transport system-specific supplements


    In the second case, the ranks of the transport systems from the supplement regulations of the
    ticket type, play a role. Using the ranks, you can express that a certain transport system (e.g.
    ICE) discharges the passenger from paying fixed supplements for other transport systems (e.g.
    IC). If several transport systems have the same rank, on the path legs covered by the ticket
    type, the maximum fixed supplement of the top-ranking transport system applies. Ranks do not
    influence distance-based supplements.
    In the third case, a fixed supplement is imposed for each path leg anew, for the transport system used.
    The difference between the three options for imposing fixed supplements can be made clearer
    with the following example:
    Example: Calculation of fixed supplements
    Transport system

    Fixed supplement [CU]

    Minimum fare
    [CU]

    Rank Distance-based
    supplement

    IC

    4.00

    0.00

    No

    ICE

    0.00

    7.00

    Yes

    RE

    0.00

    0.00

    No

    These are the distance-dependent supplements for the ICE:


    Number of fare
    points

    Fare [CU]

    50

    0.50

    100

    1.00

    200

    2.00

    300

    3.00

    400

    4.00

    500

    5.00

    600

    6.00

    > 600

    7.00

    The considered calculation contains four path legs: IC, RE, IC and ICE. The following tables
    show the calculation of the fare for the three different options for imposing fixed supplements:
    1. Supplement once per transport system:

    616

    PTVGROUP

    8.5.1.2 Transport system-specific supplements


    Path legs of
    the connection

    Fare points

    Base fare
    Fixed sup- Distance sup[CU] plement [CU] plement [CU]

    Minimum
    fare [CU]

    IC

    50

    4.00

    0.00

    0.00

    RE

    200

    0.00

    0.00

    0.00

    IC

    100

    (*) 0.00

    0.00

    0.00

    ICE

    50

    0.00

    (**) 0.50

    (***) 7.00

    Total

    400

    4.00

    0.50

    4.00

    Total fare

    8.50

    (*)0.00 CU, because the IC supplement was already imposed on the first path leg.
    (**)0.50 CU both for additive and proportional calculation of the distance supplement (see
    "Distance-based supplements" on page 618).
    (***) The minimum fare of 7.00 CU no longer has an effect, because the regular fare of 8.50
    CU is higher.
    2. Supplement only for the top-ranking transport system:
    Path legs of
    the connection

    Fare points

    Base fare
    Fixed sup- Distance sup[CU] plement [CU] plement [CU]

    Minimum
    fare [CU]

    IC

    50

    (*) 0.00

    0.00

    0.00

    RE

    200

    0.00

    0.00

    0.00

    IC

    100

    (*) 0.00

    0.00

    0.00

    ICE

    50

    0.00

    0.50

    7.00

    Total

    400

    0.00

    0.50

    4.00

    Total fare

    (**) 7.00

    (*)Only the fixed supplement of the top-ranking transport system (ICE) is obtained, even if
    in this case it is 0.
    (**)The ICE minimum fare is imposed, because the ICE is used and the regular fare of 4.50
    CU is lower than the ICE minimum fare.
    3. Supplement per path leg:
    Path legs of
    the connection

    Fare points

    IC

    50

    4.00

    0.00

    0.00

    RE

    200

    0.00

    0.00

    0.00

    IC

    100

    (*) 4.00

    0.00

    0.00

    ICE

    50

    0.00

    0.50

    (**) 7.00

    PTVGROUP

    Base fare
    Fixed sup- Distance sup[CU] plement [CU] plement [CU]

    Minimum
    fare [CU]

    617

    8.5.1.2 Transport system-specific supplements


    Path legs of
    the connection

    Fare points

    Total

    400

    Base fare
    Fixed sup- Distance sup[CU] plement [CU] plement [CU]
    4.00

    8.00

    Minimum
    fare [CU]

    0.50

    Total fare

    12.50

    (*)Different than in the first case, reimposition of fixed IC supplement.


    (**) The minimum fare of 7.00 CU no longer has an effect, because the regular fare of 12.50
    CU is higher.
    Distance-based supplements
    Each PuT transport system has its own fare stage for distance-based supplements. They are
    calculated exactly like distance-based base fares, therefore based on the number of fare
    points. The number of fare points for each transport system, is only summed up across those
    path legs which belong to lines of the transport system. Distance-based supplements are also
    added to the base fare of the ticket type.
    There are two variants, on how distance-based supplements can be read from the fare table of
    the distance stages:
    proportional calculation
    additive calculation
    This setting is a ticket type property. For proportional calculation, the distance supplement
    valid for the sum of fare points of all path legs is adopted from the fare table and then multiplied by the relative proportion of fare points of this transport system. The additive calculation
    is easier - the distance supplements for the number of fare points of the transport system are
    directly imposed for each transport system.
    The following calculation example compares the two options:
    Example: Calculation of distance-based supplements
    On a connection, 100 fare points are traversed using ICE and 50 using IC. The distance-based
    supplements are as follows:
    Number of fare points
    (FP)

    ICE supplement [CU]

    IC supplement [CU]

    3.00

    2.00

    <= 100

    4.00

    3.00

    <= 150

    5.00

    3.50

    Distance supplement for proportional calculation:

    618

    PTVGROUP

    8.5.2 Fare systems

    Distance supplement for additive calculation:

    8.5.2

    Fare systems
    A fare system is a set of lines which have the same fare logic. In principle the passenger can
    therefore use these lines with one ticket. A fare system could for example be an individual operator or a transport association.
    One or more ticket types are allocated to each fare system for each PuT demand segment.
    Example: Fare systems, ticket types and demand segments
    There are two demand segments which model whether a monthly pass is in possession or not.
    This differentiation is made in advance on the demand segment level, because purchasing a
    monthly pass is a long-term decision and not just when selecting the concrete connection.
    There are three fare systems included in the example: City, Metro and Long-distance rail. The
    three fare systems are completely impartial for passengers without a monthly pass, where
    there is a normal ticket and a short-distance ticket (with different properties) for both City and
    Metro. Monthly pass buyers are, however, offered the same ticket for City and Metro.
    Using the Visum demand segments, it is defined which PuT users are allowed to use which
    ticket types in which fare system. The following table provides an overview:
    DSeg "Passengers without a
    monthly pass"

    DSeg "Passengers with a monthly


    pass"

    Fare system City


    (Bus, Tram)

    Regular fare City (a Zonebased fare),


    Short-distance City (max. 10
    min)

    Monthly pass region

    Fare system
    Metro

    Normal fare metro


    (a distance-based fare),
    Short-distance Metro (max. 3
    stops)

    Monthly pass region

    Fare system Rail


    Single ticket rail
    long-distance
    Table 239: Linking fare systems and demand segments

    Monthly pass rail

    The fare system rank plays a role when lines belong to several fare systems, as can be seen
    in several examples subsequently (see "Procedure for ambiguous fare systems" on page
    624).

    PTVGROUP

    619

    8.5.2.1 "Fare reference" of a fare system


    8.5.2.1

    "Fare reference" of a fare system


    The most important fare system property is determining how far an individual ticket is valid.
    This may be an individual path leg, i.e. a new ticket has to be bought for each boarding. A
    second possibility would be that a ticket is valid for successive path legs within a fare system,
    and a new ticket only has to be bought when leaving the fare system and entering it again.
    Thirdly, a ticket may be valid for all path legs of a connection, which belong to the same fare
    system - even if path legs of other fare systems lie in between. All three cases are practice-related.
    The central fare system attribute Fare reference is used to model this aspect and can assume
    one of the following values:
    Each path leg separately: A ticket has to be bought for each path leg of the fare system.
    Each group of contiguous path legs: A ticket has to be bought for each group of contiguous path legs of a fare system.
    All path legs together: For all path legs together, i.e. for the whole trip, one ticket is sufficient for this fare system.
    Path legs which belong to another fare system, can never be used with the same ticket.
    Example: Fare system properties "Fare reference"
    We are looking at a connection with four path legs, with transport systems Bus Tram Train
    Bus. Using the above example of the three fare systems: Bus and Tram belong to the same
    fare systems City, therefore, the same ticket types are valid. The transport system Train
    belongs to the fare system Rail.
    To keep the example simple, let's assume the following ticket types:
    Regular fare City: 100 CU for all distances.
    Short-distance City: 60 CU for all trips up to max. 10 min. In the example, only the trip on
    the first bus is shorter than 10 min.
    Regular fare Rail: 200 CU for all distances.
    Even if the fare structure has been simplified, this example clearly shows, how the total fare
    changes subject to the fare-reference. Due to the fare reference, the following fares apply for
    the connection:
    Fare refers to...
    Path leg TSys

    Fare system

    Each path
    leg separately

    1 Bus

    City

    60
    (short
    distance)

    2 Tram

    100

    All path legs together

    100,
    also includes bus
    at the end

    100

    3 Train

    Rail

    200

    200

    200

    4 Bus

    City

    100

    100

    no extra fare

    460

    400

    300

    Fare sum
    620

    City

    Each group of contiguous path legs

    PTVGROUP

    8.5.2.1 "Fare reference" of a fare system


    In the first case the passenger pays for each path leg in the fare zone "City" individually
    and only for the first path leg is he allowed to use the short-distance ticket, because all
    other path legs have an operating time of more than 10 minutes.
    In the second case the successive path legs 1 and 2 can be used with the same ticket.
    Only in the third case do you only pay once for the entire fare zone "City".
    The third path leg is ignored, because the "Train" belongs to a separate fare system.
    The example of start and transfer fares are supplemented:
    Example: Fare reference and initial and transfer fares
    Supplement / deduction

    FS City

    FS Rail

    Initial fare

    100

    200

    Transfer fare from FS City to

    50

    -20

    Transfer fare from FS Rail to

    80

    Both fare systems therefore require an initial fare as a base value at trip start. Transfers within
    the same fare system cost 50 CU as additional charge for "City", for "Rail" no extra costs are
    charged. For a transfer from "Rail" to "City" an additional amount of 80 CU is charged, vice
    versa however, there is a discount of 20 for a transfer from "City" to "Rail".
    The table below displays the initial and transfer fares, which are added to the base fares listed
    above:
    Fare refers to...
    Path leg TSys

    Fare system

    Each path
    leg separately

    1 Bus

    City

    100

    Each group of contiguous path legs

    All path legs together

    100

    100,
    also includes bus
    at the end

    2 Tram

    City

    50

    3 Train

    Rail

    -20

    -20

    -20

    4 Bus

    City

    80

    80

    no extra fare

    Sum of
    initial and
    transfer
    fares

    210

    160

    80

    Fare sum
    (see
    above)

    460

    400

    300

    Total fare

    670

    560

    380

    PTVGROUP

    621

    8.5.2.2 Ticket selection in a fare system


    Even if the example is simple, you can see what great influence the "Fare-reference" has on
    the fare calculation and thus on the fare itself. It is therefore very important to define it according to the real fare conditions of the modeled network.
    8.5.2.2

    Ticket selection in a fare system


    In reality the ticket can not always be selected freely even if in principle several ticket types
    can be applied because there is usually a predefined order. This order is modeled in Visum
    by the rank of ticket types. It defines the hierarchy of the ticket types within the fare system.
    Taking the above example let's look at the case of an individual fare system, which has three
    different ticket types:
    1. Fare condition descriptions:
    1

    Normal fare

    The fare of the ticket type depends on the number of traversed fare
    zones as follows:
    1 fare zone: 2.00 CU
    2 fare zones: 3.00 CU
    3 fare zones: 3.50 CU
    4 or more fare zones: 4.00 CU

    Airport ticket

    All trips into or out of the special zone Airport are subject to a exception. They constantly cost 3.75 CU, independent of the fare zone at
    the other end point of the path.

    Short-distance
    fare

    For all trips up to ten minutes run time, a short-distance ticket can
    be used for the fare of 1.00 CU. These do not include trips from or
    to the airport.

    2. Modeling in Visum:
    To model these fare conditions, the three ticket types have the following properties:
    The airport ticket has the highest rank (for example 1), because it has to be used in all
    cases where it can be applied (for all trips from and to the airport)
    The airport ticket is a From-to zone-based fare, because the fare only depends on initial
    fare zone and target fare zone of the connection. In this fare matrix however, only those
    relations whose start or destination fare zone is the airport, are occupied. Other entries do
    not exist, which shows the restricted applicability.
    The short-distance ticket has the next higher rank (for example 2), because for all trips outside of the airport, it is always bought when it is applicable. A maximum duration of 10
    minutes is stipulated. There are however no threshold values for trip distance or number
    of stops.
    The normal (zone-based) fare has the lowest rank (for example 3). In principle the ticket
    can always be used, because the number of traversed zones provides a definite fare. The
    lower rank however, forces this ticket not to be used in the special cases airport trip or
    short-distance, but one of the other two.
    3. Examples for paths in this fare system (and its fares):

    622

    PTVGROUP

    8.5.2.3 Initial fare and transfer fare


    A trip over 20 minutes from fare zone city center to fare zone sports field leads through
    another fare zone university. These are three fare zones, the fare costs 3.50 CU.
    A trip over 8 minutes leads from fare zone city center to fare zone university. A shortdistance ticket applies, the trip costs 1.00 CU.
    A trip over 7 minutes and another over 12 minutes leads from fare zone university to fare
    zone airport. In each case the airport ticket for 3.75 CU applies.
    A trip within the fare zone also costs 3.75 CU.
    A trip over 45 minutes from fare zone university via fare zone airport leads to fare zone
    industrial park. The airport is not start or destination fare zone, the normal fare for three
    fare zones (3.50 CU) therefore applies.
    8.5.2.3

    Initial fare and transfer fare


    In the standard case, all fare systems are independent, so that the total fare for a connection is
    the sum of fares per fare system. Transfer fares allow modeling of interactions. Like the initial
    fare, they are added to the ticket type's basic fare for the fare system.
    The initial fare is only imposed for the first path leg and depends on the fare system of the first
    path leg. The transfer fare is calculated for each transfer, where a new ticket has to be bought.
    It depends on the fare systems of the lines, where the transfer is made.
    Both components can be negative for modeling deductions. The resulting total fare of a
    connection is however greater or equal to zero.
    Example:
    Initial and transfer fares (see ""Fare reference" of a fare system" on page 620)

    8.5.2.4

    Fare weights
    For the fare computation it is assumed that passengers have full knowledge of all fare systems. Thus, the minimum fare will be selected, if several fares applied to the connection taking
    the fare system ranks into account. Fare weights can be used to model restrictions to the assumption above. This is achieved by computing a 'perceived' fare for the alternatives on the
    basis of the fare weight. The perceived fare will only be regarded for the selection of the real
    fare.
    Example:
    Trip from C Town to A Town, part 3 (see "Procedure for ambiguous fare systems" on page
    624)

    8.5.3

    Fare calculation
    The total fare of a PuT connection is generally equal to the sum of fares for the individual fare
    systems, which occur on this path. Interactions can only be considered through transfer fares
    (see "Transport system-specific supplements" on page 615).
    Decisive is "those which occur on this path". If the fare system per path leg is clear, i.e. each
    used line (or the PuT supplement transport systems) belongs to exactly one fare system, fare
    calculation is split into separate blocks and the calculation within a block is carried out as described before (see "Ticket selection in a fare system" on page 622).

    PTVGROUP

    623

    8.5.3.1 Procedure for ambiguous fare systems


    This is also the case for the above example on "fare-reference", because the fare for the train
    line is completely independent of the fare calculation for the other three path legs (see "Example: Fare system properties "Fare reference"" on page 620). In such a simple situation, there is
    only one possible fare system combination, in step 1 of the algorithm on fare calculation (see
    "Algorithm for fare calculation" on page 627).
    The general case of several possible fare systems per path leg, however, requires an extension of the previously described modeling.
    8.5.3.1

    Procedure for ambiguous fare systems


    If lines belong to several fare systems, many possibilities will potentially occur for the selection
    of fare systems (and therefore tickets) on a connection. The following examples show typical
    situations, where such multiple-allocation is necessary.
    To systematically compare and determine all possibilities, fare systems also receive ranks,
    which expresses a specified order. First however, an example which does not need any ranks:
    Example: Fare calculation for ambiguous fare systems, trip to C Town, part 1
    Let's consider the following path legs:
    From

    To

    Line (TSys)

    Fare system

    A Town bus terminal

    A Town main station

    Bus 42 (Bus)

    City

    A Town main station B Town

    Regional train City or Rail

    B Town

    Intercity

    C Town

    Rail

    It is assumed, that on the middle path leg both City and Rail ticket types can be used, in particular all stops up to and including B Town belong to fare zones of the fare system City.
    The total path can therefore be used in two different ways (fare systems City-City-Rail or fare
    systems City-Rail-Rail), and the passenger selects the inexpensive one of the two.
    Note: In each of the two variants the regional train ticket may also apply for the path leg directly
    before or after the used line exactly then when the "fare-reference" of your fare system (City
    or Rail) is "Each group of contiguous path legs" or even "All path legs together". This aspect is
    however, not subject of the example
    If no ranks are assigned to the fare systems, all fare systems have the default rank 1, and there
    is no hierarchical order. All possibilities have to therefore be examined and the most inexpensive used, which is what this example wants.
    Example: Fare calculation for ambiguous fare systems, trip only to B Town
    Let's now look at the case, that the trip already ends in B Town:

    624

    PTVGROUP

    8.5.3.1 Procedure for ambiguous fare systems


    From

    To

    Line (TSys)

    Fare system (with rank)

    A Town bus terminal

    A Town main station

    Bus 42 (Bus)

    City (#1)

    Regional train

    City (#1) or Rail (#2)

    A Town main station B Town

    The validity range of the fare system City is not left and we assume, that the regional train in
    this case, is only allowed to be used with tickets from this fare system. This even applies, if it
    were more inexpensive to buy a Rail ticket from the main station.
    To model this ranking in Visum, the fare system City must have a higher rank (for example 1),
    than the fare system Rail (for example 2). Within the fare calculation the fare systems are regarded in descending rank order and the highest ranking used, which is applicable. Because for
    the rank 1 fare system a valid ticket already exists in this example, the rank 2 variant is not
    even reviewed.
    Example: Fare calculation for ambiguous fare systems, trip to C Town, part 2
    What does this definition of ranks now imply for the previous example, where explicitly both
    fare systems could be applied for the regional train line?
    From

    To

    Line (TSys)

    Fare system (with rank)

    A Town bus terminal

    A Town main station

    Bus 42 (Bus)

    City (#1)

    A Town main station B Town

    Regional train City (#1) or Rail (#2)

    B Town

    Intercity

    C Town

    Rail (#2)

    Compared to the case, that the trip ends in B Town, it is not possible to use the entire connection within the prior-ranking fare system City, because the intercity to C Town is not included. A
    rank 2 fare system is therefore inevitable on this path. This is the starting point for a definition
    of ranks of fare system combinations, which enable maximum flexibility when modeling such
    fare conditions.
    Note: The rank of a combination of fare systems T = {t1, t2,, tn} is defined as the maximum rank of one of its fare systems: Rank(T) := maxiRank(ti).
    With this specification one obtains an order on the set of all fare system combinations.
    This means in the course of fare calculation, Visum regards all of them and selects the
    most inexpensive total fare. Only if there are no valid combinations for a rank, will the
    combinations of the next lowest rank be considered.
    The global fall-back fare is only applied if no valid combination exists. This can be assigned with a value such as -1, to easily identify paths without valid ticket(s) after an assignment. If fares incur an assignment in the impedance definition, please note that a
    higher fall-back fare (e.g. 99999) prevents paths without a valid ticket(s) from being found
    and loaded.

    PTVGROUP

    625

    8.5.3.1 Procedure for ambiguous fare systems


    In the example, fare system combinations City-City-Rail and City-Rail-Rail are possible. Their
    ranks are the same, because max {1, 1, 2} = 2 and max {1, 2, 2} = 2. That is why none of the
    two are prior-ranking; the passenger in the regional train is therefore not fixed to the fare system City.
    By allocating rank 1 for fare system City and rank 2 for fare system Rail, it was overall achieved that the regional train within the City network can only be used with City tickets, but for
    trips across the network boundaries, it can also be used within the Rail fare system.
    Example: Fare calculation for ambiguous fare systems, trip from C Town to A Town bus
    terminal, part 3
    As in the previous example, for the trip in the opposite direction the same combinations of the
    same rank are returned from which the fare with the most favorable total fare is chosen. It is
    assumed, that a combination costs 35 (Rail) plus 5 (City-City), i.e. 40, whereas the other
    variant costs 40 (Rail-Rail) plus 2 (City), i.e. 42. On the basis of the previous assumptions
    it follows, that the fare for Rail-City-City is chosen. This choice presumes the pedestrians' full
    knowledge of all available fares. In reality, however, this is not always the case. Particularly it
    can be assumed, that visitors and other groups do not have detailed knowledge of regional
    fares like the City fare in our example, whereas the supra-regional Rail fare is well-known. To
    model, for example, that a passenger uses a certain fare system (which is Rail in the example)
    for a trip section which is as long as possible, the fare is weighted for the selection on the fare
    system level. This weight helps to determine a "perceived" fare, which is the basis for the selected fare. In other words, fare weights of 1 for the fare system Rail and 10 for City will change
    the choice, thus the fare Rail-Rail-City will be favorable (perceived fare is 40+20=60 compared to 85 for Rail-City-City).
    Example: Fare calculation for ambiguous fare systems, trip to C Town, part 4
    Let's now look at the variant, that the regional train itself goes to C Town:
    From

    To

    Line (TSys)

    Fare system (with rank)

    A Town bus terminal

    A Town main station

    Bus 42 (Bus)

    City (#1)

    A Town main station C Town

    Regional train City (#1) or Rail (#2)

    In this case it looks as if exactly like for trips to B Town the exclusive use of the City fare system is forced. However, this only applies if the City ticket can be bought up to C Town, if therefore all stops including C Town lie within fare zones which belong to the zone-based fare of
    the City fare system. If this is not the case, the attempt to use the connection with fare systems
    of rank 1 fails, and fare system Rail is applied on the second path leg.
    This makes it clear, that the affiliation of a line not automatically indicates, whether it can be
    used on its entire itinerary with tickets of this fare system. An even clearer example is the following:
    Example: Fare network with train fare system in the background
    1. Description of the network and the fare conditions:

    626

    PTVGROUP

    8.5.3.2 Algorithm for fare calculation


    A regional train line traverses the range of four fare systems (networks), which all together are
    zone-based fare systems. There are spatial overlaps between the first and the second as well
    as the second and the third.

    For trips on the regional train line within a fare system, ticket types of this fare system are mandatory. This also applies, if parts of the fare system area are traversed, which cover a different
    fare system. For trips across the boundaries of a fare system, however, ticket types of the fare
    system Rail long-distance definitely have to be used.
    This regulation still leaves the open question, which ticket type to buy, if one entirely travels in
    the covered section of two fare systems. The following regulation applies in this situation: In
    the covered sections of fare system 2 with fare system 1 and with fare system 3, the latter has
    precedence.
    2. Resulting modeling of the ticket type in Visum:
    Because the line can at least be partially used in all five fare systems, it has to be allocated to
    all fare systems. To express the precedence of fare systems 1 and 3 against fare system 2 in
    the covered sections of the fare zones, both must have a higher rank (for example 1), than fare
    system 2 (for example 2). The rank of fare system 4 is not important, it can be set to 3. The non
    zone-based fare system 5 (Rail long-distance) must have the lowest rank (for example 5),
    because each of the four zone fare systems have precedence, if a trip takes place within it.
    These ranks have a desired effect on the selection of the ticket type(s) through the following
    model:
    Each zone-based fare system has a specific fare zone type, for example 1, 2, 3 and 4, and corresponding ticket types with fare structure zone-based fare. The spatial overlap of zone fare
    systems arises in the overlap of their fare zones. All stops served by the line, thus lie exactly in
    one fare zone or in two fare zones of different types.
    This is how you achieve, that each of the zone-based ticket types can only be used, if all traversed stops lie within fare zones which belong to the fare system of the ticket. Two ticket types
    can only be used in the covered range of the fare systems and there the fare system ranks provide specified preference. The fare system "Rail long-distance" is used as a fall-back, because
    a valid ticket can be bought for this one in any case.
    8.5.3.2

    Algorithm for fare calculation


    The succession of all decisions which lead to the selection of the ticket(s) used on a path, can
    be formulated as an algorithm. This particularly clarifies the meaning of the ranks for fare systems and tickets.

    PTVGROUP

    627

    8.5.4 Application of fares


    Each path consists of a sequence of path legs. Each path leg has one PuT line which is
    connected to one or more fare systems (or a PuT-Aux transport system which is also allocated
    to fare systems). The algorithm on fare calculation is as follows:
    1. Determining fare systems:
    Go through all possible fare system combinations for the different path legs, i.e. in descending ranking order (whereas Rank of the combination = Maximum rank of the fare systems
    in the combination). Calculate the fare for each combination according to step 2. Select the
    lowest fare from the fare system combinations of the same weighted rank. Compared to the
    fare, for the weighted fare, the fare weight for each fare system is considered. If all fare systems of a rank are invalid, consider the combinations of the next rank. If there is no valid
    fare system combination, the global fall-back fare applies.
    2. Analysis of a fare system combination:
    If fixed fare systems are provided for all path legs, iterate over all fare systems used and calculate their fares according to step 3. If all calculations lead to a valid fare, the sum is a
    valid fare for the total path. If not, this fare system combination is invalid.
    3. Consideration of a fare system on all path legs allocated to it:
    According to the fare system attribute Fare reference, determine for which subsets of the
    fare system path legs separate ticket types have to be used. Iterate over all these path leg
    subsets and calculate their fares according to step 4. If all calculations supply a valid fare,
    the sum is a valid fare for the fare system. If not, fare calculation for this fare system fails.
    4. Consideration of a fare system of a path leg subset:
    For a fare system and a predefined path leg subset, iterate over all ticket types which are
    used by the fare system, in descending order. Calculate the fare for each ticket type according to step 5. From the ticket types of the same rank, select the one with the lowest fare. If
    all ticket types of a rank cannot be used, consider the ticket types of the next rank. If there is
    no applicable ticket type, the fare system is not permitted on this path leg subset.
    5. Consideration of a ticket type on a path leg subset:
    Calculate the base fare according to the fare structure of the ticket type (Distance-based
    fare, Zone-based fare, From-to zone-based fare, Short-distance fare). If the fare table does
    not contain a valid entry, the ticket type cannot be applied. Add up the initial fare for the first
    path leg of the path. Add up the transfer fare according to the fare system which was used
    on the preceding path leg.
    If distance-based supplements have been activated for the ticket type, calculate and add
    the distance-based supplement for the counted number of fare points. If the supplement
    table does not contain an appropriate entry, the ticket type cannot be applied. Determine
    and add up the fixed supplement. Compare the total fare with the minimum fares of all
    occurring transport systems and raise it if necessary.

    8.5.4

    Application of fares
    With a fare model, fares can be taken into account in both the headway-based assignment
    and the timetable-based assignment procedures. Alternatively, you can model a linear depen-

    628

    PTVGROUP

    8.6 PuT operating Indicators


    dence in terms of fare points measuring the traversed distance for the headway-based assignment.
    The following skim matrices can be derived from both PuT assignment types:
    Fare
    Number of traversed fare zones
    Please note that the skim "Number of fare zones" only counts those fare zones, which are relevant for determining the fare. If a ticket has priority (or is cheaper with the same rank), which
    has a different fare structure other than a "zone-based fare", fare zones on path legs of this
    ticket do not play a role and are not counted for the skim. This is necessary, because several
    fare zone systems, separated by type, may exist next to each other and each ticket type applies to fare zones of one type at the most. "The" number of fare zones does not exist.
    After an assignment you can access the ticket type used for each path leg, via the PuT path
    legs list and analyze both the fare and the revenue for each path leg.
    The difference between fare and revenue is, that fares always refer to the Visum fare model,
    revenues however can be calculated alternatively as a fixed revenue per passenger trip or as
    a revenue per fare point.
    Fares from the fare model can also be used as input data for Revenue calculation within the
    PuT operating indicators (see "Revenue calculation using the fare model" on page 663).

    8.6

    PuT operating Indicators


    Line costing calculations are based on operational indicators. They can be divided into the following categories:
    General indicators
    Indicators for the measurement of transport supply
    Indicators for the measurement of transport performance
    Indicators for the calculation of operating costs
    Indicators for the calculation of fare revenues
    Indicators for vehicle requirement and line blocking (see "Line blocking" on page 553).
    The indicators are described in the indicator categories. The following file lists the network
    objects you can calculate indicators for: IndicatorAvailability.xls, in the directory ...Program
    files\PTV Vision\PTV Visum 13\Doc\Eng of your Visum installation.
    Dependent on the indicator, different procedures have to be carried out, to calculate the indicator values. Some indicators are already available after a PuT assignment, others after the
    procedure PuT operating Indicators has been executed with certain settings. Furthermore, it
    also depends on whether indicators are calculated on the line hierarchy or for territories. The
    IndicatorSource.xls file, in the directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng of
    your Visum installation, contains an overview of the indicators, the procedures used to calculate them, and the calculation settings required. Basically, the following procedures are relevant for the calculation:
    PuT Operating Indicators
    Territory indicators

    PTVGROUP

    629

    8.6.1 Example for PuT operating indicators


    PuT assignment
    Line blocking
    The indicators are basically calculated for analysis period, analysis horizon and analysis time
    intervals (provided that analysis time intervals are defined). There are however exceptions,
    where there is no calculation for analysis time intervals. This is characterized in the indicator
    table (IndicatorAvailability.xls) as follows:
    AHP = available for analysis period and analysis horizon
    AHPI = available for analysis time intervals, analysis period and analysis horizon.
    X = indicator is available, but does not show a time reference

    8.6.1

    Example for PuT operating indicators


    The following example Example_LLE.ver (illustration 196) is used to illustrate the indicator calculations. The description of the indicator categories pick up this example again. You can find
    the example in the following directory: ...Users\Public\Public documents\PTV Vision\PTV
    Visum 13\Example_Net\.

    Illustration 196: Example network with two lines and volume data
    Transport Supply
    The transport system of the demonstration example consists of two lines with two line routes
    per line (outward and return line routes), but partially shortened trips.

    630

    PTVGROUP

    8.6.1 Example for PuT operating indicators


    Line

    Orig.
    Stop

    Dest.
    Stop

    Length First
    [km]
    dep.

    tCur
    [min]

    Last
    dep.

    Run
    time
    [min]

    Number of
    trips

    Valid day

    BUS >

    10

    40

    27.5

    06:07
    a.m.

    00:40

    06:07
    p.m.

    00:45

    19

    daily

    BUS <

    40

    10

    27.5

    06:02
    a.m.

    00:40

    06:02
    p.m.

    00:45

    19

    daily

    BUS >

    30

    40

    7.5

    05:37
    a.m.

    00:40

    05:37
    p.m.

    0.13

    19

    weekdays

    BUS <

    40

    30

    7.5

    06:29

    00:40

    06:29
    p.m.

    0.13

    19

    weekdays

    TRAIN >

    20

    40

    10.0

    06:29

    00:40

    06:29
    p.m.

    0.16

    19

    daily

    TRAIN <

    40

    20

    10.0

    06:09
    00:4a.m.
    0
    Table 240: Transport supply in Example_LLE.ver

    06:09
    p.m.

    0.16

    19

    daily

    Projection factors and analysis time slices


    The model contains an analysis time period TI1 for the traffic during morning peak hours (8
    a.m. to 9 a.m.). The projection factors on the analysis horizon for valid days are assigned accordingly (see User Manual: Chpt. 15.42 , page 1511).
    Valid day

    Proj. factor transport


    supply

    daily

    Proj. factor hourly costs

    365

    365

    weekdays
    260
    Table 241: Projection factors for the valid days in Example_LLE.ver

    260

    The projection factor for demand segment PuT is allocated as follows.


    Demand segment

    Projection factor

    PuT
    Table 242: Projection factor for the demand segment

    365

    Vehicles used
    Vehicle type

    Seat capacity

    Total capacity

    Standard bus

    35

    90

    Low floor bus

    35

    50

    Train
    200
    400
    Table 243: Total capacity provided in the vehicles of example Example_LLE.ver

    PTVGROUP

    631

    8.6.1 Example for PuT operating indicators


    Fare model
    The fare model includes two fare zones, which have been assigned the following stops.
    Number

    Name

    10

    A Village

    FZ100
    X

    FZ200

    20

    C Village

    30

    B Village

    40
    X City
    Table 244: Fare model in Example_LLE.ver

    Stop 30 (B village) is located exactly between fare zones FZ100 and FZ200 , and is therefore
    assigned to both fare zones.
    Tickets and Fares
    Fare zones

    One-way ticket
    [CU]
    One-way fare

    Four-trip ticket [CU]


    Fare

    Monthly pass [CU]

    One-way fare Fare

    One-way fare

    up to 2 fare zones

    1.00

    3.20

    0.80

    60.00

    1.50

    up to 3 fare zones

    2.00

    6.40

    1.60

    60.00

    1.50

    up to 4 fare zones

    3.00

    10.40

    2.60

    60.00

    1.50

    3.00

    80.00

    2.00

    as of 4 fare zones
    5.00
    12.00
    Table 245: Fares of the fare model in Example_LLE.ver

    Additionally, a supplement of 3.00 CU (currency units: for example, Euro, Pound, Dollar) is
    required for each rail ticket.
    Transport demand
    table 246 shows the number of passengers between the zones.
    FromZone

    ToZone

    Line1

    Line2

    A Village

    X City

    Bus1

    Train

    2,000

    X City

    A Village

    Train

    Bus1

    2,000

    A Village

    C Village

    Bus1

    200

    C Village

    A Village

    Bus1

    200

    C Village

    X City

    Train

    5,000

    X City

    C Village

    Train

    5,000

    B Village

    X City

    Bus1

    2,000

    X City

    B Village

    Bus1

    Total
    Table 246: Transport demand between the zones in Example_LLE.ver

    632

    Demand

    2,000
    18400

    PTVGROUP

    8.6.2 Indicators for line route and timetable evaluation


    Cost rates
    Link costs
    track charge of 100 CU/km on railway track between stop 20 and stop 40, plus depreciation charge of 100000 CU. All other links have a utilization fee of 10 CU/Km and running costs of 20 CU in the analysis horizon.
    Vehicle costs
    Standard bus
    Cost rate per hour
    [CU/h]
    Cost rate per km
    [CU/km]

    Low floor bus

    Train

    Service

    Empty

    Service

    Empty

    Service

    Empty

    300.00

    200.00

    300.00

    200.00

    700.00

    500.00

    5.00

    5.00

    5.00

    5.00

    10.00

    10.00

    Cost rate per vehicle


    [CU/Veh/AP]

    7000.00

    7000.00

    20000.00

    Table 247: Cost rates for vehicles in Example_LLE.ver


    In addition, a charge of 50CU/h is due for each vehicle combination Train.
    The operator costs amount to annual administrative costs of 1000 CU for the bus operator
    and 5000CU for the train operator as well as depreciation costs of 100000CU each.

    8.6.2

    Indicators for line route and timetable evaluation


    The following indicators comprise line data, which are made up of the line route and the timetable. Demand data is not required for calculation.
    Indicator

    Description

    Line network
    length (directed)

    Sum of link lengths of the links traversed by line routes. Traverses a line
    route a link more than once, it is only counted once.

    Line network
    length (undirected)

    Compared to the directed line network length, for links which are traversed in both directions, only the undirected values (this means, the
    mean value from the lengths of both directions) is counted. If the link is
    only traversed in one direction, the undirected length corresponds to the
    directed length.

    Network length Total length of links open to transport system. The length of both direc(directed)
    tions is included in the calculation.
    Network length Compared to directed network length, for links the average link length
    (undirected)
    (this means the mean value from the lengths of both directions) is counted
    for both open directions.
    Number of
    lines

    PTVGROUP

    The meaning of this indicator depends on the network object for which it
    is calculated.
    Main lines take the number of lines into consideration, which belong
    to the main line.
    PuT operators take the number of lines into consideration, which are

    633

    8.6.2 Indicators for line route and timetable evaluation


    Indicator

    Description
    operated by the PuT operator.
    Blocks take the number of lines into consideration, which are traversed on a block.
    Links take the number of lines into consideration, which traverse a
    link.
    Transport systems take the number of lines into consideration, which
    use this transport system.
    For zones / main zones, a line is regarded, if the zone is connected to
    a node with a stop point, which is traversed by the line. No line trip
    has to serve the stop point
    Stops take the number of lines into consideration, which traverse this
    stop. No line trip has to serve the stop
    Stop points take the number of lines into consideration, which traverse this stop point. No line trip has to serve a stop point.

    Num lines
    TSys

    Additionally returns the number of lines for each transport system. Otherwise, the indicator is analog to the number of lines.

    Num line routes

    Number of line routes of a line or number of line routes run by a vehicle


    combination during a block.

    Number of
    stop points
    total

    Number of stop points, which lie within a territory polygon.

    Number of
    Number of served stop points, which lie within a territory polygon. A stop
    stop points ser- point is served, when it is traversed by a line route. Thus, a line route item
    ved
    with this stop point is required and for the respective time profile item boarding or alighting has to be possible. It is not necessary that trips serve this
    stop point.
    Stops served

    634

    The meaning of this indicator depends on the network object for which it
    is calculated.
    Territory PuT detail regards the number of served stops being located
    within a territory polygon. Stops are not served, if none of the time profiles includes a stop at one of the stop's stop points. Multiple stops
    within a stop are only counted once
    Lines take the number of stops into consideration, which are traversed by a line. This is independent of whether a stop at the respective stop point is intended in the time profile or not
    Line routes regard the number of served stops, which are traversed
    by the line route. This means, that stops are not served, if no time profile contains a stop at one of the stop's stop points
    Time profiles take the number of stops into consideration, for which a
    stop is intended for its stop points, in the TP
    Vehicle journeys take the number of stops into consideration, where
    a vehicle journey stops

    PTVGROUP

    8.6.2 Indicators for line route and timetable evaluation


    Indicator

    Description
    Transport systems take the number of stops into consideration, which
    a transport system traverses. This is independent of whether a stop
    (boarding or alighting) is intended in the respective time profiles

    Stop events

    Number of stop events at stops within the territory polygon. All stop events
    at the stops are counted. A trip is thus counted several times, if a trip stops
    at several stop points within the stop. If a stop point lies in another territory
    than the respective stop, the stop still counts for the stop in the territory.
    The number of stop events in the territory counts for each vehicle journey
    and is aggregated for the other levels, if necessary. Different from the indicator "Stop points served" trips are required. Otherwise stop events do not
    count.

    Start stop
    events

    Number of vehicle journeys, which start at a stop in the territory.

    End stop
    events

    Number of vehicle journeys, which end at a stop in the territory.

    Earliest depar- Earliest departure from stop point located inside territory. This is the earture
    liest departure within the analysis time slice, not necessarily the first
    departure of the day (for example, departure at 12:20 a.m.).
    Latest arrival

    Latest arrival at stop point located inside territory. This is the latest arrival
    within analysis time slice, not necessarily the last departure of the day (for
    example, arrival at 11:59 p.m.).

    Stop time

    The stop time, which accumulates from stop events at stop points within
    the territory polygon. The stop time is made up of the input attribute Stop
    time at the time profile items.

    Number of PuT The meaning of this indicator depends on the network object for which it
    departures
    is calculated. The indicator is especially interesting for time interval-related analyses, to determine the departures within a certain time interval for
    example.
    For main lines / lines it returns the number of vehicle journeys run by
    this line.
    For line routes it returns the number of vehicle journeys run by this
    line route
    For time profiles it returns the number of vehicle journeys using this
    time profile
    For PuT operators it returns the number of vehicle journeys operated
    by this PuT operator
    For transport systems it returns the number of vehicle journeys operated with this transport system
    For stops it returns the number of vehicle journeys which stop for boarding. Stop events at several stop points within the stop are counted
    repeatedly. If a stop is traversed several times within a vehicle journey, the departures are also counted repeatedly

    PTVGROUP

    635

    8.6.2 Indicators for line route and timetable evaluation


    Indicator

    Description
    For stop points it returns the number of vehicle journeys which stop
    for boarding.

    Number of
    departuresTSys

    In contrast to Number of PuT departures, the number of departures is


    returned by transport system. Calculation is otherwise analog.

    Number of PuT Number of vehicle journeys, which stop for alighting at the stop or the stop
    arrivals
    point. Multiple stop events are counted several times for a stop.
    Number of arri- In contrast to Number of PuT arrivals, the number of arrivals is returned
    vals-TSys
    by transport system. Calculation is otherwise analog.
    Number of ser- The meaning of the indicator depends on the network object for which it is
    vice trips
    calculated:
    uncoupled
    For a vehicle journey it is the number, how often this vehicle journey
    has been carried out in the particular time slot (AH, AP, TI)
    For vehicle journey items it is returned, how often this vehicle journey
    traverses the respective vehicle journey item (crucial are start and
    end stop points of the vehicle journey). It is irrelevant whether boarding or alighting is permitted
    For time profiles, the number of vehicle journeys is returned which
    use the time profile in the particular time slot
    For time profile items, the number of vehicle journeys is returned
    which traverse the time profile item in the particular time slot (crucial
    are start stop point and end stop point of the vehicle journey). It is irrelevant whether boarding or alighting is permitted
    For main lines/lines/line routes, the number of vehicle journeys in the
    time slot is returned
    For the line route course, the number of vehicle journey services traversing the line route item is returned (start and end stop point of the
    trip are decisive, it is irrelevant whether boarding or alighting is permitted)
    For territory analyses, the number of vehicle journeys which are carried out in the territory in the time slot is returned. A vehicle journey is
    added to the territory, if at least one stop of the vehicle journey lies
    within the territory The stop point location is not crucial, but the stop
    location.
    For PuT operators, the number of vehicle journey services in the time
    slot of the operator's vehicle journeys is returned
    For line blocks, the number of occurrences of vehicle journeys in the
    line block is returned
    For links, the number of services in the time slot of vehicle journeys
    which traverse a link is returned. A link is regarded as if being traversed, if the vehicle journey traverses more than 50% of the link's
    length
    For a transport system, the number of vehicle journey services in the

    636

    PTVGROUP

    8.6.2 Indicators for line route and timetable evaluation


    Indicator

    Description
    time slot of vehicle journeys using this transport system is returned
    For zones, a vehicle journey counts for a zone, if the zone is connected via a node which is the access node to a stop area, and if the
    vehicle journey stops at one of the stop points of the same stop for
    passenger boardings/alighting
    For a stop the number of vehicle journeys is returned which stop at
    the stop for passenger boarding/alighting in the particular time slot.
    Multiple stop events at stop points of the stop are counted several
    times
    For a stop point the number of vehicle journeys is returned which stop
    at the stop point for passenger boarding/alighting in the particular
    time slot

    Number of ser- In contrast to the indicator Number of service trips uncoupled, coupled
    vice trips
    vehicle journeys count as one vehicle journey for this indicator. If two
    vehicle journeys have been coupled in a section, the vehicle journey item
    attribute has value 0.5 for each service within the particular time slot, and
    0.33 if three vehicle journeys have been coupled, etc. Accordingly, coupled departures count as one departure in the stop point attribute, for
    example.
    Since a vehicle journey, a time profile and a line route can be coupled by
    section, this indicator can only be returned for network objects with a unique location reference. For line routes, time profiles and vehicle journeys,
    it cannot be returned.
    For vehicle journey items it is returned, how often this vehicle journey
    traverses the respective vehicle journey item (crucial are start and
    end stop points of the vehicle journey). Coupled vehicle journeys
    count proportionally. It is irrelevant whether boarding or alighting is
    permitted
    For time profile items, the number of vehicle journeys is returned
    which traverse the time profile item in the particular time slot (crucial
    are start stop point and end stop point of the vehicle journey). Coupled vehicle journeys count proportionally. It is irrelevant whether
    boarding or alighting is permitted.
    For line route items, the number of vehicle journeys is returned which
    traverse the line route item in the particular time slot (crucial are start
    stop point and end stop point of the vehicle journey). Coupled vehicle
    journeys count proportionally. It is irrelevant whether boarding or
    alighting is permitted.
    For links, the number of services in the time slot of vehicle journeys
    which traverse a link is returned. A link is regarded as if being traversed, if the vehicle journey traverses more than 50% of the link's
    length. Coupled vehicle journeys count proportionally.
    For zones, a vehicle journey counts for a zone, if the zone is connec-

    PTVGROUP

    637

    8.6.2 Indicators for line route and timetable evaluation


    Indicator

    Description
    ted via a node which is the access node to a stop area, and if the
    vehicle journey stops at one of the stop points of the same stop for
    passenger boardings/alighting. Coupled vehicle journeys count proportionally.
    For a stop the number of vehicle journeys is returned which stop at
    the stop for passenger boarding/alighting in the particular time slot.
    Multiple stop events at stop points of the stop are counted several
    times. Coupled vehicle journeys count proportionally.
    For a stop point the number of vehicle journeys is returned which stop
    at the stop point for passenger boarding/alighting in the particular
    time slot. Coupled vehicle journeys count proportionally.

    Number of service trips


    (vehicle combination)

    For PuTDetail evaluations this indicator only differs from the Number of
    service trips uncoupled, if there are vehicle journeys with several
    vehicle journey sections and these differ in terms of the vehicle combination. In contrast to Number of service trips uncoupled the number of
    service trips is distributed to the vehicle journey sections in this case. If
    vehicle journey sections differ only in terms of the valid days, the values
    Number of service trips (vehicle combination) and Number of service
    trips uncoupled will match. Therefore, the evaluation of this indicator is
    useful for territory analyses only for levels in combination with
    xVehComb.

    Number of ser- In contrast to Number of service trips, the number of vehicle journeys is
    vice trips-TSys returned by transport system. Calculation is otherwise analog. Especially
    coupled vehicle journeys only count proportionally.
    Mean service
    trip length

    Calculation is dependent on the network object.


    For a transport system, service km / number of service trips applies
    Otherwise, service km / number of departures applies

    Mean service
    time

    Calculation is dependent on the network object.


    For a transport system, service time / number of service trips applies
    Otherwise, service time / number of departures applies

    Is coupled

    (Respective) time profile is coupled with another time profile (1) or not coupled (0).

    Effectively cou- An effective coupling means the following: a vehicle journey, which is coupled
    pled with another vehicle journey via its corresponding time profile, is
    really carried out (in other words: at least one vehicle journey service is
    required for each of the coupled time profiles, these vehicle journeys
    have to be active and require a valid 'valid day'. For a valid valid day, the
    valid day is within the analysis period and both coupled vehicle journeys
    are carried out on the same day).
    Table 248: Indicators for line route and timetable evaluation

    638

    PTVGROUP

    8.6.3 Measurement of the transport supply


    Calculation example: Number of departures per transport system
    Number of departures for analysis period = number of vehicle journeys, which depart on
    Jan 02, 2006
    For the bus, the number of departures (AP) = 76 (Trips no. 96 to 172)
    For the train, the number of departures (AP) = 38 (Trips no. 58 to 95)
    Number of departures for analysis horizon = Num Departures (AP) projection factor of
    valid day
    For the bus, the number of departures is calculated (AH) = 38 365 + 38 260 = 23750
    For the train, the number of departures is calculated (AH) = 38 365 = 13870
    Number of departures for analysis time period TI1 = Number of vehicle journeys, whose
    departure time lies between 8a.m. and 9a.m.
    For the bus, the number of departures results from (TI1) = 7 (Trip no. 99, 100, 119, 120, 138,
    139, 157)
    For the train, the number of departures results from (TI1) = 3 (Trip no. 61, 80, 81)
    Calculation example: Number of service trips per transport system
    For the analysis period and the analysis horizon, the number of service trips complies with the
    number of departures in this example. The difference between the two indicators can be seen
    when looking at the analysis time interval TI1. Now also vehicle journeys are counted, whose
    departure does not lie in the time interval between 8:00 a.m. and 9:00 a.m., though they are
    running in this time slice.
    Number of service trips analysis time interval TI1 = number of vehicle journeys between
    08:00AM and 09:00AM.
    For the bus, the resulting number of service trips (TI) = 10 (Trip no. 98, 99, 100, 118, 119,
    120, 138, 139, 156, 157)
    For the train, the resulting number of service trips (TI) = 4 (Trip no. 60, 61, 80, 81)

    8.6.3

    Measurement of the transport supply


    Transport supply indicators express operational efforts in length units or in time units. Demand
    data is not required for their calculation.
    Indicator

    Description

    Service kilometers

    Kilometers traversed by vehicle journeys. Trip length via all vehicle journeys and number of departures.

    Section service
    kilometers

    Compared to ServiceKm, the length of each individual vehicle journey


    section is added (as long as it lies within the analysis period).

    Service time

    Time required by vehicle journeys. Trip length via all vehicle journeys
    and number of departures.

    Section service
    time

    Compared to service time, the duration of each individual vehicle journey section is added (as long as it lies within the analysis period). Also
    the dwell time between adjacent vehicle journey sections is included.

    Empty kilo-

    Kilometers traversed by empty trips. Compared to vehicle journeys, no

    PTVGROUP

    639

    8.6.3 Measurement of the transport supply


    Indicator

    Description

    meters

    passengers are carried on empty trips.


    Empty kilometers = Pull-out kilometers + Interlining kilometers + Pull-in kilometers

    Section empty
    kilometers

    Compared to EmptyKm, the length of each individual vehicle journey


    section is added (as long as it lies within the analysis period).

    Empty time

    Time required by empty trips. Compared to vehicle journeys, no passengers are carried on empty trips.
    EmptyTime = Pull-out time + Interlining time + Pull-in time

    Section Empty
    Time

    Compared to empty time, the duration of each vehicle journey section is


    added (as long as it lies within the analysis period).

    Operating kilometers

    Operating kilometers = Service kilometers + Empty kilometers

    Section opeCompared to EmptyKm, the length of each individual vehicle journey


    rating kilometers section is added (as long as it lies within the analysis period).
    Out-of-depot
    time

    Operating time = Service time + Empty time

    Section operating time

    Compared to operating time, the duration of each vehicle journey section is added (as long as it lies within the analysis period).

    Stop time

    Stop time of all stop events

    Section stop
    time

    In contrast to a stop time, the stop times of overlapping vehicle journey


    sections are counted multiple times.

    Seat capacity

    Sums up the number of seats of the vehicle combinations over all


    vehicle journey sections of the object, for which the indicator is determined (e.g. lines). This attribute is only available for the elements of the
    line hierarchy and for PuT operators and transport systems.

    Seat Kilometers Seat Km = Section Service Km Number of seats of vehicle combinations


    Summed up over all vehicle journey sections and number of departures.
    Seat Hours

    Seat Hours = Section Service Time Number of seats of vehicle combinations

    Summed up over all vehicle journey sections.


    Total capacity

    Sums up the total seating and standing capacity of the vehicle combinations over all vehicle journey sections of the object, for which the
    indicator is determined (for example, lines). This attribute is only available for the elements of the line hierarchy and for PuT operators and transport systems.

    Total Capacity
    Kilometers

    Total Capacity Km = Section Service Km Total seating and standing capacity of the
    vehicle combinations

    Summed up over all vehicle journey sections.


    Total Capacity
    Hours

    Total Capacity Hours = Section Service Time Total seating and standing capacity of the
    vehicle combinations

    Summed up over all vehicle journey sections.

    640

    PTVGROUP

    8.6.3 Measurement of the transport supply


    Indicator

    Description

    Length

    Length covered by the time profile items in the territory (attribute is only
    available via Territory - PuT Detail, for level Territory x Time profile (x
    Vehicle combination) and Territory X Vehicle journey (x Vehicle combination)).

    Run time

    Travel time used to cover the time profile items in the territory, (attribute
    is only available via Territory - PuT Detail, for level Territory x Time profile (x Vehicle combination)).

    Mean Speed

    Mean speed = Service kilometers / Service time

    Capacity PuT
    Seats

    Number of seats of vehicle combinations, which traverse this link, summed up over all vehicle journey sections (Attribute is only available for
    links).

    Capacity PuT
    total

    Total seating and standing capacity of the vehicle combinations, which


    traverse this link, summed up over all vehicle journey sections and the
    number of departures (Attribute is only available for links).

    Number of
    Vehicles (in proportion to
    length)

    The number of vehicles which are - according to the current block version - required for the reference object, (line, line route, etc.). The indicator value corresponds to the number of blocks, which cover the
    vehicle journey sections of the reference object. If a block covers vehicle
    journey sections of several objects, for the vehicle only the proportion of
    the vehicle journey sections of the reference object is added to the line
    length of all vehicle journey sections.

    Number of vehic- As above, but the addition to the reference object is instead carried out
    les (in prowith the share of vehicle journey sections of the reference object in the
    portion to time) service time of all vehicle journey sections.
    Table 249: Indicators of the transport supply
    Calculation example: Service kilometers per transport system
    Service km for the analysis period = Number of trips (AP) Trip length.
    For the bus it applies that ServiceKm (AP) = 38 27.5km + 38 7.5km = 1,045km + 285km
    = 1,330km
    For the train it applies that ServiceKm (AP) = 38 10km = 380km
    Service km for the analysis horizon = Service km (AP) Projection factor of the valid day
    For the bus it applies that ServiceKm (AH) = 1045km 365 + 285km 260 = 455525km
    For the train it applies that ServiceKm (AH) = 380km 365 = 138700 km
    Service km for the analysis time interval TI1 results from summing up the km data from all
    trip sections, whose respective line route items depart in this time slice
    For the bus it applies that ServiceKm (TI1) = 113.75km. The calculation is made clearer by
    illustration 197.

    PTVGROUP

    641

    8.6.3 Measurement of the transport supply

    Illustration 197: Calculation of service kilometers between 8 a.m. and 9 a.m.


    For the train it applies that ServiceKm (TI1) = 3 10km = 30km (Trip numbers 61, 80, 81)
    Calculation example: Seat km per transport system
    Seat km for the analysis period = ServiceKm (AP) Number of seats summed up over all
    trip sections.
    For the bus it applies that SeatKm (AP) = 1330km 35 = 46550km
    For the train it applies that SeatKm (AP) = 380km 200 = 76000km
    Seat km for the analysis horizon = Seat km (AP) Projection factor of the valid day summed up over all trip sections.
    For the bus it applies that SeatKm (AH) = 38 262.5 km 260 + 38 962.5 km 365 =
    15,943.375 km
    For the train it applies that SeatKm (AH) = 76000km 365 = 27740000km
    For seat km in the analysis time interval TI, the calculation is analog to the service km calculation (illustration 197).
    For the bus it applies that SeatKm (TI) = 35 (27.5 + 3.75 + 15 + 12.5 + 5 + 27.5)km + 35
    (7.5 + 7.5 + 7.5) = 3,981.25km
    For the train it applies that SeatKm (TI) = 30km 200 = 6000km

    642

    PTVGROUP

    8.6.4 Measurement of the network performance


    Calculation example: Service time per transport system
    Service time for the analysis period = Num PuT Departures (AP) Times from Time profiles
    For the bus it applies that ServiceTime (AP) = 38 45min + 38 13min = 2204min = 36h
    44min
    For the train it applies that ServiceTime (AP) = 38 16min = 608min = 10h 8min
    Service time for the analysis horizon = Service time (AP) Projection factor of the valid day
    summed up over all trip sections.
    For the bus it applies that Service time (AH) = 38 45min 365 + 38 13min 260 =
    752590min = 12543h 10min
    For the train it applies that Service time (AH) = 38 16min 365 = 221920min = 3698h
    40min
    Service time for the analysis time interval TI: Calculation is done analog to the service kilometer calculation (illustration 197).
    For the bus it applies that service time (TI) = 45min + 13min + (5km/10km) 13min +
    12min + (5km/10km) 20min + 13min + 13min + (5km/10km) 20min + 0min +
    (5km/10km) 12min + 45min + 13min = 186.5min = 3h 10min
    For the train it applies that Service time (TI) = 3 16min = 48min
    Calculation example: Mean speed per PuT line
    Mean speed = ServiceKm(AP) / ServiceTime (AP)
    For the bus it applies that vMean = 1330km / 36h 44min = 36.2km/h
    For the train it applies that vMean = 380km / 10h 8min = 37.5km/h

    8.6.4

    Measurement of the network performance


    The indicators of the network performance result from the PuT line use by passengers. For the
    calculation of the indicators, the volumes have to be available from the PuT assignment. Some
    of the indicators are automatically calculated during assignment (see overview table IndicatorSource.xls, in the directory: ...Program files\PTV Vision\PTV Visum 13\Doc\Eng).
    Indicator

    Description

    Passenger kilometers
    (DSeg)

    The link that passengers are driving with the PuT vehicle

    Passenger hours
    (DSeg)

    Time which the passengers spend in the PuT vehicle

    Passenger trips
    TSys (DSeg)

    Repeated boarding the same transport system is not counted more


    than once (for example transferring from one bus into another).

    Passenger trips
    Unlinked / Passenger trips Unlinked PuT

    Unlinked passenger trips match the number of boarding passengers


    per object. Counts each passenger using at least one line route item
    in the territory. No passengers are counted for path legs that end
    exactly at the start or start exactly at the end of a time interval.

    PTVGROUP

    Passenger kilometers = Passenger trips unlinked trip distance from Boarding to


    Alighting stop

    Passenger hours = Volume Duration

    643

    8.6.4 Measurement of the network performance


    Indicator

    Description

    PTrips Unlinked PuT Number of passengers boarding per object additionally difDSeg
    ferentiated according to demand segments. This attribute is only
    available for zones.
    PTrips Unlinked
    >2xTransfer
    (DSeg)

    Passenger trips with 3 or more transfers on their way from origin


    zone to destination zone. This attribute is only available for the elements of the line hierarchy.

    PTrips Unlinked with Passenger trips without transfer on their way from origin zone to des0xTransfer
    tination zone. This attribute is only available for the elements of the
    line hierarchy.
    (DSeg)
    PTrips Unlinked with Passenger trips with exactly one transfer on their way from origin
    1xTransfer
    zone to destination zone. This attribute is only available for the elements of the line hierarchy.
    (DSeg)
    PTrips Unlinked with Passenger trips with exactly two transfers on their way from origin
    2xTrans
    zone to destination zone. This attribute is only available for the elements of the line hierarchy.
    (DSeg)
    PTrips Unlinked
    DSeg

    Number of boarding passengers per object additionally differentiated according to demand segments. This attribute is only
    available for the elements of the line hierarchy.

    Mean volume per


    trip

    Mean volume per trip = passenger kilometers / service kilometers

    Mean volume to
    seat capacity ratio

    Mean volume to seat capacity ratio = passenger kilometers / seat kilometers 100

    Volume seat capacity ratio

    Volume seat capacity ratio = volume / seat capacity 100

    Mean vol/cap ratio


    total

    Mean volume total capacity ratio = passenger kilometers / total capacity kilometers
    100

    (This attribute is only available for the elements of the line hierarchy.)
    (always starting from the journey item. This attribute is only available
    for the elements of the line hierarchy.)

    (This attribute is only available for the elements of the line hierarchy.)
    Total vol/cap ratio

    Total volume capacity ratio = volume / total capacity 100

    (always starting from the journey item. This attribute is only available
    for the elements of the line hierarchy.)
    Total vol/cap ratio
    PuT

    Volume capacity ratio PuT total = volume / total capacity 100

    Boarding passengers (DSeg)

    Number of boarding passengers.

    This attribute is only available for the elements of the line hierarchy.
    Boarding passengers = Origin boardings + Direct transfers + Transfers Walk-Board

    (This attribute is only available for the line hierarchy, for stops and
    stop points.)

    644

    PTVGROUP

    8.6.4 Measurement of the network performance


    Indicator

    Description

    Alighting passengers (DSeg)

    Number of alighting passengers.


    Alighting passengers = Destination alightings + Direct transfers + Passengers transferring alight-walk

    (This attribute is only available for the line hierarchy, for stops and
    stop points.)
    PassOrigin
    (DSeg)

    Number of boarding passengers, which have this stop as their origin. Passengers which transfer here are therefore not counted. (This
    attribute is only available at stops and stop points.)

    PassDestination
    (DSeg)

    Number of alighting passengers, which have this stop as their destination. Passengers which transfer here are therefore not counted.
    (This attribute is only available at stops and stop points.)

    PassThrough

    Number of through-going passengers. These are all passengers traveling with a line, which traverses this item of a line route / time profile / vehicle journey, however, they neither board nor alight here
    (This attribute is only available for the elements of the line hierarchy).

    PassThrough with
    stop (DSeg)

    Number of passengers with stop event. These are all passengers


    traveling with a line which stops at this stop point, however, they neither board or alight here (This attribute is only available for stops and
    stop points).

    PassThrough
    without stop (DSeg)

    Number of through passengers without stop event. These are all


    passengers traveling with a line, which passes the stop point, but
    does not stop there.
    (This attribute is only available for stops and stop points.)

    PassTransfer

    Number of passenger transfers in the territory


    (This attribute is only available for territories).

    PassTransTotal
    (DSeg)

    Total number of passengers transferring at this stop or stop point


    Passenger Transfers = Direct transfers + Passengers transferring walk-board + Passengers transferring alight-walk

    (This attribute is only available for stops and stop points.)


    PassTransAlightWalk (DSeg)

    Number of passengers alighting at this stop or stop point and walking to another stop or stop point for transfer
    (This attribute is only available for stops and stop points.)

    PassTransDir
    (DSeg)

    Number of passengers transferring to another line at this stop or


    stop point.
    (This attribute is only available for stops and stop points.)

    PassTransWalkBoard (DSeg)

    Number of passengers boarding at this stop or stop point after walking from another stop or stop point.
    (This attribute is only available for stops and stop points.)

    Table 250: Indicators of the network performance

    PTVGROUP

    645

    8.6.4 Measurement of the network performance


    Calculation example: Passenger trips per line
    Number of Passenger trips per analysis period
    For the bus it applies that 8400 = 200(A->C) + 200(C->A) + 2000(A->X) + 2000(X->A) +
    2000(B->X) + 2000(X->B)
    For the train it applies that 12000 = 5000(C->X) + 5000(X->C) + 1000(A->X) + 1000(X->A)
    Passenger trips 0 transfers analysis period
    For the bus it applies that 6400 = 400(A<->C) + 2000(A<->X direct) + 4000(B<->X)
    For the train it applies that 10000 = 5000(C<->X) + 5000(X->C)
    Passenger trips 1 transfer analysis period
    For the bus it applies that 2000 = 2000(A<->X with transfer between bus and train)
    For the bus it applies that 2000 = 2000(A<->X with transfer between bus and train)
    Calculation example: Passenger kilometers per line
    The value Passenger kilometers per analysis period is calculated as follows: PassKm(AP)
    = Passenger trips trip distance from Boarding to Alighting stop
    For the bus it applies that 2400 10km(A<->C) + 2000 27.5km(A<->X) + 4000 7.5km
    (B<->X) = 109000
    For the train it applies that 12000 10km(C<->X) = 120000
    Note: Unlike the calculation of transport supply indicators, the projection factor of the
    demand segment is regarded for the network performance indicators' projection to the
    analysis horizon (AH) (see User Manual: Chpt. 15.11.3 , page 1061).
    The value Passenger kilometers per analysis horizon is calculated as follows: PassKm
    (AH) = PassKm(AP) Projection factor of the demand segment summed up over all
    demand segments.
    For the bus it applies that 109000km 365 = 39785000km
    For the train it applies that 120000km 365 = 43800000km
    Passenger kilometers per analysis time interval TI:
    For the bus it applies that 9660km. The calculation can be taken from illustration 198:

    646

    PTVGROUP

    8.6.4 Measurement of the network performance

    Illustration 198: Calculation of passenger kilometers between 8:00 a.m. and 9:00 a.m.
    For the train it applies that 3 10km 316 = 9480km
    Calculation example: Passenger hours per transport system
    The value Passenger hours per analysis period is calculated as follows: PassHour(AP) =
    Passenger trips Run time from Boarding to Alighting stop.
    For the bus it applies that 2400 12min + 2000 45min + 4000 13min = 2846h 40min
    For the train it applies that 12000h 16min = 3200h
    The value Passenger hours per analysis horizon is calculated as follows: PassHour(AH) =
    PassHour(AP) Projection factor of the demand segment summed up over all demand
    segments.
    For the bus it applies that 2846h 40min 365 = 1039033h 20min
    For the train it applies that 3200h 365 = 1168000h
    The value Passenger hours per analysis time period TI is calculated as follows.
    For the bus it applies that 255h 55min. The calculation can be taken from illustration 199.

    PTVGROUP

    647

    8.6.5 Calculation of operating costs and fare gains (revenues)

    Illustration 199: Calculation of passenger kilometers between 8a.m. and 9a.m.


    For the train it applies that 3 16min 316 = 252h 48min

    8.6.5

    Calculation of operating costs and fare gains (revenues)


    illustration 200 gives an overview of the cost and revenue model in Visum and its interrelations with the assignment results. The attribute names are bold in the depiction. Various
    settings have to be made (see User Manual: Chpt. 20.3.2 , page 2156).

    648

    PTVGROUP

    8.6.6 Calculation of the operating costs

    Illustration 200: Calculation schema for costs and revenues


    Note: Please note that the reference period for costs and the reference period for revenues have to match, in order to get reasonable cost coverage results. The revenues are
    calculated for the assignment time interval. The attribute OD trips total indicates the number of passenger trips in the assignment time interval; it thus varies according to the particular assignment time interval. Thus, the revenues also vary according to the temporal
    position and length of the assignment time interval. Cost calculation, however, refers to
    the analysis period. As the assignment time interval often only consists of the peak hour
    (e.g. evening rush hour from 4-6p.m.), project the results to the analysis period when you
    want to calculate cost coverage in your model or combine indicators calculated in the
    assignment with indicators calculated in the procedure PuT operating indicators (file IndicatorSource.xls, in the directory ...Program files\PTV Vision\PTV Visum 13\Doc\Eng). To
    create identical reference periods, at the demand segment, define a projection factor of
    the assignment time interval for the analysis period (see User Manual: Chpt. 20.2 , page
    2153). The projection factor 1 is only correct here, if you carry out an assignment for the
    whole day.

    8.6.6

    Calculation of the operating costs


    The total costs can be divided into vehicle-dependent costs and infrastructure costs. These are
    the provided cost blocks:

    PTVGROUP

    649

    8.6.6.1 Vehicle type-dependent costs


    Vehicle type-dependent costs
    Hourly costs /
    Cost time

    Time-dependent costs for personnel

    Kilometer costs /
    Cost distance

    Kilometer-dependent costs for fuel, repairs, etc.

    Vehicle costs /
    Cost vehicle

    Assigned fixed cost for a vehicle (debt service as well as other fixed
    costs such as insurance costs).

    Time costs = service time hourly costs rate of vehicle journeys + empty time hourly
    cost rate of empty trips
    Distance costs = ServiceKm kilometer cost rate of vehicle journeys + empty kilometers kilometer cost rate of empty trips

    Vehicle costs = cost rate per vehicle unit number of vehicles

    The number of vehicles is an output attribute of line blocking.


    Table 251: Vehicle type-dependent costs

    Infrastructure costs
    Stop point costs /
    Cost stop point

    Costs for the usage of stop points These can be composed of depreciation costs (for example investment costs), running costs (for example maintenance costs) and utilization costs (for example fees for
    using the stops).

    Costs 1/2/3 stop


    points

    Three cost rates which are included in the calculation of stop point
    costs (see "Stop point cost" on page 655).

    Link costs / Cost


    links

    Costs for the usage of links (infrastructure cost) The link costs are divided equally between the vehicle journeys which use the link.

    Costs 1/2/3 links Three cost rates which are included in the calculation of link costs (see
    "Link costs" on page 652).
    Operator costs /
    Cost operator

    Share of costs for general operational costs These can be composed


    of depreciation costs (for example investment costs) or running costs
    (for example maintenance costs).

    Costs 1/2/3 operators

    Three cost rates which are included in the calculation of operator costs
    (see "Operator cost" on page 656).

    Table 252: Infrastructure costs


    The total costs which accumulate for operating public transport, are returned in the following
    attribute.
    Total cost
    Cost

    Costs = time costs + distance costs + vehicle costs + stop point costs + link costs + operator
    costs

    Table 253: Total cost


    8.6.6.1

    650

    Vehicle type-dependent costs


    The costs for a vehicle is composed of hourly costs, kilometer costs and fixed costs. In Visum,
    these costs are assigned to vehicle units (see User Manual: Chpt. 20.2.2 , page 2153). In

    PTVGROUP

    8.6.6.1 Vehicle type-dependent costs


    practice these kilometer and vehicle costs are dependent on the vehicle type used (for example standard or articulated bus, or tram in single or multiple traction) and the hourly costs of the
    operator (for example public or private operator, type of labor contract).
    Hourly costs (attribute Cost time)
    Time costs = service time hourly costs rate of vehicle journeys + empty time hourly cost rate of empty
    trips
    Service time describes the time for passenger transport. It can be taken from the timetable.
    Empty time comprises the times for delay buffers, driver breaks or interlining and layover.
    Line blocking is required for determining the empty times, otherwise this share is not included in the hourly costs.
    Kilometer costs (attribute Cost distance)
    Distance costs = ServiceKm kilometer cost rate of vehicle journeys + empty kilometers kilometer cost
    rate of empty trips
    Service kilometers for transporting passengers are calculated directly from the vehicle
    journeys in the timetable.
    Empty kilometers arise from empty trips between the last stop of a service trip and the first
    stop of another service trip, within a block.
    Vehicle costs (attribute Cost vehicle)
    Vehicle costs result from the fixed costs, which can be defined for each vehicle unit (see User
    Manual: Chpt. 15.28.2 , page 1284), and the vehicle demand determined by PuT line blocking.
    Vehicle costs = cost rate per vehicle unit number of vehicles
    The attribute Cost rate per vehicle unit contains the fixed costs for each vehicle unit (the
    acquisition costs for example). Fixed costs increase with every additional vehicle required.
    The value Number of vehicles results from the necessary vehicle blocks. Line blocking is
    therefore assumed for the calculation of vehicle costs.
    Calculation example: Vehicle type-dependent costs for lines
    This example regards the following vehicle type-specific cost rates (see "Example for PuT operating indicators" on page 630).
    Vehicle units

    Standard bus

    Low floor bus

    Train

    Service

    Service

    Service

    Empty

    Empty

    Empty

    Cost rate per hour [CU/h]

    300.00

    200.00

    300.00

    200.00

    700.00

    500.00

    Cost rate per km [CU/km]

    5.00

    5.00

    5.00

    5.00

    10.00

    10.00

    Cost rate per vehicle unit


    [CU/Veh]

    7,000.00

    7,000.00

    20,000.00

    Reference period of the


    cost rate per vehicle unit

    Analysis period

    Analysis period

    Analysis period

    PTVGROUP

    651

    8.6.6.2 Link costs


    Table 254: Cost rates for the vehicle units
    Vehicle combinations

    Standard bus
    Service

    Cost rate per hour [CU/h]

    Low floor bus

    Empty

    0.00

    Service

    0.00

    Cost rate per km [CU/km]


    0.00
    0.00
    Table 255: Cost rates for the vehicle combinations

    Train

    Empty

    Service

    Empty

    0.00

    0.00

    50.00

    50.00

    0.00

    0.00

    0.00

    0.00

    The following distances and times accumulate for the train:


    Vehicle combination

    ServiceKm EmptyKm

    Service
    time

    Empty time

    Train
    380km
    0km
    10.13h
    0h
    Table 256: Distances and times for the vehicle combination Train in the analysis period
    Calculating the vehicle type-dependent costs (distance costs, time costs and vehicle costs) for
    lines returns the following result for the Train line.
    Distance costs / analysis period
    CostDist(AP) = CostKmService ServiceKm(AP) + CostKmEmpty EmptyKm(AP)

    Time costs / analysis period


    CostTime(AP) = CostTimeService ServiceTime(AP) + CostTimeEmpty EmptyTime(AP)

    Vehicle costs / analysis period


    CostVehicle(AP) = Cost rate vehicle unit Number of vehicles

    8.6.6.2

    Link costs
    Link costs are infrastructure costs, which accumulate when using a link. The link costs are divided equally between the vehicle journeys which use the link. Up to three cost values (attributes CostRate1_ PuTSys - CostRate3_ PuTSys ) can be specified per link and transport
    system to model link costs (see User Manual: Chpt. 15.14.7 , page 1107). For each of these
    three cost values, one of the following cost types can be selected:
    Depreciation costs, for example annual costs for depreciation and interest rates which
    result from the investment cost for the link

    652

    PTVGROUP

    8.6.6.2 Link costs


    Running costs, for example maintenance costs and operating costs
    Utilization costs, for example fees for using stop points or tracks
    Dependent on the selected cost type, the allocation of the costs to the individual vehicle journeys is then carried out according to the formulas described below.
    Cost type depreciation costs

    CostValue: for example investment costs for a link (link attributes CostRate1-PuTSys,
    also 2 and-3)
    with q = 1 + p/100

    Cost type running costs

    CostValue: for example annual maintenance costs for a link (link attributes CostRate1PuTSys, also 2 and-3)

    Cost type utilization costs

    CostValue: for example fees for using a link (link attributes CostRate1-PuTSys, also 2
    and-3)
    CostsLinkV, L, T = CostValueL, T
    CostValueL, T

    Cost value which is entered as attribute of the link. For running costs the value can refer to AP or AH. Depreciation
    costs and utilization costs can either be distributed to all
    vehicle journeys or allocated only to vehicle journeys which
    end or start at this stop point (see User Manual: Chpt.
    20.3.2.5 , page 2162).

    CostsLinkAP, L, T

    Link costs of the link in the analysis period (AP)

    CostsLinkV, L, T

    Costs for a vehicle journey V which uses the link

    V L, T

    Number of vehicle journeys of transport system T which use


    link L.

    FacTS

    The transport supply projection factor from AP to AH (see


    User Manual: Chpt. 15.42.3 , page 1513)

    DT

    Depreciation time in years

    Interest rate [%]

    Table 257: Formulas for calculating link costs

    PTVGROUP

    653

    8.6.6.2 Link costs


    Calculation example: Link costs for vehicle journeys in the analysis period
    Example for depreciation costs
    Cost rate 2 PuTSys(Train)

    100000 CU

    Interest rate p

    7%

    Depreciation time DT

    10 years

    Projection factor transport supply


    (FacTS)

    365

    Number of vehicle journeys of the


    transport system train

    19

    Link Cost 2 of link 4


    CostsLink

    AP, L, T

    Link Cost 2 of vehicle journey 58


    39.008 19 = 2.053
    Table 258: Example calculation for link depreciation costs
    Example for running costs
    Cost rate 3 PuTSys(Bus)

    100 CU

    Links traversed by vehicle journey 96

    1 -> 2 -> 3 -> 5 -> 6 -> 7

    Link lengths

    5km per link

    Length reference of cost rate 3

    Link length

    Time reference of cost rate 3

    Analysis horizon

    Projection factor transport supply (FacTS)

    365

    Link Cost 2 for share of links 1, 2, 3 and 5

    4 (20 CU / (19 365)) = 0.01154 CU

    Link Cost 2 for share of links 6 and 7

    2 (20 CU / (38 365)) = 0.00288 CU

    Link Cost 2 for vehicle journey 96

    0.01154 + 0.00288 = 0.01442 CU

    Table 259: Example calculation for running costs of links


    Example for utilization costs (in the example, stored in attribute Link Cost 1)
    Cost rate 1 PuTSys(Train)

    100 CU

    Length of link 4

    10km

    Length reference of cost rate 1

    km

    Link Cost 1 for vehicle journey (in this exam- 100 CU/km 10km = 1000 CU
    ple, it is constant for all vehicle journeys of
    the train)
    Table 260: Example calculation for link utilization costs

    654

    PTVGROUP

    8.6.6.3 Stop point cost


    8.6.6.3

    Stop point cost


    Stop point costs are infrastructure costs which accumulate when using a stop point. The costs
    are defined for each stop point. The costs are evenly distributed between the vehicle journeys
    which allow boarding and alighting on this stop point. To model the costs, up to three cost
    values (attributes Cost rate1 to Cost rate3) may be entered for each stop point (see User
    Manual: Chpt. 15.26.2 , page 1267). For each of these three cost values, one of the following
    cost types can be selected.
    Depreciation costs, for example annual costs for depreciation and interest rates which
    result from the investment cost for the link
    Running costs, for example maintenance costs and operating costs
    Utilization costs, for example fees for using stop points or tracks
    Dependent on the selected cost type, the allocation of the costs to the individual vehicle journeys is then carried out according to the formulas described below.
    Cost type depreciation costs

    CostValue: for example investment costs for a stop point (Stop point attributes CostRate1
    to 3)

    with q = 1 + p/100

    Cost type running costs

    CostValue: for example annual maintenance costs for a stop point (Stop point attributes
    CostRate1 to 3)

    Cost type utilization costs

    CostValue: for example fees for using a stop point (Stop point attributes CostRate1 to 3)
    CostSPV, SP = CostValueSP
    CostValue

    CostsSP
    CostsSP

    PTVGROUP

    SP

    AP, SP
    V, SP

    Cost value which is entered as an attribute of the stop point SP.


    For running costs the value can refer to AP or AH. Depreciation
    costs and utilization costs can either be distributed to all vehicle
    journeys or allocated only to vehicle journeys which end or start
    at this stop point.
    Stop point costs of the stop point SP in the analysis period (AP).
    Costs for a vehicle journey V which uses the stop point SP.

    655

    8.6.6.4 Operator cost


    V

    SP

    Number of vehicle journeys which use stop point SP.

    FacTS

    The transport supply projection factor from AP to AH (see User


    Manual: Chpt. 15.42 , page 1511)

    DT

    Depreciation time in years

    Interest rate [%]

    Table 261: Formulas for the calculation of stop point costs


    8.6.6.4

    Operator cost
    Up to three cost values (attributes Cost rate1 to 3) can be entered for each operator. For each
    of these three cost values, one of the following cost types can be selected.
    Depreciation costs, for example investment costs (debt service for depot and offices)
    Running costs, for example maintenance costs (maintenance for the depot and administrative/sales costs).
    To distribute operator costs to the vehicle journeys, which are operated by this operator, a distribution key can be specified which consists of the following weighted indicators
    Service kilometers (WeightServKm)
    Seat kilometers (WeightSeatKm)
    Service time (WeightServTime)
    Number of vehicle journeys (WeightJourneys)
    Passenger trips unlinked (WeightPTripsUnlinked)
    Passenger kilometers (WeightPassKmTrav)
    With the values of any combination of these six attributes, you can thus distribute the operator
    costs onto vehicle journeys. The weighting factors must amount to 100% (see User Manual:
    Chpt. 20.3.2.5 , page 2162).
    Distribution of operator costs O on a vehicle journey

    The share of one vehicle journey V in the operator costs of its operator O is:

    Cost type depreciation costs

    CostValueO: for example investment costs for a depot

    656

    PTVGROUP

    8.6.6.4 Operator cost

    with q = 1 + p/100

    Cost type running costs

    CostValueO: = for example annual maintenance costs for the depot

    Share
    F

    The share of one vehicle journey V in operator (O)


    costs

    Number of all vehicle journeys of operator O

    CostValue

    Cost value which is specified as operator attribute

    CostOp

    Operator costs of operator O in analysis period (AP)

    CostOp

    Operator costs for one vehicle journey V by operator


    O.

    FacTS

    The transport supply projection factor from AP to AH

    DT

    Depreciation time in years

    Interest rate [%]

    AP, O
    V

    Table 262: Formulas for calculating operator costs


    Calculation example: Depreciation costs
    Cost rate 1: Investment costs for depot

    7500000 CU

    Depreciation time DT

    10 years

    Interest rate

    7%

    Projection factor transport supply


    (FacTS)

    365

    Operator Cost 1 for "Urban operator"


    = 2925.57 CU
    Weight service kilometers

    25%

    Service kilometers of trip 96

    27.5km

    Service kilometers total for operator


    "Urban operator"

    1330km

    Weight seat kilometers

    25%

    Seat kilometers of trip 96

    962.5km

    PTVGROUP

    657

    8.6.6.4 Operator cost


    Seat kilometers total for operator
    "Urban operator"

    46,550km

    Weight passenger kilometers

    50%

    Passenger kilometers of trip 96

    2,495.0km

    Passenger kilometers total for operator 109,000km


    "Urban operator"
    Share of vehicle journey 96 in operating costs
    Operator Cost 1 for vehicle journey 96

    2925.57 CU 0.022 = 63.73 CU

    Table 263: Calculation example for depreciation costs of the operator


    Calculation example: Running costs
    Cost rate 2: Maintenance cost for depot

    80,000 CU

    Time reference of the cost rate

    Analysis horizon

    Projection factor transport supply


    (FacTS)

    365

    Operator Cost 2 for "Urban operator"


    Weight service kilometers

    25%

    Service kilometers of trip 96

    27.5km

    Service kilometers total for operator


    "Urban operator"

    1,330km

    Weight seat kilometers

    25%

    Seat kilometers of trip 96

    962.5km

    Seat kilometers total for operator "Urban 46,550km


    operator"
    Weight passenger kilometers

    50%

    Passenger kilometers of trip 96

    2,495.0km

    Passenger kilometers total for operator


    "Urban operator"

    109,000km

    Share of vehicle journey 96 in operating


    costs
    Operator Cost 2 for vehicle journey 96
    Table 264: Calculation example for the running costs of the operator

    658

    PTVGROUP

    8.6.7 Calculation of the fare revenues (revenue calculation)

    8.6.7

    Calculation of the fare revenues (revenue calculation)


    With Visum revenues can be calculated and then distributed to the network objects. There are
    three methods available for revenue calculation.
    Specification of a fixed revenue for each passenger trip
    For each passenger trip, a standard fare is assumed and distributed to the lines used by
    the passenger. The revenue distribution can also be modified by specific parameter settings (fixed amount per path leg, weighting by number of fare points, weighting by number
    of path legs).
    Specification of a revenue for each fare point
    The revenue results from the following calculation: revenue/fare point multiplied by the
    number of fare points. The revenue distribution can also be modified by specific parameter settings (fixed amount per path leg, weighting by number of fare points, weighting
    by number of path legs).
    Calculation of the revenues using the fare model
    For each passenger trip, the fare is calculated from the current ticket type. This revenue is
    then distributed over the lines used by the passenger. The revenue distribution can also
    be modified by specific parameter settings (fixed amount per path leg, weighting by number of fare points, weighting by number of path legs, and transport system-specific distribution of supplements).
    The decision for one of these three possibilities depends on the model's desired level of detail,
    the availability of input data and the planned work load for modeling the revenue calculation.
    The three possibilities of revenue calculation in Visum are described below. For each possibility, an example calculation is carried out using the application example data.
    Independent of the selected type of revenue calculation, the following output attributes (revenue indicators) are available.
    Indicator

    Description

    Total revenue

    Total revenue from fare revenues which apply to the network object.

    Revenue-DSeg

    Revenue by demand segment from fare revenues which apply to the


    network object.

    Revenue total
    (length-proportional)

    Total revenue from fare gains which applies to the territory and the
    selected level. Distribution is proportional to the link lengths of the traversed links.

    Revenue-DSeg
    (length-proportional)

    Like revenue total (length-proportional), but only the revenue by


    demand segment.

    Revenue total
    (fare point-proportional)

    Total revenue from fare gains which applies to the territory and the
    selected level. Distribution is proportional to the number of traversed
    fare points on links and time profile items.

    Revenue-DSeg
    (fare point-proportional)

    Like revenue total (fare point-proportional), but only the revenue by


    demand segment.

    Revenue PTripUn- Revenue per passenger trip = Revenue total / PTripsUnlinked

    PTVGROUP

    659

    8.6.7.1 Revenue calculation from fixed revenue per passenger trip


    Indicator

    Description

    linked
    Revenue
    PTripsUnlinked_
    DSeg

    Revenue per demand segment / passenger trips unlinked per demand segment

    Cost coverage %

    Expresses the cost coverage in percent

    CostCov total

    Expresses the cost coverage in absolute numbers

    Cost coverage % = Revenue total (length proportional) / Costs 100


    Cost coverage total = Revenue total (length proportional) - Costs

    Cost coverage per passenger trip = Cost coverage total / passenger trips unlinCost coverage
    per PTripUnlinked ked
    Table 265: Revenue indicators
    8.6.7.1

    660

    Revenue calculation from fixed revenue per passenger trip


    To estimate the revenues from ticket fares, a revenue amount per passenger trip can be specified. In the following example, a fixed revenue of 4.00 CU per passenger trip is specified and
    the revenue per line calculated. The distribution regards only the number of path legs (see
    "Revenue distribution" on page 664). The following route table (PuT path legs) provides an
    overview of all other indicators required, including the passenger trips.
    From zone To zone

    Line

    A Village
    (100)

    BUS1

    10

    20

    Train

    20

    40

    X City
    (200)

    FromSPoi- ToSPoi- Pasnt


    nt
    senger
    trips

    1,501

    Fixed revenue per


    passenger
    trip [CU]

    Revenue
    share
    (Weighted
    with number of path
    legs)

    4.00
    4.00

    A Village
    (100)

    X City
    (200)

    BUS1

    10

    40

    499

    4.00 499 4.00

    A Village
    (100)

    C Village
    (201)

    BUS1

    10

    20

    200

    4.00 200 4.00

    X City
    (200)

    A Village
    (100)

    BUS1

    40

    10

    1,000

    4.00 1000
    4.00

    X City
    (200)

    A Village
    (100)

    Train

    40

    20

    1,000

    4.00

    PTVGROUP

    8.6.7.2 Revenue calculation from fixed revenue per traversed fare point
    From zone To zone

    Line

    FromSPoi- ToSPoi- Pasnt


    nt
    senger
    trips

    BUS1

    20

    10

    Fixed revenue per


    passenger
    trip [CU]

    Revenue
    share
    (Weighted
    with number of path
    legs)

    4.00

    X City
    (200)

    C Village
    (201)

    Train

    40

    20

    5,000

    4.00 5,000
    4.00

    X City
    (200)

    B Village
    (202)

    BUS1

    40

    30

    2,000

    4.00 2,000
    4.00

    C Village
    (201)

    A Village
    (100)

    BUS1

    20

    10

    200

    C Village
    (201)

    X City
    (200)

    Train

    20

    40

    5,000

    4.00 5,000
    4.00

    B Village
    (202)

    X City
    (200)

    BUS1

    30

    40

    2,000

    4.00 2,000
    4.00

    4.00 200 4.00

    Table 266: Revenue share per path leg


    Revenues per line then result from summation of the revenue shares for each line.
    Line

    Revenue per line

    Bus1

    3002 + 1996 + 800 + 4000 + 2000 + 8000 + 800 + 8000 = 28598

    Train 3,002 + 2,000 + 20,000 + 20,000 = 45,002


    Table 267: Revenue per line
    8.6.7.2

    Revenue calculation from fixed revenue per traversed fare point


    If fare points have been defined for links or time profile items of the model, revenue calculation
    can regard a fixed revenue per traversed fare point (see User Manual: Chpt. 20.5 , page
    2167).
    In the following example, a revenue of 0.20CU per fare point is specified. The route table (PuT
    path legs) provides an overview of the calculation.

    PTVGROUP

    661

    8.6.7.2 Revenue calculation from fixed revenue per traversed fare point
    From To
    Line
    zone zone
    100

    200

    From
    SP

    To SP NumFP PTrips

    BUS1

    10

    20

    10

    Train

    20

    40

    20

    1501

    Fixed reve- Revenue share


    nue per FP (Weighted with num[CU]
    ber of path legs)
    0.20
    0.20

    100

    200

    BUS1

    10

    40

    29

    499

    0.20

    100

    201

    BUS1

    10

    20

    10

    200

    0.20

    200

    100

    BUS1

    40

    10

    30

    1,000

    0.20

    200

    100

    Train

    40

    20

    20

    1,000

    0.20

    BUS1

    20

    10

    10

    0.20

    200

    201

    Train

    40

    20

    20

    5,000

    0.20

    200

    202

    BUS1

    40

    30

    10

    2,000

    0.20

    201

    100

    BUS1

    20

    10

    10

    200

    0.20

    201

    200

    Train

    20

    40

    20

    5,000

    0.20

    202

    200

    BUS1

    30

    40

    10

    2,000

    0.20

    Table 268: Revenue share per path leg


    Revenues per line then result from summation of the revenue shares for each PuT path leg.
    Line

    Revenue per line

    Bus1

    4,503 + 2,894 + 400 + 6,000 + 3,000 + 4,000 + 400 + 4,000 = 25,197

    Train 4,503 + 3,000 + 20,000 + 20,000 = 47,503


    Table 269: Revenue per line
    Fare points can be defined for links and also for time profile items. In the calculation of the revenue share for each path leg, the sum of fare points at both of those network objects goes in.

    662

    PTVGROUP

    8.6.7.3 Revenue calculation using the fare model

    Illustration 201: Calculation of the fare points for path legs


    8.6.7.3

    Revenue calculation using the fare model


    The most precise variant of the revenue calculation is the one which is based on the Visum
    fare model. To do so, fare systems and ticket types have to be defined and connected with the
    network lines (see "PuT fare model" on page 605). A fare model provides a specific fare for
    each PuT path.
    The revenue is first calculated on PuT path level. The passenger trips (volume) of the path are
    thus multiplied with the fare. The revenue is then distributed to the PuT path legs (see "Revenue distribution" on page 664). With a zone-based fare, the following revenues result for the
    paths in the example Example_LLE.ver .
    From
    zone

    To
    zone

    Path Passenlegs ger trips

    A Village

    X City

    Bus1
    Train

    1,000

    3.00

    3.00

    6.00

    6,000.00

    A Village

    X City

    Bus1

    1,000

    3.00

    0.00

    3.00

    3,000.00

    A Village

    C Village

    Bus1

    200

    2.00

    0.00

    1.00

    200.00

    X City

    A Village

    Bus1

    1,000

    3.00

    0.00

    3.00

    3,000.00

    X City

    A Vil-

    Bus1

    1,000

    3.00

    3.00

    6.00

    6,000.00

    PTVGROUP

    Number of
    fare
    zones

    Oneway
    ticket
    base
    fare
    [CU]

    Supplement for
    Train [CU]

    Fare =
    Base fare
    + Supplement
    [CU]

    Revenue =
    Volume
    Fare [CU]

    663

    8.6.7.4 Revenue distribution


    From
    zone

    To
    zone

    Path Passenlegs ger trips

    Number of
    fare
    zones

    Oneway
    ticket
    base
    fare
    [CU]

    Supplement for
    Train [CU]

    lage

    Train

    X City

    C Village

    Train

    5,000

    1.00

    3.00

    4.00

    20,000.00

    X City

    B Village

    Bus1

    2,000

    1.00

    0.00

    1.00

    2,000.00

    C Village

    A Village

    Bus1

    200

    1.00

    0.00

    1.00

    200.00

    C Village

    X City

    Train

    5,000

    1.00

    3.00

    4.00

    20,000.00

    B Village

    X City

    Bus1

    2,000

    1.00

    0.00

    1.00

    2,000.00

    Total

    Fare =
    Base fare
    + Supplement
    [CU]

    Revenue =
    Volume
    Fare [CU]

    62,400.00

    Table 270: Calculation of the revenues per path (PuT routes)


    8.6.7.4

    Revenue distribution
    Internally Visum first calculates the revenues for PuT paths. The revenues are then distributed
    to the PuT path leg and then converted to the network object line hierarchy (lines, line routes,
    etc.). You can influence the distribution of the revenues by the following parameters.
    With Weight number of path legsyou can achieve an even distribution of the revenue
    over all path legs. Each path leg receives the same revenue share, if the weight is 100%.
    With Weight number of fare points the distribution will be based on the ratio between the
    number of fare points on the path leg and the number of fare points on the total path. Thus
    you can achieve, that longer (in terms of the number of fare points) path legs receive a
    greater portion of the revenues.
    You can select any weighting between both distribution possibilities, number of path legs
    and number of fare points.
    When specifying Fixed amount per path leg, each path leg first receives a fixed sum of
    the total revenue. The remaining revenue is then distributed to the path legs according to
    the distribution rules mentioned above. If the sum of all of the fixed amounts exceeds the
    revenue to be distributed, the fixed amounts are correspondingly reduced. If a fare model
    is used, the supplements are not taken into consideration.
    Note: Revenue distribution does not regard how the revenue was calculated (fare model,
    fixed revenue per passenger trip or fixed revenue per fare point).
    For revenue distribution the following formulas are applied
    Share-FarePt = NumFarePt-PL / NumFarePt-Total

    664

    PTVGROUP

    8.6.7.4 Revenue distribution


    Share-PathLeg = 1 / NumPL
    RevShare-PathLeg =(Share-FarePt W- NumFarePt + Share-PathLeg W-NumPL)
    Rev-PathLeg = Rev-Fix + (Rev-PassTrip Rev-Fix NumPL) RevShare-PathLeg
    NumPL

    Number of path legs in a passenger trip

    NumFarePt-PL

    Number of fare points in a path leg

    NumFarePt-Total

    Total number of fare points in the passenger trip

    RevShare-PathLeg

    Share of the path revenue, which applies to the path leg

    W-NumFarePt

    Weighting of fare points

    W-NumPL

    Weighting of path legs

    Rev-PassTrip

    Revenue per passenger trip

    Rev-Fix

    Revenue which is distributed to each path leg as a fixed amount

    Rev-PathLeg

    Revenue which is distributed to the path leg

    W-NumFarePt + W-NumPL=1.0

    The revenue distribution is also demonstrated with the example Example_ LLE.ver. A zonebased fare model was modeled there and the calculation of the input data required for revenue distribution already demonstrated (see "Revenue calculation using the fare model" on
    page 663).
    Revenue distribution is only carried out for those paths which comprise more than one path
    leg. In the example, this is the path from A Village to X City, where 1,000 passengers use the
    bus and the train, and back. As the number of path leg fare points is 10 for both the bus (A Village C Village) and the train (C Village X Town), a distribution factor of 0.5 results in each
    case.
    From origin zone

    100 (A Village)

    To destination zone

    200 (X City)

    Links in the course of Path 1

    1 (Bus) -> 2 (Bus) -> 4 (Train)

    Number of fare points on traversed links

    Link 1: 5 (Bus)
    Link 2: 5 (Bus)
    Link 4: 10 (Train)

    Share-FarePt(Bus1)
    Number of path legs of Path 1

    Share-PathLeg(Bus1)
    Revenue on Path 1

    6000 CU

    Weighting of fare points

    75%

    PTVGROUP

    665

    8.6.7.4 Revenue distribution


    Weighting of path legs

    25%

    Revenue Path Leg(Bus1)

    Table 271: Revenue calculation for the path leg Bus1


    If you want to return the revenues on the line level, the following calculation thus applies.
    Line
    BUS1

    FromZon- ToZone
    e

    PTripsUnlinked

    Fare

    A Village

    X City

    1,000

    3.00

    A Village

    X City

    1,000

    6.00

    A Village

    C Village

    B Village

    X City

    C Village

    Revenue = PTrips Fare


    3,000.00

    200

    1.00

    200.00

    2,000

    1.00

    2,000.00

    A Village

    200

    1.00

    200.0

    X City

    A Village

    1,000

    3.00

    3,000.00

    X City

    A Village

    1,000

    6.00

    X City

    B Village

    2,000

    1.00

    Total

    2,000.00
    =16,400.00

    TRAIN X City

    C Village

    5,000

    4.00

    X City

    A Village

    1,000

    6.00

    C Village

    X City

    5,000

    4.00

    A Village

    X City

    1,000

    6.00

    Total

    20,000.00

    2,000.00

    =46,000.00

    Table 272: Aggregation of the path leg revenues to lines


    Another calculation example illustrates the calibration options (especially the definition of a
    fixed amount for each path leg). Let the following network be the example network.

    Illustration 202: Example network for fixed amount per path leg

    666

    PTVGROUP

    8.6.7.4 Revenue distribution


    Passenger trips

    Total number of fare points

    12

    Share-FarePt(Bus1)
    Share-FarePt(Train)
    Share-FarePt(Bus2)
    Number of path legs

    Share-PL
    Rev-PassTrip
    3.00
    Table 273: Input data for the calculation example
    Path leg

    Share per path leg

    Revenue per path leg

    Bus 1

    1.0 0.167 + 0.0 0.333 = 0.167

    0.167 3.00 = 0.50

    Train

    1.0 0.500 + 0.0 0.333 = 0.500

    0.500 3.00 = 1.50

    Bus 2
    1.0 0.333 + 0.0 0.333 = 0.333
    0.333 3.00 = 1.00
    Table 274: Revenue distribution W-NumFP = 1.0, W-NumPL= 0.0, FixSuppl = 0

    Path leg

    Share per path leg

    Revenue per path leg

    Bus 1

    0.5 0.167 + 0.5 0.333 = 0.250

    0.250 3.00 = 0.75

    Train

    0.5 0.500 + 0.5 0.333 = 0.417

    0.417 3.00 = 1.25

    Bus 2
    0.5 0.333 + 0.5 0.333 = 0.333
    0.333 3.00 = 1.00
    Table 275: Revenue distribution W-NumFP = 0.5, W-NumPL = 0.5, FixSuppl = 0.00

    Path leg

    Share per path leg

    Revenue per path leg

    Bus 1

    0.5 0.167 + 0.5 0.333 = 0.250

    0.20 + 0.250 (3.00 - 3 0.20) = 0.80

    Train

    0.5 0.500 + 0.5 0.333 = 0.417

    0.20 + 0.417 (3.00 - 3 0.20) = 1.20

    Bus 2
    0.5 0.333 + 0.5 0.333 = 0.333
    0.20 + 0.333 (3.00 - 3 0.20) = 1.00
    Table 276: Revenue distribution W-NumFP = 0.5, W-NumPL = 0.5, FixSuppl = 0.20
    When using a fare model (see "Revenue calculation using the fare model" on page 663), the
    distribution of supplements can also be influenced. With the option Distribute supplements to
    transport systems you have the following possibilities:
    If the option is selected, the supplement charged for the transport system is only distributed to the path legs which are traversed by this transport system. This is how the supplement is only distributed to the path legs, where the long-distance train is used, for

    PTVGROUP

    667

    8.6.7.5 Calculation of cost coverage


    example for a connection where a local train without supplement and a long-distance
    train with supplement are used.
    If the option has not been selected, the supplement is distributed to all path legs according to the distribution key, independent of whether the transport system, for which the
    supplement was defined, is used for this path leg. This is how a regional train also benefits from the supplement for a long-distance train, for revenue distribution, for example.
    An example illustrates the differences between both methods. There is only one fixed supplement in the example. To make it easier, there is no distance-based supplement. The base
    fare of the connection is 30.00 CU.
    TSys
    (#Rank)

    Number of Distribution Fixed sup- Transport systemfare points of the base plement
    based supplement
    on path leg fare [CU]
    [CU]
    distribution onto
    path legs [CU]

    Distribution of
    the supplement onto
    all path legs
    [CU]

    EC (#2)

    100.00

    10.00

    7.00

    (**) 3.50

    2.33

    IC (#2)

    100.00

    10.00

    7.00

    (**) 3.50

    2.33

    RE (#3)

    100.00

    10.00

    0.00

    0.00

    2.33

    30.00

    (*) 7.00

    7.00

    7.00

    Total

    (*)The fixed supplement of the top-ranking TSys (ICE) is only charged once, in this case
    7.00CU.
    (**) The supplement of 7.00CU is only distributed onto both transport systems EC and IC,
    because they have the same maximum rank. If for example, the IC had a rank3 and a fixed
    supplement of 3.00CU, the EC would obtain the complete supplement of 7.00CU, when
    taking the rank into consideration and distributing by transport system.
    8.6.7.5

    Calculation of cost coverage


    For cost coverage calculation, total revenues have to be compared with total costs. The following output attributes are available.
    Indicator

    Description

    CostCov total

    Expresses the cost coverage in absolute numbers.


    CostCov total = Revenue total (length proportional) - Costs

    CostCov Percent [%]

    Expresses the cost coverage in percent.

    Cost coverage per passenger trip unlinked

    Expresses the cost coverage per passenger trip.

    This attribute is only available for the elements of the line hierarchy and for PuT operators and transport systems.
    668

    PTVGROUP

    8.6.8 Basic calculation principles for indicators


    Table 277: Indicators for the cost coverage calculation
    For the application example, cost coverage data on line level is calculated as follows for Bus1
    for example.
    Total revenue

    16400.00 CU

    Cost

    36321.86 CU

    CostCov total

    16400.00 CU - 36321.86 CU = -19921.86 CU

    CostCov Percent [%]


    Passenger trips unlinked

    8,400

    Cost coverage per passenger


    trip unlinked

    = -2.37 CU
    Table 278: Cost coverage calculation from revenues and costs

    8.6.8

    Basic calculation principles for indicators


    Here, the following indicator calculation principles are introduced.
    Projection onto the analysis horizon (AH)
    Aggregation along the line hierarchy (Aggregation of indicators on trip section level to indicators of a higher level)
    Temporal cut (Calculation of indicators for analysis time intervals)
    Spatial cut (by territory)
    Impact caused by couplings
    Projection of additional attributes

    8.6.8.1

    Projection to the analysis horizon


    Using projection factors, the analysis period values of indicators can be extrapolated to any
    user-defined analysis horizon. If your analysis period is one day and a service trip runs every
    day throughout the year, you can for example use a projection factor of 365 to calculate the
    revenue for the entire year. If the service trip only runs on weekdays, you can select a projection factor of 260. Depending on the indicator to be calculated, the projection factor has to
    either be set for the valid day or for the demand segment (table 279).
    Indicator category

    Projection factor Projection factor


    Transport supply / Hourly costs /
    Valid day
    Valid day

    General indicators

    Transport supply

    Network performance
    Costs (apart from Cost
    Time)
    Cost Time
    Revenues
    PTVGROUP

    Projection factor
    by DSeg

    X
    X
    X
    X
    669

    8.6.8.2 Example for temporal dependencies of indicators


    Table 279: Which projection factor applies for the calculation of indicators?
    The application example makes the difference between the projection factors on valid days
    and those by the demand segment clear. For trip 135, passenger kilometers and service kilometers are compared to each other.
    Valid day

    weekdays (Monday to Friday)

    Projection factor Transport supply / Valid day

    260

    Service kilometers (AP)

    7.5km

    Service kilometers (AH)

    260 7.5 km = 1950 km

    Projection factor Demand segment PuT

    365

    Passenger kilometers (AP)

    397.5km

    Passenger kilometers (AH)


    365 397.5 km = 145087.5 km
    Table 280: Difference in the projection to AH for ServiceKm and PassengerKm
    8.6.8.2

    Example for temporal dependencies of indicators


    For projection to the analysis horizon, the indicators of transport demand (network performance, revenues), the indicators of the transport supply (operating supply, costs), and the
    hourly costs are each projected with a different factor. This takes the fact into account that the
    transport demand, for example at the weekend, can decline more severely than the transport
    supply. At the same time, there are higher personnel costs, i.e. higher hourly cost rates on Sundays.
    The projection factors for transport supply and hourly costs can be specified for each valid day
    separately. In this way, for an analysis period of one week in August, not only can the indicators of regularly occurring Valid Days be correctly projected to an analysis horizon of one
    year (for example, Mon-Fri with factor52), but also seasonally restricted Valid Days (for example, Sat+Sun during the school summer holidays by applying factor6).
    The projection factors for the extrapolation of the network performance from the assignment
    time interval to the analysis period or horizon are set separately for each demand segment.
    Therefore, the projection factor from the assignment time interval to the analysis period
    regards the relevance of the OD matrix content for the demand segment.
    If the assignment time interval and the period of validity of the matrix cover the entire analysis period, this factor is then equal to 1.
    If the assignment time interval is shorter than the analysis period, then the projection factor corresponds to the ratio between the demand in the analysis period and the demand
    in the assignment time interval.
    If the demand time series of the demand segment refers to only a part of the assignment
    time interval, then the projection factor corresponds to the ratio between the demand in
    the analysis period and that of the demand time series time period.
    The following example shows how this kind of calculation can be used to save computation
    time in case of homogeneous demand.

    670

    PTVGROUP

    8.6.8.2 Example for temporal dependencies of indicators


    Example
    The analysis period and the assignment time interval should each cover one week (Monday to
    Sunday). The timetable services from Monday to Friday are identical. For the "commuters"
    demand segment the demand from Monday to Friday may be constant and the same time
    series may be applied on weekdays, whereas on the weekend there is no demand in this segment. The demand of this demand segment is coded in the OD matrix of one day in combination with the time series for 24h, beginning Monday at 0:00. Due to the time series, only
    the trips which start on Monday are charged during assignment. In order nevertheless to indicate correct weekly values as PuT volumes per analysis period, the following projection factors are applied to the "commuters" demand segment.
    Projection from ... to ...

    Factor

    Assignment time interval AP

    Assignment time interval AH (= year)

    5 52 = 260

    The following example of a vehicle journey with two sections (illustration 203) shows the calculation of selected operating indicators for the following analysis time slices.
    the analysis period of one week
    the analysis horizon of one year
    an analysis time interval on Tuesday 7 8a.m.
    As shown in illustration 203 and table 281, vehicle journey section 1 is served daily, whereas
    vehicle journey section2 is available on Sundays and public holidays only.

    Illustration 203: Time-distance diagram for a vehicle journey with two vehicle journey sections
    VehJourney
    Valid day

    VehJournSect 1 VehJournSect 2
    Daily

    Projection factor Analysis Horizon

    Sunday+Holiday
    52

    Departure

    06:30 a.m.

    Arrival

    07:30 a.m.

    Trip length

    30 km

    30 km

    Trip length 6:30 - 7:00

    10 km

    10 km

    Trip length 7:00 - 7:15

    10 km

    10 km

    Trip length 7:15 - 7:30

    10 km

    Seat capacity

    PTVGROUP

    200

    63

    100

    671

    8.6.8.2 Example for temporal dependencies of indicators


    Table 281: Further specifications for the vehicle journey with two VJ sections
    table 282 shows the calculation of the seat kilometers. This is done by multiplying the seating
    capacity by the service trip length and then simply adding up the vehicle journey section data.
    Analysis period Mon-Sun
    VehJournSect 1

    200 seats 20 km 7 days = 28000 km

    VehJournSect 2

    100 seats 20 km 1 day = 2000 km

    Total

    30000 km

    Analysis horizon
    VehJournSect 1

    28000 km 52 = 1456000 km

    VehJournSect 2

    2000 km 63 = 126000 km

    Total

    1582000 km

    Analysis time interval Tue 7:00 8:00


    VehJournSect 1

    200 seats 10 km = 2000 km

    VehJournSect 2

    100 seats 0 km = 0 km

    Total

    2000 km

    Table 282: Calculation of seat kilometers


    Compared to seat kilometers, the calculation of service kilometers (often termed load kilometers or train kilometers) by simply adding up the vehicle journey sections is not permitted. In
    this case, it must be realized that superimposed vehicle journey sections may only be counted
    once. This is particularly important for the calculation of any track costs derived from the service kilometers. Track costs are calculated on the basis of service kilometers regardless of the
    train composition. In the projection to the analysis horizon, however, different projection factors
    may arise for the vehicle journey sections. In this case a maximum formation is taking place. In
    the example shown in table 283 , this is the case on Sunday. The calculation of the service
    time is carried out in the same way.
    Analysis period
    Mon-Sun

    Analysis time period Tue


    7:00-8:00

    Monday

    20 km 1

    20 km 52

    10 km 0

    Tuesday

    20 km 1

    20 km 52

    10 km 1

    Wednesday

    20 km 1

    20 km 52

    10 km 0

    Thursday

    20 km 1

    20 km 52

    10 km 0

    Friday

    20 km 1

    20 km 52

    10 km 0

    20 km 1

    20 km 52

    10 km 0

    10 km 1
    + 10 km 1
    + 10 km 1

    10 km 52
    + 10 km MAX
    (52;63)

    20 km 0

    Saturday
    Sunday

    672

    Analysis horizon

    PTVGROUP

    8.6.8.3 Aggregation along the line hierarchy


    Analysis period
    Mon-Sun

    Analysis horizon

    Analysis time period Tue


    7:00-8:00

    + 10 km 63
    Total

    150 km

    8,020 km

    10 km

    Table 283: Calculation of service kilometers


    8.6.8.3

    Aggregation along the line hierarchy


    Based on the value calculated for the vehicle journey section, Visum internally adds all indicators along the line hierarchy. Here, internally means that the user cannot view all indicators
    on the vehicle journey section level. This is due to the memory which is required for the data
    storage). This also applies to indicators are evaluated by territory or time slice.

    Illustration 204: Aggregation along the line hierarchy


    For operators, aggregation is also carried out via the vehicle journey sections (because as an
    option, each vehicle journey section can be assigned an operator). For the aggregation on
    transport system level, the line values are added per transport system (because a transport
    system has to be assigned to each line).
    For the service kilometers of the transport system Train in the application example, the calculation is as follows.

    PTVGROUP

    673

    8.6.8.4 Temporal cut (Time cut)

    Illustration 205: Aggregation of the service kilometers from the trips onto the line
    8.6.8.4

    Temporal cut (Time cut)


    The temporal cut is applied, if you want to calculate indicators for a certain analysis time interval (see User Manual: Chpt. 17.2.2 , page 1861) or during the calculation of the indicators for
    the analysis period. In the last case, the complete days of the analysis period are treated internally the same as a time interval, which last from 12pm to 12am. The temporal cut is carried
    out on the time profile.
    For the time cut, the departing line route items are decisive. Indicators are always first calculated on the trip section level and then aggregated along the line hierarchy (see "Aggregation along the line hierarchy" on page 673). If a time interval lasts for example from 8a.m. to
    9a.m. and a trip departs at 7:55a.m., the line route item which departs at 7:55a.m., is not included in the indicator calculation. If however, another trip departs at 8:55a.m., this line route
    item is still included in the calculation.
    The division of link-related indicators is thus based on the acuteness of individual links. In the
    case of trips exceeding a time interval limit for example, a time interval is assigned to the
    values of those links whose FromNode is traversed within the time interval. For that purpose,
    the passage times at each of the nodes and stop points crossed are interpolated from the run
    times of the time profile first and then compared with the limits of the time intervals (see "Interpolation of passage times (run times in minutes)" on page 675). A calculation example can
    also be found in a different place (see "Measurement of the transport supply" on page 639).

    674

    PTVGROUP

    8.6.8.5 Spatial cut (Territory cut)

    Illustration 206: Interpolation of passage times (run times in minutes)


    8.6.8.5

    Spatial cut (Territory cut)


    In principle, the calculation of the territory-specific portion is based on cutting the link.
    Length-related and time-related indicators, which are calculated per link (for example service kilometers), are summed up for the territory where the link is located in.
    If a link traverses several territories, the indicators of territories is proportionally added
    to the respective length shares, for length-related indicators.
    If a link traverses several territories, the indicators of territories is proportionally added
    to the respective time shares, for time-related indicators.
    For indicators which are not calculated per link, such as the number of stop events in a territory, this territory is summed up where the polygon lies.

    8.6.8.6

    Partially traversed links


    Partially traversed links are a special case. These are links with a stop point on the link, where
    a trip ends or starts at this link stop point. For the calculation of some indicators, the link has to
    be traversed by at least 50%, to be included in the calculation. Which rule applies for which
    indicator and network object, can be taken from the file IndicatorAvailability.xls. An example for
    this are the service kilometers on the link. In the upper section of the illustration 207, the link is
    only traversed by 20%. The service kilometers on the link are then 0km. In the lower section
    of the illustration, the link is traversed by 80%. The service kilometers on the link are then
    8km.

    PTVGROUP

    675

    8.6.8.7 Impact caused by couplings

    Illustration 207: Partially traversed links


    8.6.8.7

    Impact caused by couplings


    For some indicators, coupled vehicle journeys are counted proportionally. This means, that
    two vehicle journeys which are coupled, in the coupled section share the value of the indicator. The Excel file IndicatorAvailability.xls provides an overview of the indicators to which
    this applies. If indicators regard the coupled vehicle journeys only for certain network objects,
    this is additionally noted in a comment.
    The following example illustrates the influence of couplings. Couplings are taken into consideration for service kilometers, for section service kilometers however, couplings are not
    taken into consideration.

    Illustration 208: Influence of couplings on the indicator calculation


    8.6.8.8

    Projection of additional attributes


    In addition to the pre-defined PuT operating indicators also user-defined indicators can be
    extrapolated from the level of vehicle journey sections to higher levels of the line hierarchy
    called Projection of additional attributes if required, they are returned by territory, too. Each
    vehicle journey section attribute selected for the projection of additional attributes is calculated
    according to the following algorithm.
    Result attributes are created
    For the network objects Vehicle journey, Time profile, Line route, Line, Main line, TSys and
    TerritoryPuTDetail it is checked if there is a numeric, editable attribute featuring the same ID

    676

    PTVGROUP

    8.6.8.8 Projection of additional attributes


    as the original attribute. If not, a user-defined attribute featuring that ID is generated automatically. Code and name, too, are adopted from the original attribute. For the network
    objects Vehicle journey section, Service trip, Time profile, Line route, Line, Main line, TSys
    and TerritoryPuTDetail it is checked if there is a numeric, editable attribute featuring the
    same ID as the original attribute but suffixed by "AH". If not, a user-defined attribute featuring that ID is generated automatically. Code and name is each suffixed by "AH, too. If
    the result attributes already exist, they will be set to zero.
    Note: If the result attributes already exist, but are either not numeric or not editable, an
    error message will be displayed and the projection of additional attributes will not start at
    all. Unaffected hereof, the rest of the PuT Operating Indicators procedure, however, will
    still be executed.
    Calculation at vehicle journey section level
    It is assumed that the original attribute contains a value related to AP. At the vehicle journey
    section the AH result attribute value is determined as follows:
    ValueAH = ValueAP ProjFactorTransportSupply
    Here, the projection factor specified for the Valid Day of the journey section is used for the
    transport supply.
    Calculation in the line hierarchy
    The values of the original attribute are added up along the line hierarchy and allocated to
    the respective result attribute there. The values of the AH output attribute of the vehicle journey section are equally added up and allocated to the AH output attribute for each level.
    Territory cut
    If the original attribute is a length-related attribute, the value of the vehicle journey section is first distributed onto the traversed links in proportion to the line length. Then the
    link values are intersected with territories as usual. Thus, the value of a link is added to
    the share (link length in territory / link length) in the AP result attribute per object(s) of
    the line hierarchy x territory.
    If the original attribute is a time-related attribute, the value of the vehicle journey section is first distributed onto the traversed links in proportion to the run times of the time
    profile. Here, too, the link values are length-proportionally allocated to the territories
    (see above).
    If the original attribute is not length-related, its value will simply be added up for each
    traversed territory.
    The values calculated per vehicle journey section are each multiplied by the projection
    factor AH for the transport supply (see above) and then added up equally in the AH result
    attribute per object(s) of the line hierarchy x territory.
    Note: If the Init PuT Operating Indicators procedure is executed, the user-defined attributes of the TerritoryPuTDetail network object, for example, Territory x TSys x Vehicle
    combination, will be deleted (even if the LineCosting results are dropped for other reasons). The other result attributes are kept since they might have existed before. If
    necessary, they have to be deleted manually.

    PTVGROUP

    677

    8.6.8.8 Projection of additional attributes


    In the example Example_LLE.ver the network object vehicle journey section has the user-defined attribute Revenue_ per_PassKm. This reflects the ratio between revenue and passenger
    kilometers. Projection to line data is carried out according to the following schema.

    Illustration 209: Extended projection of attributes

    678

    PTVGROUP

    9 Environmental impact model and HBEFA

    Environmental impact model and HBEFA


    The Visum add-on module Environment is used to calculate the environmental impact - noise
    and pollutant emissions - caused by motorized traffic. Three procedures for calculating environmental impact are available:
    Noise-Emis-Rls90 (see "Noise volume" on page 679).
    Calculation of noise emission levels in accordance with RLS-90 (see User Manual: Chpt.
    21.4 , page 2185).
    Noise-Emis-Nordic (see "Noise volume" on page 679).
    Calculation of noise emission levels in accordance with Nordic Council of Ministers
    (1996) (see User Manual: Chpt. 21.4 , page 2185).
    Pollution-Emis (see "Air pollution emissions" on page 682).
    Calculation of air pollution emissions in accordance with emission factors of the Swiss
    Federal Office for the Environment (BAFU) (see User Manual: Chpt. 21.7 , page 2188).
    The Visum add-on module HBEFA allows you to calculate emission values in Visum by link,
    territory or network-wide. The calculation is based on the Handbook Emission Factors for
    Road Transport version 3.1. (see "Emission calculation according to HBEFA 3.1" on page
    685).
    Subjects
    Noise volume
    Air pollution emissions
    Emission calculation according to HBEFA 3.1

    9.1

    Noise volume
    To calculate noise volumes based on traffic volumes, Visum offers the Noise-Emis-Rls90 and
    Noise-Emis-Nordic procedures. The Noise-Emis-Rls90 procedure is based on the RLS-90 of
    the noise reduction for roads by the German Federal Minister for Traffic, the Noise-Emis-Nordic procedure on the Nordic Council of Ministers (1996) model.
    The model is fairly simple but 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.

    9.1.1

    Noise-Emis-Rls90 procedure
    The 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 Lm(25) using equation (7), RLS-90.
    M = relevant hourly traffic volume (car/h)
    p = relevant HGV proportion in percent of total traffic (above 2.8 t total permissible weight)
    Determination of correction factor DStrO for different road surfaces in accordance with
    table 4, RLS-90. Visum keeps the correction factors listed in this table as an ASCII file
    RLS.DAT in the background.

    PTVGROUP

    679

    9.1.2 The Noise-Emis-Nordic procedure


    Determination of speed correction Dv for permissible maximum speeds other than 100
    km/h using equation (8), RLS-90. For car v_0 is valid from 30 to130 km/h, for HGV from 30
    to 80 km/h.
    Determination of correction factor DStg for inclinations and gradients using equation (9),
    RLS-90.
    Note: The correction factor DE which takes 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 equation (6), RLS-90.

    9.1.2

    The Noise-Emis-Nordic procedure


    This procedure is an enhancement of the Noise-Emis-Rls90 procedure for the Nordic Standard in accordance with the Nordic Council of Ministers (1996). Its calculation is similar to the
    one used in the Noise-Emis-Rls90 procedure.

    9.1.3

    Link attributes for noise calculations


    The two noise calculation procedures require different input attributes (table 284). To understand these input attributes please refer to the explanations and illustrations in the RLS-90.
    The output value Noise is returned as a result.
    Attribute

    Description

    Share of HGV

    HGV-share p (above 2.8 t total permissible weight) of total traffic

    (Input)

    Default: 0
    Value range: 0 to 100

    Slope
    (Input)

    Lengthways link slant g in percent for specifying correction factor


    DStg for inclinations and gradients where the following rules apply:
    DStg = 0,6 |g| -3 for |g| > 5%

    DStg = 0 for |g| 5%


    Default: 0
    Value range: -50 to 50
    SurfaceType
    EWS surface type
    (Input)

    For different road surface types, correction penalties are generated


    and added in accordance with RLS 90, table 4. The respective data
    are stored in the parameters file RLS.DAT (see "Parameters file rls.dat" on page 681).
    Default: 1
    Value range: 1 to 9

    Noise
    Mean emission level Lm,E of long and straight roads in [dB].
    (Output)
    Table 284: Link attributes for noise calculations
    680

    PTVGROUP

    9.1.3 Link attributes for noise calculations


    Parameters file rls.dat
    *Road surface
    permissible maximum speed
    *
    30 km/h
    40 km/h
    * non-porous
    *Mastic asphalt, asphalt concrete
    * Type 1
    0
    0
    *
    *Grooved mastic asphalt
    * Concrete
    * Type 2
    1.0
    1.5
    *
    * Paving with
    * level surface
    * Type 3
    2.0
    2.5
    *
    *other paving
    *
    * Type 4
    3.0
    4.5
    *
    * ZTV Concrete 93
    * with steel brush stroke
    * Type 5
    0
    0
    *
    * ZTV Concrete 93
    * without steel brush stroke
    * Type 6
    0
    0
    *
    * Asphalt concrete 0/11
    * Mastix asphalt
    * Type 7
    0
    0
    *
    * open porous asphalt
    * Grain 0/11
    * Type 8
    0
    0
    *
    * open porous asphalt
    * Grain 0/8
    * Type 9
    0
    0

    50 km/h

    >= 60km/h

    2.0

    2.0

    3.0

    3.0

    6.0

    6.0

    1.0

    -2.0

    -2.0

    -4.0

    -5.0

    The values apply to the correction penalties per surface type.


    The illustration 210 shows an example where noise calculation is illustrated as link bars according to Noise- Emis-Rls90 . In the User Manual you will find further information on implementation (see User Manual: Chpt. 21.5 , page 2187).

    PTVGROUP

    681

    9.2 Air pollution emissions

    Illustration 210: Illustration of noise volume as link bars


    Note: To illustrate the noise volume in traffic networks, we recommend a classification
    according to the DIN standard 18005 Part 2 09.91.

    9.2

    Air pollution emissions


    In Visum, road traffic air emissions can be determined on the basis of the calculation procedure Pollution-Emis (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 cross-section volume.
    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 totaled.

    9.2.1

    Pollution-Emis procedure
    This procedure is based on emission factors issued by the Swiss Federal Office for the Environment (BAFU) for pollutants NOx, CO, HC and SO2, for both cars and HGVs. For each pollutant, a regression curve with polynomes to the 5th degree 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

    682

    PTVGROUP

    9.2.1 Pollution-Emis procedure


    the parameter text files EMI1990.DAT, EMI1992.DAT and EMI2000.DAT. For the reference
    year 1990, for example, the following values are used.
    *
    *
    *
    *
    *
    *
    *
    *

    Input file for flexible emission formulas for Switzerland 1990


    They are polynome to the 5th degree.
    a + bx + cx2 + dx3 + ex4 + fx5

    bx

    (the numbers are exponential)


    (x is the speed of cars or HGVs)

    cx2

    dx3

    ex4

    fx5

    NOx CAR
    0.75860

    2.8004e-2 -9.9187e-4

    1.4276e-5 -5.6655e-8

    0.0

    * NOx HGV
    * CO

    CAR

    * CO

    HGV

    * HC

    CAR

    * HC

    HGV

    24.216

    -0.70194

    1.5878e-2 -1.5996e-4

    16.425

    -0.38357

    2.8706e-3 -4.5425e-6

    45.380

    -3.0729

    9.7880e-2 -1.6116e-3

    2.2155

    -6.6593e-2 8.7930e-4

    -5.1330e-6
    2.3153e-3

    7.1751e-7
    0.0

    0.0
    0.0

    1.3138e-5 -4.1410e-8
    1.1381e-8

    0.0

    46.490

    -3.7859

    0.13382

    1.9258e-5 -6.1410e-8

    101.80

    -3.0309

    4.4557e-2

    -2.8928e-4 7.7300e-7

    0.0

    1980.4

    -87.564

    2.9120

    -5.0701e-2 4.3285e-4

    -1.3577e-6

    * SO2 CAR
    * SO2 HGV

    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.
    The polynome approximation of emissions relative to speed shows the following developments for CO for the different reference years in illustration 211:

    Illustration 211: Emissions relative to speed

    PTVGROUP

    683

    9.2.2 Pollutant-Emis link attributes

    9.2.2

    Pollutant-Emis link attributes


    For the emission calculation procedure Pollutant-Emis, the HGV share is required as input link
    attribute. The link attributes (air pollution) in table 285 are output as output values.
    Attribute

    Description

    Share of
    HGV
    (Input)

    Relevant HGV share in percent of total traffic (above 2.8t total permissible
    weight)

    EDat_NOx
    (Output)

    Nitric oxides in g/km

    EDat_SO2
    (Output)

    Sulphur dioxide in g/km

    EDat_CO
    (Output)

    Carbon monoxide in kg/km

    EDat_HC
    Hydrocarbons in g/km
    (Output)
    Table 285: Pollutant-Emis link attributes
    The illustration 212 shows an example where the nitrogen monoxide volumes are displayed
    as link bars according to Pollution-Emis. In the User Manual you will find further information on
    implementation (see User Manual: Chpt. 21.8 , page 2190).

    Illustration 212: Display of nitrogen monoxide volumes as link bars


    Note: For the display of pollution emissions, we recommend the use of classified values.
    684

    PTVGROUP

    9.3 Emission calculation according to HBEFA 3.1

    9.3

    Emission calculation according to HBEFA 3.1


    This chapter describes the fundamental principle and the basics of the emission calculation
    according to HBEFA (see User Manual: Chpt. 21.10 , page 2191).

    9.3.1

    Fundamental principle
    The HBEFA-based emission calculation procedure allows you to calculate emission values
    by link, by territory or network-wide in Visum. The calculation is based on the Handbook Emission Factors for Road Transport version 3.1. From the Handbook HBEFA 3.1:
    "The Handbook of emission factors for Road Transport provides emission factors, i.e. the specific emission in g/km for all current vehicle categories (PC, LDV, HDV and motorcycles), each
    divided into different categories, for a wide variety of traffic situations."
    Note: The complete HBEFA Handbook is available on the website www.hbefa.net.

    9.3.2

    Basics of the HBEFA calculation in Visum


    In Visum the emission calculation according to HBEFA determines the desired emissions and
    optionally cold start excess emissions. The traffic situation, volumes and fleet compositions are
    taken into account. The traffic situation, volumes and fleet compositions are taken into account.
    Emissions are calculated on the basis of links in Visum. Emissions are not calculated for turns,
    main turns, and connectors.
    For a HBEFA-based emission calculation, you first need to define fleet compositions. The fleet
    compositions suggested by HBEFA per country, calendar year and category (e.g. Car or HGV)
    can be used as a basis here.
    Then, the emissions are calculated with the HBEFA-based emission calculation procedure,
    which can be calculated for either one or several demand segments at the same time.
    The procedure can be calculated in two different ways:
    statically (for analysis period and analysis horizon)
    dynamically (additionally per analysis time interval)
    Note: You can calculate the dynamic variant, if volumes are available for individual analysis time intervals.
    Per demand segment, the volumes for warm emissions and cold start excess emissions stem
    from a selectable attribute. This attribute is interpreted as volume with time reference analysis
    period (AP). When calculating with AP-based volumes, the value is divided by the AP projection factor and multiplied by the AH projection factor.
    When calculating the fuel quality, as an indicator for the plausibility of the calculations, the network-wide fuel consumption (quantity/[g]) collected by demand segment is converted into the
    specific consumption ([l/100km]) separately by diesel and gasoline. First, the quantity is divided by the density of the fuel (gasoline ca. 0,75kg/l, diesel ca. 0,83kg/l) and then related to the
    mileage of the demand segment. The specific consumption by demand segment is displayed
    in the Statistics > Emissions (HBEFA) list and saved to the log file.

    PTVGROUP

    685

    9.3.2.1 Basis for calculating warm emissions


    9.3.2.1

    Basis for calculating warm emissions


    The following data is determined for each link.
    Fleet composition class to be applied:
    The fleet composition class to be applied results from the HBEFA link class of the link type
    and the link attribute Urban:
    HBEFA link class

    Urban

    Fleet composition class to be


    applied

    HBEFA_Motorway-National
    or HBEFA_Motorway-City or
    HBEFA_Semi-Motorway

    ---

    Highway

    Other

    No

    Rural

    Other

    Yes

    Urban

    Note: If you use uniform fleet compositions for each demand segment, the fleet composition for Urban is always applied.
    Gradient class:
    The gradient class results from the attribute Gradient based on the following classification:
    Value range

    Gradient class

    < -5 %

    -6 %

    -5 % to below -3%

    -4 %

    -3 % to below -1%

    -2 %

    -1 % to below 1%

    0%

    1 % to below 3%

    2%

    3 % to below 5%

    4%

    5% and more

    6%

    Level of Service (LOS):


    Depending on the parameter setting, the LOS is determined either directly from the content of the selected attribute or based on a classification by the specified attribute regarding the three specified class limits.
    Note: If you calculate by time interval and the set subattribute type is AHPI with values
    for time intervals, the LOS will be calculated per analysis time interval as well.
    Static traffic situation (i. e. without the LOS share):
    The urban/rural classification results directly from the link attribute Urban, the HBEFA link
    class directly from the link type. The speed class is determined on the basis of the set link

    686

    PTVGROUP

    9.3.2.1 Basis for calculating warm emissions


    attribute (default: v0), while only certain values are possible according to the traffic situation scheme in HBEFA (depending on urban/rural and link class):

    If there is a traffic situation whose speed does not vary by more than 5km/h, which matches
    the characteristic urban/rural and the link class, it will be allocated. In the case of two such
    traffic situations (e.g. 55km/h), the one with the higher speed will be allocated. If no traffic
    situation fulfills this condition, the nearest traffic situation with the same link class will be
    used.
    If no traffic situation matches the specified combination of urban/rural and HBEFA link class,
    the default traffic situation Rural/Motorway-National/80km/h will be used.
    For the used fleet composition, the emission factor weighted by the static traffic situation, the
    level of service and the gradient class will be multiplied for each pollutant to be calculated by
    the value of the volume attribute (AP) specified for the demand segment and by the length of
    the link. The result is the warm emission for this pollutant, this link and this demand segment
    based on the analysis period. Multiplied by the respective projection factor, the amount is
    saved in the respective link attribute (AP and AH) and added to the network-wide emission
    (AP and AH).
    If the calculation is additionally carried out per analysis time interval, the emission factor is
    determined once per interval due to the interval-dependent LOS and multiplied by the volume
    value for this interval and the length of the link. The result is then saved in the subattribute
    associated with the analysis time interval and added to the network-wide time-dependent emission.
    Calculated pollutants
    The following pollutants can be calculated in Visum. The pollutants are divided into three
    groups:
    Group 1: Established measurement programs

    PTVGROUP

    687

    9.3.2.2 Basis for calculating cold start excess emissions


    Element

    Description

    CO

    carbon monoxide

    Fuel

    fuel consumption

    Gasoline

    fuel consumption

    Diesel

    fuel consumption

    PM

    particle matters

    HC

    hydrocarbons

    NOx

    nitrogen oxide

    CO2 reported carbon dioxide "reported", i.e. without the biofuel share in the fuel
    CO2 total

    carbon dioxide "total", computed as total CO2 from fuel consumption

    PN

    Particle number

    Group 2: Complementary measurement programs and literature


    Element

    Description

    Pb

    lead

    benzene

    benzene

    CH4

    methane

    SO2

    sulfur dioxide

    NO2

    nitrogen dioxide

    NMHC

    non-methane hydrocarbon

    Group 3: Indicative literature references


    Element

    Description

    NH3

    ammoniac

    N2O

    nitrous oxide

    Note: The emission factors of the pollutants SO2, Pb and CO2 reported are country specific because they depend on the composition of the fuel. So far, only values for Germany
    can be calculated in Visum.
    9.3.2.2

    Basis for calculating cold start excess emissions


    To determine the cold start excess emissions, firstly, the cold start emissions weighted over the
    shares are calculated for each urban fleet composition used and for each pollutant. For this,
    the supplements per pollutant and subsegment are requested from the HBEFA database.
    The distribution of this emission onto links is done in two different ways, which can be switched via attribute Calculate start excess based on routes at the origin zone:

    688

    PTVGROUP

    9.3.2.2 Basis for calculating cold start excess emissions


    Polygonal calculation
    Calculation on routes
    Note: In HBEFA, cold start excess emissions are not indicated for all subsegments. For
    segments without an available excess, a cold start excess emission of 0 g/start will be
    applied.
    Polygonal, geometrical calculation
    The idea of the geometrical calculation is that the start of a route is diffuse. In the model, it begins at the origin zone and enters the link network via a connector node. Realistic routes, however, begin at an unspecified nearby location in the network. This is where the cold start excess
    emission originates, too. And this is used to avoid the calculation on routes as follows.
    For each origin zone, firstly, the absolute cold start excess emission is calculated as total over
    the demand segments over the products from the value of the attraction attribute of the
    demand segment multiplied by the share of cold start and the emission factor of the respective
    pollutant for the fleet composition to be applied. This absolute emission per pollutant is distributed length proportionally to all links that are not closed for the PrT which lie within a radius
    of 1km around the convex hull of the connector node of the zone. Cold start excess emissions
    which arise from different zones are accumulated.
    Calculation on routes
    In order to determine the cold start excess emissions on routes, all routes of the demand segments to be calculated are evaluated from the origin to the destination. For each traversed link,
    a cold start excess share AP,S is calculated as the integral of the decay function over the link
    length. This share is multiplied with the volume of the route and the share of cold start of the origin zone of the route. Any attribute, whose content does not have to correspond to the total of
    the volumes of all routes, can be used as volume value when calculating the warm emissions.
    In order to calculate meaningful cold start excess emissions anyhow, the value is divided by
    the volume of the demand segment afterwards and multiplied by the value of the volume attribute. That implies that the relation between the route volume and the link volume multiplied by
    the value of the volume attribute yields the assumed route volume on the link, which, however,
    does not have to be constant along the route any more. Per link, the value is summed up over
    all routes. The evaluation of the routes can end as soon as the first four kilometers of the route
    are traversed, because the decay function is constantly 0 thereafter.
    After that, for each link, pollutant, and demand segment, the calculated value is multiplied with
    the cold start excess emission factor of the fleet composition allocated for urban and projected
    over AP and AH.
    As in the case of the polygonal method, the calculated absolute emission of the zone is then
    distributed proportionally to this indicator per link onto the links. Please note that this does not
    yield the exact dynamic route volumes but an acceptable approximation. In order to use the
    dynamic route volumes in the procedure, the traffic flow model of the used dynamic assignment would have to be reproduced. The volume per analysis time interval calculated from
    these dynamic route volumes during the assignment is used instead.

    PTVGROUP

    689

    9.3.2.2 Basis for calculating cold start excess emissions


    Like the other emissions, the cold start excess emissions are aggregated network-wide and
    issued in the statistics list Emissions (HBEFA).
    Note: If no routes are available for a demand segment and the calculation on routes is
    demanded at a zone, no cold start excess emissions will be calculated for this zone. Besides the explicit rejection of the routes, this is for example the case if you want to determine emissions of service buses using a separate, artificial demand segment whose
    volumes result from, for example, the number of service trips. Here, the omission of the
    cold start excess emissions is in line with the fact that almost all of the trips are warm. The
    procedure can, however, still be run.

    690

    PTVGROUP

    10 GIS functions

    10

    GIS functions
    Visum allows you to include data from geographic information systems (GIS) into your model.
    Both ESRI shape files (file extension *.shp ) and the Personal Geodatabase (PGD) are supported. Visum also offers typical GIS functions such as the different objects or different coordinate systems for georeferencing your network. Furthermore, functions for network
    digitalization (GPS tracking) and visualization (legends, backgrounds, texts, polygons) are offered, which make network data preparation for presentations easier.
    Other GIS typical functions have already been discussed at some other point:
    Integrating symbolic illustrations (see "Points of Interest (POI)" on page 81)
    Showing and hiding layers (see User Manual: Chpt. 24.2.2 , page 2339)
    Freely definable coloring for network objects (see User Manual: Chpt. 24.2 , page 2337)
    Subjects
    Connection to the Personal Geodatabase and GIS objects
    Shape files as a GIS interface
    Intersect
    Coordinate systems
    Processing the network display with graphic objects
    GPS tracking

    10.1

    Connection to the Personal Geodatabase and GIS objects


    Visum can temporarily connect itself with an ESRI Personal Geodatabase (PGD) or a shape
    file. This function can be useful for example, when a traffic modeler working with Visum,
    connects to a Personal Geodatabase on the computer of a land use planner. The traffic modeler can then take the required data from the Personal Geodatabase of the land use planner by
    means of intersection (see "Intersect" on page 696) and then cut the connection. This process
    bypasses the need to import the file back to Visum.
    Note: To be use this function, you need a license for the ArcGIS program.
    During the connection to the PGD, so-called GIS objects are created in Visum. GIS objects are
    POI-like network objects (see "Points of Interest (POI)" on page 81), which are only available
    during a PGD connection. Analogous to POIs, GIS objects are organized into GIS categories.
    A GIS object is either of type point, polyline or polygon.
    GIS objects have a spatial reference. This can be used for example, to illustrate the following
    objects in the Visum network.
    Schools, swimming pools, stops
    Stretches of water, agricultural areas, planning districts
    To create GIS objects in Visum, you have to either select the PGD Feature Classes or Feature
    Datasets for display or editing. The following objects are thus created in Visum:
    For each selected Feature Class of the Personal Geodatabase, a GIS category is created.
    For each Feature a GIS object

    PTVGROUP

    691

    10.2 Shape files as a GIS interface


    None of the coordinates transferred to Visum are being converted. The GIS objects are always
    removed again as soon as the connection to the PGD has ended. If you want to permanently
    include GIS objects into the Visum network, proceed as follows:
    Convert the GIS objects into a shape file
    Read the GIS objects as POI for example
    The following applies during the Personal Geodatabase connection:
    Only key information on the objects is stored permanently.
    Information on attributes of the category is available through an attribute interface.
    Read and write access to the attributes is transferred directly to the database.

    10.2

    Shape files as a GIS interface


    Shape files are a data format for geodata, which are used in most GIS. The data format is especially suitable for the data exchange between Visum and GIS. With Visum you can read and
    save shape files.
    Note: To save shape files you need the Shapefile converter. add-on.
    A shape file is not an individual file, but is made up of three files:
    File *.shp for saving geometry data
    File *.shx contains the geometry index to link to the attribute data
    File *.dbf contains attribute data in dBase data format. You can assign the attributes contained here a Visum attribute, when reading the shape file (see User Manual: Chpt.
    25.12.2 , page 2646).
    Shape files can contain points, lines or polygons (surfaces). Only one type of element can be
    contained in a shape file.
    Note: A technical description of the data format can be found on the Internet at www.esri.com/library/whitepapers/pdfs/shapefile.pdf.

    10.2.1

    Importing shape files


    When importing shape files, the information contained in shape files is read in a Visum network. Which network it is imported to depends on the type of shape file (point, line or polygon)
    and by which processing mode (additive or non-additive). An overview on which shape file
    types are imported to which network objects is provided by table 286.
    Link, Screenline, Zone, Main zone, TerConnector
    ritory, Main node
    Point
    Polyline

    Node, Detector, Count POI


    location, Stop, Stop
    point

    X
    X

    Polygon
    X
    Table 286: Reading shape files in Visum network objects

    692

    X
    X
    X

    PTVGROUP

    10.2.1 Importing shape files


    Note: Creating POIs is only possible with additive reading of shape files, because a POI
    category has to be specified, where the POIs can be included. At least one POI category
    has to therefore be contained in the network, to read shape files as POIs.
    Connectors, stop points, and count locations can only be read in additively.
    If you want to import a shape file containing stop points as point objects, you have to import
    them as nodes first and then use the "Aggregate isolated nodes" function to create stop points,
    together with corresponding stop areas and stops (see User Manual: Chpt. 15.12.14 , page
    1076).
    While reading polylines as links, you can create alternative directed links or links with both
    directions. If a link is undirected, it has to be determined how to interpret each attribute.
    Forward: direction from node ... to node
    Backward: direction to node ... from node
    Undir. value: 50% of the value for each direction
    Symmetrical: equal value for both directions
    While importing the shape file you can determine which source attribute (from the shape file)
    should be assigned to which target attribute (an existing or user-defined attribute of the selected network object). The illustration 213 shows an example, where shape file data are read as
    a link. The shape file contains the attributes STREET_ NAM, LENGTH and LANE, which allocate the Visum link attributes Name, Length and Number of lanes.
    Note: When loading polygons from shape files (e.g. as zone polygons or POIs for a background image), you can optionally activate normalization of the loaded surface data (see
    "Multi-part surfaces" on page 124). This is required if you want to use the loaded polygons to perform geometrical operations, such as surface calculation or intersections, as
    otherwise the results might be falsified. If you merely wish to display polygons, then normalization is not required.

    Illustration 213: Source and target attribute allocations

    PTVGROUP

    693

    10.2.2 Exporting shape files


    Example applications
    Reading shape files with a road network as links in Visum. In Visum a routing-enabled
    link network is then available.
    Note: The links have to first be enabled for transport systems.
    Reading cross-communities as territories
    Reading schools as POIs
    Reading land use as POIs
    In addition to the import of shape files as Visum network objects, you can also insert shape
    files as background. This is how you can insert land use (for example residential areas, industrial areas, commercial areas) to make your network more visible, for example. You can thus
    insert multiple shape file layers into the network (for example a layer for industrial areas). The
    drawing order of the layers and its color can be changed. The illustration 214 shows an example, where two shape files were integrated as a background with land use for residential and
    commercial areas.

    Illustration 214: Land use from two shape files as background

    10.2.2

    Exporting shape files


    Note: Exporting shape files is only possible with the Shapefile converter add-on.
    Exporting shape files can be useful for example, if you want to use calculation results such as
    link volumes from a Visum assignment in a GIS. Shape files can also be used to exchange
    data with other users who only work with GIS and do not have a Visum installation.

    694

    PTVGROUP

    10.2.2 Exporting shape files


    For network objects nodes, stop points, stops, links, zones, main zones, territories, line routes,
    screenlines, connectors, POIs and detectors, binary shape files can be saved directly from
    Visum respectively. For each network object type you select, a file with the extension *.shp,
    *.shx, and *.dbf is saved. Additionally, Visum creates a *.ctf file for each exported shape file.
    Visum renames attribute identifiers, which are longer than 10 characters, because shape files
    do not support attribute identifiers with more characters. This is documented in the *.ctf file.
    If a projection is defined in Visum, Visum creates a *.prj file for each network object type, with
    the currently set projection (apart from during the setting Visum, which means no projection).
    This does not guarantee that when reading the shape file to another network, which has a different projection of coordinates, the coordinates of this network remain constant.
    The table 287 shows in which shape types the Visum network objects are illustrated.
    Point
    Nodes

    Polyline

    Polygon

    Main nodes

    Main node centroids

    Stop points

    Stops

    Links

    Zones
    Zone centroids

    X
    X

    Main zones
    Main zone centroids

    X
    X

    Territories
    Territory centroids

    X
    X

    Line routes

    Screenlines

    Connectors

    Count locations

    Detectors

    POIs
    X
    Table 287: Illustration of Visum files of shape types

    When exporting shape files, the following special cases have to be noted.
    Links
    If links are saved undirected, only one object is created for both directions. The attributes
    of the From node keep their name. Attributes of the opposite direction all start with an "R_
    ". If the option Directed is active, an individual object is saved in the shape file for each
    direction.

    PTVGROUP

    695

    10.3 Intersect
    Connectors
    You can select whether the first point of the object should be the zone (standard setting)
    or the node. For each single object the attributes of both directions are always stored.
    Reverse attributes contain the entry R_as prefix. The specified direction is always taken.
    POIs
    POIs can be point, polygon or polyline and are thus exported to three different files.

    10.3

    Intersect
    The "Intersect" functionality known from GIS describes the overlap of two subject levels of the
    same area section with the aim of gaining new information. This can be used to link two network objects which overlap each other (intersection) and saves the thus resulting information
    in an attribute. To create a demand model, GIS structure data (such as the number of employees or the number of pupils) can for example be read in POI polygons and these intersected
    with zones. The result being the type of structure data for each zone (number of employees or
    pupils per zone) in a Visum attribute.
    The intersection area of two objects results from the spatial overlapping of both objects. illustration 215 shows examples of overlapping network objects.

    Illustration 215: Examples of overlapping network objects


    Use cases
    A typical use case for an intersection is the data import from a GIS.
    696

    PTVGROUP

    10.3 Intersect
    There are land use data in GIS
    Land use data are imported to Visum using a shape file, which is read in a POI. (Alternatively Visum can be connected to a Personal Geodatabase. Land use data in Visum are
    then available as GIS objects.)
    The zone and an editable attribute are later selected as target object, to adapt the created
    information.
    Through the intersection of zones and POIs the result is the land use data per zone and
    can for example be used in a Visum demand model (for example the number of homes
    per zone).
    Intersection is not just confined to data exchange with GIS. Multiple application possibilities
    also arise within Visum. Some examples, which information can be obtained with an intersection operation are introduced in the following.
    Number of boarding PuT passengers per zone (table 288)
    Number of inhabitants in the catchment areas of line routes (table 289)
    Number of inhabitants in the catchment areas of stops (table 290)
    Vehicle kilometers within territories (table 291)
    Number of the zone where the stop point lies (table 292)
    Numbers of the stops within a zone (table 293)
    Average number of boarding PuT passengers at the stops of a zone (table 294)

    Intersecting zones and stop points: The passengers in a zone are calculated from the
    ZoneAddValue1 = Sum of passengers at all stop points in the zone polygon.
    Table 288: Calculating the number of PuT passengers per zone

    PTVGROUP

    697

    10.3 Intersect

    Intersecting line routes and zones: The inhabitants of a line route are calculated from
    LineRoute.AddValue1 = Sum of inhabitants in zones within a 500m buffer around the line
    route.
    Table 289: Calculating the number of inhabitants in the catchment areas of lines

    Intersecting stops and zones: The inhabitants of a catchment area of stops are calculated
    from Stop.AddValue1 = Sum of inhabitants in zones within a 500m buffer around the stop.
    Table 290: Calculating the number of inhabitants in the catchment areas of stops

    698

    PTVGROUP

    10.3 Intersect

    Intersecting territories and links: The vehicle kilometers in a territory are calculated from
    Territory.AddValue1 = Sum of VehicleKm PrT via all links in a territory.
    Table 291: Calculating the vehicle kilometers within territories

    Intersecting stop points and zones: In which zone a stop point lies, is calculated from
    StopPointAddValue1 = smallest zone number of the zone where the stop point lies
    (Please note that the minimum is selected here, because theoretically, a stop point could
    lie in two zones, if its polygons overlap. One of the other three functions, however, could
    also be selected). If you want to determine all zones in which the stop point lies, use a target attribute of the type Text and Concatenate as aggregate function.
    Table 292: Calculating the zone number where a stop point lies

    PTVGROUP

    699

    10.3 Intersect

    Intersecting zones and stops: which stops lie within a zone. As target attribute, a user-defined attribute of the type Text is used, to which a concatenated list of the numbers of the
    stops will be saved.
    Table 293: Determination of the numbers of the stops that lie within a zone
    The target attribute values can either be calculated as a sum, mean value, minimum or maximum of the source attribute values. If for example you do not want to calculate the total number
    of PuT passengers per zone (table 288), but the average number of PuT passengers at the
    stops of a zone, proceed as described in table 294.

    Intersecting zones and stops: The average number of passengers at stops in a zone is calculated from the ZoneAddValue1 = Average number of departures at all stops within the
    zone polygon.
    Table 294: Calculating the average number of PuT passengers at the stops of a zone
    Note: If you want to calculate the number of source objects per target object, select the
    attribute 1.0 of the source object.

    700

    PTVGROUP

    10.3 Intersect
    Buffer
    To carry out intersections, at least one involved network object type has to be two- dimensional. To obtain this, a buffer can be created around a network object.
    A buffer assigns an area to a point object, line object or a polygon. The resulting area is intersected along with the actual network object. An object point thus becomes a two-dimensional
    object when calculating the intersection.
    The buffer is not defined based on the polygon centroid, but on each point of the polygon. This
    means, that the buffer is also placed around the polygon like a belt.
    Source or target objects are first inflated by the set buffer size (s). The proportion is then calculated by which the target buffer overlaps the source buffer(s). Together with the attribute
    value of the source object, this share then enters the attribute value of the target object.
    The buffer operation (obj, radius) assigns the area (buffer) resulting from all points that have a
    distance of radius to a point of obj to the particular object. Radius = 0 results in the obj itself.
    In the case of polygon objects, polygons plus their buffers are intersected.
    Intersections
    The intersection procedure determines source objects that overlap with a specific target
    object. The attribute data of such a target object is aggregated according to the option selected
    and is then assigned to the target object. The available aggregate functions and their effect
    depend on the data types of the source and target attributes (table 295). The respective aggregation functions are available in the combinations of the table only.
    Aggregate function Data type target
    attribute

    Data type source


    attribute

    Effect

    Sum

    Numerical

    Numerical

    Text

    Numerical

    Sum source attribute


    values, weighted by
    overlapping area,
    where applicable

    Numerical

    Numerical

    Text

    Numerical

    Mean value

    PTVGROUP

    Mean value of the


    source attribute values,
    weighted by overlapping area, where
    applicable

    701

    10.3 Intersect
    Aggregate function Data type target
    attribute

    Data type source


    attribute

    Effect

    Minimum / Maximum Numerical

    Numerical

    Minimum / Maximum of
    the source attribute
    values, weighted by
    overlapping area,
    where applicable

    Number

    Concatenate
    Histogram

    Text

    Numerical

    Text

    Text

    Minimum / Maximum of
    the source attribute
    values (comparison of
    the strings)

    Numerical

    Numerical

    Text

    Numerical

    Number of overlapping
    objects

    Text

    Text

    Text

    Numerical

    Text

    Text

    Text

    Numerical

    Text

    Text

    Concatenated list of the


    source attribute values
    Concatenated list of the
    source attribute values
    and the number of their
    occurrence at overlapping objects

    Table 295: Available aggregate functions for intersection


    For numerical source and target attributes, you can either choose to use the full source attribute data or a share of the data that is proportional to the overlapping area with the source
    object. This section describes the results of the two options.
    Note: To determine the number of source objects per target object, or the ID-number of a
    surface object overlapping with another surface object, choose the full source attribute
    data. In nearly all other cases, choose the proportional share of the source attribute data.
    There are three types of intersections:
    Surface with surface
    The intersection
    of two polygons is defined as usual.
    Surface with point
    If a surface is intersected with a point, the attribute value of the point is counted 100%, if
    the point lies within the polygon. Otherwise it is counted with 0%.
    Surface with line
    The intersection of a surface with a line object is the share of the line object within the surface.
    The polygon content content(P) of a polygon is defined as usual. The following also applies:

    702

    PTVGROUP

    10.3 Intersect
    For line objects obj, content(obj) = length(obj) is defined.
    For point objects obj the content(obj) is defined as infinitesimal > 0. An infinitesimal number is a number whose absolute value is greater than zero but less than any positive real
    number be it ever so small. Content defines the overlapping share of objects. A source
    polygon P2 overlaps for example, the target polygon P1 with the following share.

    .
    If a buffer > 0 is assigned to a point or line object, it turns into a polygon.
    When you choose to use a share of the source attribute data proportional to the area overlapping with the source object, this share is calculated as follows:

    When you choose to use the full source attribute data, the share is 100%, if source and target
    object overlap (including buffers). Otherwise it is 0%. In this case the size of the overlapping
    area is not relevant.
    Intersection then results in:

    with P1 = buffer(targetobj, targetradius), P2 = buffer(sourceobj, sourceradius).


    Note: The share of a point object equals 1 if it lies within the polygon, 0 if it is positioned
    outside of it. A line object has a share x of a buffer if x = length of the section contained in
    the buffer / total length.

    PTVGROUP

    703

    10.3 Intersect
    The following examples show the effect of the intersect operation in Visum.

    Illustration 216: Intersecting three polygon objects with a link buffer


    In illustration 216, surfaces are intersected with surfaces. The intersection of two polygons is
    defined as usual.
    Prorated intersection of polygon and link buffer (1)
    Polygon is located inside of link buffer - intersection of 100% (2)
    Polygon is located outside of link buffer - intersection of 0% (3)

    Illustration 217: Intersecting point objects with a polygon


    In illustration 217 , for those point objects outside of the polygon, intersection results in 0%, for
    the three point objects inside of the polygon, intersection results in 100%. If 1.0 is selected as
    source attribute, all stops (source object) per zone (target object) are counted here for example (since value of source object = 1.0).

    Illustration 218: Intersecting point objects with a buffer polygon


    704

    PTVGROUP

    10.4 Coordinate systems


    In illustration 218 , for those point objects outside of the buffer polygon (= polygon + buffer),
    intersection results in 0%. The intersection share within the buffer polygon is 100% for all point
    objects. Six points are thus intersected with 100%.

    Illustration 219: Intersecting point object buffers with polygons


    If point objects are intersected with polygons, the intersection share of a buffer results per polygon from the position of the buffer in the respective polygon. In the illustration 219, two point
    object buffers with 100% share are intersected and one point object buffer prorated (its remaining shares intersect with polygon 2 and 3) for polygon 1.
    If a polygon is positioned exactly next to an adjacent one and a buffer is defined as > 0, point
    objects within the overlapping area will be counted twice, because the polygon buffers overlap
    each other and the point object lies within two polygons with buffers. The resulting number of
    point objects regarded for intersection is then greater than the actual number of point objects.

    10.4

    Coordinate systems
    When creating networks, components from different GIS sources are often combined, which
    partially refer to different coordinate systems. To make the data consistent a coordinate transformation is necessary. Visum supports you with this task with the following functions.
    The user can optionally specify that all coordinates in the current network belong to a predefined coordinate system (see User Manual: Chpt. 22.1.1 , page 2207).
    The coordinate system can be changed in Visum. You can automatically transform the
    coordinates of the current network (see User Manual: Chpt. 22.1.1 , page 2207).
    If data are imported, which apply to another coordinate system than that for the current network, Visum automatically transforms the imported coordinates into the system of the current network.
    There is an option to switch from the default Visum to a predefined coordinate system. Visum
    offers a selection of coordinate systems, which are provided as files with the extension *.prj .
    You can find them in the directory ...Program files\PTV Vision\PTV Visum 13\Exe\Projections.
    This file format is Well-Known-Text-Format in ESRI version.

    PTVGROUP

    705

    10.4 Coordinate systems


    Note: You can optionally specify, whether you want to work with a current projection in
    your project. It is usually sufficient to keep the standard setting ("Visum"). In this case coordinates in Visum do not apply to any current projection, but are illustrated "uninterpreted"
    in a rectangular system. If, however, original files are specified in a certain projection and
    are imported to a network, where no projection has been selected, the display is distorted. In this case select the suitable projection.
    In Visum, a difference is made between geographic coordinate systems and projected coordinate systems.
    In geographic coordinate systems, the coordinates are displayed as spherical coordinates
    with geographic length and width. They are measured as an angle from the earth's center to a
    point on the earth's surface (for example 47 6northern latitude, 12 27eastern longitude). In
    comparison, the coordinates of the earth ellipsoid is projected to a level, for plane coordinate
    systems. A location on earth is therefore distinctly determined as an X and Y coordinate on the
    level. The following example shows two projection files for a planar and a geometric coordinate system in Visum.
    Example for planar coordinate system (WGS 1984 UTM Zone 48N.prj)
    PROJCS["WGS_1984_UTM_Zone_48N",
    GEOGCS["GCS_WGS_1984",
    DATUM["D_WGS_1984",
    SPHEROID["WGS_1984",6378137,298.257223563]],
    PRIMEM["Greenwich",0],
    UNIT["Degree",0.017453292519943295]],
    PROJECTION["Transverse_Mercator"],
    PARAMETER["False_Easting",500000],
    PARAMETER["False_Northing",0],
    PARAMETER["Central_Meridian",105],
    PARAMETER["Scale_Factor",0.9996],
    PARAMETER["Latitude_Of_Origin",0],
    UNIT["Meter",1]]

    Table 296: Planar coordinate system


    Example for geographic coordinate system is the German Main Triangle Network (Deutsches
    Hauptdreiecksnetz.prj):
    GEOGCS["GCS_Deutsches_Hauptdreiecksnetz",
    DATUM["D_Deutsches_Hauptdreiecksnetz",
    SPHEROID["Bessel_1841",6377397.155,299.1528128]],
    PRIMEM["Greenwich",0],
    UNIT["Degree",0.017453292519943295]]

    Table 297: Geographic coordinate system


    Note: Please note, that in the actual file *.prj the projection properties which are written
    down row by row, have to be successive (in a row). Detailed information on how to create
    projections can be found on the ESRI homepage (for example at www.support.esri.com/index.cfm?fa=knowledgebase.techArticles.articleShow&d=14056).
    706

    PTVGROUP

    10.5 Processing the network display with graphic objects


    Visum manages coordinate systems in the following file types: Depending on the file type,
    coordinate information is saved or imported differently.
    File type

    Write

    Read

    *.ver Version
    file

    All attributes of the current


    coordinate system are
    saved.

    All attributes of the current coordinate system are read in. If the name of the system
    is not found in the list of predefined systems, it is added to the selection. A *.prj
    file is not created.

    *.net, *.mdb,
    *.accdb Network file Database

    All attributes of the current


    coordinate system are
    saved.

    If not read-in additionally, the file is read


    like a version file, in case the network
    parameter block is missing, the standard
    setting (Visum) is applied. If read-in additionally, the network parameters block is
    read-in in case it exists and is enabled
    (see User Manual: Chpt. 14.4.7 , page
    851).

    *.shp Shape file In addition to the shape file,


    a *.prj file with the currently
    set projection is created if it
    differs from the standard setting (Visum).

    If a corresponding *.prj file exists for a


    shape file, it is used as projection and
    transformed into the currently set projection if applicable. If it does not exist and
    the existing network has a coordinate system, the user selects a coordinate system
    (see User Manual: Chpt. 22.4.1 , page
    2221).

    *.inp Vissim net- The coordinates are written not applicable


    work
    to the *.inp file without further
    transformation.
    *.hgr Background file

    10.5

    not applicable

    Background files are not adjusted.

    Processing the network display with graphic objects


    Visum offers many possibilities to process your network model for print-out or presentations.
    Furthermore, the clarity of your network can be improved, by providing additional information,
    such as texts or borders of areas. This is done with so-called network-independent graphic
    objects. In contrast to network objects, network-independent graphic objects are not part of the
    network model, which means they have no influence on the calculations carried out by Visum.
    In addition to the network-independent graphic objects, you have the possibility to insert a
    legend, using a legend assistant. The following functions are available:
    Inserting texts (see "Texts" on page 708)
    Automatic creation of a legend (see "Legend" on page 708)
    Inserting polygons (see "Polygons" on page 714)
    Inserting background graphics (see "Backgrounds" on page 709)

    PTVGROUP

    707

    10.5.1 Texts

    10.5.1

    Texts
    Texts serve to additionally label the network display. There are two text types:
    Background texts
    Texts which are added to the network display
    Legend texts
    Texts which are inserted into a legend
    Note: Graphic texts are network-independent graphic objects and therefore be differentiated from labels of network objects and labels for plot output.

    10.5.2

    Legend
    Using the Legend function, in the Visum network display or schematic line diagram, you can
    show additional, descriptive and explanatory information. To do so, in the legend, select the
    objects you want to show and specify the display style (see User Manual: Chpt. 22.9 , page
    2255). In addition, in the legend footer, you can insert user-defined information, e.g. diagrams
    created with external programs (illustration 220).

    Illustration 220: Legend with user-defined texts


    708

    PTVGROUP

    10.5.3 Backgrounds

    10.5.3

    Backgrounds
    Including backgrounds allows you to improve network display and orientation as well as add
    graphic information to scale. This is how a zoning plan or a city map can be applied to the
    background of the network display for example. Graphic background data can be provided in
    different ways. You can insert existing files in various graphic or GIS formats as a background
    for your network display. Vector graphics, e.g. *.shp or *.dxf as well as raster graphics, e.g.
    *.jpg, *.bmp or *.sid, are supported.
    Besides existing graphic files, you may also use city maps or aerial and satellite images, provided by map services on the Internet, as your background image. Map providers offer highresolution aerial and satellite images as well as detailed city maps for many regions. Apart
    from commercial offers such as Microsoft Bing Maps (see "Backgrounds by Bing Maps" on
    page 710), there is free data available by map providers, e,g. OpenStreetMap, that you may
    use under certain conditions. You can download the map data automatically and insert it as
    your background. If you have a permanent Internet connection, you can show the Background
    graphic layer as an alternative to a statically embedded background. The graphic layer contains the background graphics that match a network section. They are called dynamically by
    map providers on the Internet (see User Manual: Chpt. 22.7.1.1 , page 2237).
    Note: Using data from map providers is subject to license terms and conditions. Please
    learn about these terms in advance and consider them when working on projects and
    sharing results.

    10.5.3.1

    Dynamic background map


    The graphic layer Background map dynamically embeds maps and aerial images of map services into network display. The data matching the current network section is shown at the
    respective zoom level. You can optionally show the map data in shades of gray or pale colors,
    so as to not overpower the network display (see User Manual: Chpt. 22.7.1.1 , page 2237).
    Compared to static backgrounds, the display is controlled exclusively via graphic parameters
    and options. There are no additional functions for administration. The data are not saved to the
    system, so that this functionality requires a permanent Internet connection.
    To use it, you need to select a coordinate system for the network. You can use any of the coordinate systems defined in Visum. The background maps are transformed to the coordinate system selected in Visum and are then displayed. If in Visum you select the coordinate system
    used by the map provider, no transformation is required and the background map can be displayed quicker. Most map services use a special type of Mercator projection (see "Coordinate
    systems" on page 705). The projection files delivered with Visum include this coordinate system as so-called WGS 84 - Pseudo-Mercator (adapted EPSG 3857) (see User Manual: Chpt.
    22.1.1 , page 2207). When you start a new session or open a new network, this coordinate system is your default setting. The definition of this coordinate system largely corresponds to the
    one defined in EPSG 3857, however, with minor changes that allow it to be used with common
    map services and Visum.
    By default, Visum provides several map services in the Graphic parameters. You may also
    define map services that can be used alternatively (see User Manual: Chpt. 22.7.1.3 , page
    2240).

    PTVGROUP

    709

    10.5.3.2 Statically embedding background images by map providers


    To set up a user-defined map service, you need to know the URL structure and projection this
    service uses to call map sections. You then enter a URL template for the service. It contains
    several wildcards, e.g. for map section and zoom level parameters. When calling a specific
    map section, Visum replaces the wildcards with the current data (see User Manual: Chpt.
    22.7.1.3 , page 2240). In the Graphic parameters and version file, map services are only referred to via their names. User-defined map services must have the same name on all computers
    using them. You can ensure this by exchanging a user preferences file (see User Manual:
    Chpt. 14.8.2 , page 869). This makes sure that changes made to the configuration data of
    user-defined map services become effective in all the following Visum sessions, irrespective of
    the version file used.
    10.5.3.2

    Statically embedding background images by map providers


    Besides using the dynamic graphic layer Background map, you can embed data provided by
    map services as static backgrounds. Compared to the Background map, the downloaded data
    is saved to the hard drive, so that it is available without a permanent Internet connection (with
    the exception of Bing Maps).
    Map providers offer maps and aerial photos in a pre-arranged tile configuration. They come in
    a graphic format (e.g. JPEG or PNG) and in a uniform size that allows for several detail levels.
    The data are available in a projected form, usually in Mercator projection (see "Coordinate systems" on page 705). Visum automatically downloads the tiles for the current network section
    (in the detail level selected) from the map provider, converts the data into the coordinate system format used in Visum and integrates the data as background objects. Depending on the
    size of the current network section, the original tiles are combined to several large files. The
    background files generated are saved to special background folders in the project directory.
    The folder structure is shown in the Administration tab, in the Background window. You can
    use the Administration function to control the visibility of network backgrounds (see User
    Manual: Chpt. 22.7.4 , page 2244).
    Note: To use background images of map providers you need to set a coordinate system
    for your network (see User Manual: Chpt. 22.1.1 , page 2207). Background images of
    freely accessible map providers are downloaded once and saved to the computer. The
    embedded maps are not automatically updated or adapted to a different network section.
    This is why the use of freely available map data does not require a continuous Internet
    connection. If you want to update background images, delete the existing ones and
    embed new ones.

    10.5.3.3

    710

    Backgrounds by Bing Maps


    In addition to the maps by freely available map providers, Visum provides the possibility to use
    high-resolution aerial pictures and maps by Bing Maps as background graphics. Due to the
    terms of use of Bing Maps, these data cannot be stored permanently. Therefore, Visum only
    saves the sections and zoom levels for which backgrounds of Bing Maps were embedded in
    the graphic parameters and in the version file, and reloads them from Bing Maps each time
    they are used. This ensures that the latest available map material is always used. Different
    functionalities for the administration of backgrounds are thus not available for Bing Maps backgrounds.

    PTVGROUP

    10.5.3.4 Background images from graphic and GIS files


    Notes: Backgrounds by Bing Maps are only available to customers with maintenance
    agreements.
    In order to use Bing Maps backgrounds, a coordinate system must be set for the network
    (see User Manual: Chpt. 22.1.1 , page 2207). Unlike to the use of background images of
    freely accessible map providers (see "Statically embedding background images by map
    providers" on page 710), you need an Internet connection for each session. The update
    of the backgrounds is automatic.
    10.5.3.4

    Background images from graphic and GIS files


    Backgrounds in graphics formats (table 298 ) supported by Visum can be freely scaled by the
    user and placed where required in the network display. This means, that position and size are
    determined via virtual, modifiable coordinates. It is possible to put several backgrounds on top
    of each other. Their order of display can be changed by the user. The illustration 221 shows a
    network section without background. Only the link network is displayed. Backgrounds with
    land use were inserted in the same network background in illustration 222.

    Illustration 221: Visum network display without background

    PTVGROUP

    711

    10.5.3.5 Supported background file formats

    Illustration 222: Visum network display with background


    10.5.3.5

    712

    Supported background file formats


    The table 298 outlines the most important graphic formats, which can be imported into Visum
    via graphic object type backgrounds.
    File type

    Description

    *.bmp (dib)

    Bitmap: pixel-based Windows standard format

    *.wmf (emf)

    Windows Metafile: both vector- and pixel-based Windows graphic format


    (standard and enhanced format)

    *.gif

    Graphics Interchange Format: pixel-based standard format by Compuserve


    for internet applications

    *.jpg

    Joint Photographic Experts Group: standard pixel-based format for internet


    applications developed by an ISO experts group

    *.jp2

    The JPEG2000 format also published by Joint Photographic Experts Group.


    Compared to JPG, this format offers a better compression rate and can also

    PTVGROUP

    10.5.3.6 Automatic positioning of the background in the network with World files
    File type

    Description
    receive meta data.

    *.png

    Portable Network Graphics: License-free raster graphics format for Internet


    applications. It was developed by the World Wide Web Consortium (W3C) to
    replace GIF and JPG.

    *.psd

    Photoshop: Popular pixel-based format by Adobe for professional image processing on PC

    *.tif

    Tagged Image File: pixel based default format for DTP and scanner applications; also with CCITT compression

    *.tga

    Targa: Pixel-based format by Truevision for professional image processing


    on Workstations

    *.dwg

    A CAD format developed by Autodesk for CAD software AutoCad. The DWG
    format today, is a de facto standard for CAD data exchange and the most commonly used drawing data format.

    *.dxf

    Drawing Interchange Format: A vector graphic format developed by Autodesk, for CAD data exchange, which was developed for the CAD program
    AutoCAD. A *.dxf file writes a CAD model (for example a technical drawing)
    as text according to the ASCII standard.

    *.ecw

    Enhanced Compression Wavelet: ECW is a raster graphic format, which


    allows very high compression rates. It is therefore ideal for saving aerial photographs and satellite images.

    *.shp

    Shape files are a data format for geodata, which are used in most GIS. The
    data format is ideal for including GIS data in Visum(see "Shape files as a GIS
    interface" on page 692).

    *.sid

    Multiresolution seamless image database


    MrSID is a compressed format for raster graphics. It is ideal for cartographic
    data and satellite images.

    *.svg

    Scalable Vector Graphics


    Standard for describing two-dimensional vector graphics in the XML syntax.
    The main language volume can be displayed by the most used web browsers
    without additional plug-ins (for example Firefox). A plug-in such as the SVG
    Viewer by Adobe allows the display on the Internet Explorer.

    Table 298: Background formats supported by Visum


    10.5.3.6

    Automatic positioning of the background in the network with World files


    If a raster graphic background is to be included in Visum, georeferencing the background in
    the network can be executed automatically, if in addition to the actual graphic file (for example
    Background.jpg) a so-called World file (for example Background.jpw) is available, which contains the data for georeferencing the image file. If a World file is available, this makes the
    exchange and including backgrounds much easier, because the background is automatically
    inserted in the right position in Visum. The effort for vernier adjustment of the background does
    therefore not apply.

    PTVGROUP

    713

    10.5.4 Polygons
    A World file contains the transformation information used by the image, for the reference to
    world coordinates. The format was specified and introduced by ESRI. The naming convention
    for World files provides, that the last letter of the file ending of the graphic file is replaced with a
    w, the rest of the file name corresponds to the respective graphic file (if the graphic is named
    Map.tif for example, the respective World file is then named Map.tiw). A World file describes
    the coordinates, the scale and the rotation of the background.
    Note: World files do not contain a reference to a coordinate system.
    Each World file has six rows. The table 299 shows an example for a World file.
    Row 1: Parameter A pixel size in x direction
    Row 2: Parameter D rotation about y axis
    Row 3: Parameter B rotation about x axis
    Row 4: Parameter E pixel size in y direction
    Row 5: X coordinate of the upper left pixel of the background
    Row 6: Y coordinate of the upper left pixel of the background
    32.0
    0.0
    0.0
    -32.0
    691200.0
    4576000.0

    Table 299: Example for a World file


    Note: Georeferencing and thus creating the World file can be executed with GIS software
    (for example ArcGIS by ESRI). Because the World file is a text file, it is theoretically possible to create it yourself in the text editor, if the necessary information is known.

    10.5.4

    Polygons
    The polygons of Visum are graphic objects available for free design of your drawings. Polygons can be edited in many ways:
    Drawing lines or areas
    Choice of color
    Position of lines and line types
    Patterns for areas

    10.6

    GPS tracking
    If a GPS receiver is connected to your PC, you can display the current position in the network
    graphic. With tracking switched on, the network graphic display is then updated in user-defined time intervals (see User Manual: Chpt. 22.10 , page 2261).
    The function requires a connection via a serial interface. Receivers with a Bluetooth or USB
    interface can also be used, if they emulate a serial interface. You can apply these functions to
    digitalize links for example.

    714

    PTVGROUP

    10.6 GPS tracking


    Each time the updating time interval has expired, the marking bitmap will be refreshed, however, only if a GPS signal has actually been received. A GPS signal accompanied by a warning
    (for example due to bad transmission or incorrect conversion of the coordinates) will be drawn
    in Marking1 color (see User Manual: Chpt. 24.2 , page 2337). The position acquired by the
    GPS receiver (length, width) will always be transferred into the current projection of the network (see "Coordinate systems" on page 705). If no projection has been set, the position is
    taken over directly. All that has to be noted is that the network coordinates correspond to the
    actual geographical position.

    PTVGROUP

    715

    11 Interactive analyses

    11

    Interactive analyses
    Visum offers various functionalities that allow you to evaluate your traffic model interactively.
    These can be used to analyze both PrT and PuT. The following interactive analyses are available.
    Flow bundles

    Filtering paths obtained through assignment according to different


    criteria (e.g. all paths traversing a specific link)

    Isochrones

    Analysis of the accessibility of network objects. Network objects


    which can be accessed from one or several network objects within
    the same time are highlighted in the same color (e.g. all locations
    that can reached from a specific node within 5 minutes on foot).

    Shortest path
    search

    Search for the shortest path between zones, nodes or main nodes,
    according to different criteria (e.g. distance)

    Subjects
    Flow bundles
    Isochrones
    Shortest path search

    11.1

    Flow bundles
    Flow bundles are used to filter and graphically display loaded paths (obtained through assignment) according to various criteria. Loaded paths are the result of assignment calculation
    and are characterized by the following properties:
    They consist of a route path from an origin zone to a destination zone.
    They have a transport system type (PrT, PuT or PuT-Sys).
    The show a volume (passengers, vehicles).
    Flow bundles consist of all paths traversing the network objects marked for flow bundle calculation. Marked network objects thus constitute the path filter criteria of a flow bundle. In the
    following section, you will learn about how to use the individual filter criteria. The illustration
    223 displays the principle of the flow bundle. The left figure shows all paths found in the assignment. The right figure shows the paths traversing the highlighted link.

    716

    PTVGROUP

    11.1 Flow bundles

    All PrT paths (displayed as volume bars)

    Filtering of all PrT paths traversing the highlighted link by defining a flow bundle

    Illustration 223: The flow bundle as path filter


    The flow bundle can be displayed graphically in the network editor (see User Manual: Chpt.
    23.1.2 , page 2275) or output as a list (see User Manual: Chpt. 24.1.6 , page 2315). Using PuT
    assignment as an example, illustration 224 displays the flow bundle paths in the PuT path legs
    list. In the graphical display, the path 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.

    Illustration 224: Display of the flow bundle paths in the PuT path leg list
    Note: To display a flow bundle, you first have to calculate an assignment and save its
    paths. You can save paths in the PrT (see User Manual: Chpt. 18.1.2 , page 1890) and in
    the PuT (see User Manual: Chpt. 19.1.1.2 , page 1996).
    The flow bundle type is defined via the network object type selected:

    PTVGROUP

    717

    11.1.1 Flow bundle definition through selection of network objects


    Flow bundles based on nodes, main nodes, stops, stop points or stop areas (highlighting
    nodes, main nodes, stop points, stop areas or stops)
    Link flow bundle (highlighting links)
    Zone and main zone flow bundle (highlighting zones or main zones)
    Traffic type-based flow bundle (by setting specific links or network objects of the line hierarchy, i.e. lines, line routes, etc., passive)
    The flow bundle can be created by highlighting one or more objects of a network object type. It
    can also be determined by any combination of highlighted network objects of different network
    object types (see "Combining flow bundle criteria" on page 725).
    Notes: If a flow bundle is active, its demand can be saved as a flow bundle matrix.
    The flow bundle considers the active settings of the OD pair filter. This allows you to perform flow bundle analyses that are additionally defined via the zone type (e.g. for internal
    zones only).

    11.1.1

    Flow bundle definition through selection of network objects


    Flow bundles can be defined through the selection of one or several network objects. Depending on the network object type, specific settings can be made.
    Node flow bundle (PrT and PuT)
    The node flow bundle lists all paths traversing the selected node(s).
    For PrT and PuT, select the demand segments for each node whose paths you want to use for
    flow bundle calculation. The assignment results and thus the paths of each demand segment
    are listed separately.
    For PuT, you additionally have the option of limiting the PuT supply (e.g. to certain lines) (see
    "PuT supply filter" on page 725).
    In the following example (illustration 225 ), the flow bundle contains all paths that traverse
    node 100,001, using line 002. There may be path legs shared with other lines before or after
    the leg via node 100,001 with line 002, see illustration 226.

    718

    PTVGROUP

    11.1.1 Flow bundle definition through selection of network objects

    Illustration 225: PuT node flow bundle with additional filter criteria for lines

    Illustration 226: Some of the paths which traverse node 100001 and use line 002
    Main node flow bundle (PrT only)
    The main node flow bundle works analogous to the node flow bundle. It outputs paths traversing the selected main node(s). You need to select the demand segments whose paths you
    want to use for flow bundle calculation.

    PTVGROUP

    719

    11.1.1 Flow bundle definition through selection of network objects


    Link flow bundle (PrT and PuT)
    The link flow bundle lists all paths traversing the marked links. In PuT, some links might only
    be traversed partially, due to link stop points. The determining factor for the flow bundle is the
    middle of the link: a link is considered traversed, if a path traverses the middle of the link.
    You have to select the demand segments, both in PrT and PuT, whose paths you want to use
    for flow bundle calculation.
    Just like for the nodes, for PuT you additionally have the option of limiting PuT supply (e.g. to
    certain lines) (see "PuT supply filter" on page 725).
    Flow bundles based on stop points, stop areas and stops (PuT only)
    The flow bundles for the three network objects of the stop hierarchy (stop point, stop area and
    stop) output all paths traversing each of the selected network objects. You can limit the passenger types for each network object selected:
    Origin boardings (B): A path is displayed in the flow bundle, if passengers board at the network object selected, i.e. if there is no other PuT partial leg before boarding.
    Destination alightings (A): A path is displayed in the flow bundle, if passengers alight at
    the network object selected, i.e. if there is no other PuT partial leg after alighting.
    Transfers (T): A path is displayed in the flow bundle, if passengers traverse at the network
    object selected. This can be at a boarding or an alighting point of transfer.
    Through passengers with stop (W): A path is displayed in the flow bundle, if there is a stop
    at the selected network object and passengers remain on board. The line stops at the network object without passengers alighting or transferring.
    Through passengers without stop (N): A path is displayed in the flow bundle, if passengers pass the selected network object without stopping. In this case the line does not
    stop.
    Just like for nodes and links, you additionally have the option of limiting PuT supply (e.g. to certain lines) (see "PuT supply filter" on page 725). For transfers, you can set separate filters for
    alighting and boarding passengers.
    Zone and main zone flow bundle (PrT and PuT)
    Flow bundles for the network object types zone and main zone list all paths starting or ending
    at the selected network object. Accordingly, you specify whether you want to filter by origin traffic or by destination traffic.
    Origin traffic: all paths starting in the selected zone or main zone
    Destination traffic: all paths ending in the selected zone or main zone
    Origin and destination traffic: all paths that start or end in the selected zone or main zone
    In addition, you have to select the demand segments, both in PrT and PuT, whose paths you
    want to use for flow bundle calculation.
    Just like for the nodes, for PuT you additionally have the option of limiting PuT supply (e.g. to
    certain lines) (see "PuT supply filter" on page 725). Limiting PuT supply applies to the first or
    last PuT path leg, depending on whether you have filtered by origin or destination traffic.

    720

    PTVGROUP

    11.1.2 Flow bundle definition through selection of traffic types

    11.1.2

    Flow bundle definition through selection of traffic types


    By setting links or network objects of the line hierarchy (lines, line routes, etc.) to active or passive, you can filter paths of the flow bundle by traffic type (internal traffic, origin traffic, destination traffic, through traffic, external traffic or bypassing internal traffic).
    In the following example, Lynnwood town center through traffic is illustrated by the traffic typebased flow bundle. Only those paths are displayed in the flow bundle that start and end in an
    external zone, but between the zones traverse the city center. In the illustration 227, the flow
    bundle is displayed for the through traffic and for the flow bundle path from external zone 136
    to external zone 27.

    Illustration 227: Display of through traffic with a flow bundle of active links
    Note: To calculate a traffic-type based flow bundle, you need to set at least one link or
    one network object of the line hierarchy to passive. To set an object to passive, use the filter (see User Manual: Chpt. 15.7 , page 1008) or spatial selection (see User Manual:
    Chpt. 15.8 , page 1033).
    In both cases (links or network objects belonging to the line hierarchy), Visum distinguishes
    between the traffic types internal traffic, origin traffic, destination traffic, through traffic, external

    PTVGROUP

    721

    11.1.2 Flow bundle definition through selection of traffic types


    traffic and bypassing internal traffic. These traffic types partition the number of all paths, i.e.
    each path has a unique traffic type.
    The following examples refer to a link traffic type flow bundle, for which inner city links have
    been set to active and outer city links to passive.
    Internal trips: Paths used by active network objects only. Example: The flow bundle shows
    the paths in the urban area.
    Origin demand: Paths starting with an active network object and ending with a passive network object. Example: The flow bundle shows all commuter flows from the urban area to
    its urban hinterland.
    Destination demand: Paths starting with a passive network object and ending with an
    active network object. Example: The flow bundle shows all commuter flows from the urban
    hinterland to the urban area.
    Through traffic: All paths that start and end with a passive object, but use at least one
    active object in-between. Example: The flow bundle shows HGV traffic traversing a conurbation.
    External trips: Paths that do not use active network objects. Example: The flow bundle
    shows traffic bypassing a conurbation.
    Bypassing internal trips: Paths that start and end with an active network object, but use at
    least one passive network object in-between. Example: The flow bundle shows traffic that
    starts and ends in an urban area, but that traverses the urban hinterland, e.g. on a bypassing road that has a higher speed limit.
    The table 300 shows which sequence of links (for a link traffic type flow bundle) or of PuT lines
    on path legs of a PuT path (for a PuT line traffic type flow bundle) belongs to which traffic type.
    For sequences with more than four objects, there are more variants.
    Number of links
    or PuT lines
    Internal trips

    a-a

    a-a-a

    a-a-a-a

    Origin demand

    a-p

    a-x-p

    a-x-x-p

    Destination demand

    p-a

    p-x-a

    p-x-x-a

    Through traffic

    p-a-p

    p-a-x-p or
    p-x-a-p

    External trips

    p-p

    p-p-p

    p-p-p-p

    Bypassing internal trips

    a-p-a

    a-p-x-a or
    a-x-p-a
    Table 300: Traffic type based on status (active / passive) of links or PuT lines
    The abbreviations in table 300 have the following meaning:
    a: link or PuT line active
    p: link or PuT line passive
    x: not relevant whether link or PuT line is active or passive

    722

    PTVGROUP

    11.1.2.1 Traffic type flow bundle for active links


    11.1.2.1

    Traffic type flow bundle for active links


    You can use traffic type flow bundles for active links for paths of PrT assignments or PuT assignments, as both path types can be described as a sequence of links.
    On PuT paths, links can be traversed with PuT lines, PuT-Aux TSys or PuT-Walk TSys. All
    three possibilities are accounted for in the link traffic type flow bundle. Transitions within a stop
    or between stop areas and the nodes assigned to them are ignored. So for the distinction between active and passive areas of a path (including PuT paths), only links are taken into
    account.
    The link traffic type flow bundle also allows you to limit PuT supply, e.g. to specific lines (see
    "PuT supply filter" on page 725). Only those links are considered active that have been set to
    active and that are used by an active PuT line.
    Example: Calculation of the number of passengers using long-distance transportation on a
    link corridor (completely or partly):
    The link corridor is active, all other links are passive.
    Selection of long-distance transportation TSys in PuT supply
    Selection of the traffic types internal traffic, origin traffic, destination traffic, through traffic and bypassing internal traffic
    If you want to combine several conditions of the type "Active links" within one flow bundle, you
    might have to reverse the active links for the flow bundle, i.e. set all passive links to active and
    vice versa. To do so, switch the reference quantity of the link traffic type flow bundle from
    "active links" to "passive links" and vice versa.
    Example: You want to determine the number of passengers using part of and the entire link
    corridor for long-distance transportation, but outside the corridor only use local public transport.
    The link corridor is active, all other links are passive.
    Add a flow bundle term with long distance transportation TSys as the PuT supply and
    the traffic types internal traffic, origin traffic, destination traffic, through traffic and
    bypass internal traffic.
    Add another flow bundle term with the operator AND and long-distance transportation
    TSys as the PuT supply. Choose the traffic type "external traffic". Select "passive links"
    as the reference quantity.
    By combining two terms that have different reference quantities you can a) filter paths using a
    specific PuT supply on active links and b) filter paths using a specific, but different PuT supply
    on passive links.

    11.1.2.2

    Traffic type flow bundle for active PuT lines


    The path filter for active PuT lines, line routes, etc. shows the lines or line routes used on a specific path. For the link traffic type flow bundle, these lines or line routes are links. This means a
    PuT path is considered a sequence of active and passive path legs, based on the active status
    of the lines, line routes, etc. used on the individual path legs.
    You can specify the line hierarchy level of the PuT supply used. The options are: line, line
    route, time profile, vehicle journey and vehicle journey section.

    PTVGROUP

    723

    11.1.2.2 Traffic type flow bundle for active PuT lines


    The first three network object types are always available. Vehicle journey and vehicle journey
    section, however, must be based on timetable-based assignment, for which paths are saved
    as connections.
    Vehicle journey sections are a special case. They do not carry volumes and there is no unique
    vehicle journey section for a path leg, even if a vehicle journey is specified. So when you
    select the vehicle journey section level, a PuT path leg is considered active, if it can be fully
    covered by active journey sections of its vehicle journey. Visum checks whether there is an
    active vehicle journey section for each vehicle journey item on the PuT path leg.
    The table 301 depicts the significance of the traffic types after applying a path filter for active
    PuT lines. The line filter has been set to active for long-distance trains ("ICE") and to passive
    for LRT lines ("RE").
    Internal trips
    Through traffic
    Origin demand
    Destination demand
    Bypassing internal trips
    External trips
    Legend

    Active PuT supply


    Passive PuT supply
    Table 301: Significance of traffic types after applying path filter for active PuT lines
    For instance, you can perform the following analyses on active PuT lines, using a path filter:
    1. Objective: Determine the number of passengers using a long-distance line on at least one
    path leg
    Only long-distance trains are active. Selection of the network object type lines.
    Selection of the traffic types internal traffic, origin traffic, destination traffic, through traffic and bypassing internal traffic
    2. Determine the number of passengers using at least one long-distance line on at least one
    path leg and at least one public transport line on one path leg
    Only long-distance lines are active. Selection of the network object type lines.
    Selection of the traffic types origin traffic, destination traffic, through traffic and bypassing internal traffic
    3. Objective: Determine number of passengers who only use vehicle journeys provided by a
    specific operator X.
    Only vehicle journeys of operator X are active. Selection of network object type vehicle
    journeys.
    Selection of the traffic type internal traffic

    724

    PTVGROUP

    11.1.3 PuT supply filter

    11.1.3

    PuT supply filter


    For PuT, you can define flow bundle conditions, using the criterion PuT supply. It allows you to
    filter paths by network objects that traverse them using a specific transport system, line, etc. A
    path is only included in a flow bundle, if it uses the selected PuT supply at the network object.
    You can choose between different types of PuT supply. The options are: transport systems,
    main lines, lines, line routes, time profiles, vehicle journeys and operators. Vehicle journeys
    and operators require a timetable-based assignment, for which paths are saved as connections.
    The results obtained with the supply filter depend on the network object type:
    nodes and links represent fairly simple examples. The supply filter criteria is met, if the
    node or link is traversed by the supply selected. Thereby it is irrelevant whether the paths
    traverses the node or link, or starts or ends there.
    For zones and main zones, the supply filter filters the first or last path leg - depending on
    whether you choose to filter by origin or destination traffic. The options Also PuT-Walk
    TSys and Also PuT-Aux TSys are taken into account when Visum checks the connector
    node of the path. Consequently, a path starting or ending with a PuT-Walk or PuT-Aux
    transport system belongs to the flow bundle, if the respective option has been activated or
    the first or last path leg is used for the PuT supply selected.
    For stop points, stop areas and stops, Visum distinguishes between two cases:
    When determining the number of passengers transferring, you can set supply filters
    with the criteria "alighting" and "boarding". This, for instance, allows you to filter all
    paths that at a stop switch from long-distance transport to local transport.
    Just as for the zones, the options PuT-walk and PuT-Aux play a special role. If you
    select "boarding" and the option Also walk TSys, you will also filter by all transfers that
    after alighting include a footpath - independent of the PuT supply the passengers alighted from. The same applies respectively for the option Also Aux TSys.
    For all other passenger types, the supply filter is used as described for nodes and
    links.
    When using the traffic type flow bundle conditions for active links, you can additionally filter the
    PuT supply. The PuT supply filter is applied directly to the active links. For a traffic type-based
    flow bundle, a link on a PuT path is considered active, if both the link itself and the PuT supply
    on it are active.

    11.1.4

    Combining flow bundle criteria


    For paths determined by a flow bundle, you can combine several criteria and connect them
    with AND THEN or OR. You can also combine PrT criteria and PuT criteria.
    The flow bundle in illustration 228 , e.g., includes a combination of AND THEN and OR operators. All paths starting in zone 102 and ending in zones 1, 2 or 5 are output in the flow
    bundle. For zone 102 the traffic type origin traffic was permitted, for zones 1, 2 and 5 only traffic
    type destination traffic. The required settings can be seen in the window, in illustration 228.

    PTVGROUP

    725

    11.1.4 Combining flow bundle criteria

    Illustration 228: Paths which start in zone 102 and end in zones 1, 2 or 5
    Definition of an AND THEN term
    A flow bundle describes all paths that the network objects selected traverse in a specified
    sequence. The illustration 229 shows a filter that includes many AND THEN link combinations.
    The flow bundle shows all paths that traverse these links in the sequence specified.

    726

    PTVGROUP

    11.1.4 Combining flow bundle criteria

    Illustration 229: All paths which traverse a link section in north direction
    Notes: Any number of nodes, main nodes, stops, stop areas, stop points and links can be
    linked in any order.
    Zones and main zones can only be the beginning or end of a path and can therefore not
    be traversed.
    Flow bundle conditions for network objects (see "Flow bundle definition through selection of
    network objects" on page 718) and flow bundle conditions for traffic types (see "Flow bundle
    definition through selection of traffic types" on page 721) can be combined through the AND
    operator. In this case, however, the sequence is not specified, as traffic type flow bundles
    always refer to the entire path. This is why there are used at the end of AND THEN operations.
    Note: You can use the AND operator to combine various traffic type flow bundle conditions or to combine traffic type flow bundle conditions with network object flow bundle
    conditions.
    The following example shows the flow bundle of illustration 227, for which two additional links
    were selected. The flow bundle filters the Lynwood through traffic, traversing the two links in
    the sequence specified.

    PTVGROUP

    727

    11.1.4 Combining flow bundle criteria

    Illustration 230: Through traffic traversing the two links in the sequence specified
    Using negated conditions (complement)
    Using a negated network object flow bundle condition, you can filter by paths that are not used
    by selected network objects.
    When combining the negated condition with positive network object flow bundle conditions,
    you have various filter options:
    1. Objective: all vehicles traversing link 1, but not link 100 afterwards.
    First AND THEN operation: link 1
    Second AND THEN operation: link 100, complement
    2. Objective: all vehicles traversing link 2, but not link 100 before.
    First AND THEN operation: link 100, complement
    Second AND THEN operation: link 2
    3. Objective: all vehicles traversing link 1, then link 2, but do not traverse link 100 in-between.
    First AND THEN operation: link 1
    Second AND THEN operation: link 100, complement
    Third AND THEN operation: link 2
    4. Objective: all vehicles traversing link 1, then link 2, but that do not traverse link 100 on their
    entire path.

    728

    PTVGROUP

    11.1.4 Combining flow bundle criteria


    First AND THEN operation: link 100, complement
    Second AND THEN operation: link 1
    Third AND THEN operation: link 100, complement
    Fourth AND THEN operation: link 2
    Fifth AND THEN operation: link 100, complement
    The examples show that the negated network object flow bundle conditions are always evaluated for an area between positive network object flow bundle conditions. If the sequence is
    not important, you might have to add the negated conditions a few times (see example 4).
    The sequence is not important for traffic type-based flow bundle conditions. This means that
    when you use a complement, it produces a simple logic negation - which corresponds to the
    selection of a complementary traffic type set.
    Defining an OR operation
    Adding an OR operation ends a series of AND THEN operations. Then you can add additional
    conditions. A flow bundle describes all paths that fulfill at least one of the filter criteria linked to
    an OR operation.
    Any number of AND THEN operations can be linked by OR operations. Each path is only output once with the flow bundle, even if it is found for several AND THEN operations.
    The illustration 231 shows how you can simultaneously show a PrT flow bundle and a PuT
    flow bundle, using an OR operation. The PrT flow bundle shows all PrT paths traversing nodes
    106,062,539 and 106,062,191. The PuT flow bundle shows all PuT paths traversing stops
    106,061,623 and 106,063,464.

    PTVGROUP

    729

    11.1.5 Flow bundles with alternative routes

    Illustration 231: Combining flow bundles for PrT and PuT by using an OR operation

    11.1.5

    Flow bundles with alternative routes


    To display all paths in the flow bundles that do not traverse the selected network objects, show
    the alternative routes. Then only those OD relations are taken into account that use the selected network objects. If 60% of the paths of an OD pair traverse the link s selected for the flow
    bundle, then the alternative routes make up the remaining 40% of the paths of this relation.
    These are the OD pair paths that do not traverse the selected link s. In the example in illustration 232 , two links of a bypass (in both line directions) are highlighted for the flow bundle.
    The links of each direction are combined through an AND THEN operation. The two AND
    THEN operations for the two line directions are combined via an OR operation. So, independent of the direction, all paths are shown that traverse this link section.

    730

    PTVGROUP

    11.1.5 Flow bundles with alternative routes

    Illustration 232: Link flow bundle with AND THEN operation and OR operation
    In illustration 233, a flow bundle of alternative routes is displayed for the same flow bundle criteria as in illustration 232 . For all OD pairs for which paths were found in the origin flow
    bundle, the paths are listed that do not traverse the link section selected. The comparison of
    the two illustrations shows, that most traffic uses the by-pass on these OD pairs. Only a few
    road users choose the routes which lead through the city. In a planning project the effectiveness of a created measurement could thus be allocated.

    PTVGROUP

    731

    11.2 Isochrones

    Illustration 233: Link flow bundle with alternative routes

    11.2

    Isochrones
    Based on one or several selected network objects, isochrones visualize the accessibility of all
    other network objects.
    The accessibility can be classified in intervals that are highlighted in different colors in the Network editor. You can, for instance, highlight all towns in the same color that can be accessed
    from a specific node within a certain time.
    In practice, isochrones are used to analyze the catchment area of stops. In illustration 234, all
    stop areas in the urban area were highlighted and then an isochrone calculation was performed. You can see, that especially potential PuT passengers from the eastern part of the city
    (highlighted in dark red) need more than 8min to the next stop.

    732

    PTVGROUP

    11.2 Isochrones

    Illustration 234: Isochrones to display the accessibility of stop areas


    The illustration 235 illustrates the effectiveness of isochrones in a simple example. In this
    example, isochrones were drawn based on node 20. The travel time in the loaded network
    (tCur) was used as the path-choice criterion. The links were labeled with these times. The link
    segments were highlighted in different colors depending on their accessibility (here depending on tCur ) (see User Manual: Chpt. 24.3.7 , page 2352). If you e.g. travel from node 20 via
    node 11 to node 41, the in-vehicle time is 29min 35s. Accordingly, the last link section before
    node 41 is highlighted in dark red, as from here your journey is longer than 26min.

    PTVGROUP

    733

    11.2.1 PrT isochrones

    Illustration 235: Functional principle of isochrones illustrated in a simple example


    If several network objects are selected for isochrone display, the shortest path from the selected network objects to the link section is calculated for each link section. The shortest of these
    shortest paths then determines which accessibility interval is assigned to the link section. If
    e.g. nodes 21 and 31 are selected for the isochrone display and a link section can be reached
    from node 21 in 22min and from node 31 in 28min, the link section is assigned to the accessibility interval <= 22min and is highlighted accordingly.
    Note: The accessibility of network objects can be calculated and displayed simultaneously for both PuT and PrT.

    11.2.1

    PrT isochrones
    The accessibility of network objects is determined via a shortest path search. Thereby the following attributes are used as search criteria:
    tCur (travel time in loaded network)
    t0 (travel time in unloaded network)
    Distance
    Impedance
    AddValues 1 to 3
    Note: When selecting the route choice criterion, note that t0, tCur and Impedance correspond to each other as long as no assignment has been calculated.
    You can use nodes, main nodes and zones (or a combination of them) as reference points of
    PrT isochrones.

    734

    PTVGROUP

    11.2.1 PrT isochrones


    The results of PrT isochrone calculation are listed under the attribute Isochrones time PrT of
    nodes, main nodes and zones. The minimum run time is listed for each network object.
    The following options are available for displaying PrT isochrones graphically in the Network
    editor:
    Display of the accessibility of link sections
    2D drawing
    Classified display of nodes, main nodes and zones by Isochrones Time PrT
    Accessibility of link sections
    This display option shows individual link sections in the color of the accessibility interval they
    belong to. The illustration 236 shows the accessibility of link sections from marked node 7357.
    Dark red colored link sections can only be reached in more than 10min.

    Illustration 236: Accessibility of link sections from node 7357


    Classified display of network objects
    Like all other attributes, the result of PrT isochrones can be used as a basis for classified display of nodes and zones.

    PTVGROUP

    735

    11.2.2 PuT isochrones


    This means that nodes and zones are highlighted in color, depending on their Isochrones
    Time PrT. In illustration 237, zones were classified according to the Isochrones Time PrT.

    Illustration 237: Classification of zones according to Isochrones time PrT

    11.2.2

    PuT isochrones
    PuT isochrones are used to analyze the accessibility of nodes, stops, stop areas, stop points
    and zones within a specified time interval. Accessibility is determined based on a timetablebased connection search. The search can be based on a departure or an arrival time interval.
    In the first case, you determine all connections leaving from the network object selected within
    a certain time period, including an additional time span. This time span is entered after you
    have selected the departure period and refers to the time within which the connection must
    reach the destination.
    In the second case, you analyze all connections that arrive at the network object selected
    within a certain time period and you enter a lead time. This is the time span directly before the
    arrival period specified and during which the connections must leave their starting point.
    You can use nodes, stop areas and zones (or a combination of them) as reference points of
    PuT isochrones.
    You can find the results of PuT isochrone calculation in the attributes Isochrones time PuT
    and Number of transfers PuT for nodes, stops, stop areas, stop points and zones. For each
    network object, the minimum journey time and minimum number of required transfers is listed.
    Please note that both values might appear in different connections, i.e. there is not necessarily
    one connection with both the minimum journey time and the minimum number of transfers.

    736

    PTVGROUP

    11.2.2 PuT isochrones


    The results depend on the time intervals specified. You can influence the calculation (except
    for the time reference), by limiting the search to active vehicle journey sections or by specifying
    a maximum number of transfers.
    The following options are available for displaying PuT isochrones graphically in the Network
    editor:
    2D drawing
    The attributes Isochrones time PuT and Isochrones number of transfers PuT can be
    used in 2D to classify the accessibility intervals.
    Classified representation of nodes, zones, stops, stop areas and stop points
    The attributes Isochrones time PuT and Isochrones number of transfers PuT can be
    used for a classified representation of one or several network object types.
    Isochrone display in 2D
    For 2D display, the network background is highlighted in color depending on the individual
    accessibility intervals.
    In illustration 238, this type of representation is used to visualize the attribute Isochrones time
    PuT, i.e. the time required to access stop areas. The main train station is highlighted, i.e. the
    isochrones show the PuT journey time starting from the main train station.

    PTVGROUP

    737

    11.2.2 PuT isochrones

    Illustration 238: 2D display of the accessibility of stop areas from the main station
    Classified display of network objects
    Just like all other attributes, the results of PuT isochrones can be used for a classified representation of nodes, zones, stops, stop areas or stop points:
    Isochrones time PuT
    The illustration 239 shows an example, where the stops are displayed as classified. The
    stop Karlsruhe main station is marked as start. The stops are illustrated as circles and
    their coloring depends on the time in which each stop can be reached from the main station.

    738

    PTVGROUP

    11.2.2 PuT isochrones

    Illustration 239: Classified display of stops on the basis of the isochrone time PuT
    Isochrones Number of transfers PuT
    In illustration 240 the Isochrones number of transfers PuT was selected as a classification
    criterion. It is then clearly shown which stops can be reached from the main train station
    with no transfer, one transfer or more than one transfer.

    PTVGROUP

    739

    11.2.3 Combination of PrT and PuT isochrones

    Illustration 240: Classified display of stops on the basis of the isochrone number of transfers

    11.2.3

    Combination of PrT and PuT isochrones


    Visum allows you to simultaneously display isochrones for PrT and PuT in a single network.
    This is how you can compare the accessibility in PrT and PuT. In our example in illustration
    241, the stops are classified and displayed according to the Isochrones Time PuT. Stop area
    106,062,191 was selected for isochrone calculation. For PrT, the link sections are classified
    based on isochrone time PrT. Node 106,062,191 was highlighted as a reference point for the
    PrT isochrone and is located at the corresponding stop area.
    If you now compare accessibility starting from the highlighted node or stop area to the bus station (stop area 106062529), you can see whether it is quicker to use a car or the bus. Based
    on this comparison, you can derive measures, e.g. to increase the attractiveness of PuT.
    illustration 241 graphically shows that the bus station can be reached via PuT (106,062,529)
    in <= 6min from starting point (106,062,191). A comparison with PrT (colored link sections)
    shows that the same start-destination relation can be covered in less than 3 minutes.

    740

    PTVGROUP

    11.3 Shortest path search

    Illustration 241: Comparison of accessibility in PrT and PuT in a graphical view


    The exact figures are provided in the list view (see illustration 242). The exact Isochrones
    Time PrT is 2min 50s, the Isochrones Time PuT is 5min 25s.

    Illustration 242: Comparison of accessibility in PrT and PuT in a list view

    11.3

    Shortest path search


    With the shortest path search command you can determine the best paths from a chosen origin to a chosen destination and display the result in the network (see illustration 243). Different
    search criteria can be used to find the shortest path. The paths found can then be displayed in
    a shortest path search list.

    PTVGROUP

    741

    11.3 Shortest path search

    Illustration 243: Shortest path search between two nodes in PrT


    An interactive shortest path search can be used especially to find errors in network modeling.
    With the graphic output of the shortest path, you can quickly determine implausible shortest
    paths in the network editor. It could thus occur, that links for a transport system were mistakenly blocked by the modeler and therefore an unexpected path between two nodes is assumed as the shortest path. With the shortest path search you can find such paths and undo the
    road closure if necessary.
    Shortest path search PrT
    In PrT, shortest paths can be searched for between nodes, main nodes or zones. The shortest
    path is searched for the selected traffic system respectively. The following choice criteria are
    possible as search criteria.
    t0 (travel time in unloaded network)
    tCur (travel time in loaded network)
    Impedance
    Distance
    AddValues 1 to 3 (this also allows the use of values of any other attributes as a criteria for
    the shortest path search)

    742

    PTVGROUP

    11.3 Shortest path search


    Shortest path search PuT
    Shortest path search for PuT can either be timetable-based (PuT tab) or transport systembased (PuT TSys tab).
    If a timetable-based search is performed, the connection with a minimum search impedance
    is output as the shortest path. Thereby search impedance is any linear combination of journey
    time and the number of transfers.
    Search impedance = x journey time + y number of transfers
    You can also specify whether you consider a shorter journey time or less transfers more favorable for the shortest path search. You can search for a timetable-based shortest path between
    two zones or two stop areas.
    The transport system-based shortest path search does not differentiate between individual
    PuT lines. Modeling the transport supply only considers the links of a basic network with their
    specific run times. A basic network may include the following three options:
    All road and rail links of the link network
    Only those links traversed by PuT lines
    Only those links traversed by active PuT lines
    A graph is created from the links of this basic network. If forms the basis for a shortest path
    search. Because individual lines are not distinguished, transfer stops with their respective
    transfer times cannot be included in the search. However, it is possible to include transfer
    times between different transport systems (transfer penalties for transport system transfers,
    such as between bus and train). The transport system-based shortest path search can be performed for an area between two zones or two nodes.

    PTVGROUP

    743

    12 Tabular and graphical display

    12

    Tabular and graphical display


    Visum provides a wide range of graphical and tabular display options for the data of your traffic model. You can analyze the model data from different views. You can e.g. show the link
    volumes calculated in an assignment procedure in table or a list, or graphically as link bars in
    the Network editor, as depicted in illustration 244. Below, display types which are often used
    are introduced in examples. Primarily, these are there to give an idea on the diversity of the
    graphic display possibilities in Visum. You can find all setting possibilities for graphic parameters and lists in the detailed description (see User Manual: Chpt. 24 , page 2299).

    Illustration 244: Graphical and tabular display of link volumes


    Subjects
    Lists
    Bars
    Categorized display with attribute values
    Labeling with tables
    Labeling with charts
    Turn volumes
    Desire lines
    Stop catchment areas
    PuT transfer relations
    744

    PTVGROUP

    12.1 Lists
    PuT connections and transfer flows
    Lane allocation
    2D display
    Schematic line diagram
    Signal time-space diagram
    Column charts
    Evaluations in the timetable editor

    12.1

    Lists
    Use lists for the following applications:
    To get an overview of the network object data of your model and network analyses results
    in table form
    To save attribute files for the exchange with other Visum models
    To export any attribute of the list in a database or in a spreadsheet
    To simultaneously change the attribute values of multiple network objects, as efficiently as
    in spreadsheets
    To display the set of network objects, which correspond to the set filter criteria
    To perform attribute-classified analyses on the properties of network objects
    The list columns contain freely selectable attributes, the rows contain different objects. There
    are two types of lists, specific lists for each network object type and evaluation lists.

    12.1.1

    List display and entry options


    Lists are mainly used to display the properties of network objects and other network data in a
    table. You can specify the number of attributes displayed, the sequence of the columns and
    the display format (e.g. decimal places, alignment) for each column. The choice of attributes
    together with the column format are called the list layout (see User Manual: Chpt. 24.1 , page
    2299). You can save the list layout to files to use it again later. This allows you to open views
    of certain network aspects or to prepare for specific tasks.
    Using lists, you can access both the direct and indirect attributes of network objects. Indirect
    attributes are attributes of other network objects, e.g. in a zones list, you can view the number
    of origin connectors (see User Manual: Chpt. 15.2 , page 958). You can sort nearly all lists
    (exception: path lists) by any column.
    The network object data is not only readable, you can also change it directly in the list view. To
    do so, simply enter a new value. You can change any editable attributes. To have more options, activate the Extended input options (see User Manual: Chpt. 24.1.3 , page 2306) for attributes whose specification is limited. You can then change attributes, such as TSysSet, in a
    separate window. For attributes including an enumeration type, a list box of options is displayed in clear text format.
    The list allows you to make changes efficiently to several objects and/or attributes at the same
    time. To do so, simply highlight the cells you want to change and enter a new value. The new
    value is then adopted for all highlighted cells. When making your changes, you cannot only
    enter constant values (e.g. "2"), but also simple calculation procedures. If, for instance, you
    want to double the length of all links, in the "Links" list, highlight all the cells of the "Length"

    PTVGROUP

    745

    12.1.1 List display and entry options


    column. Enter "=*2" and Visum multiplies each cell value by 2. This option is also available via
    the context menu (Arithmetic operations on marked section). When using lists, you can also
    use the Windows Clipboard for data exchange, i.e. the Copy and Paste commands for data
    exchange with a Microsoft Excel file. To exchange larger amounts of data, you can export the
    list content into databases or ASCII-based Visum attribute files (*.att).
    Thereby each row in the list represents a network object. Commands for network objects are
    also available in the list context menu. To change attributes, you can also open the Change
    network object dialog box. The dialog also allows you to delete objects and provides special
    functions as the display of column diagrams. If you highlight the cells of several rows, all changes made using the context menu or the Network editor, will apply to all highlighted objects.
    Another option is to open the Multi-edit dialog for the respective network object, which e.g.
    allows you to assign attribute values via formulas. Moreover, it provides all the special Multiedit functions.
    You can synchronize lists of network objects with the Network editor, if they have an own
    mode in the Network editor (see User Manual: Chpt. 24.1.9 , page 2320). Highlighting objects
    in the list then also highlights the same objects in the Network editor window. You can specify
    to keep the current view, to show the highlighted network object or to auto zoom into the highlighted area. Highlighting objects in the network will also highlight the same objects in the list.
    Synchronization further allows you to easily perform analyses, e.g. to search for the ten links
    with the highest volume, simply show the respective volume attribute in the link list. Then sort
    the list by this attribute in descending order and highlight the first ten rows. If you have activated synchronization, you can then see the respective objects in the Network editor window.
    The synchronization option is also available for some other lists. However, in this case, synchronization only works in one direction. Highlighting objects in the list will highlight the same
    objects in the network, but this does not work vice versa, as other object types cannot be highlighted in the network. Examples would be item lists (e.g. line routes), paths (PrT paths, PuT
    paths) and line blocks. In these lists, you can highlight a row and the geographical course of
    the respective object is then also highlighted in the network.
    You can aggregate the display of network objects in lists. To do so, select an attribute by which
    you want to group the objects. Network objects with the same attribute value are then grouped
    in a row. Then an aggregation function is applied to the attribute values of the grouped network objects and its value is displayed. Typical aggregation functions are sums, minimum,
    maximum, average and weighted mean. You can also use comparison, concatenate, frequency of occurrence, and distinct occurrence. The frequency of occurrence indicates how
    often a value occurs in the data of an aggregated row. The aggregate function distinct occurrence only lists all occurring values. You can also group network objects by several attributes
    at the same time. An example would be an analysis of transferring passengers by transport
    systems: In the passenger transfer list, you could show the transport system code of the fromtime profile item and the to-time profile item as indirect attributes. Then you could group the
    data by these two columns. As aggregation function for the volume attributes, you would
    choose sum. The result is displayed in a from-transport system row and a to-transport system
    row. If have not limited your selection to a stop, you can also group the objects by stop numbers to receive a network-wide overview of the passengers transferring between transport systems. To copy such a view to a spreadsheet program, highlight all cells. In the same way, you

    746

    PTVGROUP

    12.1.2 Specific network object lists


    can perform similar analyses and validity checks or e.g. use the links list to calculate the average volume of specific links.

    12.1.2

    Specific network object lists


    Specific lists are provided for all network object types (see "Example of a link list" on page
    747). Here you can edit the input attributes of the network objects and display additional noneditable attributes, such as assignment results for example (see "Example of a link list" on
    page 747). Some of these lists have special features that are explained below.

    Illustration 245: Example of a link list


    Territory lists
    Both territory lists contain PrT and PuT indicators precisely broken down. This is how the indicators can be calculated based on spatial territories, for example the service kilometers which
    lie within a county (see "Spatial cut (Territory cut)" on page 675). The sublists Basis and PuT
    detail are available for territories.
    Basis

    The list outputs precise indicators of PrT and PuT for each territory. Dependent
    on the indicator, an assignment or the procedure territory indicators or PuT operating indicators have to be calculated before.
    Hint
    To get more detailed information on how to calculate the values for this list, have
    a look at the files IndicatorOrigin.xls and IndicatorAvailability.xls in your Doc
    directory of your Visum installation.

    PuT
    detail

    For PuT, the indicators for each territory can be refined on the following levels of
    the line hierarchy, and if desired also per vehicle combination (see "Spatial cut
    (Territory cut)" on page 675).
    Territory x Transport system
    Territory x Main line
    Territory x Line
    Territory x Line route
    Territory x Time profile
    Territory x Vehicle journey

    PTVGROUP

    747

    12.1.2 Specific network object lists


    Territory x TSys x Vehicle combination
    Territory x Main line x Vehicle combination
    Territory x Line x Vehicle combination
    Territory x Line route x Vehicle combination
    Territory x Time profile x Vehicle combination
    Territory x Vehicle journey x Vehicle combination
    This is how you can evaluate service kilometers per line within a territory for
    example.
    Note
    The list only contains entries after the procedure PuT operating indicators has
    been calculated.
    Table 302: Territory lists
    OD pair lists
    In an OD pair list you can output the following attributes for each relation between two zones:
    Values from the skim matrices of the model
    Values from the demand matrices of the model
    Direct distance between zones
    Values from the direct and indirect attributes of the From zone or To zone of the relation
    Note: The matrix values can also be edited in this list, so that you do not have to switch to
    the matrix editor.
    Stop lists
    Visum provides lists for the network object stop, stop area and stop point. In addition to the
    base list for the network objects themselves, you can also find a list for the timetables at stop
    points and the transfer times between the stop areas of the stops, the transport systems, and
    the time profiles.

    748

    Stop points arrivals/departures

    The list exports the vehicle journeys and attributes of any stop point
    selected by the user such as, Arrival and Departure. As an option,
    you can also filter according to time profiles at the selected stop point.

    Transfers and
    stop area walk
    times in stop

    For each stop, the list contains the transfer walk times and the passenger transfers per transport system between the stop areas of the
    stop. Use the list for example, if you want to change the transfer times
    of multiple stops. You therefore do not have to open the window Edit
    stop for each individual stop, to change the times.

    Time profiles:
    Transition walk
    times

    For each stop, the list contains the transfer times between the time profiles of the stop.

    Transport systems: Transition


    walk times

    For each stop, the list contains the transfer times between the transport
    systems of the stop.

    PTVGROUP

    12.1.2 Specific network object lists


    Table 303: Stop lists
    Item lists
    In addition to basis lists (for example line route list) for the network objects of the line hierarchy
    and for system routes, item lists are also offered (for example the line route items list). These
    lists contain the individual elements (items) of the network object. These are:
    Line route items

    All nodes and stop points of the line route

    Time profile items

    All profile points of a time profile (see User Manual: Chpt. 15.31.3.3
    , page 1313)

    Vehicle journey
    items

    All profile points of the time profile which are traversed by the
    vehicle journey selected by the user

    System route items


    Table 304: Item lists

    All nodes and stop points which lie on the system route

    In items lists, you can switch between the section view and the classical view. The classical
    view displays the sequence of fixed points like stop points, route points or profile points, while
    the section view focuses on the items between these points (see User Manual: Chpt. 24.1.6.2 ,
    page 2315).
    Line lists
    In addition to the base list for network objects of the line hierarchy and the respective course
    lists, Visum offers two special lists for coupling.
    Coupling sections

    All coupling sections with their From stop point No and To stop
    point No. This is how you can illustrate which stop points are coupled between which time profiles.

    Coupling section
    The list shows which time profile is coupled between which time proitems
    file elements.
    Table 305: Line lists
    Line block lists
    To display and edit input and output attributes of line blocking, the lists line block versions, line
    blocks and line block items are available.
    Line block versions

    Shows the line block versions contained in the model.

    Blocks

    The list shows the line blocks of all line block versions. As an option,
    only the line blocks of a line block version selected by the user can be
    displayed.

    Block items

    The individual elements of all line blocks are contained in this list. The
    list shows the parts which make up a line block and in which order
    these are traversed (vehicle journeys, empty trips, stand times, but also

    PTVGROUP

    749

    12.1.3 Matrix list


    user-defined line block item types). As an option, only the items of a line
    block version selected by the user can be displayed.
    Table 306: Line block lists

    12.1.3

    Matrix list
    The matrix list shows an overview of all matrices.

    12.1.4

    Evaluation lists
    Evaluation lists only contain results from calculations or statistical values on the network
    model. Their entries can therefore not be edited. An example is the PrT path list:

    Illustration 246: PrT path list


    Evaluation lists for paths
    The paths found between origin and destination zone in the assignment, are output in the path
    lists (see User Manual: Chpt. 24.1.10 , page 2321).
    Note: The lists are empty if no assignment was calculated.

    750

    PrT paths

    Lists the paths calculated in a PrT assignment for the selected


    demand segment. The rows contain the paths from an origin zone
    to a destination zone.

    PrT path sets

    Displays any existing PrT path sets.

    PrT paths on link level

    Compared to the PrT path list, the links which lie on the path are
    listed additionally for each path. This is how the exact course of
    the path can be comprehended.

    PuT OD pairs

    Lists aggregated skims for each OD pair, which were calculated

    PTVGROUP

    12.1.4 Evaluation lists


    for the routes or connections found with the assignment.
    Note
    You must calculate the skims beforehand for PuT with the assignment or in a separate procedure (see "PuT skims" on page
    456), for PrT via the procedure Calculate skim matrix (see "PrT
    skims" on page 311).
    PuT paths

    Lists the paths calculated in a PuT assignment for the selected


    demand segment. The rows contain the paths from an origin zone
    to a destination zone.

    PuT path legs

    Lists all path legs (see "Network model" on page 40) of each
    route or connection of an OD pair from an origin zone to a destination zone for the selected demand segment, found by the PuT
    assignment.

    Table 307: Evaluation lists for paths


    Evaluation lists for transfers
    There are three different transfer lists. These lists allow a display of the transfers per stop or
    per time profile/transport system and the transfers and stop area walk times within a stop (see
    User Manual: Chpt. 24.1 , page 2299).
    Note: The lists do not contain any entries if no PuT assignment was calculated beforehand.
    Evaluation lists for paths from the shortest path search
    The shortest path list outputs the attributes of a previously calculated shortest path search for
    PrT or PuT.
    Note: A previously calculated assignment is not required.

    PTVGROUP

    751

    12.1.4 Evaluation lists


    Statistical evaluation lists
    Statistics - Network
    information

    The list provides statistical information on the current network.


    Number in network
    Number of objects per network type
    License
    Maximum number of objects for the current Visum license
    Max
    Maximum number of objects for the largest Visum license
    Furthermore, the list also provides detailed information (with subattribute) on the specific number of network objects. These are for
    example
    Number of origin connectors or destination connectors of PrT
    or PuT
    Number of one-way roads or turning prohibitions for each
    transport system
    Note
    The list further allows you to access attributes of the Network
    object, e.g. user-defined attributes.

    Statistics Goodness
    of PrT assignment

    Output of convergence criteria as indicators of the PrT assignment quality (see "Convergence criteria of assignment quality"
    on page 329).
    Notes
    The convergence criteria are automatically calculated for the PrT
    assignment procedures Equilibrium, Equilibrium_Lohse and Stochastic assignment.
    The list further allows you to access attributes of the Network
    object, e.g. user-defined attributes.

    Statistics - Goodness
    Output of convergence criteria as indicators of the PrT assiof PrT assignment with gnment quality for assignments with ICA
    ICA
    Note
    The list further allows you to access attributes of the Network
    object, e.g. user-defined attributes.
    Statistics - Assignment Output of the statistical evaluation of the assignment analysis for
    analysis
    PrT or PuT (see "Assignment analysis PrT" on page 446 and
    "Assignment analysis PuT" on page 528)

    752

    PTVGROUP

    12.2 Bars
    Statistics PuT assignment statistics

    Output of indicators for PuT assignments which refer to the entire


    network
    Note
    The indicators are calculated automatically with a PuT assignment (see "Transport system-based assignment" on page 471).

    Emissions HBEFA

    Output of the skims calculated network-wide by the emission calculation according to HBEFA (see "Emission calculation according to HBEFA 3.1" on page 685)
    Note
    The list further allows you to access attributes of the Network
    object, e.g. user-defined attributes.

    Table 308: Statistical evaluation lists

    12.2

    Bars
    You can draw links and connectors, whose width complies with the values of an indirect or
    direct attribute of the link or the connector (see User Manual: Chpt. 24.5 , page 2367). The link
    volume from a PrT assignment can thus for example be visualized, like in illustration 247, by
    scaling the link bar with the attribute Volume [Veh] PrT.

    Illustration 247: Link bars with PrT volume


    Connector bars can also be drawn. In illustration 248 the attribute Volume [Veh] PrT is displayed on the connectors.

    PTVGROUP

    753

    12.2 Bars

    Illustration 248: Connector bars with PrT volume


    You can draw as many bars as you like with different attributes along the link or connector.
    This is how you can simultaneously display the volume from a PrT assignment (attribute
    Volume [Veh] PrT) and the volume from a PuT assignment (attribute Volume [Pass] PuT) on
    a link, as can be seen in illustration 249.

    Illustration 249: Two link bars with PrT and PuT volume

    754

    PTVGROUP

    12.3 Categorized display with attribute values

    12.3

    Categorized display with attribute values


    The display of the active network objects in the network editor can be categorized with attribute values of the network object (see User Manual: Chpt. 24.12 , page 2411). This makes it
    possible to draw links differently in dependency of their link type, for example. In illustration
    250, illustration 251 and illustration 252 link and zone categorizations are illustrated.

    Illustration 250: Categorized link display according to link category

    Illustration 251: Categorized link display according to saturation PrT

    PTVGROUP

    755

    12.3 Categorized display with attribute values

    Illustration 252: Zone categorization according to origin traffic


    Bars (see "Bars" on page 753) can also be displayed in categories. In dependency of attribute
    Saturation PrT, the link bar is colored red, green or yellow in illustration 253.

    Illustration 253: Link bar display categorized according to saturation PrT

    756

    PTVGROUP

    12.4 Labeling with tables

    12.4

    Labeling with tables


    In the network editor, the network objects can be labeled with freely configurable tables. You
    can output up to 5 rows and 2 columns of attribute names and the respective values, but also
    free text, in the table (see User Manual: Chpt. 24.2 , page 2337). This is how you can label the
    stop points in your model with tables for example, which show the number of boarding passengers, transfers and alighting passengers (illustration 254).

    Illustration 254: Table display of boarding passengers, transfers and alighting passengers at
    stops

    12.5

    Labeling with charts


    In the network editor, the network objects can be labeled with freely configurable charts (see
    User Manual: Chpt. 24.11.2 , page 2405). Bar and pie charts are available. For zones you can
    display the number of inhabitants and jobs in a column chart for example (illustration 255).

    PTVGROUP

    757

    12.5 Labeling with charts

    Illustration 255: Number of residents and workplaces per zone


    You can also display the results of the mode choice (see "Mode choice" on page 139) the
    distribution of travel demand to the individual transport modes for each zone in a pie chart
    (illustration 256).

    758

    PTVGROUP

    12.6 Turn volumes

    Illustration 256: Display of the mode selection as pie charts for zones

    12.6

    Turn volumes
    Turn volumes visualize attributes of turns (see "Network model" on page 40) at individual
    nodes (see User Manual: Chpt. 24.14 , page 2435). If you select the attribute Volume [Veh]
    PrT (AP) for example, after an assignment you can illustrate which traffic volumes apply to the
    turns of a node (illustration 257).
    The turn attributes can also be displayed in a turn list (see "Lists" on page 745).
    Tip: In the junction editor, you can also display turn volumes (see User Manual: Chpt.
    15.40.18 , page 1501).

    PTVGROUP

    759

    12.7 Desire lines

    Illustration 257: Display of turn volumes

    12.7

    Desire lines
    A desire line visualizes the values for relations between zones (From zone to To zone). The
    values displayed on the desire line may derive from different origins.
    From a demand matrix (for example to visualize the demand between zones)
    From a skim matrix (for example to visualize the journey time between zones)
    As a value from the network model itself (for example the direct distance between zones)
    From a zone attribute of the From zone or the To zone of the relation (for example to illustrate the From zone\origin traffic to other zones)
    For each OD pair you can draw both a desire line link as well as one or more desire line bars
    for a proportional display of the values (see User Manual: Chpt. 24.13 , page 2429).
    The display of desire lines is useful for illustrating demand matrices and indicator matrices in
    the network editor. This is how you can get an overview, which OD pairs (From zone to To
    zone) are especially in demand, for example. The example shown in illustration 258 shows
    the travel demand between the zone Oppidum and all other zones. It is clear, that there is an
    especially high demand between the zones Oppidum and B town.

    760

    PTVGROUP

    12.7 Desire lines

    Illustration 258: Desire line with bars scaled at the demand between zones
    The desire line is drawn on the linear distance between the zones. If you are interested in the
    exact course of the paths between origin and destination zones, use the Shortest Path
    Search (see User Manual: Chpt. 23.3 , page 2291).
    Combined with the OD pair filter (see User Manual: Chpt. 15.7.6 , page 1026) the display of
    the desire lines on OD pairs, which correspond to the filter criteria, can be confined. As an alternative, the number of the OD pairs displayed can also be displayed via a classified display
    (see User Manual: Chpt. 24.2 , page 2337).
    Furthermore, the desire line can also be drawn classified. As shown in illustration 259, you
    can highlight OD pairs with a high traffic demand with colors, for example.

    PTVGROUP

    761

    12.8 Stop catchment areas

    Illustration 259: Desire line with bars classified according to the demand between zones

    12.8

    Stop catchment areas


    Using stop catchment areas, you can draw circles around the stops, to graphically display the
    PuT development quality in the network. The circle can either be drawn with a constant radius
    or in proportion to the values of direct or indirect stop attributes. Circles were drawn with a constant radius of 400m in the example in illustration 260. As you can see, the Eastern part of the
    small town is insufficiently accessible by PuT, so that the extension measures should aim
    towards making this territory more accessible.

    762

    PTVGROUP

    12.8 Stop catchment areas

    Illustration 260: Stop catchment areas with a large radius of 400m


    Stop catchment areas can also be drawn classified. In illustration 261 catchment areas with a
    radius of 300m are drawn around the stops. The circles of stops with more than 1,000 departures per analysis period are red, stops with less than 500 departures are orange, and stops
    with less than 100 departures are displayed in green. This is how you can display how strongly stops are frequented and how the entire network is made accessible by PuT, in a graphic.

    PTVGROUP

    763

    12.9 PuT transfer relations

    Illustration 261: Stop catchment areas classified according to the number of departures

    12.9

    PuT transfer relations


    The graphics layer Transfer relations allows a display of transfer relations between (active)
    stop areas of the (active) stops as volume bars in the network. This view is required in PuT networks in which the stop hierarchy is used for a realistic modeling of transfers. For each pair of
    stop areas you can draw both a transfer link (linear distance between the stop areas) as well
    as one or more bars for a proportional display of the values. Use the stop area filter or the classified display of transfer relations (see User Manual: Chpt. 24.8 , page 2392) to limit the display to particular transfer relations. In addition to transfers, other attributes like, for example,
    the different walk times can be displayed graphically.

    764

    PTVGROUP

    12.10 PuT connections and transfer flows

    Illustration 262: Transfer relations between stop areas of a stop

    12.10

    PuT connections and transfer flows


    The clock-face transfers view displays connections on the supply side and volumes and transfer flows on the demand side.
    The temporal distribution over the clock-face is defined by a basic cycle. Around the outer
    edge of the clock arriving and departing vehicle journeys are shown at the minute they pass
    the stop. Within time tolerances, vehicle journeys of the same line and direction can be aggregated to service groups, separately for arrival and departure. Accordingly, incoming and outgoing volumes as well as transfer flows within the stop can be displayed on this aggregation
    level. For matching connections, the transfer times inclusive of the walk times defined at the
    stop need to be taken into account. Transfer times and minimum walk times can be displayed
    in the shape of circular arcs for pairs of marked service groups.

    PTVGROUP

    765

    12.11 Lane allocation

    Illustration 263: Transfers display of regular services


    The assessment of connections is an important task for a planner. The view allows a detailed
    evaluation of connections and consistent connections, in particular in combination with differentiated demand flows. You can easily test and analyze the impact of several service variants on the demand flows at important transfer points.
    The view of the clock-face primarily allows an analysis of transfer flows according to temporal
    aspects. Respective evaluations can be supplemented by the graphic display of the spatial
    transfer relations between stop areas in the network.

    12.11

    Lane allocation
    To visualize the node topology in the network editor (see "Junction modeling" on page 88) you
    can graphically display the lane allocation at nodes. A rectangle is then drawn for each outgoing link of a node, which is open for one or more PrT transport systems and which has one
    or more lanes. Inside the rectangle, an arrow is drawn for each approach lane and an arrow
    head for each permitted lane turn. The illustration 264 shows an example of a node with four
    legs.

    766

    PTVGROUP

    12.11 Lane allocation

    Illustration 264: Lane allocation in the network display


    A classified display is also possible for the lane allocations, by direct and indirect node attributes. This is how you can export the lane allocation in different colors, depending on the
    node volume. The illustration 265 demonstrates this with an example of a roundabout.

    Illustration 265: Classified lane allocation according to the node volume

    PTVGROUP

    767

    12.12 2D display

    12.12

    2D display
    For point objects, (for example nodes or stops) the two-dimensional (extrapolated) display
    type can be actuated for display of the distribution of attribute values. Any numerical attribute
    can be selected for display of extrapolated attribute values.
    The attribute value of the point object is extrapolated over the entire network area. For twodimensional visualization, up to 10 value ranges can be defined with a specific background
    color assigned to each interval.
    The extrapolation process:
    Based on each Visum object of the selected point object class (nodes, zones, ...) an extrapolated value is computed for each pair of co-ordinates in the network area. In this process, the extrapolated value rises linearly with growing distance from the point object. The
    rising speed is specified as parameter v-access.
    The final extrapolated attribute value of a pair of co-ordinates is the minimum of all attribute values calculated from all Visum objects.
    Example
    Node P1 with co-ordinates (x,y) = (0,0) has AddVal1 = 100. Point P = (300, 400) has a distance
    of
    to P1. This distance is 500m if the network scale is 1. Using V-access
    = 5 (km/h), the AddValue will rise by 360, because for 500 m exactly 360 seconds are required
    if speed = 5 km/h. The P1-related extrapolated AddValue of point P sums up to 100 + 360 =
    460.
    Finally, the minimum of all extrapolated values calculated by Visum from all point objects Pi of
    the network is the extrapolated AddVal attribute value of point P.
    Based on user-defined classification intervals, the graphical display of attribute value distribution will show rings of value ranges having specific colors around any point object (illustration 266) of the selected class.

    768

    PTVGROUP

    12.12 2D display

    Illustration 266: Isochrone view


    Originally, this display type has been implemented in Visum for graphical display of isochrones (see "Displaying isochrones and the accessibility of network objects" on page 2278)
    showing accessibility of network objects.
    For the extrapolation of numerical attributes of Visum point objects, the input parameters do
    not necessarily have to be of the speed or time data type.
    V-access (access speed) for extrapolation of attribute values
    tMax-access (maximum extrapolated attribute value) for classified display
    V-access (access speed)
    Internally, the formula
    is still used by Visum. For calculation of t values, speed is specified by the user as parameter v=v-access and distance s results from the network scale. For
    attributes of other data types (for example AddValues without [unit]) the following has to be
    taken into account: Formula

    PTVGROUP

    produces a value in [seconds], which is, depending on the

    769

    12.13 Schematic line diagram


    attributes data type, interpreted as 1 unit. See example above: the resulting 360 [s] are added
    to the AddVal data.

    12.13

    Schematic line diagram


    The schematic line diagram visualizes PuT supply in the form of a schematic network display
    similar to the flow bundles in the network. The tool is also known as Timetable network graph
    (used in earlier versions of Visum). In this display selected stops of the network, the so-called
    transfer nodes, are symbolized by squares which are connected to one or more edges each.
    They each represent a subset of the vehicle journeys of the PuT supply with specific properties
    between the transfer nodes. The display can be supplemented by bars, transfer flows, labels
    and a legend.
    In the planning process, this display format serves a better understanding of the current supply
    concept and the optimization and manual planning of timetables and connections, especially
    in combination with other views (synchronization of the marked stops), for example the clockface transfers view (see "PuT connections and transfer flows" on page 765). In addition, the
    finished graphics can be used to communicate planning results to other planners, decision
    makers or customers. It can also be updated when changes occur in the timetable supply.

    12.13.1 Defining and editing a schematic line diagram


    To create a schematic line diagram, you first need to add the relevant transfer nodes to the
    graphics, individually (see User Manual: Chpt. 24.16.3.1 , page 2452) or bundled by a filter
    (see User Manual: Chpt. 24.16.3.2 , page 2452). Visum automatically positions the squares
    that symbolize a transfer node each based on the geographical location of the nodes and avoids a graphical overlap. You can edit the position of the transfer nodes to achieve the desired
    layout (see User Manual: Chpt. 24.16.3.1 , page 2452) . This does not change the geographical location of the stops in the network. Stops that are added later will be positioned
    automatically by Visum even if the display is stretched or compressed.
    To add edge courses to the view, you have to select the relevant vehicle journeys individually
    or by choosing time slots, lines, directions, line routes or time profiles (see User Manual: Chpt.
    24.16.4 , page 2453). An edge course in the schematic line diagram always represents a set
    of vehicle journeys. Depending on the aggregation function and the connection of edges (see
    User Manual: Chpt. 24.16.8 , page 2475), Visum generates one or more edge courses between the transfer nodes. These are inserted automatically, preferably without any overlap and
    arranged in a clearly visible manner. The size of each transfer node is adjusted depending on
    the number of attached edge courses. You can manually edit the courses as well as the positions where the edge courses touch the transfer nodes. Edge courses can have any number of
    intermediate points between which they are always arranged rectangularly or diagonally. A
    help grid is used for the positioning of the transfer nodes and the edge courses, which can be
    displayed, if needed.
    Besides the manual editing of the layout, you can optimize the positions of the transfer nodes
    and the edge courses later with an automatic algorithm.

    770

    PTVGROUP

    12.13.2 Display of supply in the schematic line diagram

    12.13.2 Display of supply in the schematic line diagram


    The edge courses displayed in the schematic line diagram represent subsets of the vehicle
    journeys, more precisely the respective vehicle journey items, operating between the transfer
    nodes. The total set of vehicle journey items displayed in the schematic line diagram is based
    on the selected transfer nodes and vehicle journeys. This set is displayed through one or more
    edge courses between two transfer nodes, the number of edges resulting from the relevant
    start and end points of the edges of one of the following objects:
    all stops where boarding or alighting is permissible
    all stops with profile points
    all stops with route points
    all stops of the line route
    line route items with a specific attribute value
    This allows you to realize different views of the timetable (passenger view, operation level).
    The number of edges between the two transfer nodes results from vehicle journey aggregation
    performed on a chosen aggregation level (see User Manual: Chpt. 24.16.8 , page 2475). Besides the 'typical' aggregation of the vehicle journeys based on the service pattern or lines between the transfer nodes, further aggregation levels can be chosen:
    Service trip pattern number (=service pattern)
    Line directed / undirected
    Main line directed / undirected
    Line route
    Vehicle journey (no aggregation)
    Time profile
    Transport system directed / undirected
    Operator directed / undirected
    Some aggregation levels distinguish between directed and undirected. This way you can control if one edge course each will be created between the transfer nodes or only one common
    edge course for both "running directions". In the case of the other aggregation levels which
    relate to vehicle journey-based attributes, an undirected display does not make sense; therefore only directed edge courses will be created.
    For the aggregation by service trip pattern number, the respective input attribute will be used. It
    can either be determined manually, via the Calculate service trip patterns (see User
    Manual: Chpt. 19.5 , page 2086)procedure or the respective Multi-edit functionality for vehicle
    journeys. There you will find the description of the algorithms for the calculation of the service
    trip patterns.
    For edge courses, you can specify the standard graphic parameters for line objects. As a special feature, you can classify edge courses on two classification levels, for example to combine
    a display of the service frequency with the standard colors for specific lines. For the illustration
    of the service frequency in particular, several new line styles featuring up to four parallel lines
    can be selected (see User Manual: Chpt. 24.16.5 , page 2455).
    For coupled vehicle journey sections, you can display branches in the schematic line diagram.
    Furthermore, you can bundle edge courses manually. This way you can display supplies as

    PTVGROUP

    771

    12.13.3 Display of demand and transfer flows in the schematic line diagram
    such, where a headway of an hour can be achieved by an alternate service of a main section
    instead of lines operating with a headway of two hours with deviating destinations.
    The edge courses can be labeled with attribute values at the start transfer node and end transfer node each and at the center of the course. For the transfer nodes, up to three attribute
    values can be used for the label within or at a chosen position outside of the rectangle.
    For the classification and labels of the edge courses, some attributes aggregated from the data
    of the underlying vehicle journeys are available:
    Headway
    Departure and arrival times
    Number of stopovers
    Run times
    Volumes
    In addition, relations to vehicle journey items and to the opposite direction are available. They
    provide access to further aspects of the data model.

    12.13.3 Display of demand and transfer flows in the schematic line diagram
    On the edge courses you can display any attribute values of the underlying vehicle journeys,
    for example volumes. For the formatting of bars, especially for a classified display, the standard graphic parameters are provided (see User Manual: Chpt. 24.16.5 , page 2455). Unlike
    for link bars, the attribute value allocated to an edge is not constant over the entire course,
    because an edge symbolizes a set of vehicle journeys between any selected transfer nodes,
    so that the volume, for example, may differ at the hidden stopovers. Bars can thus be divided
    at the centered label and show the attribute values that each apply to the start transfer node
    and the end transfer node on the two sections.
    To visualize transfer flows you can display bars between the incoming and outgoing edge
    courses within the transfer nodes. You can specify the bar display with the standard parameters.

    12.13.4 Saving layout information and transferring layouts to variants


    On the one hand, the arrangement of the elements in the schematic line diagram is based on
    the selection of transfer nodes and vehicle journeys. On the other hand, it is optimized and
    adjusted to your needs by manual modifications. In many cases, a suitable arrangement shall
    be used for other variants and timetable updates. If they were linked to the data structures in
    the data model, manual modifications would be lost as soon as an edge course disappeared
    from the schematic line diagram, e.g. due to the selection of a different aggregation level, a
    modification of the vehicle journey selection, or changes to or even replacements of timetable
    data (e.g. due to data import for a new timetable period). To retain a manually edited layout of
    the schematic line diagram despite such modifications and transfer the layout to other supply
    variants in other version files, the following mechanisms are provided. Besides automatically
    saving parameters in the version file, you can separately save all parameters to files and
    reload them, which allows you to easily transfer the layout and graphic parameters to other version files. The settings are saved in two kinds of files. The graphic parameters file contains all
    purely graphic settings regarding colors, bars and so on. The layout file contains the settings
    regarding selected transfer nodes and vehicle journeys and their positions and courses as
    772

    PTVGROUP

    12.14 Signal time-space diagram


    well as the information on the allocation of vehicle journeys to edge courses. In the schematic
    line diagram, the allocation of vehicle journeys to edge courses is not controlled by the actual
    key attribute (i.e. the vehicle journey number) but, depending on the selected aggregation
    level, via a set of identifying attributes. In the layout parameters window (see User Manual:
    Chpt. 24.16.8 , page 2475), these attributes are listed in the field Identification attribute for
    unused edge courses. When editing the timetable data or the layout parameters (for example
    the vehicle journey selection), the vehicle journeys are reallocated to the edge courses based
    on these attributes, new edge courses are created, if necessary, existing ones are hidden and
    the graphic display is adjusted. Even for hidden edge courses the layout parameters will not
    be lost, i.e. Visum "remembers" that there used to be an edge course for line A between transfer node 123 and 987 with a manually adjusted course, even if the edge is not displayed any
    more. This information is used again when requesting an edge course with the same key once
    more. You can, however, explicitly empty this "memory" of the schematic line diagram.
    The dynamic allocation of vehicle journeys to edge courses and the preservation of the layout
    information on hidden edge courses allows you to retain a display despite of changes to or a
    complete exchange of the timetable data (with deviating vehicle journey numbers) and use it
    on other supply variants. In particular, this mechanism allows the use of the schematic line diagram together with the scenario management, when, for example, creating a line diagram with
    the desired layout in the base version which will then be automatically adjusted to the data of
    the scenario when opening scenario results.

    12.14

    Signal time-space diagram


    With the signal time-space diagram (see User Manual: Chpt. 24.17 , page 2479), you can display the signal times of signal controls along a path (see "Paths" on page 63) in a timedistance diagram and manually adjust and optimize the offset between the signal controls.
    Optionally, green bands can also be displayed for a second path in opposite direction. The
    green bands start at the green times of the upstream signal controls and extend in driving
    direction to the next signal control. The gradient is determined on the basis of the travel time
    that is calculated according to the parameters set for the signal offset optimization (see User
    Manual: Chpt. 18.4.2 , page 1923). You can choose between two different display modes for
    the signal space-time diagram. In the "Flowing off" mode, the green bands are drawn as parallelograms whose width corresponds to the entire green time of the upstream signal controls.
    In the "Arterial bands" mode, the green band with the maximum width is determined which
    leads through the green stages of all signal controls of the signal time-space diagram ("progressive signal system"). If such a green band cannot be found, no green band will be drawn.

    PTVGROUP

    773

    12.14 Signal time-space diagram

    Illustration 267: Signal time-space diagram in mode "Flowing off"

    Illustration 268: Signal time-space diagram in mode "Arterial bands"


    774

    PTVGROUP

    12.15 Column charts


    The offset of the signal controls can be edited directly in the diagram in order to synchronize
    the green bands.
    A user-defined PrT path which shall be used for the opposite direction, must have at least two
    nodes in common with the path of the first direction and all intermediate nodes must be traversed in reverse order. This requirement permits the use of two separate paths for the display
    and thus, for example, the consideration of lanes divided by direction.

    12.15

    Column charts
    You can create column charts with values of direct and indirect attributes (see "Attributes" on
    page 103) from the network editor, for individual network objects (see User Manual: Chpt.
    12.14 , page 773). You can create common chart displays directly from Visum, without having
    to export list contents to Excel, to create the graphics there.
    There are two standard types of column charts:
    Column charts for time intervals: If you have defined time intervals (see "Spatial and temporal correlations in Visum" on page 94) in your model, you can display an attribute for
    each time interval, for a network object. This function especially supports you when analyzing dynamic assignments. The illustration 269 shows a column chart, for which three
    columns with the passenger volume for the entire PuT, the tram and the bus are drawn for
    a link, for each time interval.

    Illustration 269: Column charts for time intervals


    Column charts for relations between network objects. For a network object (for example
    stop), you can display attributes, linked via the Visum data model network object (for example the stop points of a stop) as column charts. In illustration 270, a column chart was invoked for the stop Durlacher Tor and a column was drawn for each network object stop
    point. As you can see, the stops are assigned three stop points, for which each the number of boarding passengers, alighting passengers and transfers is displayed as a column
    chart.

    PTVGROUP

    775

    12.16 Evaluations in the timetable editor

    Illustration 270: Column chart for relations between network objects

    12.16

    Evaluations in the timetable editor


    In the Visum timetable editor you are provided with the tabular timetable as a tabular and the
    graphical timetable as a graphical evaluation tool (see User Manual: Chpt. 15.43 , page
    1526). The timetable editor also offers a block view for line blocks (see "Displaying line blocks
    in the block view" on page 2119).
    Tabular timetable
    In the standard view, the tabular timetable is presented as in illustration 271.

    776

    PTVGROUP

    12.16 Evaluations in the timetable editor

    Illustration 271: Tabular timetable in the standard view


    In the regular service mode (see User Manual: Chpt. 15.43.4 , page 1531) all vehicle journeys
    are displayed as regular services with the additional attributes Headway start, Headway end,
    Headway time and Number of vehicle journeys (illustration 272).

    PTVGROUP

    777

    12.16 Evaluations in the timetable editor

    Illustration 272: Tabular timetable in regular service mode


    You can also display the columns of the tabular timetable as classified (see User Manual:
    Chpt. 24.2 , page 2337). In the following example, the table background is classified by revenues (illustration 273).

    778

    PTVGROUP

    12.16 Evaluations in the timetable editor

    Illustration 273: Table background classified by revenue


    Graphical timetable
    Vehicle journeys and vehicle journey sections are displayed graphically in the graphical timetable. In illustration 274, the stroke display is classified according to lines (see User Manual:
    Chpt. 24.2 , page 2337), to distinguish vehicle journeys of different lines by using different
    colors.

    PTVGROUP

    779

    12.16 Evaluations in the timetable editor

    Illustration 274: Graphical timetable with classified display of vehicle journey line style properties
    Item bars, which can be scaled with direct and indirect vehicle journey or vehicle journey section attributes, can be drawn for vehicle journeys and vehicle journey sections (see User
    Manual: Chpt. 24.2 , page 2337). In the following example, the Volume of the vehicle journeys
    is used as scaling attribute (illustration 275).

    780

    PTVGROUP

    12.16 Evaluations in the timetable editor

    Illustration 275: Item bars for vehicle journeys


    Item bars can also be classified (see User Manual: Chpt. 24.2 , page 2337). In illustration 276
    classification is carried out with the vehicle journey volume.

    PTVGROUP

    781

    12.16 Evaluations in the timetable editor

    Illustration 276: Classification of item bars with the vehicle journey volume
    Visum offers the possibility of displaying multiple bars with different attributes on vehicle journeys or vehicle journey sections (see User Manual: Chpt. 24.2 , page 2337). The illustration
    277 displays bars for Boarding passengers , Alighting passengers and Through passengers.

    782

    PTVGROUP

    12.16 Evaluations in the timetable editor

    Illustration 277: Display of item bars for boarding passengers, through passengers and alighting passengers

    PTVGROUP

    783

    13 Literature

    13

    Literature
    Bellei, G.; Gentile, G.; Meschini, L.; Papola, N.: A demand model with departure time choice
    for within-day dynamic traffic assignment. In: European Journal of Operational Research
    175 (2006), No. 3, pages 1557-1576
    (available online at URL http://www.sciencedirect.com)
    Bellei, G.; Gentile, G.; Papola, N.: A within-day dynamic traffic assignment model for urban
    road networks. In: Transportation Research B 39 (2005), No. 1, pages 1-29 (available
    online at URL http://www.sciencedirect.com)
    Bregman, L. M.: Ein Beweis der Konvergenz des Verfahrens von G.W. Sheleikhovski fr ein
    Transportproblem mit Beschrnkungen (in Russian). Shurnal vycisl. mat. i mat. fiz. 7 (1967),
    No. 1, pages 147-156 (Convergence of the procedure)
    Bregman, L. M.: Eine Relaxationsmethode zur Bestimmung des gemeinsamen Punktes konvexer Mengen und ihre Anwendung zur Lsung konvexer Optimierungsaufgaben (in Russian). Shurnal vycisl. mat. i mat. fiz. 7 (1967), No. 3, pages 620-631 [Engl. translation: The
    relaxation method of finding the common point of convex sets and its application to the solution of problems in convex programming. U.S.S.R. Computational Math. Math. Phys. 7
    (1967), pp.200-217]
    Brilon, W.: Traffic engineering and the new German highway capacity manual. In: Transportation Research A 28 (1994), No. 6, page 473
    (available online at URL http://www.sciencedirect.com)
    Brilon, W.; Weinert, A.: Bemessungsverfahren fr Knotenpunkte mit abknickender Vorfahrt. In:
    Straenverkehrstechnik 7, 2002, pages 346-356.
    Bundesministerium fr Verkehr (publisher): Richtlinien fr den Lrmschutz an Straen, Ausgabe 1990 (RLS-90). Federal Ministry of Transport, Building and Urban Affairs, 1990
    EMNID-Institut GmbH (publisher): KONTIV 89: Bericht zur Methode. Anlagenband und Tabellenteil. Bielefeld, 1991 (Method report)
    Evans, A. W.: Some properties of trip distribution methods. In: Transportation Research 4
    (1970), No. 1, pages 19-36 (available online at URL http://www.sciencedirect.com)
    Evans, S. P.; Kirby, H. R.: A three-dimensional Furness procedure for calibrating gravity
    models. In: Transportation Research 8 (1974), No. 2, pages 105-122 (available online at
    URL http://www.sciencedirect.com)
    Frschner, G.: Verkehrsplanerische Berechnungsmethode des Straengterverkehrs. In: Wissenschaft und Technik im Straenwesen, Heft 20, Berlin, 1982 (Transportation planning calculation method)
    Forschungsgesellschaft fr Straen- und Verkehrswesen (publisher): Leitfaden fr Verkehrsplanungen. Kln: FGSV, 1985. (Road Traffic Resarch Association in Germany), 1985
    Forschungsgesellschaft fr Straen- und Verkehrswesen (publisher): Richtlinien fr die
    Anlage von Straen, Teil: Wirtschaftlichkeitsuntersuchungen (RAS-W86). Kln: FGSV,
    1986 (Road Traffic Resarch Association in Germany)
    Forschungsgesellschaft fr Straen- und Verkehrswesen (publisher): Empfehlungen fr
    Wirtschaftlichkeitsuntersuchungen an Straen (EWS-97): Aktualisierung der RAS-W86.
    Kln: FGSV, 1997. (Road Traffic Resarch Association in Germany)
    Furness, K. P.: Trip forecasting. Unpublished presentation. London, 1962
    Furness, K. P.: Time function iteration. In: Traffic Engin. Control 7 (1965), No. 7, pages 458460

    784

    PTVGROUP

    13 Literature
    Gentile G.: Linear User Cost Equilibrium: a new algorithm for traffic assignment. Submitted for
    publication, 2009
    Gentile, G.; Meschini, L.; Papola, N.: Macroscopic arc performance models with capacity constraints for within-day dynamic traffic assignment. In: Transportation Research B 39 (2005),
    No. 4, pages 319-338 (available online at URL http://www.sciencedirect.com)
    Gentile, G.; Meschini, L.: Fast heuristics for the continuous dynamic shortest path problem in
    traffic assignment. Submitted to the AIRO Winter Conference 2005 special issue of the European Journal of Operational Research on Network Flows, 2006
    Gentile, G.; Meschini, L.; Papola, N.: Spillback congestion in dynamic traffic assignment: a
    macroscopic flow model with time-varying bottlenecks. In: Transportation Research B 41
    (2007), No. 10, pages 1114-1138 (available online at URL http://www.sciencedirect.com)
    The Highways Agency (publisher): The geometric design of roundabouts. In: Design Manual
    for Roads and Bridges, Vol. 6, Section 2, Part 3, TD 16/93. London, 1993
    Kimber, R. M.: The traffic capacity of roundabouts. In: Transportation and Road research Laboratory report LR 942. Crowthorne: Transportation and Road research Laboratory, 1980
    Kimber, R. M.; Daly, P. N.: Time-dependent queueing at road junctions: Observation and prediction. In: Transportation Research B 20 (1986), No. 3, pages 187-203 (available online at
    URL http://www.sciencedirect.com)
    Kimber, R. M.; Hollis, E. M.: Traffic queues and delays at road junctions. Transportation and
    Road research Laboratory report LR 909. Crowthorne: Transportation and Road research
    Laboratory, 1979
    Kirby, H. R.: Theoretical requirements for calibrating gravity models. In: Transportation Research 8 (1974), No. 2, pages 97-104
    (available online at URL http://www.sciencedirect.com)
    Kirchhoff, P.: Verkehrsverteilung mit Hilfe eines Systems bilinearer Gleichungen: Ein Beitrag
    zur Entwicklung von Verkehrsverteilungsmodellen. Braunschweig, Technische Universitt,
    Institut fr Verkehr und Stadtbauwesen, Diss., 1970 (Dissertation on Trip distribution)
    Kirchhoff, P.; Leutzbach, W.; Pampel, E.; Holz, S.; Mott, P.; Sahling, B. M.: Verkehrs- und
    Betriebsplanung. In: Forschung Stadtverkehr, Reihe Auswertungen, Heft A3, 1987. (Traffic
    and Operational Planning)
    Lamond, B.; Stewart, N. F.: Bregmans balancing method. In: Transportation Research B 15
    (1984), No. 4, pages 239-248 (available online at URL http://www.sciencedirect.com)
    Lebeuf, R.; Jrnsten, K.; Stewart, N. F.: On the use of Bregmans balancing method for the
    solution of relaxed distribution problems. Tech. Rep. No. 353. Montral, Universit de Montral, Dpartement d'informatique et de recherche oprationelle (IRO), 1980
    Leutzbach, W.; Haupt, T.; Mott, P.: Ermittlung der Verkehrsnachfrage. In: Forschung Stadtverkehr, Reihe Auswertungen, Heft A4, 1988. (Determination of Travel Demand)
    Lohse, D.: Berechnung von Personenverkehrsstrmen. In: Wissenschaft und Technik im Straenwesen, Heft 17, 1977 (Calculating passenger demand flows)
    Lohse, D.; Teichert, H.; Dugge, B.; Bachner, G.: Ermittlung von Verkehrsstrmen mit n-linearen Gleichungssystemen Verkehrsnachfragemodellierung. Scientific series of Institut fr
    Verkehrsplanung und Straenverkehr of TU Dresden, Vol. 5, p. 102, 1997 (Calculating passenger demand flows)
    Lohse, D.; Wegener, B.: Abschnitt 3: Verkehrsplanerische Berechnungsverfahren. In: Bauakademie der DDR (publisher): Richtlinie fr Stadtstraen. Teil I: Methoden und Verfahren

    PTVGROUP

    785

    13 Literature
    der stdtischen Verkehrsplanung, Ausgabe 1981. Berlin: Bauinformation, 1982 (Transportation planning calculation procedures)
    Mcke, P. A.; Ruske, W.: Straenverkehrstechnische Untersuchungen fr den zweiten Ausbauplan. In: Strae und Autobahn 19 (1968), No. 6, pages 201-211 (Transportation planning analyses)
    Mhring, R.; Nkel, K.; Wnsch, G.: A model and fast optimization method for signal coordination in a network. In: van Zuylen, H.; Middelham, F. (publisher): Proceedings of the 11th
    Symposium on Control in Transportation Systems - CTS 2006, pages 73-78, Delft, 2006
    Nordic Council of Ministers (publisher): Road Traffic Noise: Nordic Prediction Method. Tema
    Nord 1996: 525. Denmark : Nordic Council of Ministers, 1996. ISBN 9291208361
    Norm DIN 18005 Teil 2 September 1991. Schallschutz im Stdtebau: Lrmkarten; Kartenmige Darstellung von Schallimmissionen. Berlin: Beuth Verlag, 1991 (Noise Prevention in Urban Development)
    Ortzar, J. D.; Willumsen, L. G.: Modelling Transport. Chichester : Wiley, 1990
    Ortzar, J. D.; Willumsen, L. G.: Modelling Transport. Third edition. Chichester : Wiley, 2001
    Salzwedel, J.: Untersuchungen zur Einordnung der verkehrsplanerischen Berechnung des
    Gter- und Wirtschaftsverkehrs in das Modell- und Programmsystem PEVA. (Transportation
    planning analyses). Dresden, Technische Universitt, Institut fr Verkehrsplanung und
    Strassenverkehr, Diplomarbeit, 1997 (Degree dissertation)
    Schiller, C.: Integration des ruhenden Verkehrs in die Verkehrsangebots- und Verkehrsnachfragemodellierung. Scientific series of Institut fr Verkehrsplanung und Straenverkehr of TU Dresden, Vol. 8, 2004 (Transport supply and Traffic demand modelling)
    Schmiedel, R.: Bestimmung verhaltensorientierter Personenkreise fr die Verkehrsplanung.
    Karlsruhe, Universitt (TH), Fakultt fr Bauingenieur- und Vermessungswesen, Diss.,
    1984 (Dissertation on Behaviour-oriented coverage)
    Schnabel W.; Lohse, D.: Grundlagen der Straenverkehrstechnik und der Straenverkehrsplanung. Berlin : Transpress VEB Verlag fr Verkehrswesen, 1980 (Foundations of Traffic Engineering and Transportation Planning)
    Schnabel W.; Lohse, D.: Grundlagen der Straenverkehrstechnik und der Verkehrsplanung.
    Bd. 2. Berlin : Verlag fr Bauwesen, 1997 (Foundations of Traffic Engineering and Transportation Planning)
    Sonntag, H. u.a.: Entwicklung eines Wirtschaftsverkehrsmodells. Bundesministerium fr Verkehr. Berlin, 1995 - Forschungsbericht im Auftrag des Bundeministeriums fr Verkehr (Commercial transport model development)
    Transportation Research Board: Highway Capacity Manual, Washington, DC, 2000.
    Transportation Research Board: Highway Capacity Manual, Washington, DC, 2010.
    U.S. Bureau of Public Roads (publisher): Traffic Assignment Manual. Washington, D.C.: U.S.
    Department of Commerce, Bureau of Public Roads, 1964

    786

    PTVGROUP

    List of illustrations

    List of illustrations
    Illustration 1: Visum network model and impact model
    16
    Illustration 2: Example of the temporal distribution of travel demand by four intervals of 30
    minutes
    20
    Illustration 3: Network of the original version
    26
    Illustration 4: Network of the version used for version comparison
    26
    Illustration 5: Network with version comparison: The volumes of both versions compared as
    well their difference are displayed. "Verscomp" is the name of the version comparison. 27
    Illustration 6: Network 1 used for merge network
    29
    Illustration 7: Network 2 used for merge network
    29
    Illustration 8: Merge network of network 1 and network 2
    30
    Illustration 9: Connection between transport systems, modes, demand segments and
    demand matrices
    46
    Illustration 10: Example of a TURNSTANDARD table in the network file, which is used to specify standard values for turn penalties and turn capacity
    52
    Illustration 11: Rank of the link type and its resulting major flows (yellow), flow hierarchy (red) 54
    Illustration 12: Examples for defining transport systems of a link
    55
    Illustration 13: Example for the different speeds of two PrT transport systems depending on
    the volume
    56
    Illustration 14: Transportation demand between zones illustrated in the transport network and
    as a demand matrix
    57
    Illustration 15: Supply of the travel demand via connectors to the network
    58
    Illustration 16: Possibilities for modeling connectors
    59
    Illustration 17: Intersection area with multiple nodes
    60
    Illustration 18: Node and link types of main nodes
    61
    Illustration 19: Main turns open to traffic
    62
    Illustration 20: Main turns not open to traffic
    62
    Illustration 21: The stop hierarchy
    65
    Illustration 22: Possibilities of modeling stop points
    66
    Illustration 23: The line hierarchy used to model the PuT supply
    69
    Illustration 24: Example for two line routes of a line
    70
    Illustration 25: Example of two time profiles of a line route
    71
    Illustration 26: Lengths in Visum and their coherence
    74
    Illustration 27: Assignment of run times in Visum
    75
    Illustration 28: Example of the aggregation of line routes
    77
    Illustration 29: Examples: Coupling two and three line routes
    78
    Illustration 30: Calculation example for the calculation of indicators in case of couplings
    79
    Illustration 31: Reachability analyses for secondary schools
    82
    Illustration 32: Allocating POIs to links
    83
    Illustration 33: Visualization of the local position of count locations with the date of the count 85
    Illustration 34: The Congestion Charge in London is an area toll
    86
    Illustration 35: Summation and average calculations with screenlines
    87
    Illustration 36: Calculation of the urban traffic volume with screenlines
    88
    Illustration 37: Time series by percentage
    97
    PTVGROUP

    787

    List of illustrations

    97
    Illustration 38: Time series of matrix numbers
    Illustration 39: The relationship between the different analysis time slots
    99
    Illustration 40: Assignment not possible because the validity of the demand and the assignment time interval do not overlap.
    101
    Illustration 41: The demand between 6:30 and 7:30 a.m. is assigned.
    101
    Illustration 42: The demand between 6:30 and 7:30 a.m. is assigned.
    101
    Illustration 43: Structural data of zones stored in user-defined attributes
    111
    Illustration 44: Count data stored in user-defined link attributes
    112
    Illustration 45: Generating a subnetwork with stop point matrices regarding path legs and
    stop point matrices regarding paths
    120
    Illustration 46: Positive and negative surfaces
    124
    Illustration 47: Surfaces after import
    127
    Illustration 48: Blue and red surfaces were adjusted to each other
    128
    Illustration 49: Blue surface is the reference surface, red surface adjusts itself to the blue surface
    128
    Illustration 50: Correlations between different demand objects
    135
    Illustration 51: Integrated 4-step demand model in Visum
    137
    Illustration 52: Extended 4-step model
    138
    Illustration 53: Modeling through decision tree
    141
    Illustration 54: Daily time series for origin-destination groups of HW and WH (SrV 1987 Dresden)
    147
    Illustration 55: EVA1 function dependent on impedance w
    170
    Illustration 56: EVA2 function dependent on the parameters a and b
    171
    Illustration 57: Application of tolerance value in Go to procedure
    197
    Illustration 58: Impedance calculation for a PuT connection, for clarity illustrated in the unit
    [min]
    223
    Illustration 59: Example network
    229
    Illustration 60: VD function type BPR according to the Traffic Assignment Manual
    235
    Illustration 61: VD function type INRETS
    237
    Illustration 62: VD function type LOHSE
    239
    Illustration 63: Capacity analysis process for signalized nodes
    247
    Illustration 64: Method of calculation at two-way stops
    268
    Illustration 65: Calculation process for an all-way stop node
    280
    Illustration 66: Calculation process for roundabouts according to HCM 2010
    288
    Illustration 67: Approaching flows at a four-leg roundabout
    290
    Illustration 68: Calculation process for roundabouts according to the TRL/Kimber method
    293
    Illustration 69: Description of the node geometry for the TRL/Kimber model
    294
    Illustration 70: Example network for signal coordination
    303
    Illustration 71: Green time split at all nodes with succeeding left turns
    304
    Illustration 72: A path through the example network passes SCs at nodes 7003, 8003, 8002
    and 9002
    305
    Illustration 73: Progression quality for approach West at node 8003
    305
    Illustration 74: Progression quality for approach North at node 8002
    306
    Illustration 75: Example network for proportional distribution of the traffic demand
    313

    788

    PTVGROUP

    List of illustrations

    Illustration 76: Blocking back model, phase 1: Formation of congestion Iteration steps 1 and
    2.
    321
    Illustration 77: Blocking back model, phase 1: Formation of congestion Iteration step 3, route
    1
    321
    Illustration 78: Blocking back model, phase 1: Formation of congestion Iteration step 3, route
    2
    322
    Illustration 79: Blocking back model, phase 1: Formation of congestion Iteration step 4, route
    1
    322
    Illustration 80: Blocking back model, phase 1: Formation of congestion Iteration step 4, route
    2
    323
    Illustration 81: Blocking back model, phase 2, relief of congestion. Initial situation
    323
    Illustration 82: Blocking back model, phase 2, relief of congestion. Iterations step 1, route 1 324
    Illustration 83: Blocking back model, phase 2, relief of congestion. Iteration step 1, route 2 324
    Illustration 84: Blocking back model, phase 2, relief of congestion. Iteration step 2, route 1 325
    Illustration 85: Blocking back model, phase 2, relief of congestion. Iteration step 2, route 2 325
    Illustration 86: Blocking back model, phase 2, relief of congestion. Iteration step 3, route 1 325
    Illustration 87: Blocking back model, phase 2, relief of congestion. Iteration step 3, route 2 326
    Illustration 88: Overall wait time as an integral via the interpolated measured queue lengths 328
    Illustration 89: Parameterization of the Kirchhoff distribution model
    331
    Illustration 90: Parameterization of the Logit distribution model
    331
    Illustration 91: Parameterization of the Box-Cox distribution model
    332
    Illustration 92: Parameterization of the Lohse distribution model
    333
    Illustration 93: Distribution with variable beta according to the modified Kirchhoff rule (see
    Schnabel / Lohse)
    334
    Illustration 94: Parameterization of the Lohse distribution model with variable Beta
    335
    Illustration 95: The procedure of incremental assignment
    339
    Illustration 96: Example network for equilibrium assignment
    344
    Illustration 97: The procedure of equilibrium assignment
    348
    Illustration 98: The procedure of network balancing for an OD pair during equilibrium assignment
    349
    Illustration 99: Linear User Cost Equilibrium between two paths
    355
    Illustration 100: Numerical example of the procedure of how to obtain the descent direction 359
    Illustration 101: Numerical example of the procedure of how to obtain the descent direction 360
    Illustration 102: Example for the proportionality with balanced link volumes
    364
    Illustration 103: Extended example for the proportionality with balanced link volumes
    365
    Illustration 104: The procedure of Equilibrium_Lohse assignment
    374
    Illustration 105: ICA-based impedance calculation
    375
    Illustration 106: The procedure of assignment with ICA
    382
    Illustration 107: Adjustment of the link VD function
    384
    Illustration 108: The procedure of stochastic assignment
    390
    Illustration 109: Discarding routes
    391
    Illustration 110: Example of similarity of routes
    392
    Illustration 111: Volumes and link run times after the first internal iteration step m=1
    396
    Illustration 112: Example for area toll: The London Congestion Charging Zone
    401

    PTVGROUP

    789

    List of illustrations

    Illustration 113: Reducing area toll to link toll(For reasons of clarity, turns without toll are not
    displayed)
    402
    Illustration 114: Toll station at highway exit
    403
    Illustration 115: Example of a matrix toll
    403
    Illustration 116: Shortest path search graph with matrix toll
    404
    Illustration 117: Time-cost diagram
    405
    Illustration 118: Density function
    406
    Illustration 119: Distribution function
    406
    Illustration 120: Efficient routes
    407
    Illustration 121: Distribution of traffic demand across the routes
    408
    Illustration 122: Equilibrium formation with TRIBUT
    409
    Illustration 123: Attribute selection for the Toll systems list
    409
    Illustration 124: Attribute selection for the Toll matrices list
    410
    Illustration 125: The dynamic user equilibrium problem
    411
    Illustration 126: Time slice approach (left) and time profile approach (right) to the Continuous Dynamic Network Loading problem
    412
    Illustration 127: Scheme of the fixed point formulation for WDDTA with spillback congestion 413
    Illustration 128: Recursive expressions of path exit time, entrance time and cost
    415
    Illustration 129: The adopted parabolic-trapezoidal fundamental diagram, expressing the
    relation among vehicular flow, speed, and density along a given arc.
    416
    Illustration 130: The trapezoidal fundamental diagram suggested for urban links
    417
    Illustration 131: Scheme of the fixed point formulation for the NPM
    418
    Illustration 132: Arc with time-varying capacity
    420
    Illustration 133: Flow pattern given by the Simplified Theory of Kinematic Waves
    421
    Illustration 134: Flow pattern given by the Averaged Kinematic Wave model
    422
    Illustration 135: Determination of the arc hypocritical exit time
    423
    Illustration 136: Trajectories of a hypercritical kinematic wave and of the intersecting vehicles
    424
    Illustration 137: Graphical determination of the time series of the inflow capacity in the case
    of triangular fundamental diagram, piecewise constant inflow, and constant exit capacity
    426
    Illustration 138: Dynamic version of the Bellman relation
    428
    Illustration 139: Variables and models of fixed point formulations for the network performance model (left) and for dynamic assignment with spillback (right)
    430
    Illustration 140: Example network
    432
    Illustration 141: Results of dynamic equilibrium assignment with and without spillback
    433
    Illustration 142: Shape of the fundamental diagram based on link attributes
    434
    Illustration 143: Parabolic sub-critical branch in the fundamental diagram
    435
    Illustration 144: Signalized intersection in reality
    435
    Illustration 145: Diagram of the signalized node in Visum
    436
    Illustration 146: Example of impedance calculation of a connection
    440
    Illustration 147: Example of network volume along a connection
    441
    Illustration 148: The procedure of dynamic stochastic assignment
    445
    Illustration 149: Different modeling options for main and subordinated networks
    450
    Illustration 150: Timetable
    452

    790

    PTVGROUP

    List of illustrations

    452
    Illustration 151: Line map
    Illustration 152: Example network
    463
    Illustration 153: Example for skim calculation for partially traversed links
    471
    Illustration 154: Network volume after transport system-based assignment (parameters file
    472
    TSys1.par)
    Illustration 155: Network volume after transport system-based assignment (parameters file
    473
    TSys2.par)
    Illustration 156: Example network for choice models
    488
    Illustration 157: Structure of the choice in scenario 1 (no information)
    488
    Illustration 158: Structure of the choice in scenario 2 (local information)
    489
    Illustration 159: Structure of the choice in scenario 3 (information in the vehicle)
    490
    Illustration 160: Volume for headway-based assignment, transfer penalty 2 min
    494
    Illustration 161: Coordination of lines
    496
    Illustration 162: Network volume for timetable-based assignment (parameter file timetab1.par)
    512
    Illustration 163: Flow chart of a timetable-based assignment
    514
    Illustration 164: Smoothing of the vol/cap ratio in iteration i
    525
    Illustration 165: Readiness to change dependent on the alternative's departure time
    527
    Illustration 166: Standard questionnaire
    533
    Illustration 167: Processing of PuT passenger surveys
    534
    Illustration 168: Validity check of the survey path leg
    536
    Illustration 169: Validity check of the preceding section
    537
    Illustration 170: Territories in the example
    544
    Illustration 171: Line 2 traverses several territories
    546
    Illustration 172: Allocation of vehicles and operators in the line hierarchy
    552
    Illustration 173: Example line block with pull-out trip, interlining trip and pull-in trip
    554
    Illustration 174: Conflict between empty trips and vehicle demand
    556
    Illustration 175: Line network of the example with three bus lines (red, blue and yellow)
    558
    Illustration 176: (Graphical) timetable of the example, color codes as above
    558
    Illustration 177: Covering the timetable through pure line blocks
    560
    Illustration 178: Covering the timetable through blocks without empty trips
    561
    Illustration 179: Covering the timetable through line comprehensive blocks with empty trips 563
    Illustration 180: Unsymmetrical timetable with trips beyond 24 hours
    566
    Illustration 181: Blocking days and vehicle demand
    570
    Illustration 182: Display of a change of the running direction in the course of vehicle journey
    block items. The line route makes a U-turn in the station "TFS"
    580
    Illustration 183: State model for line blocks
    583
    Illustration 184: Example for partitioning according to vehicle combination and operator
    586
    Illustration 185: Inserting the nodes and edges for vehicle journey sections
    587
    Illustration 186: Inserting the edges for entering the depots and for empty trips between stop
    points
    588
    Illustration 187: Inserting the edges for leaving from depots
    589
    Illustration 188: Example graph after inserting the timeline edges and edge reduction
    590
    Illustration 189: Optimal cost flow in the example graph
    592
    Illustration 190: Example 1 for the decomposition into blocks
    593

    PTVGROUP

    791

    List of illustrations

    Illustration 191: Example 2 for the decomposition into blocks


    Illustration 192: Example for block display of a block with 5 blocking days
    Illustration 193: Possibilities of fare modeling in Visum
    Illustration 194: Example for a distance-based fare with 5 fare stages
    Illustration 195: Example for a zone-based fare with three overlapping fare zones and six
    stops.
    Illustration 196: Example network with two lines and volume data
    Illustration 197: Calculation of service kilometers between 8 a.m. and 9 a.m.
    Illustration 198: Calculation of passenger kilometers between 8:00 a.m. and 9:00 a.m.
    Illustration 199: Calculation of passenger kilometers between 8a.m. and 9a.m.
    Illustration 200: Calculation schema for costs and revenues
    Illustration 201: Calculation of the fare points for path legs
    Illustration 202: Example network for fixed amount per path leg
    Illustration 203: Time-distance diagram for a vehicle journey with two vehicle journey sections
    Illustration 204: Aggregation along the line hierarchy
    Illustration 205: Aggregation of the service kilometers from the trips onto the line
    Illustration 206: Interpolation of passage times (run times in minutes)
    Illustration 207: Partially traversed links
    Illustration 208: Influence of couplings on the indicator calculation
    Illustration 209: Extended projection of attributes
    Illustration 210: Illustration of noise volume as link bars
    Illustration 211: Emissions relative to speed
    Illustration 212: Display of nitrogen monoxide volumes as link bars
    Illustration 213: Source and target attribute allocations
    Illustration 214: Land use from two shape files as background
    Illustration 215: Examples of overlapping network objects
    Illustration 216: Intersecting three polygon objects with a link buffer
    Illustration 217: Intersecting point objects with a polygon
    Illustration 218: Intersecting point objects with a buffer polygon
    Illustration 219: Intersecting point object buffers with polygons
    Illustration 220: Legend with user-defined texts
    Illustration 221: Visum network display without background
    Illustration 222: Visum network display with background
    Illustration 223: The flow bundle as path filter
    Illustration 224: Display of the flow bundle paths in the PuT path leg list
    Illustration 225: PuT node flow bundle with additional filter criteria for lines
    Illustration 226: Some of the paths which traverse node 100001 and use line 002
    Illustration 227: Display of through traffic with a flow bundle of active links
    Illustration 228: Paths which start in zone 102 and end in zones 1, 2 or 5
    Illustration 229: All paths which traverse a link section in north direction
    Illustration 230: Through traffic traversing the two links in the sequence specified
    Illustration 231: Combining flow bundles for PrT and PuT by using an OR operation
    Illustration 232: Link flow bundle with AND THEN operation and OR operation
    Illustration 233: Link flow bundle with alternative routes

    792

    594
    601
    606
    610
    611
    630
    642
    647
    648
    649
    663
    666
    671
    673
    674
    675
    676
    676
    678
    682
    683
    684
    693
    694
    696
    704
    704
    704
    705
    708
    711
    712
    717
    717
    719
    719
    721
    726
    727
    728
    730
    731
    732

    PTVGROUP

    List of illustrations

    733
    Illustration 234: Isochrones to display the accessibility of stop areas
    Illustration 235: Functional principle of isochrones illustrated in a simple example
    734
    Illustration 236: Accessibility of link sections from node 7357
    735
    Illustration 237: Classification of zones according to Isochrones time PrT
    736
    Illustration 238: 2D display of the accessibility of stop areas from the main station
    738
    Illustration 239: Classified display of stops on the basis of the isochrone time PuT
    739
    Illustration 240: Classified display of stops on the basis of the isochrone number of transfers 740
    Illustration 241: Comparison of accessibility in PrT and PuT in a graphical view
    741
    Illustration 242: Comparison of accessibility in PrT and PuT in a list view
    741
    Illustration 243: Shortest path search between two nodes in PrT
    742
    Illustration 244: Graphical and tabular display of link volumes
    744
    Illustration 245: Example of a link list
    747
    Illustration 246: PrT path list
    750
    Illustration 247: Link bars with PrT volume
    753
    Illustration 248: Connector bars with PrT volume
    754
    Illustration 249: Two link bars with PrT and PuT volume
    754
    Illustration 250: Categorized link display according to link category
    755
    Illustration 251: Categorized link display according to saturation PrT
    755
    Illustration 252: Zone categorization according to origin traffic
    756
    Illustration 253: Link bar display categorized according to saturation PrT
    756
    Illustration 254: Table display of boarding passengers, transfers and alighting passengers
    at stops
    757
    Illustration 255: Number of residents and workplaces per zone
    758
    Illustration 256: Display of the mode selection as pie charts for zones
    759
    Illustration 257: Display of turn volumes
    760
    Illustration 258: Desire line with bars scaled at the demand between zones
    761
    Illustration 259: Desire line with bars classified according to the demand between zones
    762
    Illustration 260: Stop catchment areas with a large radius of 400m
    763
    Illustration 261: Stop catchment areas classified according to the number of departures
    764
    Illustration 262: Transfer relations between stop areas of a stop
    765
    Illustration 263: Transfers display of regular services
    766
    Illustration 264: Lane allocation in the network display
    767
    Illustration 265: Classified lane allocation according to the node volume
    767
    Illustration 266: Isochrone view
    769
    Illustration 267: Signal time-space diagram in mode "Flowing off"
    774
    Illustration 268: Signal time-space diagram in mode "Arterial bands"
    774
    Illustration 269: Column charts for time intervals
    775
    Illustration 270: Column chart for relations between network objects
    776
    Illustration 271: Tabular timetable in the standard view
    777
    Illustration 272: Tabular timetable in regular service mode
    778
    Illustration 273: Table background classified by revenue
    779
    Illustration 274: Graphical timetable with classified display of vehicle journey line style properties
    780
    Illustration 275: Item bars for vehicle journeys
    781
    Illustration 276: Classification of item bars with the vehicle journey volume
    782

    PTVGROUP

    793

    List of illustrations

    Illustration 277: Display of item bars for boarding passengers, through passengers and
    alighting passengers

    794

    783

    PTVGROUP

    List of tables

    List of tables
    Table 1: Additional attributes for a compared numerical attribute after version comparison
    Table 2: Definition of scenarios based on modifications
    Table 3: Extension of scenarios for a demand variant
    Table 4: Basic network objects of a transport network
    Table 5: PuT network objects of a transport network
    Table 6: General network objects
    Table 7: PrT transport systems properties
    Table 8: Flow hierarchy symbols
    Table 9: OD pairs in the example Example.ver
    Table 10: Example of three vehicle journeys
    Table 11: Input data for the calculation example
    Table 12: Calculation of indicators for the line route
    Table 13: Calculation of indicators for the links
    Table 14: Network objects of the junction model
    Table 15: Deriving projection factors for AP and AH
    Table 16: Example of the interaction of analysis time intervals and time series
    Table 17: Examples of input and output attributes at the link
    Table 18: Example of a 1..1 relation in the Visum network model
    Table 19: Example of a 0..1 relation in the Visum network model
    Table 20: Example of a 0..n relation with aggregate function Count
    Table 21: Example of a 0..n relation with aggregate function Min
    Table 22: Example of a 0..n relation with aggregate function Max
    Table 23: Example of a 0..n relation with aggregate function Sum
    Table 24: Example of a 0..n relation with aggregate function Avg
    Table 25: Example of a 0..n relation with aggregate function Concatenate
    Table 26: Example of a 0..n relation with aggregate function Histogram
    Table 27: Example of a 0..n relation with aggregate function Distinct
    Table 28: Saving the cost per kilometer to a user-defined attribute
    Table 29: Time-varying attributes and their allocation to assignment procedures
    Table 30: Impact of time-varying attributes in the Dynamic Stochastic assignment
    Table 31: Table Main nodes
    Table 32: Table Surfaces
    Table 33: Table Surface items
    Table 34: Table Faces
    Table 35: Table Face items
    Table 36: Table Edges
    Table 37: Table Points
    Table 38: Table Intermediate points
    Table 39: Examples of the normalization of surfaces
    Table 40: Demand object types in the EVA demand model
    Table 41: Properties of the demand strata in the EVA demand model
    Table 42: Zone attributes for the EVA demand model
    Table 43: Typical break-down of a demand stratum into 8 activities and 17 demand strata =
    activity pairs
    Table 44: Examples of relevant structural properties and person groups of the demand
    strata
    PTVGROUP

    25
    33
    33
    42
    45
    46
    48
    51
    58
    74
    80
    80
    80
    89
    100
    100
    104
    105
    105
    106
    107
    107
    108
    108
    109
    110
    112
    115
    117
    121
    121
    121
    122
    122
    123
    123
    123
    125
    142
    145
    146
    147
    148
    795

    List of tables

    152
    Table 45: Trip generation in EVA model: OD type 1
    Table 46: Trip generation in EVA model: OD type 2
    153
    Table 47: Trip generation in EVA model: OD type 3
    154
    Table 48: Explanation of variables and indexes used
    155
    Table 49: Example data for demand strata in an EVA model
    156
    Table 50: Example data for zone attributes in the EVA demand model (value of the structural
    properties)
    157
    Table 51: Example data for mobility rates in the EVA demand model
    157
    Table 52: Example data for production rates in the EVA demand model
    157
    Table 53: Sample computation of the production and attraction rates for the demand stratum
    HW
    158
    Table 54: Sample computation of the production and attraction rates for the demand stratum
    HO
    159
    Table 55: Sample computation of the production and attraction rates for the demand stratum
    WH
    160
    Table 56: Sample computation of the production and attraction rates for the demand stratum
    OH
    161
    Table 57: Sample computation of the production and attraction rates for the demand stratum
    OO (1)
    162
    Table 58: Sample computation of the production and attraction rates for the demand stratum
    OO (2)
    163
    Table 59: Sample computation for balancing (1)
    164
    Table 60: Sample computation for balancing (2)
    164
    Table 61: Zone attributes with results of trip generation of the EVA demand model
    165
    Table 62: Definition of the mode availability and capacity utilization according to the OD
    type
    167
    Table 63: Function types for evaluation
    168
    Table 64: Parameters of the evaluation function EVA1
    168
    Table 65: Parameters of the evaluation function EVA2
    170
    Table 66: Examples of activities and their structural properties
    175
    Table 67: Activity attributes in the tour-based model
    176
    Table 68: Attribute of an activity pair in the tour-based model
    176
    Table 69: List of the activity chains: mobility rates per person group in %
    177
    Table 70: Basic matrix
    203
    Table 71: Result matrix
    204
    Table 72: Abbreviations used in the User model PrT.
    228
    Table 73: Example network
    230
    Table 74: Link-based PrT paths of a PrT assignment
    231
    Table 75: Variables used in VD functions
    234
    Table 76: Parameters for all VD functions
    234
    Table 77: VD function type BPR2 - modified BPR
    235
    Table 78: VD function type BPR3 - modified BPR
    235
    Table 79: VD function type CONICAL (Spiess)
    235
    Table 80: VD function type CONICAL_MARGINAL
    236
    Table 81: VD function type EXPONENTIAL
    236
    Table 82: VD function type INRETS
    236
    Table 83: VD function types LOGISTIC, QUADRATIC, SIGMOIDAL_MMF_NODES,
    SIGMOIDAL_MMF_LINKS
    237

    796

    PTVGROUP

    List of tables

    Table 84: VD function type AKCELIK


    Table 85: VD function type AKCELIK2
    Table 86: VD function type LOHSE
    Table 87: VD function type Linear Bottleneck
    Table 88: Input data for link impedance calculation
    Table 89: Car travel times and speeds
    Table 90: HGV travel times and speeds
    Table 91: Calculation of link impedance for HGVs and cars
    Table 92: Advantages and disadvantages of the node impedance model
    Table 93: Attributes for impedance calculation based on turns VD function
    Table 94: Attributes for impedance calculation based on node VD function
    Table 95: Attributes for calculation of uncontrolled nodes
    Table 96: Input attributes for signalized nodes
    Table 97: Output attributes for signalized nodes
    Table 98: Input attributes for the calculation of two-way stops
    Table 99: Ranking of movements
    Table 100: Calculation of conflicting volumes
    Table 101: Base values for the critical gap
    Table 102: Follow-up times
    Table 103: Impeding movements
    Table 104: Allocation of a LOS to the mean delay per vehicle
    Table 105: Input attributes for an all-way stop node
    Table 106: Adjustment factors
    Table 107: Calculation of probability of degree of conflict
    Table 108: Excerpt of DOC table for two lanes per approach
    Table 109: Lookup table base follow-up time
    Table 110: Base values for the saturation follow-up time
    Table 111: Determining the LOS based on mean wait time per vehicle
    Table 112: Input attributes for roundabout nodes according to HCM 2010
    Table 113: LOS per lane based on the mean delay
    Table 114: Input attributes for calculation according to the TRL/Kimber method
    Table 115: LOS for calculation based on the mean delay, according to Kimber
    Table 116: Input attributes with an effect on signal coordination
    Table 117: Output attributes of links for results of signal coordination
    Table 118: Procedure parameters for signal coordination
    Table 119: PrT skims
    Table 120: Aggregation functions for skim data calculation
    Table 121: Parameters for distribution with variable beta in Illustration 1
    Table 122: Distribution for two alternatives with impedance 5 and 10
    Table 123: Distribution for two alternatives with impedance 105 and 110
    Table 124: Distribution for two alternatives with impedance 50 and 100
    Table 125: Model parameters
    Table 126: Example of incremental assignment (BPR function a=1, b=2, R=tCur)
    Table 127: Input attributes for incremental assignment
    Table 128: Output attributes of incremental assignment
    Table 129: Calculation of the user optimum for the example network
    Table 130: Calculation of the system optimum for the example network
    Table 131: Example network for equilibrium assignment

    PTVGROUP

    238
    238
    238
    239
    240
    240
    240
    240
    242
    243
    244
    246
    250
    251
    270
    271
    271
    273
    274
    275
    279
    281
    282
    282
    283
    284
    285
    287
    289
    292
    295
    298
    309
    310
    311
    312
    312
    334
    336
    336
    336
    336
    338
    340
    341
    342
    342
    344

    797

    List of tables

    Table 132: Assignment results for the three PrT paths


    Table 133: Assignment result at the links
    Table 134: Input attributes of equilibrium assignment
    Table 135: Output attributes of equilibrium assignment
    Table 136: Example equilibrium procedure (BPR function a=1, b=2)
    Table 137: Variants of route volumes for the link volumes in Illustration 1
    Table 138: Variants of route volumes for the link volumes in Illustration 2
    Table 139: Impedance in unloaded network, input parameters of Equilibrium_Lohse procedure
    Table 140: Example of Equilibrium_Lohse: 1st iteration step
    Table 141: Example of Equilibrium_Lohse: 2nd iteration step
    Table 142: Example of Equilibrium_Lohse: 3rd iteration step
    Table 143: Input attributes of the Equilibrium_Lohse procedure
    Table 144: Output attributes of the Equilibrium_Lohse procedure
    Table 145: Input attributes of assignment with ICA
    Table 146: Additionally calculated turn/main turn attributes for assignment with ICA
    Table 147: Additionally calculated link attributes for assignment with ICA
    Table 148: Input attributes for stochastic assignment
    Table 149: Output attributes for stochastic assignment
    Table 150: Impedance in unloaded network, input parameters for stochastic assignment
    Table 151: Calculation of commonality factor C for all route pairs
    Table 152: Volumes in the first internal iteration step m = 1
    Table 153: Volumes in the second internal iteration step m = 2
    Table 154: Input attributes for TRIBUT
    Table 155: Output attributes for TRIBUT
    Table 156: Toll amounts for the example network
    Table 157: Comparison of conventional toll assignment and TRIBUT
    Table 158: Input attributes for the DUE procedure
    Table 159: Input attributes for dynamic user equilibrium
    Table 160: Output attributes of the Dynamic user equilibrium
    Table 161: Input attributes of dynamic stochastic assignment
    Table 162: Output attributes of dynamic stochastic assignment
    Table 163: Calculation rules for the output attributes of assignment analysis
    Table 164: Demand matrix and temporal distribution of demand for the example
    Table 165: PuT supply of the example with connections from A-Village to X-City
    Table 166: Path legs after a timetable-based assignment (paths saved as connections)
    Table 167: Path legs after a timetable-based assignment (paths saved as connections)
    Table 168: Skims of time
    Table 169: Skims of length
    Table 170: Monetary skims [Currency units]
    Table 171: Skims of frequency
    Table 172: Skims of attribute data
    Table 173: Derived skims
    Table 174: Example of the connection skims of an OD pair
    Table 175: Availability of the skims in the PuT assignment procedures
    Table 176: Combination of skim data to the mean skim value per OD pair
    Table 177: Example for the determination of the time difference DT
    Table 178: Comparison of the impedance functions in the PuT assignments
    Table 179: Connector weights for the example
    798

    345
    345
    346
    347
    350
    364
    365
    367
    368
    369
    369
    372
    373
    378
    379
    380
    387
    388
    394
    395
    396
    396
    398
    399
    403
    404
    434
    437
    438
    442
    443
    448
    451
    453
    455
    456
    458
    459
    459
    460
    460
    463
    464
    465
    466
    468
    469
    470

    PTVGROUP

    List of tables

    470
    Table 180: Temporary demand matrix for the assignment in the example
    Table 181: Example for headway calculation from mean headway according to timetable
    475
    Table 182: Example for headway calculation from mean wait time according to timetable
    476
    Table 183: Considering elapsed wait time
    484
    Table 184: Travel times and headways of the lines in the example network
    490
    Table 185: Line shares and the mean costs depending on the information available
    491
    Table 186: Headway calculation for the example
    492
    Table 187: Impedance calculation for the routes in the example
    493
    Table 188: Changes to shares with variation of the transfer penalty
    494
    Table 189: Mean skim values for the headway-based assignment
    494
    Table 190: Calculation of the temporal distance
    505
    Table 191: Procedure parameters for the comparison of the distribution models
    2
    Table 192: Example 1 Initial situation
    509
    Table 193: Example 2 Isochronous, identical pair of connections
    509
    Table 194: Example 3 Identical pair of connections with high temporal proximity
    509
    Table 195: Example 4 Similar pair of connections with high temporal proximity (connection 3 now includes transfer)
    510
    Table 196: Example 5 - Differing pair of connections with moderate temporal proximity
    510
    Table 197: Result of connection search (transfer penalty 10 min, parameter file timetab1.par) 2
    Table 198: Temporal distances T and impedances R of the connections for the two analyzed intervals of travel demand
    511
    Table 199: Distribution of trips to the connections (Kirchhoff, = 3)
    512
    Table 200: Calculation rules for the attributes of the assignment analysis
    531
    Table 201: Status indicators for the surveyed path leg
    538
    Table 202: Status indicators for the preceding section
    539
    Table 203: Status indicators for the succeeding section
    540
    Table 204: Status indicators for the entire survey data record
    540
    Table 205: Level Territory x Transport system
    543
    Table 206: Indicators for line route analysis by territory
    544
    Table 207: Territory-based indicator data for transport performance and revenue analysis 545
    Table 208: Territory-based analysis on aggregation level Territory x Line
    546
    Table 209: Analysis of the Vol/Cap ratio of seats on the line route level
    547
    Table 210: Service kilometer analysis on the level of lines
    548
    Table 211: Cost and revenue computation on the level of lines
    549
    Table 212: Evaluation of transport performance indicators on the level of operators
    549
    Table 213: Evaluation of service kilometers per time interval for the bus operator
    551
    Table 214: PassengerKm-to-ServiceKm ratio for the Bus operator
    551
    Table 215: Example line block with pull-out trip, interlining trip and pull-in trip
    555
    Table 216: Block data of the three approaches
    559
    Table 217: Block items of the line blocks in block version 1
    561
    Table 218: Block items of the line blocks in block version 2
    563
    Table 219: Block items of the line blocks in block version 3
    565
    Table 220: Open block and closed block for the unsymmetrical example (Illustration 1)
    567
    Table 221: Block items of both blocks in the example Block items in the recurring rhythm
    were omitted for a better overview. Block 1 is open, block 2 is closed.
    568
    Table 222: Block version attributes
    570
    Table 223: Block attributes
    573
    Table 224: Block item attributes
    575

    PTVGROUP

    799

    List of tables

    575
    Table 225: Block item type attributes
    Table 226: Attributes of the line blocking cost function
    577
    Table 227: Depot attributes of stop points
    577
    Table 228: Cost rates for downtimes at depots and stop points based on vehicle unit (cost
    rates as listed in Table 1)
    578
    Table 229: Cost rates for downtimes at depots and stop points based on vehicle com578
    bination (cost rates as listed in Table 1)
    Table 230: Turn standard attributes with reference to running directions
    581
    Table 231: Turn attributes with reference to running directions
    581
    Table 232: Line route attributes with reference to running directions
    581
    Table 233: Objective function components for line blocking with vehicle interchange
    599
    Table 234: Line blocking and vehicle requirement indicators
    602
    Table 235: Example illustrating different variants of distribution of empty time and empty kilometers on individual vehicle journeys.
    604
    Table 236: PuT interlining matrix with t-PuTSys between stop points
    605
    Table 237: Fare stages for the example on distance-based fare
    610
    Table 238: Example network: Fare zones that have been traversed and fare
    612
    Table 239: Linking fare systems and demand segments
    619
    Table 240: Transport supply in Example_LLE.ver
    631
    Table 241: Projection factors for the valid days in Example_LLE.ver
    631
    Table 242: Projection factor for the demand segment
    631
    Table 243: Total capacity provided in the vehicles of example Example_LLE.ver
    631
    Table 244: Fare model in Example_LLE.ver
    632
    Table 245: Fares of the fare model in Example_LLE.ver
    632
    Table 246: Transport demand between the zones in Example_LLE.ver
    632
    Table 247: Cost rates for vehicles in Example_LLE.ver
    633
    Table 248: Indicators for line route and timetable evaluation
    638
    Table 249: Indicators of the transport supply
    641
    Table 250: Indicators of the network performance
    645
    Table 251: Vehicle type-dependent costs
    650
    Table 252: Infrastructure costs
    650
    Table 253: Total cost
    650
    Table 254: Cost rates for the vehicle units
    652
    Table 255: Cost rates for the vehicle combinations
    652
    Table 256: Distances and times for the vehicle combination Train in the analysis period
    652
    Table 257: Formulas for calculating link costs
    653
    Table 258: Example calculation for link depreciation costs
    654
    Table 259: Example calculation for running costs of links
    654
    Table 260: Example calculation for link utilization costs
    654
    Table 261: Formulas for the calculation of stop point costs
    656
    Table 262: Formulas for calculating operator costs
    657
    Table 263: Calculation example for depreciation costs of the operator
    658
    Table 264: Calculation example for the running costs of the operator
    658
    Table 265: Revenue indicators
    660
    Table 266: Revenue share per path leg
    661
    Table 267: Revenue per line
    661
    Table 268: Revenue share per path leg
    662
    Table 269: Revenue per line
    662

    800

    PTVGROUP

    List of tables

    Table 270: Calculation of the revenues per path (PuT routes)


    Table 271: Revenue calculation for the path leg Bus1
    Table 272: Aggregation of the path leg revenues to lines
    Table 273: Input data for the calculation example
    Table 274: Revenue distribution W-NumFP = 1.0, W-NumPL= 0.0, FixSuppl = 0
    Table 275: Revenue distribution W-NumFP = 0.5, W-NumPL = 0.5, FixSuppl = 0.00
    Table 276: Revenue distribution W-NumFP = 0.5, W-NumPL = 0.5, FixSuppl = 0.20
    Table 277: Indicators for the cost coverage calculation
    Table 278: Cost coverage calculation from revenues and costs
    Table 279: Which projection factor applies for the calculation of indicators?
    Table 280: Difference in the projection to AH for ServiceKm and PassengerKm
    Table 281: Further specifications for the vehicle journey with two VJ sections
    Table 282: Calculation of seat kilometers
    Table 283: Calculation of service kilometers
    Table 284: Link attributes for noise calculations
    Table 285: Pollutant-Emis link attributes
    Table 286: Reading shape files in Visum network objects
    Table 287: Illustration of Visum files of shape types
    Table 288: Calculating the number of PuT passengers per zone
    Table 289: Calculating the number of inhabitants in the catchment areas of lines
    Table 290: Calculating the number of inhabitants in the catchment areas of stops
    Table 291: Calculating the vehicle kilometers within territories
    Table 292: Calculating the zone number where a stop point lies
    Table 293: Determination of the numbers of the stops that lie within a zone
    Table 294: Calculating the average number of PuT passengers at the stops of a zone
    Table 295: Available aggregate functions for intersection
    Table 296: Planar coordinate system
    Table 297: Geographic coordinate system
    Table 298: Background formats supported by Visum
    Table 299: Example for a World file
    Table 300: Traffic type based on status (active / passive) of links or PuT lines
    Table 301: Significance of traffic types after applying path filter for active PuT lines
    Table 302: Territory lists
    Table 303: Stop lists
    Table 304: Item lists
    Table 305: Line lists
    Table 306: Line block lists
    Table 307: Evaluation lists for paths
    Table 308: Statistical evaluation lists

    PTVGROUP

    664
    666
    666
    667
    667
    667
    667
    669
    669
    670
    670
    672
    672
    673
    680
    684
    692
    695
    697
    698
    698
    699
    699
    700
    700
    702
    706
    706
    713
    714
    722
    724
    748
    749
    749
    749
    750
    751
    753

    801

    PTV VISUM 13
    USER MANUAL

    14 Basics of program operation

    14

    Basics of program operation


    This section of the documentation describes how to operate Visum. You can find basic information and background knowledge in the first section of the documentation (see Fundamentals: Chpt. 2 , page 15).
    Note: To operate the program, you will need a good working knowledge of Windows.
    Tip: For your first steps with Visum, you can use simple example data that can be installed with your Visum version. Once installed, you can find them under ...Users\Public\Public documents\PTV Vision\PTV Visum 13
    Subjects
    Program start and start screen
    Program interface
    Shortcuts and functions keys in Visum
    Opening and saving files
    Selecting the direction of traffic
    Specifying standard units for length and speed
    Specifying time periods and points in time
    Editing user preferences
    Displaying information about Visum
    Enabling or disabling installed add-ons
    Starting Visum with different settings
    Comparing and transferring versions and networks
    Scenario management

    14.1

    Program start and start screen


    To start Visum, simply double-click the Visum icon

    on your desktop.

    After Visum has been started, the start screen appears, providing detailed information on the
    program version:
    Number and size of the Visum version
    License expiration date
    Customer name
    Then the graphical user interface of the program is displayed.
    Note: You can specify how you want the graphical user interface displayed (see "Starting
    Visum with different settings" on page 887).
    Some settings in Visum are saved to the registry when the session is terminated and will
    be used automatically when the program is started again (see "Editing user preferences"
    on page 867).

    PTVGROUP

    803

    14.2 Program interface


    Tip: Further program information can be accessed via the Help> About menu and the
    Help> License menu (see "Displaying information about Visum" on page 885).

    14.2

    Program interface
    After the start screen, the program interface of Visum will appear during program start which
    includes any other windows. The Network editor window (see "Network editor window" on
    page 818) comes up with an empty network including a satellite image of the earth; depending
    on the settings, other windows may be open (see "Specifying the size and position of windows" on page 872). Then you can, for example, read a network version from file (see "Opening a version file" on page 840).
    Note: If you start Visum by double-clicking a version file in the Windows Explorer, the corresponding network version is immediately opened.

    Note: A separate window opens when you choose to work with lists, the timetable editor,
    the matrix editor, the procedure sequence, the signal time-space diagram, the junction
    editor, transfers display of regular services or a schematic line diagram (see "Other windows" on page 823).

    804

    PTVGROUP

    14.2 Program interface


    (1) Title bar
    Here, name and version number of the program are displayed as well as the name of the opened file and in brackets the name of the currently active window.
    (2) Menu bar
    Via the menus, you can call the program functions. The menus provided in the menu bar
    depend on the currently active window. The commands provided in the Edit menu depend on
    the currently selected object type.
    (3) Toolbars
    Via the tool bars, you can call the program functions. The toolbars displayed depend on the
    window that is currently active (see "Tool bars" on page 823).
    (4) Network window
    Here you select a processing mode and an object type. You can also enable or disable the
    graphical display of network object types or graphics object types and set filters per network
    object type. Additional functions are available via the context menu (see "Network window" on
    page 808).
    (5) Matrices window
    This window gives you an overview of your matrices and allows you to edit them (see "Matrices window" on page 810).
    (6) Marking window
    This window allows you to access network objects that refer to currently highlighted network
    objects (see "Marking window" on page 810).
    (7) Quick view window
    Here the attribute values are displayed for the currently highlighted network object. In the
    Quick view window, you can edit the attribute values of the highlighted network objects (see
    "Quick view window" on page 810).
    (8) Smart map window
    In small format, this window shows an overview of the total network (see "The Smart map window" on page 813). The section shown in the Network editor window is displayed as a rectangle (or as cross lines) in the Smart map window. The smart map provides quick access to a
    certain network section (see "Refreshing the view" on page 821).
    (9) Messages window
    This window shows messages, warnings and notes. Its list entries allow to quickly jump to the
    respective position in the Network editor window (see "Messages window" on page 883).
    (10) Network editor window
    The Network editor window shows the network currently open. Here you can adjust the display and edit the network graphically (see "Network editor window" on page 818 and "Editing
    the network" on page 957). Using the scrollbars, you can move the currently displayed network section horizontally or vertically.
    PTVGROUP

    805

    14.2.1 Working with windows


    (11) Tab bar
    With the window configuration Show as tabs, the tab bar shows all windows open. To open
    windows, you can also select them via a list box on the Windows toolbar (see "Toggling between windows" on page 828). To toggle between windows, click the respective tab.
    Tip: You can close a window by clicking the tab with the middle mouse button.
    (12) Graphics tools window
    You can use the Graphics tools window to work with the following interactive, graphical evaluation tools:
    Flow bundle (see "Displaying flow bundles" on page 2265)
    Turn volumes (see "Displaying turns, main turns, and turn volumes" on page 2435)
    Isochrones (see "Displaying isochrones and the accessibility of network objects" on page
    2278)
    Shortest path search (see "Searching for and displaying shortest paths" on page 2291)
    Desire line (see "Displaying desire lines" on page 2429)
    Paths projection (see "Projecting PrT path volumes" on page 1833)
    (13) Status bar
    The status bar contains various data:
    Details on the highlighted network object, if only a single network object is highlighted
    Number of highlighted network objects, if several network objects have been highlighted
    Commands for network processing steps
    Network scale (see "Editing the network scale" on page 2209)
    Coordinates of the pointer in the network

    14.2.1

    Working with windows


    There are different ways to arrange, sort, and dock windows together:
    Arranging windows via the toolbar
    Moving windows
    Docking windows together
    Removing window docking

    14.2.1.1

    Arranging windows via the toolbar


    Note: The following functions are provided for all windows shown in the list of the Windows toolbar (see "Tool bars" on page 823). They are not available for the following windows: Network, Quick view, Matrices, Marking, Protocol, Find and Smart map.
    Currently open windows you can place clearly laid out on screen.
    In the Windows tool bar click the desired icon.

    806

    PTVGROUP

    14.2.1.2 Moving windows


    Icon

    Name

    Description

    Arrange windows as
    tabs

    This toolbar button allows you to arrange all open


    windows as tabs, similar to sheets in Microsoft Excel.
    A tab bar is created at the bottom of the window. The
    windows appear in the order given by opening them
    one by one. Click a tab to move its corresponding
    window to the foreground.

    Arrange windows horizontally

    Via this icon you can call the display of all of the
    open windows one below the other. The windows
    appear in the order given by opening them one by
    one.

    Arrange windows vertically

    Via this icon you can call the display of all of the
    open windows side by side. The windows appear in
    the order given by opening them one by one.

    The windows are rearranged accordingly.


    Tip: Alternatively, from the Windows menu (top), choose View> Window configuration to
    arrange your windows.
    14.2.1.2

    Moving windows
    You can move all windows independently of the program window. You can also move them to
    a second screen.
    1. Click the title bar or tab of the window and hold down the mouse button and the C TRL key.
    Then drag the window to the position of your choice.
    2. Release the mouse button and key.
    The window is moved the position of your choice. If the window contains other tabs with open
    windows, they are moved as well.
    Note: When you move a window without pressing the C TRL key, the window anchoring
    symbol is displayed (see "Docking windows together" on page 807).

    14.2.1.3

    Docking windows together


    You can dock windows together to form groups that you can move as you like. Visum provides
    optical aids to assist you. A symbol and shaded background show you where you can dock
    windows.
    1. Click the title bar or tab of the window and hold down the mouse button.
    When you move the cursor, a symbol is displayed that shows you your window anchoring
    options.

    PTVGROUP

    807

    14.2.1.4 Removing window docking


    Element

    Description
    You can dock the window in your target window at each of its four
    borders. To additionally dock it as a tab, point the cursor to the
    middle of the symbol.

    You can dock the window in your target window at its top border.
    You can dock the window in your target window at its bottom border.
    You can dock the window in your target window at its left border.
    You can dock the window in your target window at its right border.

    2. Drag the mouse pointer to the symbol of your choice.


    The desired target area is shaded in color.
    3. Release the mouse button.
    Note: Important is to where you drag the mouse pointer, not the window.
    The window is placed at the desired position in the target window.
    14.2.1.4

    Removing window docking


    You can remove the docking of windows.
    1. Click the title bar or tab of the window and hold down the mouse button.
    2. Drag the mouse pointer to the desired position on your desktop. then release the mouse
    button.
    The docking is removed.

    14.2.2

    Network window
    The Network tab contains a list of object types - network objects are listed in the top section
    and graphical objects in the bottom section (see "Network object types" on page 958 and
    "Inserting additional information in the network display" on page 2232). Here, you can call multiple functions for display and selection of objects in the network and for network processing as
    well.
    Notes: Some object types are only available if the respective add-on has been activated
    (see "Enabling or disabling installed add-ons" on page 886).
    You can customize the display of object types (see "Customizing the Network window"
    on page 809)

    808

    PTVGROUP

    14.2.2 Network window

    (1) Tool bar


    Via these icons you choose the operating mode for further network processing (see "The operating modes of the network model" on page 996).
    (2) Object icon by object type
    Use this icon to enable or disable the graphical display of objects of a particular object type in
    the network (see "Editing the display and order of drawing settings for graphic layers" on page
    2339).
    (3) Filter icon by network object type
    Use this icon to enable or disable the network type-specific filter (see "Switching filters on or
    off" on page 1022).
    (4) Button labeled by object type name
    Use this button to select the object type you either want to create a new object for or to edit or
    to mark one or multiple objects of this type. Right-click to call more processing functions for the
    selected object type. Mouse-over on the labeled button calls a quick info displaying both, the
    total number of objects of this type and for network objects the number of currently active
    objects of this type.
    (5) Spatial selection settings by network object type
    A red dot indicates that currently objects of this network object type are passive according to
    the current spatial selection. The per network object type checkbox is only displayed if the spatial selection mode has been enabled. Use this check box to activate the particular network
    object type for spatial selection (see "Selecting network object types for the spatial selection
    mode" on page 1034).
    Customizing the Network window
    You can define the object types that are listed in the Network window. In case of projects in
    the field of private transport, for example, you can disable the entire network objects required
    for public transport network modeling. Or you can, for example, disable the graphics object
    type Backgrounds, if you do not want to use background files (see "Network object types" on
    page 958 and "Inserting additional information in the network display" on page 2232).
    Notes: Some object types are only available if the respective add-on has been activated
    (see "Enabling or disabling installed add-ons" on page 886).
    1. From the View menu, choose Configuration Network window.

    PTVGROUP

    809

    14.2.3 Marking window


    The Network objects configuration window opens.
    2. In the Visible column, select the network and graphics object types you want to show in the
    Network window.
    Tip: Click the Check all or Uncheck all button to check or uncheck all of the network
    and graphics object types at the same time.
    3. Confirm with OK.
    The selected network and/or graphics object types are shown in the Network window.
    Note: This configuration is saved to the Registry when the Visum session is terminated
    and will be used automatically when the program is started again.

    14.2.3

    Marking window
    The Marking window shows all currently selected network objects, including their related
    objects. Related objects are network objects which refer to a network object in the network
    model.
    Note: You can find the relations between network object types in the Attributes.xls file,
    under ...Program files\PTV Vision\PTV Visum 13\Doc (Relation tab) (see "Accessing attributes" on page 963).

    Using the navigator and icons, you can quickly access network objects to highlight or edit
    them (see "Accessing associated objects in the View menu" on page 1005).

    14.2.4

    Matrices window
    The Matrices window contains a navigator with the matrices available in the respective version (see "Matrices overview" on page 1715).

    14.2.5

    Quick view window


    The Quick view window contains a selection of attributes and attribute values of the currently
    selected object/s. Here you can directly edit the attribute values of marked objects (see "Modifying attribute values in the Quick view" on page 995).
    You can select the attributes to be displayed (see "Selecting attributes for the Quick view display" on page 811). Additionally you can change various display properties (see "Editing
    Quick view settings" on page 812).

    810

    PTVGROUP

    14.2.5.1 Selecting attributes for the Quick view display


    The tool bar of the Quick view window provides the following icons.
    Icon

    Name

    Description

    Attribute
    selection

    Selection of the attributes you want to display in the Quick view window (see "Selecting attributes for the Quick view display" on page
    811).

    Copy attri- Copy displayed input attribute values (except IDs) to Clipboard (see
    butes
    "Copying attribute values to the clipboard" on page 993).
    Note
    This functionality is only provided as long as just a single network
    object has been marked.
    Paste attri- Assign the attribute values from the Clipboard to the currently selecbutes
    ted number of network objects. The network objects do not have to
    be of the same network object type (see "Pasting attribute values
    from the clipboard" on page 994).
    Open
    Quick
    view layout

    Opens a Quickview layout file (see "Opening the Quick view layout"
    on page 813)

    Save
    Quick
    view layout

    Saves a Quickview layout file (see "Saving Quick view layout" on


    page 813)

    The top entry <Network object type> and a number indicate how many objects of this network
    object type are currently selected.
    Note: Different attribute values of several marked objects will be indicated by the * sign in
    the particular row, if the aggregate function Compare is selected. To e.g. calculate the
    total length of all links selected in the Network editor window, in the Quickview window,
    choose the aggregate function Sum (see "Editing the display properties of attributes" on
    page 970).
    You can customize position, size, and visibility of the Quickview window (see "Modifying toolbars and windows" on page 824).
    14.2.5.1

    Selecting attributes for the Quick view display


    You can decide by object type which of the attributes are to be displayed in the Quick view window.
    1. In the Network window, click the object type of your choice.
    2. In the Quick view window, click the

    Attribute selection icon.

    The Attribute selection (<Network object>) window opens.

    PTVGROUP

    811

    14.2.5.2 Editing Quick view settings


    3. Make the desired settings (see "The window used for the selection of multiple attributes" on
    page 968).
    4. Confirm with OK.
    The attributes selected and their values are displayed in the Quick view window, in the units
    and sequence specified.
    Note: When the session is terminated, the attribute selection of the Quick view window is
    saved in a *.qla file for all objects. This file will be opened automatically when Visum is
    started next time. You can choose where to save this file (see "Editing the storage location of files" on page 837).
    14.2.5.2

    Editing Quick view settings


    You can edit various settings for the Quick view.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> Quick view.
    3. Make the desired changes.

    812

    Element

    Description

    Fonts for quick


    view

    Select font
    Use the button to select a font, style and font size in a separate window for the quick view.
    Notes
    The button shows the currently selected font in parentheses.
    You can reset the font to the Visum standard setting (see "Resetting
    fonts" on page 828).

    Row labels

    Here you can specify whether the attributes are displayed as short
    names or as long names.

    Miscellaneous

    Extended input options


    If this option has been selected, you have the following input options:
    Logical values are controlled via activated/deactivated check
    boxes, for example Use automatic link orientation.
    The values of a set can be edited in drop-down lists, for example Control type.
    Values of a set of which you can select multiple items, are displayed as buttons labeled with the current selection. They open
    a new window. In the window, you can select multiple items, for
    example TSysSet.

    PTVGROUP

    14.2.5.3 Saving Quick view layout


    Element

    Description
    Values for user-defined attributes of type File are displayed as button, which are labeled with the name of the selected file. The button
    opens the Open file window, where you can make a new selection.

    4. Confirm with OK.


    The Quick view is displayed with the selected settings.
    14.2.5.3

    Saving Quick view layout


    You can save your layout settings to a *.qla file to access them again later. The Network editor window shows the attributes, aggregation functions and width of the attribute column in the
    layout file for all network object types. By default, the Quick view standard layout is saved to
    your user directory. You can save layout files to the storage location of your choice, e.g. to project directories.
    1. Open the Quick view window.
    2. Make the desired settings (see "Quick view window" on page 810).
    3. In the Quick view window, click the

    Save quickview layout icon.

    The Save Quickview layout window opens.


    Tip: Alternatively, from the File menu, choose Save as> Quickview layout.
    4. Select the desired directory and enter the desired file name.
    5. Confirm with OK.
    The file is saved.
    14.2.5.4

    Opening the Quick view layout


    You can load a Quick view layout file *.qla into your network.
    1. Open the Quick view window.
    2. In the Quick view window, click the

    Open quickview layout icon.

    The Open Quickview layout window opens.


    Tip: Alternatively, from the File menu, choose Open> Quickview layout.
    3. Open the desired file.
    4. Confirm with OK.
    The file is opened.

    14.2.6

    The Smart map window


    Note: To open the menu Smart map window, from the View menu, choose Smart map.

    PTVGROUP

    813

    14.2.6.1 Refreshing the Smart map


    In a small format, the Smart map window provides an overview of the network. A red rectangle
    indicates the network section currently displayed in the Network editor window. If the zoom
    factor used in the Network editor window is too high to display the section as a rectangle in
    the Smart map, the section is displayed as cross hairs instead.

    The Smart map view depends on the Network editor view. Changes made to the Network
    editor view affect the Smart map view and vice versa. For instance, if you zoom into the network or move the current view, the position of the rectangle or cross hairs is moved in the
    Smart map as well. To change the network view, change the position or size of the red rectangle in the Smart map.
    By default, the graphic parameters set for network display are used for Smart map display.
    Optionally, you can set specific graphic parameters for the Smart map which can be saved to
    file and read from file again.
    You can customize the position, size, and visibility of the Smart map window (see "Modifying
    toolbars and windows" on page 824).
    14.2.6.1

    Refreshing the Smart map


    By default, the Smart map is updated automatically. Nevertheless, you can manually refresh
    the display at any time.
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Select the Refresh command.
    The Smart map is updated.

    14.2.6.2

    Moving the Network editor view


    To move the view shown in the Network editor, move the red rectangle in the Smart map.
    1. In the Smart map window, place the pointer inside of the red rectangle.
    The pointer appears as a cross with arrow heads.
    2. Hold down the mouse button.
    3. Drag the rectangle to the position of your choice and release the mouse button.
    The network window view is adjusted according to the Smart map.

    814

    PTVGROUP

    14.2.6.3 Enlarging and reducing the view of the Network editor window
    14.2.6.3

    Enlarging and reducing the view of the Network editor window


    To enlarge or reduce the Network editor view, in the Smart map window, change the rectangle size.
    1. In the Smart map window, place the pointer inside of the red rectangle.
    The mouse pointer turns into a double-arrow.
    2. Hold down the mouse button.
    3. Then drag the rectangle to the size you want and release the mouse button.
    The network window view is adjusted according to the Smart map.

    14.2.6.4

    Specifying a new view of the Network editor window


    To define a new view of the Network editor window, in the Smart map window, drag open a
    new rectangle.
    1. In the Smart map window, place the pointer outside the red rectangle.
    The mouse pointer turns into a magnifying glass with a plus sign in it.
    2. In the Smart map window, click where you want to position the top left corner of your new
    section and hold down the mouse button.
    Tip: If the new position is within the red rectangle, hold down the CTRL key.
    3. Then drag the rectangle to the size you want and release the mouse button.
    The network window view is adjusted according to the Smart map.

    14.2.6.5

    Enlarging or reducing the Smart map view (zoom)


    For a bigger or smaller network display in the Smart map, you can zoom in or zoom out.
    Note: This will not change the view in the Network editor window.
    Reducing the display (zoom out)
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Select the Zoom out entry.
    Tip: Alternatively you can use the PAGE UP key.
    The display in the Smart map window is reduced by factor 2.0.
    Enlarging the display (zoom in)
    1. Right-click in the Smart map window.
    A shortcut menu opens.

    PTVGROUP

    815

    14.2.6.6 Shifting view in the Smart map


    2. Select the Zoom in entry.
    Tip: Alternatively you can use the PAGE DOWN key.
    The display in the Smart map window is enlarged by factor 2.0.
    Showing the entire network in the Smart map window
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Select the Display entire network entry.
    Tip: Alternatively you can use the H OME key.
    In the Smart map window, the entire network is displayed. The red rectangle is adjusted according to the network section shown in the Network editor window.
    Centering the window section of the Network editor in the Smart map
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Click Center.
    In the Smart map window, the view is moved so that the red rectangle, i.e. the current window
    section in the Network editor is centered.
    14.2.6.6

    Shifting view in the Smart map


    1. Click in the Smart map window.
    2. Press one of the arrow keys.
    The view in the Smart map window is shifted.

    14.2.6.7

    Setting the graphic parameters for the Smart map window


    By default, the network in the Smart map window is displayed the same way as in the Network editor window. If applicable, you can edit these graphic parameter settings.
    Editing graphic parameters for Smart map display
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    3. Make the desired settings (see "Specifying basic settings for the network window" on page
    2337).

    816

    PTVGROUP

    14.2.6.7 Setting the graphic parameters for the Smart map window
    Note: This window provides the same graphic parameters as for the Network editor
    window. Some of the parameters, for example the color for marked objects, do not
    apply to the Smart map display, since markings are not highlighted in the Smart map.
    4. Confirm with OK.
    The network display in the Smart map window is adjusted accordingly. These settings are
    saved with the version file.
    Saving graphic parameters for Smart map display
    Current graphic parameter settings for Smart map display you can save to a graphic parameter file.
    Note: For the Smart map, graphic parameters are saved as *.gpa file.
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Select the Save graphic parameters entry.
    The Save graphic parameter file window opens.
    3. Select the desired directory and enter the desired file name.
    4. Click the Save button.
    The current graphic parameter settings are saved to file.
    Saving graphic parameters for Smart map display
    For the Smart map, you can read graphic parameter settings from file.
    Note: For the Smart map, graphic parameters are saved as *.gpa file.
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Select the Open graphic parameters entry.
    The Open graphic parameter file window opens.
    3. Open the desired file.
    4. Click the Open button.
    For the Smart map, the graphic parameter settings are read from file.
    Applying the graphic parameters set for network display
    You can use the graphic parameter settings of the Network editor window for the Smart map.
    1. Right-click in the Smart map window.
    A shortcut menu opens.
    2. Choose Graphic parameters from network view.
    PTVGROUP

    817

    14.2.7 Network editor window


    The current graphic parameter settings of the Network editor window are adopted for the
    Smart map. Subsequent changes made to the graphic parameters of the Network editor window will change the graphic parameters set for Smart map accordingly. Refresh the Smart
    map display, if necessary (see "Refreshing the Smart map" on page 814).

    14.2.7

    Network editor window


    The Network editor window is opened by default when you start the program. In the Network
    editor window, the network currently open is displayed graphically (see "Displaying data
    graphically and in lists" on page 2299). Here, you can select and edit network objects (see
    "Editing the network" on page 957). The current editing option is displayed in the window title
    bar.
    You can specify which network section you want to show in the Network editor window. Furthermore, you can refresh the display. If you have defined multiple analysis time intervals, you
    can switch from one interval to another. This way changes to attribute values over time
    become obvious.
    Note: The Network editor display and the Smart map display are coupled (see "The
    Smart map window" on page 813). If you change the section in the Network editor window, this will change the position of the red rectangle or cross hairs in the Smart Map
    window and vice versa.

    14.2.7.1

    Scaled display
    1. In the View menu, select the Zoom entry.
    The Zoom window opens.
    2. Select the Zoom to scale 1 : option.
    3. Enter the desired value.
    4. Confirm with OK.
    The view is displayed with the desired scale.

    14.2.7.2

    Enlarging the view (zooming in)


    Tip: You can also use the SmartMap to change the view in the Network editor window
    (see "Enlarging and reducing the view of the Network editor window" on page 815).
    Enlarging the view to a certain section
    1. On the View toolbar, click the

    Set window section icon.

    The pointer appears as magnifier.


    Tip: Alternatively, from the View menu, choose > Set window section or press the Z
    key.

    818

    PTVGROUP

    14.2.7.3 Reducing the view (zooming out)


    2. In the network display, click the position where you would like to start drawing the enlarged
    section and keep the left mouse button pressed.
    3. Drag the pointer to the opposite corner and release the mouse button when the desired
    size has been reached.
    The view is enlarged to the dimensions of the selected section. The mouse pointer is reset to
    standard display.
    Enlarging the view by a certain factor
    1. In the View menu, select the Zoom entry.
    The Zoom window opens.
    2. Select the Zoom by factor option.
    3. Enter a factor > 1.
    4. Confirm with OK.
    The view will be enlarged by the user-defined factor.
    Enlarging the view with the help of the scroll wheel
    1. Click into the Network editor window.
    2. Move the scroll wheel forward.
    The view is enlarged, the mouse pointer remains in focus.
    Note: Hold down the C TRL key and rotate the mouse wheel to enlarge the view and keep
    the center in focus.
    Tip: Alternatively, you can enlarge the view by pressing the PAGE UP key.
    14.2.7.3

    Reducing the view (zooming out)


    On the View toolbar, click the

    Reduce window section icon.

    The section is minimized.


    Tips: Alternatively, to minimize the view, from the View menu, choose > Reduce window
    section or press the PAGE DOWN key.
    You can also use the SmartMap to change the view in the Network editor window (see
    "Enlarging and reducing the view of the Network editor window" on page 815).
    Reducing the view by a certain factor
    1. In the View menu, select the Zoom entry.
    The Zoom window opens.
    2. Select the Zoom by factor option.
    PTVGROUP

    819

    14.2.7.4 Displaying the entire network


    3. Enter a factor < 1.
    4. Confirm with OK.
    The view will be reduced by the user-defined factor.
    Reducing the view with the help of the scroll wheel
    1. Click into the Network editor window.
    2. Move the scroll wheel backwards.
    The view is reduced, the mouse pointer remains in focus.
    Note: Hold down the C TRL key and rotate the mouse wheel to reduce the view and keep
    the center in focus.
    14.2.7.4

    Displaying the entire network


    On the View toolbar, click the

    Display entire network icon.

    The overall network is displayed in the Network editor window.


    Tip: Alternatively, to display the whole network, from the View menu, choose> Display
    entire network or press the H OME key.
    14.2.7.5

    Shifting the view


    1. On the View toolbar, click the

    Shift window section mode icon.

    The pointer is displayed as a hand. You have switched to the shift view mode.
    Tips: Alternatively, you can temporarily switch to the shift mode. To do so, hold down
    the space bar, the middle mouse button or the mouse wheel.
    You can also switch to the Shift window section mode when moving a network
    object in the network. To do so, hold down the space bar while moving the network
    object.
    2. Click any position in the network and hold down the mouse button.
    3. Drag the view to the position of your choice and release the mouse button.
    The view is shifted.
    4. In the View tool bar, click the

    Shift window section mode icon to disable this mode.

    The mouse pointer is reset to standard display.


    Note: Only the display is shifted, the network itself is not. Coordinates remain unchanged.

    820

    PTVGROUP

    14.2.7.6 Refreshing the view


    Tips: Alternatively, you have these possibilities to shift the view:
    Press an arrow key on your keyboard. If you keep the Shift key pressed at the same
    time, you increase the shift movement.
    Use the scrollbars of the Network editor window.
    You can also shift the view in the network window with the help of the Smart map (see
    "Moving the Network editor view" on page 814).
    14.2.7.6

    Refreshing the view


    Sometimes it might happen that your changes to the network are not displayed right away. In
    this case you should refresh the view.
    In the View tool bar, click the

    Refresh icon.

    The display is refreshed.


    Tip: Alternatively, you can refresh the display via menu View> Refresh.
    14.2.7.7

    Displaying previous views


    After changes to the view you can call previous views one by one for display. When you are
    showing a previous view, you can scroll forward to the following view again.
    1. On the View toolbar, click the

    Previous window section icon.

    The previous view is displayed.


    Tip: Alternatively, from the View menu, choose > Previous window section or press
    ALT + LEFT ARROW to switch to the previous view.
    2. On the View toolbar, click the

    Next window section icon.

    The next view is displayed.


    Tip: Alternatively, use the View> Next window section menu or press ALT + RIGHT
    ARROW to switch to the next view.
    14.2.7.8

    View by analysis time interval


    If analysis time intervals have been defined (see "Defining analysis time intervals" on page
    1861), for each analysis time interval, you can graphically display the attribute values which
    have changed over time. In the network display each analysis time interval corresponds to a
    view. You can browse through these views in both directions, either automatically or by hand.
    Note: For a display of time-varying attribute values, you need to set the required graphic
    parameters (see "Specifying basic settings for the network window" on page 2337).

    PTVGROUP

    821

    14.2.8 The Graphics tools window


    1. From the View menu, choose> Toolbars> Analysis time intervals. Then select Visible or
    Automatic.
    Note: Choose Automatic to show the Analysis time intervals toolbar, which is displayed if you have defined analysis time intervals.
    2. On the Analysis time intervals toolbar, select the analysis time interval you want to display.
    The view referring to the selected analysis time interval is displayed.
    3. On the Analysis time intervals toolbar, click the icon of your choice.
    Icon

    Name

    Description

    Start the animation of Switch to the particular previous interval every 2


    the analysis time
    seconds, until next interaction
    intervals (backward)
    Previous analysis
    time interval (single
    step)

    Switch from current to previous interval

    Next analysis time


    interval (single step)

    Switch from current to next interval

    Start the animation of Switch to the particular next interval every 2 seconds,
    the analysis time
    until next interaction
    intervals (forward)
    Stop the animation

    Terminate automatic switching

    The corresponding view is displayed.

    14.2.8

    The Graphics tools window


    The Graphics tools window contains tools for graphical display and interactive evaluation. In
    the window, you can specify settings for each graphics tool.

    822

    Element

    Description

    Flow bundle

    (see "Displaying flow bundles" on page 2265)

    Turn volumes

    (see "Displaying turns, main turns, and turn volumes" on page 2435)

    Isochrones

    (see "Displaying isochrones and the accessibility of network objects"


    on page 2278)

    Shortest path
    search

    (see "Searching for and displaying shortest paths" on page 2291)

    Desire line

    (see "Displaying desire lines" on page 2429)

    Paths projection

    (see "Projecting PrT path volumes" on page 1833)

    PTVGROUP

    14.2.8.1 Showing the Graphics tools window


    14.2.8.1

    Showing the Graphics tools window


    From the View menu, chose Graphics tools.
    The Graphics tools window opens, and all graphics tools available are displayed. Click a
    graphics tool to open its section where you can specify settings for it.
    Tip: Alternatively, from the Graphics menu, choose the desired entry. The Graphics
    tools window opens, showing the settings of the graphics tool selected.

    14.2.9

    Other windows
    A separate window opens when you choose to work with lists, the timetable editor, the matrix
    editor, the procedure sequence, the signal time-space diagram, the junction editor, transfers
    display of regular services or a schematic line diagram.
    List window (see "Working with lists" on page 2299)
    Junction editor window (see "Using the Junction editor" on page 1435)
    Timetable editor window (see "The Timetable editor window" on page 1530)
    Matrix editor window (see "The Matrix editor window" on page 1717)
    Procedure sequence window (see "Opening the procedure sequence" on page 1847)
    Signal time-space diagram window (see "Displaying signal time-space diagrams" on
    page 2479)
    Transfers display of regular services (see "Displaying connections and transfer flows at
    stops" on page 2392)
    Schematic line diagram window (see "Creating schematic line diagrams" on page 2451)

    14.2.10 Tool bars


    Via the tool bars, you can call the program functions. It depends on the currently active window
    which of the tool bars are displayed. The program interface provides the following toolbars:
    Functions, Windows, Analysis time intervals. The Network editor window includes the toolbars Graphic parameters , Spatial selection and View. The Spatial selection toolbar is only
    displayed if the Spatial selection mode is selected (see "Setting network objects active/passive via the spatial selection" on page 1033).
    Toolbars of the pro- Description
    gram interface
    Functions
    New, Open, Save version, Undo, Start procedure sequence, Open
    info window
    Windows
    Change alignment of windows (see "Restoring window settings" on
    page 827), open another window

    PTVGROUP

    823

    14.2.11 Modifying toolbars and windows


    Toolbars of the pro- Description
    gram interface
    Analysis time intervals
    In the Network editor window, show data of a different analysis
    time interval (see "View by analysis time interval" on page 821)

    Toolbars of the
    Network editor
    window
    Graphic parameters

    Description

    Find, Edit legend (see "Creating legends" on page 2255), Settings for
    graphical display (see "Marking active and passive network objects"
    on page 1004 and "Displaying data graphically and in lists" on page
    2299), Print (see "Printing the network display" on page 2499), Save
    screenshot (see "Exporting screenshots" on page 2663), Show or
    hide layer background map (see "Dynamically embedding background maps provided on the Internet " on page 2237).

    Spatial selection
    Definition of active and passive network objects by spatial selection
    (see "Setting network objects active/passive via the spatial selection"
    on page 1033)
    View
    Editing the view in the Network editor window (see "Network editor
    window" on page 818)

    Tip: You can customize the position and visibility of the toolbars (see "Modifying toolbars
    and windows" on page 824).

    14.2.11 Modifying toolbars and windows


    You can customize toolbars and windows individually, e.g. change their position. Furthermore,
    default settings can be restored for windows and tool bars.
    Note: This configuration is saved to the Registry when the Visum session is terminated
    and will be used automatically when the program is started again.
    14.2.11.1 Shifting tool bars
    You can move toolbars within their program section.
    1. Click the toolbar handle

    and hold down the mouse button.

    2. Drag the tool bar to the desired position and release the left mouse button.
    824

    PTVGROUP

    14.2.11.2 Moving the windows Network, Marking, Matrices, Quick view, Protocol, Smart Map
    and Find/Shift network object
    The tool bar is shifted.
    14.2.11.2 Moving the windows Network, Marking, Matrices, Quick view, Protocol, Smart Map and Find/Shift network object
    1. Click the header of the window and hold the mouse button down.
    2. Drag the window to the desired position and release the left mouse button.
    The window is shifted.
    14.2.11.3 Scaling windows
    You can change the width and height of a window.
    1. Move the mouse pointer to the edge of a window.
    The mouse pointer turns into a double-arrow.
    2. Hold down the mouse button.
    3. Drag the edge until the intended width or height has been reached and release the mouse
    button.
    Window width and/or height are changed.
    Note: If you have scaled the window width to where the toolbars are not completely
    shown, at the end of the respective toolbar, click the

    symbol, to show its hidden icons.

    14.2.11.4 Showing and hiding windows and toolbars


    You can show or hide the toolbars Functions , Windows, Analysis time intervals and the windows Network editor , Network, Marking, Matrices, Quick view, Protocol, Smart Map and
    Find a network object.
    Note: The Spatial selection toolbar is only displayed if the Spatial selection mode is
    selected (see "Setting network objects active/passive via the spatial selection" on page
    1033).
    Under menu View> Tool bars, select the desired entry.
    The selected tool bar or window is hidden or shown.
    Tip: To hide a window, you can also click the X top right in the title bar.
    14.2.11.5 Hiding a window temporarily
    Notes: This function is available for the windows Network, Quick view, Matrices, Marking and Smart map.
    To hide a window, in its title bar, click the

    PTVGROUP

    symbol.

    825

    14.2.11.5 Hiding a window temporarily


    The window is faded out. A tab labeled with the name of the hidden window appears in the left
    margin of the window.
    Note: If the window you want to hide has other windows docked to it as tabs, the other
    windows are also hidden.

    Temporarily displaying hidden windows


    1. Place the pointer on the tab created for the hidden window.
    The window is shown temporarily.

    Note: Clicking in the network display will hide the temporarily displayed window
    again.
    2. In the title bar of the window you want to show, click the

    symbol.

    The window is shown permanently.


    Note: If you choose to show a window permanently, all other temporarily hidden windows
    are also shown.

    826

    PTVGROUP

    14.2.11.6 Restoring window settings


    14.2.11.6 Restoring window settings
    You can reset these settings:
    Window size
    Position in the graphical user interface
    Layout of lists in windows
    Restoring window positions
    You can restore the default setting of windows.
    From the View menu, choose Window configuration> Reset all.
    The default position of windows is restored according the Visum default settings.
    Tip: Alternatively, to restore the window settings, from the Edit menu, choose > User
    Preferences> GUI> General. Then click the Reset window configuration button.
    Resetting the position and size of windows
    You can change the size and the position of some windows, e.g. of the Edit project directories window (menu File> Project directories > Edit project directories ). You can reset
    those windows to their default position (centered on screen) and to their default size.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> General.
    3. Click the Reset dialog positions button.
    4. Confirm with OK.
    The windows are reset to their default position and size.
    Resetting the layout of lists in windows
    Some windows in Visum contain lists, e.g. windows you can open via the Network window. In
    these lists, you can change the columns width, for example for better readability of listed data.
    You can discard such settings by resetting the lists to their default layout.
    Note: This function does not affect list windows (see "Working with lists" on page 2299).
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> General.
    3. Click the Reset grid settings button.
    4. Confirm with OK.
    The lists are reset to their default layout.

    PTVGROUP

    827

    14.2.12 Toggling between windows


    Resetting the window configuration
    You can restore the window configuration settings (see "Specifying the size and position of
    windows" on page 872).
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> General.
    3. Click the Reset window configuration button.
    4. Confirm with OK.
    The setting is reset.
    Resetting fonts
    In the Quick view window, in lists and in the junction editor you can reset the fonts to the
    Visum standard setting.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> General.
    3. Click the Reset fonts button.
    4. Confirm with OK.
    The fonts are reset to the Visum standard setting.
    Resetting all settings at the same time
    You can restore the following settings simultaneously: toolbar settings, the size, view and position of the Network, Quick view, Matrices, Marking, Protocol, Find, and Smart Map windows,
    their fonts and list layout.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> General.
    3. Click the Reset all button.
    4. Confirm with OK.
    All toolbars, the Network, Quick view, Matrices, Marking, Protocol, Find, and Smart Map window as well as their list layout are restored to the default settings.

    14.2.12 Toggling between windows


    In case you have opened several windows you can toggle between the open windows and
    place another window on top.
    In the Windows tool bar, select the desired window from the selection list, for example List
    (Zones).

    828

    PTVGROUP

    14.3 Shortcuts and functions keys in Visum

    The selected window is displayed on top.


    Tips: Alternatively, choose the window you want to switch to from the Windows menu or
    via the respective tab, if you selected Arrange as tabs.
    You can also customize the arrangement of windows (see "Restoring window settings"
    on page 827).

    14.3

    Shortcuts and functions keys in Visum


    By default, the following shortcuts and function keys are meant to help you access program
    functions and areas quickly and easily.
    Shortcuts and function keys in the Network editor
    Note: Some of the shortcuts and function keys listed below are also available in other
    views.
    Keys

    Description

    CTRL+C

    Copies attributes of the selected network object to the Clipboard.

    CTRL+G

    Opens the Graphic parameters window

    CTRL+L

    Opens the License window

    CTRL+N

    Opens a new file

    CTRL+O

    Opens a window for file type choice

    CTRL+P

    Opens the Printer settings window

    CTRL+S

    Saves the current version

    CTRL+V

    Pastes attributes from the Clipboard into window

    CTRL+Y

    Redo

    CTRL+Z

    Undo

    CTRL+T AB

    Switches to the next view open

    SHIFT+CTRL+T AB

    Switches to the previous view open

    CTRL+F4

    Closes active view

    F1

    Opens context-sensitive online Help

    F2

    Highlights the opposite direction of the link or connector selected

    F3

    Opens the Find window of the network object currently selected

    F4

    Shows/hides the bar labeling of the selected object

    PTVGROUP

    829

    14.3 Shortcuts and functions keys in Visum


    Keys

    Description

    F5

    Switches to the Edit shape mode

    F6

    Moves the bar labeling of the selected object

    F7

    Aggregates zones and line routes

    F8

    Splits links and zones

    ALT+F4

    Quits the program

    ALT+LEFT ARROW

    Switches to the previous section

    ALT+RIGHT ARROW

    Switches to the next section

    SHIFT+F3

    Opens the Find vehicle journeys window


    Note
    The network object Lines / Line routes must be selected.

    INS

    Switches to the Insert mode

    HOME

    Displays entire network


    Note
    This function is also available in other views.

    DEL

    Calls the delete function of the network object currently selected


    Note
    In the Procedure sequence window, you can also press this key to
    delete the selected procedure step.

    Switches to the Set window section mode

    PAGE UP

    Enlarges the network display


    Tip
    This function is also available in other views.

    PAGE DOWN

    Reduces the network display


    Tip
    This function is also available in other views.

    ARROW KEYS

    Move the view in the corresponding direction

    ENTER

    Opens the Edit window of the selected network object

    SPACE BAR

    Switches to the Shift window section mode as long as you press


    the key

    Shortcuts in the Timetable editor

    830

    Keys

    Description

    CTRL+F3

    Highlights coupled vehicle journeys

    F3

    Opens the Find vehicle journeys window

    PTVGROUP

    14.4 Opening and saving files


    Shortcuts in the Matrix editor and in lists
    In the Matrix editor and in lists, you can use shortcuts to choose sections (see "Selecting cells
    using the keyboard" on page 1763 and "Selecting list sections via the keyboard" on page
    2320).
    Shortcuts in the Scripts menu
    There are no additional shortcuts available in the Scripts menu. However, you may define
    your own shortcuts that refer to running a registered script (see "Editing the script menu" on
    page 2664).

    14.4

    Opening and saving files


    Visum provides several ways to save data to file and to read data from file. For instance you
    can save the network, filter settings and matrices separately or save all data together as a version file and read data from file accordingly.
    Note: You can also import and export data of other file formats (see "Using interfaces for
    data exchange" on page 2511).
    Subjects
    Opening and saving files separately
    Settings for opening and saving data files
    Editing the storage location of files
    Opening and saving a version file
    Opening and saving a project directories file
    Opening and saving a network file and adding comments
    Reading network data additionally
    Reading a network file with incomplete line routes or system routes
    Starting with an empty program interface

    14.4.1

    Opening and saving files separately


    Notes: You can open and save a selection of the most important file types. For more information, please refer to the respective manual section. How to open and save file types
    that are not mentioned here is described in the respective context (see "File types" on
    page 2674).
    You can also specify that log files shall be saved automatically (see "Using protocol files"
    on page 876).

    14.4.1.1

    Saving a file
    Certain data or settings you can save to file.
    1. Click the

    Save as icon.

    Tip: Alternatively, to open the window, hold down the C TRL and O keys.
    The Select file type window opens.
    PTVGROUP

    831

    14.4.1.1 Saving a file


    2. Select the desired file type.
    File type

    File
    extension

    Project direc- *.pfd


    tories

    Description

    Standard path settings by file type (see "Saving a project


    directories file" on page 839)

    Version

    *.ver

    Network and various settings and parameters (see "Saving


    a version file" on page 841)

    Network

    *.net

    Network data (see "Saving a network file" on page 846)

    OD demand
    data

    *.dmd

    Demand data (see "Saving demand data" on page 1842)

    Filters

    *.fil

    Filter settings for all network objects (see "Reading and


    saving filters" on page 1024)

    Procedure
    parameters

    *.par, *.xml List of selected procedures and the particular settings (see

    "Saving procedure parameter settings to file" on page


    1868)

    Graphic para- *.gpa


    meters

    Settings for graphical network display (see "Saving the


    graphic parameters of the network window" on page 2496)

    Active network objects

    *.ane

    Spatial selection settings for all network objects ("active" or


    "passive") (see "Saving a spatial selection of network
    objects" on page 1039)

    EVA weighting matrix

    *.wmt

    Weighting matrix (see "Managing weighting matrices" on


    page 1677)

    Texts

    *.txt

    Legend or background texts (see "Saving texts" on page


    2237)

    Legend parameters

    *.lgd

    Legend parameters (see "Opening and saving legend parameters" on page 2260)

    Environmental
    parameters

    *.upa

    Environmental calculation parameters (see "Setting environmental impact parameters" on page 2183)

    User preferences

    *.xml

    Settings in the Edit> User Preferences menu (see


    "Saving, opening and restoring user preferences" on page
    869)

    Script menu
    file

    *.xml

    Entries in the Scripts menu (see "Editing the script menu"


    on page 2664)

    3. Confirm with OK.


    Note: Depending on the file type another window opens in which you have to specify
    settings.

    832

    PTVGROUP

    14.4.1.2 Opening a file


    The Save <file type> window opens.
    Note: The path displayed here by default can be edited (see "Editing the storage location of files" on page 837).
    4. Enter the desired file name and path, if required.
    5. Click the Save button.
    The corresponding data are saved to a file of the selected type.
    Note: If you save your data as a version file with a new name, the new version file will be
    open automatically on screen. When you save a network version to a network file, it
    depends on your current setting of Use file name as document name, whether the
    newly saved network file or the version file is opened (see "Settings for opening and
    saving data files" on page 835). From the title bar you can see which of the files is open.
    For all other file types applies: After saving data to file your original file remains open.
    14.4.1.2

    Opening a file
    1. Click the

    Open icon.

    The Select file type window opens.


    2. Select the desired file type.
    File type

    File
    extension

    Project direc- *.pfd


    tories

    Description

    Standard path settings by file type (see "Opening a project


    directories file" on page 839)

    Version

    *.ver

    Network and various settings and parameters (see "Opening a version file" on page 840)

    Network

    *.net

    Network data (see "Opening and saving a network file and


    adding comments" on page 844)

    OD demand
    data

    *.dmd

    Demand data (see "Reading demand data from file" on


    page 1836)

    Filters

    *.fil

    Filter settings for all network objects (see "Reading and


    saving filters" on page 1024)

    Procedure
    parameters

    *.par, *.xml List of selected procedures and the particular settings (see

    "Reading procedure parameter settings from file" on page


    1868)

    Graphic para- *.gpa


    meters
    Attributes

    PTVGROUP

    *.att

    Settings for graphical network display (see "Reading


    graphic parameters of the network window" on page 2497)
    Attribute data by network object type (see "Reading attri-

    833

    14.4.1.2 Opening a file


    File type

    File
    extension

    Description

    bute data into lists" on page 2328)


    Active network objects

    *.ane

    Spatial selection settings for all network objects ("active" or


    "passive") (see "Reading a spatial selection of network
    objects" on page 1039)

    EVA weighting matrix

    *.wmt

    Read weighting matrix data from file (see "Managing weighting matrices" on page 1677)

    Texts

    *.txt

    Texts to be displayed in legend or background (see "Reading texts" on page 2237)

    Legend parameters

    *.lgd

    Legend parameters (see "Opening and saving legend parameters" on page 2260)

    Network
    merge parameters

    *.nmp

    Settings for reading a merged network (see "Merging networks" on page 902)

    Environmental
    parameters

    *.upa

    Environmental calculation parameters (see "Setting environmental impact parameters" on page 2183)

    User preferences

    *.xml

    Load settings in the Edit> User Preferences menu (see


    "Saving, opening and restoring user preferences" on page
    869)

    Script menu
    file

    *.xml

    Entries in the Scripts menu (see "Editing the script menu"


    on page 2664)

    Scenario
    management
    project

    *.vpdb

    Project of scenario management (see "Scenario management" on page 921)

    3. Confirm with OK.


    Note: Depending on the selected file type, further windows might open for further settings required. For more information, please refer to the particular manual sections.
    The Open <file type> window opens.
    4. Select the desired path and file name.
    Note: You can edit the path displayed here by default (see "Editing the storage location of files" on page 837).
    5. Click the Open button.

    834

    PTVGROUP

    14.4.2 Settings for opening and saving data files


    In case of unsaved changes to the current network when opening a network or version file,
    a security prompt appears.
    Note: Depending on the selected file type, further windows might open for further settings required. For more information, please refer to the particular manual sections.
    6. If applicable, confirm this query with Yes.
    The file is opened.
    Note: Possible effects depend on the selected file type and on your settings.
    Version file: The file which has been open is closed and the version file will be opened. The name of the version file is shown in the title bar (see "Opening a version
    file" on page 840).
    Network file: You can open a network file to replace current data or read network
    data additionally to this file. In the first case, the current file is closed and the network
    file will be opened on screen. In the latter case, network data is added to the file
    currently open (see "Opening and saving a network file and adding comments" on
    page 844).
    Network merge parameters: The file that was open before is closed. A combination
    built from two version files will be opened. The names of the two version files are displayed in the title bar (see "Displaying flow bundles" on page 2265).
    To all other file types applies: Data read from file is added to the currently open file.
    Tip: You can also open a file by clicking the selected file in the list of recently opened
    files in the File menu. Alternatively, drag a file from the Windows Explorer to the program
    interface.

    14.4.2

    Settings for opening and saving data files


    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> Warnings.
    3. Select the desired option.
    Element

    Description

    Display warnings
    when saving

    Via this option you decide whether a security query shall be


    prompted if a version is saved to file overwriting a file with the
    same name (see "Saving a version file" on page 841).

    4. In the navigator, select Files & protocols> General.


    5. Select the desired options.

    PTVGROUP

    835

    14.4.2 Settings for opening and saving data files


    Element

    Description

    Use file name as


    document name

    Via this option you set the default for saving a network to file.
    If this option has been selected, the network just saved to
    file will be open then.
    If this option has not been selected, the file currently being
    open will remain open.
    Note
    You may edit this default setting when you save a network file
    (see "Saving a network file" on page 846).

    List of most recently From the drop down list, select the appropriate number of entopened files
    ries to be stored with the MRU list in the File menu.
    Encoding for text
    files

    From the drop down list, select the appropriate data format for
    text files to be saved.
    ANSI
    Unicode
    Unicode big endian
    UTF-8
    Automatic: In this mode, the file will be written in ANSI
    code page if all signs can be represented correctly, otherwise as UTF-8.

    6. In the navigator, select Files & protocols> Backup copy.


    7. Select the desired options.

    836

    Element

    Description

    Save version with


    backup copy

    Via this option you decide, whether a backup copy of the version shall be saved.
    Note
    The original file is only replaced by the new version if this is
    complete and correct.

    Automatic backup
    every ... minutes

    Use this option to define, whether Visum shall save a backup


    copy of the current network version at regular intervals. The
    backup copy has the name of the currently loaded file and also
    its file extension. Additionally, the file extension .ves is added
    automatically (Example: example.net.ves). By default, the
    backup copy is saved to the directory in which the currently loaded file has been stored. This you can change via option Common folder for backup copy. Enter the time gap between two
    backup copies (maximum: 120 minutes).
    Notes
    To open a backup copy, rename it to *.ver and read it from file

    PTVGROUP

    14.4.3 Editing the storage location of files


    Element

    Description
    like a version file.
    Visum cannot save a backup copy as long as a modal window
    is open. In this case, the backup copy will be created as soon
    as the window is closed. This guarantees that only consistent
    data states are saved to file.
    If no file is currently opened, for example directly after program
    start, the backup copy is saved to the standard folder for version files (see "Changes to settings in the configuration file" on
    page 889) under the name Tmpn.ves.

    Common folder for


    backup copy

    Use this option to define a common directory that stores all


    backup copy files (cf. option Automatic backup every ... Minutes). As long as no folder has been selected here each backup
    copy is saved to the directory from which the currently open file
    has been read.
    Notes
    Existing files with the same name in this directory will be overwritten.
    If no backup copy can be created, for example due to insufficient access rights to the target folder, Visum will first try to
    save the backup copy to the standard directory for version files
    under the name Tmpn.ves (see "Changes to settings in the configuration file" on page 889). If this also fails, a message will
    appear.

    8. Confirm with OK.

    14.4.3

    Editing the storage location of files


    Visum uses various file types to which data is saved or from which data is read. For most of
    these file types you can define a directory where files of this type are to be stored by default
    and from where they are read by default. Visum will also browse through this folder for related
    files of the file type, for example for backgrounds or POIs.
    1. Choose the File menu. Then point to Project directories.
    2. Click Edit project directories.
    The Edit project directories window opens.
    Note: In this window, all relevant Visum file types are listed (see "File types" on page
    2674).
    3. In the row of a particular file type, click the button

    PTVGROUP

    837

    14.4.4 Opening and saving a project directories file


    Note: Via the All button you can change the directory for almost all of the file types
    simultaneously. Exceptions are the project directory file (*.pfd), user-VDF-DLLs, projections (*.prj) and Visum add-ins.
    We recommend to create a project folder for your project and sub-folders for the required file types. For all file types, you can then change the path to the project folder
    (example: T:\Project_XY). Subsequently you can set the specific path to the particular
    sub-folder (e.g. to T:\Project_ XY\ver for versions or to T:\Project_XY\gpa for graphic
    parameters) for each of the required file types.
    4. Select the desired folder.
    5. Confirm with OK.
    In the Directory column the path to the selected folder is listed.
    Note: Alternatively you can edit the path by double-clicking the current entry and edit
    the path directly. This way you can also enter relative paths.
    ..\ refers to a sub-folder of the installation folder of your Visum installation (example: ..\PTV Visum 13\Doc)
    Under Windows XP, %MYDOCUMENTS%\ refers to C:\Documents and settings\<User>\Own files. Under Windows VISTA and Windows7, it refers to C:\Users\<User>\Documents
    Under Windows XP, %APPDATA%\ refers to C:\Documents and settings\<User>\Application data\. Under VISTA and Windows7, it refers to C:\Users\<User>\AppData\Roaming\
    6. If necessary, change further directories.
    7. Confirm with OK.
    When a file is to be read or saved next time Visum will use the new paths by default.
    Notes: These settings only apply until your Visum session is terminated. But you can
    save the settings to file and read them from file again (see "Saving a network file" on
    page 846).
    You can also edit given file extensions or add more file extensions. We recommend not
    to change this setting.

    14.4.4

    Opening and saving a project directories file


    A project directories file stores the standard path by Visum file type. In it there is preset from
    which folders the Visum file types are to be read by default and to which folders they are to be
    saved to by default. Additionally, a project directories file contains the specific file extension(s)
    by file type. Thus the various file types can be distinguished.
    The standard project directories file std.pfd is installed automatically.
    Windows XP: c:\Documents and settings\<User>\Application data\PTV Vision\PTV Visum
    13\<Version number>\std.pfd

    838

    PTVGROUP

    14.4.4.1 Saving a project directories file


    Windows VISTA and Windows7:
    C:\Users\<User>\AppData\Roaming\PTV Vision\PTV Visum 13\std.pfd
    It is opened by default when Visum is started. Alternatively you can decide that a different project directories file shall be opened during program start (see "Editing user preferences" on
    page 867).
    14.4.4.1

    Saving a project directories file


    You can store the standard path settings predefined by file type (see "Editing the storage location of files" on page 837).
    1. Choose the File menu. Then point to Project directories.
    2. Click Save project directories.
    The Save: Project directories window opens.
    3. Select the desired directory and enter the desired file name.
    Notes: By default, the folder you have selected for saving project directories files is
    displayed (see "Editing the storage location of files" on page 837).
    Only if the paths are directly saved to the standard project directories file C:\<User>\Application data\Roaming\PTV Vision\PTV Visum 13\std.pfd (see "Changes to
    settings in the configuration file" on page 889), will your settings be automatically loaded with the next program start. Otherwise the standard settings from the standard
    project directories file will be read when Visum is started the next time. If required you
    can open the file you had saved and read your settings from file in Visum(see "Opening a project directories file" on page 839)
    We recommend to save your user-defined project directories file with the project data
    files to your project directory (see "Editing the storage location of files" on page 837).
    This way, you can archive all project data together.
    4. Confirm with OK.
    The file is saved.

    14.4.4.2

    Opening a project directories file


    Opening a project directories file means the definition of paths to be regarded by default for
    Read or Save a file.
    1. Choose the File menu. Then point to Project directories.
    2. Click Open project directories.
    The Open: Project directories window opens.
    3. Open the desired file.
    4. Click the Open button.
    The project directories file is read.

    PTVGROUP

    839

    14.4.5 Opening and saving a version file


    Note: Alternatively you can open a project directories file automatically during program
    start (see "Changes to settings in the configuration file" on page 889).

    14.4.5

    Opening and saving a version file


    Version files are the most important and most frequently used file type for saving your Visum
    work. Besides the network, further data is saved to a version file. Version files include the following data:
    Network data
    Demand data and skim matrices
    User-defined attributes, AddValues, etc.
    Graphic parameters with flow bundles, turn volumes, isochrones and references to active
    backgrounds etc.
    State active/passive of network objects thus filter settings and spatial selection
    Procedure parameters
    Assignment results (e.g. connections) and any other calculated results (convergence criteria of PrT assignment quality included)
    You can also save and read this data separately (see "Opening and saving files separately"
    on page 831).
    By default, the version data file extension is *.ver (see "File types" on page 2674).

    14.4.5.1

    Opening a version file


    Note: Visum version files are not downwards compatible. This means you cannot use an
    older Visum version to open version files created in a recent Visum version. E.g. you cannot open a Visum 13.01 version file with Visum 13.00. The bug fix version number,
    appended to the actual version number with a hyphen, is ignored in this context (Help
    menu > About> Version).
    1. In the File menu, select the Open version entry.
    In case of unsaved changes to the current network, a security prompt appears.
    2. Confirm this security prompt.
    The Open: Version window opens.
    3. Open the desired file.
    4. Click the Open button.
    Note: Depending on the contents of the version file and your settings different queries
    or warning will be displayed, which you have to confirm.
    The version file is opened and the name of the version file appears in the window header.

    840

    PTVGROUP

    14.4.5.2 Saving a version file


    Notes: Which of the windows are open after reading a version file depends on your settings (see "Specifying the size and position of windows" on page 872).
    For each version file you can specify how the matrices contained in the version are read
    when opening the version file (see "How to handle matrix data when opening or saving a
    version file" on page 843).
    The PrT assignment result stored with the version file will be discarded in case of version
    files saved with a Visum version prior to Visum 10, if this network contains nodes.
    If you open a version file larger than your license permits, a warning is displayed that
    says Visum is in the oversize mode. The title bar indicates the oversize mode when the
    network is too large. You cannot save the version file in this mode. Reduce the network
    to license size (see "Subnetwork generation" on page 1602) to use all functions and
    save the network file.
    Besides the Subnetwork generator, you can use the following functions in the oversize
    mode:
    Edit network
    Make screenshots of Network and Timetable editor
    Execute COM scripts
    Tips: Alternatively, you can open a version file by clicking the selected file in the list of
    recently opened files in the File menu or by drag % drop. Drag the version file from the
    Windows Explorer into the program window on screen.
    Alternatively, you can open a version file during program start automatically (see "Changes to settings in the configuration file" on page 889).
    Alternatively, you can open a version file by double-clicking the version file in the Windows Explorer. In this case, a specific project directory file (aktdrv.pfd ) is used for the
    start. It ensures that Visum browses for referenced files in the directory where the version
    file itself has been stored.
    14.4.5.2

    Saving a version file


    A version file you may save with identical path and file name (thus the existing file is overwritten) or to a different directory and/or with a new file name.
    You can also save a version file as one of the actions in the procedure sequence.
    Note: Visum version files are not downwards compatible. This means you cannot use an
    older Visum version to open version files created in a recent Visum version. E.g. you cannot open a Visum 13 version file with Visum 12.50. The bug fix version number, appended to the actual version number with a hyphen, is ignored in this context (Help menu >
    About> Version).
    Saving a version file with identical path and file name
    1. On the Functions toolbar, click the

    PTVGROUP

    Save version icon.

    841

    14.4.5.2 Saving a version file


    Tip: Alternatively, click menu File> Save version or press CTRL+S.
    Note: If under Edit> User Preferences> GUI> Warnings you selected Display warnings when saving, a security query is opened (see "Settings for opening and saving
    data files" on page 835).
    2. If applicable, confirm this query with Yes.
    The version file is saved with identical path and file name. The existing version file is thus
    replaced.
    Note: A backup copy can be saved automatically (see "Settings for opening and saving
    data files" on page 835).
    Saving a version file with a different path or file name
    1. In the File menu, select the Save version as entry.
    The Save: Version window opens.
    2. If necessary, select a different directory.
    3. If necessary, edit the file name.
    4. Click the Save button.
    The version file is saved.
    Saving a version in the procedure sequence
    You can save the version file in the procedure sequence (see "Setting up and starting the procedure sequence" on page 1847).
    Note: During a procedure sequence, no security queries are prompted on screen when
    overwriting an existing version file.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Select the desired position in the procedure sequence and add the procedure Save version from the Miscellaneous category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Parameters: Save version window opens.
    4. Make the desired changes.

    842

    PTVGROUP

    14.4.5.3 How to handle matrix data when opening or saving a version file
    Element

    Description

    Browse

    The button opens a window. It allows you to select the file you
    want to save your version to.
    Note
    You can either select an existing file and overwrite it or enter a
    new file name. If you select an existing file, you need to confirm
    the security query.

    Add the current


    value of the innermost 'Go To' counter to the filename

    Select this option to append an underscore and counter to the file


    name selected. When you save the counter, it contains the current iteration value of the innermost GoTo loop (see "Go to a procedure in the procedure sequence (GoTo procedure)" on page
    1697).

    5. Confirm with OK.


    The file name (without counter) is displayed in the Variant/file column.
    Tips: Alternatively, you can edit the file name as follows:
    double-click the entry in the Variant/file column and edit it directly
    click the
    icon and select a file.
    This will not affect the counter appended.
    6. Start the procedure (see "Setting up and starting the procedure sequence" on page 1847).
    During procedure execution, the version is saved according to the specified order of actions.
    14.4.5.3

    How to handle matrix data when opening or saving a version file


    For each version file you can specify how the matrices contained in the version are read when
    opening the version file. In addition, you can save the matrix data to a separate file.
    1. Open the desired version file.
    2. In the File menu, select the File properties entry.
    The File properties window opens.
    3. Make the desired changes.
    Element

    Description

    No special hand- If this option has been selected, all matrix data is read immedialing of matrix data tely when the version is read from file.
    Load matrix data If this option has been selected, no matrix data is read when the
    later from version version is read from file. The matrix data will be imported on
    file, if applicable
    demand. Thus, the version file is opened faster.
    Note

    PTVGROUP

    843

    14.4.6 Opening and saving a network file and adding comments


    Element

    Description
    This option only takes effect if the matrix swap file is enabled (see
    "Specifying settings for treatment of matrices" on page 1760).

    Save matrix data


    as separate
    matrix data file

    If this option has been checked, all matrix data of version are
    saved as a separate file. It is stored in the folder where the version file has been stored and has the same file name. The file
    extension is *.vmx.
    Notes
    This option only takes effect if the matrix swap file is enabled (see
    "Specifying settings for treatment of matrices" on page 1760).
    We recommend that you activate this option when working with
    version files that contain a large amount of matrix data. Using this
    option will accelerate the 'Save version' process, for example
    after network editing operations. Since the matrices are not concerned they do not have to be stored again in this case.
    Tip
    To re-integrate the matrix files in the version file, uncheck this
    option and save the version to file.

    4. Confirm with OK.


    5. Save the version file.
    The selected setting is transferred to the version file. When opened the next time it will be applied.

    14.4.6

    Opening and saving a network file and adding comments


    Network files contain network model data, i.e. data of all network objects in tabular form. In
    Visum, you can open and save network files like any other file type. Furthermore, you can read
    network data additionally to the network being displayed on screen (see "Reading network
    data additionally" on page 851).
    By default, the network data file extension is *.net (see "File types" on page 2674).
    Note: You can write network files in the following languages: English, German, French,
    Italian, Polish. The network file is generally written in one of the supported languages displayed in the user interface of Visum. If another language is used, it is written in English.

    14.4.6.1

    Adding comments to the network


    You can add an unlimited number of comments to the network model. These will be saved
    with the network file and with the version file.
    1. In the File menu, select the File info entry.
    The Network notepad window opens.
    2. Enter the comment.

    844

    PTVGROUP

    14.4.6.2 Opening a network file


    3. Confirm with OK.
    The comment is stored.
    14.4.6.2

    Opening a network file


    1. Click the

    Open icon.

    The Select file type window opens.


    2. Select the Network entry.
    3. Confirm with OK.
    The Open network window opens.
    4. Select the desired file.
    5. Click the Open button.
    The Read network window opens.
    6. Make the desired changes.
    Element

    Description

    Show warnings on
    screen

    Select this option to show warnings when loading files.


    If this option is not selected, no warnings are shown when you
    load files. Then the loading is quicker.
    Note
    If in the warning settings, you selected Save warnings and
    details to the message file and in the log files, you selected Message file: Create new file, warnings are saved to a message file
    (see "Specifying settings for protocol files" on page 876).

    Display error messages on screen

    Select this option to show error messages when loading files.


    If this option is not selected, no error messages are shown
    when you load files. Then the loading is quicker.

    Read network file


    additively

    Select this option to read the network file in addition to the


    currently opened network. You can specify further settings (see
    "Reading network data additionally" on page 851).
    If this option is not selected, the network currently opened is
    closed and the network of the network file is opened.

    Show the 'ComSelect this option to open the window Read network (completing line routes' pleting the courses of line routes/system routes). Here you spewindow
    cify how Visum shall read incomplete line or system routes (see
    "Reading a network file with incomplete line routes or system routes" on page 861).
    Normalize created

    PTVGROUP

    Select this option to normalize all newly added polygons and


    all polygons changed through the import process.

    845

    14.4.6.3 Saving a network file


    Element

    Description

    and modified polyIf this option is not selected, no polygons are normalized.
    gons (Self-interNotes
    secting test)
    Polygons have to be normalized, if for example you require the
    area or want to intersect the polygons. You do not have to normalize polygons to e.g. only show them in the background (see
    Fundamentals: Chpt. 3.5.2 , page 124).
    You can also normalize polygons later on (see "Normalizing all
    surfaces" on page 1052).
    Merge points with
    Select this option to merge polygon points with the same cooridentical co-ordi- dinates.
    nates
    If this option is not selected, the polygon points are not merged.
    Notes
    This option is useful, e.g., when the polygon points represent a
    municipal border. If two polygons are merged, both polygons automatically change when shifting the polygon point.
    You can also merge polygon points later on (see "Merging all
    polygon points with identical co-ordinates" on page 1053).
    7. Confirm with OK.
    Notes: If the Show the 'Completing line routes' window option has been checked,
    the Read network (completing the courses of line routes/system routes) window
    opens. Here you can specify how you want to add the data (see "Reading a network
    file with incomplete line routes or system routes" on page 861).
    Network objects from tables labeled $-<Name of object type> are ignored during the
    import (see "Creating a model transfer file" on page 908).
    The network file is opened and the network is displayed in the Network editor window. The
    name of the network file is shown in the title bar.
    14.4.6.3

    Saving a network file


    Note: When you save a network file, the attribute values are saved with a specific number
    of decimal places (see "Settings for decimal places and aggregate functions" on page
    960).
    1. Click the

    Save as icon.

    The Select file type window opens.


    2. Select Network and click OK.
    The Save network window opens.

    846

    PTVGROUP

    14.4.6.3 Saving a network file


    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The Save network (user-defined) window opens.
    Note: If you show the program interface in a language (e.g. Greek) that is not supported by the network file, the Display language section is displayed at the top of the
    window. Here you can select a language for display of the table. By default, the network file is then written in English.
    5. If necessary, reduce the amount of data to be saved to file.
    Element

    Description

    Hide calculated
    attributes

    If this option has been selected, the calculated attributes are


    hidden and are not saved.
    If this option has not been selected, calculated attributes are
    equally saved.
    Tip
    Saving calculated attributes can be useful for further evaluation
    purposes, such as an analysis in a database.
    Note
    Calculated attributes are ignored during the reading process.

    Hide attribute with


    If this option has been checked, only selected attributes are
    default values
    saved with their values.
    Tip
    Use this option to reduce file size.
    If this option has not been checked, all of the selected attributes are saved with their values not regarding whether attribute
    value and default value are identical or not.
    Note
    You can find the default attribute values in the Attribute.xls file,
    under ...\Program files\PTV Vision\PTV Visum 13\Doc.
    Hide empty tables If this option has been selected, only those tables containing network objects are saved to file.
    Save only active
    network objects

    If this option has been selected, only those network objects of the
    selected tables are saved to file which are active.
    Note
    In this case node geometries and signalizations are only saved
    for active nodes or main nodes. It is not relevant whether the links
    involved are active or not.

    6. Select which file shall be open once the network will have been saved.

    PTVGROUP

    847

    14.4.6.3 Saving a network file


    Element

    Description

    Use file name as


    document name

    Via this option you decide whether the network file or the current
    file shall be open later.
    If this option has been selected, the network just saved to file
    will be open then.
    If this option has not been selected, the file currently being
    open will remain open.
    Note
    You can change the default setting of this option (see "Settings for
    opening and saving data files" on page 835).

    7. Select the data tables you want to save to file.


    Element

    Description
    The table has been selected and will be saved to file.
    The table has not been selected and will not be saved to file.
    Note
    The Version data block table cannot be disabled.

    Check all tables Via this button, you may check all tables.
    Note
    The status of the attributes in the tables remains unchanged.
    Uncheck all
    tables

    Use this button to deselect all tables except Version block.


    Note
    The status of the attributes in the tables remains unchanged.

    Frequent cases The data required for description of the objects of a particular network object type are stored in just a single or in multiple tables. Link
    object data, e.g., are included in the Link table. Links with an edited
    shape are additionally part of the data block Link polygons.
    Use this button to select all data tables required for the description of
    specific network objects (so-called use cases) and there attributes at
    the same time (see "Selecting data tables required for network
    object type description for saving data to file" on page 850).
    8. Click a table name.
    The table attributes are displayed.
    Tip: Click the CTRL key and keep it pressed while clicking multiple tables one by one
    to show the attributes of these tables simultaneously.

    848

    PTVGROUP

    14.4.6.3 Saving a network file


    Note: Due to current option settings in the upper section of the window possibly not all
    of the attributes might be displayed by table.
    9. Select the attributes you want to save to file.
    Element

    Description
    The attribute has been selected and is saved to file.
    The attribute has not been selected and is not saved to file.
    The attribute is a key attribute and cannot be switched off.
    Key attributes are attributes which serve for unique identification of
    network objects.
    The attribute is a mandatory attribute and cannot be excluded.

    Attribute
    groups

    Via this button you can either select or switch off predefined groups of
    attributes in a separate window (see "Selecting or deselecting groups
    of attributes for saving data" on page 849).

    Standard

    Click this button to hide empty tables and calculated attributes. All
    other attributes are selected. The Save only active network objects
    option remains unchanged.

    Tip: Right-click a table name. In the context menu, activate or deactivate all table attributes currently displayed.
    Note: Alternatively, you can read selected tables and attributes from a network file
    *.net (see "Reading a layout from a network file" on page 851).
    10. Confirm with OK.
    Network data is saved according to the current settings.
    Selecting or deselecting groups of attributes for saving data
    1. Make sure that the Save network (user-defined) window is open (see "Saving a network
    file" on page 846).
    2. Click the Attribute groups button.
    The Save selected groups of attributes window opens.
    3. In the selection list, mark the predefined attribute group you would like to select or deselect.
    Tip: To select multiple attribute groups, hold down the C TRL key while clicking the desired entries one by one.
    4. Click the desired button.

    PTVGROUP

    849

    14.4.6.3 Saving a network file


    Element

    Description

    Activate

    All attributes of the selected groups are enabled.

    Switch off

    Except key attributes and mandatory attributes, all attributes of the


    selected group are deactivated.

    Activate exclusively

    All attributes of the selected group are activated for saving data to
    file and all attributes of other groups - except key attributes and
    mandatory attributes - are excluded from saving data to file.

    5. Click the Close button.


    According to the current settings, the attributes are either selected or deselected.
    Selecting data tables required for network object type description for saving data to file
    In Visum network files, several tables contain data for the description of specific network
    objects, for example zones and corresponding polygons, timetable or line blocking data.
    To make sure that you save all the tables and attributes required (so-called use case) to the
    network file, you can activate a predefined selection of tables and attributes adapted to the
    data you wish to save.
    1. Make sure that the Save network (user-defined) window is open (see "Saving a network
    file" on page 846).
    2. Click the Frequent cases button.
    The Use cases for selective network saving window opens.
    3. Make the desired changes.

    850

    Element

    Description

    Save polygons

    If this option has been selected, all tables required for polygon
    definition are selected. You can decide whether the tables of the
    related network object types (Zones, Main zones, Main nodes,
    Territories, POIs, Toll systems) are to be saved, too.

    Save timetable

    If this option has been selected, all tables are selected that contain data with regard to the timetable. You can decide whether
    data regarding calendar period and valid days are to be saved.
    Save calendar period and valid days
    If this option has been selected, the tables Calendar period, Valid
    days and Holidays are saved to file.
    Note
    This option is only provided, if a weekly or an annual calendar
    has been defined in the network.

    Save blocks

    If this option has been selected, the tables storing PuT line blocks
    and corresponding data are selected.

    PTVGROUP

    14.4.7 Reading network data additionally


    Element

    Description
    Note
    Since line blocks refer to valid days, option Save calendar period
    and valid days is selected automatically.

    Save main nodes

    Click this option to select main node tables and their data.

    4. Confirm with OK.


    Saving selected network data as layout
    You can save the currently selected tables and attributes as network file *.net without contents
    and read them again later as default values.
    1. Make sure that the Save network (user-defined) window is open (see "Saving a network
    file" on page 846).
    2. Click the Save layout button.
    The Save network window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    Selected tables and attributes are saved as data block templates without data.
    Reading a layout from a network file
    For saving network data to file you can read selected tables and attributes from an existing network file or from a network file without content, which was saved just as layout file.
    1. Make sure that the Save network (user-defined) window is open (see "Saving a network
    file" on page 846).
    2. Click the Open layout button.
    The Open network window opens.
    3. Select the desired file.
    4. Click the Open button.
    The tables and attributes contained in the network file are adopted.

    14.4.7

    Reading network data additionally


    By reading additional network data, you can extend or edit an existing network.
    To start, you open your network. Then, open the additional network file whose data you want
    to read in. Now specify which tables of the additional network file you want to adopt and how
    you want to deal with conflicts. The whole process can be divided into the following steps:
    Specifying settings for reading in additional network data
    Selecting data tables you want to read in
    Specifying settings for conflict avoidance and conflict handling

    PTVGROUP

    851

    14.4.7.1 Specifying settings for reading in additional network data


    Additionally, you have the following options:
    Saving settings for reading additional network data
    Opening settings for reading additional network data
    Note: If you want to read in an additional network file with coordinates, make sure your
    current network version contains a predefined system of coordinates (see "Selecting a
    coordinate system" on page 2207).
    14.4.7.1

    Specifying settings for reading in additional network data


    1. Open a version or network file.
    2. Click the

    Open icon.

    The Select file type window opens.


    3. Select Network and click OK.
    The Open network window opens.
    4. Select the file whose network data you want to read in.
    5. Click the Open button.
    The Read network window opens.
    6. Make the desired settings for reading in files.
    Element

    Description

    Show warnings on
    screen

    Select this option to show warnings when loading files.


    If this option is not selected, no warnings are shown when you
    load files. Then the loading is quicker.
    Note
    If in the warning settings, you selected Save warnings and
    details to the message file and in the log files, you selected Message file: Create new file, warnings are saved to a message file
    (see "Specifying settings for protocol files" on page 876).

    Display error messages on screen

    Select this option to show error messages when loading files.


    If this option is not selected, no error messages are shown
    when you load files. Then the loading is quicker.

    Show the 'ComSelect this option to open the window Read network (completing line routes' pleting the courses of line routes/system routes) when reading
    window
    in a file. Here you specify how Visum shall read incomplete line
    or system routes (see "Reading a network file with incomplete
    line routes or system routes" on page 861).
    7. Select the Read network file additively option.
    More options will be available.

    852

    PTVGROUP

    14.4.7.1 Specifying settings for reading in additional network data


    8. Make the desired changes.
    Element

    Description

    First of all, determine existing


    tables

    Select this option to check the network file you want to read in.
    Only the tables of this file are then displayed for table selection.
    If this option is not selected, all tables are available for selection.

    Create warnings
    Select this option to show warnings about existing network
    for conflicts in the objects when reading in files in the "Ignore" mode (see "Selecting
    data tables you want to read in" on page 854).
    "Ignore" mode
    Deactivate this option, if you do not want to show warnings
    about existing network objects when reading in files in the
    "Ignore" mode. Then the loading is quicker.
    Note
    If in the warning settings, you selected Save warnings and
    details to the message file and in the log file settings, you selected Create new file, the warnings are saved to the message file
    (see "Specifying settings for protocol files" on page 876).
    Permit the deletion of objects

    If this option has been selected, network objects in tables labeled $-<name of object type> will be deleted from the network.
    If this option has not been selected, tables that are labeled $<Object type name> will be ignored.

    Show statistics of Select this option to have Visum create a model transfer file while
    modifications
    reading in a new file. The model transfer file contains all changes
    that are made according to the new file. The file is saved to the
    project directory specified for model transfer files, under the name
    <Current version name> - ReadNetwork.tra. It is automatically
    opened when it is read in.
    9. Make the settings of your choice under Polygon handling after import.

    PTVGROUP

    853

    14.4.7.2 Selecting data tables you want to read in


    Element

    Description

    Normalize created
    Select this option to normalize all newly added polygons and
    and modified poly- all polygons changed through the import process.
    gons (Self-interIf this option is not selected, no polygons are normalized.
    secting test)
    Notes
    Polygons have to be normalized, if for example you require the
    area or want to intersect the polygons. You do not have to normalize polygons to e.g. only show them in the background (see
    Fundamentals: Chpt. 3.5.2 , page 124).
    You can also normalize polygons later on (see "Normalizing all
    surfaces" on page 1052).
    Merge points with
    Select this option to merge polygon points with the same cooridentical co-ordi- dinates.
    nates
    If this option is not selected, the polygon points are not merged.
    Notes
    This option is useful, e.g., when the polygon points represent a
    municipal border. If two polygons are merged, both polygons automatically change when shifting the polygon point.
    You can also merge polygon points later on (see "Merging all polygon points with identical co-ordinates" on page 1053).
    10. Confirm with OK.
    The Read network data additionally window opens. Select the data tables you want to
    read in.
    14.4.7.2

    Selecting data tables you want to read in


    In the Read network data additionally window, select the data tables you want to read into the
    existing network. Here you can also specify how you want Visum to deal with conflicts.
    1. Make sure that the Read network data additionally window is open.

    854

    PTVGROUP

    14.4.7.2 Selecting data tables you want to read in

    Note: At the top of the window, the Display language section is displayed, if the
    Visum interface is in a language that is not supported by the network files. Here you
    can select the language you want to show the texts of the column Network objects
    (table) in.
    2. Select the data tables you want to read into your current network.
    Element

    Description
    The table is added to the existing network data.
    The table is not read into the existing network.

    Network objects
    (table)

    This column lists the data tables you can read into your network.
    Depending on whether the option First of all, determine existing
    tables is activated, this list either contains all tables available or
    only those saved to the network file.

    Check all

    Via this button, you may check all tables.

    Uncheck all

    Via this button, you may uncheck all tables.

    Edit

    Use this button to specify the settings for conflict avoidance and
    conflict handling for several tables at the same time. To do so,
    highlight the tables. Then click Edit.

    Frequent cases

    Click this button to select additional data tables (required to describe specific network objects) together with preset options for
    conflict avoidance and handling (see "Frequent cases:reading in
    frequently required data tables" on page 856).

    Conflict avoidance (see "Specifying settings for conflict avoidance and conflict handConflict handling ling" on page 857).

    PTVGROUP

    855

    14.4.7.2 Selecting data tables you want to read in


    Element

    Description

    Save

    Click Save to save your settings, so you can use them again later
    on. The settings specified here are saved to a *.arnp file and can
    be quickly read in again when required.

    Open

    Click Open to open the settings saved as a *.arnp file.

    Frequent cases:reading in frequently required data tables


    Data required to describe an object of a particular network object type is stored in one or multiple tables. All link object data, e.g., is listed in the Links table. Links with an edited shape,
    additionally save data to the Link polygons.
    To make sure you read in all tables and attributes required (so-called use case), you can
    select a predefined set of the tables and attributes you wish to read in, including the appropriate settings for conflict avoidance and handling.
    1. Make sure the Read network data additionally window is open (see "Reading network
    data additionally" on page 851).
    2. Click the Frequent cases button.
    The Use cases for additive network reading window opens.
    3. Make the desired changes.

    856

    Element

    Description

    Read polygons

    If this option has been selected, all of the tables required for polygon definition are selected for additive reading. You can decide
    which of the network object types having polygons (Zones, Main
    zones, Main nodes, Territories, POIs, Toll systems) are also read.

    Read timetable

    Activate this option to select all tables containing timetable-based


    data and specify how you want Visum deal to with vehicle journeys that have the same number.
    Retain all existing vehicle journeys
    Existing vehicle journeys are not changed, while additional, new
    vehicle journeys are read in.
    Replace existing vehicle journeys if number is identical
    If an existing vehicle journey has more sections than the read in
    vehicle journey, the existing sections are replaced with the new,
    read in ones. The other sections remain unchanged.
    Note
    These two options are only available if the read in data contains
    vehicle journeys.

    Read blocks

    If this option has been selected, the line block tables and corresponding data are selected for reading plus the data on valid

    PTVGROUP

    14.4.7.3 Specifying settings for conflict avoidance and conflict handling


    Element

    Description
    days, calendar period and holidays.
    Note
    Line blocks refer to valid days and cannot be read from file
    without this data.

    Read main nodes

    Activate this option to select main nodes with polygons, node allocations and main turns.

    4. Confirm with OK.


    The selected tables are read in according to the predefined settings. You can now specify the
    conflict handling settings.
    14.4.7.3

    Specifying settings for conflict avoidance and conflict handling


    A conflict arises when a network object you want to read in and an already existing network
    object have the same key. In this case, Visum allows you to specify how to proceed for each
    data table you wish to read in.
    Note: Key attributes are attributes which serve for unique identification of network objects
    (see "Identifiers" on page 2327).
    Tip: To make the settings for several data tables at the same time, highlight the respective tables and then click the Edit button.
    1. Select Conflict avoidance if you know that the network objects of your existing network and
    the network objects you want to read in have the same key, but are not identical.

    PTVGROUP

    857

    14.4.7.3 Specifying settings for conflict avoidance and conflict handling


    Element

    Description

    Conflict avoidance

    If this option has not been selected or if it is not provided, you


    can - in the Conflict handling column - choose how to handle network objects with identical keys.
    If this option is selected, in the Conflict handling column, Offset or Prefix are displayed. Here you can change the value of the
    key attribute you want to read in, to make it unique.
    Prefix
    (In the Conflict handling column)
    To an alphanumerical key attribute, you can add an alphanumerical prefix in the first position.
    Offset
    (In the Conflict handling column)
    To the value of a numerical key attribute you can add a constant
    value.
    Note
    When specifying offsets, make sure that the offset values you
    define are added to all keys of the network object.
    Example:
    Link 1 has the following keys: link number 1, From node number
    10 and To node number 20. If you specify the offset value 1 for
    links and 2 for nodes, Visum will read this link in as link number 2,
    From node 12 and To node 22.
    Note the following: If Visum cannot add the link because it cannot
    find To node 22, Visum will subtract the offset value from the To
    node and try to add the link with the To node number 20.

    2. If you do not want to choose conflict avoidance, select an option for conflict handling.

    858

    PTVGROUP

    14.4.7.3 Specifying settings for conflict avoidance and conflict handling


    Element

    Description

    Conflict handling
    (if Conflict avoidance is not selected or available)

    Only check
    This setting is only available for specific elements, e.g. transport
    system, mode, and demand segment. Visum checks whether the
    network objects you want to read in already exist in the current
    network. If this is not the case, an error message is displayed and
    the reading in process is cancelled.
    Ignore
    Ignored are those network objects in the network file being read
    that have identical keys which are already in use in the currently
    open network file. The existing network objects and their attribute
    values remain unchanged.
    Overwrite object/course
    Existing network objects for which the network file contains network objects with identical keys, are replaced by the objects read
    from file. Attribute values of attributes which are not contained in
    the network file are set to a standard value.
    Overwrite attributes
    Existing network objects that have the same keys as objects in
    the network file remain unchanged. Only their attribute values are
    overwritten. Attribute values of attributes which are not contained
    in the network file remain unchanged.
    Overwrite structure
    If the network file contains lanes for a leg, they are overwritten.
    Cancel
    Reading is cancelled.

    3. Confirm with OK.


    It is checked whether the data on the system of coordinates of the network file are identical
    with those of the existing network. Depending on the constellation either a warning or a window opens or the data are read from file without any further query.
    4. Make the desired changes, if applicable.
    Coordinates
    data in the network file

    Coordinates
    Response when read in
    data in the network

    None

    Visum (no pro- The coordinates are read without transformation.


    jection)

    None

    From proThe Select spatial reference system window


    jection file *.prj opens. Select the system of co-ordinates of the net-

    PTVGROUP

    859

    14.4.7.4 Saving settings for reading additional network data


    Coordinates
    data in the network file

    Coordinates
    Response when read in
    data in the network
    work file via option From file. Visum transforms the
    co-ordinates of the network file into co-ordinates of
    the network. If you select the option Visum
    (untransformed reading) instead, the coordinates
    will be read from file without transformation. Confirm with OK.

    From projection
    file *.prj

    Visum (no pro- A warning is issued. Confirm with OK. The coorjection)
    dinates are read without transformation.
    Note
    To match the data, it is generally recommended to
    first change the coordinate system of the network
    (see "Selecting a coordinate system" on page
    2207).

    From projection
    file *.prj

    From proThe data are read without further queries. In case of


    jection file *.prj different co-ordinate systems the co-ordinates of the
    network file will be transformed into co-ordinates of
    the network.

    Note: If the Show the 'Completing line routes' window option has been checked, the
    Read network (completing the courses of line routes/system routes) window
    opens. Here you can specify how you want to add the data (see "Reading a network
    file with incomplete line routes or system routes" on page 861).
    The network data are read in. If you select the option Show statistics of modifications, the
    model transfer file with the changes made is opened. When you close this window, a query
    window is opened that allows you to save or delete the file.
    14.4.7.4

    Saving settings for reading additional network data


    1. Make sure the Read network data additionally window is open (see "Reading network
    data additionally" on page 851).
    2. Make sure the desired options are set (see "Reading network data additionally" on page
    851).
    3. Click the Save button.
    The Save: Parameters for 'Read network additively' window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The settings are saved as *.anrp file.

    860

    PTVGROUP

    14.4.7.5 Opening settings for reading additional network data


    14.4.7.5

    Opening settings for reading additional network data


    1. Make sure the Read network data additionally window is open (see "Reading network
    data additionally" on page 851).
    2. Click the Open button.
    The Open: Parameters for 'Read network additively' window opens.
    3. Select the desired *.anrp file.
    4. Click the Open button.
    The settings are read from file.

    14.4.8

    Reading a network file with incomplete line routes or system routes


    If the network file to be opened contained incomplete line routes or system routes (i.e. one or
    more link or stop point missing in the course of the route or being blocked for the route), you
    can pre-define how to complete the given data when read in.
    1. Open a network file or read network data additionally (see "Opening a network file" on page
    845 and "Reading network data additionally" on page 851).
    2. In the Read network window, select the Show the 'Completing line routes' window option.
    During the reading in process, the Read network (completing the courses of line routes/system routes) window opens.
    3. Make the desired changes.
    Element

    Description

    Transport system From the selection list, select the transport system the settings are
    valid for.
    Delete existing
    line routes after
    reading

    If this option has been selected, all lines defined in the currently
    open network and their corresponding data (line routes etc.) are
    deleted after the reading process.
    Note
    This option is only provided for Read network additionally (see
    "Reading network data additionally" on page 851).

    Stop points section In case of no stop points on nodes


    You can decide how to handle missing stop points in the route.
    Do not create line route
    If this option has been selected, line routes which should use the
    missing stop point of the node are not read in.
    Use stop point of node
    If this option has been selected, the invalid stop point number in
    the route read from file is ignored. The stop point defined (with
    identical number) for the node will be used instead.

    PTVGROUP

    861

    14.4.8 Reading a network file with incomplete line routes or system routes
    Element

    Description
    Create stop point
    If this option has been selected, a stop point with the node's coordinates, code and name is created for each node without stop
    point.
    Notes
    If there is a stop point already, the line route cannot be read in.
    No line route items are created for stop points on links.
    If stop points are closed to this transport system
    You can decide how data shall be adjusted if lines of the selected
    transport system are not permitted to serve certain stop points.
    Do not create time profile
    If this option has been selected, time profiles including stops at
    blocked stop points are not read from file.
    Remove stop event from time profile
    If this option has been selected, time profiles including stop
    events at blocked stop points are read from file but the stop point
    will not be served.
    Open stop point to TSys
    If this option has been selected, time profiles including stop
    events at blocked stop points are read from file and the stop point
    will be opened to the transport system, thus it will be served.

    Links and turns


    section

    862

    Also use closed links for routing


    Select this option to also include links closed for the transport system selected for routing.
    Also use closed turns for routing
    Select this option to also include turns closed for the transport system selected for routing.
    If links are missing or not permitted for this transport system
    The course of existing line routes is to be used first
    If the option has been selected, existing line routes are checked
    to complement the missing section.
    Note
    This option is only provided for Read network additionally (see
    "Reading network data additionally" on page 851).
    If no path was determined this way or else
    You can decide how data shall be adjusted if no appropriate line
    route course could be found due to missing links or blocked links.
    Do not create line route / system route
    If this option has been selected, the routes using the particular

    PTVGROUP

    14.4.8 Reading a network file with incomplete line routes or system routes
    Element

    Description
    links will not be read from file.
    Open existing link or use type to insert new link
    If this option has been selected, blocked links are opened to the
    selected transport system and missing links are created. In the
    list, click the link type you want to use for links newly inserted
    links (see "Specifying link types" on page 1099).
    Search for shortest path
    If this option has been selected, a route course is searched for
    which has to meet certain requirements (shortest path).

    Parameters: Shor- Search criterion


    test path search
    In the list, click the criterion you want to use for the shortest path
    search.
    Link length (direct distance): direct distance link length from
    start to destination stop area
    Link run time: transport system based run time on the link
    Time from speed def. by link type: time calculated from the
    speed defined for the transport system on the respective link
    type
    Link length
    If no shortest path found or length > <factor> direct distance
    You can decide how data is to be adjusted in the event that no
    route course is found that meets the specified conditions or if the
    length of the found route exceeds the direct distance between the
    two stop areas by the indicated factor.
    Enter the desired factor in the input field.
    Do not create line route / system route
    If this option has been selected, line routes and system routes are
    not read from network file.
    Insert only, if link can be opened
    If this option has been selected, line routes and system routes are
    only read from network file if those links can be permitted for the
    selected transport system.
    Insert always; If possible, the link is opened, otherwise it is
    created
    If this option has been selected, line routes and system routes are
    read from network file. Missing links in a route course will be created. In the list, click the link type you want to use for links newly
    inserted links (see "Specifying link types" on page 1099).
    Link type of newly created links
    Here you specify the link type for newly inserted links.

    PTVGROUP

    863

    14.4.9 Starting with an empty program interface


    Element

    Description
    Set the link type of opened links to
    Here you can specify a link type for opened links. This way you
    can tell later which links were opened during the read in process.

    Apply to all transport systems

    Click this button to apply the settings set for the currently selected
    transport system to all transport systems.

    4. Click the >> button.


    The network data is read from file and incomplete line routes and system routes are completed
    according to the current settings.
    Note: Links that are created or opened for route completion will be logged to log file, as
    far as a log file has been opened (see "Specifying settings for protocol files" on page
    876).

    14.4.9

    Starting with an empty program interface


    Note: Prior to starting with an empty program window, you should save your current state
    of work to file (see "Opening and saving files" on page 831).
    1. On the Functions toolbar, click the

    New button.

    Tip: To create a new version, from the File menu, choose> New or press CTRL+N.
    In case of changes to the network that have not been saved to file yet a security prompt
    appears.
    2. Confirm the query with OK.
    The empty program interface is displayed.

    14.5

    Selecting the direction of traffic


    You can define the traffic direction in networks. When creating a new network, you can choose
    another traffic direction than for an opened or saved network.
    Notes: The direction of traffic you should define first for your project and you should not
    edit it later.
    In case of changes to the direction of traffic of an existing network existing node topologies are discarded. The display is not adjusted automatically and calculated assignment results are not reset automatically. Therefore, you should check your complete
    network and your data.
    1. From the Network menu, choose Network settings.
    The Network settings window opens.
    2. Select the Direction of traffic tab.

    864

    PTVGROUP

    14.5.1 Selecting the standard unit for direction of traffic in the current network
    3. Choose either right-hand traffic or left-hand traffic for network modeling.
    4. Confirm with OK.
    A query opens.
    5. Confirm with Yes or Yes for all.
    6. Confirm another security query with Yes.
    In the network, the direction of traffic is changed and existing node topologies (see "Using the
    Junction editor" on page 1435) are deleted.

    14.5.1

    Selecting the standard unit for direction of traffic in the current network
    1. From the Network menu, choose Network settings.
    The Network settings window opens.
    2. Select the Direction of traffic tab.
    3. Choose either right-hand traffic or left-hand traffic for network modeling.
    4. Confirm with OK.
    A query opens.
    5. Confirm with Yes or Yes for all.
    6. Confirm another security query with Yes.
    In the network, the direction of traffic is changed and existing node topologies (see "Using the
    Junction editor" on page 1435) are deleted.

    14.5.2

    Selecting the standard unit for the direction of traffic in the new network
    You can select which traffic direction to set as the default in new networks. Right-hand traffic is
    preselected.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Network>General
    3. Choose either right-hand traffic or left-hand traffic for network modeling.
    4. Confirm with OK.
    The settings are applied.

    14.6

    Specifying standard units for length and speed


    You can choose the units in which length and speed are displayed in the network. When creating a new network, you can choose different units than for an opened or saved network.
    Note: Internally, Visum always uses metric units for computation.

    PTVGROUP

    865

    14.6.1 Selecting the standard unit for lengths and speed in the current network

    14.6.1

    Selecting the standard unit for lengths and speed in the current network
    You can choose the units in which the opened network is displayed and saved in Visum.
    1. From the Network menu, choose Network settings.
    The Network settings window opens.
    2. Select the Units tab.
    3. Select the desired option.
    Element

    Description

    Metric

    Entry in meters, kilometers and kilometers per hour

    Imperial

    Entry in feet, miles and miles per hour

    4. Confirm with OK.


    The settings are applied.
    Tip: You can enter lengths with any unit (m, km, ft, mi). Then Visum will convert the value,
    so that it is displayed in the unit selected.

    14.6.2

    Selecting standard units for length and speed in new networks


    You can choose the units in which length and speed are displayed in new networks. You cannot use this function to change existing networks.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Network> General.
    3. Select the desired option.
    Element

    Description

    Metric

    Entry in meters, kilometers and kilometers per hour

    Imperial

    Entry in feet, miles and miles per hour

    4. Confirm with OK.


    The settings are applied.

    14.7

    Specifying time periods and points in time


    You can enter a time in several dialogs in Visum. Examples are walk times at stops or the
    headway start and end in a tabular timetable.
    You can enter times in the following formats:

    866

    PTVGROUP

    14.8 Editing user preferences


    Time periods
    s (seconds)
    min (minutes)
    h (hours)
    Example: 3s are 3 seconds.
    Tip: If you enter a time period without a unit (s, h or min), it is generally interpreted in
    minutes - in some exceptions in seconds. If you are not sure, we recommend that you
    enter the unit as well.
    Points in time
    hh:mm:ss
    hh:mm
    Example: 06:10:00 stands for the point in time 06:10 a.m.
    You can also enter this point in time as follows: 6,10 or 6:10. If you want to specify 6 o'clock,
    you can simply enter 6.
    In the attribute selection, you specify how you want times output in lists (see "Editing the display properties of attributes" on page 970).
    Note: If you read or set time periods without a unit via COM, e.g. using the AttValue
    method, these are generally interpreted in seconds.

    14.8

    Editing user preferences


    In the User Preferences window (Editmenu > User Preferences), you specify basic settings
    for Visum. These include settings for the user interface, protocols, backup files, standard units
    for length and speed, etc.
    Visum saves the settings and changes made in the User Preferences window (per user and
    installation) to the Windows system database (registry). If you open several instances of Visum
    at the same time, Visum will save the settings made in the instance you closed last to the registry. The settings made in other Visum instances will be lost.
    When you start Visum, it will load the basic settings saved to the registry.
    Note: If you start Visum via the COM interface, your settings made in the User Preferences window will not be saved to the registry when you quit the program. To save
    your settings in this case, set the switch to SaveOptionsToRegistryOnClose.
    User preferences overview
    Saving, opening and restoring user preferences

    14.8.1

    User preferences overview


    From the Edit menu, choose User Preferences.
    The User Preferences window opens. Here you can make the following basic settings:

    PTVGROUP

    867

    14.8.1 User preferences overview


    Navigator
    First level

    Navigator
    Second level

    Description

    GUI

    General

    (see "Restoring window settings" on page 827)


    (see "Specifying the size and position of windows"
    on page 872)

    Lists

    (see "Setting list options" on page 2306)

    Network editor

    (see "Creating a boundary" on page 1042)

    Junction editor

    (see "Adjusting the display and the input options of


    the list view" on page 1440)

    Matrix editor

    (see "Setting options for display in the Matrix window" on page 1758)
    (see "Specifying treatment of division by zero" on
    page 1759)
    (see "Specifying a default value for new relations" on
    page 1759)

    Quick view

    (see "Editing Quick view settings" on page 812)

    Attribute selection

    (see "Specifying settings for the attribute selection


    windows" on page 959)

    Warnings

    (see "Specifying settings for protocol files" on page


    876)

    Miscellaneous

    (see "Setting the reference journey for a time profile"


    on page 1318)
    (see "Displaying document names in progress dialogs" on page 885)

    Background
    map

    (see "Inserting background images of map services


    on the Internet" on page 2237)

    General

    (see "Specifying settings for protocol files" on page


    876)
    (see "Settings for opening and saving data files" on
    page 835)

    Backup copy

    (see "Settings for opening and saving data files" on


    page 835)

    Files & protocols

    Activity protocol (see "Specifying settings for protocol files" on page


    876)
    Matrices

    868

    (see "Specifying settings for treatment of matrices" on


    page 1760)
    (see "Settings for Reading matrix from file in $O format" on page 1761)

    PTVGROUP

    14.8.2 Saving, opening and restoring user preferences


    Navigator
    First level

    Navigator
    Second level

    Description

    Working environment

    General

    (see "Undoing and redoing actions" on page 870)


    (see "Specifying the number of processor cores to be
    used" on page 873)
    (see "Registering Visum version as COM server" on
    page 874)
    (see "Default settings for Visum updates" on page
    875)

    GPS tracking

    (see "GPS tracking" on page 2261)

    Scenario management

    (see "Editing procedure parameter sets" on page


    937)

    General

    (see "Selecting standard units for length and speed


    in new networks" on page 866)

    Links

    (see "Specifying a rounding factor for the PuT run


    time on links" on page 1099)

    Connectors

    (see "Specifying standard values for connectors" on


    page 1159)

    Lines

    (see "Specifying default values for lines and line routes" on page 1291)

    Matrix toll

    (see "Specifying the matrix toll of a toll system" on


    page 1422)

    Turns and main


    turns

    (see "Creating turns" on page 1093)

    Network

    Formats
    (decimal separator)

    14.8.2

    (see "Selecting a decimal point" on page 873)

    Saving, opening and restoring user preferences


    Saving user preferences
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. Click the Save button.
    The Save user preferences window opens.
    3. Select a path and enter the name of the file you want to save.
    The basic settings are saved in XML format to the file you specified.

    PTVGROUP

    869

    14.8.3 Undoing and redoing actions


    Tip: Alternatively, from the File menu, choose> Save as> User Preferences to save
    your basic settings.
    Opening the User preferences window
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. Click the Open button.
    The Open user preferences window opens.
    3. Select the path and name of the file you want to open.
    The basic settings are opened. When you close Visum, they are saved to the Windows registry.
    Tip: Alternatively, from the File menu, choose> Open> User Preferences to open the
    basic settings.
    Restoring the default user preferences
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. Click the Standard values button.
    All basic settings in the User Preferences window are reset to the default standard values.

    14.8.3

    Undoing and redoing actions


    You can undo and redo several changes or actions.
    To undo actions, the UNDO stack must be activated and you need to specify how many actions you want to save for undoing (maximum 50).
    If you undo an action by mistake, you can redo it again.

    14.8.3.1

    Activating the undo command and specifying number of actions


    You can specify whether you want to save actions for undoing and how many.
    Note: If you are working with large networks, it might be advisable not to save any actions
    in order to save memory space.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Working environment> General.
    3. Make the desired changes.

    870

    PTVGROUP

    14.8.3.2 Actions:undoing
    Element

    Description

    UNDO stack is
    active

    Select this option to save the (specified number of) actions last
    performed, so you will be able to undo or redo them later on.
    If this option is not selected, no actions are saved. You can
    then not undo any actions later on.

    Number of stored The number of actions saved that you can undo. You can specify
    actions
    to save a maximum of 50 actions.
    4. Confirm with OK.
    The settings are applied.
    14.8.3.2

    Actions:undoing
    You can either undo the last action or several actions at the same time.
    Notes: When you use certain functions, your last actions are deleted. Then the Undo and
    the Redo buttons are greyed out, showing that you cannot undo any actions. A security
    query will inform you in time as soon as you call such a function.
    1. On the Functions toolbar, next to the

    Undo icon, click the downward arrow.

    The Undo window opens. It shows a list of the last actions performed. The latest action
    undone is listed at the top.

    2. In the list, click the actions you want to undo.


    3. Confirm with OK.
    The actions selected are undone.

    Tip: To undo just the last action, click the


    Undo icon, or select menu Edit> Undo.
    You can also use the shortcut keys C TRL+Z.
    14.8.3.3

    Redoing undone actions


    You can redo one or several of the actions undone.
    1. To do so, on the Functions toolbar, click the downward arrow next to the

    Redo icon.

    The Redo window opens. It shows a list of the actions last undone. The latest action
    undone is listed at the top.

    PTVGROUP

    871

    14.8.4 Specifying the size and position of windows

    2. In the list, click one or several actions that you want to redo.
    3. Confirm with OK.
    The actions selected are redone.

    Tip: To redo the last action undone, click the


    You can also use the shortcut keys C TRL+Y.

    14.8.4

    Redo icon, or select menu Edit> Redo.

    Specifying the size and position of windows


    When starting the program or loading a file you basically define the window display. Hereby,
    the current settings may be kept, for example.
    These settings include the visibility, size and position of the following windows: Network editor,
    Lists, Junction editor, Timetable editor, Schematic line diagram, Transfers display of regular
    services. They also apply for the size and position of all other windows, e.g. the Matrix editor.
    Note: Click the Reset window configuration button to restore the default settings.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> General.
    3. In the Window configuration section, check the desired option.
    Element

    Description

    Always reset

    When you open a version or network file or start the program


    without a version file, the Network editor window opens in full
    screen mode.

    Apply from verWhen a version file is read, the settings saved with the version
    sion file, otherwise are used. If you start the program without a version file or open a
    reset
    network file, the Network editor window opens in full screen
    mode.
    Apply from verWhen a version file is read, the settings saved with the version
    sion file, otherwise are used. Current configuration is kept when a network is read
    retain
    from file. The recently used configuration is used after program
    start without version.
    Always retain

    872

    The current configuration is kept when a network or a version is


    read from file. The recently used configuration is used after program start without version.
    PTVGROUP

    14.8.5 Selecting a decimal point

    Notes: Older version files do not store the window configuration details. If you open
    such a file and click the first option, the Network editor window opens. The current
    configuration is kept when an outdated version is read from file while the last option is
    selected.
    4. Confirm with OK.
    The settings are applied.

    14.8.5

    Selecting a decimal point


    You decide whether a full stop or a comma shall be used as decimal point. This option applies
    to the data display of the graphical user interface and for import and export of data.
    Notes: Right after the installation Visum uses the decimal point as specified by the current settings of system control.
    WindowsXP: Language options> Regional settings tab> Adjust button
    VISTA: Time, Language and Region> Region and Language> Formats tab>
    Adjust this format button
    Windows7: Time, Language and Region> Region and Language> Edit date, time
    or number format> Formats tab> Further settings button
    When exporting data, you should select the same decimal point as in the program in
    which you want to open the data.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Formats.
    3. In the Decimal separator section, select the desired option.
    4. Confirm with OK.
    The settings are applied.

    14.8.6

    Specifying the number of processor cores to be used


    If you work with a computer with more than one processor core, you can specify how many
    cores shall be used for certain calculations.

    PTVGROUP

    873

    14.8.7 Registering Visum version as COM server


    Notes: Currently Visum can perform the following calculations on several processor
    cores at the same time:
    Headway-based or timetable-based assignment
    Equilibrium assignment LUCE
    HBEFA calculation (partially)
    Equilibrium_Lohse, stochastic assignment, dynamic stochastic assignment
    PrT skim matrix calculation
    PuT operating Indicators
    Flow bundle (PrT, PuT)
    OD pair filter evaluation of network volumes (PrT, PuT)
    4-step model for trip distribution
    EVA weighting, EVA trip distribution and mode choice
    Tour-based model - Combined trip distribution / mode choice
    Line blocking with vehicle interchange
    Import and export of PuT connections
    Edit attribute
    The more processor cores you use, the faster the computation speed. However, rounding
    deviations may occur. To avoid these please use only one core.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Working environment> General.
    3. In the CPU selection list, select the appropriate entry.
    4. Confirm with OK.
    The settings are applied.
    Note: If you want to execute the Equilibrium assignment LUCE procedure, the number of
    processor cores has to be defined with the procedure parameters. This parameter setting
    overrules the global settings (see "Parameters of Equilibrium assignment LUCE" on
    page 1941).

    14.8.7

    Registering Visum version as COM server


    You can install the same Visum version several times on your computer. With the installation
    of Visum the currently installed instance is automatically registered as COM server. If you want
    to use a different Visum instance with the same version number as COM server, you have to
    register it first.
    1. Open the desired Visum instance.
    2. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    3. In the navigator, select Working environment> General.

    874

    PTVGROUP

    14.8.8 Default settings for Visum updates


    4. Click the Register as COM server button.
    5. Click OK to confirm.
    The instance is registered as COM server.

    14.8.8

    Default settings for Visum updates


    You can specify default settings for updates. This way you make sure that the options of your
    choice are automatically set after the next Visum update.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Working environment> General.
    3. Make the desired changes.
    Element

    Description

    Preset option
    'Register as COM
    server'

    Select this option to automatically activate the option Register as


    COM during the next Visum update.

    Preset option
    'Associate .ver
    files with Visum'

    Select this option to automatically activate the option Associate


    .ver files with Visum during the next Visum update.

    4. Confirm with OK.


    The default settings for the options are now made for the Visum updates.

    14.8.9

    Language of the graphical user interface


    During a program session, you can change the language in the GUI.
    Note: Therefore, a multi-language program version is required.
    1. From the Help menu, choose License.
    The License window opens.
    2. In the Language section, select the language you would like to use from selection list 1.
    3. Select other languages in selection list 2 and selection list 3, if applicable.
    Note: If warnings, properties etc. are not available in language 1, language 2 will be
    used instead or language 3, if this text is not available in language 2 either.
    4. Confirm with OK.
    The language used in the program is changed.

    PTVGROUP

    875

    14.8.10 Using protocol files

    14.8.10 Using protocol files


    Visum can log actions, program events, and errors and save them to different files. All three
    types of protocol files are text files whose character code you can change (see "Settings for
    opening and saving data files" on page 835).
    Protocol file Standard
    file name
    Log file

    Protocol.txt

    Meaning
    The log file logs the procedure, including start and end times of
    the procedure steps, all steps carried out as well as internal
    program procedures and their details. It, for example, contains
    details on the number of iterations during assignments or additional statistics.

    Message file Messages.txt Message files include all error messages, notes, warnings and
    messages displayed on the program interface, as well as user
    responses. Each message has a timestamp and a message
    type ID. Especially when procedures are performed one by
    one or a script file is run, the combination of warnings and
    error messages in a single file might be helpful.
    Running a script file does not produce messages on
    screen. Thus errors do not become obvious. The message
    file allows you to check error messages.
    Prior to starting a procedure sequence you can select
    option Suppress output of warnings during procedure
    execution for an uninterrupted run. The message file
    allows you to check warnings.
    Activity protocol

    [Filename].trc

    The activity protocol logs the user actions. The number of logged user actions depends on the selected level of detail. The
    activity protocol file has the same name as the file being
    currently open (version file, network file or database) and the
    file extension is .trc. It will be stored in the same directory as
    soon as the open file is saved. For each version, network or
    database respectively exactly one activity protocol is created.

    14.8.10.1 Specifying settings for protocol files


    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Files & protocols> General.
    3. In the Message file (messages.txt) section, make the settings of your choice.

    876

    PTVGROUP

    14.8.10.1 Specifying settings for protocol files


    Element

    Description

    Write no file

    Use this option if you do not want to save errors to a message file.

    Create new file Use this option if you want to save errors to a new message file.
    Note
    If there is already a message file during program start, it is overwritten. If this is not possible, then file Messages1.txt will be created.
    Continue with
    file, if existing.
    Otherwise
    create new file.

    Click this option to save errors to an existing error file.


    Note
    If there already is an error file, it is updated during program start.
    Otherwise a new Messages.txt file is created.

    4. Make the desired changes in the Log file (protocol.txt) section.


    Element

    Description

    Write no file

    Use this option if you do not want to save a log file.

    Create new file Use this option if you want to save a new log file.
    Note
    If there is already a log file during program start, it is overwritten. If this
    is not possible, then file Log1.txt will be created.
    Continue with
    file, if existing.
    Otherwise
    create new file.

    Use this option to specify that information is recorded to an existing


    log file.
    Note
    If there is already a log file during program start, it is overwritten.
    Otherwise a new Protocol.txt file is created.

    Note: By default, the message file and log file are saved to the folder specified in the
    project directory file for the Log file (see "Editing the storage location of files" on page
    837). You can change this setting (see "Starting Visum with different settings" on page
    887).
    5. In the navigator, select GUI> Warnings.
    6. Make the desired changes.
    Element

    Description

    Save warnings and


    notes to the message
    file

    Click this option to save warnings and notes (e.g. when a


    network or demand data is read in), in addition to error messages, to the error file.

    Suppress output of war- Via this option you decide, that warnings which do not endnings during procedure

    PTVGROUP

    877

    14.8.10.1 Specifying settings for protocol files


    Element

    Description

    execution

    anger the running procedures shall not be displayed on


    screen. This is especially helpful in case of iterative runs of
    operations (including Go to the operation), since the running operations are not interrupted unnecessarily.
    Note
    Warnings indicating that a procedure cannot be run are still
    issued on screen. Alternatively, you can show warnings in
    the Messages window (see "Messages window" on page
    883).
    Tip
    Suppressed warnings you can log to the message file and
    check them subsequently.

    Display warnings when


    saving

    Via this option, you decide whether a security query shall


    be prompted if a version is saved under the same name
    of an existing file (see "Settings for opening and saving
    data files" on page 835).

    7. In the navigator, select Files & protocols> Activity protocol.


    8. Make the desired changes.
    Element

    Description

    Level

    Via this selection list you decide whether the activity protocol is to be
    saved and which of the provided levels of detail is to be used.
    0 - No protocol: Visum saves no activity protocol.
    1 - Top Level activities: Any transactions, calculations, and operations that generate new networks will be recorded.
    2 - all activities: Any top level activities and actions will be recorded.
    3 - all activities in detail: Any top level activities and Edit actions
    will be recorded with attribute data (old and new values).
    4 - all activities in max. detail: Any top level activities and delete
    actions will be recorded with all of the old attributes and values.

    User

    With the changes, the entered name will be saved to the activity protocol.

    Watch size

    Via this option you specify, whether Visum issues a security query as
    soon as the user-defined size of the protocol file is exceeded.
    Note
    When the security query is issued, you can decide to either continue or
    quit recording.

    9. Confirm with OK.

    878

    PTVGROUP

    14.8.10.2 Adding a comment to the activity protocol


    The changes are applied.
    Note: Your settings are applied immediately. You do not have to restart Visum.
    14.8.10.2 Adding a comment to the activity protocol
    1. Make sure that the activity protocol is saved (see "Using protocol files" on page 876).
    2. In the Edit menu, click the Comment in activity protocol entry.
    The Comment activity protocol window opens.
    3. Enter the desired comment.
    4. Confirm with OK.
    The comment is added to the activity protocol as a separate row.
    14.8.10.3 Viewing log files
    You can view log files saved to the log file folder specified (see "Editing the storage location of
    files" on page 837).
    1. From the File menu, choose Show log files.
    The Log files window opens.
    2. Click the desired file.
    3. Click the Open button.
    The file opens in a text editor window.
    14.8.10.4 Examples: Protocol files
    Here you can find examples of a log file, message file, and an activity protocol.
    Log file Log.txt Example (excerpt)
    Read version D:\Visum\EXAMPLE.VER
    Reading version from file, start at 5/27/10 16.19.26
    5 Transport systems
    3 Modes
    3 Demand segments
    1 Calendar period
    1 Valid days
    2 Vehicle units
    2 Vehicle combinations
    2 Directions
    2 Operators
    2 Points
    2 Edges
    2 Faces
    2 Surfaces
    9 Nodes
    2 Zones
    100 Link types
    22 Links

    PTVGROUP

    879

    14.8.10.4 Examples: Protocol files


    56 Turns
    4 Connectors
    4 Stops
    4 Stop areas
    4 Stop points
    4 Transfer walk times between stop areas
    1 Fare systems
    2 Lines
    4 Line routes
    4 Time profiles
    12 vehicle journeys
    4 Specific transition times
    1 Block versions
    3 Matrices
    1 Time series
    1 Demand time series
    6 Goodness of PrT assignment
    13 Turn standards
    End time of Read version from file 5/27/10 16.19.26
    27.05.10 16.25.55 Procedure - start
    27.05.10 16.25.55 Start Procedure step 1: "PrT assignment"
    The shortest path graph has been reduced by 61.5%
    Iteration 1 DSeg C Routes tot. 1
    The shortest path graph has been reduced by 61.5%
    Iteration 1 DSeg H Routes tot. 1
    The shortest path graph has been reduced by 61.5%
    Iteration 2 DSeg C Routes tot. 2
    The shortest path graph has been reduced by 61.5%
    Iteration 2 DSeg H Routes tot. 1
    The shortest path graph has been reduced by 61.5%
    Iteration 3 DSeg C Routes tot. 3
    The shortest path graph has been reduced by 61.5%
    Iteration 3 DSeg H Routes tot. 2
    Iteration
    1 Network balancing partial step
    1 modified OD
    pairs
    1 totalExcessCost 1842164.00000000 avgExcessCost 837.34727273
    Iteration
    1 Network balancing partial step
    2 modified OD
    pairs
    0 totalExcessCost 46596.44689264 avgExcessCost 21.18020313
    Iteration
    1 Number of deleted paths after OD balancing 0
    Iteration
    1 Number of deleted paths after network balancing 0
    The shortest path graph has been reduced by 61.5%
    Iteration 2 DSeg Car Routes tot. 3 Routes new 0
    The shortest path graph has been reduced by 61.5%
    Iteration 2 DSeg HVeh Routes tot. 2 Routes new 0
    Iteration
    2 gap 0.01311459
    Equilibrium assignment finished after 2 iteration steps
    27.05.10 16.25.55 Time before WBRePack
    27.05.10 16.25.55 Time after WBRePack
    27.05.10 16.25.55 Time before WBRePack
    27.05.10 16.25.55 Time after WBRePack
    27.05.10 16.25.56 Start Procedure step 2: "PuT assignment"
    Assignment with 3 computation core(s)
    Assignment after Init 5/27/10 16.25.56
    Search from zone 100: Search tree dimension = 28, time = 0s
    Number of calculated search runs 1

    880

    PTVGROUP

    14.8.10.4 Examples: Protocol files


    Time Search
    = 0s
    Time Choice
    = 0s
    Time Storage = 0s
    Time Skims = 0s
    Time Summary = 0s
    27.05.10 16.25.56 End of assignment
    Save version D:\Visum\EXAMPLE_test

    Message file Messages.txt


    (incomplete)
    Save matrix E:\Usability\Quickstart\oev_test.MZW not possible!!
    Incorrect skim parameters, no assignment result calculated
    No OD demand for any OD pair. Assignment is not possible.

    Activity protocol [Version name].trc


    The file usually saves one row per operation. Each row consists of 5 entries which are separated by TAB:
    <Time> <Record code> <User> <RefObject> <Description>

    <Time>
    The <Time> entry contains the timestamp of execution (local time) in the following format
    YYYY-MM-DD hh:mm:ss. The particular entry is usually written before executing an operation
    so that crashes can be allocated.
    <Record code>
    Field <Record code> may contain the following values:
    Record code

    Meaning

    TRDO_S

    Transaction in Do-Direction: Start

    TRDO_E

    Transaction in Do-Direction: End (successful, commit)

    TRDO_C

    Transaction in Do-Direction: Cancelled (cancel)

    TRUNDO_S

    Transaction in Undo-Direction: Start

    TRUNDO_E

    Transaction in Undo-Direction: End

    TRREDO_S

    Transaction in Redo-Direction: Start

    TRREDO_E

    Transaction in Redo-Direction: End

    Command (in Do/Redo-Direction)

    Command (in Undo-Direction)

    File-I/O (Version, Network, Subnetwork, Database)

    Procedure (Assignment, ...)

    Changes to trace settings

    Comment (user entry ) (see "Adding a comment to the activity protocol"


    on page 879))

    Continuation line

    PTVGROUP

    881

    14.8.10.4 Examples: Protocol files


    <Reference object>
    Record code

    Reference object

    Transactions start/ end/ canceled

    Empty

    Commands that refer to a single


    network object

    Name of the network object type + Blank + ExternalKeyString

    Other commands

    Empty

    File I/O

    File name, exceptions:


    for Read Attributes via clipboard empty
    for Import from several files (e.g. TModel) empty

    Procedure

    Reference object(s) Procedures

    Changes to trace settings

    Empty

    Comment

    Empty

    Continuation line

    Empty

    <Description>
    Depending on the trace level, field <Description> contains variably detailed descriptions of the
    operations.
    Record code

    Trace Description
    level

    Transactions start/
    end/ canceled

    >0

    <Name of transaction>

    Create command

    >1

    Create

    Edit command

    Edit

    3+4

    Edit in the first row, in other rows each


    <Attribute short name>: <old value> -> <new value>
    (for all edited input attributes)

    <Network object type> Multi-Edit

    3+4

    in the first row <Network object type> Multi-Edit, Attribute


    <Attribute short name>,
    in any further row each
    <ExternalKeyString>: <old value> -> <new value>

    2+3

    Delete

    Delete in the first row, in other rows each


    <Attribute short name>: <old value>
    (for all input attributes with a value different from the standard value)

    Other commands

    >0

    Individual descriptions

    File I/O

    >0

    Save version to file / Save network / Save sub-network /

    Multi-edit command

    Delete command

    882

    PTVGROUP

    14.8.11 Messages window


    Record code

    Trace Description
    level
    Save database / Read version from file / Read network/database / Read additionally network/database /
    Read EDF / Read HAFAS / Read EMME / Read TModel /
    Read attributes

    Procedure

    >0

    Consecutive number + Blank + Operation + Blank + Procedure / File

    Changes to trace set- All


    tings

    Trace on Level X / Trace off / New trace level X

    Comment

    Text entry by user

    All

    Example of an activity protocol of level 4:

    14.8.11 Messages window


    The Messages window contains the message file and log file (see "Viewing log files" on page
    879). Additional information is added to these files that allows you to access network objects.
    You can analyze Visum's info messages, e.g. infos, warnings or safety prompts, in a separate
    window.
    The list entries are displayed in different colors.

    PTVGROUP

    883

    14.8.11 Messages window


    Font color

    Description

    Gray

    Entry refers to a network that no longer exists, e.g. after you have loaded or created a new network.

    Black

    Entry refers to he network currently open. There is no object that can


    be displayed in the Network editor window.

    Blue

    Entry refers to the network currently open. Synchronization with the


    Network editor window is possible. The network object belonging to
    the entry can be highlighted in the network.

    1. From the View menu, choose Messages.


    The Messages window opens.
    2. Click the icons to make the settings of your choice.
    Icon

    Name

    Description

    Select priorities to be dis- Click the icon to open the Select priorities window.
    played
    You can choose the types of entries you want to
    show in the list.
    Errors
    Warnings
    Notes
    System messages
    Find...

    Find

    Enter a search term that is searched for in full-text


    mode in the messages displayed. To start the first
    search, pressing ENTER.

    Find next

    Starts searching the messages displayed for the


    next search term in the Find... box.

    Do not show again

    The list entries selected are not shown again.


    Note
    You cannot undo this action.

    No synchronization with
    network editor

    The Messageswindow is not synchronized with


    other windows.

    Synchronization with net- If possible, network objects highlighted in the Meswork editor: Mark
    sages window are highlighted in other windows
    and vice versa.

    884

    PTVGROUP

    14.8.12 Displaying document names in progress dialogs


    Icon

    Name

    Description

    Synchronization with net- If possible, network objects highlighted in the Meswork editor: Mark and
    sages window are highlighted in other windows. If
    shift view
    required, the network section is shifted in such a
    way that all marked objects are visible.
    Synchronization with net- If possible, network objects highlighted in the Meswork editor: Mark and
    sages window are highlighted in other windows.
    auto zoom
    Additionally, in the network an auto zoom is carried
    out for the marked objects.
    In the Messages window, you can view the following data:
    Element

    Description

    Time

    Time, in the format hh:mm:ss, when the message was saved.

    Priority

    Priorities of the messages. You can choose among the


    following options to show:
    Errors
    Warnings
    Notes
    System messages

    Type

    Network object type affected by the message.

    ID

    Network object ID number

    Message text

    Message text of the files messages.txt or protocol.txt

    14.8.12 Displaying document names in progress dialogs


    If calculations are executed in parallel with multiple Visum instances, multiple progress dialogs are displayed. To be able to distinguish those, it may be useful to display the name of the
    respective network in the title of the progress dialog.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> Miscellaneous.
    3. Then select the Show document name option.
    4. Confirm with OK.

    14.9

    Displaying information about Visum


    You can display various information on your Visum installation, for example about network version, add-on modules and dongle etc. and also for support and updates.

    14.9.1

    General information on Visum


    1. From the Help menu, choose About.

    PTVGROUP

    885

    14.9.2 Displaying details on program and license


    The PTV Visum window appears.

    Tip: Alternatively, on the Functions toolbar, click

    to open the window.

    Note: From here you have access to the homepage of PTV AG. There, you can make
    support requests and download updates (see "Service & Support" on page 10).
    2. Click the Close button.

    14.9.2

    Displaying details on program and license


    You can gain information on dongle, network size, installed add-ons, version number, build
    number and installation directory of your software.
    1. From the Help menu, choose License.
    Tip: Alternatively, press C TRL and P to open the window.
    The License window opens.
    Note: Here you can switch to another language for operating the program and enable
    or disable installed add-ons (see "Language of the graphical user interface" on page
    875 and "Enabling or disabling installed add-ons" on page 886).
    2. Confirm with OK.

    14.10

    Enabling or disabling installed add-ons


    If required, you can enable or disable installed add-ons. Thus, you can for example disable
    program elements which are currently not required, for a better overview of your project.
    Note: You can activate or de-activate add-on modules automatically during program start
    via a command line parameter using their short cut (see "Specifying command line parameters for the start of Visum" on page 887).
    1. From the Help menu, choose License.
    The License window opens.
    2. In the Add-on modules section, make the desired changes.
    Note: Options grayed out indicate an add-on which has not been installed with the
    program (see "Add-ons" on page 5).
    3. Confirm with OK.
    The changes are applied.

    886

    PTVGROUP

    14.11 Starting Visum with different settings


    Note: This configuration is saved to the Registry when the Visum session is terminated
    and will be used automatically when the program is started again.

    14.11

    Starting Visum with different settings


    During program start, Visum uses the configuration file (*.cfg ) which stores references to other
    files. These files are either automatically opened during program start or updated by default.
    By default Visum uses the settings of the configuration file ...\PTV Visum 13\exe\VISUM.cfg .
    There are three ways to start Visum with different settings:
    Enter the particular settings in the command line of your Visum start connection. They will
    overwrite the settings of the configuration file.
    Edit the settings in the standard configuration file ..\PTV Visum 13\exe\Visum.cfg. Then,
    Visum will always use these settings for program start.
    Create a copy of the file Visum.cfg for example a separate one for each project and
    rename it or save it to a different folder. In this file you can adopt the settings to your project. Then you create a connection to Visum and enter the name of the newly created configuration file. In this way you can start Visum with project-specific settings.
    Note: Changes to the configuration of Visum should only be performed by experienced
    Visum users.
    Furthermore you can start Visum without graphical user interface.

    14.11.1 Specifying command line parameters for the start of Visum


    You can create a shortcut to start Visum in which you specify your settings.
    1. On your desktop, create a shortcut to the file
    ...\Program Files\PTV Vision\PTV Visum 13\Exe\Visum13.exe.
    2. Right-click the shortcut.
    The shortcut menu opens.
    3. Select the Properties entry.
    The Properties of Visum window opens.
    4. Select the Reference tab.
    5. In the Target entry field, add a blank at the end and the desired parameter(s).
    Notes: A path that contains a blank needs to be put in quotes.
    Multiple parameters need to be separated by blanks.

    PTVGROUP

    887

    14.11.1 Specifying command line parameters for the start of Visum


    Parameters

    Description

    -f <Directory and name Specifies the message file in which error messages are output
    of message file>
    (see "Using protocol files" on page 876)
    -g <Directory and
    Opens the specified graphic parameters file (see "Printing the
    name of graphic para- network display" on page 2499)
    meters file>
    -h <Directory and
    name of version file>

    Opens the specified version file (see "Opening a version file"


    on page 840)
    Example: -h D:\ProjectA\ProjectA.ver

    -l<3-digit language
    code>

    Starts Visum in the desired language, if available.


    Example: The parameter -IDEU starts Visum in German.
    Note
    Currently available languages are: German (DEU), English
    (ENG), French (FRA), Italian (ITA), Spanish (ESP), Portuguese
    (POR), Polish (POL), Russian (RUS), Hungarian (MAG), Greek
    (GRE), Chinese (CHI), and Japanese (JAP)

    -modoff<Add-on
    module>

    Deactivates an add-on module


    Example: -modoffPUT
    Notes
    Here you have to use the defined codes of the add-on modules (see "Add-ons" on page 5).
    Some add-on modules only make sense in combination with
    others. Thus, it may occur that further add-on modules will be
    deactivated at the same time.
    You can enable the add-on module again after program start
    (see "Enabling or disabling installed add-ons" on page 886).
    You can also start Visum without the user interface (see "Starting Visum without graphical user interface" on page 892).

    -modon<Add-on
    module>

    Activates an add-on module, if available


    Example: -modonPUT
    Note
    Here you have to use the defined codes of the add-on modules (see "Add-ons" on page 5).

    -nw

    Suppresses the message when opening a read-only version


    file

    -o <Directory and
    Opens the specified list layout file (see "Adjusting the list layname of list layout file> out" on page 2308)
    -p <Directory and
    name of project directory file>

    888

    Opens the specified project directory file (see "Opening a project directories file" on page 839)

    PTVGROUP

    14.11.2 Changes to settings in the configuration file


    Parameters

    Description

    -reg

    Registers Visum as COM server. An additional message


    appears.

    -regs

    Registers Visum as COM server without further query

    -regserver

    Corresponds to -reg

    -s

    Saves the version file under the same name without a prompt
    and then quits Visum

    -t <Directory and name Specifies log file to which the information is recorded (see
    of log file>
    "Using protocol files" on page 876)
    -u <Directory and
    name of procedure
    parameters file>

    Opens specified procedure parameters file (see "Saving procedure parameters to a file and loading them from a file" on
    page 1867)

    -unregserver

    Deletes the registration of the Visum instance as COM server

    -VJ

    Enlarges windows in Visum

    -x

    Executes the current procedure sequence. Warnings are not


    displayed, errors lead to cancellation of the procedure.

    6. Confirm with OK.


    This reference is saved to Settings on your personal computer. Your parameter settings will be
    regarded for Visum program start via this reference.

    14.11.2 Changes to settings in the configuration file


    1. Use a text editor to open the configuration file.
    Note: After installation, you can find the standard configuration file under ...\Program
    files\PTV Vision\PTV Visum 13\exe\VISUM.cfg
    Entry

    Standard

    Description

    * -E
    EmissionFile

    EMISS.DAT

    Emission calculation factors published by


    the Swiss Federal Department for Environment and Environmental Impact Assessments read in during program start
    Note
    You should not edit this setting.

    * -F
    MessagesFile

    Messages.TXT

    Message file to which error messages are


    output (see "Using protocol files" on page
    876)

    * -G

    STD.GPA

    Graphic parameters (binary format) that are


    read during program start (see "Reading

    PTVGROUP

    889

    14.11.2 Changes to settings in the configuration file


    Entry

    Standard

    Description

    GParFile

    and saving the graphic parameters of the


    network window" on page 2496)

    * -H
    VersionFile

    Network version file to be opened during


    program start (optional) (see "Opening a version file" on page 840)

    * -0
    StdListLayoutPath

    Standard list layout which is read during program start (optional) (see "Adjusting the list
    layout" on page 2308)

    * -P
    PathFile

    STD.PFD

    Standard project directories to be read


    during program start (see "Opening a project directories file" on page 839)

    * -R
    RlsFile

    RLS.DAT

    Correction factors for different types of road


    surfaces for noise emission calculation
    which are read during program start
    Note
    You should not edit this setting.

    * -T

    Protocol.TXT

    Log file to which records are logged (see


    "Using protocol files" on page 876)

    LogFile
    * -U
    ProceduresettingsFile

    Procedure parameters read during program


    start (optional) (see "Saving procedure parameters to a file and loading them from a file"
    on page 1867)

    2. Edit the desired paths and file names.


    Note: You can enter the file name with or without path/directory. If only the file name is
    entered, Visum checks the directory currently set for this file type in the Project directories file (see "Opening and saving a project directories file" on page 838).
    3. If necessary, save the configuration file to another directory and/or with a different file name.
    Note: To avoid overwriting by a program update we recommend to store this file in a
    folder different from the program folder or to change the file name at least. If, for example, you stored the file together with your project data, you could save all data to
    archive together.
    The configuration file is saved. If you have saved the file to another directory or under a different file name, you must specify that it is used during program start (see "Using a different
    configuration file during program start" on page 891).
    Example: User-defined configuration file
    * -E

    890

    PTVGROUP

    14.11.3 Using a different configuration file during program start


    EmissionFile
    emiss.dat
    * -F
    MessagesFile
    C:\Projects\Project_xy\ProtocolFiles\Messages
    * -G
    GParFile
    C:\Projects\Project_xy\ListLayout\Layout.gpa
    * -H
    VersionFile
    C:\Projects\Project_xy\Version_B.VER
    * -0
    StdListLayoutPath
    C:\Projects\Project_xy\ListLayout\Layout.lla
    * -P
    PathFile
    C:\Projects\Project_xy\aktdrv.pfd
    * -R
    RLSFile
    rls.dat
    * -T
    LogFile
    C:\Projects\Project_xy\ProtocolFiles\Protocol.txt
    * -U
    ProceduresettingsFile
    C:\Projects\Project_xy\ProcSettings\PrPar.par

    .TXT

    14.11.3 Using a different configuration file during program start


    You can specify that Visum shall use another configuration file for program start. Additionally,
    you can define further parameters.
    1. On your desktop, create a shortcut to the file
    ...\Program Files\PTV Vision\PTV Visum 13\Exe\Visum13.exe.
    2. Right-click the shortcut.
    The shortcut menu opens.
    3. Select the Properties entry.
    The Properties of Visum window opens.
    4. Select the Reference tab.
    5. In the Target entry field, delete the name of the specified configuration file at the end, if applicable.
    6. To the Target entry field, add a blank at the end and the complete path to the particular configuration file.
    Note: A path that contains a blank needs to be put in quotes.
    7. Add further parameters, if necessary (see "Specifying command line parameters for the
    start of Visum" on page 887).
    8. Confirm with OK.
    This reference is saved to Settings on your personal computer. Your parameter settings will be
    regarded for Visum program start via this reference.
    Note: If you have specified different settings via parameters in the Target entry field, the
    respective configuration file entries are ignored and the Target parameter settings are
    used.
    PTVGROUP

    891

    14.11.4 Starting Visum without graphical user interface

    14.11.4 Starting Visum without graphical user interface


    You may use Visum without GUI for COM applications.
    1. On your desktop, create a shortcut to the file
    ...\Program Files\PTV Vision\PTV Visum 13\Exe\Visum13.exe.
    2. Right-click the shortcut.
    The shortcut menu opens.
    3. Select the Properties entry.
    The Properties of Visum window opens.
    4. Select the Reference tab.
    5. To the Target entry add a blank at the end and parameter -modoffUI.
    6. Confirm with OK.
    This reference is saved to Settings on your personal computer. If you double-click this reference, Visum will start without GUI. In your Windows GUI you can see the Visum icon in the
    Windows tool bar bottom right.
    Notes: In the Windows tool bar, right click the Visum icon to open the context menu and
    terminate your Visum session.
    The setting to start Visum without GUI is saved to the registry when the session is terminated. Therefore, you have to specify explicitly if you want to start Visum with GUI
    again. There are two possibilities.
    Right-click the Visum icon in the Windows tool bar and select Visible after restart.
    Start Visum with the -modonUI parameter.
    Tip: Alternatively, you can start Visum via COM interface without GUI. To do so, you have
    to register the desired Visum instance as COM server (see "Registering Visum version as
    COM server" on page 874).

    14.12

    Comparing and transferring versions and networks


    Visum offers various possibilities to compare and transfer transport networks and version files
    (see Fundamentals: Chpt. 2.5 , page 22):
    Comparing versions
    Merging networks
    Creating and applying model transfer files
    Scenario management is its most comprehensive solution (see "Scenario management" on
    page 921).

    14.12.1 Comparing versions


    You can compare two version files. For this purpose, you enable an open version file to
    access the attribute values of a second version. For a version comparison, two variants are

    892

    PTVGROUP

    14.12.1.1 Specifying a network name for version comparison


    provided. With the first variant, you adopt the attributes from the comparison network into the
    opened network. With the second variant, you also account for indirect attributes. In contrast to
    the first variant, the attributes of the comparison network are not transferred, but connected by
    relations and will constantly be updated as long as the comparison network is open (see Fundamentals: Chpt. 2.5.1 , page 23).
    14.12.1.1 Specifying a network name for version comparison
    You can specify a name for each network you want to use in version comparison and scenario
    management, in order to identify the network attributes.
    1. Open the desired version file.
    2. In the Network menu, select the Network settings entry.
    3. Select the Network name tab.
    4. Into the Name of network for version comparison, enter a name of your choice.
    5. Confirm with OK.
    The name of the network is saved.
    14.12.1.2 Comparing version files
    1. Open the desired version file.
    2. From the File menu, choose Compare and transfer networks.
    3. Then click Version comparisons.
    The Version comparisons window opens.
    4. Click the

    Add button.

    The Generate version comparison window opens.


    5. Make the desired changes.

    PTVGROUP

    893

    14.12.1.2 Comparing version files


    Element

    Description

    Type of version
    comparison

    Under Options, you specify the version comparison variant you


    want to use.
    Use attribute from comparison network
    If this option has been checked, the attributes are transferred from
    the comparison network and will be stored with the version. In the
    Version comparisons window, the word "attribute" is added to
    the beginning of the version comparison code.
    Load the comparison network as background
    If this option has been checked, access to all attributes is provided by a relation to the comparison network as long as this network is loaded in the background. The attributes of the
    comparison network will not be stored with the version, but will be
    displayed again as soon as the file is re-opened. In this case, the
    program must find the comparison network at the directory location you specified under Version file. You can edit the path to the
    comparison network when updating the comparison (see "Updating version comparisons" on page 902).
    In the Version comparisons window, the words "comparison network" are added to the beginning of the version comparison
    code.
    Note
    For a detailed description of the differences between these two
    version comparison variants please refer to the 'Fundamentals'
    (see Fundamentals: Chpt. 2.5.1 , page 23).

    Version file

    icon select the version file with which you want to comVia the
    pare the current version.

    Code

    Unique code for version comparison


    Notes
    The code is used for IDs and attribute names. It must not contain
    blanks.

    Use the same


    comparison attributes as for

    If this option has been selected, you can select an existing version comparison from the list whose comparison attributes will be
    used.
    If this option has been selected, the next attribute selection window does not open.
    Note
    This option is available if you have selected Use attributes from
    comparison network.

    Do not adopt matri- Click this option if you do not want to adopt matrices from the comces
    parison network. Then less storage space is required.

    894

    PTVGROUP

    14.12.1.2 Comparing version files


    Element

    Description
    Note
    This option is available if you have selected Load comparison
    network in the background.

    Change link bars


    automatically to
    differences

    If this option has been selected, scaling and classification attributes of link bars are automatically converted to the new attribute
    generated by the version comparison with the difference between
    the original and the newly added attribute value.

    6. Confirm with OK.


    The Create version comparison (User-defined) window opens.
    Note: This window is not displayed if you selected the options Use the same comparison attributes as for or Load comparison network in the background as a version comparison.
    7. If required, reduce the amount of data you want to compare.
    Element

    Description

    Hiding calculated
    attributes

    If this option has been selected, only selected readable attributes and their values are compared additionally to the key attributes.
    If this option has not been selected, both readable and non-readable attributes and their values are compared.

    Hide attribute with


    If this option has been selected, only selected attributes and
    default values
    their values are compared.
    If this option has not been selected, all selected attributes and
    their values are compared, disregarding whether attribute value
    and default value are identical or not.
    Note
    You can find the default attribute values in the Attribute.xls file,
    under ...\Program files\PTV Vision\PTV Visum 13\Doc.
    Hide empty tables If this option has been selected, only tables containing network
    objects are compared.
    8. Select the network object types to be compared.
    Element

    Description
    This network object type is used for comparison.
    This network object type is not used for comparison.

    PTVGROUP

    895

    14.12.1.2 Comparing version files


    Element

    Description

    Check all tables Click this button to select all network object types.
    Uncheck all
    tables

    Click this button to deactivate all network objects and their attributes.

    9. Click a network object type.


    The attributes and, if applicable, the subattributes of the network object type are displayed.
    Tip: Click the CTRL key and keep it pressed while clicking the desired entries one by
    one to show the attributes of multiple network object types at the same time.
    Note: Due to current settings in the upper section of the window not all attributes of a
    network object type may be displayed.
    10. Select the attributes and subattributes you want to compare.
    Element

    Description
    The attribute has been selected and is compared.
    The attribute has not been selected and is not compared.
    The attribute is a key attribute and cannot be switched off.
    The attribute is a mandatory attribute.

    Attribute
    groups

    Via this button you can either select or switch off predefined groups of
    attributes in a separate window (see "Selecting or deselecting groups
    of attributes for comparison" on page 897).

    Standard

    Click this button to hide empty tables and display calculated attributes. The attribute selection is reset to the standard setting.

    Tip: Right-click a network object type. Then use the context menu to activate or deactivate all currently displayed attributes of the network object type.
    Tip: Alternatively, you can read selected network object types and attributes from a
    network file *.net (see "Reading a layout from a network file" on page 898).
    11. Confirm with OK.
    The versions are compared. In the Version comparisons window, the version comparison is
    listed.

    896

    PTVGROUP

    14.12.1.2 Comparing version files


    Notes: Version comparisons of the type Use attributes of comparison network are marked with a plus sign. Click the plus sign to show the attributes of the respective version
    comparison.
    If you move the mouse pointer over the entry, the quick info provides additional information on time and date of the version comparison and the date of the version file used
    for comparison.
    Further version comparisons can be added in the same way.
    You can save the version file including the version comparison.
    Selecting or deselecting groups of attributes for comparison
    1. Make sure that the Create version comparison (User-defined) window is open (see "Comparing version files" on page 893).
    2. Click the Attribute groups button.
    The Save selected groups of attributes window opens.
    3. In the selection list, mark the predefined attribute group you would like to select or deselect.
    4. Click the desired button.
    Element

    Description

    Activate

    All attributes of the selected groups are enabled.

    Switch off

    Except key attributes and mandatory attributes, all attributes of the


    selected group are deactivated.

    Activate exclusively

    All attributes of the selected group are activated for saving data to
    file and all attributes of other groups - except key attributes and
    mandatory attributes - are excluded from saving data to file.

    5. Click the Close button.


    According to the current settings, the attributes are either selected or deselected.
    Saving selected network data as layout
    You can save the currently selected tables and attributes as network file *.net without contents
    and read them again later as default values.
    1. Make sure that the Create version comparison (User-defined) window is open (see "Comparing version files" on page 893).
    2. Click the Save layout button.
    The Save network window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    Selected tables and attributes are saved as data block templates without data.

    PTVGROUP

    897

    14.12.1.3 Using comparison values / set graphic parameters


    Reading a layout from a network file
    For version comparison you can read selected network object types and attributes from an
    existing network file or from a network file without content, which was saved just as layout file.
    1. Make sure that the Create version comparison (User-defined) window is open.
    2. Click the Open layout button.
    The Open network window opens.
    3. Select the desired network file.
    4. Click the Open button.
    The selection of network object types and attributes contained in the network file is applied.
    14.12.1.3 Using comparison values / set graphic parameters
    For a version comparison that adopts attributes from a comparison network, Visum adds a new
    attribute to each attribute selected. The new attribute contains an attribute value of the second
    network. Additionally for numerical attributes Visum carries out various comparisons automatically: For each compared numerical attribute additional attributes for the absolute and relative deviation as well as for the minimum and maximum are created.
    Additionally, new attributes Exists in network <Code of version comparison> of the type
    True/False are added to each network object type. These attributes allow you to quickly check
    whether the network objects exist in both versions files you are comparing.
    These attributes can be used like all other attributes, in particular for the graphic display and in
    lists (see Fundamentals: Chpt. 2.5.1 , page 23).
    In the attribute selection window, the compared attributes are listed under their names in the
    conventional and in the alphanumerical sorting order (see "The window used for the selection
    of one attribute" on page 963). The values of the original version are listed as This network if
    you have not specified a name for the original network (see "Specifying a network name for
    version comparison" on page 893). The new attributes contain the name of the version comparison (in the following example VersComp).

    In the hierarchical sorting order all new attributes are listed under Version comparison
    <Name of version comparison>.

    898

    PTVGROUP

    14.12.1.4 Copying comparison values to user-defined attributes

    14.12.1.4 Copying comparison values to user-defined attributes


    You can save selected attribute values or all compared attribute values of a comparison network to new, user-defined attributes. Thus, the values are kept after termination of the version
    comparison.
    You proceed differently depending on the version comparison chosen.
    Creating user-defined attributes by adopting direct attributes during version comparison
    1. From the File menu, choose Compare and transfer networks.
    2. Then click Version comparisons.
    The Version comparisons window opens.
    3. Select the desired version comparison or the desired attributes.
    4. Click the

    Copy to UDA button.

    The version comparisons or attributes are saved to new user-defined attributes.


    Note: Since user-defined attributes do not have subattributes, a user-defined attribute is
    created for each subattribute.
    ID and short name of the new user-defined attributes are generated from the original
    short name of the attribute, added by the name of the version comparison. If the generated ID already exists, an error message is displayed and this attribute will not be created.
    Creating user-defined attributes during version comparison with comparison network in
    the background
    1. From the File menu, choose Compare and transfer networks.
    2. Then click Version comparisons.
    The Version comparisons window opens.
    3. Select the desired version comparison or the desired attributes.
    4. Click the

    Copy to UDA button.

    The Copy data to user-defined attributes window opens.

    PTVGROUP

    899

    14.12.1.4 Copying comparison values to user-defined attributes


    Notes: Since user-defined attributes do not have subattributes, a user-defined attribute is created for each subattribute.
    ID and short name of the new user-defined attributes are generated from the original
    short name of the attribute, added by the name of the version comparison. If the generated ID already exists, an error message is displayed and this attribute will not be
    created.
    5. If necessary, reduce the amount of data you want to copy.
    Note: Only direct attributes are displayed for selection.
    Element

    Description

    Hide calculated
    attributes

    Select this option to additionally copy selected readable attributes and their values besides key attributes.
    Deselect this option to copy both readable and non-readable
    attributes and their values.

    Hide attribute with


    If this option has been selected, only selected attributes and
    default values
    their values are compared.
    If this option has not been checked, all of the selected attributes are copied with their values not regarding whether attribute
    value and default value are identical or not.
    Note
    You can find the default attribute values in the Attribute.xls file,
    under ...\Program files\PTV Vision\PTV Visum 13\Doc.
    Hide empty tables Select this option to copy tables containing network objects.
    6. Choose the network object types you want to copy to user-defined attributes.
    Element

    Description
    The network object type is copied.
    The network object type is not copied.

    Save layout

    Click this button to save your selection as a network file *.net (see
    "Saving selected network data as layout" on page 897).

    Open layout

    Click this button to read in your selection saved as a network file


    *.net (see "Reading a layout from a network file" on page 898).

    Check all tables Click this button to select all network object types.
    Uncheck all
    tables

    Click this button to deselect all network object types. The attributes,
    however, remain selected.

    7. Click a network object type.


    The attributes and, if applicable, the subattributes of the network object type are displayed.
    900

    PTVGROUP

    14.12.1.5 Editing version comparisons

    Tip: Click the CTRL key and keep it pressed while clicking the desired entries one by
    one to show the attributes of multiple network object types at the same time.
    Note: Due to current settings in the upper section of the window not all attributes of a
    network object type may be displayed.
    8. Select the attributes and subattributes you want to copy.
    Element

    Description
    The attribute is selected and copied.
    The attribute is neither selected nor copied.

    Attribute
    groups

    Via this button you can either select or switch off predefined groups of
    attributes in a separate window (see "Selecting or deselecting groups
    of attributes for comparison" on page 897).

    Standard

    Click this button to restore the window default settings.

    Tips: Right-click a network object type. Then use the context menu to activate or deactivate all currently displayed attributes of the network object type.
    9. Confirm with OK.
    The attributes are copied to user-defined attributes.
    14.12.1.5 Editing version comparisons
    You can edit a version comparison that adopts attributes from comparison networks. In doing
    so you can add attributes to the selected version comparison or remove attributes from it.
    1. From the File menu, choose Compare and transfer networks.
    2. Then click Version comparisons.
    The Version comparisons window opens.
    3. Select the desired version comparison.
    4. Click the

    Edit button.

    The Create version comparison (User-defined) window opens.


    5. Edit the current attribute selection as desired.
    6. Click the OK button.
    Adding attributes will call a query.
    7. Confirm the query with Yes.
    The attributes are updated.

    PTVGROUP

    901

    14.12.1.6 Updating version comparisons


    14.12.1.6 Updating version comparisons
    You can update a version comparison. Hereby, the values of the same attributes are read from
    the same version file.
    1. From the File menu, choose Compare and transfer networks.
    2. Then click Version comparisons.
    The Version comparisons window opens.
    3. Select the desired version comparisons.
    4. Click the

    Update button.

    The Update version comparison window opens.


    5. In the Version file box, check the path specified and change it, if required.
    Note: It is important to check the path, e.g., if you have received the versions you want
    to compare from an external source.
    6. Confirm with OK.
    The version comparisons are updated.
    Note: You cannot update the lsInSelection attribute in the version comparison. All passive objects of version comparison remain passive, even if in the current version, objects
    are set to IsInSelection. If the comparison network differs from the current network, Visum
    informs you accordingly.
    14.12.1.7 Deleting version comparisons or attributes
    1. From the File menu, choose Compare and transfer networks.
    2. Then click Version comparisons.
    The Version comparisons window opens.
    3. Select the desired version comparisons or attributes.
    4. Click the

    Delete button.

    The version comparisons or attributes are deleted.

    14.12.2 Merging networks


    Note: Prior to Visum version 11.5 this function was called Difference network.
    With this functionality you can compare two networks and display the differences (see Fundamentals: Chpt. 2.5.2 , page 28).
    In the two networks to be compared, the following must correspond with each other:

    902

    PTVGROUP

    14.12.2.1 Creating a network merge


    The calendar settings (calendar type and time interval)
    All modes, transport systems, demand segments (code) and the allocations between
    these objects (for example demand segment to mode)
    The types of transport systems (PrT, PuT etc.).
    The vehicle journey items
    If there are network objects in network 1 and network 2 with an identical ID, all objects to
    which they refer must also have the same ID. Deviant surface objects are an exception
    (main nodes, zones, main zones, territories, POIs) as are deviant transport systems of a
    line. Here, Visum uses the reference from network 1.
    Notes: Main nodes can only be compared if they consist of identical partial nodes in both
    networks.
    Otherwise a warning is issued and the opening of the merged network is cancelled.
    14.12.2.1 Creating a network merge
    Note: First you need to save the two models to be compared as version files.
    1. From the File menu, choose Compare and transfer networks.
    2. Then click Network merge mode.
    The Network merge mode window opens.

    3. Make the desired changes.


    Element

    Description

    Network 1

    Version file
    Click the
    button to select a version file that you want to compare
    with another version file.
    Note
    Alternatively, you can enter the file name and the path in the field.

    Network 2

    PTVGROUP

    Version file

    903

    14.12.2.1 Creating a network merge


    Element

    Description
    Click the
    button to select a version file that you want to compare
    with the other version file you selected.

    Graphic parameters

    File

    Filter

    File

    Click the
    button to select a graphic parameters file.
    Save
    You can click the button to save the current graphic parameters in a
    file.

    button to select a filter file.


    Click the
    Save
    You can click the button to save the current filter settings in a file.
    Open

    Use this button to open a *.nmp file.


    Note
    If you open a network merge file, the data will be displayed in the window. The merged network itself is not loaded.

    Save

    Use this button to save the data displayed in the window in a *.nmp
    file.

    4. Confirm with OK.


    The merged network is calculated and displayed. The title bar of the program window indicates that you are in the network merge mode.
    Notes: You can terminate the display of the merged network by opening a different version or network file.
    In the Network merge mode the following operations can be carried out:
    Zooming, scrolling, shift mode (hand)
    Creating new user-defined attributes
    Setting a Multi-edit selection
    Setting filters
    List output with attribute interface (clipboard, attribute file, database)
    Opening, editing, and saving graphic parameters
    Opening network/version/(database, INTREST, TModel)
    Saving the network
    Database exports
    Connecting to a Personal Geodatabase
    Turn volume display
    Show network statistics
    Printing

    904

    PTVGROUP

    14.12.2.2 Setting the graphic parameters for the display of difference values
    14.12.2.2 Setting the graphic parameters for the display of difference values
    In the merged network, you can display difference values wherever attributes are displayed by
    selecting an attribute with the Difference subattribute value.
    In the graphic display (e. g. link bars or connector bars, classified attribute values, labels
    as tables and charts, turn volumes, 2D display) (see "Displaying data graphically and in
    lists" on page 2299)
    In lists (see "Working with lists" on page 2299)
    In filters (see "Using filters to set network objects active or passive" on page 1008)
    User-defined attributes (see "Managing user-defined attributes" on page 973)
    Graphic display of differences by means of link bars
    Note: Please do not confuse the display of differences in the merged network with the Difference option, which is used to compare the values of two attributes, and the display of
    the differences in one network version (see "Configuring a difference bar display" on
    page 2379).
    If you want to display difference values by means of link bars, proceed as follows (see Fundamentals: Chpt. 2.5.2 , page 28).
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Links > Bars > Display entry.
    3. Insert the desired bar (see "Defining one or multiple bars" on page 2373).
    4. Make the desired settings for the bar (see "Setting the display properties of a standard bar"
    on page 2375).
    5. Under ScaleAttrID, choose an attribute with the subattribute Difference.

    PTVGROUP

    905

    14.12.2.2 Setting the graphic parameters for the display of difference values

    6. Confirm with OK.


    The difference values are displayed in the network.
    Tip: You can also display classified difference values, for example by displaying negative
    difference values of volumes in red and positive difference values in green. You can do
    this by selecting the Classified drawing mode option on the Fill style tab, creating two
    classes >0 and 0 for which you select attribute Volume, and specifying the respective
    color.
    Parallel display of attribute values
    You can also display attribute values from network 1, network 2, and the merged network in
    parallel. To display values in parallel, proceed as follows.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Links > Bars > Display entry.

    906

    PTVGROUP

    14.12.2.3 Displaying merged network values in lists

    3. Insert a bar for each of the following attributes: v0 PrT (Diff), v0 PrT (Network1) and v0 PrT
    (Network2).
    4. Specify the desired bar settings (see "Setting the display properties of a standard bar" on
    page 2375).
    5. Confirm with OK.
    The values are displayed next to each other.

    14.12.2.3 Displaying merged network values in lists


    You can display merged network values in lists for nearly all network objects.
    Note: You cannot display merged network values in the blocks, relations or paths lists,
    nor in the node geometry or control lists.

    PTVGROUP

    907

    14.12.2.4 Saving merged networks


    1. Make sure that the list window of the required list is open.
    2. On the toolbar, click the

    Select attributes icon.

    The Attribute selection window opens.


    3. Select attributes with the Network 1, Network 2 and Difference subattributes.
    4. Confirm with OK.
    The values are displayed.
    14.12.2.4 Saving merged networks
    You can save the current settings of your merged network in a *.nmp file.
    1. In the File menu, point to Save as.
    2. Then click Network merge parameters.
    The Save: Network merge parameters window opens.
    3. Save the file to the desired location.

    14.12.3 Creating and applying model transfer files


    Using model transfer files you can save the difference between two models, i.e. network and
    OD demand data. You can read, or more precisely, apply, a model transfer file generated that
    way to the matching version file in order to transfer it to the other model (see Fundamentals:
    Chpt. 2.5.3 , page 31).
    Scenario management is based on model transfer files (see "Scenario management" on page
    921).
    14.12.3.1 Creating a model transfer file
    1. Open the desired version file.
    2. From the File menu, choose Compare and transfer networks.
    3. Then click Create model transfer file.
    The Create model transfer file window opens.
    4. Make the desired changes.
    Element

    Description

    Network 2

    Version file
    button to select the file of your choice.
    Click the
    Note
    The two version files must have the same system of co-ordinates.

    Output

    908

    The transfer file converts network 2 to network 1


    The created file serves to transfer the selected network into the

    PTVGROUP

    14.12.3.1 Creating a model transfer file


    Element

    Description
    currently opened network.
    The transfer file converts network 1 to network 2
    The created file serves to transfer the currently opened network
    into the selected network.

    Show model trans- If this option has been selected, the new model transfer file is disfer file after crea- played.
    ting
    5. Confirm with OK.
    The Save model transfer file window opens.
    6. Select the desired folder.
    7. Enter the desired file name.
    8. Click the Save button.
    The Save model transfer file (User-defined) window opens.
    Note: The network file cannot be written in all languages the Visum program interface
    is available in. If you show the program interface in a language (e.g. Greek) that is not
    supported by the network file, the Display language section is displayed at the top of
    the window. Here you can select a language for display of the table elements.
    9. If necessary, reduce the amount of data to be saved to file.
    Element

    Description

    Hide calculated
    attributes

    If this option has been selected, the calculated attributes are


    hidden and are not saved.
    If this option has not been selected, calculated attributes are
    equally saved.

    Hide attribute with


    If this option has been checked, only selected attributes are
    default values
    saved with their values.
    Tip
    Use this option to reduce file size.
    If this option has not been checked, all of the selected attributes are saved with their values not regarding whether attribute
    value and default value are identical or not.
    Note
    You can find the default attribute values in the Attribute.xls file,
    under ...\Program files\PTV Vision\PTV Visum 13\Doc.
    Hide empty tables If this option has been selected, only those tables containing
    objects are saved to file.

    PTVGROUP

    909

    14.12.3.1 Creating a model transfer file


    10. Select the data tables you want to save to file.
    Note: When selecting the tables with network object types, make sure that the selected combination makes sense. If possible, use the Frequent cases button to have
    access to a number of useful combinations.
    Element

    Description
    The table has been selected and will be saved to file.
    The table has not been selected and will not be saved to file.
    Note
    Table $VERSION cannot be excluded.

    Check all tables Via this button, you may check all tables.
    Note
    The status of the attributes in the tables remains unchanged.
    Uncheck all
    tables

    Via this button, you may uncheck all tables except $VERSION.
    Note
    The status of the attributes in the tables remains unchanged.

    Frequent cases The data required for the description of a network or demand object
    are stored in just a single or in multiple tables. All data of a link
    object, e.g., is listed in the $Links table. Links with an edited shape
    are additionally listed in the $LinkPoly block.
    Use this button to select all data tables required for the description of
    specific objects (so-called use cases) and their attributes at the
    same time (see "Selecting data tables required to describe an object
    type for saving data to file" on page 912).
    11. Click a table name.
    The table opens and the names of the attributes of this table are displayed.
    Tip: Click the CTRL key and keep it pressed while clicking multiple tables one by one
    to show the attributes of these tables simultaneously.
    Note: Due to current option settings in the upper section of the window possibly not all
    of the attributes might be displayed by table.
    12. Select the attributes you want to save to file.

    910

    PTVGROUP

    14.12.3.1 Creating a model transfer file


    Element

    Description
    The attribute has been selected and is saved to file.
    The attribute has not been selected and is not saved to file.
    The attribute is a key attribute and cannot be switched off.
    Key attributes are attributes which serve for unique identification of
    network objects.
    The attribute is a mandatory attribute and cannot be excluded.

    Attribute
    groups

    Via this button you can either select or switch off predefined groups of
    attributes in a separate window (see "Selecting or deselecting groups
    of attributes for saving data" on page 911).

    Standard

    Click this button to hide empty tables and calculated attributes. All
    other attributes are selected.

    Note: Alternatively, you can read selected tables and attributes from a network file
    *.net (see "Reading a layout from a network file" on page 913).
    13. Confirm with OK.
    Network and OD demand data are saved according to the current settings.
    Note: The tables of network and OD demand data in the model transfer file have the following labeling:
    $-<Name of object type>: data to be deleted (for the version opened at the start)
    $+<Name of object type>: added data (for the version opened at the start)
    $<Name of object type>: data to be changed, specifically topologically modified courses
    $*<Name of object type>: data of individual attributes to be changed
    $!<Name of object type>: data which have to be saved for internal reasons, even if
    they are matching in both models
    Selecting or deselecting groups of attributes for saving data
    1. Make sure that the Save model transfer file (User-defined) window is open (see "Creating
    a model transfer file" on page 908).
    2. Click the Attribute groups button.
    The Save selected groups of attributes window opens.
    3. In the selection list, mark the predefined attribute group you would like to select or deselect.
    4. Click the desired button.

    PTVGROUP

    911

    14.12.3.1 Creating a model transfer file


    Element

    Description

    Activate

    All attributes of the selected groups are enabled.

    Switch off

    Except key attributes and mandatory attributes, all attributes of the


    selected group are deactivated.

    Activate exclusively

    All attributes of the selected group are activated for saving data to
    file and all attributes of other groups - except key attributes and
    mandatory attributes - are excluded from saving data to file.

    5. Click the Close button.


    According to the current settings, the attributes are either selected or deselected.
    Selecting data tables required to describe an object type for saving data to file
    In Visum, several tables contain data for the description of specific network or demand objects,
    for example zones and corresponding polygons, timetable or line block data.
    To make sure that all the tables and attributes required (so-called use case) are saved to the
    model transfer file, you can activate a predefined selection of tables and attributes, adapted to
    the data you wish to save.
    1. Make sure that the Save model transfer file (User-defined) window is open (see "Creating
    a model transfer file" on page 908).
    2. Click the Frequent cases button.
    The Use cases for selective network saving window opens.
    3. Make the desired changes.

    912

    Element

    Description

    Save polygons

    If this option has been selected, all tables required for polygon
    definition are selected. You can decide whether the tables of the
    related network object types (Zones, Main zones, Main nodes,
    Territories, POIs, Toll systems) are to be saved, too.

    Save timetable

    If this option has been selected, all tables are selected that contain data with regard to the timetable. You can decide whether
    data regarding calendar period and valid days are to be saved.
    Save calendar period and valid days
    If this option has been selected, the tables Calendar period, Valid
    days and Holidays are saved to file.
    Note
    This option is only provided, if a weekly or an annual calendar
    has been defined in the network.

    Save blocks

    If this option has been selected, the tables storing PuT line blocks
    and corresponding data are selected.

    PTVGROUP

    14.12.3.2 Showing the content of a model transfer file


    Element

    Description
    Note
    Since line blocks refer to valid days, option Save calendar period
    and valid days is selected automatically.

    Save main nodes

    Click this option to select main node tables and their data.

    4. Confirm with OK.


    Save selected network and OD demand data as layout
    You can save the currently selected tables and attributes as network file *.net without contents
    and read them again later as default values.
    1. Make sure that the Save model transfer file (User-defined) window is open (see "Creating
    a model transfer file" on page 908).
    2. Click the Save layout button.
    The Save network window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    Selected tables and attributes are saved as data block templates without data.
    Reading a layout from a network file
    You can read selected tables and attributes from an existing network file or from a network file
    that was saved just as layout file.
    1. Make sure that the Save model transfer file (User-defined) window is open (see "Creating
    a model transfer file" on page 908).
    2. Click the Open layout button.
    The Open network window opens.
    3. Select the desired file.
    4. Click the Open button.
    The selected tables and attributes contained in the network file are adopted.
    14.12.3.2 Showing the content of a model transfer file
    There are two options for showing the data of a model transfer file in a tree structure. You can
    also compare this data with the network data of the currently opened version file. To do so, synchronize the model transfer file with other windows, e.g. the Network editor window, so that
    the respective network objects are highlighted in both windows at the same time.
    1. Open the desired version file.
    2. From the File menu, choose Compare and transfer networks> Show model transfer file.
    The Open: Model transfer file window opens.

    PTVGROUP

    913

    14.12.3.2 Showing the content of a model transfer file


    3. Select the desired file.
    4. Click the Open button.
    The model transfer file is opened. The data is displayed in a navigator.
    Note: There are up to four entries listed below each object type:
    Inserted: This entry contains the objects inserted.
    Deleted: This entry contains the objects deleted.
    Modified: This entry contains the objects that were edited directly. It also includes
    the subentry All with all edited objects and a subentry for the edited attributes. For
    each attribute, you can see the objects whose attributes were edited and their new
    attribute values.
    Dependently modified: This entry contains objects that were edited indirectly.
    Time profiles and vehicle journeys, e.g., are automatically changed when a line route
    is changed.
    A dot in front of an object indicates that the object exists in the network which is
    currently open. Objects with a circle do not exist in the currently open network.
    5. Click the icons to make the settings of your choice.
    Tip: Alternatively, use the context menu or the Model transfer file menu to call functions.
    Icon

    Menu command

    Description

    Open model trans- Opens another model transfer file


    fer file
    Open model trans- Opens another model transfer file in a new window
    fer file in new window
    Reload model
    transfer file

    Reloads the data of the model transfer file

    Apply model trans- Applies the model transfer file shown to the network
    fer file to current
    currently open (see "Applying model transfer files" on
    network
    page 916)

    914

    Expand tree completely

    Expand all subentries in the navigator


    Tip
    If you want to open the subordinated entries one by one,
    click the icon.

    Expand tree up to
    object nodes

    Expands the navigator so that all objects are shown.

    PTVGROUP

    14.12.3.2 Showing the content of a model transfer file


    Icon

    Menu command

    Description

    Reduce tree

    All subentries in the navigator are collapsed


    Tip
    If you want to close the subordinated entries one by one,
    click the icon.

    Copy tree to clipboard

    Copies the content to the clipboard

    No synchronization

    (see "Synchronizing the model transfer file with other windows" on page 915)

    Mark object(s)

    (see "Synchronizing the model transfer file with other windows" on page 915)

    Mark and shift


    view

    (see "Synchronizing the model transfer file with other windows" on page 915)

    Mark and autozoom

    (see "Synchronizing the model transfer file with other windows" on page 915)

    Tree view > Flat

    Click this icon to show "dependent" object types in the


    navigator at the top level (e.g. the polygon of a link or the
    course of a line route).

    Tree view > Hierarchical

    Click this icon to show "dependent" object types in the


    navigator below their respective object type (e.g. a polygon below links).

    Synchronizing the model transfer file with other windows


    You can synchronize the model transfer file with other windows, e.g. the Network editor window, the Junction editor window or a list. If the windows are synchronized, you can highlight
    one or several network objects in one window and they are automatically highlighted in the
    other windows as well (i.e. if they have the same code). Depending on your setting, the view in
    the Network editor window is automatically shifted or zoomed in.
    Note: Synchronization only works, if you activate it for all relevant windows.
    List window (see "The list window" on page 2304)
    Junction editor window (see "Using the Junction editor" on page 1435)
    Transfers display of regular services (see "Synchronizing the transfers display of
    regular services with other windows" on page 2395)
    Schematic line diagram (see "Synchronizing the schematic line diagram with other
    windows" on page 2474).
    1. Position the window with the model transfer file and the other windows of your choice next
    to each other.
    2. From the Model transfer file menu, choose > Synchronization with Network editor and
    select the entry of your choice.

    PTVGROUP

    915

    14.12.3.3 Applying model transfer files


    Element

    Description

    No synchronization

    The model transfer file is not synchronized with other windows.

    Mark object(s)

    The objects highlighted in the model transfer file are also highlighted in the other windows and vice versa.

    Mark and shift


    view

    The objects highlighted in the model transfer file are also highlighted in the other windows and vice versa. If required, the network section of the Network editor window is moved so that all
    highlighted objects are visible.
    Note
    This does not affect the scale of the network editor.

    Mark and autozoom

    The objects highlighted in the model transfer file are also highlighted in the other windows and vice versa. Additionally, in the
    network an auto zoom is carried out for the marked objects.

    3. In the model transfer file, click an entry.


    The network objects below the selected entry are highlighted in the other windows.
    Note: A dot next to a network object indicates that this object exists in the network
    which is currently open. Network objects with a circle do not exist in the network
    currently open and can thus not be marked.
    4. In another window, click an entry for an inserted, changed or deleted network object.
    The network object is highlighted in the Model transfer file window.
    14.12.3.3 Applying model transfer files
    You can apply a model transfer file created beforehand to the currently opened version file.
    Hereby, you transfer the network and OD demand data concerned to another model.
    1. Open the desired version file.
    2. In the File menu, select the Compare and transfer networks> Apply model transfer data
    file entry.
    The Open: Model transfer file window opens.
    3. Select the desired file.
    4. Click the Open button.
    Note: Alternatively, you may enter path and file name.
    A query opens.
    5. Confirm the query with OK.
    The Apply model transfer data file window opens.
    916

    PTVGROUP

    14.12.3.3 Applying model transfer files


    6. Make the desired changes.
    Element

    Description

    Show warnings on
    screen

    Select this option to show warnings when loading files.


    If this option is not selected, no warnings are shown when you
    load files. This will speed up the reading process.
    Note
    If in the warning settings, you selected Save warnings and
    details to the message file and in the log files, you selected Message file: Create new file, warnings are saved to a message file
    (see "Specifying settings for protocol files" on page 876).

    Display error messages on screen

    Select this option to show error messages when loading files.


    If this option is not selected, no error messages are shown
    when you load files. This will speed up the reading process.

    7. Make the desired changes.


    Element

    Description

    First of all, determine existing


    tables

    If this option has been selected, the model transfer file is


    checked. Only available data tables will be listed for selection
    then.
    If this option has not been selected, all tables will be provided
    for selection.

    Create warnings
    for conflicts in
    mode "Ignore"

    If this option has been selected and the Ignore mode (see next
    window) has been activated, warnings about existing network
    objects will be displayed on the screen during the reading process.
    If this option is not selected, and you select the Ignore mode,
    no warnings about already existing network objects are displayed
    during the reading in process. This will speed up the reading process.
    Note
    To save warnings to a message file, in the warning settings,
    select Save warnings and details to the message file and in the
    log file settings, select Create new file (see "Specifying settings
    for protocol files" on page 876).

    Permit the deletion of objects

    If this option has been selected, network objects in tables labeled $-<name of object type> will be deleted from the network (see
    "Creating a model transfer file" on page 908).
    If this option has not been selected, tables that are labeled $<Object type name> will be ignored.

    8. Confirm with OK.


    PTVGROUP

    917

    14.12.3.3 Applying model transfer files


    The Apply model transfer data file window opens.

    Note: When selecting the network object types, make sure that the selected combination makes sense. If possible, use the Frequent cases button to have access to a
    number of useful combinations.
    Note: The network file cannot be written in all languages the Visum program interface
    is available in. If you show the program interface in a language (e.g. Greek) that is not
    supported by the network file, the Display language section is displayed at the top of
    the window. Here you can select the language you want to show the texts of the
    column Network objects (table) in.
    9. Select the data tables you want to read additionally to your current network.
    Element

    Description

    Column to the left

    If this option has been selected, the particular table will be


    read additionally to the given data.

    Network objects
    (table)

    List of data tables which are required for object description.


    Depending on the First of all, determine existing tables option,
    this list contains either any possible table or only those saved
    with the model transfer file.

    Check all

    Via this button, you may check all tables.

    If this option is not checked the particular table will be ignored.

    918

    PTVGROUP

    14.12.3.3 Applying model transfer files


    Element

    Description

    Uncheck all

    Via this button, you may uncheck all tables.

    Frequent cases

    The data required for description of the objects of a particular network object type are stored in just a single or in multiple tables.
    All data of a link object, e.g., is listed in the $Links table. Links
    with an edited shape are additionally listed in the $LinkPoly
    block.
    Via this button you can select all data tables required for description of certain network objects (so-called use cases) at the
    same time. Furthermore you can automatically set preventive options for conflict handling (see "Selecting data tables required to
    describe an object type for saving data to file" on page 912).

    10. Decide for each data table, how network objects are to be read if the current network
    already contains a network object with an identical object key.
    Note: Key attributes are attributes which serve for unique identification of network
    objects (see "Identifiers" on page 2327).
    Element

    Description

    Conflict avoidance
    If this option has been selected, you can - in the Conflict handfor new objects
    ling column - modify the value of the key attribute in a way that
    makes the value unique.
    If this option has not been selected or if it is not provided, you
    can - in the Conflict handling column - choose how to handle network objects with identical keys.
    Conflict handling
    for new objects (if
    Conflict avoidance
    has been selected)

    According to the data type of the key attribute, enter an alphanumerical prefix value or a numerical offset value.
    Prefix
    To an alphanumerical key attribute, you can add an alphanumerical prefix in the first position.
    Offset
    To the value of a numerical key attribute you can add a constant
    value.

    Conflict handling
    for new objects (if
    Conflict avoidance
    has not been selected or is not available)

    From the selection list, select the appropriate option for handling
    of network objects with identical key.
    Only check
    Visum checks whether the current network already contains the
    network objects which are to be read from file additionally. If this
    is not the case, an error message is displayed and reading data
    from file is cancelled. This option is provided for, for example,

    PTVGROUP

    919

    14.12.3.3 Applying model transfer files


    Element

    Description
    Transport Systems, Modes and Demand segments.
    Ignore
    Ignored are those network objects in the network file being read
    that have identical keys which are already in use in the currently
    open network file. The existing network objects and their attribute
    values remain unchanged.
    Overwrite object/course
    Existing network objects for which the network file contains network objects with identical keys, are replaced by the objects read
    from file. Attribute values of attributes which are not contained in
    the network file are set to a standard value.
    Overwrite attributes
    Existing network objects for which the network file contains network objects with identical keys are kept but their attribute values
    are replaced. Attribute values of attributes which are not contained in the network file remain unchanged.
    Overwrite structure
    If the network file contains lanes for a leg, they are overwritten.
    Cancel
    Reading is cancelled.

    Tips: Alternatively you may specify the settings for multiple data tables at the same
    time by marking the tables and clicking the Edit button (see "Setting options for multiple data tables" on page 920).
    Alternatively you can read the settings from the parameter file for additive network reading (*.anrp) (see "Saving settings for the application of model transfer data files" on
    page 921).
    You may save these settings (see "Opening settings for the application of model transfer data files" on page 921)
    11. Confirm with OK.
    The network and OD demand data are read.
    Tip: You can also open a network file by clicking the selected file in the list of recently
    opened files in the File menu.
    Setting options for multiple data tables
    1. Make sure that the Apply model transfer data file window is open (see "Applying model
    transfer files" on page 916).
    2. Press the CTRL key and keep it pressed.
    920

    PTVGROUP

    14.13 Scenario management


    3. In the list of tables, mark the entries you would like to edit.
    4. Click the Edit button.
    A window opens.
    5. Make the desired settings (see "Applying model transfer files" on page 916).
    6. Confirm with OK.
    The settings are used for the selected tables.
    Saving settings for the application of model transfer data files
    1. Make sure that the Apply model transfer data file window is open (see "Applying model
    transfer files" on page 916).
    2. Make sure the desired options are set (see "Editing modifications" on page 928).
    3. Click the Save button.
    The Save: Parameters for 'Read network additively' window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The settings are saved as *.anrp file.
    Opening settings for the application of model transfer data files
    1. Make sure that the Apply model transfer data file window is open (see "Applying model
    transfer files" on page 916).
    2. Click the Open button.
    The Open: Parameters for 'Read network additively' window opens.
    3. Select the desired *.anrp file.
    4. Click the Open button.
    The settings are read from file.

    14.13

    Scenario management
    Scenario management is used to manage variants of a version file. These variants are organized within the project as scenarios including modifications (see Fundamentals: Chpt. 2.6 ,
    page 31).
    A project is ideally carried out in the following steps:
    1. Creating a base version
    2. Creating a new project and selecting the appropriate base version
    3. Defining modifications
    4. Defining scenarios based on modifications
    5. Specifying the procedure sequence

    PTVGROUP

    921

    14.13.1 Creating a project for Scenario management


    6. Calculating scenarios
    7. Comparing calculation results
    In the ideal case, you start by creating a single base version and then define its modifications
    step by step. However, you might already have several scenarios, either in form of a version
    file and several model transfer files or in form of several version files that only slightly differ. In
    this case, you can convert your data for scenario management during step 3: Defining modifications as follows:
    Apply your model transfer files and complete the modification (see "Creating modifications" on page 926). Visum then saves the modification to the project, as a new model
    transfer file (with the same content).
    If you have a second version file that only slightly differs from the base version, load the
    second file during step 3: Defining modifications (see "Creating modifications" on page
    926). Then complete the modification. Visum then saves the differences between the base
    version and the newly opened version to the project as a model transfer file. You then
    create a scenario and assign the modification to it. The scenario now corresponds to your
    second version file.

    14.13.1 Creating a project for Scenario management


    To use scenario management, you first have to create a project (see Fundamentals: Chpt.
    2.6.2 , page 34). To do so, choose a version file you want to use as the basis of the project. It,
    for instance, contains the actual status which forms the basis for further planning.
    1. Create a base version *.ver for your project.
    2. From the File menu, choose Scenario management> New project.
    The Create new project window is opened.

    3. Make the desired changes.

    922

    Element

    Description

    File name

    Name of the scenario management project


    This is the name of the project file and of the project folder. You
    can specify a meaningful name for the project later (see "Editing
    basic settings of the project" on page 923).

    Base directory

    Folder the project is saved to

    PTVGROUP

    14.13.2 Editing basic settings of the project


    Element

    Description
    Click the

    button to select a folder.

    Use currently loa- Select this option to use a copy of the version file currently open
    ded data as base as the project base version. The file is then copied to the folder
    version
    specified.
    Use existing version as base version

    Select this option to use the copy of a *.ver file as the project base
    version. The file is then copied to the folder specified.
    Click the

    symbol to select a version file.

    4. Confirm with OK.


    In the base folder, a new folder with the name of the project is created. The project is saved to
    it as a *.vpdb file. In parallel, Visum creates several subfolders. The Edit project window
    opens. Here you can enter or change further data (see "Editing basic settings of the project" on
    page 923).
    Note: You must not change the folder structure of the project in the Windows explorer.

    14.13.2 Editing basic settings of the project


    After creating a project for scenario management, you can change its basic settings.
    1. From the File menu, choose Scenario management> Open project.
    The Open: Scenario management project window opens.
    2. Select the project database *.vpdb of your choice.
    3. Click the Open button.
    The Edit project window opens.
    Tip: You can also open a project in Visum by double-clicking the desired *.vpdb project
    database in the Windows directory.
    4. Select the Basic settings tab.
    5. Make the desired changes.
    Note: You can use the keyboard shortcut C TRL +C in all tabs of the Edit project window
    to copy, and then press the C TRL+V to paste at a different location.
    Element

    Description

    Project name

    Name of the project. By default, it is the name you specified when


    creating the project. If you change the project name, this will not
    affect the name of the project file or project folder.

    Base version

    Click the Edit base version button to open and edit the data of the

    PTVGROUP

    923

    14.13.2 Editing basic settings of the project


    Element

    Description
    version file (see "Editing the base version" on page 925).

    Project directories

    Click the Edit project directories button to specify per file type how
    you want to manage your data:
    in a common directory (SharedData folder),
    separately for each scenario (Scenarios folder),
    To structure the organization of your project data, you can create
    subfolders for the Scenario and SharedData folders. In the Folder
    (relative) column, click the
    button to specify the storage location
    for each file type.
    To open or save a file in procedure sequence, simply enter the
    respective file name. Via the project directories, it is specified from
    where the file is retrieved and where it is saved.
    Note
    When you edit the base version, the program automatically suggests the SharedData folder as storage location.

    Log
    Click the
    Create log entry icon to insert a new row at the end
    of the logfile. Here you can enter text and change the date if required.
    ScenarioIndicator

    Click the Select scenario indicators icon


    to choose relations
    (see "The window used for the selection of multiple attributes" on
    page 968 and "Indirect attributes: relation types and aggregate functions" on page 966). You can show these indicators in the Scenarios tab, after scenario calculation (see "Calculating scenarios
    locally on a computer" on page 938). Here values are available that
    were aggregated across the whole network. This allows you to compare several scenarios with each other.
    Click the
    Edit code for scenario indicator icon to change the
    name by which a scenario indicator is displayed in the list.

    6. Make your changes in the respective tabs.

    924

    PTVGROUP

    14.13.3 Editing the base version


    Element

    Description

    Scenarios

    Creating and managing scenarios (see "Managing scenarios" on page 933)


    Calculating scenarios (see "Calculating scenarios and showing results" on page 938)
    Comparing scenarios (see "Comparing scenarios" on page
    948)
    Exporting scenarios (see "Saving a scenario as a version file"
    on page 956)

    Modifications

    Creating and managing modifications (see "Managing modifications" on page 925)


    Exporting modifications (see "Saving modifications as a
    model transfer file" on page 956)

    Procedure parameter sets

    Managing procedure parameter sets (see "Specifying procedure


    parameters" on page 935)

    Comparison pattern

    Managing comparison patterns for scenario comparison (see


    "Specifying comparison patterns" on page 949)

    7. Click the Close project button.


    The project is automatically saved and closed.
    Note: You must not change the folder structure of the project in the Windows explorer.

    14.13.3 Editing the base version


    All scenarios are based on the base version. If you change data in the base version, the modifications made might then no longer match the base version. Then the scenarios become useless. Therefore you should only change the base version to a degree that it does not affect the
    modifications.
    1. Make sure that the desired project is open (see "Editing basic settings of the project" on
    page 923).
    2. In the Edit project window, click the Basic settings tab.
    3. Click the Edit base version button.
    The base version is opened. At the same time the Edit base version window opens.
    4. Make your changes to the base version.
    5. In the Edit base version window, click the Finish button.
    The Edit project window opens again. Now you can make additional changes to the project.

    14.13.4 Managing modifications


    A modification is a grouping of changes that belong together content-wise and are made to the
    supply or demand.

    PTVGROUP

    925

    14.13.4.1 Creating modifications


    Modifications are used to create scenarios. A scenario is created by applying one or several
    modifications to a base version (see "Managing scenarios" on page 933).
    14.13.4.1 Creating modifications
    To create a modification, select a base scenario, make changes to it and save the changes.
    Visum creates a model transfer file containing the differences between modification and base
    scenario.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    Add modification icon.

    3. Then click the

    Tip: Alternatively, click the


    fication.

    Duplicate modification icon, to copy an existing modi-

    The Create new modification window opens.


    4. Make the desired changes.
    Element

    Description

    Code

    Short name of modification

    Description

    Description of modification

    Group

    Use this field to enter text or select an existing group. You can use the
    Group property to sort modifications.

    Tip: You can first leave these fields empty and make or change its entries later on, in
    the Modifications tab.
    5. Confirm with OK.
    The Select the basis scenario window opens.
    6. Make the desired changes.
    Note: You have two options:
    Use the respective buttons to select the dependent modifications and the modifications that exclude each other. In this case, the base scenario is user-defined.
    Or in the list at the bottom, click a base scenario. In this case, the appropriate
    modifications, dependent and excluding, are automatically selected and the buttons are labeled accordingly.

    926

    PTVGROUP

    14.13.4.1 Creating modifications


    Element

    Description

    Depending on

    A modification may be dependent on other modifications. For example, when you create a new PuT line on a link that you inserted in
    another modification. Use the respective button to select the modifications that are dependent on the current modification.
    This has the following effect: If a scenario contains a dependent
    modification, all modifications that are dependent on it are also applied.
    Note
    You can change this setting later on (see "Editing the properties of a
    modification" on page 929).

    Mutually excludes

    One modification might exclude other modifications. Click the


    respective button to select the modification of your choice. This settings has the effect that the excluding modifications cannot be applied to the same scenario.
    Note
    You can change this setting later on (see "Editing the properties of a
    modification" on page 929).

    Basis scenario

    Scenario or base version you are using as a basis for modification.


    The modifications (dependent and excluding) are automatically
    selected and are later adopted into the columns of the modification.
    Note
    The user-defined scenario is automatically selected when you click
    a button to choose a modification.

    The version file of the selected base scenario is opened. At the same time the Edit Modification window opens.
    7. Make your changes to the version file.
    Note: You have several options to do so:
    You can, e.g., make the changes directly in the Network editor window.
    You can read in additional network or demand data.
    You can apply one or several model transfer files (see "Applying model transfer
    files" on page 916). This way you can integrate existing model transfer files into
    scenario management.
    You can open another version file. The differences between the selected base
    scenario and the version file opened are then saved to the project as a model
    transfer file. This allows you to integrate two version files in scenario management.
    Please note the information on uniqueness of network object IDs (see "Information on
    uniqueness of IDs in modifications" on page 928).
    8. In the Edit modification window, click the Finish button.
    PTVGROUP

    927

    14.13.4.2 Information on uniqueness of IDs in modifications


    The Edit project window opens again. The list now contains the new modification. The changes are saved to the project as a model transfer file. Now you can make additional changes to
    the project.
    Tip: To open the model transfer file, click the

    Show modification icon.

    14.13.4.2 Information on uniqueness of IDs in modifications


    Within scenario management, Visum makes sure that all network objects of a project have unique IDs. They are managed in the database file. This way, there are no network objects with
    the same ID in your modifications.
    When you add a new network object, Visum automatically suggests the next free ID for the project. This is why Visum automatically activates the option Conflict avoidance for numerical
    keys, when reading in additional network data or modification files. Visum then automatically
    determines the next free ID per network object type and selects the corresponding offset.
    In some cases, however, it might be useful to change these settings. For instance, you might
    want to compare the same stop at different locations or with different properties, in several scenarios. In this case, create a stop with the same ID in several modifications. The modifications
    then exclude each other, but they can be used in several scenarios. When comparing these
    scenarios, you can compare the stop attributes (and the corresponding lines), as they have the
    same ID.
    14.13.4.3 Editing modifications
    You can edit the changes made to network or demand data in the modification.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    3. In the list, click the modification of your choice.
    4. Click the

    Edit the modification's changes to the network icon.

    The version file is opened. At the same time the Edit Modification window opens.
    5. Make your changes to the version.
    Note: You can make the changes directly in the version. However, you can also read
    in a model transfer file (see "Applying model transfer files" on page 916).
    6. In the Edit modification window, click the Finish button.
    The changes are saved as a model transfer file. The Edit project window opens again. Now
    you can make additional changes to the project.
    14.13.4.4 Viewing modifications in the Network editor window
    You can view the content of modifications. Thereby, a model transfer file is opened that contains the modification. To show the network objects listed in the model transfer file in your

    928

    PTVGROUP

    14.13.4.5 Editing the properties of a modification


    network, first open the version file of your choice.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. Open the base version of a project or one of the scenarios.
    3. In the Edit project window, click the Modifications tab.
    4. In the list, click the modifications of your choice.
    5. Then click the

    Show modification icon.

    The modification is opened in a model transfer file (see "Showing the content of a model transfer file" on page 913). Synchronize the file with the Network editor window to show the changes in both windows at the same time.
    14.13.4.5 Editing the properties of a modification
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.

    Note: Click the Attribute selection symbol


    to show and hide columns (see "The
    window used for the selection of multiple attributes" on page 968).
    3. Make the desired settings in the list.
    Element

    Description

    LoadOrder

    Number specifying the sequence the modification is applied in. To


    change the numbers, click the symbols (see "Specifying the load order
    of modifications" on page 930).

    Code

    Modification code

    Description

    Description of modification

    Group

    Use this field to enter text or select an existing group. You can use the
    Group property to sort modifications.

    Dependent on A modification may be dependent on other modifications. For example,


    when you create a new PuT line on a link that you inserted in another
    modification. Click this button to select the modifications that are dependent on a modification.
    This has the following effect: If a scenario contains a dependent modification, all modifications that are dependent on it are also applied.
    Notes
    You can check the dependency between two modifications and thereby automatically select the respective entry in the column (see

    PTVGROUP

    929

    14.13.4.6 Specifying the load order of modifications


    Element

    Description
    "Checking independence between two modifications" on page 931).
    If a modification is dependent on another modification, which in turn is
    also dependent on a modification, the list is actually longer than displayed in this column. All modifications dependent on another modification are displayed in the columns DependentOnCompleted and
    DependentOnCompletedSortedByLoadOrder.

    Exclusion

    One modification might exclude other modifications. Click the respective button to select the modification of your choice. This settings has
    the effect that the excluding modifications cannot be applied to the
    same scenario.
    Note
    You can check the combinability of modifications and thereby automatically select the respective entry in the column (see "Checking combinability of modifications" on page 932).
    If a modification is dependent on another modification that excludes a
    third modification, the exclusion will also apply to this modification. All
    modifications that are excluded are displayed in the ExclusionCompleted table.

    Note: When you change exclusions and dependencies between modifications, Visum
    performs a few tests:
    A modification cannot be dependent on another modification and at the same
    time exclude it, not even indirectly.
    Two modifications used in the same scenario cannot exclude each other.
    According to the load order, a dependent modification must be listed after the
    modification it is dependent on.
    14.13.4.6 Specifying the load order of modifications
    Modifications are applied in a specific order that is indicated through a number in the LoadOrder column. In a scenario, the modifications are applied in this order. You can change the
    order of modifications. However, thereby a dependent modification must always be listed after
    the modifications it is dependent on.
    Note: To avoid error messages when loading scenarios, you should first check the dependencies of modifications before you change the order they are applied in (see "Checking
    modifications" on page 931).
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    3. In the list, click the modification of your choice.

    930

    PTVGROUP

    14.13.4.7 Checking modifications

    4. Then click the

    Shift modification downwards or

    Shift modification upwards icon.

    The position of the modification in the order is changed. To check the current position of a
    modification, look at its number in the LoadOrder column.
    14.13.4.7 Checking modifications
    You can check whether two modifications are dependent on each other and whether they can
    be combined. You, for instance, check the dependency of modifications before changing the
    order they are applied in.
    Checking independence between two modifications
    This test allows you to check whether the same results are produced when you change the
    order the modifications are applied in. If the two modifications are dependent on each other,
    you can automatically change the entries in the DependentOn and Exclusion columns.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    3. In the list, click the two modifications of your choice.
    4. Then click the

    Check independency icon.

    The two modifications are compared. A window opens, informing you whether the two modifications are independent or not. If they are dependent, the Modification ... and modification ... overlap window opens, showing the overlaps in a model transfer file. The
    Overlappings of modifications window is opened, offering you several options.
    5. Make the desired changes.
    Element

    Description

    Do not change the dependencies and exclusions of


    the modifications ... and ...

    Nothing is changed.

    Remove the dependencies Deletes the entries of both modifications in the Depenbetween the modifications dentOn column of the modifications list.
    ... and ... and retain the
    exclusions.

    PTVGROUP

    931

    14.13.4.8 Deleting modifications


    Element

    Description

    Remove the dependencies Deletes the entries of both modifications in the Depenbetween the modifications dentOn column of the modifications list.
    ... and ..., add the two-way Adds entries in the Exclusion column.
    exclusions instead.
    Add the dependency of
    modification ... to ... and
    remove the two-way exclusions.

    For the modification specified first, an entry is added in


    the DependentOn column, listing the name of the second
    modification. If required, the load order is then also changed.
    If there are entries for these modifications in the Exclusion column, these are also deleted, if required.

    6. Click the Finish button.


    The Edit project window opens again. Depending on the option activated, the entries in the
    DependentOn and Exclusion are changed.
    Checking combinability of modifications
    This test allows you to check whether modifications can be applied in the specified sequence
    in a scenario.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    3. In the list, click the modifications of your choice.
    4. Then click the

    Check combinability icon.

    The two modifications are compared. A message window opens, informing you of whether the
    modifications can be combined or not.
    14.13.4.8 Deleting modifications
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    3. In the list, click the modifications of your choice.
    4. Then click the

    Delete modification icon.

    A query opens.
    5. Confirm the query with Yes.
    If there are scenarios using the using, a second confirmation prompt opens.
    6. Confirm the query with Yes.

    932

    PTVGROUP

    14.13.5 Managing scenarios


    The modification is deleted. If this modification was used in scenarios, its allocation to the scenarios is removed.

    14.13.5 Managing scenarios


    A project may include several scenarios. All scenarios of the same project are based on the
    same base version. The difference between scenarios consists in the different modifications
    applied to them. So each scenario has its own version file with a different network and/or
    demand data that you can look at.
    Scenarios may also have different procedure parameters, which may result in different calculations being performed and thus different results being produced.
    You can compare several scenarios and open them similar to version comparison.
    14.13.5.1 Creating scenarios
    To create scenarios, you need a project (see "Creating a project for Scenario management" on
    page 922).
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. Then click the

    Add scenario icon.

    Tip: Alternatively, click the

    Duplicate scenario icon to copy a scenario.

    In the list, a row is created for the new scenario.


    4. Make your changes in the respective columns.
    Element

    Description

    Code

    Code of scenario

    Description

    Description of scenario

    ParameterSet

    By default, a scenario is assigned the same parameter set as the


    base version (entry 0 from base version). If you have specified
    several parameter sets, select the set of your choice from the
    drop-down list (see "Specifying procedure parameters" on page
    935).

    Modifications

    Allocated modifications
    Use this button to allocate modifications to a scenario (see "Assigning modifications to a scenario" on page 934). If you do not allocate a modification, the scenario corresponds to the base version.
    Note

    PTVGROUP

    933

    14.13.5.2 Assigning modifications to a scenario


    Element

    Description
    The ModificationsCompleted column lists the modifications assigned and the modifications that are dependent on the ones assigned. A scenario thus consists of the base version and all
    modifications listed in the ModificationsCompleted column. The
    ModificationsCompletedSortedByLoadOrder column lists all
    modifications of a scenario in the order they are loaded.

    Calculation state

    Calculation state of scenario (see "Calculating scenarios locally


    on a computer" on page 938)

    Last calculation

    Date and time of the last calculation

    Note: Click the Attribute selection symbol


    to show and hide columns (see "The window used for the selection of multiple attributes" on page 968). Here you can also select
    the code numbers you specified in the Basic settings tab (see "Editing basic settings of
    the project" on page 923).
    14.13.5.2 Assigning modifications to a scenario
    To create a scenario, which is different from your base version, you need to assign the scenario modifications. You can only assign a scenario modifications that can be combined. You
    can check in advance whether they can be combined or not (see "Checking combinability of
    modifications" on page 932).
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the row of the respective scenario, in the Modifications column, click the respective button.
    The Modifications window opens.
    4. Select the modifications of your choice.
    5. Confirm with OK.
    The modifications selected are assigned to the scenario. The numbers of the modifications
    selected are displayed on the button in ascending order.
    Note: The button only shows the modifications selected. If one of these modifications is
    dependent on another modification, the latter is also automatically assigned to the scenario. You can find a list of all modifications assigned in the ModificationsCompleted
    column. The ModificationsCompletedSortedByLoadOrder column lists all modifications
    of a scenario in the order they are loaded. The order is specified in the Modifications tab
    (see "Specifying the load order of modifications" on page 930).

    934

    PTVGROUP

    14.13.5.3 Opening the network of a scenario


    14.13.5.3 Opening the network of a scenario
    You can open the network of a scenario. This view solely allows for network checks, the network is not subject to changes.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the list, click the scenario of your choice.
    4. Then click the

    Load scenario (only network) icon.

    The network of the scenario is displayed in the Network editor window. The Edit project window remains open and in the foreground.
    Notes: You should not edit scenarios. All changes you make to a scenario are dismissed
    as soon as you close the scenario. However, you can save scenarios as normal version
    files outside scenario management and then edit them (see "Saving a scenario as a version file" on page 956).
    You can also open a scenario with calculation results (see "Opening a scenario containing calculation results" on page 948).
    14.13.5.4 Deleting scenarios
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the list, click the scenarios of your choice.
    4. Then click the

    Delete scenario icon.

    5. Confirm the query with Yes.


    The scenarios are deleted.

    14.13.6 Specifying procedure parameters


    You can specify several procedure parameters for scenarios. First, you specify the parameters
    for the base version. By default, these are applied to all scenarios. Then, when required, you
    specify additional procedure parameters and assign them to your scenarios.
    14.13.6.1 Specifying procedure parameters for the base version
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Basic settings tab.
    3. Click the Edit base version button.
    The base version is opened. At the same time the Edit base version window opens.

    PTVGROUP

    935

    14.13.6.2 Creating a procedure parameter set


    4. In the version, make the desired changes to the procedure parameters (menu Calculate>
    Procedure sequence and Calculate> General procedure settings).
    Note: If you open or save any files under Procedure sequence, you should use the
    paths suggested. Depending on your settings, the files are either automatically saved
    to a common folder or they are managed per scenario (see "Editing basic settings of
    the project" on page 923).
    5. In the Edit base version window, click the Finish button.
    The Edit project window opens again. Now you can make additional changes to the project.
    14.13.6.2 Creating a procedure parameter set
    You can create a procedure parameter set. To do so, first use the parameters of the version file
    currently open. You can also use the parameters of a procedure parameters file *.par, *.xml or
    a script file *.vbs,*.py, *.pys, *.js, *.rb, *.pl and *.tcl.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Procedure parameter sets tab.
    3. Then click the

    Create a procedure parameter set icon.

    Tip: Alternatively, click the


    an existing set.

    Duplicate the procedure parameter set icon to copy

    The Create a procedure parameter set window opens.


    4. Make the desired changes.
    Element

    Description

    Code

    Short name of the parameter set

    Description

    Description of parameter set

    Use the currently


    loaded procedure
    parameters

    If this option is activated, the new set will receive the procedure
    parameters of the version file currently open.

    Use existing procedure parameters or script


    file

    Select this option and click the respective button to use a procedure parameters file (*.par, *.xml) or a script file (*.vbs,*.py,
    *.pys, *.js, *.rb, *.pl and *.tcl) (see "Saving procedure parameter
    settings to file" on page 1868).
    Note
    If you select a script file that contains other scripts, these must be
    copied manually to the folder of the main script.

    5. Confirm with OK.


    936

    PTVGROUP

    14.13.6.3 Editing procedure parameter sets


    The procedure parameter set is added in a new row. You can then continue to edit the procedure parameters (see "Editing procedure parameter sets" on page 937).
    Note: After specifying the procedure parameters, you have to assign them to the scenario
    of your choice (see "Creating scenarios" on page 933).
    14.13.6.3 Editing procedure parameter sets
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Procedure parameter sets tab.
    3. In the drop-down list, click the procedure parameter set of your choice.
    4. Then click the

    Edit the procedure parameter set icon.

    A scenario, containing a procedure parameter set, is opened. At the same time the Edit the
    procedure parameter set window opens.
    Note: If the procedure parameter set is not used in a scenario, the base version is
    used. In this case, error messages might be displayed, if there are no references.
    Tip: Alternatively, click the same icon in the Scenarios tab to call the function.
    5. In the version file, make the desired changes to the procedure parameters (menu
    Calculate> Procedure sequence and Calculate> General procedure settings).
    Notes: If you open or save any files under Procedure sequence, you should use the
    paths suggested. Depending on your settings, the files are either automatically saved
    to a common folder or they are managed per scenario (see "Editing basic settings of
    the project" on page 923).
    If data is read in during the procedure sequence, make sure this data is not changed
    through other modifications. Otherwise, you might risk that one scenario is overwriting
    the data of another scenario.
    If you are using a script as procedure, the script is automatically opened in the editor
    you specified under Edit> User Preferences> Working environment> Scenario
    management.
    6. In the Edit the procedure parameter set window, click the Finish button.
    The changes are saved. The Edit project window opens again. Now you can make additional
    changes to the project.
    14.13.6.4 Loading procedure parameters from a file
    You can overwrite a procedure parameter set with the procedure parameters of a file.

    PTVGROUP

    937

    14.13.7 Calculating scenarios and showing results


    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Procedure parameter sets tab.
    3. In the drop-down list, click the procedure parameter set of your choice.
    4. Click the

    Select external file for procedure parameter set icon.

    The Open Procedure parameter file window opens.


    5. Select the desired file.
    6. Click the Open button.
    The procedure parameters re copied to the procedure parameter set selected.

    14.13.7 Calculating scenarios and showing results


    You can calculate a scenario and show the calculation results.
    The Calculation state column lists whether a scenario has been calculated and whether the
    calculation results are current.
    14.13.7.1 Calculating scenarios locally on a computer
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. Make the basic settings for scenario calculation (see "Managing compute nodes" on page
    941).
    3. In the Edit project window, click the Scenarios tab.
    4. In the ParameterSet column, select the procedure parameters of your choice (see "Creating a procedure parameter set" on page 936).
    5. In the list, click the scenarios of your choice.
    Tip: To select several scenarios, hold down the C TRL key while you click the individual scenarios.
    6. Then click the

    Calculate scenario icon.

    The scenarios are calculated. The Calculation state column lists the status Calculated. The
    Result file column shows the name of the result version file that Visum automatically assigns.
    If your list contains additional columns with the code numbers you specified, the columns are
    filled with data obtained from the calculation (see "Editing basic settings of the project" on
    page 923).
    14.13.7.2 Distributing scenario calculations across multiple computers
    You can distribute the calculation of scenarios among computers. This allows you to bundle
    computing capacity and produce results more quickly. For distribution of the calculation, use
    the PTV Visum Scenario calculation server software that is installed with Visum. For
    938

    PTVGROUP

    14.13.7.2 Distributing scenario calculations across multiple computers


    calculation distribution, certain requirements must be met (see Fundamentals: Chpt. 2.6.2.6 ,
    page 37)
    Start Scenario calculation server
    To start the Scenario calculation server:
    In the Visum 13 program group, click the
    PTV Visum Scenario Calculation Server
    icon (see "How to install and start Visum" on page 9).
    The
    PTV Visum Scenario Calculation Server icon is shown in the Info section of the Windows task and the server is active.
    Note: As long as the Scenario calculation server is active, you cannot update or install
    the Visum software.
    Setting up the Scenario calculation server
    You need to set up the Scenario calculation server on each computer that is part of your calculation network.
    1. Click the

    icon.

    The PTV Visum Scenario calculation server window appears.


    2. Make the desired changes.
    Scenario calculation server: Basic settings tab
    Element

    Description

    Base directory

    Path to which all scenario files are saved during the calculation
    process.
    The default setting is c:\Users\xxx\Documents\VisumCalculationServer.

    Service address
    section

    Port
    You have to open the port on the computer, so the main computer
    can access the computer network. The port can be freely selected.
    Base path
    The name of the base path can be freely specified.

    Start Visum Scenario Calculation


    Server when logging in

    Select this option to automatically start the Scenario calculation


    server as soon as you log on to your computer.

    Allow conSelect this option to configure the Scenario calculation server


    figuration through through another computer.
    other computers

    PTVGROUP

    939

    14.13.7.2 Distributing scenario calculations across multiple computers


    Element

    Description

    Stop service/Start Click this button to start or stop the server. You can only use the
    service
    computer for distributed calculation if the Scenario calculation server is active.
    Show server log

    Click this button to open the file LogServer.txt of the Scenario calculation server in which all activities of the server are logged.

    Apply

    Click this button to accept all changes to the settings without closing the PTV Visum Scenario calculation server window.

    Exit

    Click this button to shut down the Scenario calculation server.

    Scenario calculation server: Scenario calculation tab


    Maximum number of Visum instan- Specification of maximum number of Visum
    ces for scenario calculation
    instances used simultaneously for calculation
    Number of cores per Visum
    instance

    Selection of number of cores used per Visum


    instance.

    Notes: The selection offered in the lists depends on the number of processor kernels of
    the computer the server is activated on.
    You can also change the settings in Visum, in the project, in the Compute node tab (see
    "Managing compute nodes" on page 941).
    When changing the setting, please note the following:
    The product of these two values should not exceed the number of your compute
    node's processor cores.
    If you have to calculate several scenarios at the same time, it makes sense to select
    the maximum number of Visum instances. If required, however, choose one instance
    less, so that you have one core left to continue working with the compute node
    during scenario calculation.
    In this case, select only one core per instance.
    If you calculate only one scenario at a time, it makes sense to only use one Visum
    instance and assign it all the cores.
    Scenario calculation server: Hold-off times tab
    Do not perform scenario
    calculation
    during hold-off
    times

    If this option is selected, scenario calculation cannot be performed on


    the compute node through another computer during the time periods
    specified. This could for instance be during your regular working
    hours, when you need your full computing capacity.

    Hold-off times Existing hold-off times. You may specify hold-off times for each day of
    the week. To do so, in the Hold-off times column, click the row of your
    choice to edit the hold-off time.

    940

    PTVGROUP

    14.13.7.2 Distributing scenario calculations across multiple computers


    Add hold-off
    time

    Click this button to add new hold-off times to the list.

    Delete hold-off Click this button to delete the hold-off times selected from the list.
    times selected
    Note: As long as the Scenario calculation server is active, you cannot update or install
    the Visum software.
    Managing compute nodes
    You can use any computer of the project to start distributed calculation of scenarios. The Scenario calculation server does not have to be active on the main computer.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Compute nodes tab.
    3. Make the desired changes.
    Element

    Description

    Project ID

    Entry of a name for the Scenario management project.

    Further input files

    Files required for scenario calculation in addition to the base version, modifications, and procedure parameters (see "Copying
    additional files to compute nodes" on page 943).

    Result files

    Files downloaded onto the master computer after the calculations


    performed by the compute nodes (see "Downloading result files
    from the compute node" on page 944).

    Name

    Displays compute node name. localhost is the master computer


    that controls distributed computing.
    Note
    If the Scenario calculation server is activated on the master computer, it is additionally executed as a compute node. Hold-off
    times are then also taken into account.

    State

    Shows activity status of Scenario calculation server in the compute node.


    Ready
    The compute node is available for distributed computing.
    Note
    If hold-off times are set for the compute node, the program also
    displays when the node is available again.
    Wrong server version
    The compute node is available. The Scenario calculation server

    PTVGROUP

    941

    14.13.7.2 Distributing scenario calculations across multiple computers


    Element

    Description
    is active, but has the wrong version number (see Fundamentals:
    Chpt. 2.6.2.6 , page 37).
    Service not available
    Compute node is not found or is not active. This, e.g., happens if
    on a compute node, during a current Visum session, the Scenario
    calculation server is stopped or switched off.
    Unknown error
    Is displayed when any other errors occur during communication
    with the compute node. You can find the error details in the quick
    info.

    Number of Visum
    instances

    Number of Visum instances set on the calculation server. In the


    list box, you can change the number (see "Setting up the Scenario calculation server" on page 939).

    Hold-off times

    Hold-off times of compute node. If processing the compute node


    through another computer is allowed, you can click this button to
    change the settings.

    Number of cores
    per Visum
    instance

    Number of cores used per Visum instance (see "Setting up the


    Scenario calculation server" on page 939).

    Base address

    Shows the computer address specified in the Service address


    section of the compute node's Scenario calculation server (see
    "Setting up the Scenario calculation server" on page 939).

    Note
    When changing the setting, please note the following:
    The product of these two values should not exceed the number of your compute node's processor cores.
    If you have to calculate several scenarios at the same time, it
    makes sense to select the maximum number of Visum instances. If required, however, choose one instance less, so that
    you have one core left to continue working with the compute
    node during scenario calculation.
    In this case, select only one core per instance.
    If you calculate only one scenario at a time, it makes sense to
    only use one Visum instance and assign it all the cores.

    Manual entry of a compute node, if it is not found automatically


    (see "Adding a compute node manually" on page 945).
    Deleting a compute node from the list
    Status of Scenario calculation server of linked compute node
    Automatically search for active compute nodes

    942

    PTVGROUP

    14.13.7.2 Distributing scenario calculations across multiple computers


    Element

    Description
    Note
    All compute nodes are found that lie in the same subnetwork as
    the network.
    Open log file of selected compute node

    The Compute node tab settings are saved to the Visum registry, not to the project.
    Copying additional files to compute nodes
    The base version, modifications, and procedure parameters are automatically transferred to
    each of the compute nodes (see Fundamentals: Chpt. 2.6.2.6 , page 37). To add files to or
    exclude files from distributed computing, click the Additional input files button.
    Note: You must specify these settings to have scenarios calculated on other computers
    than the master computer.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Compute nodes tab.
    3. Then click the Additional input files button.
    The Further input files window opens. Two window sections are displayed. In the left section, you specify the additional files you want to copy to the compute node. In the right section, you specify the files you do not want to copy to the compute node.
    4. Make the desired changes.
    Note: The following paragraph describes how to use the left window section. The right
    window section can be used the same way, but the files specified there will not
    copied to the compute node.

    PTVGROUP

    943

    14.13.7.2 Distributing scenario calculations across multiple computers


    Element

    Description

    Base directory

    List box or folder from which you can copy additional files to the
    compute node. The files are saved to the corresponding folder
    of the compute node (see "Setting up the Scenario calculation
    server" on page 939).
    Note
    You must delete the files there manually that are no longer
    required.
    Files in common (common files)
    In the Project folder, files of the SharedData subfolder are
    copied to the compute node.
    All scenario folders
    Files of the Scenarios folder, in the Project folder, are copied to
    the compute node.
    Scenario folder <Number of scenario>
    Files of the scenario folder specified are copied to the compute
    nodes.

    File name

    Enter the names of the files you want to copy to the compute
    node. Into the field, enter an asterisk * to copy all files of the folder.
    Click the respective symbol to add an additional folder to the
    list.
    Click the respective symbol to delete the selected folder from
    the list.

    Default settings

    Click this button to restore the default settings.

    5. Click the Close button.


    The settings are adjusted.
    Downloading result files from the compute node
    After calculation, the calculation results on the compute nodes are required by the master computer. You may specify which result files are automatically downloaded by the compute nodes
    after the calculation. This is important if you, e.g., have a slow network or work with very large
    scenarios, for which you do not need all result files.
    Note: You must specify these settings to have scenarios calculated on other computers
    than the master computer.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Compute nodes tab.
    3. Then click the Result files button.
    944

    PTVGROUP

    14.13.7.2 Distributing scenario calculations across multiple computers


    The Result files window opens. Two window sections are displayed. In the left window section, you specify the result files you want to download onto the master computer. In the right
    window section, you specify the files you do not want to download.
    Note: The settings in the Result files window are applied automatically, if in the Calculate scenarios window, you selected the option Download result files. If you have
    not selected this option, the settings are applied when in the Scenarios tab, you click
    the

    symbol to download the result files.

    4. Make the desired changes.


    Note: The following paragraph describes how to use the left window section. The right
    window section can be used the same way, but the files specified there are not downloaded.
    Element

    Description

    Base directory

    List box or folder from which you can download files to the master computer. The files are saved to the corresponding folder on
    the master computer.
    Files in common (common files)
    Files of the SharedData folder, in the Project folder, are downloaded.
    All scenario folders
    Files of the Scenarios folder, in the Project folder, are downloaded.
    Scenario folder <Number of scenario>
    Files are downloaded to the Scenario folders specified.

    File name

    Specify the files you want to download. Into the field, enter an
    asterisk * to copy all files of the folder. To select a subfolder,
    enter \folder name*.
    Click the respective symbol to add an additional folder to the
    list.
    Click the respective symbol to delete the selected folder from
    the list.

    Default settings

    Click this button to restore the default settings.

    Adding a compute node manually


    You can manually add a compute node to your project. E.g. if the computer in your network is
    not in the same subnetwork as the master computer of the project.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    PTVGROUP

    945

    14.13.7.2 Distributing scenario calculations across multiple computers


    2. Ensure that a Scenario calculation server is active on the compute node you want to add.
    3. In the Edit project window, click the Compute node tab.
    4. Then click the

    Create computing node symbol.

    The Create computing node window opens.


    5. Make the desired changes.
    Element

    Description

    Name

    Enter a name for the compute node.

    Base address

    Enter the base address of the compute node. You can find it in
    the status bar of the Scenario calculation server of the compute
    node.

    6. Confirm with OK.


    'The compute node is added to the project.
    Distributed calculation of scenarios
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. Make the basic settings for scenario calculation (see "Managing compute nodes" on page
    941).
    3. In the Edit project window, click the Scenarios tab.
    4. In the ParameterSet column, select the procedure parameters of your choice (see "Creating a procedure parameter set" on page 936).
    5. In the list, click the scenarios of your choice.
    Tip: To select several scenarios, hold down the C TRL key while you click the individual scenarios.
    6. Then click the

    Calculate scenario icon.

    The Calculate scenarios window opens.


    Note: The window only opens if you have activated the Distributed computing
    module (see "Enabling or disabling installed add-ons" on page 886). If you do not
    have this module, a security query is displayed.
    7. Make the desired changes.

    946

    PTVGROUP

    14.13.7.3 Resetting the calculation status of scenarios


    Element

    Description

    Number

    Displays the scenario number

    Code

    Shows the scenario code

    Compute nodes

    List box with the available compute nodes. Use the list box to allocate the compute node.

    Download result
    files

    Select this option to download the result files automatically. Use


    the settings in the Result files window to specify the files you
    want to downloaded automatically (see "Copying additional files
    to compute nodes" on page 943).
    Note
    This option is automatically selected and cannot be changed, if
    the calculation is performed locally on the computer.

    Distribute scenarios evenly to


    computing nodes

    Click this button to distribute the scenarios evenly across the compute nodes.

    Calculate all sce- Click this button to calculate all scenarios locally on the computer.
    narios on this computer
    Download all
    result files

    All result files are selected for automatic download.


    Note
    You can use this option with distributed computing.

    No download of
    result files

    None of the result files are selected for automatic download.


    Note
    You can use this option with distributed computing.

    8. Confirm with OK.


    The scenarios are recalculated. In the Calculation state column, the state Calculated is displayed, after the calculations have been carried out. In the Compute node column, the compute node on which the scenario was calculated is displayed. The Result file column shows
    the name of the result version file that Visum automatically assigns. If your list contains additional columns with the code numbers you specified, the columns are filled with data obtained
    from the calculation (see "Editing basic settings of the project" on page 923).
    14.13.7.3 Resetting the calculation status of scenarios
    You can reset the calculation status of a scenario. Then the code numbers and version file calculated are automatically deleted.
    1. Make sure that the desired project is open (see "Editing basic settings of the project" on
    page 923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the list, click the scenarios of your choice.

    PTVGROUP

    947

    14.13.7.4 Opening a scenario containing calculation results

    4. Then click the

    Reset calculation state icon.

    A query opens.
    5. Confirm the query with Yes.
    The calculation status is reset to Not calculated.
    14.13.7.4 Opening a scenario containing calculation results
    You can show the calculation results of a calculated scenario. This view solely allows for network checks, the network is not subject to changes.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the list, click the calculated scenario of your choice.
    4. Then click the

    Load scenario including results icon.

    The scenario and its calculation results are displayed in the Network editor window. The Edit
    project window remains open and in the foreground.
    Note: You should not edit scenarios. All changes you make to a scenario are dismissed
    as soon as you close the scenario. However, you can save scenarios as normal version
    files outside scenario management and then edit them (see "Saving a scenario as a version file" on page 956).
    14.13.7.5 Showing message and log files of scenarios
    You can show the message file and log file of a calculated scenario (see "Viewing log files" on
    page 879).
    Note: A message file and log file will only exist, if you have made the corresponding setting (see "Specifying settings for protocol files" on page 876).
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the list, click the scenario of your choice.
    4. Then click the

    Show log file or

    Show message file icon.

    The corresponding window opens.

    14.13.8 Comparing scenarios


    You can compare two scenarios. To do so, use version comparison (see "Comparing versions" on page 892). At first, you specify comparison patterns that form the basis for your comparison.

    948

    PTVGROUP

    14.13.8.1 Specifying comparison patterns


    14.13.8.1 Specifying comparison patterns
    To compare two scenarios, you specify comparison patterns. These include the network
    objects and attributes that you want to compare. The procedure is the same as for version comparison (see "Comparing versions" on page 892). You can use both types of version comparison.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Comparison pattern tab.
    3. Then click the

    Create a comparison pattern icon.

    Tip: Alternatively, click the


    parison pattern.

    Duplicate the comparison pattern icon to copy a com-

    The Define comparison pattern window opens.


    4. Make the desired changes.
    Element

    Description

    Define comparison

    On calculated results of the scenarios


    If this option is activated, you open the version files of the two scenarios calculated to create a comparison pattern. Select this
    option e.g. to show calculation results using link bars.
    On input data of the scenarios
    If this option is activated, you open the networks of the scenarios
    to create a comparison pattern. They do not contain any calculation results. This option is used to compare the networks of
    scenarios.

    Scenarios for the


    comparison definition

    Leading scenario
    Select the scenario used as a leading version file to create the
    comparison pattern. This file contains the comparison attributes.
    Comparison scenario
    Select the scenario used as a comparison version file to create
    the comparison pattern. This version file contains the comparison
    attributes listed in the leading version file.
    Notes
    Select the On calculated results of the scenarios option, to only
    show the calculated scenarios in the drop-down lists.
    You can change the scenarios you choose here later on, when
    applying the comparison patterns. You should choose scenarios
    that contain the data you want to compare, so that you can e.g.

    PTVGROUP

    949

    14.13.8.1 Specifying comparison patterns


    Element

    Description
    select the appropriate graphic parameters.

    Header data of the Code


    comparison patCode of comparison pattern
    tern
    Description
    Short description of the comparison pattern
    5. Click the Edit the comparison pattern button.
    The Generate version comparison window opens.
    Creating a comparison pattern for version comparison, including the adoption of attributes
    To perform a version comparison, including the adoption of attributes into the leading network:
    1. In the Type of version comparison section, select Use attributes from comparison network.
    2. Make the desired changes.
    Element

    Description

    Type of version
    comparison

    Use attribute from comparison network


    If this option is selected, Visum adopts the attributes of the comparison network into the leading network.

    Change link bars


    automatically to
    differences

    If this option has been selected, scaling and classification attributes of link bars are automatically converted to the new attribute
    generated by the version comparison with the difference between
    the original and the newly added attribute value.

    3. Confirm with OK.


    The Create version comparison (User-defined) window opens.
    4. If required, reduce the amount of data you want to compare.
    Element

    Description

    Hide calculated
    attributes

    If this option has been selected, only selected readable attributes and their values are compared additionally to the key attributes.
    If this option has not been selected, both readable and non-readable attributes and their values are compared.

    Hide attribute with


    If this option has been selected, only selected attributes and
    default values
    their values are compared.
    If this option has not been selected, all selected attributes and
    their values are compared, disregarding whether attribute value

    950

    PTVGROUP

    14.13.8.1 Specifying comparison patterns


    Element

    Description
    and default value are identical or not.
    Note
    You can find the default attribute values in the Attribute.xls file,
    under ...\Program files\PTV Vision\PTV Visum 13\Doc.

    Hide empty tables If this option has been selected, only tables containing network
    objects are compared.
    5. Select the network object types to be compared.
    Element

    Description
    This network object type is used for comparison.
    This network object type is not used for comparison.

    Check all tables Click this button to select all network object types.
    Uncheck all
    tables

    Click this button to deactivate all network objects and their attributes.

    6. Click a network object type.


    The attributes and, if applicable, the subattributes of the network object type are displayed.
    Tip: Click the CTRL key and keep it pressed while clicking the desired entries one by
    one to show the attributes of multiple network object types at the same time.
    Note: Due to current settings in the upper section of the window not all attributes of a
    network object type may be displayed.
    7. Select the attributes and subattributes you want to compare.
    Element

    Description
    The attribute has been selected and is compared.
    The attribute has not been selected and is not compared.
    The attribute is a key attribute and cannot be switched off.
    The attribute is a mandatory attribute.

    Attribute
    groups

    Via this button you can either select or switch off predefined groups of
    attributes in a separate window (see "Selecting or deselecting groups
    of attributes for comparison" on page 897).

    Standard

    Click this button to hide empty tables and display calculated attributes. The attribute selection is reset to the standard setting.

    PTVGROUP

    951

    14.13.8.1 Specifying comparison patterns


    Tip: Right-click a network object type. Then use the context menu to activate or deactivate all currently displayed attributes of the network object type.
    Tip: Alternatively, you can read selected network object types and attributes from a
    network file *.net (see "Reading a layout from a network file" on page 898).
    8. Confirm with OK.
    The Edit the comparison pattern window opens. At the same time, the leading scenario
    selected is opened as a version file that allows you to make further settings.
    9. In the Edit the comparison pattern window, make the settings of your choice.
    Element

    Description

    Graphic parameters configuration

    Select this option to save the graphic parameters used in the current version file together with the version pattern.

    Filter configuration

    Select this option to save the filter settings used in the current version file together with the version pattern.

    List layout configuration

    Select this option to save the lists and their layout in the current
    version file together with the version pattern.

    10. If required, specify the graphic parameters and filter settings in the version file.
    Tip: To do so, use the corresponding menus or read in new data.
    11. If required, open the lists of your choice in the version file to specify their layout.
    Tip: You can e.g. show specific columns or load a list layout.
    12. Click the Finish button.
    A new entry is then listed in the Comparison pattern tab.
    Creating a comparison pattern for version comparison, including comparison network in
    the background
    If you want to compare versions and keep the comparison network open in the background
    with the attributes linked via relations, please follow this approach after step 6:
    1. Select Load comparison network in the background below Type of version comparison.
    Note: Visum loads the comparison network in the background and links the attributes
    with the leading network via relations (see Fundamentals: Chpt. 2.5.1 , page 23).
    2. Specify any further settings you need.

    952

    PTVGROUP

    14.13.8.2 Editing comparison patterns


    Element

    Description

    Do not adopt matri- Click this option if you do not want to adopt matrices from the comces
    parison network. Then less storage space is required.
    Change link bars
    automatically to
    differences

    If this option has been selected, scaling and classification attributes of link bars are automatically converted to the new attribute
    generated by the version comparison with the difference between
    the original and the newly added attribute value.

    3. Confirm with OK.


    The Edit the comparison pattern window opens. At the same time, the leading scenario
    selected is opened as a version file that allows you to make further settings.
    4. In the Edit the comparison pattern window, make the settings of your choice.
    Element

    Description

    Graphic parameters configuration

    Select this option to save the graphic parameters used in the current version file together with the version pattern.

    Filter configuration

    Select this option to save the filter settings used in the current version file together with the version pattern.

    List layout configuration

    Select this option to save the lists and their layout in the current
    version file together with the version pattern.

    5. If required, specify the graphic parameters and filter settings in the version file.
    Tip: To do so, use the corresponding menus or read in new data.
    6. If required, open the lists of your choice in the version file to specify their layout.
    Tip: You can e.g. show specific columns or load a list layout.
    7. Click the Finish button.
    A new entry is then listed in the Comparison pattern tab.
    14.13.8.2 Editing comparison patterns
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Comparison pattern tab.

    Note: Click the Attribute selection symbol


    to show and hide columns (see "The
    window used for the selection of multiple attributes" on page 968).

    PTVGROUP

    953

    14.13.8.3 Deleting comparison patterns


    3. In the list, click the comparison pattern of your choice.
    4. Then click the

    Edit the comparison pattern icon.

    The Edit the comparison pattern window opens.


    5. Make the desired settings (see "Specifying comparison patterns" on page 949).
    The comparison pattern is changed.
    14.13.8.3 Deleting comparison patterns
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Comparison pattern tab.
    3. In the list, click the comparison patterns of your choice.
    4. Then click the

    Delete the comparison pattern icon.

    5. Confirm the query with Yes.


    The comparison patterns are deleted.
    14.13.8.4 Comparing scenarios
    You can compare several scenarios. In this case, you perform a version comparison based on
    a comparison pattern (see "Comparing versions" on page 892 and "Specifying comparison patterns" on page 949)
    Note: To use the base version for comparison, simply create a new scenario that only
    contains the base version without any modifications.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. Select at least two scenarios.
    Note: To compare calculation results, you first have to calculate the scenarios.
    4. Click the

    Compare scenarios icon.

    The Compare scenarios window opens.


    5. Make the desired changes.

    954

    PTVGROUP

    14.13.9 Exporting data of a Scenario management project


    Element

    Description

    Comparison pat- Comparison pattern used for the comparison


    tern
    Run comparison

    For calculation results of the scenarios


    Select this option to open the version files of the scenarios calculated and create a scenario comparison. Select this option e.g. to
    show calculation results using link bars.
    For input data of the scenarios
    Select this option to open the networks of the scenarios and create a
    scenario comparison. They do not contain any calculation results.
    This option is used to compare the networks of scenarios.

    Leading scenario

    In the drop-down list, click the scenario to open it. It contains the comparison attributes of other scenarios.
    Note
    Select the For calculation results of the scenarios option, to only
    show the calculated scenarios in the drop-down list.

    Scenarios

    List of selected scenarios


    Note
    Select the For calculation results of the scenarios option, to only
    show the calculated scenarios.

    6. Then click the Compare button.


    The versions are compared. The version file of the leading scenario is opened. It contains the
    comparison attributes of the other scenarios selected (see "Comparing versions" on page
    892).

    14.13.9 Exporting data of a Scenario management project


    A project of scenario management consists of a folder with several subfolders and files.
    Note: You must not change the folder structure of the project in the Windows explorer.
    However, you can export the data of a project to edit it outside Scenario management or pass
    it on to other users.
    14.13.9.1 Forward project
    You can forward a project to other users by copying the entire base folder. The base folder of a
    project is named according to the project name. This project name has to be specified when
    the project is created. The base folder stores the project database file *.vpdb and various subfolders. You may not change the structure of a base directory.
    All project directory settings are automatically changed in the new copied directory, as the
    paths are relative to the directory.

    PTVGROUP

    955

    14.13.9.2 Saving a scenario as a version file


    14.13.9.2 Saving a scenario as a version file
    You can export a scenario of a Scenario management project to edit it outside the project.
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Scenarios tab.
    3. In the list, click the scenario of your choice.
    4. Then click the

    Save scenario as icon.

    The Save version window opens.


    5. If necessary, select a different directory.
    6. Enter a file name.
    7. Click the Save button.
    The scenario is saved.
    Tip: Alternatively, open the scenario as a version file and save it under another name.
    14.13.9.3 Saving modifications as a model transfer file
    1. Make sure the desired project is open (see "Editing basic settings of the project" on page
    923).
    2. In the Edit project window, click the Modifications tab.
    3. In the list, click the modification of your choice.
    4. Then click the

    Save modification as icon.

    The Save: Model transfer file window opens.


    5. If necessary, select a different directory.
    6. Enter a file name.
    7. Click the Save button.
    The modification is saved.
    Tip: Alternatively, open the modification as a model transfer file and save it under another
    name.

    956

    PTVGROUP

    15 Editing the network

    15

    Editing the network


    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:
    Nodes and main nodes
    Links
    Turns and main turns
    Zones and main zones
    Zone connectors
    Territories
    Paths and paths sets
    Stops with stop areas and stop points (PuT)
    PuT lines with line routes, time profiles, and main lines
    System routes (PuT)
    The network model also contains the following data:
    Operational data on PuT vehicles and on public transport operators
    Points of Interest (POIs), count locations, detectors, toll systems, and screenlines
    Territories for precise PrT and PuT indicator calculations (with user-defined territory boundaries)
    GIS objects, which are active within the network only during a Personal Geodatabase
    connection
    Visum provides different kinds of network objects:
    Point objects are defined by means of co-ordinates.
    Line objects have a spatial course.
    Polygonal objects are point objects with a spatial extent. They are modeled by means of a
    centroid and a boundary polygon (see "Managing boundaries of polygonal network
    objects" on page 1042).
    Network objects are described by means of attributes. You can enter the values of some attributes; other attribute values are calculated (see "Managing attributes" on page 958).
    Network processing modifies the properties of the transport network. This may produce different indicator values and assignment results.
    Notes: As long as you modify only attribute data of network objects, for example, the
    length of a link, the current assignment result will not be initialized, even though a new
    calculation of the assignment might produce a different result.
    In the case of modifications to the network structure, a current assignment result is initialized. Inserting, deleting, or renumbering a network object as well as merging nodes, splitting zones or links, and aggregating zones are changes to the network structure. PuT
    assignment results are kept if new zones and connectors are inserted.

    PTVGROUP

    957

    15.1 Network object types


    Subjects
    Network object types
    Managing attributes
    Editing attribute values of network objects
    The operating modes of the network model
    Finding network objects in the network
    Marking network objects in the network
    Using filters to set network objects active or passive
    Setting network objects active/passive via the spatial selection
    Checking the state of network objects
    Managing boundaries of polygonal network objects
    Managing transport systems, modes and demand segments
    Working with individual network objects
    Using the Junction editor
    Checking the network and fixing errors
    Specifying a calendar and valid days
    Using the Timetable editor
    Using the subnetwork generator

    15.1

    Network object types


    The Fundamentals volume provides an overview of all network object types of the Visum network (see Fundamentals: Chpt. 3.1 , page 40).

    15.2

    Managing attributes
    Network objects are described by means of attributes. The Basics manual provides detailed
    information on attributes (see Fundamentals: Chpt. 3.3 , page 103). Here is a short overview of
    the types of attributes in Visum:
    Direct attributes
    Direct attributes describe an attribute directly. As a rule, they are predefined and can be subdivided into the following types:
    Input attributes: The user enters the values of these attributes.
    Output attributes (or calculated attributes): The values of these attributes are calculated
    automatically by Visum.
    Indirect attributes
    Indirect attributes are direct attributes of other network objects, which bear a network model
    relation to the currently selected network object.
    User-defined attributes
    In addition to the predefined attributes, the user can define any desired attributes, which they
    can edit or manage like predefined attributes. Formula attributes are a particular form of userdefined attributes. They are not used for direct storage of data, but represent an operand
    which encompasses other attributes (see Fundamentals: Chpt. 3.3.3.1 , page 113).
    Time-varying attributes

    958

    PTVGROUP

    15.2.1 Specifying general settings for attributes


    Time-varying attributes only affect the procedures Dynamic User Equilibrium and Dynamic Stochastic assignment. Time variations can only be set for specific network objects with a time
    reference.
    Characteristics of attributes
    Each attribute has a unique attribute ID in English, as well as a short name and a long name.
    Example: The attribute Number has the attribute ID No, the long name Number and the short
    name No.
    The Attributes.xls file contains the complete list of all network object types and their attributes
    with IDs, short names and long names.
    Subjects
    Specifying general settings for attributes
    The Attributes.xls file
    Accessing attributes
    The window used for the selection of one attribute
    The window used for the selection of multiple attributes
    Managing user-defined attributes
    Managing time-varying attributes

    15.2.1

    Specifying general settings for attributes


    Displaying short names or long names of attributes
    Specifying settings for the attribute selection windows
    Settings for decimal places and aggregate functions

    15.2.1.1

    Displaying short names or long names of attributes


    You can specify the display of the short name or the long name of attributes separately for lists,
    the Quick view and the Junction editor.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the GUI entry.
    3. Select one of the entries Lists, Quick view or Junction editor.
    The page Lists, Quick view or Junction editor opens.
    4. Specify the desired setting under Column headers or Row labels.
    5. Confirm with OK.

    15.2.1.2

    Specifying settings for the attribute selection windows


    You can specify basic settings for the attribute selection windows (see "The window used for
    the selection of one attribute" on page 963 and "The window used for the selection of multiple
    attributes" on page 968).
    1. From the Edit menu, choose User Preferences.

    PTVGROUP

    959

    15.2.1.3 Settings for decimal places and aggregate functions


    The User Preferences window opens.
    2. In the navigator, select the GUI> Attribute selection entry.
    The Attribute selection page opens.
    3. Define the desired settings:
    Element

    Description

    Use AP as a preset analysis time


    slot for attribute
    selection

    If the option has been checked, the analysis time slot is always
    preset with AP (analysis period). By default, no analysis time slot
    is selected (see "Preset the analysis time slot" on page 967).

    Sorting for attribute selection

    Select the sorting that shall be displayed by default: Classical,


    alphanumerical, hierarchical (see "The window used for the selection of one attribute" on page 963).

    4. Confirm with OK.


    15.2.1.3

    Settings for decimal places and aggregate functions


    1. From the Network menu, choose Network settings.
    The Network settings window opens.
    2. Select the Attributes tab.
    3. Make the desired changes.
    Section
    Standard number of decimal places per data type

    960

    Element

    Description

    Coordinates

    The coordinates are displayed with the set number of decimal places. The setting has an effect on the following points in Visum, for
    instance:
    Editing background objects (see "Editing a background" on
    page 2247)
    WKT attributes
    Editing graphic parameters (see "Specifying basic settings"
    on page 2337)
    Editing network objects: Zones, territories, detectors, main
    zones, nodes, POIs, stops, stop areas
    Status bar of program window (cursor position) (see "Program interface" on page 804)

    Speed

    Speed is displayed with the set number of decimal places. The


    setting has an effect on the following points in Visum, for instance:
    Graphic parameters of isochrones (see "Setting graphic para-

    PTVGROUP

    15.2.1.3 Settings for decimal places and aggregate functions


    Section
    Standard number of decimal places per data type

    Element

    Description
    meters for the display of isochrones" on page 2288)
    Standard values of connectors (see "Specifying standard
    values for connectors" on page 1159)

    Short length (m, ft) The short length is displayed with the set number of decimal places. The setting has an effect on the following points in Visum, for
    instance:
    Intersecting objects (see "Intersecting objects" on page 2217)
    Long length (km,
    mi)

    The long length is displayed with the set number of decimal places. The setting has an effect on the following points in Visum, for
    instance:
    Detectors, editing stop points (see "Managing detectors" on
    page 1410 and "Managing stop points" on page 1266)
    PuT fares window (see "Defining PuT fares" on page 2171)
    Displaying turn volumes (see "Adjusting the basic settings for
    the display of turn volumes" on page 2437)
    Aggregating nodes (see "Aggregating isolated nodes" on
    page 1076)

    Currency

    The currency is displayed with the set number of decimal places.


    The setting has an effect on the following points in Visum, for
    instance:
    PuT fares window (see "Defining PuT fares" on page 2171)
    Editing operators (see "Editing the attribute values of operators" on page 1282)
    Vehicle units and vehicle combinations (see "Properties and
    options of vehicle units" on page 1284 and "Properties and
    options of vehicle combinations" on page 1287)

    t0 at (main) turns

    The attribute value at turns and main turns is displayed with the
    set number of decimal places. The setting has an effect on the following points in Visum, for instance:
    Editing turns (see "Editing main node attributes in the list
    view" on page 1452)
    Editing main turns (see "Editing main turn attributes in the list
    view" on page 1456)

    PTVGROUP

    961

    15.2.2 The Attributes.xls file


    Section
    Standard number of decimal places per data type

    Element

    Description

    Other numbers
    with decimal places

    The attribute value at user-defined attributes is displayed with the


    set number of decimal places. The setting has an effect on the following points in Visum, for instance:
    Creating user-defined attributes (see "Creating a user-defined attribute" on page 973)

    Always output floa- If this option has been selected, values are saved in files of type
    ting point numbers *.net, *.dmd and *.tra with the maximum possible number of deciin network,
    mal places (twelve at maximum). Other settings for numbers with
    demand and
    decimal places are ignored.
    model transfer
    files with maximum precision

    Section
    Aggregate functions 'Concatenate' and 'Histogram' with indirect attributes and aggregation

    Element

    Description

    Separator

    You can specify the separator that separates multiple listed output attribute values (e.g. in lists).
    The comma is set as default.
    Note
    The semicolon ;, the dollar sign $ and the double prime sign are
    not permitted.

    Maximum string
    length (blank =
    unlimited)

    You can enter any desired value or leave the field blank. If the
    length of the output attribute values exceeds the specified value,
    the output is cut off. If no value is specified, the output is not cut
    off.
    The default value is 255.

    4. Confirm with OK.

    15.2.2

    The Attributes.xls file


    The Attributes.xls file (...\Program files\PTV Vision\PTV Visum 13\Doc\Eng ) contains a complete list of all network object types (or all tables) and all attributes (with ID, short name, and
    long name) in all languages provided by Visum.
    The attributes are listed in the following tabs:
    All attributes are listed in the Attributes tab (completed by the ENumStrings (enums) and
    SubAttributes tabs).

    962

    PTVGROUP

    15.2.3 Accessing attributes


    The relations of the attributes are listed in the Relation tab.
    New, deleted, and modified attributes are listed accordingly in the Attr_new, Attr_deleted, Attr_modified tabs.
    The file contains the following information on each attribute:

    15.2.3

    Column

    Description

    In/output

    Input attribute or output attribute

    Type

    Compulsory/optional (input) or calculated/optional (output)

    Editable

    Editable (yes/no)

    ValueType

    Data type (for example integer, real, time period, string, string long)

    SubAttr

    Subattribute, for example transport system or analysis horizon

    Category

    Group of the attribute

    Source

    Data source, for example assignment

    Modules

    Depending on the add-on module

    Min/Max

    Value range

    DefaultVal

    Standard value for the default

    CrossValue

    Treatment of undirected values

    CanBeTemporary

    Can be time-varying (yes/no)

    Description

    Description of the attribute

    Accessing attributes
    Visum provides several ways to access attributes. You can, for example, click the
    attributes icon.

    Select

    This is where you can access attributes in the program:


    In the Quick view window (see "Quick view window" on page 810)
    In the list view of a network object type (see "Editing the properties of objects in lists" on
    page 2321)
    In the junction editor (see "Using the Junction editor" on page 1435)
    In the Create or Edit window of a network object
    In the Multi-edit window in the Edit mode
    In the Edit graphic parameters window (see "Specifying basic settings for the network
    window" on page 2337)
    In the filter window (see "Opening a filter window" on page 1008)
    In the Marking window

    15.2.4

    The window used for the selection of one attribute


    If you can select only one attribute in the program (for example, when choosing an attribute for
    the classified drawing mode in the graphic parameters), the Attributes (<Network object
    type>) window opens.

    PTVGROUP

    963

    15.2.4 The window used for the selection of one attribute

    Note: If you position your mouse pointer over an attribute, a quick info appears. It shows
    its long name, for indirect attributes it specifies additionally the related network object
    type and, if applicable, the aggregate function of the attribute.
    Section
    Address
    bar

    Name

    Description
    The address bar is particularly useful when dealing with indirect attributes. It displays the full path of the marked attribute. In case of attributes with a time reference, the attribute name is completed by a
    short form of the currently set analysis time slot.
    Use this icon to find an attribute in the list. Enter the name of the
    wanted attribute in the attribute bar and click the icon. The attribute
    will be marked in the list.
    Tip
    You can also search for indirect attributes. To do this, enter for example the following: From node\Number

    964

    PTVGROUP

    15.2.4 The window used for the selection of one attribute


    Section

    Name

    Description

    C, A, H

    Click the icon to switch to between the three possible types of sorting:
    C = the classical sorting (default setting). The most frequently
    used attributes are listed at the top of the list, indirect attributes
    are listed at the bottom.
    A = the alphanumerical sorting. When picking this sorting, special entries (for example 1.0 or no selection) are listed first, and
    then, in alphabetical order, the direct attributes, and finally the
    indirect attributes. Attributes on lower levels are also arranged
    in alphabetical order.
    H = the hierarchical sorting. When picking this sorting, special
    entries are listed first. Then, one directory is listed for each existing attribute category (marked by a c). These contain the direct
    attributes of the respective category in alphabetical order.
    Finally, the indirect attributes are listed in alphabetical order.
    Note
    You can adjust the default setting (see "Specifying settings for the
    attribute selection windows" on page 959).

    Create
    alias

    Use the icon to specify a user-defined alias for an attribute name for
    a faster access. The alias is listed in addition to the preset short or
    long name (see "Specifying an alias for attribute names" on page
    967).

    Graphic
    indicators in
    the list

    Form

    Dot
    Signifies existing attribute values, i.e. input attributes and calculated
    output attributes.
    Ring
    Signifies output attributes that are not calculated yet.
    c (=category; in the hierarchical sorting order only)
    Signifies attribute categories that contain the direct attributes of the
    respective category in alphabetical order.

    Graphic
    indicators in
    the list

    Color

    Green
    Signifies attributes without subattributes.
    Red
    Signifies attributes for which you need to select a subattribute.
    The list of subattributes opens if you click the plus sign.
    Gray
    Signifies attributes for which the respective add-on module is not
    activated or matrices that are not available
    Blue

    PTVGROUP

    965

    15.2.4.1 Indirect attributes: relation types and aggregate functions


    Section

    Name

    Description
    Signifies aliases, i.e. attribute names created by the user.
    Black
    Signifies user-defined attributes.

    Preset
    the analysis time
    slot

    Button

    15.2.4.1

    In the Preset the analysis time slot list, you can specify an analysis
    time slot before selecting an attribute. It is relevant to attributes with
    a time reference, for example, the Volume. If you select an attribute
    with a time reference, it will be set for the analysis time slot selected
    here (see "Preset the analysis time slot" on page 967).
    Note
    You can adjust the default setting (see "Specifying settings for the
    attribute selection windows" on page 959).
    New

    If you click the New icon, the Create user-defined attribute <(Network object type)> window opens. Here you can create a user-defined attribute (see "Managing user-defined attributes" on page 973).

    Indirect attributes: relation types and aggregate functions


    Relation types of indirect attributes
    In the classical sorting, indirect attributes are listed at the bottom of the list. They can be related
    to the network object in three different ways. These relations are called relation types in Visum.
    The following indicators depict the relations between the currently selected network object
    type and its indirect attributes:
    Indicator

    Description
    The network object has got exactly one associated network object in the respective category.
    The network object has got either exactly one or no associated network object
    in the respective category.
    The network object has got several associated network objects in the respective
    category. These are aggregated by aggregate functions.

    Note: If you position the mouse pointer on an indirect attribute, a quick info indicates the
    full path, the name, an explanation and the origin of the attribute.
    Aggregate functions of indirect attributes
    If you expand a relation of a network object with several associated network objects, aggregate functions are displayed. These indicate how the associated network objects are aggregated. They refer to either all objects (Count ) or all active objects (CountActive ) of the
    relation.

    966

    PTVGROUP

    15.2.4.2 Specifying an alias for attribute names


    Count and CountActive (Number of all associated network objects)
    Min and MinActive
    Max and MaxActive
    Sum and SumActive
    Avg and AvgActive
    Concatenate and ConcatenateActive
    Histogram and HistogramActive
    Distinct and DistinctActive
    Notes: You can use the aggregation function Histogram to get a quick overview of an
    attribute of another network object, for example, the link types of all links of a node. Identical values will then be displayed in groups.
    These aggregate functions only refer to the output of attribute values in lists, graphic parameters, filters or in the Quick view.
    15.2.4.2

    Specifying an alias for attribute names


    Specifying an alias can be useful if you frequently click on an indirect object which is found at
    the bottom of the display hierarchy. An alias is listed in addition to the predefined attribute
    name. If an alias has been specified, the attribute is thus listed twice.
    Tip: If in the Network menu you select the Aliases entry, you can get an overview of all
    existing aliases of the network. In the window you can display the aliases of individual or
    all objects. In the list you can create new aliases and edit or delete existing aliases.
    1. In the list, mark the attribute for which you want to specify an alias.
    2. Click the Alias button.
    The Create alias for <network object type> window opens.
    3. Enter the desired alias and click OK.
    The alias appears at the top of the list. A blue dot or ring indicates an alias. The Alias button is displayed in red.
    Editing or deleting an alias
    Right-click the alias to edit or delete it.
    A context menu opens. Here you can specify whether you want to delete or edit the alias.
    Notes: In the classical and in the alphanumerical sorting, aliases are displayed at the
    very top. In the hierarchical sorting, they are listed under Alias.
    Aliases are saved with the network file and with the version file when saving networks.
    Internally, only the attribute ID is saved.

    15.2.4.3

    Preset the analysis time slot


    In the Preset the analysis time slot list, you can select an analysis time slot. It is relevant to
    attributes with a time reference, for example, the Volume . If you select an attribute with a time

    PTVGROUP

    967

    15.2.5 The window used for the selection of multiple attributes


    reference, it will be set automatically for the analysis time slot selected here.
    The Fundamentals manual provides further information on analysis time slots (see Fundamentals: Chpt. 3.2.3 , page 98).
    Apart from the user-defined analysis time periods, the following entries can be selected:
    -: no analysis time slot selected
    AP: Analysis period
    AH: Analysis horizon
    CurInt: time interval currently selected in the Network editor window
    User-defined analysis time intervals
    Note: If you select entry - (no analysis time slot) in the Preselected analysis time slot
    list, in the navigator, the display of the attributes changes. All attributes with a time reference are displayed with subentries that correspond to the existing analysis time intervals. This way, you can select the desired analysis time slot directly for an attribute.

    15.2.5

    The window used for the selection of multiple attributes


    If, in the program, you can select more than one attribute, for example, in the Quick view or in
    the Timetable editor, the Attribute selection (<Network object type >) window opens. The attribute selection in the list view and the Quick view provides additional functionalities which enable you to define an aggregated list view.
    The window is separated in two sections:
    The upper section shows the current attribute selection. These are the currently selected
    attributes and their settings. You can edit these settings.
    The lower section shows the attributes that you can add to the attribute selection. This window essentially corresponds to the one that is used to select one attribute (see "The window used for the selection of one attribute" on page 963).

    968

    PTVGROUP

    15.2.5.1 Adding a group of attributes to the attribute selection

    Note: If you position your mouse pointer over an attribute, a quick info appears. It shows
    its long name, for indirect attributes it specifies additionally the related network object
    type, the source and, if applicable, the aggregate function of the attribute.
    1. In the upper section, mark the attribute below which you want to insert a new attribute.
    2. If required, edit the preselection of the analysis time periods of the attributes with a time reference for which you want to display attribute values.
    3. In the lower section of the navigator, click the desired attribute.
    4. Click the Add button.
    The attribute is inserted in the desired position in the list of selected attributes.
    Deleting attributes from the selection
    1. In the upper list, mark the desired attributes.
    2. Click the Delete button.
    The marked attributes are deleted from the selection.
    15.2.5.1

    Adding a group of attributes to the attribute selection


    1. Click the Add group button.

    PTVGROUP

    969

    15.2.5.2 Editing the display properties of attributes


    The Add group of attributes window opens.
    2. Select the option specifying the group of attributes you want to add: All user-defined attributes, All editable attributes, All attributes.
    3. Click OK.
    The selected group is added to the attribute selection.
    Note: The Add group button is not available if you open the Attribute selection (Network) window in the Basic settings tab of the scenario management.
    15.2.5.2

    Editing the display properties of attributes


    In the upper window section, specify how the selected attributes shall be displayed when output. The settings that you can specify depend on the type of the attribute. The Attribute selection (<Network object type>) window of the list view contains additional functionalities. They
    are used to define an aggregated list view.
    Column

    Description

    Attribute

    Name of the selected attribute


    You cannot edit the name of the attribute.

    Grouping
    (in list view
    only)

    You can aggregate network objects with the same attribute value in one
    row. If you activate this option for an attribute, for all other attributes (or
    columns) you need to specify how their attribute values shall be aggregated. You can specify a grouping for one or multiple columns.
    Example: You want to determine the average length of links of type 20.
    For that purpose, group the links by attribute TypeNo in the list. This
    aggregates all links of type 20 in one row. For the length attribute, select
    the aggregate function Average. Visum then determines the average
    length of links of type 20 and displays the value in the Avg(Length)
    column.

    Aggregate
    function

    Here you determine which aggregate function shall be used (see "Selecting an aggregate function for a column in a grouped list" on page 2311).

    (only in list
    view and Quick
    view)
    Weight
    (only in list
    view and Quick
    view)

    970

    If you have selected Weighted average as aggregate function, weighting


    1.0 is set as a default. Click the box and the Attribute (<Network object
    type>) window opens where you can select the attribute by which you
    want to weight (see "Selecting an aggregate function for a column in a
    grouped list" on page 2311).
    This option is only available for numerical attributes.

    PTVGROUP

    15.2.5.2 Editing the display properties of attributes


    Column

    Description

    Decimal places

    Number of displayed decimal places


    You can use these buttons to increase or decrease the number of decimal places.
    The option is only available for attributes of the type decimal place.
    You can edit the default value (see "Settings for decimal places and
    aggregate functions" on page 960).

    Units

    If the option has been selected, the set output unit with the attribute value
    is displayed in the Format column.
    This option is only available to times and lengths.

    Alignment

    The alignment of the attribute value in the column of the output list
    For numerical attributes, we recommend a right alignment, for alphanumerical attributes a left alignment.

    Format

    For some attributes you can specify the format in which the attribute
    values shall be output by using the drop-down list. The format also affects
    the data entry (see "Editing attribute values in a list" on page 2321):
    Scientifical: Some numerical attributes can be output in scientific
    notation. The numbers are output in exponential notation which
    leads to an abbreviated display of large numerical values. Example:
    0.000234 would be 2.34e-004 in scientific notation.
    Times can be displayed in seconds (s), minutes (m) or hours (h) or in
    the formats hh:mm and hh:mm:ss.
    Lengths can be displayed in different units (e.g. kilometers or
    meters).
    In the basic settings, you can adjust whether the data shall be output
    in metrical or in imperial units (see "Specifying standard units for
    length and speed" on page 865).
    For example, by default, volumes are displayed in their respective
    unit (e.g. vehicles, PCU, passengers). They can, however, also be
    displayed as percentages of the total volume or in scientific notation.
    Use the arrow to move one or several attribute up in the list. To do this
    mark the attribute and click the arrow.
    Use the arrow to move one or several attribute down in the list. To do this
    mark the attribute and click the arrow.

    1. Confirm with OK.


    Specifying analysis time intervals for attributes with a time reference
    In case of attributes that refer to a specific time period, for example the volume, you first need
    to specify the analysis time slot for which you want to display the attribute value, and then the
    attribute. For each selected analysis time slot, an entry will be added. The time slot will be
    added in brackets to the attribute name.

    PTVGROUP

    971

    15.2.5.2 Editing the display properties of attributes


    If required, you can also apply the selected analysis time slot to already selected attributes
    (see Fundamentals: Chpt. 3.2 , page 94).
    1. Make sure that the Attribute selection (<Network object type>) window is open.
    2. Click the button next to the Preset the analysis time slots label.
    Note: The button is labeled with the currently selected analysis time slots. If no analysis time slot has been selected, the button is labeled with ....
    The Preset the analysis time slots window opens.

    3. In the drop-down list, select one or several entries. To select multiple entries press and hold
    down the CTRL key and click the desired entries.
    Element

    Description

    Select none

    Use this button to cancel an earlier selection of entries.

    Select all

    Use this button to select all entries at the same time.

    Notes: If you preselect one or several time slots, attributes with a time reference are
    displayed without subentries in the navigator. In this case, if you add an attribute with
    a time reference to the list in the upper section, the attribute is added for each applicable analysis time slot.
    If you do not select an analysis time slot, attributes with a time reference are displayed
    with subentries in the navigator. The subentries correspond to the existing analysis
    time slots. In this case, in the navigator you can select the attribute directly with the
    desired analysis time slot.
    4. Confirm with OK.
    A query opens.

    972

    PTVGROUP

    15.2.6 Managing user-defined attributes


    Element Description
    Yes

    If there is already an attribute with a time reference in the list in the upper section of the window, for this attribute, an entry will be inserted for each selected analysis time slot. Entries with other analysis time slots will be removed.
    If you have not selected an analysis time slot, one entry each will be inserted
    for all existing analysis time slots.

    No

    If, in the list in the upper section of the window, there already is an attribute
    with a time reference, it will not be changed.

    5. Click Yes to confirm.


    The button is labeled with the set analysis time slots. As soon as you add an attribute with a
    time reference, an entry is added for each selected analysis time slot.

    15.2.6

    Managing user-defined attributes


    For network objects and some geometry and signal control objects, you can define your own
    attributes (UDAs) in addition attributes predefined in Visum.
    A user-defined attribute is marked by a black dot.
    Subjects
    Creating a user-defined attribute
    Generating user-defined attributes when reading attributes
    Editing attribute values of user-defined attributes
    Editing a user-defined attribute
    Deleting user-defined attributes

    15.2.6.1

    Creating a user-defined attribute


    1. In the Network menu, select the User-defined attributes entry.
    The User-defined attributes window opens.
    2. Select the object type from the list of Network objects, for which you would like to define a
    user-defined attribute.
    Notes: If you select the All network objects entry in the list, all user-defined attributes
    of all objects will be listed.
    If you select the Network entry, you can specify general settings for the network.
    3. Click the

    Create button.

    The Create user-defined attribute <Network object type> window opens.


    4. Enter the desired data.

    PTVGROUP

    973

    15.2.6.1 Creating a user-defined attribute


    Element

    Description

    Attribute ID Unique attribute name


    Code

    Unique code of the attribute

    Name

    Name of the attribute

    Comment

    Description of the attribute (optional)

    Type

    Use the list to select a data type. Select from the following data types:
    Bool
    For logical statements, that is true or false
    File
    Reference to a file
    Formula
    Enter a formula
    Integer
    Whole number
    Precise duration
    Precise duration, with decimal places, e.g. 35.004s
    Number with decimal places
    Real number with a fixed number of decimal places (see "Selecting a decimal point" on page 873)
    Kilometers/miles
    Long length according to setting (see "Specifying standard units for length
    and speed" on page 865)
    Long text
    String with an unlimited number of characters in case of an undefined Max.
    length
    Alternatively, under Max. length, you can enter a value > 255.
    Meters/Feet
    Short length according to setting (see "Specifying standard units for length
    and speed" on page 865)
    Text
    String with a maximum string length of 255
    Time
    Duration in seconds, display format 12h35min12s
    Time
    Time in format hh:mm:ss (12:23:12) or hh:mm (12:23)

    Type-dependent attributes
    Depending on the selected Type , you can also specify the following attribute values and options:

    974

    PTVGROUP

    15.2.6.1 Creating a user-defined attribute

    Element

    Description

    Default value

    If the option has been selected, you can enter a default value for the
    default setting.
    Note
    Via the Blank option, you can allocate to numerical attributes alternatively the default value Blank. For arithmetic operations the characteristic blank is interpreted as 0.

    Minimum

    If the option has been selected, you can enter a minimum permitted
    value.
    Note
    If you do not want to define a minimum permitted value, select the
    Unlimited option.

    Maximum

    If the option has been selected, you can enter a maximum permitted
    value.
    Note
    If you do not want to define a maximum permitted value, select the
    Unlimited option.

    Decimal places

    Decimal places

    Max. length

    Maximum number of characters

    Options for
    split / connect

    For some types, the following option is provided for the calculation of
    attribute values when splitting or connecting links.
    Values are copied (standard setting)
    If the option has been selected, an identical attribute will be created for both new links when splitting a link (see "Splitting a link"
    on page 1119).
    If the option has been selected, the attribute will be created for
    just one of the links when connecting the links (see "Deleting a
    node" on page 1083).
    Values are scaled
    If the option has been selected, the attribute will be distributed to
    each new link in proportion to the length of the two new links.
    The total of both values thus equals the original value.
    If this option has been selected, the attribute is summed up when
    connecting the links.
    Note
    You can verify the Values are copied/scaled setting in the Scalable
    column of the network file. 0 means that the values are copied, 1
    means that the values are scaled.

    PTVGROUP

    975

    15.2.6.1 Creating a user-defined attribute


    Element

    Description

    Cross-section
    logics

    For attributes of network object types that have a direction (like links
    or connectors), you need to specify how the cross-section values
    shall be calculated. The cross-section value is determined on the
    basis of the values of the two directions. You have the following options:
    Sum
    Mean
    Minimum
    Maximum
    Depending on the selected option, the total, mean, minimum, or maximum of the two directions will be used as cross-section value.
    Ignore blocked directions
    If this option has been selected, blocked directions are ignored in the
    calculation.
    Attribute whose values enter the formula
    Use the button to select direct or indirect attributes (and subattributes,
    if provided) of the network object type.
    The selection is done in a separate window (see "The window used
    for the selection of one attribute" on page 963).
    Click this button to select a binary operator for the formula. The selection available depends on the operand type, of which the values are
    used in the formula.
    Click the button to select a function for the formula.
    Abs(x) absolute value of x
    Floor(x) rounds x to the next smaller integer, the text Floor() is
    inserted at the cursor position.
    Max(x,y) forms the maximum of x and y
    Min(x,y) forms the minimum of x and y
    Power(x,y) corresponds to xy, the text Pow(,) is inserted at the
    cursor position
    Percent(x,y) corresponds to 100*x/y, the text Percent(,) is
    inserted at the cursor position
    Truncate (x,p) rounds x to p decimal places, the text Truncate
    (,) is inserted at the cursor position
    Click this button to insert a bracket term without content into the formula.

    1. Confirm with OK.


    The user-defined attribute is inserted.

    976

    PTVGROUP

    15.2.6.2 Generating user-defined attributes when reading attributes


    Tip: Alternatively, you can add user-defined attributes as follows:
    By right-clicking a network object type in the Network window and selecting Create
    user-defined attribute in the context menu
    Directly in the attribute selection list (see "The window used for the selection of one
    attribute" on page 963)
    15.2.6.2

    Generating user-defined attributes when reading attributes


    You can create user-defined attributes as target attributes when reading an attribute file. When
    reading in attributes, the generated attributes store the values of the source attributes.
    1. Read an attribute file (see "Reading an attribute file" on page 2646).
    The Read attributes window opens.

    2. Click the Create button.


    The Type selection window opens.

    Note: If you want to create just one user-defined attribute, in the desired row, click the
    New button and create a user-defined attribute (see "Creating a user-defined attribute" on page 973).
    3. In the drop-down list, select a data type (see "Creating a user-defined attribute" on page
    973).
    4. Confirm with OK.

    PTVGROUP

    977

    15.2.6.3 Editing attribute values of user-defined attributes


    For all source attributes that are not allocated, user-defined attributes of the selected type will
    be generated.
    15.2.6.3

    Editing attribute values of user-defined attributes


    For a lot of network object types, a window is displayed when creating or editing a network
    object in which you can specify attribute values. For these network object types, you can
    modify attribute values as follows:
    Notes: User-defined attributes of the type network are found under the Network> Network settings menu in the User-defined attributes tab.
    The attribute values of user-defined attributes of the type node are edited in the junction
    editor (see "Editing a node in the Junction editor" on page 1441). Here you can also edit
    the user-defined attribute values of turns, lanes, etc.
    1. Create a user-defined attribute for the desired network object type (see "Creating a userdefined attribute" on page 973).
    2. Insert a network object of the network object type or edit a corresponding network object.
    The Create <Network object type> window or the Edit <Network object type> window
    opens.
    3. Select the User-defined attributes tab.
    Notes: The tab is only displayed if a user-defined attribute exists for the network
    object type. It contains a list of all user-defined attributes of the network object type.
    4. If required, use the buttons to select the attributes to be displayed.
    Element

    Description

    Show all

    Click the button to display all user-defined attributes.

    Rows

    Use the button to select the user-defined attributes in a separate window


    that you want to display (see "The window used for the selection of multiple attributes" on page 968).

    5. In the Value column of the row of the desired attribute, enter the desired value.
    Attribute of type file: Via the button, select the desired file.
    Attribute of type Bool: Tick the checkbox.
    Other types: Click the cell and enter a number or a text.
    Note: In case of direction-based network object types (links, connectors) an attribute
    value is highlighted in yellow, if the attribute values of the two directions differ.
    6. Enter the desired value.
    7. Confirm with OK.
    The attribute value is changed.
    978

    PTVGROUP

    15.2.6.4 Editing a user-defined attribute


    Notes: You can also edit the attribute values of user-defined attributes like other attribute
    values (see "Editing attribute values of network objects" on page 983 and "Editing attribute values in a list" on page 2321).
    Exception: You cannot edit the attribute values of user-defined formula attributes. Therefore, the user-defined formula attributes in the Edit <Network object type> window
    User-defined attributes tab und the Multi-edit <Network object type> windows are not
    displayed.
    15.2.6.4

    Editing a user-defined attribute


    1. In the Network menu, select the User-defined attributes entry.
    The User-defined attributes window opens.
    2. In the Network objects list, select the object type, for which the user-defined attribute has
    been created that you want to edit.
    3. In the list, click the user-defined attribute that you want to edit.
    4. Click the

    Edit button.

    The Edit user-defined attribute <Network object type> window opens.


    5. Edit the desired attribute (see "Creating a user-defined attribute" on page 973).
    6. Confirm with OK.
    The values are modified.
    15.2.6.5

    Deleting user-defined attributes


    1. In the Network menu, select the User-defined attributes entry.
    The User-defined attributes window opens.
    2. In the Network objects list, select the object type, for which the user-defined attribute has
    been created that you want to delete.
    3. In the list, click the user-defined attribute that you want to delete.
    Note: If you want to delete multiple attributes at the same time, hold down the C TRL
    key and click the attributes.
    4. Click the

    Delete button.

    The user-defined attribute is deleted.

    15.2.7

    Managing time-varying attributes


    With the aid of time-varying attributes, you can override the regular value of an attribute with a
    deviating value for a defined amount of time. This way you can, for example, model the impact
    of tidal flow lane allocation or transient road works.

    PTVGROUP

    979

    15.2.7.1 Creating time-varying attributes


    You can allocate time-varying attributes to the following network object types:
    Node
    Main node
    Links
    Turn
    Main turns
    To set a time-varying value, you first need to specify which attribute shall be time-varying.
    Then you specify the duration of the deviating value and enter the value that shall apply during
    the specified time.
    Subjects
    Creating time-varying attributes
    Entering and editing time-varying data for time-varying attributes
    Deleting time-varying attribute data
    15.2.7.1

    Creating time-varying attributes


    1. In the Network menu, select the Time-varying attributes entry.
    The Time-varying attributes window opens.
    2. Click the

    Create button.

    The Create time-varying attribute window opens.

    3. In the Network object list, select the network object type for which you want to create a
    time-varying attribute.
    4. In the Attribute list, select the attribute for which you want to specify time-varying values.
    5. Confirm with OK.
    The attribute is created. In the next step, you enter the duration of the deviating value and
    enter the value that shall apply during the specified time.
    15.2.7.2

    Entering and editing time-varying data for time-varying attributes


    Once you have specified that an attribute is time-varying, you need to enter the data for the
    time variation. Here you specify the time during which the variation applies and the value
    which is used for the attribute during the specified time.
    Time-varying attributes of links are edited in the Network editor window. Time-varying attributes of nodes, main nodes, turns and main turns are edited in the junction editor. Here, click
    the
    Edit time-varying attributes icon. Independent of the type of access the Edit timevarying attributes window opens. Below the process is described using the example of links.

    980

    PTVGROUP

    15.2.7.2 Entering and editing time-varying data for time-varying attributes

    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click a link for which you want to specify time-varying data.
    The Edit link window opens.
    4. Select the Time-varying attributes tab.
    Notes: The tab lists all attributes that you have inserted as time-varying attributes (see
    "Creating time-varying attributes" on page 980).
    For links and turns, you need to specify the attributes data for each direction.
    5. Click the Edit button.
    The Edit time-varying attributes window opens.

    6. Click the Create button.


    The Create time-varying attribute at <Network object> window opens.
    7. In the window, you can make the following changes:
    Element

    Description

    Attribute

    Name of the time-varying attribute

    Periodical

    If the option has been selected, the allocated deviant value of the attribute
    will be effective every day of the selected Valid day within the time range specified.

    Valid day

    Use the list to select a valid day.


    The selection depends on the calendar settings (see "Specifying a calendar
    and valid days" on page 1511).

    From
    To

    Specify a starting time and an ending time of the deviant attribute value.

    PTVGROUP

    981

    15.2.7.3 Deleting time-varying attribute data


    Element

    Description
    As From - To time slot, you can enter a time interval between two points in
    time (also stretching over several days if a calendar is in use). When using
    the Periodical option, you can enter the combination of a valid day and a
    time interval (within a day).

    Value

    Specify an attribute value.


    This deviating attribute value applies at the specified time.

    8. Confirm with OK.


    The data for the time-varying attribute are inserted.
    15.2.7.3

    Deleting time-varying attribute data


    You can delete time-varying attribute data in two ways:
    Deleting the time variation of an attribute
    1. In the Network menu, select the Time-varying attributes entry.
    The Time-varying attributes window opens.
    2. In the list, click the attribute whose time-varying data you want to delete.
    3. Click the

    Delete button.

    The time variation for the attribute is deleted at the respective network object. All time variation
    data of the attribute are deleted.
    Deleting time variation data of an attribute
    1. In the Network window, click the

    Edit mode icon.

    2. Click the button of the desired network object type.


    3. In the network, double-click the desired network object.
    The Edit <Network object> window opens.
    4. Select the Time-varying attributes tab.
    The tab lists all time-varying attributes of the network object type.
    5. Click the Edit button.
    The Edit time-varying attributes window opens.
    6. In the list, mark the attribute with the time variation data that you want to delete.
    7. Click the Delete button.
    The time variation data are deleted.

    982

    PTVGROUP

    15.3 Editing attribute values of network objects

    15.3

    Editing attribute values of network objects


    You can edit the attribute values of several marked, all active or for all network objects. Some
    attribute values cannot be edited. You cannot edit the IDs of the network objects (e.g. Number)
    or calculation results (e.g. Volume).
    Subjects
    The attribute value zero
    Assigning a constant value to an attribute or adding attribute values
    Editing attribute values of set attributes
    Multiplying an attribute value with a factor
    Allocating an attribute value to a different attribute
    Calculating attribute values from the values of other attributes
    Rounding attribute values
    Editing attribute values during a procedure sequence
    Allocating attribute values by intersecting a source attribute
    Exchanging attribute values via the clipboard
    Modifying attribute values in the Quick view
    A detailed description on how to edit the attribute values of individual network objects is given
    with the respective network object type, for example links (see "Editing the attribute values of
    links" on page 1113).
    Procedure for several marked network objects
    1. Mark the network objects whose attribute values you want to edit (see "Marking network
    objects in the network" on page 1004).
    2. Press the ENTER key.
    The Multi-edit <Network object type>: <Number> objects window opens.
    3. Edit the values of the desired attributes.
    Procedure for all or all active network objects
    1. If required, set the network objects active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected network objects are active.
    2. In the Network window, click the

    Edit mode icon.

    3. With the right mouse button, click the button of the desired network object type.
    A shortcut menu opens.
    4. Select the Multi-edit entry.
    The Multi-edit <Network object type> window opens.

    PTVGROUP

    983

    15.3.1 The attribute value zero


    5. Select whether you want to edit the attribute values of all network objects or just the active
    ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active network objects are
    taken into account.
    If the option has not been selected, all network objects are
    taken into account.

    6. Select the Formula tab.


    7. Edit the values of the desired attributes.

    15.3.1

    The attribute value zero


    For attributes calculated by assignment or line costing, the Visum display mode distinguishes
    between the following types of the attribute value zero:
    Attributes which are undefined, have not been calculated and thus have the attribute
    value 0: These undefined output attributes are displayed as empty strings.
    Attributes which are defined, have been calculated in the network version and have the
    attribute value 0 as a result: These defined output attributes (calculated attribute value 0)
    are output as digit 0.
    Note: In internal calculations (for example in filters), attributes not yet calculated are still
    regarded as zeros. When setting a filter, you thus always have to enter the digit 0 as
    upper and lower limit of the value range.

    15.3.2

    Assigning a constant value to an attribute or adding attribute values


    1. Make sure that the Multi-edit <Network object type> window is open and that the Formula
    tab is selected (see "Editing attribute values of network objects" on page 983).
    All input attributes of the selected network object type can be selected.
    2. Select the attribute to which you want to allocate a constant value and a subattribute, if
    available.
    3. Click the Constant button.
    The Attribute: Constant value window opens. Depending on the selected network object
    type, you can either select or enter a value.
    4. Enter the desired value.

    984

    PTVGROUP

    15.3.3 Editing attribute values of set attributes


    Note: When entering numerical attribute values with a length or time reference, you
    need to consider the units:
    If you enter just the value, it is saved in standard format.
    You can enter a value with unit. In this case, Visum converts the value so that it is
    displayed in the specified format. Example: The format minutes is specified for an
    attribute. You enter 2h. The entry field then contains the value 120.
    5. Make the desired changes.
    Element

    Description

    Add value

    If the option has been selected, the entered value is added to the
    existing attribute value.
    If this option has not been selected, the current attribute value is
    replaced by the input value.

    6. Confirm with OK.


    The attribute value is changed.
    Tip: Alternatively, you can assign a constant value to an attribute during the procedure
    sequence (see "Editing attribute values during a procedure sequence" on page 990).

    15.3.3

    Editing attribute values of set attributes


    This functionality affects all attributes which contain quantities or sets of entries. You can allocate or remove one or multiple entries. In the case of link attribute TSys set, you can, for example, open or block the transport system Bus for all or all active links.
    1. Make sure that the Multi-edit <Network object type> window is open and that the Formula
    tab is selected (see "Editing attribute values of network objects" on page 983).
    All input attributes of the selected network object type can be selected.
    2. Select whether you want to edit the attribute values of all network objects or just the active
    ones.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active network objects are taken
    into account.

    3. Select the attribute that you want to edit.


    Note: You can allocate a constant value to the entry sets of the following attributes.
    TSys set of the network object type Links
    Is depot for vehicle combinations of the network object type Stop points
    Fare system set of the network object type Lines
    Vehicle combination set of the network object type Vehicle journey section
    PTVGROUP

    985

    15.3.3 Editing attribute values of set attributes


    4. Click the Constant button.
    The Attribute: Constant value window opens.
    5. Make the desired settings.
    Note: Depending on the network object you are editing different buttons are available.

    986

    Element

    Description

    Open

    Use this button to select a transport system which you want to open for all
    or all active links of the network. The entry with the transport system is
    moved to the list Actions to be executed.
    Note
    This button is only provided for the attribute TSys set of the network
    object type Link.

    Close

    Use this button to select a transport system which you want to block for all
    or all active links of the network. The entry with the transport system is
    moved to the list Actions to be executed.
    Note
    This button is only provided for the attribute TSys set of the network
    object type Link.

    Open all

    This button opens all transport systems for all or all active links of the network. The entries with the transport system are moved to the Actions to
    be executed list.
    Note
    This button is only provided for the TSys set attribute of the Link network
    object type.

    Close all

    This button closes all transport systems for all or all active links of the network. The entries with the transport system are moved to the Actions to
    be executed list.
    Note
    This button is only provided for the TSys set attribute of the Link network
    object type.

    Delete all
    in list

    Via this button, you can delete the Actions to be executed list. You can
    delete individual rows via the X at the end of the row.
    Note
    This button is only provided for the TSys set attribute of the Link network
    object type.

    Allocate

    Use this button to pick an attribute value that you want to allocate to all or
    all active network objects of the selected type. The entry with the attribute
    value is moved to the list Actions to be executed. You can, for example,

    PTVGROUP

    15.3.4 Multiplying an attribute value with a factor


    Element

    Description
    allocate the value Bus to the stop point attribute Is depot for vehicle combinations.

    Delete

    Use this button to pick an attribute value that you want to delete from all or
    all active network objects of the selected type. The entry with the attribute
    value is moved to the list Actions to be executed. You can, for example,
    delete the value Train from the stop point attribute Is depot for vehicle
    combinations.

    The selected actions are displayed in the list Actions to be executed.


    Note: If you want to remove an action from the list Actions to be executed, click the X
    next to the action.
    6. Confirm with OK.
    The attribute values are edited.

    15.3.4

    Multiplying an attribute value with a factor


    1. Make sure that the Multi-edit <Network object type> window is open and that the Formula
    tab is selected (see "Editing attribute values of network objects" on page 983).
    All input attributes of the selected network object type can be selected.
    2. Select the attribute that you want to multiply with a factor, and a subattribute, if available.
    3. Click the Factor button.
    Note: This functionality is only available to numerical attributes.
    The Multiply attribute * factor window opens.
    4. Enter the desired factor in the input field.
    5. Make the desired settings.
    Element

    Description

    Add value

    If the option has been selected, the calculated value is added to the
    existing attribute value.
    If the option has not been selected, the existing attribute value is
    replaced by the calculated value.

    Cut off

    PTVGROUP

    If this option has been selected, all decimal places of the calculated
    value are dropped.
    Note
    The option is only available for attributes of the type integer.

    987

    15.3.5 Allocating an attribute value to a different attribute


    Element

    Description

    Round

    If this option has been selected, the calculated value is rounded. Decimal places up to and including four are rounded off, from five they are
    rounded up. This applies to negative numbers, too.
    Note
    The option is only available for attributes of the type integer.

    6. Confirm with OK.


    The attribute value is changed.
    7. Click the Close button.
    Tip: Alternatively you can multiply an attribute value by a factor during the procedure
    sequence (see "Editing attribute values during a procedure sequence" on page 990).

    15.3.5

    Allocating an attribute value to a different attribute


    1. Make sure that the Multi-edit <Network object type> window is open and that the Formula
    tab is selected (see "Editing attribute values of network objects" on page 983).
    All input attributes of the selected network object type can be selected.
    2. Select the attribute to which you want to allocate the value of a different attribute (target attribute), and a subattribute, if available.
    3. Click the Attribute button.
    The Use the following attribute data for the selected attribute window opens.
    4. Click the <Attribute> button.
    The Attributes (<Network object type>) window opens.
    5. Select the attribute whose value you want to allocate to the attribute (source attribute), and
    a subattribute, if available (see "The window used for the selection of one attribute" on page
    963).
    6. Confirm with OK.
    The attribute is selected.
    7. Enter a factor in the input field, if required.
    8. Make the desired settings.

    988

    PTVGROUP

    15.3.6 Calculating attribute values from the values of other attributes


    Element

    Description

    Add value

    If the option has been selected, the calculated value is added to the
    existing attribute value.
    If the option has not been selected, the existing attribute value is
    replaced by the calculated value.
    Note
    This option is only available for numerical target attributes.

    Cut off

    If this option has been selected, all decimal places of the calculated
    value are dropped.
    Note
    The option is only available in case of numerical target attributes of
    the type integer.

    Round

    If this option has been selected, the calculated value is rounded. Decimal places up to and including four are rounded off, from five they are
    rounded up. This applies to negative numbers, too.
    Note
    The option is only available in case of numerical target attributes of
    the type integer.

    9. Confirm with OK.


    The attribute value is changed.
    Note: If you want to edit other attribute values, repeat step 2 to9.
    10. Click the Close button.
    Tip: Alternatively, you can allocate the value of a different attribute to an attribute during
    the procedure sequence (see "Editing attribute values during a procedure sequence" on
    page 990).

    15.3.6

    Calculating attribute values from the values of other attributes


    1. Make sure that the Multi-edit <Network object type> window is open and that the Formula
    tab is selected (see "Editing attribute values of network objects" on page 983).
    All input attributes of the selected network object type can be selected.
    2. Select the attribute whose value you want to calculated based on the values of other attributes (target attribute), and a subattribute, if available.
    3. Click the Formula button.
    Note: This functionality is only available to numerical attributes.

    PTVGROUP

    989

    15.3.7 Rounding attribute values


    The window <Network object type> window: Create attribute value with formula result
    <Attribute name> opens.
    4. Into the text box, enter the desired formula for calculation, or click the buttons next to the text
    box to create a formula (see "Creating a user-defined attribute" on page 973)
    5. Confirm with OK.
    The attribute value is changed.
    6. Click the Close button.
    Tip: Alternatively, you can calculate an attribute value based on the values of other attributes during the procedure sequence (see "Editing attribute values during a procedure
    sequence" on page 990).

    15.3.7

    Rounding attribute values


    1. Make sure that the Multi-edit <Network object type> window is open and that the Formula
    tab is selected (see "Editing attribute values of network objects" on page 983).
    All input attributes of the selected network object type can be selected.
    2. Select the attribute whose values you want to round, and a subattribute, if available.
    3. Click the Round button.
    Note: This functionality is only available to numerical attributes.
    The Round window opens.
    4. Enter the rounding factor in the input field.
    5. Confirm with OK.
    The attribute value is changed.
    Note: If you want to edit other attribute values, repeat steps 2 to5.
    6. Click the Close button.
    Tip: Alternatively, you can round off an attribute value during the procedure sequence
    (see "Editing attribute values during a procedure sequence" on page 990).

    15.3.8

    Editing attribute values during a procedure sequence


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.

    990

    PTVGROUP

    15.3.8 Editing attribute values during a procedure sequence


    2. In the desired position of the procedure sequence, insert the Edit attribute procedure of the
    Miscellaneous category (see "Setting up and starting the procedure sequence" on page
    1847).
    3. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The Parameters: Edit attribute window opens.
    4. Enter the desired data.
    Element

    Description

    Network object Use the drop-down list to select the network object type whose attritype
    bute values you want to edit.
    Note
    Moreover, you can select Network in order to edit user-defined attributes of the network, for example.
    Only active
    ones

    If the option has been selected, only active objects of the selected target network object type will be taken into account.

    Target attribute

    Attribute whose value you want to edit.


    Use the button to select an attribute (and a subattribute, if available).
    The selection is done in a separate window (see "The window used
    for the selection of one attribute" on page 963).
    Note
    You can edit both the values of numerical attributes and the values of
    alphanumerical attributes.

    5. Into the text box, enter the desired formula for calculation, or click the buttons next to the text
    box to create a formula.
    Note: In Visum, you create uniform formulas for attributes and matrices. Depending on
    the context, the program provides different elements for creating a formula. For attributes,
    the functionality is described via user-defined attributes (see "Creating a user-defined
    attribute" on page 973).
    6. Confirm with OK.
    7. Execute the procedure (see "Setting up and starting the procedure sequence" on page
    1847).
    The attribute values are edited.
    Note: For attributes, you can also calculate mean values according to the Method of Successive Averages (MSA) (see Fundamentals: Chpt. 4.2.6.3 , page 198).

    PTVGROUP

    991

    15.3.8 Editing attribute values during a procedure sequence


    Example 1

    These settings yield all active links in the network with the name Pedestrian zone.
    Example 2

    These settings yield the AddValue 1 of all nodes in the network according to the following formula:
    AddVal1 = |AddVal2 + AddVal3| + AddVal1 (1.5 Number of Connectors(C)) + Main node
    number + 4
    Example 3

    These settings yield the value of the alphanumerical, user-defined target attribute Plot label
    (type text) of all nodes in the network from the node attributes Number, Name and TypeNo.

    992

    PTVGROUP

    15.3.9 Allocating attribute values by intersecting a source attribute

    Notes: If you combine several numerical values, we recommend the use of a separator.
    For this you can create a user-defined attribute (UDA) of type text with a non-numerical
    character as default value (see "Managing user-defined attributes" on page 973) and
    insert this UDA as additional attribute each between two numerical attributes in order to
    ensure the readability of the consecutive attribute values.
    The separator should neither be a full stop, a comma (decimal separator), nor a semicolon (readability of network data).

    15.3.9

    Allocating attribute values by intersecting a source attribute


    You can intersect the attribute values of any desired network objects that overlap spatially (see
    "Intersecting objects" on page 2217).

    15.3.10 Exchanging attribute values via the clipboard


    You can exchange attribute values via the clipboard as follows:
    Copying attribute values to the clipboard
    Pasting attribute values from the clipboard
    15.3.10.1 Copying attribute values to the clipboard
    You can copy the values of selected or all input attributes (except IDs) of a network object to
    the clipboard.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the button of the desired network object type.


    3. Mark the desired network object in the network (see "Marking network objects in the network" on page 1004).
    4. In the Quick view window, click the

    Attribute selection icon.

    The Select attributes (<Network object type>) window opens.


    5. Select the attributes whose values you want to copy to the clipboard (see "Quick view window" on page 810).

    PTVGROUP

    993

    15.3.10.2 Pasting attribute values from the clipboard


    6. Confirm with OK.
    The selected attributes are displayed in the Quick View.
    7. In the Quick view window, click the

    Copy attributes window.

    The values of the input attributes displayed in the Quick view window are copied to the clipboard (except IDs).
    Tip: You can also copy the attribute values to the clipboard via the context menu> Copy
    attributes entry, or by pressing the C TRL and C keys.
    15.3.10.2 Pasting attribute values from the clipboard
    You can allocate the attribute values from the clipboard to any number of objects of the same
    or of a different network object type.
    The values of input attributes (except IDs) are allocated, which are both defined for the source
    and the target network object type and lie within the value range of the target network type.
    Notes: Some attributes are not provided for all network object types (AddValue-TSys is,
    for example, only provided for links).
    Some attributes have a different value range depending on the network object type (for
    zones, the value range of the attribute Type is, for example, 0-9, and for links 0-99).
    1. Make sure that the clipboard contains attribute values (see "Copying attribute values to the
    clipboard" on page 993).
    2. In the Network window, click the

    Edit mode icon.

    3. Click the button of the desired network object type.


    4. In the network, mark the network objects whose attribute values you want to allocate (see
    "Marking network objects in the network" on page 1004).
    5. In the Quick view window, click the

    Paste attributes icon.

    The values of the input attributes contained in the clipboard (except IDs) are copied.
    Note: If you have edited the attribute selection of the network object type or switched to a
    different network object type before pasting the attributes from the clipboard, only the
    values for the input attributes displayed in the Quick view window will be copied.
    Tip: You can also paste the attribute values from the clipboard via the context menu>
    Paste attributes entry, or by pressing the C TRL and C keys.

    994

    PTVGROUP

    15.3.11 Modifying attribute values in the Quick view

    15.3.11 Modifying attribute values in the Quick view


    You can only edit attribute values that are highlighted in white. The following options are provided:
    Editing attribute values in the Quick view
    Editing attribute values in the Quick view with arithmetic operations
    15.3.11.1 Editing attribute values in the Quick view
    1. Make sure that the network objects are selected in the network whose attribute values you
    want to edit.
    2. In the Quick view, mark one or more cells (see "Quick view window" on page 810).
    Notes: If you mark a link, the Quick view shows the attribute values of the marked
    direction only. You thus only edit the attribute values of one link direction.
    If several network objects are marked with different attribute values, an asterisk * is
    displayed instead of the attribute value.
    3. Enter the desired value in a marked cell and press ENTER.
    Note: When entering numerical attribute values with a length or time reference, you
    need to consider the units:
    If you enter just one digit, the value is interpreted in the format in which the attribute is displayed. Example: If an attribute is displayed in the minutes format, the
    value 5 is read as 5 minutes.
    You can change the format in the attribute selection window (see "The window
    used for the selection of multiple attributes" on page 968).
    You can enter a number with a unit. In this case, Visum converts the value in such
    a way that it is displayed accordingly in the selected format. You may enter
    lengths in metric (m, km) or imperial (ft, mi) units.
    Example: If an attribute is displayed in the minutes format, you can enter 2h. After
    the confirmation, the value 120 will be displayed.
    The new attribute value is displayed in all marked cells.
    15.3.11.2 Editing attribute values in the Quick view with arithmetic operations
    1. Make sure that the network objects are selected in the network whose attribute values you
    want to edit.
    2. In the Quick view, mark one or more numerical cells (see "Quick view window" on page
    810).
    3. In a marked cell, enter one of the below arithmetic operations:

    PTVGROUP

    995

    15.4 The operating modes of the network model


    Operation

    Syntax

    Addition

    =+2

    Subtraction

    =-2

    Multiplication

    =*2

    Division

    =/2

    Raise to power

    =^2

    Form the minimum

    =min2

    Form the maximum

    =max2

    Use an exponential function

    =exp

    Take logarithm

    =log

    Form reciprocal value

    =1/

    The operation is run for all marked cells with a numerical value. The result is entered as attribute value.
    Note: If you have selected an alphanumerical cell, the text of the arithmetic operation is
    entered in the cell.

    15.4

    The operating modes of the network model


    Visum provides several possibilities to model a network. You can create, edit, and delete network objects or set them active or passive. The Network window provides three different operating modes.

    Insert mode
    Edit mode
    Spatial selection mode
    Note: If you cannot execute an instruction step, check that you have selected the right
    operating mode.

    15.4.1

    Activating the Insert mode


    In the Insert mode, you can create network objects.
    In the Network window, click the

    Insert mode icon.

    Tip: Alternatively, you can switch to the Insert mode by pressing the INS key or by
    selecting the Insert mode entry in the Edit menu.
    A detailed description on how to insert network objects is given with the respective network
    object type, for example, links (see "Managing links" on page 1099).

    996

    PTVGROUP

    15.4.2 Activating the Edit mode

    15.4.2

    Activating the Edit mode


    In the Edit mode, you can search for(see "Marking network objects in the network" on page
    1004), mark, edit, or delete network objects.
    1. In the Network window, click the

    Edit mode icon.

    Tip: Alternatively, you can switch to the Edit mode by selecting the Edit mode entry in
    the Edit menu.
    2. Click the button of the network object type that you want to edit.
    The Edit mode is activated. In the network, you can select a network object that you want to
    edit.
    A detailed description on how to search for, mark, edit, and delete network objects is given
    with the respective network object type, for example links (see "Managing links" on page
    1099).

    15.4.3

    Activating the Spatial selection mode


    In the Spatial selection mode, you set network objects active or passive. This way, you can
    limit the number of network objects that you want to edit.
    Note: Network objects are active, if they are both included in the spatial selection and
    comply with the current filter settings (see "Using filters to set network objects active or
    passive" on page 1008).
    In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar opens and, in the Network window, the Switch on/off spatial
    selection option is displayed for each network object type.

    Tip: Alternatively, you can switch to the Spatial selection mode by selecting the Spatial
    selection mode entry in the Edit menu.
    The Spatial selection toolbar provides the following icons:

    PTVGROUP

    997

    15.4.3 Activating the Spatial selection mode


    Icon

    Name

    Description

    Set spatial selection to


    the exclusive state

    Sets specific network objects active (see "Setting network objects active/passive via the spatial selection"
    on page 1033)
    Any former active/passive states of network objects
    are discarded.

    Add objects to spatial


    selection

    Sets network objects active. The network objects are


    added to the set of already active network objects.
    Already active network objects stay active (see
    "Extending and reducing the spatial selection of network objects" on page 1038)

    Exclude objects from


    spatial selection

    Sets network objects passive. The network objects


    are removed from the set of already active network
    objects. Already passive network objects stay passive (see "Extending and reducing the spatial selection of network objects" on page 1038)

    Note
    One of the three modes above is always selected.
    Mark objects in territory
    for spatial selection

    Sets the network objects active that lie within territory


    polygons by selection of territories (see "Setting network objects active within territories" on page 1037)

    Include all objects into


    the spatial selection

    Setting all network objects active (see "Setting all network objects active" on page 1035)

    Invert spatial selection

    Sets all active network objects passive, and all passive network objects active (see "Inverting the active/passive state of network objects" on page 1038)

    Remove all objects from


    the spatial selection

    Setting all network objects passive (see "Setting all


    network objects passive" on page 1035)

    For selection operations, In the Network window, select all network object
    check all types
    types for the Spatial selection mode
    For selection operations, In the Network window, exclude all network object
    uncheck all types
    types from the Spatial selection mode
    Read spatial selection
    from file

    Read in a saved spatial selection (see "Reading a


    spatial selection of network objects" on page 1039)

    Save spatial selection to Save the current spatial selection (see "Saving a spafile
    tial selection of network objects" on page 1039)
    How to set network objects active or passive via a spatial selection is described in a separate paragraph (see "Setting network objects active/passive via the spatial selection" on
    page 1033).

    998

    PTVGROUP

    15.5 Finding network objects in the network

    15.5

    Finding network objects in the network


    In a search window, you can search for network objects with a specific attribute value. All attributes of the network object type are available. This function is provided for nearly all network
    object types.
    1. In the Network window, click the button of the desired network object type.
    2. On the toolbar of the Network editor window, click the

    Find a network object icon.

    The Find a network object window opens and in the Network object field the desired network object type is already preset.
    Search called in Network editor window

    Search called in Lists (links) window

    Tip: Alternatively you can call the Find a network object window with the F3 key or in
    the Edit menu, select the Find entry
    Note: If you call the search for network objects in another window than the Network
    editor window, the functionality is limited. The window has a name referring to the network object type searched for: Find <Network object type>.
    The following operations are not possible then:
    Selecting another object than the pre-selected one
    Marking all entries
    Synchronization with other windows
    Editing the attributes directly from the list of results
    3. If necessary, click the

    PTVGROUP

    symbol to display more details concerning the search.

    999

    15.5 Finding network objects in the network


    4. Make the desired changes.
    Element

    Description

    Search for

    Input field for the string you want to find. The search starts as
    soon as you enter something into the field. It takes place in the
    background and reacts immediately to modifications of the string.
    symbol indicates that the search process is running. If
    The
    you click the symbol, the search process will be stopped. The
    cross then turns gray. The input in the search field and the list of
    results remain unchanged. Via the small triangle at the end of the
    row you can open the last queries and select again.
    Notes
    This is not a case-sensitive setting, blanks may be used.
    You can search for all attribute values.
    You can also indicate time or length units if they are part of
    the entered attribute value. This reduces the list.
    If no string is entered in the field, the list displays all network
    objects of the respective network object type.
    If any changes in the network are made during the search process, it is immediately aborted. After the network change you
    have to restart the search manually.

    Network object

    Selection list for the network object or object searched for

    Only search within For some network objects or objects, it is possible to limit the
    search to a smaller subset by selecting only a category or a line.
    The list box is only available for network objects:
    POI: Selection of a POI category
    GIS objects: Selection of a GIS category
    Line route, time profile, vehicle journey: Selection of a line

    1000

    PTVGROUP

    15.5 Finding network objects in the network


    Element

    Description

    Search in attribute In the selection list, all attributes of the list are displayed. You can
    extend the selection list via the
    icon. The selection is saved
    in the registry for the network objects and is available after the restart of Visum.
    Notes
    If you have selected the All attributes of the results list entry, the
    search process considers all attributes that appear in the list. An
    object is displayed as search result if one of the attributes matches the query.
    If you search for in an attribute which is not listed in the results list,
    this attribute is added to the list as the first column.
    Compare

    You can define the search method.


    Part of field content
    The string searched for can be at any position within the entry in
    the list field.
    Note
    If the string in the Search for field contains blanks, the string is
    separated at the blanks and it will be searched for its components. Hereby, the components do not overlap. For example, if
    you search for Haus str, Hausstr and Hausdorfstrasse
    would be search results, but not Haustr.
    Entire field
    String searched for and field content of the list have to match.
    Beginning of field content
    Search value has to be identical with the beginning of the field
    content, the rest can be completed variably. For example, if you
    search for 123, 123405 and 1231 would be search results, but
    not 0123.

    5. Use the toolbar to adjust the settings accordingly.


    Element

    Description
    Switch on/off so that only active objects will be displayed in the list (see
    "Using filters to set network objects active or passive" on page 1008
    and "Setting network objects active/passive via the spatial selection" on
    page 1033).
    Note
    The function is activated if the icon is pressed (red).
    Marks all entries of the list

    PTVGROUP

    1001

    15.5 Finding network objects in the network


    Element

    Description
    Note
    The marking is not automatically extended if due to a change of the
    query, for example, the list becomes longer.
    The search window is not synchronized with other windows.
    Note
    This option is only available if you start the search from the Network
    editor window.
    The objects marked in the list are highlighted in other windows and
    vice versa.
    This option is only available if you start the search from the Network
    editor window.
    The objects marked in the list are highlighted in other windows and
    vice versa. If required, the network section of the network window is shifted in such a way that all marked objects are visible.
    Notes
    This does not affect the scale of the network editor.
    This option is only available if you start the search from the Network
    editor window.
    The objects marked in the list are highlighted in other windows and
    vice versa. Additionally, in the network an auto zoom is carried out for
    the marked objects.
    Note
    This option is only available if you start the search from the Network
    editor window.
    Resets in the list the attributes displayed in the columns to the default
    settings.
    Calls the Attribute selection window. Here, you can select the attributes for display in the columns of the results list (see "The window
    used for the selection of multiple attributes" on page 968).

    1002

    PTVGROUP

    15.5.1 Editing search results


    Element

    Description

    Show selection

    Use this button to close the search window. The selection marked in
    the results list is adopted in the window from which the search was started, for example, from a list window or the Timetable editor.
    Note
    The button is only available if the search has not been started from the
    Network editor window.

    Accept
    Use this button to close the search window. No search result will be
    empty selec- adopted for the window from which the search was started, for examtion/All
    ple, from a list window or the Timetable editor.
    Note
    The button is only available if the search has not been started from the
    Network editor window.
    In the table rows the list contains all network objects of the network object type searched for
    matching the criteria. The attributes of the network objects are listed in columns. The number
    of search results found is indicated at the top left of the list. Passive network objects are displayed in gray.

    15.5.1

    Editing search results


    You can edit the search results in the Find a network object window via the context menu or
    via the Quick view window. Depending on the network object type all available operations can
    be distinguished.
    Editing attributes in the Quick view window
    You can edit the attributes of the network objects directly from the list in the Quick view window. The Find a network object window may remain open.
    1. Make sure that the Find a network object window is open and that the desired search has
    been performed (see "Finding network objects in the network" on page 999).
    2. Make sure that in the toolbar of the Find a network object window, the
    icon has been
    selected. Thus, network objects marked in the list are equally marked in other windows.
    3. In the search results list, mark the network object you want to edit.
    The network object is displayed in the Quick view window.
    4. Edit the desired attributes of the network object (see "Modifying attribute values in the Quick
    view" on page 995).
    The attribute values are edited.
    Editing search results via the context menu
    Via the context menu, you can call various functionalities to edit the search results. Depending
    on the network object type the available functionalities may be different.

    PTVGROUP

    1003

    15.6 Marking network objects in the network


    1. Make sure that the Find a network object window is open and that the desired search has
    been performed (see "Finding network objects in the network" on page 999).
    2. In the results list, mark the network object that you want to edit.
    3. Right-click the marked row.
    A context menu opens.
    4. Select the desired entry.
    Element

    Description

    Autozoom

    The network section is enlarged and the network object is positioned in the middle of the section. Multiple network objects can
    be marked, too. Possible for all network objects.

    Edit

    Opens the window to edit the network object


    Tip
    Alternatively, you can double-click the desired row.

    Edit line route

    Opens the Edit line route window (see "Editing attribute values of
    line routes" on page 1336)

    Timetable editor

    Opens the Timetable editor window (see "Using the Timetable


    editor" on page 1526). Possible for all network objects of the line
    hierarchy. Multiple network objects can be marked, too.

    The desired function is executed and the chosen window opens.

    15.6

    Marking network objects in the network


    In the network, you can mark network objects as follows.

    15.6.1

    Marking active and passive network objects


    You can mark network objects regardless of whether they are active or passive. You can edit
    or delete marked network objects.
    Tip: You can also mark network objects in the lists (see "Working with lists" on page
    2299), in the Timetable editor (see "Using the Timetable editor" on page 1526), in the
    Network window (see "Marking window" on page 810), in the Quick view (see "Quick
    view window" on page 810), in the Signal time-space diagram (see "Displaying signal
    time-space diagrams" on page 2479), in the Matrix editor (see "Managing, showing and
    analyzing matrices" on page 1715) and in the Schematic line diagram (see "Creating
    schematic line diagrams" on page 2451).
    Note: Below, the standard procedure is described, which applies to most of the network
    objects. A detailed description on how to mark network objects is given with the respective network object type, for example links (see "Managing links" on page 1099).

    1004

    PTVGROUP

    15.6.2 Marking only active network objects

    1. In the Network window, click the

    Edit mode icon.

    2. Click the button of the desired network object type.


    3. In the network, click the desired network object.

    Note: If in the tool bar the


    Click only active objects icon is activated, you can
    only click active network objects (see "Marking only active network objects" on page
    1005). In this mode passive network objects are ignored.
    The network object is marked. It is highlighted in red according to the default settings of the
    graphic parameters. The Quick view window displays the attribute values of the network
    object.
    Note: In case of polygons, click the centroid of the network object or anywhere within
    the boundary.
    4. Press the CTRL key and click on further network objects.
    The network objects are marked.

    15.6.2

    Marking only active network objects


    You can specify that a user can only click active network objects in the network. This is useful,
    for example, if you want to mark a network object that lies very close to other network objects
    of the same type which shall yet not be marked. In this case passive network objects are ignored.
    1. In the toolbar, click the

    Click only active objects icon.

    The icon is activated. You cannot click passive network objects.


    2. In the network, click the desired network objects (see "Marking network objects in the network" on page 1004).
    Only active network objects are marked.
    3. If you want to use all network objects, on the toolbar click the
    icon again.

    Click only active objects

    All network objects can be clicked.

    15.6.3

    Accessing associated objects in the View menu


    If you have marked one or several network objects, you can easily access associated objects.
    1. Mark the desired network object(s) (see "Marking network objects in the network" on page
    1004).
    The network objects are marked and highlighted in the network display.

    PTVGROUP

    1005

    15.6.3 Accessing associated objects in the View menu


    Note: You can specify the colors and the line styles for the display of network objects
    marked in the network and all associated network objects in the Graphics> Edit
    graphic parameters> menu, Basis> entry, Marking 1 and Marking 2 option (see
    "Specifying basic settings" on page 2337).
    2. In the View menu, select the Marking entry.
    The navigator displays a list of the marked network object types and the associated network
    objects.

    Notes: A red dot indicates an object that is marked in the network. Green dots indicate
    associated network objects.
    If a network object is marked, the marked network object will be the first entry in the
    navigator. All associated objects are arranged in categories and will be listed as subordinated entries.
    If several network objects are marked, the list of objects will be hierarchical:
    The network object types and the categories will be listed as superordinated entries.
    The network objects currently marked in the network (red) and their associated
    objects (green) will be listed as subordinated entries.
    Graphic elements that indicate the type of the relation to other network objects are
    described elsewhere (see "The window used for the selection of one attribute" on
    page 963).
    In the toolbar of the window, you can use the following icons to edit the display.

    1006

    PTVGROUP

    15.6.3 Accessing associated objects in the View menu


    Icon

    Name

    Description

    Show only active


    objects

    Switch on/off so that only active objects will be displayed in the navigator (see "Using filters to set network objects active or passive" on page 1008 and
    "Setting network objects active/passive via the spatial selection" on page 1033).
    Note
    The function is activated if the icon is pressed
    (red).

    Expand object tree

    Open all subordinated entries in the navigator


    Tip
    If you want to open the subordinated entries one
    by one, click the icon.

    Reduce object tree

    Close all subordinated entries in the navigator


    Tip
    If you want to close the subordinated entries one
    by one, click the icon.

    Back to previous marking

    Back to previous marked network object

    Go to next marking

    Go to next marked network object

    3. Click the desired associated object.


    The selected network object is highlighted in the network display.
    Notes: In the navigator, you can also select several objects at the same time if you
    hold down the C TRL key while clicking the desired entries.
    If you click on a category, all objects of the category are selected.
    4. Click the

    Mark selected network objects icon.

    The selected object is marked in the network. In the Marking window of the navigator, it is displayed at the top of the list of entries. In the Network window, the respective network object
    type is selected.
    Tip: Alternatively, you can double-click the desired object.

    Note: With the

    Back to previous marking icon you return to the previously marked

    network object. With the


    network object.

    PTVGROUP

    Go to next marking icon you get back to the later marked

    1007

    15.7 Using filters to set network objects active or passive


    Tip: You can edit marked network objects or objects associated with them by rightclicking the object in the navigator and selecting the desired entry in the context menu.
    The available editing functionalities are identical to those for editing marked network
    objects in the network display.
    Note: In addition to the marked objects, you can highlight those network objects which
    are network model-related to the marked network object (see "Showing/hiding extended
    markings" on page 2448).

    15.7

    Using filters to set network objects active or passive


    If you want to edit several network objects at the same time, you can filter them on the basis of
    specified attributes. You can thus limit the entire network to a specific selection of network
    objects.
    By default, a filter affects the network objects of exactly one network object type (standard filter). However, there are also hierarchical filters, where the filter conditions of a network object
    type may affect other network object types, too (see "Working with hierarchical filters" on page
    1016).
    To standard filters, the following applies:
    Network objects, whose attributes comply with the filter settings, are set active.
    Network objects, whose attributes do not comply with the filter settings, are set passive.
    Notes: Network objects are only active, if they comply with the current filter conditions
    and are contained in the spatial selection (see "Setting network objects active/passive
    via the spatial selection" on page 1033).
    The OD pair filter works differently. It filters OD pairs between active zones (see "Modeling demand" on page 1606).
    The GIS object filter does not apply to all network objects of the network object type, but
    just for one category of the GIS objects.
    The POI filter is defined per category. Optionally, it also applies to the POIs of its subcategories. Furthermore, there is a filter over all POIs.
    Under the Network> Network statistics menu, you can get an overview of how many
    network objects per network object type are currently contained in the spatial selection,
    how many are filtered and how many are active (see "berblick ber die Zustnde aller
    Netzobjekte" on page 1041).

    15.7.1

    Opening a filter window


    1. Right-click the

    Switch on/off filter icon of the desired network object type.

    The Filter for <Network object type> window opens.


    Tip: You can also call the Filter for <Network object type> window via the Filter> <Network object type> menu.
    1008

    PTVGROUP

    15.7.2 Specifying filter conditions and applying filters

    Notes: For POIs and GIS objects, at least one category needs to be defined so that the
    window opens.
    For the network object types stops, stop areas, and stop points, the same window Filter
    for PuT stops etc. opens in each case.
    The upper part of the Filter for <Network object type> window contains options which apply
    to the entire filter.
    The lower part of the window usually contains a list in which you can define the filter conditions. In hierarchical filters, several lists are arranged in tabs - one tab for each network
    object type of the hierarchy.
    In the list, each row is equivalent to a filter condition. The options in the list apply line by line
    (see "Specifying filter conditions and applying filters" on page 1009).

    15.7.2

    Specifying filter conditions and applying filters


    Note: Network objects are only active, if they comply with the current filter conditions and
    are contained in the spatial selection (see "Setting network objects active/passive via the
    spatial selection" on page 1033).
    1. Make sure that the filter window of the desired network object type is open (see "Opening a
    filter window" on page 1008).
    2. Select the desired tab (hierarchical filters) or the desired category in the list (POI filter and
    GIS object filter), if required.
    3. Set up the filter conditions (see "Specifying a filter condition" on page 1010).
    4. Select the desired options in the upper part of the filter window.
    Element

    Description

    Complement

    If the option has been selected, all network objects that comply with
    the filter conditions are set passive. All others are set active.
    If the option has not been selected, the network objects that comply
    with the filter conditions are set active. All others are set passive.
    Notes
    The option is not available in hierarchical filters.
    If the Complement option has been selected for individual filter conditions, it first has an effect on the individual filter conditions. They result
    in an overall complement. The Complement option applies to the entire
    filter condition.

    Undirected

    PTVGROUP

    If the option has been selected, all network objects are active of
    which the undirected values based on both directions comply with the
    respective filter conditions.

    1009

    15.7.2.1 Specifying a filter condition


    Element

    Description
    If the option has not been selected, only the directions of the network
    objects will be active which comply with the respective filter conditions.
    Example
    A link has the following PrT volume:
    From node 10 - To node 11 = 500
    From node 11 - To node 10 = 700
    As a filter condition, Volume[Veh] PrT 500 is specified.
    If the option has been selected, no direction of the link will be active
    since the undirected value of the volume is 1200 and the filter condition
    is thus not met.
    If the option has not been selected, only the direction From node 10 - To
    node 11 will be active, since the value lies within the specified range.
    Note
    The option is only provided in the link filter and in the connector filter.

    5. Select the Use filter option.


    Note: In the Filter applies to section of hierarchical filters, you also have to specify, to
    which network object types the filter conditions shall apply (see "Working with hierarchical filters" on page 1016).
    6. Click the Preview button.
    The network objects are displayed active and passive according to the current settings. The
    Filter for <Network object type> window remains open.
    7. Edit the filter settings, if required.
    Note: If you edit the filter settings, you need to click the Preview button again to
    refresh the display.
    8. Confirm with OK.
    Tip: Alternatively, you can confirm your changes with ALT + ENTER.
    The network objects are set active and passive according to the current settings.
    15.7.2.1

    Specifying a filter condition


    1. Make sure that the filter window of the desired network object type is open (see "Opening a
    filter window" on page 1008).
    2. Select the desired tab (hierarchical filters) or the desired category in the list (POI filter and
    GIS object filter), if required.
    By default, a row is displayed for the definition of a filter condition.
    3. Click the empty button under the Attribute column header.

    1010

    PTVGROUP

    15.7.2.1 Specifying a filter condition


    The Attributes (<Network object type>) window opens.
    4. Select the desired attribute (see "The window used for the selection of one attribute" on
    page 963).
    5. Confirm with OK.
    The selected attribute is displayed.
    6. For each row, select the desired operator in the Operation column.
    Note: Depending on the attribute type, different operations can be selected.
    Element

    Description

    Is contained in

    is contained in

    Between (limits included)

    greater/equal to value 1 and smaller/equal to value 2

    < Value

    smaller than value

    < Attribute

    smaller than attribute

    > Value

    greater than value

    > Attribute

    greater than attribute

    Value

    smaller/equal to value

    Attribute

    smaller/equal to attribute

    Value

    greater/equal to value

    Attribute

    greater/equal to attribute

    = Value

    equal to value

    = Attribute

    equal to attribute

    Value

    unequal to value

    Attribute

    unequal to attribute

    Is empty

    there is no entry

    Contains all

    contains all (e.g. transport systems)

    Contains none

    contains none (e.g. transport systems)

    Contains at least one

    contains at least one (e.g. transport system)

    7. Specify the desired value range.


    Note: Depending on the selected attribute different input options are provided.

    PTVGROUP

    1011

    15.7.2.1 Specifying a filter condition


    Input option

    Input of the value range

    Two input fields

    If you have selected a numerical attribute, two input fields are provided.
    If required, enter the lower limit of the value range in the left input
    field and the upper limit of the value range in the right input field.
    Notes
    The upper and the lower limit are always included in the value
    range.
    Empty entries are permitted, i.e. if you do not enter an upper limit,
    all values greater than or equal to the lower limit are contained in
    the value range. If you do not specify a lower limit, all values smaller than the upper limit are contained in the value range.
    If you specify neither a lower limit nor an upper limit, only the network objects without attribute values will be active.

    One input field

    If you have selected an alphanumerical attribute, one input field is


    provided. Enter the string by which you want to filter.
    You have two input options:
    complete string (sequence of characters), for example market
    All network objects with the attribute value market are set
    active.
    One or more characters in the correct order with a wildcard
    (*), for example mark* or *et
    All network objects with an attribute value that starts with
    mark or ends in et are set active.
    Notes
    You can specify multiple wildcards in one string (* and ?). A question mark replaces exactly one character. Wildcards can be located anywhere within the string.
    This is a case-sensitive setting.
    If you do not enter a value, only network objects without attribute
    values are active.

    Field with button

    If the attribute has predefined attribute values, a button is provided instead of input fields. A click on the button opens a window
    in which you can select the desired entries.
    Tips
    You can select several non-consecutive entries if you hold down
    the CTRL key while clicking the desired entries.
    You can select all entries by clicking the Select all button. You
    can discard your selection by clicking the Select none button.

    8. If required, select the Complement option in the column in which you define filter conditions.

    1012

    PTVGROUP

    15.7.2.1 Specifying a filter condition


    Note: This option inverts the filter conditions of the respective row. If it has been selected, exactly those network objects will be active which would usually be passive and
    vice versa.
    Example 1

    The link filter activates all links of the transport system Car and of the selected link types,
    whose saturation exceeds 100%.
    Example 2
    Links are filtered by their link numbers.
    Input of the filter conditions
    Attribute

    Effect

    Value range
    From

    Complement Complement
    (all)
    (line by line)

    To

    Filtered links

    No.

    2 No. 5

    No.

    No. < 2, No. > 5 *

    No.

    No. < 2, No. > 5 **

    No.

    2 No. 5*

    No.

    No. 2

    No.

    No. 5

    No.

    No. = 5

    *) The complement applies to all value ranges of all selected attributes.


    **) The complement only applies to the respective attribute.
    Notes: If you want to delete or copy a filter condition, select the desired row and click
    the Delete or Duplicate button.
    If you want to delete or copy multiple filter conditions, press and hold down the C TRL
    key, select the desired rows and click the Delete or Duplicate button.
    PTVGROUP

    1013

    15.7.2.2 Specifying combined filter conditions


    15.7.2.2

    Specifying combined filter conditions


    1. Make sure that the filter window of the desired network object type is open (see "Opening a
    filter window" on page 1008).
    2. Select the desired tab (hierarchical filters) or the desired category in the list (POI filter and
    GIS object filter), if required.
    3. Set up the filter conditions (see "Specifying a filter condition" on page 1010).
    4. Click the Create button.
    Another filter condition is created. In the first column, And is set automatically.
    Concatenation

    Description

    And

    The filter conditions linked with And are additive, i.e. a network object
    is only active, if it complies with all filter conditions linked by And.

    Or

    A network object will be active, if it complies with at least one of the filter conditions linked by Or.
    The input logic follows Morgans law:
    A or B = not (not A and not B).

    5. Click the And button, if required.


    In the column, Or is set.
    6. Specify another filter condition (see "Specifying a filter condition" on page 1010).
    7. Insert further filter conditions, if required, and specify the kind of operation.
    Notes: If you want to delete or copy a filter condition, select the desired row and click
    the Delete or Duplicate button.
    If you want to delete or copy multiple filter conditions, press and hold down the C TRL
    key, select the desired rows and click the Delete or Duplicate button.

    Examples for filter conditions


    Filter conditions for links
    Volume[Veh] PrT 1000
    Saturation PrT < 100

    The link filter filters all links that comply with both filter conditions (And operation).
    1014

    PTVGROUP

    15.7.2.3 Setting filter conditions in brackets

    The link filter filters all links that comply with at least one of the two filter conditions (Or operation).
    15.7.2.3

    Setting filter conditions in brackets


    In a filter with multiple conditions you can set brackets to ensure that the filter conditions are
    applied correctly.
    Brackets are only permitted in a filter condition if at least three rows exist with filter conditions.
    1. Make sure that the Filter for <Network object type> window of the desired network object
    is open and three or more filter conditions are defined.
    2. In the filter window, mark the rows that you want to put in brackets. Press and hold down the
    CTRL key and click at least two row numbers displayed one below the other.
    The rows with the filter conditions are marked.
    3. Click the Put into brackets button.
    The marked filter conditions are put in brackets.
    4. If you want to remove the brackets, mark the respective filter conditions and click the
    Remove brackets button.
    The brackets are removed.
    Example
    Filter conditions for links
    Volume[Veh] PrT 1000
    Saturation PrT < 100
    Capacity PrT 1200

    PTVGROUP

    1015

    15.7.2.4 Working with hierarchical filters

    The link filter filters all links that have a maximum volume of 1000 and saturation below 100%
    or have a maximum capacity of 1200 vehicles.
    15.7.2.4

    Working with hierarchical filters


    By default, a filter affects the network objects of exactly one network object type. However,
    there are also hierarchical filters, where the filter conditions of a network object type may affect
    other network object types, too. This applies to stops, stop areas, stop points, lines, line routes,
    line route items, time profiles, time profile items, vehicle journeys, vehicle journey items,
    vehicle journey sections, path sets, paths, and path items.
    If, for example, you only want to filter the vehicle journey sections of a certain transport system,
    proceed as follows. Filter the lines by the TSys Code attribute and thus at the same time all
    associated vehicle journey sections. If, however, you want to filter, for example, all lines which
    use a specific vehicle combination proceed as follows. Filter the vehicle journey sections by
    the Vehicle combination number attribute and thus at the same time all lines.
    For the hierarchical filter, you always need to specify two settings, which are independent of
    each other:
    Specify the filter conditions. These can be specified for one or more network object types.
    You can additionally restrict a network object filter to individual network objects.
    Example: In a hierarchy of A-B-C-D-E, you define filter conditions for B and D.
    Specify to which of the hierarchically linked network object types the filter shall apply. If
    you exclude a network object type from the filter, this type is not filtered and the network
    objects are all activated.
    Example: You define that the filter only applies to layers C and D.
    The network objects of the network object types to which the filter applies, are active, if all of
    the following conditions apply:
    The network object complies with its filter conditions.
    On each higher level, the predecessor complies with the specified filter conditions.
    On each lower level, either no filter conditions have been specified or filter conditions
    have been specified and a consistent path exists to this level, on which each network
    object complies with the conditions specified for that level.

    1016

    PTVGROUP

    15.7.2.4 Working with hierarchical filters


    In the above example, only network objects of level C and D can thus be filtered, depending
    on the filter conditions that have been specified for B and D. The network objects of level A, B
    and E will all be active, since the filter does not apply to them.
    Example of a hierarchical filter of the line hierarchy
    The line filter distinguishes between hierarchy objects (line, line route, time profile, vehicle journey, and vehicle journey section) and item objects (line route item, time profile item, vehicle
    journey item).
    A hierarchy object is active, if, from this object, a path exists up and down in the hierarchy
    along which the following applies on each level (even on the level of the object):
    The hierarchy object fulfills its own filter criterion, if one has been defined.
    At least one associated item object fulfills its own filter criterion, if defined.
    An item object is active, if the associated hierarchy object is active and fulfills its own condition,
    if defined.
    In the following example, conditions have been defined for the levels line, line route, line route
    item, time profile, time profile item and vehicle journey.

    PTVGROUP

    1017

    15.7.2.4 Working with hierarchical filters

    Active network objects


    L1, since at least one item object fulfills
    its own conditions
    R1, since its own conditions are fulfilled
    and all item objects fulfill their conditions
    P2, since it fulfills its own conditions and
    at least one associated item object fulfills its own conditions
    R1V1, R1V2, R1V3 and R1V4, since
    they fulfill their own conditions and the
    associated hierarchy object (R1) is
    active
    P2V1 and P2V3 are active, since they
    fulfill their own conditions and the associated hierarchy object (P2) is active
    1018

    Passive network objects


    P1, since none of the item objects fulfill
    their own conditions
    P1V1, P1V2, P1V3, since they do not fulfill their own filter conditions
    F1 and F2, since their time profile P1 is
    not active

    PTVGROUP

    15.7.2.4 Working with hierarchical filters

    Note: Network objects are only active, if they comply with the current filter conditions and
    are contained in the spatial selection (see "Setting network objects active/passive via the
    spatial selection" on page 1033).
    1. Make sure that the filter window of the desired network object type is open (see "Opening a
    filter window" on page 1008).
    2. Select the desired tab.
    3. Set up the filter conditions (see "Specifying a filter condition" on page 1010).
    4. Click the Selection on/off button.
    The Selection <Object> window opens.
    Note: This button is not provided for line route items, time profile items, and vehicle
    journey items.
    5. Select the network objects to which the specified filter conditions shall apply by clicking in
    the desired rows of the list.
    Element

    Description

    Check all

    Use this button to select all rows.

    Uncheck
    all

    Use this button to initialize a selection.

    Invert

    Use this button to select the non-selected rows and vice versa.

    Note: You can select several successive rows if you hold down the C TRL key and leftclick the desired rows.
    6. Select the Use selection option.
    7. Confirm with OK.
    The button label is displayed in a different color.
    8. Select the Use filter option.
    9. If required, select other tabs and specify further filter conditions.
    Note: The labels of tabs, in which filter conditions have been specified, are displayed
    in a different color.
    10. In the Filter applies to section, specify to which network object types the filter shall apply.
    Note: In the line filter, you can select all options via the Check all button and deselect
    all options via the Uncheck all button.

    PTVGROUP

    1019

    15.7.2.5 Working with relations in filters


    11. Confirm with OK.
    The network objects of the network object types to which the filter applies, are set active or passive according to the filter conditions and the hierarchical relations.
    15.7.2.5

    Working with relations in filters


    You can define filter conditions for indirect attributes using 1:n relations. So network objects
    can be filtered for compliance with one or all relations. Thus, in each filter condition, select a
    relation, an attribute of the network object at the other end of the relation, a set operation and
    an operator.
    For example, you can filter all lines which do not traverse a certain link, or all zones connected
    to a node.
    1. Make sure that the filter window of the desired network object type is open (see "Opening a
    filter window" on page 1008).
    2. Select the desired tab (hierarchical filters) or the desired category in the list (POI filter and
    GIS object filter), if required.
    By default, a row is displayed for the definition of a filter condition.
    3. Select the Complement option, if required. in the row in which you are defining the filter
    conditions.
    Note: If this is selected, precisely those network objects are activated that would otherwise be passivated by the filter conditions and vice-versa.
    If you use the option Use complement with a 1:n relation, please note that the complement applies to the entire condition, including the set operation. Applied to a 1:n
    relation, this means that an All x =Value A condition becomes the One x Value A
    condition.
    4. Click the (<Network object type>) button under the Relation column header.
    The Relations (<Network object type>) window opens.
    5. Open the desired relation.
    6. Confirm with OK.
    The desired relation is displayed.
    Tip: By default, the first entry (<Network object type>) of the selection list is displayed,
    which does not correspond to any relation.
    7. Click the empty button under the Attribute column header.
    The Attributes (<Network object type>) window opens.
    Note: In the window not the attributes of the current network object are displayed but
    all attributes for the destination of the selected relation.

    1020

    PTVGROUP

    15.7.2.5 Working with relations in filters


    8. Select the desired attribute.
    9. Confirm with OK.
    The selected attribute is displayed.
    10. In the drop-down list, select the desired set operation from the Set operation column.
    Element

    Description

    One

    The operation is performed for the selected object.

    All

    The operation is performed for all objects.

    Note: The field is empty if no 1:n relation has been selected in the Relation column.
    11. For each row, select the desired operator in the Operation column.
    Element

    Description

    Is contained in

    is contained in

    Between (limits included)

    greater/equal to value 1 and smaller/equal to value 2

    < Value

    smaller than value

    < Attribute

    smaller than attribute

    > Value

    greater than value

    > Attribute

    greater than attribute

    Value

    smaller/equal to value

    Attribute

    smaller/equal to attribute

    Value

    greater/equal to value

    Attribute

    greater/equal to attribute

    = Value

    equal to value

    = Attribute

    equal to attribute

    Value

    unequal to value

    Attribute

    unequal to attribute

    Is empty

    there is no entry

    Contains all

    contains all (e.g. transport systems)

    Contains none

    contains none (e.g. transport systems)

    Contains at least one

    contains at least one (e.g. transport system)

    12. Specify the desired value range.

    PTVGROUP

    1021

    15.7.3 Switching filters on or off


    Note: Depending on the selected attribute different input options are provided.
    13. Confirm with OK.
    The filter is applied.
    Example 1
    Find all lines not using link A
    Network object is Line
    Relation is Line routes\line route items
    Attribute is InLink\name
    Set operation is All
    Operator is value
    Value is A
    Example 2
    Find all zones connected to node 4711
    Network object isZone
    Relation is Origin connectors
    Attribute is Node\number
    Set operation is One
    Operator is = value
    Value is 4711
    If you want to find all zones which are only connected to node 4711, you have to select the All
    set operator.

    15.7.3

    Switching filters on or off


    You can switch on/off filters quickly without having to delete the filter conditions.
    Note: Under the Network> Network statistics menu, you can get an overview of the
    active network object filters (see "berblick ber die Zustnde aller Netzobjekte" on page
    1041).

    15.7.3.1

    Switching on filters
    1. Make sure that filter conditions are specified (see "Specifying filter conditions and applying
    filters" on page 1009).
    2. Click the

    Switch on/off filter icon of the desired network object type.

    Note: If no filter conditions are specified, a window opens. If you confirm the query
    with Yes, the filter window of the respective network object type opens. Specify the filter conditions here (see "Specifying filter conditions and applying filters" on page
    1009).

    1022

    PTVGROUP

    15.7.3.2 Switching off individual filters


    The filter will be switched on and the network objects are filtered according to the specified filter conditions. The Switch on/off filter icon is pressed and displayed in a different color.
    Tip: Alternatively, you can enable a network object filter by selecting the Use filter option
    in the respective filter window (see "Specifying filter conditions and applying filters" on
    page 1009); in case of hierarchical filters, in combination with the Filter applies to option
    (see "Working with hierarchical filters" on page 1016).
    15.7.3.2

    Switching off individual filters


    1. Click the

    Switch on/off filter icon of the desired network object type.

    The filter is switched off. All network objects which are contained in the spatial selection are
    active. The Switch on/off filter icon is not highlighted any more.
    Tip: Alternatively, you can switch off a network object filter by selecting the Use filter
    option in the respective filter window (see "Specifying filter conditions and applying filters" on page 1009), and in case of hierarchical filters, in combination with the Filter applies to option (see "Working with hierarchical filters" on page 1016).
    15.7.3.3

    Switching off several filters at the same time


    1. In the Filter menu, select the Set passive entry.
    The Disable filter window opens.
    2. Select the network object filters that you want to switch off.
    Notes: You can only select the network object types with currently active filters.
    Use the Check all button to select all network object filters and the Uncheck all button to switch off all network object filters.
    3. Confirm with OK.
    The selected filters are switched off.

    15.7.4

    Initializing filter conditions


    There are several ways to initialize filter conditions:
    Initializing the filter conditions of a filter
    Initializing the filter conditions of several filters

    15.7.4.1

    Initializing the filter conditions of a filter


    1. Make sure that the filter window of the desired network object type is open (see "Opening a
    filter window" on page 1008).
    2. If required, select the desired category in the list (POI filter and GIS object filter).
    3. Click the Initialize button.

    PTVGROUP

    1023

    15.7.4.2 Initializing the filter conditions of several filters


    All filter conditions of the filter are initialized. In case of hierarchical filters, the filter settings are
    initialized in all tabs.
    15.7.4.2

    Initializing the filter conditions of several filters


    1. In the Filter menu, select the Initialize entry.
    The Initialize filter window opens.
    2. Select the network object filters whose filter conditions you want to initialize.
    Element

    Description

    Uncheck all

    Use this button to deselect all network object filters.

    Check all

    Use this button to select all network object filters.

    Note: You can only select the network object types with currently active filters.
    3. Confirm with OK.
    The filter conditions of the selected network object filters are initialized.
    15.7.4.3

    Initializing all filters during a procedure sequence


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the desired position of the procedure sequence, insert the Initialize all filter settings procedure of the Miscellaneous category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Execute the procedure (see "Setting up and starting the procedure sequence" on page
    1847).
    All filters are initialized.

    15.7.5

    Reading and saving filters


    You can read and save filter settings as follows.

    15.7.5.1

    Saving filters
    You can save the currently specified filter settings of all network object types to a file.
    Note: Specified filter conditions and active filters are also saved with the version file (see
    "Opening and saving a version file" on page 840).
    1. In the Filters menu, select the Save filter file entry.
    The Save: Filter window opens.

    1024

    PTVGROUP

    15.7.5.2 Reading filters


    Tip: You can also call the Save: Filter window via the File> Save as> menu and the
    Filters entry.
    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The filter conditions of all network object filters are saved.
    Note: If you want to save the filter of a specific network object type only, specify filter conditions for this network object type only and save those conditions. If you want to save the
    conditions of particular filter types, we recommend indicating this in the file name, for
    example by calling a node filter file N_exl.fil.
    15.7.5.2

    Reading filters
    1. In the Filter menu, select the Open filter file entry.
    The Open: Filter window opens.
    Tip: You can also call the Open: Filter window via the File> Open> menu and the Filter entry.
    2. Select the desired file.
    3. Click the Open button.
    The Read filter window opens.

    4. Select the network object filters that you want to read in.

    PTVGROUP

    1025

    15.7.5.3 Reading filters during a procedure sequence


    Element

    Description

    Initialize existing
    filters first

    If the option has been selected, all currently set filters which are
    not contained in the filter file are initialized when reading the filters.

    Uncheck all

    Use this button to deselect all network object filters.

    Check all

    Use this button to select all network object filters.

    Note: Network object filters are grayed out in the list if they are not contained in the filter file.
    5. Confirm with OK.
    The selected network object filters are read in.
    15.7.5.3

    Reading filters during a procedure sequence


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the desired position of the procedure sequence, insert the Read filter operation of the
    Miscellaneous category (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the icon

    in the Variant/file column.

    The Open: Filter window opens.


    4. Select the desired file.
    5. Click the Open button.
    6. Execute the procedure (see "Setting up and starting the procedure sequence" on page
    1847).
    The filter file is read in.
    Tip: Alternatively you can double-click the field in the Variant/file column and enter manually path and file name.

    15.7.6

    Exception: Filter for OD pairs


    The filter for OD pairs is fundamentally different from the network object filters since it exclusively filters origin-destination pairs between zones and PuT paths. Thus, it does not serve to
    set individual network objects active or passive (see "Modeling demand" on page 1606). The
    filter for OD pairs allows you to filter and display PuT volumes and indicators in the network
    specifically for OD pairs and PuT paths. Hereby, the filter conditions for PuT paths are subordinated to OD pair conditions.

    1026

    PTVGROUP

    15.7.6.1 Opening an OD pair filter


    The filters have an effect on the following lists if in the respective list under Selection the Filter
    for OD pairs entry has been selected. The Filter network volumes option has no influence
    here (see "Opening a list" on page 2299).
    PuT assignment statistics
    PuT OD pairs
    PuT paths
    PuT path legs
    Note: The Main OD pairs filter provides the same filtering options for Main OD pairs as
    the filter for OD pairs for OD pairs. However, PuT paths cannot be filtered using this filter.
    15.7.6.1

    Opening an OD pair filter


    1. Right-click the

    Switch on/off filter icon of the OD pairs network object type.

    The Filter for OD pairs of zones window opens.


    Tip: You can also call the Filter for OD pairs of zones window via the Filters> OD pairs
    menu.
    15.7.6.2

    Defining filter conditions for OD pairs and PuT paths


    Using the filter for OD pairs you can define conditions for OD pairs and PuT paths.
    Setting conditions for OD pairs
    You can filter relations between zones on the basis of the following conditions:
    Direct distance between the centroids of the zones
    Values of direct and indirect zone attributes
    Values of a demand matrix
    1. Make sure that the filter for OD pairs is open (see "Opening an OD pair filter" on page
    1027).
    2. Click the button below the Relation column header.
    The Relations (OD pairs) window opens.
    3. Open the desired relation.
    4. Confirm with OK.
    The selected relation is displayed.
    5. Click the button below the Attribute column header.
    The Attributes (OD pairs) window opens.
    6. Select the desired attribute (see "The window used for the selection of one attribute" on
    page 963).
    7. Confirm with OK.
    The selected attribute is displayed.

    PTVGROUP

    1027

    15.7.6.2 Defining filter conditions for OD pairs and PuT paths


    8. Select the desired operator in the Operation column (see "Specifying a filter condition" on
    page 1010).
    9. Specify the desired value range.
    10. Select the Complement option, if required.
    Note: This option inverts the filter conditions of the respective row. If it has been selected, exactly those network objects will be active which would usually be passive and
    vice versa.
    11. If required, select the Filter network volumes option.
    Note: If the option has not been selected, the network volumes are not recalculated
    for the filter.
    12. Click the Create button, if required.
    Another filter condition is created. In the Operation column, And is set automatically.
    Concatenation

    Description

    And

    The filter conditions linked with And are additive, i.e. an OD pair is only
    active, if it complies with all filter conditions linked by And.

    Or

    An OD pair will be active if it complies with at least one of the filter conditions linked by Or.
    The input logic follows Morgans law:
    A or B = not (not A and not B).

    13. Click the And button, if required.


    In the Operation column, Or is set.
    14. Specify another filter condition.
    15. Insert further filter conditions, if required, and specify the kind of operation.
    Note: If you insert more than three rows, in the Filter condition section, you can set
    brackets in the filter condition using thePut into brackets button (see "Specifying combined filter conditions" on page 1014).
    16. If you want to delete a filter condition, mark the desired row and click the Delete button.
    Tip: If you want to delete multiple filter conditions, press the C TRL key and keep it pressed. Mark the desired rows an click the Delete button.

    1028

    PTVGROUP

    15.7.6.2 Defining filter conditions for OD pairs and PuT paths


    Example

    The OD pair filter determines all relations which comply with the following conditions:
    The origin is a zone which is part of a main zone with an AddValue 1000.
    The direct distance between the centroids of the zones is 2 kilometers.
    The From Zone Number is not equal to 100.
    Setting filter conditions for PuT paths
    In addition to the OD pair filters you can specify filter conditions for PuT paths in order to define
    which PuT paths are included in the PuT network volumes.
    1. Make sure that the filter for OD pairs is open (see "Opening an OD pair filter" on page
    1027).
    2. Select the PuT paths tab.
    3. Click the button below the Relation column header.
    The Relations (PuT paths) window opens.
    4. Select the desired relation.
    5. Confirm with OK.
    The selected relation is displayed.
    6. Click the button below the Attribute column header.
    The Attributes (PuT paths) window opens.
    7. Select the desired attribute (see "The window used for the selection of one attribute" on
    page 963).
    Note: You can filter for the demand segment of the PuT path if you select the DSegCode attribute. A path is allocated only to a demand segment if for this demand segment its volume is > 0.
    8. Confirm with OK.

    PTVGROUP

    1029

    15.7.6.2 Defining filter conditions for OD pairs and PuT paths


    The selected attribute is displayed.
    9. In the drop-down list, select the desired set operation from the Set operation column.
    Element

    Description

    One

    The operation is performed for the selected object.

    All

    The operation is performed for all objects.

    Note: The field is empty if no 1:n relation has been selected in the Relation column.
    10. In the Operation column, select the desired operator (see "Specifying a filter condition" on
    page 1010).
    11. Specify the desired value range.
    12. Select the Complement option, if required.
    Note: This option inverts the filter conditions of the respective row. If it has been selected, exactly those PuT paths will be active which would turn passive due to the filter
    condition.
    13. Click the Create button, if required.
    Another filter condition is created. In the Operation column, And is set automatically.
    Concatenation

    Description

    And

    The filter conditions linked with And are additive, i.e. an OD pair is only
    active, if it complies with all filter conditions linked by And.

    Or

    An OD pair will be active if it complies with at least one of the filter conditions linked by Or.
    The input logic follows Morgans law:
    A or B = not (not A and not B).

    Note: If you insert more than three rows, in the Filter condition section, you can set
    brackets in the filter condition using the Put into brackets button (see "Specifying
    combined filter conditions" on page 1014).
    14. Click the And button, if required.
    In the Operation column, Or is set.
    15. If you want to delete a filter condition, mark the desired row and click the Delete button.

    1030

    PTVGROUP

    15.7.6.3 Applying filters for OD pairs


    Tip: If you want to delete multiple filter conditions, press the C TRL key and keep it pressed. Mark the desired rows an click the Delete button.
    15.7.6.3

    Applying filters for OD pairs


    1. Make sure that the filter for OD pairs is open (see "Opening an OD pair filter" on page
    1027).
    2. Define the filter conditions for the OD pairs and for the PuT paths, if required (see "Defining
    filter conditions for OD pairs and PuT paths" on page 1027).
    3. If required, select the Filter network volumes option to recalculate the network volumes for
    the filter.
    Notes: If the option has been selected, only those PuT paths which fulfill both the conditions of the OD pair filter and those of the PuT path filter are considered when calculating the network volume.
    In the PuT paths, PuT path legs and PuT OD pairs lists only those paths or OD pairs
    are displayed in the Filter for OD pairs selection which fulfill the conditions of all filters of the Filter for OD pairs of zones window, independently from the Filter network volumes option.
    A recalculation of the PrT network volumes is based on the volumes on the link and,
    thus, takes into account the demanded volume. If a PrT assignment including
    blocking back model has been calculated, congestion is not taken into account. If the
    Filter network volumes option is active, the Volume PrT [veh] (AP) attribute, for
    example, corresponds to the value for Volume demand PrT [veh] (AP) after the recalculation.
    4. Select the Use filter option.
    .

    Note: The option applies to both tabs of the Filter for OD pairs of zones window.
    5. Click the Preview button.
    The relations are set active and passive according to the current settings. The Filter for OD
    pairs of zones window remains open.
    6. Edit the filter settings, if required.
    Note: If you edit the filter settings, you need to click the Preview button again to
    refresh the display.
    7. Confirm with OK.
    The relations are set active and passive according to the current settings.

    PTVGROUP

    1031

    15.7.6.4 Filtering the traffic between two zones


    Note: In the graphic display and in listings, the OD pair filter has an effect on all volume
    skims:
    Flow bundles and turn volumes
    Volumes of links, connectors, turns, PuT paths and PuT lines
    Boarding, alighting, and transfer passengers at stops
    15.7.6.4

    Filtering the traffic between two zones


    You can filter the traffic between specific types of zones.
    The relative position in the area under consideration determines the type of zone. Internal
    zones are zones, which lie within the area under consideration. External zones lie outside of
    the area under consideration. Zones, whose relative position is not defined in the area under
    consideration, are neutral.
    You can evaluate the following kinds of traffic individually or in combination with each other
    and then display the results graphically or in tables:
    Traffic from internal zones to internal zones
    Traffic from internal zones to external zones
    Traffic from external zones to internal zones
    Traffic from external zones to internal zones
    Note: With the OD pair filter, you cannot filter traffic of the types origin traffic, destination
    traffic, and through traffic. For such evaluations, please use the subnetwork generator
    (see "Using the subnetwork generator" on page 1601) or flow bundles (see "Displaying
    flow bundles" on page 2265).
    1. Click the

    Edit mode icon.

    2. Click the Zones button.


    3. Mark the zone or zones whose relative position you want to edit in the area under consideration (see "Selecting zones" on page 1141).
    4. Edit the relative position of the zone in the area under consideration via the drop-down list
    Relative state (see "Zones: Basis tab" on page 1137) or the attribute Relative state (see
    "Editing the attribute values of zones" on page 1142).
    5. Confirm with OK or press the ENTER key.
    The relative state is changed.
    6. Open the OD pair filter (see "Opening an OD pair filter" on page 1027).
    7. Specify the filter conditions (see "Defining filter conditions for OD pairs and PuT paths" on
    page 1027) as follows:
    For each traffic type by which you want to filter, specify two filter conditions linked by
    AND with the attributes From zone\Relative state and To zone\Relative state.
    If you want to filter by more than on traffic types, link the pairs of filter conditions with
    OR.

    1032

    PTVGROUP

    15.8 Setting network objects active/passive via the spatial selection

    8. Confirm with OK.


    The traffic is filtered.
    Note: Traffic from/to neutral zones is not taken into account for the output of traffic between internal or external zones.
    Example

    The OD pair filter filters the following traffic types:


    Traffic between zones of the relative state internal
    Traffic from internal to external zones and
    Traffic from external to internal zones
    The number of OD pairs found between zones of the respective relative state is reduced by the
    additional filter condition minimum direct distance 1 km.

    15.8

    Setting network objects active/passive via the spatial selection


    If you want to edit several network objects at the same time, via the spatial selection, you can
    set the desired objects active and the remaining objects passive. You can thus limit the entire

    PTVGROUP

    1033

    15.8.1 Selecting network object types for the spatial selection mode
    network to a specific selection of network objects. By default, passive network objects are highlighted in gray (see "Specifying basic settings for the network window" on page 2337).
    Notes: Network objects are active only if they are both included in the spatial selection
    and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).
    Under the Network> Network statistics menu, you can get an overview of how many
    network objects per network object type are currently contained in the spatial selection,
    how many are filtered and how many are active (see "berblick ber die Zustnde aller
    Netzobjekte" on page 1041).
    You have various options to set network objects active or passive via the spatial selection.
    Setting all network objects passive
    Setting all network objects active
    Setting individual network objects active or passive
    Setting network objects active within a polygon
    Setting network objects active within territories
    Notes: A spatial selection is not possible in case of system routes, lines, line routes, and
    all subordinated items.
    Only network objects of network object types whose Switch on/off spatial selection
    option has been selected, will be taken into account (see "Selecting network object types
    for the spatial selection mode" on page 1034).

    15.8.1

    Selecting network object types for the spatial selection mode


    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar opens and in the Network window, the Switch on/off spatial
    selection options are displayed.

    2. Select the Switch on/off spatial selection option for the desired network object types.
    Network objects of the network object types which are selected will be considered in the spatial selection. All remaining network objects keep their respective active/passive state.

    1034

    PTVGROUP

    15.8.2 Setting all network objects passive

    Tip: If you want to consider all network object types in the spatial selection, click the
    For selection operations, check all types icon. If you do not want to consider any of the
    network object types in the spatial selection, click the
    uncheck all types icon.

    15.8.2

    For selection operations,

    Setting all network objects passive


    Note: Only network objects of network object types whose Switch on/off spatial selection option has been selected, will be taken into account.
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the
    tion icon.

    Remove all objects from the spatial selec-

    All objects are set passive.

    15.8.3

    Setting all network objects active


    Notes: Only network objects of network object types whose Switch on/off spatial selection option has been selected, will be taken into account.
    Only network objects which comply with the current filter conditions can be set active
    (see "Using filters to set network objects active or passive" on page 1008).
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the
    icon.

    Include all objects into the spatial selection

    All network objects are set active.

    15.8.4

    Setting individual network objects active or passive


    Notes: You cannot set single system routes, lines, line routes, paths, path items and all
    subordinated items active or passive (see "Setting lines active/passive" on page 1296).
    You can set individual network objects active or passive, independent of the setting of
    the Switch on/off spatial selection option.
    Only network objects which comply with the current filter conditions can be set active
    (see "Using filters to set network objects active or passive" on page 1008).
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    PTVGROUP

    1035

    15.8.5 Setting network objects active within a polygon


    2. In the Network window, click the button of the desired network object type.
    3. Click on an active network object.
    Note: In case of polygons, click the centroid of the network object or anywhere within
    the boundary (see "Marking network objects in the network" on page 1004).
    The network object is set passive.
    4. Click on a passive network object.
    Note: In case of polygons, click the centroid of the network object or anywhere within
    the boundary (see "Marking network objects in the network" on page 1004).
    The network object is set active.
    Note: If you want to set just a few network objects active, set all network objects passive
    first by clicking the

    15.8.5

    icon, and then set the desired network objects active one by one.

    Setting network objects active within a polygon


    Notes: You cannot set single system routes, lines, line routes, paths, path items and all
    subordinated items active or passive by specifying a polygon (see "Setting lines active/passive" on page 1296).
    Only network objects of network object types whose Switch on/off spatial selection
    option has been selected, will be taken into account.
    Only network objects which comply with the current filter conditions can be set active
    (see "Using filters to set network objects active or passive" on page 1008).
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the
    icon.

    Set spatial selection to the exclusive state

    3. Hold down the C TRL key and click to define the polygon points of the planned polygon.
    4. Press the ENTER key.

    1036

    PTVGROUP

    15.8.6 Setting network objects active within territories

    All network objects, which are located within the territory, are set active. Network objects outside of the polygon are set passive.
    Note: To zones, main zones, main nodes, POIs and GIS objects with polygons the co-ordinates of the centroid apply.
    Tip: Alternatively, you can simply specify a rectangular section by defining the upper left
    corner of the intended rectangle with a mouse click, then holding down the mouse key
    and dragging the desired rectangle.

    15.8.6

    Setting network objects active within territories


    Notes: You cannot set single system routes, lines, line routes, paths, path items and all
    subordinated items active or passive by specifying a territory (see "Setting lines active/passive" on page 1296).
    Only network objects of network object types whose Switch on/off spatial selection
    option has been selected, will be taken into account.
    Only network objects which comply with the current filter conditions can be set active
    (see "Using filters to set network objects active or passive" on page 1008).
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the
    tion icon.

    Mark objects in territory for spatial selec-

    3. In the network, click the centroid of the desired territory or anywhere within its boundary
    (see "Marking territories" on page 1209).
    All network objects, which are located within the territory polygon, are set active. Network
    objects outside of the polygon are set passive.
    Note: To zones, main zones, main nodes, POIs and GIS objects with polygons the co-ordinates of the centroid apply.

    PTVGROUP

    1037

    15.8.7 Inverting the active/passive state of network objects

    15.8.7

    Inverting the active/passive state of network objects


    Notes: Only network objects of network object types whose Switch on/off spatial selection option has been selected, will be taken into account.
    Only network objects which comply with the current filter conditions can be set active
    (see "Using filters to set network objects active or passive" on page 1008).
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the

    Invert spatial selection icon.

    All passive network objects are set active and all active network objects are set passive.

    15.8.8

    Extending and reducing the spatial selection of network objects


    Notes: Only network objects of network object types whose Switch on/off spatial selection option has been selected, will be taken into account.
    Only network objects which comply with the current filter conditions can be set active
    (see "Using filters to set network objects active or passive" on page 1008).
    1. Set the desired network objects active via the spatial selection.
    2. In the Spatial selection toolbar, click the

    Add objects to spatial selection icon.

    3. Select the desired network objects.


    The additionally selected network objects are set active. All remaining network objects
    keep their respective active/passive state.

    1038

    PTVGROUP

    15.8.9 Saving a spatial selection of network objects

    4. In the Spatial selection toolbar, click the

    Exclude objects from spatial selection icon.

    5. Select the desired network objects.


    The additionally selected network objects are set passive. All remaining network objects keep
    their respective active/passive state.

    15.8.9

    Saving a spatial selection of network objects


    You can save the network objects which are currently contained in the spatial selection to a
    file. The current spatial selection is saved with the version file.
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the

    Save spatial selection to file icon.

    The Save active network objects window opens.


    Tip: You can also call the Save active network objects window via the File> Save
    as> menu and the Active network objects entry.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The current spatial selection is saved.
    Note: Under the Network> Network statistics menu, you can get an overview of how
    many network objects per network object type are currently contained in the spatial selection, how many are filtered and how many are active (see "Checking the state of network
    objects" on page 1040).

    15.8.10 Reading a spatial selection of network objects


    You can read network objects which are contained in a spatial selection from file.
    Note: Only network objects which comply with the current filter conditions can be set
    active (see "Using filters to set network objects active or passive" on page 1008).
    1. In the Network window, click the

    Spatial selection mode icon.

    The Spatial selection toolbar is displayed.


    2. In the Spatial selection toolbar, click the

    Read spatial selection from file icon.

    The Open active network objects window opens.


    Tip: You can also call the Open active network objects window via File> Open>
    menu and Active network objects entry.
    PTVGROUP

    1039

    15.9 Checking the state of network objects


    3. Select the desired file.
    4. Click the Open button.
    The Read active network objects window opens.

    5. Select the network object types for which you want to read the spatial selection from file.
    Element

    Description

    add

    If the option has been selected, the currently active network objects
    remain active. Other network objects might be set active when reading
    the data.
    If the option has not been selected or if it is not available, only those
    network objects will be active which are saved as active in the file.
    Note
    The option is only available, if, in the network, at least one network object
    is passive.

    Check all

    Use this button to select all options.

    Uncheck
    all

    Use this button to deselect all options.

    6. Confirm with OK.


    The respective network objects are set active or passive.
    Note: Under the Network> Network statistics menu, you can get an overview of how
    many network objects per network object type are currently contained in the spatial selection, how many are filtered and how many are active (see "berblick ber die Zustnde
    aller Netzobjekte" on page 1041).

    15.9

    Checking the state of network objects


    You can check how many objects of a network object type exist in the network and how many
    of these are contained in the spatial selection, filtered, active and passive. Network objects are
    active, if they both comply with the set filters and are contained in the spatial selection.

    1040

    PTVGROUP

    15.9.1 Checking the state of a network object type

    15.9.1

    Checking the state of a network object type


    1. In the Network window, move the mouse pointer over the button of the desired network
    object type.
    A quick info appears.

    15.9.2

    Element

    Description

    Red dot

    A red dot indicates that the spatial selection does not contain all network
    objects of the respective type.

    Quick info

    The quick info displays the number of network objects of the respective type
    that exist in the network and the number of active network objects of the
    respective type.

    berblick ber die Zustnde aller Netzobjekte


    Sie knnen sich einen berblick ber aktuell gefilterte, rumlich ausgewhlte und aktive Netzobjekte verschaffen.
    1. Whlen Sie im Men Netz den Eintrag Netzstatistik.
    Das Fenster Netzstatistik ffnet sich.
    2. Whlen Sie das Register Basis-Netz.
    Fr die Netzobjekte des Basis-Netzes werden die aktuellen Zustnde angezeigt.

    3. Whlen Sie das Register V-Netz.


    Fr die Netzobjekte des V-Netzes werden die aktuellen Zustnde angezeigt.

    PTVGROUP

    1041

    15.10 Managing boundaries of polygonal network objects

    15.10

    Managing boundaries of polygonal network objects


    Note: The functionality is provided for main nodes, zones, main zones, territories, toll systems and POIs with polygons.
    Boundaries of polygonal network objects are polygons which define the boundaries and the
    spatial extent of a network objects. They are optional.
    You can specify a boundary immediately when creating a network object or afterwards. A detailed description on how to directly define the boundary when inserting a network object is given
    with the respective network object type, for example Zones (see "Creating a zone" on page
    1136).
    By default, boundaries consist of a surface (see Fundamentals: Chpt. 3.5 , page 120). You
    can, however, also specify boundary polygons which consist of several faces (see "Creating
    new faces" on page 1050) . Visum normalizes the surfaces automatically when editing a
    shape. You can position new polygon points directly on existing polygon points and merge
    them, if required.
    You can edit boundaries as follows:
    Creating a boundary
    Editing polygon points
    Creating new faces
    Deleting faces
    Deleting boundaries
    Normalizing all surfaces
    Merging all polygon points with identical co-ordinates
    Fuzzy alignment of surfaces

    15.10.1 Creating a boundary


    Prerequisite is that no boundary has been defined yet for the desired network object.

    1042

    PTVGROUP

    15.10.1 Creating a boundary


    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    Visum switches to the Insert mode for boundaries.
    Tip: You can also use the context menu> entry Edit shape to switch to the Insert
    mode for boundaries.
    3. Insert at least three polygon points where you need them with consecutive anti-clockwise
    clicks.
    Note: You can also use polygon points of existing polygons for the new polygon. To
    do so, via the Edit> User Preferences> GUI> Network editor menu, select the Permit snapping option and specify a Snap radius (see "Merging polygon points of two
    polygons" on page 1047).
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the surface (see Fundamentals: Chpt. 3.5 , page 120).

    Notes: Even though you can also insert the polygon points in a clockwise direction,
    this would create a so-called negative face (=hole), which cannot be saved as boundary as no surface exists yet from which it can be cut out (see Fundamentals: Chpt.
    3.5 , page 120).
    If you have selected the Permit snapping option under Edit> User Preferences >
    GUI> Network editor, adjacent polygon points of other polygons are displayed as
    small circles and the mouse pointer turns into a lasso as soon as an existing polygon
    point can be snapped. This way, you can use existing points explicitly.

    4. Confirm the definition of the boundary with a right-click or press ENTER.

    PTVGROUP

    1043

    15.10.2 Editing polygon points


    The boundary is created and the polygon points are highlighted. The Edit shape window
    opens.
    Note: If you confirm the definition of the boundary with a right-click, the coordinates of
    the position of the click will not be saved as polygon point.
    5. If required, reshape the boundary (see "Managing boundaries of polygonal network
    objects" on page 1042).
    6. If desired, select the Merge snapped points option.
    This option merges polygon points that you inserted with the snap function with the original
    polygon point. If you shift the polygon point later on, both polygons will be changed automatically.
    7. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the new boundary is created and the
    step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    8. Click Yes to confirm.
    The network objects (nodes, zones or links) which are within the boundary, are allocated to
    the higher-level network object (main node, main zone or toll system), and the boundary is
    inserted. The surface is normalized automatically.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the network objects later (see "Allocating nodes to one or multiple main
    nodes" on page 1181 and "Editing main node attributes in the list view" on page 1447).

    15.10.2 Editing polygon points


    Prerequisite is that a boundary has already been defined for the desired network object (see
    "Creating a boundary" on page 1042).
    15.10.2.1 Creating polygon points
    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    3. Press the CTRL key and keep it pressed.
    1044

    PTVGROUP

    15.10.2.2 Shifting polygon points


    4. On the boundary, click the position, where you want to create the polygon point.

    The polygon point is created.


    Notes: If you create a polygon point in the position of another point of the boundary,
    the existing polygon point is deleted.
    If the boundary contains exactly three polygon points, the existing polygon point will
    not be deleted nor will the new polygon point be created.
    5. Create further polygon points, if required.
    6. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the new boundary is created immediately and the step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    7. Click Yes to confirm.
    The network objects (nodes, zones or links), which lie within the boundary, are allocated to the
    higher-level network object (main node, main zone or toll system) and the new boundary is
    saved.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).
    15.10.2.2 Shifting polygon points
    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    3. Click the desired polygon point and hold down the mouse button.
    4. Drag the polygon point to the new position and release the mouse button.

    PTVGROUP

    1045

    15.10.2.3 Deleting polygon points

    Notes: If you press the ESC key while dragging, you can cancel the action and the
    polygon point is reset to its original position.
    The polygon point is shifted and the boundary adjusted.
    Note: If you shift the polygon point to the position of a point of a different polygon, the
    polygon points are merged. If you want to prevent the merging of the polygon points,
    deactivate the Permit snapping option via the Edit> User Preferences > GUI> Network editor menu.
    5. Shift further polygon points, if required.
    6. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the new boundary is created immediately and the step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    7. Click Yes to confirm.
    The network objects (nodes, zones or links), which lie within the boundary, are allocated to the
    higher-level network object (main node, main zone or toll system) and the new boundary is
    saved.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).
    15.10.2.3 Deleting polygon points
    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.

    1046

    PTVGROUP

    15.10.2.4 Merging polygon points of two polygons


    3. Press the CTRL key and keep it pressed.
    4. Click the desired polygon point.

    The polygon point is deleted and the boundary adjusted.


    Note: You can delete polygon points only if the boundary contains more than three
    polygon points.
    5. Delete further polygon points, if required.
    6. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the new boundary is created immediately and the step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    7. Click Yes to confirm.
    The network objects (nodes, zones or links), which lie within the boundary, are allocated to the
    higher-level network object (main node, main zone or toll system) and the new boundary is
    saved.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).
    15.10.2.4 Merging polygon points of two polygons
    When merging two polygon points, you first need to specify that a new polygon point may be
    captured by an existing one ("snapping") This ensures that the points have the same co-ordinates. Furthermore, an option enables you to specify whether the two points shall be merged
    or remain two separate points afterwards.
    Note: You can also simultaneously merge all polygon points in the network with the
    same coordinates (see "Merging all polygon points with identical co-ordinates" on page
    1053).
    1. Make sure that the Permit snapping option is selected via the Edit> User Preferences>
    GUI> Network editor menu and specify a Snap radius.

    PTVGROUP

    1047

    15.10.2.4 Merging polygon points of two polygons


    2. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    3. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    4. Click the desired polygon point and hold down the mouse button.
    5. Drag the polygon point to the position of the polygon point of a different polygon.

    Adjacent polygon points of other polygons are displayed as small circles and the mouse
    pointer turns into a lasso as soon as an existing polygon point can be snapped.
    6. Release the mouse button when the lasso is displayed.
    The polygon point is shifted and obtains the coordinates of the other polygon point. The
    Edit shape window opens.
    7. Select the Merge snapped points option.
    8. Confirm with OK.
    The polygon points are merged. The edges between the merged polygon points are also
    merged.
    In case of main nodes, main zones and toll systems, a query opens in some cases.
    9. Click Yes to confirm.
    The network objects (nodes, zones or links), which lie within the boundary, are allocated to the
    higher-level network object (main node, main zone or toll system) and the new boundary is
    saved.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).

    1048

    PTVGROUP

    15.10.2.5 Separating merged polygon points


    15.10.2.5 Separating merged polygon points
    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    3. Hold down the SHIFT key.
    4. Click the desired merged polygon point and hold down the mouse button.
    5. Drag the polygon point to the new position and release the mouse button.

    The polygon points are separated and the boundaries adjusted.


    6. Separate further merged polygon points, if required.
    7. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the new boundaries are created
    immediately and the step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    8. Click Yes to confirm.
    The partial network objects (nodes, zones or links), which lie within the boundary, are allocated to the higher-level network object (main node, main zone or toll system) and the new
    boundary is saved.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).

    PTVGROUP

    1049

    15.10.3 Creating new faces

    15.10.3 Creating new faces


    If, for a network object, you want to specify a boundary polygon, which consists of several
    faces, you can create further faces (see Fundamentals: Chpt. 3.5 , page 120).
    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    3. Click the New face button.
    4. Create a new face with consecutive mouse-clicks (see "Creating a boundary" on page
    1042).
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the face.

    Note: Depending on the direction in which you create the polygon points, the face either belongs to the total surface or is cut out off another face (hole).
    If you insert the polygon points in a counterclockwise direction, the face is part of
    the total surface, i.e. a so-called positive face is created (see Fundamentals:
    Chpt. 3.5 , page 120).
    If you insert the polygon point in a clockwise direction, the face is subtracted from
    the other face, i.e. a so-called negative face is created. You can only create a
    negative face within an existing face (see Fundamentals: Chpt. 3.5 , page 120).
    5. Confirm the definition of the face with a right-click or press ENTER.
    The new face is created.
    6. Create further faces, if required.
    7. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the new boundary is created and the
    step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    8. Click Yes to confirm.
    1050

    PTVGROUP

    15.10.4 Deleting faces


    The network objects (nodes, zones or links), which lie within the boundary, are allocated to the
    higher-level network object (main node, main zone or toll system) and the new boundary is
    saved.
    Note: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).

    15.10.4 Deleting faces


    You can delete individual faces of a boundary polygon that consists of several faces.
    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    3. Click the desired face.
    4. Click the Delete face button.
    The marked face is deleted.
    5. Delete further faces, if required.
    6. Confirm with OK.
    Depending on the network object type, the following applies:
    In case of zones, territories, and polygonal POIs, the changes are applied immediately
    and the step ends here.
    In case of main nodes, main zones and toll systems, a query opens in some cases. Proceed with the next step.
    7. Click Yes to confirm.
    The network objects (nodes, zones or links), which lie within the boundary, are allocated to the
    higher-level network object (main node, main zone or toll system) and the new boundary is
    saved.

    PTVGROUP

    1051

    15.10.5 Deleting boundaries


    Notes: If you want to insert the main node, main zone or toll system with a boundary yet
    without allocated partial network objects, click No when prompted by the query. You can
    also allocate the partial network objects later (see "Allocating nodes to one or multiple
    main nodes" on page 1181 and "Editing main node attributes in the list view" on page
    1447).
    If you want to delete all faces of a boundary polygon at the same time, in the Edit shape
    window, click the Initialize button (see "Deleting boundaries" on page 1052).

    15.10.5 Deleting boundaries


    1. Mark the desired network object (see "Marking network objects in the network" on page
    1004).
    2. Press F5.
    The Edit shape window opens.
    Tip: You can also call the Edit shape window via the context menu> entry Edit
    shape.
    3. Click the Initialize button.
    The boundary is deleted. Visum switches to the Insert mode for boundaries (see "Creating a
    boundary" on page 1042).
    Tip: You can also delete the boundary with F2.
    Note: In case of multi-face boundary polygons, all faces are deleted at the same time.

    15.10.6 Normalizing all surfaces


    You can normalize all surfaces in the network. In this process, the sizes of the surfaces are calculated correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    You only need this functionality if you have previously read in a network or a shapefile without
    normalizing the surfaces (see "Opening and saving a network file and adding comments" on
    page 844 and "Importing Shapefiles" on page 2221).
    1. In the Network menu, select the Network settings entry.
    The Network settings window opens.
    2. Select the Surfaces tab.
    3. Click the Normalize all surfaces (self-intersecting test) button.
    The Normalize surfaces (self-intersecting test) window opens.
    4. Select the desired option for the network object types.

    1052

    PTVGROUP

    15.10.7 Merging all polygon points with identical co-ordinates


    Element

    Description

    None

    If this option has been selected, no surface of the network object


    type is normalized.

    All

    If this option has been selected, all surfaces of the network object
    type are normalized.

    Only active ones


    Open the 'Filters' dialog
    If this option has been selected, the
    icon becomes available. You can activate network objects via the
    filter (see "Using filters to set network objects active or passive"
    on page 1008).
    5. Confirm with OK.
    The desired surfaces in the network are normalized.

    15.10.7 Merging all polygon points with identical co-ordinates


    You can merge all polygon points in the network that have the same co-ordinates. If two polygons are merged, both polygons automatically change when shifting the polygon point. This is
    useful, for example, if polygons have joint boundaries.
    Note: You can already merge polygon points when inserting or editing polygons (see
    "Creating a boundary" on page 1042 and "Merging polygon points of two polygons" on
    page 1047).
    When reading in networks and shapefiles, you can specify whether polygon points with
    the same co-ordinates shall be merged (see "Opening and saving a network file and
    adding comments" on page 844 and "Importing Shapefiles" on page 2221).
    1. In the Network menu, select the Network settings entry.
    The Network settings window opens.
    2. Select the Surfaces tab.
    3. Click the Merge all points with identical co-ordinates button.
    All polygon points with the same co-ordinates are merged.

    15.10.8 Fuzzy alignment of surfaces


    You can perform a fuzzy alignment for all network surfaces. Then the points of a surface are
    moved, within a defined threshold, towards a reference area. This allows you to remove
    unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy alignment for surfaces (see "Importing Shapefiles" on page 2221).
    1. From the Network menu, choose Network settings.
    The Network settings window opens.

    PTVGROUP

    1053

    15.10.8 Fuzzy alignment of surfaces


    2. Select the Surfaces tab.
    3. Click the Fuzzy surface alignment button.
    The Fuzzy surface alignment window opens.
    4. Make the desired changes.
    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    5. Confirm with OK.


    The desired surfaces in the network are aligned.
    Editing surface set
    You can select surfaces for fuzzy alignment.
    1. In the Network menu, select the Network settings entry.
    2. Select the Surfaces tab.
    3. Click the Fuzzy surface alignment button.
    4. Click on the desired entry in the Surface set column.
    The Select surfaces window opens.
    5. Make the desired changes.

    1054

    PTVGROUP

    15.11 Managing transport systems, modes and demand segments


    Element

    Description

    Network object
    types
    Zones
    Main zones
    Main nodes
    Territories
    Points of Interest
    Toll systems

    All
    If this option has been selected, all surfaces of the network object
    type are aligned.
    None
    If this option has been selected, no surface of the network object
    type is aligned.
    Only active ones
    If this option is selected, only the surfaces of the active network
    objects of the desired network object type are aligned. If this
    option has been selected, the
    icon becomes available. You
    can activate network objects via the filter (see "Using filters to set
    network objects active or passive" on page 1008)
    Only passive
    If this option is selected, only the surfaces of the passive network
    objects of the desired network object type are aligned.
    If this option has been selected, the
    icon becomes available.
    You can set all network objects passive via the filter (see "Using
    filters to set network objects active or passive" on page 1008)

    15.11

    Managing transport systems, modes and demand segments


    Transport systems (TSys), modes, and demand segments (DSeg) serve to model supply and
    demand (see Fundamentals: Chpt. 3.1.1 , page 46).

    15.11.1 Managing transport systems


    Each transport system is allocated to a type of transport system (PrT, PuT, PuTWalk, PuTAux)
    (see Fundamentals: Chpt. 3.1.1.1 , page 46).
    15.11.1.1 Creating a transport system
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Transport systems tab.

    PTVGROUP

    1055

    15.11.1.1 Creating a transport system

    3. Click the Create button.


    The Create transport system window opens.
    4. Enter the desired data (see "Properties and options of transport systems" on page 1057).
    5. Confirm with OK.
    The Create mode and demand segment automatically window opens.

    Element

    Description

    Create mode and


    demand segment
    automatically

    If the option has been selected, in addition to the transport system, a mode and a demand segment will be created and allocated to the transport system.
    If the option has not been selected, only the transport system
    will be created. You can create a mode and a demand segment
    later on (see "Creating a mode" on page 1059 and "Creating a
    demand segment" on page 1061) and make the allocation.

    Code

    Code for the mode and the demand segment

    Name

    Name for the mode and the demand segment

    Note: If the transport system is of type PuT, PuTWalk or PuTAux, and at least one PuT
    mode already exists, the Permit TSys for modes window opens instead, in which
    you can allocate the transport system to an existing PuT mode.
    6. Confirm with OK.
    The newly created transport system is displayed in the list in the TSys/Modes/DSeg window.

    1056

    PTVGROUP

    15.11.1.2 Properties and options of transport systems


    7. Again, click OK to confirm.
    The transport system is created and, if you have selected the option, also the associated mode
    and demand segment.
    15.11.1.2 Properties and options of transport systems

    Element

    Description

    Code

    Code of the transport system

    Name

    Name of the transport system

    Type

    Type of the transport system (PrT, PuT, PuTWalk or PuTAux)

    Passenger car Only for transport systems of the type PrT


    units
    Number of PCUs per vehicle of PrT transport system. The value indicates
    the effect of the volume of a vehicle of a PrT transport system.
    Transfer network attributes from

    If you select this option, you can specify a reference transport system.
    Visum checks the network objects that have been allocated to the reference transport system via TSysSet. Then it allocates these network
    objects to the new transport system. Attributes which relate to the transport system are also transferred: for example VMax_PrTSys on a PrT link
    type, VDef_PuTSys on a PuT link type and T_PuTSys on a PuT link. That
    means: The link types, turns, connectors, etc. which are open for the reference transport system are also open for this transport system.
    All transport systems of the same type are available as reference transport system. Additionally, for the PuT transport system type, all transport
    systems of the PuT-Aux type are available. For PuT-Aux transport systems, any existing transport systems of the PuT type are available.

    Enter only link If you select this option, you can specify the link types that are open for
    attributes
    this transport system.

    PTVGROUP

    1057

    15.11.1.3 Editing the attribute values of transport systems


    Element

    Description
    Besides, for PrT you specify the maximum speed (VMax PrT) and for PuT
    the mean speed (v PuT) for the link types.

    Default values vMax PrT


    by link type
    Only for transport systems of the type PrT
    Maximum speed of the PrT transport system
    v PuT
    Only for transport systems of the types PuT, PuTWalk and PuTAux
    Mean speed of the PuT transport system
    permitted for link type
    Use the list to select the link types on which the transport system shall be
    permitted.
    15.11.1.3 Editing the attribute values of transport systems
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Transport systems tab.
    3. In the list of transport systems, select the transport system whose attribute values you want
    to edit.
    4. Click the Edit button.
    The Edit transport system window opens.
    5. Edit the values of the desired attributes (see "Properties and options of transport systems"
    on page 1057).
    Notes: If you want to edit the type of the transport system, you need to delete the transport system and create it again with the correct type (see "Creating a transport system" on page 1055).
    You can edit the speeds vMax-PrT and v-PuT per link type or global type via menu
    Network> Link types (see "Specifying link types" on page 1099).
    6. Confirm with OK.
    The attribute values of the transport system are changed.
    15.11.1.4 Deleting transport systems
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Transport systems tab.
    3. In the list, select the transport system that you want to delete.

    1058

    PTVGROUP

    15.11.2 Managing modes


    4. Click the Delete button.
    A query opens.
    Note: You can only delete public transport systems if they are not used by a line (see
    "Managing lines" on page 1291).
    5. Confirm the query with Yes.
    The transport system is deleted.

    15.11.2 Managing modes


    A mode comprises either one private transport system or several public transport systems (see
    Fundamentals: Chpt. 3.1.1.2 , page 48).
    15.11.2.1 Creating a mode
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Modes tab.

    3. Click the Create button.


    The Create mode window opens.
    4. Enter the desired data (see "Properties and options of modes" on page 1060).
    5. Confirm with OK.
    The mode is created.
    Note: You can automatically create modes when creating transport systems (see "Creating a transport system" on page 1055).

    PTVGROUP

    1059

    15.11.2.2 Properties and options of modes


    15.11.2.2 Properties and options of modes

    Element

    Description

    Code

    Code of the mode

    Name

    Name of the mode

    Type

    Type of transport system (PrT or PuT)

    Transport systems

    The list contains all transport systems of the selected type (PrT or
    PuT). Marked transport systems are allocated to the mode.
    Note
    To a mode of type PrT, you can allocate only one PrT transport system.

    Interchangeable

    If the option has been selected, the mode does not have to be
    used by all vehicle journeys of a chain, but can be replaced by a different mode.
    If the option has not been selected, the mode has to be used by all
    vehicle journeys of a chain.
    Note
    This option is only relevant for demand modeling with the EVA and
    the VISEM model (see "Modeling demand" on page 1606).

    15.11.2.3 Editing the attribute values of modes


    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Modes tab.
    3. In the list, select the mode whose attribute values you want to edit.
    4. Click the Edit button.
    The Edit mode window opens.
    5. Edit the values of the desired attributes (see "Properties and options of modes" on page
    1060).
    6. Confirm with OK.

    1060

    PTVGROUP

    15.11.2.4 Deleting modes


    The attribute values of the mode are changed.
    15.11.2.4 Deleting modes
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Modes tab.
    3. In the list, select the mode that you want to delete.
    4. Click the Delete button.
    A query opens.
    5. Confirm the query with Yes.
    The mode is deleted.
    Note: Together with the selected mode, all associated demand segments and demand
    descriptions are deleted.

    15.11.3 Managing demand segments


    A demand segment belongs to exactly one mode. Therefore, a demand segment is the link between transport supply and transport demand (see Fundamentals: Chpt. 3.1.1.3 , page 48).
    15.11.3.1 Creating a demand segment
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Demand segments tab.

    3. Click the Create button.


    The Create demand segment window opens.
    4. Enter the desired data (see "Properties and options of demand segments" on page 1062).
    5. Confirm with OK.
    The demand segment is created.
    PTVGROUP

    1061

    15.11.3.2 Properties and options of demand segments

    Note: You can automatically create demand segments when creating transport systems
    (see "Creating a transport system" on page 1055).
    15.11.3.2 Properties and options of demand segments

    Element

    Description

    Code

    Code of the demand segment

    Name

    Name of the demand segment

    Mode

    Use the drop-down list to allocate the demand segment to a mode.

    Occupancy rate

    Factor which is used to convert matrix values available as vehicle


    journeys into number of persons

    Projection factors For analysis period


    of assignment
    Factor which is used to convert the demand values of the assignment
    time intervals
    time interval to the analysis period (see "Projecting matrix values" on
    page 1800).
    For analysis horizon
    Factor which is used to convert the demand values of the assignment
    period to the analysis horizon (see "Projecting matrix values" on
    page 1800).
    15.11.3.3 Editing the attribute values of demand segments
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Demand segments tab.
    3. In the list, select the demand segment whose attribute values you want to edit.
    4. Click the Edit button.
    The Edit demand segment window opens.
    5. Edit the values of the desired attributes (see "Properties and options of demand segments"
    on page 1062).
    6. Confirm with OK.

    1062

    PTVGROUP

    15.11.3.4 Deleting demand segments


    The attribute values of the demand segment are changed.
    15.11.3.4 Deleting demand segments
    1. In the Demand menu, select the TSys/Modes/DSegs entry.
    The TSys/Modes/DSeg window opens.
    2. Select the Demand segments tab.
    3. In the list, select the demand segment that you want to delete.
    4. Click the Delete button.
    A query opens.
    5. Confirm the query with Yes.
    The demand segment is deleted.
    Note: If you delete a demand segment, all associating demand descriptions will also be
    deleted.

    15.12

    Managing nodes
    Nodes are point objects, which specify the location of intersections, merging links or points in
    road and rail network. They are start and end points of links. Via nodes, zones are connected
    to the network (see Fundamentals: Chpt. 3.1.2 , page 50).

    15.12.1 Creating a node


    You can create a node on a link or in any desired position in the network.
    Note: If you want to create a node on a link, you first need to split the link (see "Splitting a
    link" on page 1119).
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Nodes button.


    3. In the network, click the position where you want to insert the node.
    The Create node window opens.

    PTVGROUP

    1063

    15.12.1 Creating a node

    4. In the upper section of the Create node window, enter the desired data.
    Element

    Description

    Number

    Unique number of the node


    The nodes are numbered consecutively. You can overwrite the
    preset number with a number that does not yet exist in the network.
    Note
    If you edit the node number, existing assignment results will be
    deleted for all demand segments.

    Type

    The node type (0...99) categorizes the node for the definition of
    turn standards (see "Managing turns" on page 1090).
    Note
    The standard type is 0.

    Code

    Code of the node

    Name

    Name of the node

    5. In the Basis tab, enter the desired data.

    1064

    PTVGROUP

    15.12.1 Creating a node


    Element

    Description

    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object,
    you can also create user-defined attributes (see "Managing userdefined attributes" on page 973).

    Capacity PrT

    Allowed hourly PrT capacity of the node

    t0 PrT

    Private transport turning time in an unloaded network

    Main node number Display of the main node number if the node is allocated to a
    main node
    You can edit the allocation via the
    main nodes" on page 1169).

    button (see "Managing

    Position

    Coordinates of the node in the network


    The coordinates are assigned automatically according to the set
    coordinate system (see "Selecting a coordinate system" on page
    2207).
    Note
    You need Z-coordinates (height) for the 3D display in Vissim The
    elevation data are exported during an ANM export.

    Control

    Use the drop-down list to select the control type of the node:
    Unknown
    Uncontrolled
    Two-way stop
    Two-way yield
    Signalized
    All-way stop
    Roundabout

    Method for impedances at node

    Use this option to specify that the standard method for calculating
    the node impedances shall not be used, but the method that is set
    directly for the node. If the option has been selected, you can pick
    the desired method in the list.
    You can specify the standard method under the Calculate>
    General procedure settings> entry PrT settings> Node impedances menu (see "Definition and application of volume-delay
    functions" on page 1892 and "Calculating node impedances
    using Node impedance calculation (ICA)" on page 1914).

    6. Make the desired changes in the Time-varying attributes tab (see "Entering and editing
    time-varying data for time-varying attributes" on page 980).
    7. Confirm with OK.
    The node is inserted in the network.
    PTVGROUP

    1065

    15.12.2 Properties and options of nodes

    15.12.2 Properties and options of nodes


    You can edit all nodes and their attributes in the junction editor. The Junction editor opens if
    you double-click the desired node (see "Editing a node in the Junction editor" on page 1441).

    15.12.3 Finding a node


    How to find nodes is described for all network objects (see "Finding network objects in the network" on page 999).

    15.12.4 Selecting nodes


    There are several ways to select nodes in order to edit them in another step.
    Marking nodes
    Setting nodes active/passive
    15.12.4.1 Marking nodes
    1. In the Network window, click the

    Edit mode window.

    2. Click the Nodes button.


    3. In the network, click the node that you want to mark.
    The node is marked.
    4. If you want to mark additional nodes, press the C TRL key and keep it pressed.
    5. One by one, click the nodes that you want to mark.
    The nodes are marked.

    Note: If in the toolbar the


    Click only active objects icon is activated, you can only
    mark active nodes with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a node by searching for it (see "Finding a node" on page
    1066) or select the respective row in the node list (see "Selecting list sections" on page
    2319).
    15.12.4.2 Setting nodes active/passive
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.12.5 Editing the attribute values of nodes


    You can edit the attribute values of one node, all marked nodes or all (active) nodes.

    1066

    PTVGROUP

    15.12.5.1 Editing the attribute values of a node


    15.12.5.1 Editing the attribute values of a node
    You can edit the attribute values of single nodes in the junction editor or edit the attribute
    values of all or all active nodes (see "Using the Junction editor" on page 1435).
    15.12.5.2 Editing the attribute values of marked nodes
    1. Mark the desired nodes whose attribute values you want to edit (see "Selecting nodes" on
    page 1066).
    2. Press the ENTER key.
    The Multi-edit nodes: <number> objects window opens.
    Tip: You can also call the Multi-edit nodes: <Number> objects window via the context menu > entry Edit or double-click the last node to be marked.
    3. Edit the values of the desired attributes (see "Editing node attributes in the list view" on
    page 1443 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.12.5.3 Editing the attribute values of all or all active nodes
    Note: If there are no passive nodes in the network, all nodes are edited. Markings of
    nodes are ignored.
    1. If required, set the nodes active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit nodes window opens.
    4. Select whether you want to edit the attribute values of all nodes or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active nodes will be taken
    into account.

    5. Select the Formula tab.

    PTVGROUP

    1067

    15.12.5.4 Displaying the attribute values of a node in a column chart


    6. Edit the values of the desired attributes (see "Editing node attributes in the list view" on
    page 1443 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.12.5.4 Displaying the attribute values of a node in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.12.6 Shifting nodes


    1. In the Network window, click the

    Edit mode window.

    2. Click the Nodes button.


    3. In the network, click the node that you want to shift and hold down the left mouse button.
    4. Drag the node to the new position and release the mouse button.
    The Shift node window opens if the node is neither isolated nor without PuT objects.
    Notes: If you press the ESC key while dragging, you can cancel the action and the
    node is reset to its original position.

    Notes: The Shift node window is only displayed, if at least one link begins at the node
    or if a stop or stop area is allocated to the node. Otherwise the node is simply shifted.
    If you move the node to the position of another node, Visum tries to merge the nodes.
    In this case, the Merge/shift node(s) window opens (see "Merging nodes" on page
    1069).
    5. Select the desired options.

    1068

    Element

    Description

    Adjust link length


    to new polygon
    length

    If the option has been selected, the resulting direct distance of


    links from/to the shifted node is calculated automatically and
    saved as link length.
    Note
    The option is disabled if the node is isolated.

    Shift also stop

    If the option has been selected, stop areas and stops allocated to

    PTVGROUP

    15.12.7 Merging nodes


    Element

    Description

    (area)

    the node get the same co-ordinates as the shifted node.


    Note
    The option is disabled if none of these network objects are allocated to the node.

    6. Confirm with OK.


    The node is shifted.
    Tip: You can also edit the node coordinates in the junction editor (see "Editing a node in
    the Junction editor" on page 1441).

    15.12.7 Merging nodes


    Notes: If parallel links would be created, you cannot merge the respective nodes.
    1. In the Network window, click the

    Edit mode window.

    2. Click the Nodes button.


    3. In the network, click the node that you want to merge and hold down the left mouse button.
    4. Drag the node to the position of another node and release the mouse button.
    The Merge/shift node(s) window opens.

    Note: If the nodes cannot be merged, this window contains a corresponding message. The node will be shifted instead (see "Shifting nodes" on page 1068).
    5. Select the desired options.
    Element

    Description

    Merge nodes

    If the option has been selected, the nodes are merged.


    If the option has not been selected, the node is shifted to the
    new position without the nodes being merged.

    Use data of which Select the desired node.

    PTVGROUP

    1069

    15.12.8 Specifying major flows at nodes


    Element

    Description

    node?

    The node number and all other attribute values of the desired
    node and its stop points are used as values for the merged node
    and stop point.

    Recalculate link
    lengths

    If the option has been selected, all link lengths are recalculated.

    Shift also stop


    (area)

    If the option has been selected, the stop and the stop area of the
    shifted node will also get the new co-ordinates.
    Note
    The option is disabled if none of these network objects are allocated to the node.

    Note: If you merge the nodes, the current assignment result is deleted.
    6. Confirm with OK.
    The nodes and, if applicable, their stop points are merged. Depending on the setting, stops
    and stop points will also be shifted.

    15.12.8 Specifying major flows at nodes


    The links of the node with the top-ranking link types turn into major flows (see "Specifying link
    types" on page 1099).
    1. Select the nodes, whose major flows you want to specify, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Major flows entry.
    The Multi-edit nodes window opens.
    Tip: If the network object type Nodes has been selected, you can also call the Multiedit Nodes window via the Edit> Major flows menu.
    4. Make sure that the Special functions tab has been selected and the Major flows entry in
    the drop-down list.
    5. Decide whether you want to specify the major flows of all nodes or all active nodes.

    1070

    PTVGROUP

    15.12.9 Setting the polygon allocation of nodes


    Element

    Description

    Only active ones

    If the option has been selected, only active nodes will be taken
    into account.

    6. Click the Specify major flows automatically button.


    A query opens.
    7. Confirm with OK.
    The major flows are specified.
    8. Click the Close button.

    15.12.9 Setting the polygon allocation of nodes


    Prerequisite is that there are nodes within a polygon (territory, zone or main zone).
    You can specify that a selected attribute receives the number of the territory, zone, or main
    zone in which the node lies.
    Example
    Ten nodes lie within the territory number 738. You can specify that all ten nodes receive the
    number 738 as Add Value 1. In the node list, you can then see immediately in which territory
    the nodes lie.
    1. If required, set the nodes active, whose allocation you want to set, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter (see "Using filters to set network objects active or passive" on page 1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Set polygon allocation entry.
    The Multi-edit nodes window opens.
    Tip: If the network object type Nodes has been selected, you can also call the Multiedit nodes window via the Edit> Set polygon allocation menu.
    4. Make sure that the Special functions tab and the Set polygon allocation entry in the dropdown list have been selected.
    5. Make the desired changes.

    PTVGROUP

    1071

    15.12.10 Updating impedances at nodes


    Element

    Description

    Only active ones

    If the option has been selected, only active nodes will be taken
    into account.

    Object

    In the drop-down list, you can select the type of network object
    whose number you want to use as attribute value.

    Attribute to be set Use the drop-down list to select an attribute which shall store the
    number of the selected object.
    6. Click the Set button.
    The nodes store the number as attribute value.
    7. Click the Close button.

    15.12.10 Updating impedances at nodes


    For example, you can use this feature to test the node performance. It is only effective for
    nodes for which the impedance method ICA (Intersection Capacity Analysis) is specified (see
    "Calculating node impedances" on page 1911).
    If you want to update the impedance of a node that has an associated signal control, you can
    specify that the signal cycle and split optimization is carried out for the signal control at the
    same time. The optimization will then be done automatically for all nodes or main nodes of the
    signal control while the impedances are updated.
    1. Select the nodes whose impedances you want to update. To do this, use
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Update node impedances entry.
    The Multi-edit nodes window opens.
    4. Make sure that the Special functions tab is selected and the Update impedances at node/signal cycle and split optimization entry is displayed in the drop-down list.
    5. Specify whether you want to execute the function for all nodes or only for active nodes.

    1072

    Element

    Description

    Only active ones

    If the option has been selected, only active nodes will be taken
    into account.

    PTVGROUP

    15.12.11 Updating the impedances at all nodes and main nodes


    6. If you want to execute the signal cycle and split optimization for nodes with a signal control,
    select the Signal cycle and split optimization option.
    Element

    Description

    Signal cycle and


    green time optimization

    If this option has been selected, Visum checks for all nodes with a
    signal control which optimization method has been specified for
    the signal control (see "Properties and options of signal controls"
    on page 1465). Dependent on the specified optimization method,
    no optimization, only the signal split optimization or the signal
    cycle and split optimization is carried out.

    7. Click the Update impedances at node/signal cycle and split optimization button.
    A query opens.
    8. Confirm the query with OK.
    The impedances are updated. If the Signal cycle and split optimization option has been selected, for nodes with a signal control either no optimization, only the signal split optimization, or
    the signal cycle and split optimization is carried out. This depends on the optimization method
    specified for the signal control.
    Note: If a node is allocated to a signal control, impedances and optimizations are always
    calculated simultaneously for all nodes and main nodes that are allocated to this signal
    control.
    You can also execute the signal cycle and split optimization for single or all active nodes
    (see "Optimizing signal cycles and split of a single signal control" on page 1501 and
    "Optimizing signal cycle and split times for active nodes" on page 1921).

    15.12.11 Updating the impedances at all nodes and main nodes


    You can calculate the current impedances for all nodes or main nodes. The general and specific settings at the nodes determine how the impedances will be calculated (see "Calculating
    node impedances" on page 1911).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the desired position of the procedure sequence, insert the Update impedances at node
    procedure of the Assignments category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Start the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The impedances of the nodes and main nodes are updated.

    PTVGROUP

    1073

    15.12.12 Setting coordination groups for signal controls

    15.12.12 Setting coordination groups for signal controls


    With this functionality, you can allocate the number of a coordination group to the signal control of selected nodes.
    1. Select the nodes, whose SCs you want to allocate numbers to, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Set SC coordination groups entry.
    The Multi-edit nodes window opens.
    Tip: If the network object type Nodes has been selected, you can also call the Multiedit nodes window via the Edit > Set coordination groups for SC menu.
    4. Make sure that the Special functions tab has been selected and the Set coordination
    groups for SC entry in the drop-down list.
    5. Select whether you want to edit the SCs of all nodes or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active nodes will be taken
    into account.

    6. Make the desired changes.

    1074

    Element

    Description

    Coordination
    group

    If the option has been selected, you can allocate a coordination


    group to the SCJ of all selected nodes. In the drop-down list,
    select the desired coordination group.
    Tip
    You can create and edit signal coordination groups in menu
    Network> Signal coordination groups. (see "Managing signal
    coordination groups" on page 1497).

    Node attribute

    If the option has been selected, the value of the selected attribute
    will be allocated to all signal coordination group numbers.
    Tip
    You can create user-defined attributes for this purpose (see
    "Managing user-defined attributes" on page 973).

    PTVGROUP

    15.12.13 Resetting the lane data of nodes


    7. Click the Set button.
    The selected coordination group number or the value of the selected attribute is allocated
    to all selected signal controls.
    8. Click the Close button.
    Tips: You can also edit the Coordination group number attribute in the Signal control>
    SC list for the desired signal control.

    15.12.13 Resetting the lane data of nodes


    Note: You can edit the lanes of individual nodes in the junction editor (see "Using the
    Junction editor" on page 1435).
    1. If required, set the nodes active whose lane data you want to reset to the standard values,
    via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Lane definition entry.
    The Multi-edit nodes window opens.
    Tip: If the network object type Nodes has been selected, you can also call the Multiedit nodes window via the Edit> Lane definition menu.
    4. Make sure that the Special functions tab has been selected and the Lane definition entry
    in the drop-down list.
    5. Specify whether you want to reset the lane data of all nodes or all active nodes.
    Element

    Description

    Only active ones

    If the option has been selected, only active nodes will be taken
    into account.

    6. Click the Reset lane data button.


    A query opens.
    7. Confirm the query with OK.
    The lane data are reset.
    8. Click the Close button.
    PTVGROUP

    1075

    15.12.14 Aggregating isolated nodes

    15.12.14 Aggregating isolated nodes


    Note: You can only execute this operation if there are isolated nodes in the network, for
    example when reading external network data additively (see "Reading network data additionally" on page 851).
    The aim is to automatically integrate isolated nodes into an existing network. You can insert
    isolated nodes as stop points in the network, even if no stop points were assigned to the
    nodes before. This facilitates the integration of stop data into an existing private transport network model.
    The integration sequence is based on the distances between the isolated nodes in the network. The process begins with the node that is located closest to the basic network. If required,
    the distances are determined anew after each integration step. Then, the next closest isolated
    node is integrated and so on.
    It ends when all isolated nodes have been integrated or when the network lies beyond the
    snap radius of all remaining isolated nodes. For stop points, the minimum distance between
    neighboring stop points on links is regarded. Below the minimum distance, a node carrying a
    stop point is inserted.
    It is ruled out that two initially isolated nodes are merged in the process, as data would be lost
    otherwise. This situation could occur if the first node, after it has been integrated, turns into the
    network object nearest to the second one. The second node would not be merged with the first
    one then, but would either remain isolated or be integrated into the network in a different way,
    using the following trick. This trick only works if the first integrated node has one or two legs following integration. In this case, an incident link of the node is split and the second isolated
    node is used as an intermediate point.
    The isolated nodes retain their attributes in any case even if merged with network nodes
    which would then lose all their attributes instead.
    Note: The coordinates are an exception to this. You can specify whether the coordinates
    of the existing network or the coordinates of the isolated nodes shall be used.
    1. Select the nodes, which you want to integrate, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    2. In the Network window, right-click the Nodes button.
    A context menu opens.
    3. Select the Aggregate isolated nodes entry.
    The Aggregation of isolated nodes window opens.

    1076

    PTVGROUP

    15.12.14 Aggregating isolated nodes

    4. Make the desired changes.


    Scope
    Nodes to be integrated (origin)
    Attribute

    Description

    Integrate only active


    nodes

    If the option has been selected, only active isolated nodes


    are integrated into the network.
    If the option has not been selected, all isolated nodes are
    integrated into the network.
    Note
    The active/passive attribute is not relevant to existing network nodes.

    Snap radius

    The snap radius determines the area surrounding an isolated node, within which network objects will be searched. If
    neither network nodes nor links are located within this area,
    the node in question remains isolated. As with link lengths,
    the snap radius takes the scale of the network into account.
    The default value is 100.

    Tolerance range for


    merging

    If there are any nodes within the tolerance range that are
    contained in the snap radius (default=5m), the node to be
    integrated will be merged with the nearest node within
    reach. This is done, even if a link is positioned closer to that
    node.

    PTVGROUP

    1077

    15.12.14 Aggregating isolated nodes


    Scope
    Network integration (destination)
    Attribute

    Description

    Integrating nodes as
    existing

    If this option has been selected, isolated nodes are inserted


    with an assigned stop point only if they carried a stop point
    before the integration.

    Always as node with


    stop point (standard)

    If this option has been selected, isolated nodes are always


    inserted with a stop point. The link is split and the isolated
    node inserted where the link is split.
    Note
    The Permit creating on links must be selected.

    Always just as stop


    point
    (node attributes are not
    used)

    If this option has been selected, the isolated node is inserted


    as a stop point which is placed either on a network node or
    on a network link. Links are not split however.
    Note
    If the Permit creating on links option has been selected,
    undirected link stop points might be inserted.

    Permit creating on
    links

    If this option has not been selected, the network integration is performed exclusively by merging nodes. This
    ensures that, when determining the next network object, only
    nodes are considered. Usually, more isolated nodes remain
    as a result.
    If this option has been selected, stop points are created
    the link without the link being split. Stop points created in this
    way are undirected and therefore serve both directions of the
    link. If a node is merged with an already existing directed
    stop point, the stop point will be undirected after the aggregation.

    Create only on active


    network links

    1078

    If this option has been selected, objects will be inserted on


    active links only. Passive links are ignored.

    PTVGROUP

    15.12.14 Aggregating isolated nodes


    Scope
    Network integration (destination)
    Attribute

    Description

    Merge only active network nodes

    If this option has been selected, isolated nodes will only be


    merged with active network nodes.
    Passive network nodes are ignored.

    Permit merging with


    stop points

    If this option has been selected, an isolated node can be


    merged with a stop point which already exists in the network,
    as long as it lies within the user-defined snap radius and the
    tolerance range.
    If this option has not selected, an isolated node cannot be
    merged with an already existing stop point. This might make
    sense if you want to import a large number of nodes as stop
    points, because it is usually undesirable to merge an existing stop point with another object that has just been inserted. The new node remains isolated and needs to be
    handled separately, where applicable.
    Exception
    Since the Aggregate isolated nodes procedure prevents
    that two initially isolated nodes are merged in the course of
    the operation, just one node will be integrated into the network, if at all possible, if the option has not been selected.
    Further nodes remain isolated or split an incident link, if possible.
    Note
    The log file (see "Using protocol files" on page 876) also contains failed integrations. If integration fails because it is not
    allowed to merge nodes with stop points, a corresponding
    entry with the operation number "4" is added.

    PTVGROUP

    1079

    15.12.14 Aggregating isolated nodes


    Scope
    Integration parameters

    1080

    Attribute

    Description

    Use coordinates of

    Use this option to specify whether the coordinates of the isolated nodes or of the existing network nodes shall be used.
    Nodes and links of the network
    If this option has been selected, the isolated nodes slide into
    the network.
    Isolated nodes
    If this option has been selected, nodes and links (intermediate points) move towards the initially isolated nodes. In
    this case, a few things should be noted: Due to the gradual
    changes to the network topology, it can happen that a different network object is allocated to the isolated nodes that
    have not yet been integrated (which, as a result, changes
    their distance to the existing network) than at the start. This
    can result in the existing network "going beyond" the snap
    radius of an isolated node, or that it "moves into" the snap
    radius not until the course of the process. The basis for each
    subsequent step in the integration process is always the
    shortest distance of the isolated nodes to the network that is
    currently valid.
    Adapt length of link to linear distance
    If the option has not been selected, the link lengths are
    not recalculated.

    Use stop allocation of

    Allocations of stop points to stop areas should remain untouched by the integration of isolated nodes. If two stop points
    are merged however, their aggregate can refer to only one of
    the previously allocated stop areas.
    Use the options to specify which stop area shall be used.
    Nodes of the network
    Standard setting
    Isolated nodes
    You can delete stop areas and stop points which are separated from the network as a result of this operation. You can,
    for example, filter isolated objects via the attributes
    CStopArea::NumStopPoints and CStop::NumStopAreas
    and delete them via Multi-delete.

    PTVGROUP

    15.12.14 Aggregating isolated nodes


    Section Operations
    Attribute

    Description

    Protocol

    The log file provides a detailed report on the individual steps


    of the integration process. Each line describes the successful or failed (ID = 0) integration of an individual isolated
    node.
    None
    No protocol will be saved.
    In file
    Specify a directory to which the protocol shall be saved (see
    "Description of the flow trace" on page 1082).

    Clear Undo stack to


    save RAM

    If this option has been selected, no operations are saved.

    Notes on the integration logic


    During the integration, the attributes (especially IDs) of the isolated nodes (and their stop
    points) are always transferred to the network. Only for co-ordinates and the stop hierarchy,
    there are special choice options. If a stop point is generated from a node, the code and the
    name of the stop point is the same as the code and the name of the node. However, if two stop
    points are merged, no transport system will be blocked that was permitted to use the stop point
    in the network before.
    The objects contained in the network are only overwritten despite transferring the data, rather
    than being deleted in terms of the object identity; in other words, dependent data (for example
    line routes that use stop points) are not lost.
    Stops and stop areas which exist at isolated nodes, might also be isolated after the integration
    process, yet are not deleted automatically. Their coordinates are never adjusted.
    Case 1: Merging isolated nodes with network nodes
    Note: Compared to Visum8, there are now more constellations when integrating isolated
    nodes. The minimum distance of an isolated node to the network still determines which
    of the following cases results.
    Merging an isolated node with a network node leads to one of four scenarios, as both, the isolated node and the network node, can but do not necessarily carry a stop point. The Use coordinates of option clearly determines, which network object "wins". The transport system set of
    an existing stop point is never reduced.
    Case 2: Creating on link polygon
    If the Permit creating on links option has been selected and a point on a link polygon which
    is neither the From node nor the To node of the link, is the network point located nearest to the
    node, the isolated node will be inserted on the link polygon.

    PTVGROUP

    1081

    15.12.14 Aggregating isolated nodes


    The link is either split and a new node (possibly with stop point) is inserted, or a stop point is
    placed on the link.
    Please note: Since there is an internal minimum distance (= link length/1000) between adjacent stop points on a link, the insertion of a stop point might fail if the value falls below the limiting value. In this case, a node with a stop point on the link is created, even if option Always
    just as stop point has been selected. This is possible as there is no internal minimum
    distance between stop points and link nodes.
    Case 3: Merging with link stop point
    In rare cases, a stop point on a link might be the network point located nearest to the isolated
    node. This is a combination of case 1 and case 2: a merge operation according to case 1 is
    performed on a link as in case 2, which is then split (only if a node shall be inserted). As in
    case 1, the transport system set of existing stop points is not reduced. The minimum distance
    problem cannot occur in this context.
    Description of the flow trace
    The format used is:
    IsolNodeNo;Operation;LinkNoOld;LinkNoNew1;LinkNoNew2;
    lNodeNoOld;Distance

    Each operation is marked by a number 0 to 4 with the following meaning:


    0

    Integration is not possible.

    The next network object is a link:


    split link (attributes 3, 4 and 5 written).

    The next network object is a node: Node is merged (attribute 6 is written).

    The next network object is a node (attribute 6) which cannot be merged, because
    it was itself initially isolated and has at least three legs. An incident network link is
    split instead (attributes 3, 4, and 5).

    The node remains isolated as it is not permitted to merge stop points (see "Exception" on page 1079).

    If the integration fails (operation ID = 0) the following distinction is made:


    If the integration failed for the reason that an isolated node could not be merged with a
    (multiple-leg) node because it was originally isolated, at least the distance is known and
    can be saved to file.
    If the existing network lies beyond the snap radius of the isolated node however, the exact
    distance is not known and 1 is saved as "distance".

    1082

    IsolNodeNo

    Number of the isolated node

    Operation

    ID of the operation performed (see above)

    LinkNoOld

    Number of the split link

    LinkNoNew1

    Number of the first link generated by link splitting (identical to

    PTVGROUP

    15.12.15 Deleting nodes


    number of the split link)
    5

    LinkNoNew2

    Number of the second link generated by link splitting (new maximum link number)

    NodeNoOld

    Number of the merged network node

    Distance

    Distance of the isolated node to the network at the time of integration

    Attributes 1, 2 and 7 are always saved, attributes 3 to 6 depending on the operation performed.

    15.12.15 Deleting nodes


    There are several ways to delete nodes.
    15.12.15.1 Deleting a node
    Notes: If a stop point is located on the node that you want to delete, the stop point will
    also be deleted.
    If the stop point is served by a PuT line, this line as well as its line routes, time profiles
    and vehicle journeys will also be deleted. Nodes with two legs are an exception to this
    (see "Exception: Deleting nodes with two legs and no stop point and connecting the
    links" on page 1084).
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Nodes button.


    3. In the network, click the node that you want to delete.
    4. Press the DEL key.
    Tip: You can also delete the marked node via the context menu> entry Delete.
    A window opens.
    Note: You can also delete associated stop areas, if you select the Delete also stop
    (area) option. The associated stop is only deleted if it does not have any further stop
    areas.
    5. Confirm with OK.
    A query opens.
    6. Click Yes to confirm.
    The node is deleted.

    PTVGROUP

    1083

    15.12.15.1 Deleting a node


    Exception: Deleting nodes with two legs and no stop point and connecting the links
    If you delete a node without stop point, you can specify that the two links of the node will be
    connected.
    Note: You cannot connect the links if there is already a link between the adjacent nodes
    of the node that you want to delete. In this case, the connected link would coincide with
    the link of the adjacent nodes. However, in Visum, identical links are not permitted.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Nodes button.


    3. In the network, click the node that you want to delete.
    The node is marked.
    4. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked node via the context menu> entry Delete.
    5. Click the Connect button.
    The Connect links window opens.
    6. Enter a new link number in the input field, if required.
    7. Select the link of which all other attributes shall be used.
    8. Confirm with OK.
    The node is deleted and the links are connected.
    Note: For the new link, Visum uses the transport systems which were permitted on both
    connected links.
    Exception: Deleting two-legged node with a stop point
    If you delete two-legged nodes with a stop point, a new window opens in which you can specify, if and how the two links of the node will be connected.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Nodes button.


    3. In the network, click the node that you want to delete.
    The node is marked.
    4. Press the DEL key.

    1084

    PTVGROUP

    15.12.15.2 Deleting several marked nodes

    5. Select the desired options.


    Element

    Description

    Delete links

    If the option has been selected, the links will be deleted.

    Connect links and If the option has been selected, the links will be connected and
    delete stop point
    the stop point deleted.
    Connect links and If the option has been selected, the links will be connected and
    set stop point on the stop point will be located on the stop point.
    link
    Delete also stop
    (area)

    If the option has been selected, associated stop areas will also be
    deleted.
    Note
    The associated stop is only deleted, if it does not have any further
    stop areas.

    6. Confirm with OK.


    A query opens.
    7. Confirm with OK.
    If you connect the links, window Connect links opens.
    8. Enter a new link number in the input field, if required.
    9. Select the link of which all other attributes shall be used.
    10. Confirm with OK.
    The node is deleted. The associated links are connected or deleted, depending on the selected option.
    15.12.15.2 Deleting several marked nodes
    1. Mark the nodes that you want to delete (see "Selecting nodes" on page 1066).
    The selected nodes are marked.
    2. Press the DEL key.
    The Delete multiple nodes window opens.
    Tip: You can also delete the marked node via the context menu> entry Delete.
    PTVGROUP

    1085

    15.12.15.2 Deleting several marked nodes

    The issued statistics categorize all nodes to be deleted. It offers special options for the following node categories:
    Node category

    Option

    Nodes are connec- Delete also connected nodes


    ted
    If the option has been selected, connected nodes will be deleted.

    1086

    Isolated nodes

    Delete
    If the option has been selected, isolated nodes will be deleted.

    Nodes with 1 leg

    Delete
    If the option has been selected, nodes with one leg will be deleted, including the link.

    Nodes with 2 legs

    Delete
    If the option has been selected, nodes with two legs will be deleted.
    Use the following options to specify how to handle the associated
    links (see "Exception: Deleting nodes with two legs and no stop
    point and connecting the links" on page 1084).
    Delete links
    If the option has been selected, links to and from the deleted
    node will be deleted, including all possibly existing stop
    points.
    Connect links and delete stop
    If this option is selected, the links are connected and the stop
    is deleted.
    If the option has been selected, the Delete nodes with 2
    legs, connect links window opens afterwards, in which you
    can select attributes which must coincide for the links to be
    connected. If the selected attributes do not coincide, the
    nodes with deviating attribute values will not be deleted.

    PTVGROUP

    15.12.15.2 Deleting several marked nodes


    Node category

    Option
    Connect links and set stop point on link
    If this option is selected, the links are connected and the stop
    point is set on the link.
    Then the Delete nodes with 2 legs, connect links window
    opens, in which you can select attributes that must coincide
    for link connection. If the selected attributes do not coincide,
    the nodes with deviating attribute values will not be deleted.
    Connect links only if no stop point is located at the node
    If this option is selected, the links are only connected, if there
    is no stop point at the respective node
    Then the window Delete nodes with 2 legs, connect links
    opens, in which you can select attributes that must coincide
    for link connection. If the selected attributes do not coincide,
    the nodes with deviating attribute values will not be deleted.

    Nodes with multiple legs

    Delete
    If the option has been selected, nodes with multiple legs will be
    deleted, including the links.

    Delete also stop


    (area)

    If the option has been selected, possibly existing stop areas at


    nodes will also be deleted.

    3. Select the node categories, which you want to delete, and the associated options.
    Note: In large networks, select option Clear Undo stack to save RAM, if required.
    4. Confirm with OK.
    A query opens.
    5. Select which nodes you want to delete.
    Element

    Description

    Yes

    The node listed in the window will be deleted, and also all network objects with a reference to the node.

    Yes for all

    All remaining marked nodes will be deleted, and also the network
    objects with a reference to the node.

    No

    Neither the node listed in the window will be deleted, nor the network objects with a reference to the node.

    No for all

    Neither of the remaining marked nodes will be deleted, nor the


    network objects with a reference to the node.

    PTVGROUP

    1087

    15.12.15.3 Deleting active nodes


    Notes: If you click the Yes or No buttons, the query is displayed for the next node number.
    With the Yes for all or No for all buttons, you only regard the remaining nodes, for
    which neither Yes nor No has been clicked.
    The confirmed marked nodes are deleted.
    15.12.15.3 Deleting active nodes
    1. Select the nodes, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected nodes are active.
    2. In the Network window, right-click the Nodes button.
    The Nodes context menu opens.
    3. Select the Multi-delete entry.
    The Delete multiple nodes window opens.
    The issued statistics categorize all nodes to be deleted. It offers special options for the following node categories:
    Node category

    Option

    Nodes are connec- Delete also connected nodes


    ted
    If the option has been selected, connected nodes will be deleted.

    1088

    Isolated nodes

    Delete
    If the option has been selected, isolated nodes will be deleted.

    Nodes with 1 leg

    Delete
    If the option has been selected, nodes with one leg will be deleted, including the link.

    Nodes with 2 legs

    Delete
    If the option has been selected, nodes with two legs will be deleted.
    Use the following options to specify how to handle the associated
    links (see "Exception: Deleting nodes with two legs and no stop
    point and connecting the links" on page 1084):
    Delete links
    Links to and from the deleted node are deleted, including any
    stop points.
    Connect links and delete stop point
    The links are connected and the stop point is deleted.

    PTVGROUP

    15.12.15.3 Deleting active nodes


    Node category

    Option
    If this option is selected, the window Delete nodes with 2
    legs, connect links opens, in which you can select attributes
    that must coincide for connection of the links. If the selected
    attributes do not coincide, the nodes with deviating attribute
    values will not be deleted.
    Connect links and set stop point on link
    If this option is selected, the links are connected and the stop
    point is set on the link.
    Then the Delete nodes with 2 legs, connect links window
    opens, in which you can select attributes that must coincide
    for link connection. If the selected attributes do not coincide,
    the nodes with deviating attribute values will not be deleted.
    Connect links only if no stop point is located at the node
    If this option is selected, the links are only connected, if there
    is no stop point at the respective node
    Then the window Delete nodes with 2 legs, connect links
    opens, in which you can select attributes that must coincide
    for link connection. If the selected attributes do not coincide,
    the nodes with deviating attribute values will not be deleted.

    Nodes with multiple legs

    Delete
    If the option has been selected, nodes with multiple legs will be
    deleted, including the links.

    Delete also stop


    (area)

    If the option has been selected, possibly existing stop areas at


    nodes will also be deleted.

    4. Select the node categories, which you want to delete, and the associated options.
    Note: In large networks, select option Clear Undo stack to save RAM, if required.
    5. Confirm with OK.
    A query opens.
    6. Select which nodes you want to delete.
    Element

    Description

    Yes

    The node listed in the window will be deleted, and also all network objects with a reference to the node.

    Yes for all

    All remaining active nodes will be deleted, and also the network
    objects with a reference to the node.

    PTVGROUP

    1089

    15.13 Managing turns


    Element

    Description

    No

    Neither the node listed in the window will be deleted, nor the network objects with a reference to the node.

    No for all

    Neither of the remaining active nodes will be deleted, nor the network objects with a reference to the node.

    Notes: If you click the Yes or No buttons, the query is displayed for the next node number.
    With the Yes for all or No for all buttons, you only regard the remaining nodes, for
    which neither Yes nor No has been clicked.
    The confirmed active nodes are deleted.

    15.13

    Managing turns
    Turns specify which movements are permitted at a node, that is, whether turning at a node
    from one link to another link is permitted. 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.

    15.13.1 Managing turn standards


    Turn standards are templates based on which you can allocate default values to the attributes
    Time penalty, Capacity PrT and Is change of running direction for newly created turns (see
    Fundamentals: Chpt. 3.1.2 , page 50).
    15.13.1.1 Creating turn standards
    You can create new turn standards.
    1. In the Network menu, select the Turn standards entry.
    The Turn standards window opens. All existing turn standards are displayed.

    1090

    PTVGROUP

    15.13.1.1 Creating turn standards

    Note: In the list, you can shift the selected entry if you click the
    and
    buttons.
    The IDs of the shifted objects change automatically. The turn standard with the highest ID has the highest priority. As soon as a turn is inserted, Visum checks which turn
    standard applies, beginning with the highest ID. The values of these turn standards
    are allocated to the new turn.
    2. Click the

    Create button.

    The Create turn standard window opens.

    3. Make the desired changes.


    Element

    Description

    ID

    Specify a unique ID.


    Note
    Turn standards are numbered consecutively. The preset number
    can be overwritten by a number which has not yet been assigned
    in the network.

    Turn type

    Turn type of the turns for which the attribute values shall be used
    Notes
    The values range from 0-9 or ?. The signs have the following meaning:
    0=not specified
    1=right
    2=straight
    3=left
    4=U-turn
    5-9=free for the illustration of special cases
    ?=any turn type

    Flow hierarchy

    Flow hierarchy of the turns for which the attribute values shall be

    PTVGROUP

    1091

    15.13.1.2 Editing turn standards


    Element

    Description
    used
    Notes
    The value range is ++, +-, --, -+. The signs have the following meaning:
    ++ = major flow into major flow
    +- = major flow into minor flow
    -+ = minor flow into major flow
    -- = minor flow into minor flow
    The ? can be used as wildcard for any sign.

    Node type

    Node type of the turns for which the attribute values shall be used
    Note
    The value range is 0 to 99.
    The ? can be used as wildcard for any sign.

    Time penalty

    Time penalty for a turning movement in seconds


    Standard value that is used automatically for new turns which
    have the properties specified above

    Capacity PrT

    PrT capacity
    Standard value that is used automatically for new turns which
    have the properties specified above

    Is change of running direction

    If the option has been selected, the turn allocated from this turn
    standard represents a change of direction.
    Standard value that is used automatically for new turns which
    have the properties specified above

    4. Confirm with OK.


    The turn standard is created.
    15.13.1.2 Editing turn standards
    You can edit the turn standards.
    1. In the Network menu, select the Turn standards entry.
    The Turn standards window opens.
    2. From the drop-down list, select the desired turn standard.
    3. Click the

    Edit button.

    The Edit turn standard window opens.


    4. Make the desired settings (see "Creating turn standards" on page 1090).
    5. Confirm with OK.

    1092

    PTVGROUP

    15.13.1.3 Deleting turn standards


    The changes are applied.
    15.13.1.3 Deleting turn standards
    You can delete turn standards.
    1. In the Network menu, select the Turn standards entry.
    The Turn standards window opens.
    2. From the drop-down list, select the desired turn standard.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.

    3. Click the

    Delete button.

    4. Confirm with OK.


    The selected turn standard is deleted.

    15.13.2 Creating turns


    Together with a new link, all possible turns are inserted at the From node and the To node of
    the link (see "Creating a link" on page 1105). You can thus not insert turns manually, but edit
    them only. Main turns are edited in the junction editor (see "Editing turns in the Junction editor"
    on page 1450).
    The newly created turns have preset attribute values that you can specify in the turn standards
    (see "Managing turn standards" on page 1090). By default, they are open to all transport systems which are permitted both on the From link and on the To link (see Fundamentals: Chpt.
    3.1.2.2 , page 50).
    You can specify that new turns of U-turn type are closed by default.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the entry Network> Turns and main turns.
    3. Select the Close the U-turns and open any other (main) turn for the transport systems
    of the adjacent links option.
    For newly created turns, the U-turns are closed.

    15.13.3 Properties and options of turns


    You can edit all turns and their attributes in the junction editor. The junction editor opens if you
    double-click the desired turn (see "Editing turns in the Junction editor" on page 1450).

    15.13.4 Finding a turn


    You can only search for the node associated to a turn (see "Finding network objects in the network" on page 999).
    PTVGROUP

    1093

    15.13.5 Selecting turns

    15.13.5 Selecting turns


    There are several ways to select turns in order to edit them in another step.
    Marking a turn
    Setting turns active/passive
    15.13.5.1 Marking a turn
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Turns button.


    3. Click the node associated to the turn in the network.
    The turn is marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive turns with the mouse (see "Marking only active network objects" on page 1005).
    15.13.5.2 Setting turns active/passive
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.13.6 Editing the attribute values of turns


    You can edit the attribute values of single turns in the junction editor or edit the attribute values
    of all or all active turns (see "Using the Junction editor" on page 1435).
    15.13.6.1 Editing the attribute values of all or all active turns
    Note: If there are no passive turns in the network, all turns are edited. Markings of turns
    are ignored.
    1. If required, set the turns active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected turns are active.
    2. In the Network window, right-click the Turns button.
    The Turns context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit turns window opens.
    4. Select whether you want to edit the attribute values of all turns or just the active ones.

    1094

    PTVGROUP

    15.13.6.2 Displaying the attribute values of a turn in a column chart


    Element

    Description

    Only active ones

    If the option has been selected, only active turns will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of turns" on page 1093
    and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.13.6.2 Displaying the attribute values of a turn in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).
    15.13.6.3 Allocating standard data to turns
    1. Select the turns, to which you want to allocate standard data, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected turns are active.
    2. In the Network window, right-click the Turns button.
    The Turns context menu opens.
    3. Select the Standard values entry.
    The Multi-edit turns window opens.
    Tip: If the network object type Turns has been selected, you can also call the Multiedit turns window via the Edit> Standard values menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to allocate standard data to all turns or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active turns will be taken into
    account.

    6. Select the attributes that you want to overwrite with the standard data.
    Note: Use the CTRL key if you want to select several attributes.

    PTVGROUP

    1095

    15.13.6.4 Recalculating the transport system set of turns


    Element

    Description

    Type number

    Number of the turn type

    Capacity PrT

    Private transport capacity of the turns

    t0 PrT

    Private transport turning time in an unloaded network

    Is change of running direction

    Turn represents a change of direction.

    7. Click the Use standard values button.


    The selected standard attribute data are allocated to the turn values.
    Note: You can edit the standard data in menu Network> Turn standards (see "Managing turn standards" on page 1090).
    8. Click the Close button.
    15.13.6.4 Recalculating the transport system set of turns
    You can redetermine the transport systems for all or all active turns in the network. To each
    turn, including U-turns, all transport systems that are permitted both on the respective From
    link and To link will then be allocated. This corresponds to the default setting that Visum applies when inserting new turns. You can, for example, use this functionality after editing the
    transport systems of links.
    1. If required, set the turns active, whose transport systems you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    2. In the Network window, right-click the Turns button.
    The Turns context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit turnswindow opens.
    4. Select the Special functions tab.
    5. Specify whether you want to recalculate the transport systems for all or all active turns.
    Element

    Description

    Only active ones

    If the option has been selected, only active turns will be taken into
    account.

    6. Click the desired button.

    1096

    PTVGROUP

    15.13.7 Specifying an automatic allocation of the turn type


    Element

    Description

    Calculate the PrTTSysSet from the PrTTSysSet of the links

    Use the button to redetermine the PrT transport systems of


    the selected turns.

    Calculate the PuTTSysSet from the PuTTSysSet of the links

    Use the button to redetermine the PuT transport systems of


    the selected turns.

    The transport systems are allocated to the turns.


    Notes: U-turns are treated according to the settings in the Edit> User Preferences>
    Network> Turns and main turns menu (see "Creating turns" on page 1093).

    15.13.7 Specifying an automatic allocation of the turn type


    Operations which have an effect on (main) turns cause a recalculation of the type of (main)
    turns (see "Creating turn standards" on page 1090). This, for example, happens, when you
    create, delete, or merge links or nodes, when you allocate nodes to main nodes, when you
    edit the data of relevant attributes (TSysSet, NumLanes) or when reading in or importing network data.
    During the recalculation, the type is set automatically. You can specify the criteria of the automatic allocation.
    1. In the Network menu, select the Network settings entry.
    The Network settings window opens.
    2. Select the Network objects tab.
    3. In the Turn types section, check the desired option.
    Element

    Description

    The type is allocated based on the angle of the (main) turn:


    Only initial assignment according
    Angle < (180 - 45): type 1 is allocated to the (main) turn
    to angle of new
    (right).
    turn
    (180 - 45) angle (180 + 45): type 2 is allocated to the
    (main) turn (straight on).
    Angle < (180 + 45): type 3 is allocated to the (main) turn
    (left).
    From link = To link or From leg = To leg (based on the link orientation): type 4 is allocated to the (main) turn (U-turn).
    All turns via a
    node which are
    open for ICA are
    preset automatically, other-

    PTVGROUP

    The type is allocated based on the following rules, if (main) turns


    are "open for ICA". Otherwise type 0 is allocated to them.
    "Open for ICA" means that at least one lane has been defined for
    the From link and the To link or for the From leg and the To leg.

    1097

    15.13.8 Deleting turns


    Element

    Description

    wise type 0

    Each of the two links or legs and the (main) turn itself furthermore
    need to be open for at least one private transport system.
    For the automatic allocation, the following rules apply:
    ICA (Intersection capacity analysis) only considers the types
    1 to 4 and at the maximum one straight turn (type 2) per link,
    which leads to the node (or one straight main turn per leg to
    the main node).
    Of all (main) turns of a (main) node which deviate at the maximum 45 from 180, type 2 is allocated to the (main) turn
    which is closest to 180.
    All (main) turns with an angle > straight are left turns and type
    3 is allocated to them.
    All (main) turns with an angle < straight are right turns and
    type 1 is allocated to them.
    Note
    If the network contains more than one straight turn per link to the
    node (or straight main turns per leg to the main node), ICA (Intersection capacity analysis) is not calculated.

    All turns via a


    node which are
    open for Private
    transport are preset automatically,
    otherwise type 0

    The type is allocated automatically, if the (main) turn is "open for


    private transport". Otherwise type 0 is allocated to them.
    "Open for private transport" means that each of the two links and
    the turn itself (or each of the two legs and the main turn itself)
    must be open for at least one private transport system. Types 0 to
    9 are taken into account.

    Note: For the automatic allocation, all (main) turns of a (main) node are taken into
    account.
    4. Confirm with OK.
    The settings are applied.
    Notes: You can edit the (main) turn types manually later on (see "Editing turns in the Junction editor" on page 1450 and "Editing main turns in the Junction editor" on page 1454).
    Subsequently, you can allocate the attribute standard values for t0 and CapPrT to the
    (main) turns (see "Managing turn standards" on page 1090).

    15.13.8 Deleting turns


    Turns cannot be deleted like other network objects. They are deleted automatically when the
    associated node is deleted (see "Deleting nodes" on page 1083).

    1098

    PTVGROUP

    15.14 Managing links


    Notes: Turns are defined per transport system. Consequently, you can "delete" a turn for
    one, several, or all transport systems if you block it for each transport system.
    You can also block all turns, if you click the Turns button in the Network window and
    press the DEL key.

    15.14

    Managing links
    Links connect nodes and thus describe the structure of the road and rail network. A link has
    two directions, for which you can specify different settings. However, the same link number is
    allocated to both directions.

    15.14.1 Specifying a rounding factor for the PuT run time on links
    You can specify a rounding factor for the PuT run time which is used when inserting a new
    link.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the entry Network> Links.
    3. In the list next to Round PuT run time to, select the desired value.
    4. Confirm with OK.

    15.14.2 Specifying link types


    Link types are used in order to define standard values for link attributes, like the set of permitted transport systems, the number of lanes, or the capacity or rank of a link.
    Links can be allocated to different link types. Visum differentiates the link type numbers 00 to
    99, which can be aggregated to global types 0* to 9*. It is useful to differentiate between relevant link categories on the basis of the global types (see Fundamentals: Chpt. 3.1.3.1 , page
    53).
    Specifying link attribute values for selected link types
    1. In the Network menu, select the Link types entry.
    The Link types window opens.

    PTVGROUP

    1099

    15.14.2 Specifying link types

    2. In the list, select the types or global types, and specify the desired standard attribute values
    for the links of the respective type.
    Section
    Link types

    1100

    Element

    Description

    Types

    If the option has been selected, you can allocate attributes and transport systems to the link types 00-99. Select the link types, to which
    you want to allocate attributes and transport systems, by pressing the
    CTRL key and clicking the desired types in the list.

    Global type

    If the option has been selected, you can allocate attributes and transport systems to the global types 0-9. Select the global types, to which
    you want to allocate attributes and transport systems, by pressing the
    CTRL key and clicking the desired global types in the list.

    Name

    Enter a name

    Rank

    Enter a rank (see Fundamentals: Chpt. 3.1.3.1 , page 53)

    PTVGROUP

    15.14.2 Specifying link types


    Section
    Link types

    Element

    Description

    Strict

    If this option has been selected, changes made to the attributes of


    the link type are applied to all allocated links of this link type.
    Notes
    With this option you can specify for each link type whether changes
    shall be adopted automatically to the allocated links.
    Prior to confirming the changes made to the attributes of the link type,
    a query will point out the number of links affected by the changes.
    You can edit the attributes of the links at any time, the Strict option
    does not inhibit that.
    When opening network or attribute files the values of the link attributes are always read, even if the link types are strict.
    Changes made to attributes of the link type are transferred to the related links:
    if a different link type is allocated to the links and the new link
    type has the property Strict.
    if the Strict option is activated for an existing link type.
    If this option has been not selected, the edited attributes are only
    applied to newly inserted links with this link type. Links already allocated to this link type will not be changed.

    HBEFA link type

    Select a HBEFA link type for the calculation of the operation HBEFAbased emission calculation
    Note
    The list box is only displayed if you have activated the HBEFA addon (see "Enabling or disabling installed add-ons" on page 886).

    v0 PrT

    Enter a standard speed for the private transport in the unloaded network

    vMin PrT

    Enter a minimum standard speed for the private transport

    Capacity PrT

    Enter a standard capacity in car units

    Lanes

    Enter a standard number of lanes

    In the Transport systems section, you can preset attribute values and specify which PrT and
    PuT transport systems are permitted for a type.

    PTVGROUP

    1101

    15.14.3 Allocating standard values to link attributes


    Section
    Transport systems

    Element

    Description

    Perm. (Std)

    If the option has been selected, the respective PrT or PuT transport
    system is permitted on the link or global type.

    Max. speed

    Maximum speed for the transport system


    You can edit the values if you double-click in the field.

    Std. speed

    Mean speed of the PuT transport system


    You can edit the values if you double-click in the field.

    Cost 1-3

    Costs of the PuT transport system (see "Stop points: Cost tab" on
    page 1271)

    The links are specified according to your settings.

    15.14.3 Allocating standard values to link attributes


    With this functionality you can replace the current values of selected link attributes with the predefined standard values of the respective link type (see "Specifying link types" on page 1099).
    Tip: All values of the link attributes can be replaced by the current values of a link type by
    selecting the Strict option in the Link types window (see "Specifying link attribute values
    for selected link types" on page 1099).

    1. If required, set the links active whose values you want to replace, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Standard values entry.
    The Multi-edit links window opens.

    1102

    PTVGROUP

    15.14.4 Specifying the number of link orientations

    Tip: If the network object type Links has been selected, you can also call the Multiedit links window via the Edit> Standard values menu.
    4. Make sure that the Special functions tab has been selected and the Standard values entry
    in the drop-down list.
    5. Select, whether you want to replace the values of all links or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active links will be taken into
    account.

    6. Press the CTRL key and select the attributes, to which you want to allocate the standard
    values of the link type.
    7. Click the Use standard values button.
    The current values of the selected attributes are overwritten by the preset standard values
    of the link type.
    8. Click the Close button.

    15.14.4 Specifying the number of link orientations


    You can specify how many directions are generally permitted at nodes and main nodes.
    1. In the Network menu, select the Network settings entry.
    The Network settings window opens.
    2. Select the Network objects tab.
    3. In the Link orientations section, check the desired option.

    PTVGROUP

    1103

    15.14.5 Recalculating link orientations


    Element Description
    4-

    If this option has been selected, only main directions (N, SE, SW, NW) are
    used at nodes and main nodes with up to four links. Only for nodes with five
    or more links, secondary directions (NE, SE, SW, NW) will also be used.
    Secondary directions (for example NNW) are only used for nodes with more
    than eight links.

    8-

    If this option has been selected, main and secondary directions are used at
    all nodes and main nodes with up to eight links. Secondary directions (for
    example NNW) are only used for nodes with more than eight links.
    Tip
    This option is useful, if you want to allocate secondary directions at an angular intersection, for example.

    16 -

    If this option has been selected, also sub-secondary directions (for example
    NNW) can be used at all nodes and main nodes.

    4. Confirm with OK.


    Notes: If you have changed the number of the directions, you should recalculate the link
    orientations (see "Recalculating link orientations" on page 1104).
    You can edit the orientations of individual nodes in the junction editor (see "Editing links
    in the schematic view" on page 1458).

    15.14.5 Recalculating link orientations


    With this functionality, you can recalculate the link orientations at nodes and main nodes. It is
    useful, if you have changed the number of directions at all nodes/main nodes (see "Specifying
    the number of link orientations" on page 1103).
    1. In the Network window, right-click the Links button.
    The Links context menu opens.
    2. Select the Orientations entry.
    The Multi-edit links window opens.

    1104

    PTVGROUP

    15.14.6 Creating a link

    3. Make the desired changes.


    Element

    Description

    Calculate oriIf the option has been selected, all orientations at nodes are recalentations at nodes culated.
    Only for active nodes
    If the option has been selected, only the orientations of active
    nodes are recalculated.
    Calculate orientations at main
    nodes

    If the option has been selected, all orientations at main nodes are
    recalculated.
    Only for active main nodes
    If the option has been selected, only the orientations of active
    main nodes are recalculated.

    4. Click the Re-calculate link orientations button.


    The link orientations of the selected nodes are calculated.
    5. Click the Close button.

    15.14.6 Creating a link


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Links button.


    3. Click the node at which you want the new link to start (=From node).
    4. Click the node at which you want the new link to end (=End node).
    The Create link window opens.

    PTVGROUP

    1105

    15.14.6 Creating a link

    Note: If you want to edit the link course while creating the link, you can define the
    course with left-clicks after positioning the From Node with a left-click. Complete the
    course with a click on the To Node.
    5. Make the desired changes.
    Element

    Description

    Number

    Unique number of the link


    The links are numbered consecutively. The preset number can be
    overwritten by a number which has not yet been assigned in the
    network.
    Note
    The number is identical for both directions of the link.

    From node
    To node

    Display of the node numbers at which the link starts and ends

    Type

    Use the drop-down list to allocate the link to a link type (see "Specifying link types" on page 1099).

    Opposite direction

    If the option has been selected, the opposite direction of the


    link is created with the same link number.
    If the option has not been selected, a link is inserted with the
    same link number, which is yet closed to all transport systems. In
    this case, the inserted link is a one-way road.
    Notes
    One-way roads are evaluated with reference to the permitted
    transport systems. You can specify the graphic display of oneway roads in the Graphics> Edit graphic parameters> Links
    menu. You can set specific markings for the attributes IsOneWayRoad and IsOneWayRoad_TSys (transport systembased) (see "Specifying basic settings for the network window" on
    page 2337).
    If IsOneWayRoad has been selected in the attribute selection, all
    links which were inserted explicitly as one-way roads (opposite
    direction is closed to all transport systems) are highlighted.

    1106

    PTVGROUP

    15.14.7 Properties and options of links


    Element

    Description
    This previously non-existent direction of the link cannot be included in the merged network calculation following the Permit TSys
    for the opposite direction operation, because differences are
    only determined between two attribute values of an existing link.
    In case of a subsequent merged network calculation, we recommend that you set a capacity of 0 for the opposite direction instead of creating a "real" one-way road (see "Displaying flow
    bundles" on page 2265).

    Type

    Use the drop-down list to allocate the desired link type to the
    Opposite direction. It can vary from the type of the outward direction.

    Details

    You can open the Edit link window via this button. You can specify further settings for the link (see "Editing the attribute values of
    links" on page 1113).

    6. Confirm with OK.


    The link is inserted.
    Note: When creating a link, all turns are generated that are technically possible at both
    nodes of the link. For this, the standard values of the user-defined turn standards are
    used (see "Managing turn standards" on page 1090).

    15.14.7 Properties and options of links


    Note: Some of the described properties and options will only be displayed, if you have
    activated the respective add-on module (see "Displaying details on program and license"
    on page 886).

    PTVGROUP

    1107

    15.14.7.1 Links: General attributes


    The upper section of the Edit link window contains the general attributes of the link. In the
    lower section, you can edit specific attributes in various tabs.
    15.14.7.1 Links: General attributes
    Notes: You have to enter all link attributes (except Number) and all permitted or closed
    transport systems separately for each direction.
    Attribute values are highlighted that differ from those entered for the opposite direction.
    Element

    Description

    Number

    Unique number of the link


    The links are numbered consecutively. The preset number can be
    overwritten by a number which has not yet been assigned in the network.
    Note
    The number is identical for both directions of the link.

    Type

    Use the list box to allocate the desired link type to the link (see "Specifying link types" on page 1099).

    From node
    To node

    Display of the node numbers at which the link starts and ends

    Transport systems

    You can open the Transport systems window via this button. In this
    window you can select the permitted transport systems for each direction. You can select several transport systems, if you hold down the
    CTRL key.

    Opposite

    Use this button to switch to the opposite direction of the link.

    15.14.7.2 Links: Basis tab


    Notes: The attributes in the Basis tab do not depend on the transport system.
    Some of the attributes have preset standard values (see "Specifying link types" on page
    1099).

    1108

    Element

    Description

    Direct distance

    Display of the direct distance

    Length

    Enter the link length

    AddVal1-3

    Free attributes to which you can allocate values


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes. Advantage: You can name
    user-defined attributes appropriately.

    PTVGROUP

    15.14.7.3 Links: PrT TSys tab


    Element

    Description

    PlanNo

    Plan number

    Bar label

    If the option has been selected, the bar label is displayed (see "Displaying properties via bars" on page 2367).

    v0 PrT

    Maximum speed of the private transport

    Lanes

    Display of the number of lanes

    Capacity PrT

    Capacity of the link in car units

    HGV share [%]

    HGV share in total mean daily traffic

    Name

    Name of the link

    15.14.7.3 Links: PrT TSys tab


    In this tab, you can specify settings for all transport systems of private traffic.
    Element

    Description

    Permitted

    If the option has been selected for the transport system, it is permitted on the link.
    If the option has not been selected for the respective transport system, the link is not closed to the PrT transport system.

    v0

    Calculated speed in the unloaded network


    Note
    In order to determine the value, the values v0-PrT and v0-PrT-Sys
    are compared. The smaller value of the two is then v0.

    vCur

    Display of the speed of each transport system in the unloaded network

    t0

    Display of the in-vehicle time in the unloaded network

    tCur

    Display of the in-vehicle time in the loaded network

    Volume

    Display of the calculated volume

    Cross-section

    Display of the calculated undirected value

    Impedance

    Display of the calculated impedance

    AddValue

    Free attribute, to which you can allocate a value

    Toll

    Road toll for each PrT transport system


    Note
    If the link is allocated to a toll system, this attribute value is not used
    for the TRIBUT learning procedure (see "Managing toll systems" on
    page 1417).

    15.14.7.4 Links: PuT TSys tab


    In this tab, you can specify settings for all transport systems of public transport.

    PTVGROUP

    1109

    15.14.7.5 Links: Environment tab


    Element

    Description

    Permitted

    If the option has been selected for the transport system, it is permitted on the link.
    If the option has not been selected for the respective transport system, the link is not closed to the PuT transport system.

    t-PuT

    Display of the run time of each PuT transport system

    Volume

    Display of the calculated volume

    Cross-section

    Display of the calculated undirected value

    AddValue

    Free attribute, to which you can allocate a value

    Cost 1-3

    Costs of the respective transport system

    Number of fare
    points

    Number of fare points per transport system

    Note: The link attribute Number of touching line routes. which is not contained in the
    Edit link window, indicates the number of line routes that traverse an arbitrarily small section of a link. You can, for example, use it in the link list or in the link filter.
    15.14.7.5 Links: Environment tab
    In this tab, you can specify settings for the environmental impact analysis (see "Settings for the
    environmental impact model and emission calculation according to HBEFA" on page 2183).
    Note: The Environment tab is only displayed, if you have activated the Noise emissions
    RLS 90 add-on (see "Displaying details on program and license" on page 886).
    Element

    Description

    Urban

    Characteristic urban / rural for HBEFA-based calculation (see


    "Input attributes for calculation" on page 2197)

    Slope [%]

    Gradient of the lane (positive: uphill, negative: downhill)

    Surface type

    Road surface type (according to EWS-97)

    Noise

    Calculated noise

    NOx

    Calculated NOx pollutants

    SO2

    Calculated SO2 pollutants

    CO

    Calculated CO pollutants

    HC

    Calculated HC pollutants

    15.14.7.6 Links: Congestion tab


    In this tab, you can specify settings for the blocking-back model (see "Blocking back model settings and calculation" on page 1925).

    1110

    PTVGROUP

    15.14.7.7 Links: DUE tab


    Note: The settings in the Congestion tab only apply to the optional blocking-back model
    used in conjunction with static PrT assignments. They do not influence dynamic assignments or the regular node impedance calculation.
    Element

    Description

    Calculated
    Display of the calculated stocking capacity
    stocking capacity
    [CarUnits]
    Stocking capacity
    If the option has been selected, you can enter a stocking capacity
    [car units]
    which will be used in the calculation.
    If the option has not been selected, the calculated stocking capacity will be used in the calculation.
    Permeability of
    queue [%]

    Enter a percentage

    Queue length
    [CarUnits]

    Display of the calculated queue length

    Relative queue
    length [%]

    Display of the calculated relative queue length

    Mean wait time

    Display of the calculated mean wait time

    Total wait time

    Display of the total wait time

    15.14.7.7 Links: DUE tab


    In this tab, you can specify settings for the procedure Dynamic User Equilibrium (DUE) (see
    "Dynamic User Equilibrium (DUE)" on page 1969).
    Note: The settings in the DUE tab only apply to the PrT procedure Dynamic User Equilibrium (DUE).
    Element

    Description

    Average space
    required by car
    unit per lane

    Enter the length required by a car unit in case of a fully congested


    link, i.e. when the maximum vehicle density has been reached.
    Note
    The value needs to fulfill the following condition:
    SpacePerPCU <= 1000 v0PrT / (2 1.05 CapPrT/ NumLanes)}
    The standard value is calculated as follows:
    SpacePerPCU = MIN {7.00, 1000 v0PrT/(2 1.05 CapPrT/ NumLanes)}

    vWave

    Enter the slope for the hypercritical branch of the fundamental diagram (see Fundamentals: Chpt. 6.18.4 , page 417)

    PTVGROUP

    1111

    15.14.7.8 Links: ICA tab


    Element

    Description
    Note
    The standard value is calculated as follows:
    Max{v0PrT 0.3, CapPrT/(1000/LinkSpacePerPCU CapPrT
    2/v0PrT)}
    Tip
    Use the Multi-edit functionality to allocate a value to all links (see
    "Resetting DUE attributes to the standard values" on page 1133).

    Fundamental diagram type

    Use the list box to select one of the two types of the fundamental diagram (see Fundamentals: Chpt. 6.18.4 , page 417).

    Out capacity

    If the option has been selected, you can enter an out capacity for
    the link.
    If the option has not been selected, the regular capacity PrT
    (CapPrT) will be used.

    15.14.7.8 Links: ICA tab


    The data in the ICA tab are used in the calculation of the node impedance calculation ICA
    (Intersection Capacity Analysis) (see "Calculating and exporting ICA" on page 1499).
    Element

    Description

    Arrival type

    Level of platooning in traffic arriving at the To node

    15.14.8 Finding a link


    How to find links has been described for all network object types (see "Finding network objects
    in the network" on page 999).

    15.14.9 Selecting links


    There are several ways to select links in order to edit them in another step.
    Marking links
    Setting links active/passive
    15.14.9.1 Marking links
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click next to the link in the desired direction.
    The link is marked.
    4. If you want to mark additional links, press the C TRL key and keep it pressed.
    5. One by one, click next to further links in the directions you want to mark.
    The links are marked.
    1112

    PTVGROUP

    15.14.9.2 Setting links active/passive

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive links with the mouse (see "Marking only active network objects" on page 1005).
    Tip: Alternatively, you can mark a link by searching for it (see "Finding a link" on page
    1112) or by selecting the respective row in the list of links (see "Selecting list sections" on
    page 2319).
    15.14.9.2 Setting links active/passive
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.14.10 Editing the attribute values of links


    You can edit the attribute values of one link, all marked links or all (active) links.
    15.14.10.1 Editing the attribute values of a link
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, double-click next to the link in the desired direction whose attribute values
    you want to edit.
    The Edit link window opens.
    Tip: If the link is marked, you can also call the Edit link window via the context menu>
    entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of links" on page
    1107).
    5. Confirm with OK.
    The attribute values are edited.
    Tip: You can also edit the values of the input attributes of links in the Quick view window
    or in the list of the network object type (see "Quick view window" on page 810 and "Working with lists" on page 2299).
    15.14.10.2 Editing the attribute values of marked links
    1. Mark the desired links whose attribute values you want to edit (see "Selecting links" on
    page 1112).
    2. Press the ENTER key.

    PTVGROUP

    1113

    15.14.10.3 Editing the attribute values of all or all active links


    The Multi-edit nodes: <Number> objects window opens.
    Tip: You can also open the Multi-edit links: <Number> objects window via the context menu > Edit entry or by double-clicking the last link you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of links" on page 1107
    and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.14.10.3 Editing the attribute values of all or all active links
    Note: If there are no passive links in the network, all links are edited. Markings of links
    are ignored.
    1. If required, set the links active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit links window opens.
    4. Select whether you want to edit the attribute values of all links or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active links will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of links" on page 1107
    and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.14.10.4 Displaying the attribute values of a link in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    1114

    PTVGROUP

    15.14.11 Editing the shape of a link course

    15.14.11 Editing the shape of a link course


    Tip: You can already edit the course of a link when creating it (see "Creating a link" on
    page 1105).
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click the link in the desired direction whose shape you want to edit.
    The link is marked.
    4. Right-click in the network display.
    A context menu opens.
    5. Select the Edit shape entry.
    Tip: Alternatively, press the F5 key.
    6. In the network, mark the position of the first intermediate point with a left-click.

    A rubber band connects the From node via the current position of the mouse with the To
    node of the link.
    7. If required, define further intermediate points by marking the desired positions in the network.

    Note: If you press the ESC key, the course will be discarded and the link will be reset
    to the previous course.
    8. Once you have inserted all intermediate points, press the ENTER key to complete the
    course.
    Tip: Alternatively, right-click in the network display.
    A query opens.
    9. Use the polygon length as length, if required.
    The course of the link is changed.

    PTVGROUP

    1115

    15.14.12 Reshaping the course of a link

    15.14.12 Reshaping the course of a link


    You can re-edit the shape of the link course.
    1. Right-click in the network display.
    A shortcut menu opens.
    2. Select the Edit shape entry.
    The Edit shape of link window opens.

    Element

    Description

    Initialize F2

    Use this button to discard the course and reset the link to the
    direct distance From node - To node.
    Tip
    Alternatively, press the F2 key.

    Take over lengthpolygon

    If the option has been selected, the new link length with be calculated automatically.
    If the option has not been selected, the length of the link is not
    adjusted.
    Note
    The direct distance of each link polygon is calculated from the
    coordinates of the intermediate points and the lengths of the resulting link sections.
    Tip
    You can also use the distances resulting from an edited course
    as link lengths for several links. In the Multi-edit links window,
    select the Length attribute, click the Attribute button and generate the length from the Length polygon attribute.

    3. In the network, click the polygon point that you want to shift and hold down the mouse button.
    4. Drag the polygon point to the desired position and release the left mouse button.
    5. If required, drag further polygon points to new positions.
    6. Delete existing polygon points, if required, by pressing the C TRL key and clicking the polygon point.
    7. Insert further polygon points, if required, by pressing the C TRL key and clicking the course.
    8. Confirm with OK.

    1116

    PTVGROUP

    15.14.13 Reallocating links


    The course of the link is changed.
    Tip: Alternatively, you can confirm the course by clicking in the network display.
    Note: The link label is displayed at the longest section of a link with an edited shape, if
    the label length does not exceed the length of this link section on screen. In that case,
    you can reduce the text size.

    15.14.13 Reallocating links


    This function allows changing the To node or the From node of a link.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click next to the link in desired direction that you want to reallocate.
    The link is marked.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Reallocate entry.
    The link is displayed without arrow head.
    6. Click the desired node that you want to reallocate and hold down the left mouse button.
    7. Move the To node or the From node to the node to which you want to reallocate the link and
    release the mouse button.
    Note: While moving the mouse pointer changes into a cross

    A query opens.
    8. Select whether the polygon length is to be adopted as length.
    Element

    Description

    Yes

    If the option has been selected, the new link length with be calculated automatically.

    No

    If the option has been selected, the length of the link is not adjusted.
    Note
    The direct distance of each link polygon is calculated from the
    coordinates of the intermediate points and the lengths of the resulting link sections.

    The link is reallocated.


    PTVGROUP

    1117

    15.14.14 Resetting link polygons

    15.14.14 Resetting link polygons


    With this functionality you can reset the user-defined polygons to the direct distance From
    node - To node.
    1. In the Network window, right-click the Links button.
    The Links context menu opens.
    2. Select the Polygons entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multiedit links window via the Edit> Polygons menu.
    3. Make sure that the Special functions tab has been selected and the Polygons entry in the
    drop-down list.
    4. Select whether you want to edit the attribute values of all links or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active links will be taken into
    account.

    5. Click the Initialize button.


    The polygons are reset to the direct distance between the From node and the To node.
    6. Click the Close button.

    15.14.15 Generalizing link polygons


    With this functionality you can reduce the number of intermediate points of link polygons.
    1. In the Network window, right-click the Links button.
    The Links context menu opens.
    2. Select the Polygons entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multi-edit
    links window via the Edit> Polygons menu.
    3. Make sure that the Special functions tab has been selected and the Polygons entry in the
    drop-down list.
    4. Select whether you want to generalize the polygons of all links or just the active ones.

    1118

    PTVGROUP

    15.14.16 Splitting a link


    Element

    Description

    Only active ones

    If the option has been selected, only active links will be taken into
    account.

    5. Click the Generalize link polygons button.


    The Generalize link polygons window opens.
    6. Make the desired changes.
    Element

    Description

    Precision (in
    Visum coordinates)

    Specification, how far the polygons may deviate from the previous
    ones

    Total number of
    intermediate
    points (before)

    Calculated total number of intermediate points before and after


    generalization
    Note
    The calculated total numbers will be output if you click the Preview button.

    Preview

    Calculates the total number of intermediate points based the entry


    under Precision.
    Note
    The old and the new course are displayed in the network editor.

    7. Confirm with OK.


    The link polygons are generalized.

    15.14.16 Splitting a link


    You can split a link by inserting an intermediate node.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click next to the link in desired direction that you want to split.
    4. Press F8.
    5. Insert an intermediate node by clicking in the network.
    The Create node window opens.

    PTVGROUP

    1119

    15.14.17 Copying attribute values to the opposite direction


    Note: The intermediate node does not have to be located on the link to be split. As
    intermediate node, you can
    mark any desired node in the network (except the From node and To node of the
    link that you want to split) or
    add an "isolated" node to the network (see "Creating a node" on page 1063).
    6. Make the desired changes (see "Properties and options of nodes" on page 1066).
    7. Confirm with OK.
    The Split link window opens.

    8. Make the desired changes.


    Element

    Description

    New link numbers The program suggests the next link available numbers in the network. You can edit the link numbers.
    9. Confirm with OK.
    The link is split. Two resulting links, possibly a new intermediate node, and new turns are inserted.

    15.14.17 Copying attribute values to the opposite direction


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click next to the link in desired direction, whose attributes you want to copy.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Copy attributes to reverse direction entry.
    The values of all editable attributes of the marked link are automatically applied to the opposite direction of the marked link.

    15.14.18 Labeling link bars


    In the network, you can visualize the values of link attributes with the aid of link bars (see "Displaying properties via bars" on page 2367). You can label the link bars displayed in the network.
    You can edit the labels of link bars as follows:
    1120

    PTVGROUP

    15.14.19 Switching on/off the labels of link bars


    switch on/off (see "Switching on/off the labels of link bars" on page 1121)
    shift (see "Shifting the labels of link bars" on page 1122) and
    reset them to their standard positions (see "Relocating the link bars to their standard positions" on page 1123).

    15.14.19 Switching on/off the labels of link bars


    If you want to display the labels of link bars, in the Graphics> Graphic parameters> menu of
    the Edit graphic parameters> Links window, you have to select the Draw bar labels option
    (see "Specifying basic settings for the network window" on page 2337).
    For each link, you can overwrite the standard setting for all links.
    15.14.19.1 Switching on/off the bar label of a link
    You can switch on/off the bar label of individual links as follows:
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click next to the link in the desired direction, whose bar label you want to
    switch on or off.
    4. Press F4.
    The label of the link bar is switched on or off.
    Tip: You can also enable/disable the label display via the Switch bar label on/off entry in
    the context menu.
    Notes: For the display of the label of the link bars, the text size and the text scaling factor
    is taken into account. Use the Preview entry in the File > Print menu if you want to check
    your settings before printing.
    If, for individual links, no bar label is displayed, you should reduce the text size or the text
    scaling factor or zoom into the network (see "Specifying basic settings" on page 2337).
    15.14.19.2 Switching on/off labels of marked links
    You can switch on/off the bar labels of several marked links as follows:
    1. Click the

    Edit mode icon.

    2. Click the Links button.


    3. Mark the desired links.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Click the Switch bar label on/off entry.
    The bar labels of the marked links are switched on or off.
    PTVGROUP

    1121

    15.14.19.3 Switching on/off bar labels of all or all active links


    15.14.19.3 Switching on/off bar labels of all or all active links
    You can switch on or off the bar labels of all or all active links as follows.
    1. If required, set the links active whose bar labels you want to switch on or off, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, click the

    Edit mode icon.

    3. Click the Links button.


    4. Right-click in the network display.
    The Links context menu opens.
    5. Select the Labels entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multiedit links window via the Edit> Labels menu.
    6. Make sure that the Special functions tab has been selected and the Labels entry in the
    drop-down list.
    7. Make the desired settings.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active links will be taken into
    account.
    If the option has not been selected, all links will be taken into
    account.

    Element

    Description

    Switch on

    All bar labels are switched on, if you click this button.

    Switch off

    All bar labels are switched off, if you click this button.

    The bar labels are switched on or off.


    8. Click the Close button.

    15.14.20 Shifting the labels of link bars


    You can shift the labels of link bars along the respective link.

    1122

    PTVGROUP

    15.14.21 Relocating the link bars to their standard positions


    Note: By default, the link bar label is displayed as follows:
    At the midway point of the link in case of links that have not been reshaped. The link
    bar label is not issued if the text length exceeds the direct distance length of the link.
    For links with an edited shape
    at the longest section (standard). The link bar label is not issued if the text length
    exceeds the section length in the network display.
    in the middle. The link bar label is not issued, if the text length exceeds the direct
    distance From node - To node.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click next to the link in the desired direction, whose label you want to shift.
    4. Press F6.
    Tip: Alternatively, you can change the position of the label via the Shift bar labels
    entry in the context menu.
    5. In the network, click the position where you want to position the label.
    A query opens.
    6. Click the Yes button, if you want to position the label of the reverse direction opposite.
    The link bar label is shifted.
    Note: If you click the No button, the position of the label of the reverse direction will not be
    changed.

    15.14.21 Relocating the link bars to their standard positions


    You can relocate the bar labels of all or all active links to their standard positions as follows.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. Right-click in the network display.
    The Links context menu opens.
    4. Select the Labels entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multiedit links window via the Edit> Labels menu.

    PTVGROUP

    1123

    15.14.22 Links: Opening the Timetable editor


    5. Make sure that the Special functions tab has been selected and the Labels entry in the
    drop-down list.
    6. Make the desired settings.
    Element

    Description

    Only active ones

    If the option has been selected, only active links will be taken
    into account.
    If the option has not been selected, all links will be taken into
    account.

    Element

    Description

    Initialize position

    If you click the button, all labels are relocated to their standard
    positions, i.e. in the middle of the link in case of links whose
    course equals the direct distance, and at the longest section in
    case of links whose course has been edited.
    Note
    This option only applies to labels that have been shifted beforehand.

    The labels of the link bars are reset to their standard positions.
    7. Click the Close button.

    15.14.22 Links: Opening the Timetable editor


    With this function, you can open the Timetable editor (see "Using the Timetable editor" on
    page 1526). The line routes that traverse the selected links are preselected.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. Press the CTRL key and keep it pressed.
    4. Click one by one next to the links in the desired directions which you want to mark.
    The selected links are marked.
    5. Right-click in the network display.
    A context menu opens.
    6. Select the Timetable editor entry.
    If you have marked only one link, the Timetable editor opens. If you have marked multiple
    links, the Handling of marked links window opens.

    1124

    PTVGROUP

    15.14.23 Determining the link course based on a shortest path search

    7. Make the desired changes.


    Element

    Description

    Line routes traversing one or


    more of the marked links

    If the option has been selected, all line routes are displayed that
    traverse one of the marked links.

    Line routes which If the option has been selected, only line routes are displayed that
    traverse all of the traverse all of the marked links.
    marked links
    8. Confirm with OK.
    The Timetable editor opens and the traversed line routes are displayed according to the selected option.
    Notes: The displayed direction of the displayed line routes is picked independently of the
    attribute direction, so that the orientation of the line routes is the same, if they traverse the
    selected links in the same direction.
    This functionality is not available if the Timetable editor is already open.

    15.14.23 Determining the link course based on a shortest path search


    With this functionality you can determine the link sequence between at least two marked
    nodes for a PrT transport system or at least two marked stop points for a PuT transport system
    based on the currently set parameters.
    Afterwards, you can for example edit the marked link sequence as follows.
    Simultaneously modify the attributes of the marked links in the Quick view window.
    Use the editing functionalities for several objects in the context menu or the Edit menu.
    Edit the line routes, which traverse the marked links, in the Timetable editor (see "Using
    the Timetable editor" on page 1526).
    1. In the Network window, right-click the Links button.
    The Links context menu opens.
    2. Select the Link sequence from shortest path search entry.
    The Edit shape of link sequence window opens.

    PTVGROUP

    1125

    15.14.23 Determining the link course based on a shortest path search

    Tip: If the network object type Links has been selected, you can also open the Edit
    shape of link sequence window via the Edit> Link sequence from shortest path
    search menu.
    3. Make the desired changes.
    Element

    Description

    Autozoom

    Use this button to shift the network section. Marked objects are shifted to
    the middle of the screen.

    Parameters

    Use this button to specify the parameters for the shortest path search.
    In the Path search parameters window, you can specify the following
    settings:
    Transport system
    Use the drop-down list to select a transport system. You can select any
    transport system that exists in the network.
    Use also closed links for routing
    If the option has been selected, the search also considers links that have
    been closed to the transport system.
    Use also closed turns for routing
    If the option has been selected, the search also considers turns that have
    been closed to the transport system.
    Search criterion
    Use the list box to select a search criterion (see "Creating a system route"
    on page 1368).

    4. In the network, click the first node or stop point and hold down the mouse key.
    5. Move the mouse pointer to the next desired node or stop point and release the mouse button.
    6. If required, drag the mouse pointer to further nodes or stop points.
    7. Confirm with OK.
    In the network, the link sequence found based on the parameter settings is marked for further
    modifications.

    1126

    PTVGROUP

    15.14.24 Checking the symmetry of both directions of a link

    15.14.24 Checking the symmetry of both directions of a link


    With this functionality you can check the symmetry of the input values of selected link attributes
    of the two 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.
    Notes: Any previously set spatial selection of active network objects will not be taken into
    account when checking the symmetry, but will be reset automatically. Save the previous
    selection beforehand, if required (see "Saving a spatial selection of network objects" on
    page 1039).
    However, active link filters will be taken into account, i.e. only links which fulfill the current
    filter criteria are checked.
    1. In the Network window, right-click the Links button.
    The Links context menu opens.
    2. Select the Check link symmetry entry.
    The Link symmetry window opens.
    Tip: If the network object type Links has been selected, you can also open the Link
    symmetry window via the Edit> Check link symmetry menu.
    3. In the Attribute to be compared section, click the button with the attribute name.
    The Attributes (links) window opens.
    4. In the attribute list, select the attribute that you want to compare.
    5. Confirm your selection with OK.
    The attribute is selected.
    6. Close the Link symmetry window with OK.
    Links, whose two directions agree in the selected attribute, become passive links.

    15.14.25 Removing collinear points


    With this functionality, you can remove the intermediate points of links which do not affect the
    course of the link because the direction of the link does not change at those points. Using this
    functionality reduces the drawing effort.
    1. If required, set the links active whose collinear points you want to remove, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    PTVGROUP

    1127

    15.14.26 Calculating the gradient from z-coordinates


    The Links context menu opens.
    3. Select the Polygons entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multi-edit
    links window via the Edit> Polygons menu.
    4. Make sure that the Special functions tab has been selected and the Polygons entry in the
    drop-down list.
    5. Click the Delete collinear points button.
    The collinear points of the selected links are removed.

    15.14.26 Calculating the gradient from z-coordinates


    The gradient is a link attribute. It is used amongst other things for the following purposes:
    ANM export to Vissim
    ICA calculations
    Emission calculation according to HBEFA
    Visum can only calculate the gradient of a link if the z coordinates of the From node and To
    node of the link are known (see "Editing the attribute values of nodes" on page 1066). The gradient is displayed in percentage.
    Visum calculates the gradient for one link direction. The opposite direction gets the same gradient value with reversed sign, however.
    1. If required, set the links active whose gradients you want to calculate (see "Using filters to
    set network objects active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page 1033).
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Calculate slope from z-coordinates entry.
    The Multi-edit links window opens.
    4. Make sure that the Special functions tab has been selected and the Calculate slope from
    z-coordinates entry in the drop-down list.
    5. Make the desired changes.

    1128

    PTVGROUP

    15.14.27 Interpolating z-coordinates


    Element

    Description

    Only active ones

    If this option has been selected, only the gradients of active


    links will be calculated.
    If this option has not been selected, the gradients of all links
    will be calculated.

    Reference attribute for length

    Length (input attribute)


    You can read the link attribute or have it calculated by Visum and
    edit it afterwards Select this reference attribute, if you have reliable lengths. This way you will get the most accurate results.
    Length direct
    This link attribute stands for the direct distance between the From
    node and the To node. It is calculated automatically by Visum.
    Length polygon
    This link attribute specifies the length of the polygon between the
    From node and the To node. It is calculated automatically by
    Visum.

    6. Click the Set button.


    Visum calculates the gradients of the links you specified. The gradient is a link attribute and
    displayed as percentage. You will also find the slope details in the Environment tab of the
    Edit link window (see "Properties and options of links" on page 1107).

    15.14.27 Interpolating z-coordinates


    With this functionality you can interpolate the z-coordinates of links.
    Note: The functionality can save the effort of editing route courses after an export to Vissim.
    1. If required, set the links active, whose z-coordinates you want to adjust, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Polygons entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multi-edit
    links window via the Edit> Polygons menu.

    PTVGROUP

    1129

    15.14.28 Generating link attribute values from turn attribute values


    4. Make sure that the Special functions tab has been selected and the Polygons entry in the
    drop-down list.
    5. Click the Interpolate z-coordinates button.
    The z-coordinates of the selected links are interpolated.

    15.14.28 Generating link attribute values from turn attribute values


    With this functionality, you can generate link attribute values from the existing values of a turn
    attribute or main turn attribute.
    The following rules apply:
    If the two nodes of a link are not part of a main node, turn attributes are allocated to the
    link attributes.
    If the link is an inner link, i.e. both nodes of a link are part of the same main node, turn attributes are allocated to the link attributes.
    If one node (node 1) of a link is part of a main node and the other node (node 2) is not part
    of a main node, the values of the main turn (node 1) and the values of the turn (node 2)
    are used.
    If one node (node 1) of a link is part of a main node and the other node (node 2) is part of
    a different main node, only the values of the main turns are used for the calculation.
    Notes: Prerequisite is that, for turns, volume data are available as turn attributes.
    You can also generate link attribute values based on other attributes of turns at the From
    node or To node of the link.
    1. If required, set the links active whose link attributes you want allocate the values of turn and
    main turn attributes to via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Create attribute data entry.
    The Multi-edit links window opens.

    1130

    PTVGROUP

    15.14.28 Generating link attribute values from turn attribute values

    Tip: If the network object type Links has been selected, you can also call the Multi-edit
    links window via the Edit> Create attribute data menu.
    4. Make sure that the Special functions tab has been selected and the Turn-AddValues entry
    in the drop-down list.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, the value of the selected attributes of all active links will be replaced.
    If the option has not been selected, the value of the selected
    attributes of all links will be replaced.

    Link attribute

    Use the button to select the attribute, to which you want to allocate the values of a turn attribute.

    Set to

    In the drop-down list, select the desired entry.


    Note
    The attribute values of each node of the link are compared and
    the value is determined based on the selected option.

    Turn attribute

    Use the button to select the attribute based on which you want to
    generate the link attribute data.

    Main turn attribute Use the button to select the attribute based on which you want to
    generate the link attribute data.
    Add

    If the option has been selected, the determined attribute values


    and already existing link attribute values will be added up.

    6. Click the Set button.


    The new values for the selected link attribute are determined.
    7. Click the Close button.

    PTVGROUP

    1131

    15.14.29 Generating link run times from line run times

    15.14.29 Generating link run times from line run times


    Note: This functionality is only relevant for the public transport.
    With this functionality, you can replace the values of the link run times with the values of the
    line run times.
    1. If required, set the links active whose values you want to replace, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Link run times from line run times entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multiedit window via the Edit> Link run times from line run times menu.
    4. Make sure that the Special functions tab has been selected and the Run times of links
    from run times of lines entry in the drop-down list.
    5. Make the desired changes.
    Element

    Description

    Weighting

    Use the drop-down list to select the type of weighting.


    Minimum
    Mean
    Maximum
    If a link is part of more than one time profile, the link run time can
    be determined from the weighted mean of the run times of all time
    profiles, from the minimum run time of the time profiles, or from
    the maximum run time of the time profiles which include this link.

    Regard only
    active time profiles

    If the option has been selected, only active time profiles will be
    taken into account.

    6. Click the Set button.


    The line run times are used as link run times for the PuT transport systems.

    1132

    PTVGROUP

    15.14.30 Generating link run times from line run times in a procedure sequence

    15.14.30 Generating link run times from line run times in a procedure sequence
    1. On the toolbar, click the

    Open Procedure sequence window button.

    The Procedure sequence window opens.


    2. In the desired position of the procedure sequence, insert the Set link run times from line
    run times operation of the Miscellaneous category (see "Setting up and starting the procedure sequence" on page 1847).
    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Set link run times from line run times window opens.
    4. Make the desired changes.
    Element

    Description

    Weighting

    Use the drop-down list to select the type of weighting.


    Minimum
    Mean
    Maximum
    If a link is part of more than one time profile, the link run time can
    be determined from the weighted mean of the run times of all time
    profiles, from the minimum run time of the time profiles, or from
    the maximum run time of the time profiles which include this link.

    Regard only
    active time profiles

    If the option has been selected, only active time profiles will be
    taken into account.

    Regard only
    active links

    If the option has been selected, only active links will be taken into
    account.

    5. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The link run times are generated.

    15.14.31 Resetting DUE attributes to the standard values


    With this functionality you can set the value of the vWave and the value of the space per car
    unit for all or all active links to the standard value (see "Dynamic User Equilibrium (DUE)" on
    page 1969).
    1. If required, set the links active, whose DUE attribute values you want to reset, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.

    PTVGROUP

    1133

    15.14.32 Deleting links


    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the DUE attributes entry.
    The Multi-edit links window opens.
    Tip: If the network object type Links has been selected, you can also call the Multi-edit
    links window via the Edit> DUE attributes menu.
    4. Make sure that the Special functions tab and the DUE attributes entry in the drop-down
    list have been selected.
    5. Click the Set button.
    The values of the DUE attributes are reset to the standard values.

    15.14.32 Deleting links


    There are several ways to delete links.
    Deleting a link
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. In the network, click the link that you want to delete (see "Marking links" on page 1112).
    4. Press the ENTER key.
    The link is deleted.
    Tip: You can also delete the marked link via the context menu> entry Delete.
    Deleting several marked links
    1. Mark the links that you want to delete (see "Selecting links" on page 1112).
    The selected links are marked.
    2. Press the ENTER key.
    A query opens.
    Tip: You can also delete the marked links via the context menu> entry Delete.
    3. Confirm with OK.
    A query opens.
    4. Confirm the query.
    The links are deleted.

    1134

    PTVGROUP

    15.15 Managing zones


    Deleting all active links
    1. Select the links, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected links are active.
    2. In the Network window, right-click the Links button.
    The Links context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    4. Confirm with OK.
    The Delete all active links window opens.
    5. Select which links you want to delete.
    Element

    Description

    Yes

    The link listed in the window will be deleted and also the network objects
    with a reference to the link.

    Yes for all

    All remaining active links will be deleted, and also the network objects
    with a reference to the links.

    No

    Neither the link listed in the window will be deleted nor the network
    objects with a reference to the link.

    No for all

    None of the remaining active links will be deleted, nor any of the network
    objects with a reference to the link.

    Notes: If you click the Yes or No buttons, the query is displayed for the next link number.
    With the Yes for all or No for all buttons, you only regard the remaining links, for
    which neither Yes nor No has been clicked.
    The confirmed links are deleted.

    15.15

    Managing zones
    Zones are origin and destination of trips within the transport network, for example residential
    areas, commercial areas, shopping centers, schools. They are connected to the network via
    connectors. Each vehicle journey starts and ends at a zone (see Fundamentals: Chpt. 3.1.4 ,
    page 56).

    PTVGROUP

    1135

    15.15.1 Creating a zone

    15.15.1 Creating a zone


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Zones button.


    3. In the network, click the position where you want to insert the centroid of the zone.
    The Create zone window opens.
    4. Enter the desired data (see "Properties and options of zones" on page 1137).
    5. Confirm with OK.
    The centroid of the zone is inserted. You can now create a boundary.
    Note: The optional zone boundary is used to calculate the area of the zone and
    shows its spatial extent.
    You can continue as follows:
    If you do not want to define a boundary for the zone, press the ESC key. The zone is
    then inserted as centroid without a boundary. You can specify the boundary later (see
    "Creating a boundary" on page 1042).
    If you want to define the boundary for the zone, proceed with the next step.
    6. Specify the boundary of the zone by inserting at least three polygon points in a counterclockwise direction in the desired positions.
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the surface (see Fundamentals: Chpt. 3.5.2 , page 124).

    Note: Even though you can also insert the polygon points in a clockwise direction,
    this would create a so-called negative face (=hole), which cannot be saved as boundary as no surface exists yet from which it can be cut out.
    7. Confirm the definition of the boundary with a right-click or press ENTER.
    The boundary is created and the polygon points are highlighted. The Edit shape window
    opens.
    Note: If you confirm the definition of the boundary with a right-click, the coordinates of
    the position of the click will not be saved as polygon point.

    1136

    PTVGROUP

    15.15.2 Properties and options of zones


    8. If required, reshape the boundary (see "Editing polygon points" on page 1044).
    9. Confirm with OK.
    The zone is inserted in the network.
    Note: You need to insert connectors to and from zones separately (see "Managing
    connectors" on page 1159).

    15.15.2 Properties and options of zones


    Note: Some of the described properties and options will only be displayed, if you have
    activated the respective add-on module (see "Displaying details on program and license"
    on page 886).

    The upper section of the Create zone or Edit zone window contains the general attributes of
    the zone. In the lower section, you can edit specific attributes in various tabs.
    15.15.2.1 Zones: General attributes
    Element

    Description

    Number

    Unique number of the zone


    The zones are numbered consecutively. You can overwrite the preset number with a number that does not yet exist in the network.

    Type

    The zone type (0...9) categorizes the zone. The standard type is 0.

    Code

    Code of the zone

    Name

    Name of the zone

    15.15.2.2 Zones: Basis tab

    PTVGROUP

    1137

    15.15.2.3 Zones: Connections tab


    Element

    Description

    Relative state

    You can define an area under consideration for the evaluation of the
    traffic between zones if you assign a relative state to the zones.
    In the drop-down list, select whether the zone shall be inside of the
    area under consideration (Internal) or outside of it (External), or whether the state of the zone shall not be relevant to the evaluation of the
    traffic between zones (Ignore).
    Note
    This setting is relevant to the OD pair filter (see "Exception: Filter for
    OD pairs" on page 1026).

    AddValue1-AddVa- Free attributes which you can use to enter additional values.
    lue3
    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes (see "Managing user-defined
    attributes" on page 973).
    Position

    Coordinates of the zone centroid in the network


    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).
    Note
    The label of a zone is always displayed at the position of its centroid.

    15.15.2.3 Zones: Connections tab


    Section PrT
    Element

    Description

    Origin connectors By shares


    Use this option to specify that the PrT origin traffic is distributed proportionally to the PrT origin connectors (see "Connectors: Basis tab"
    on page 1162).
    Absolute
    Use this option to specify that distribution of the PrT origin traffic to
    the PrT connectors is absolute.
    Dest. connectors

    1138

    By shares
    Use this option to specify that the PrT destination traffic is distributed
    proportionally to the PrT destination connectors (see "Connectors:
    Basis tab" on page 1162).
    Absolute
    Use this option to specify that the distribution of the PrT destination
    traffic to the PrT destination connectors is absolute.

    PTVGROUP

    15.15.2.4 Zones: Demand tab


    Section PrT
    Element

    Description

    Method for
    Use the drop-down list to select a method for the calculation of the
    connector shares shares of proportional connectors for the zone which deviates from
    the standard.
    Tips
    You can change the standard method in the Calculate> General procedure settings> menu under the PrT settings> entry in the
    Connector weights apply to list (see "Proportional distribution of
    demand" on page 1888).
    You can also change the method for several zones via the Method
    for connector shares attribute (see "Editing attribute values of network objects" on page 983).

    Note: For PrT connectors with a distribution by shares, the impedances are determined
    according to the set impedance function during the assignment (see "Definition and application of volume-delay functions" on page 1892).
    Section PuT
    Element

    Description

    Connectors

    By shares
    Use this option to specify that the PuT origin and destination traffic is
    distributed proportionally to the PuT origin and destination connectors (see "Connectors: Basis tab" on page 1162).
    Note
    For a distribution by shares, in the Calculate> Procedure
    sequence menu the PuT assignment procedure from the Assignments category needs to be selected with the Timetable-based or
    Headway-based setting and the Regard connectors as shares
    parameter (see "Timetable-based assignment:Basis tab" on page
    2022 and "Headway-based assignment:Basis tab" on page 2011).
    Absolute
    Use this option to specify that the distribution of the PuT origin and
    destination traffic to the PuT origin and destination connectors is
    absolute.

    15.15.2.4 Zones: Demand tab


    In the OD demand tab, the current traffic volume of the zone is displayed per direction and
    demand segment in the network, and totalized per PrT and PuT transport type and overall (see
    "Modeling demand" on page 1606).

    PTVGROUP

    1139

    15.15.2.5 Zones: DStrata tab


    15.15.2.5 Zones: DStrata tab
    In the DStrata tab, you can edit the value of the productions and attractions calculated for the
    specific zone.
    The productions and attractions of the demand strata are calculated for each zone in the (EVA)
    trip generation step of the demand calculation (see "Starting the iterative repetition" on page
    1697).
    For demand models of type EVA-P (see "Managing demand objects" on page 1617), you can
    edit the value of further demand volumes.
    Element

    Description

    Select demand
    model

    Use the drop-down list to select the demand model, the demand
    strata of which you want to display in the list (see "Managing demand
    objects" on page 1617).

    DStratum

    Demand strata defined for the selected demand model (see "Managing demand objects" on page 1606).

    Productions

    Number of trips that start at the zone

    Attractions

    Number of trips that terminate at the zone

    Home trips

    Number of trips that originate and terminate at the respective zone


    Note
    This column is only available for demand models of type EVA-P and
    Tour-based model.

    Production target

    Number of trips that start at the respective zone, which is calculated


    in the EVA trip generation step before taking account of the constraints (see "Modeling demand" on page 1606).
    Note
    This column is only available for demand models of type EVA-P.

    Attractions target Number of trips that terminate at the respective zone, which is calculated in the EVA trip generation step before taking account of the
    constraints (see "Modeling demand" on page 1606).
    Note
    This column is only available for demand models of type EVA-P.

    1140

    Balance factor
    productions

    Factor which is calculated optionally when solving the trilinear equation system during EVA distribution/mode choice for the production
    side (see Fundamentals: Chpt. 4.2.2.3 , page 165).

    Balance factor
    attractions

    Factor which is calculated optionally when solving the trilinear equation system during EVA distribution/mode choice for the attraction
    side (see Fundamentals: Chpt. 4.2.2.3 , page 165).

    PTVGROUP

    15.15.2.6 Zones: HBEFA tab


    You can also edit the values via menu Demand> Demand models> tab Demand
    strata> button Productions/attractions (see "Managing demand objects" on page
    1606).
    15.15.2.6 Zones: HBEFA tab
    In the HBEFA tab you can specify the settings for the HBEFA-based calculation of the cold
    start excess calculation (see Fundamentals: Chpt. 9.3.2.2 , page 688).
    Element

    Description

    Calculate cold
    start surplus by
    area

    If the option has been selected, the cold start surplus is calculated by
    area.

    Calculate cold
    start surplus on
    paths

    If the option has been selected, the cold start surplus is calculated on
    paths.

    Cold start share

    Use this attribute to specify the share of cold start for this zone. You
    can allocate values between 0 and 1 to this attribute.
    Tip
    If the zone is a cordon zone, for example, it makes sense to allocate
    value 0 to the zone, because vehicles are usually warm already as
    they pass a cordon zone.

    15.15.3 Finding a zone


    How to find zones is described for all network objects (see "Finding network objects in the network" on page 999).

    15.15.4 Selecting zones


    There are several ways to select zones in order to edit them in another step.
    Marking zones
    Setting active/passive zones
    15.15.4.1 Marking zones
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Zones button.


    3. In the network, or within the boundary of the first zone, click the centroid that you want to
    mark.
    The zone is marked.
    4. If you want to mark additional zones, press the C TRL key and keep it pressed.
    5. One after another, click the centroids or within the boundaries of the zones that you want to
    mark.

    PTVGROUP

    1141

    15.15.4.2 Setting active/passive zones


    The zones are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive zones with the mouse (see "Marking only active network objects" on page 1005).
    Tip: Alternatively, you can mark a zone by searching for it (see "Finding network objects
    in the network" on page 999) or by selecting the respective row in the list of zones (see
    "Selecting list sections" on page 2319).
    15.15.4.2 Setting active/passive zones
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.15.5 Editing the attribute values of zones


    You can edit the attribute values of one zone, all marked zones or all (active) zones.
    15.15.5.1 Editing the attribute values of a zone
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Zones button.


    3. In the network, double-click the centroid or within the boundary of the zone whose attribute
    values you want to edit.
    The Edit zone window opens.
    Tip: If the zone is marked, you can also call the Edit zone window via the context
    menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of zones" on page
    1137).
    5. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of zones in the Quick view window or in the list of the network object type (see "Quick view window" on page 810 and
    "Working with lists" on page 2299).
    15.15.5.2 Editing the attribute values of marked zones
    1. Mark the desired zones whose attribute values you want to edit (see "Marking zones" on
    page 1141).

    1142

    PTVGROUP

    15.15.5.3 Editing the attribute values of all or all active zones


    The selected zones are marked.
    2. Press the ENTER key.
    The Multi-edit nodes: <Number> objects window opens.
    Tip: You can also call the Multi-edit zones: <Number> objects window via the context menu> entry Edit or double-click the last zone that you mark.
    3. Edit the values of the desired attributes (see "Properties and options of zones" on page
    1137 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.15.5.3 Editing the attribute values of all or all active zones
    Note: If there are no passive zones in the network, all zones are edited. Markings of
    zones are ignored.
    1. If required, set the zones active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit zones window opens.
    4. Select whether you want to edit the attribute values of all zones or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active zones will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of zones" on page
    1137 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.

    PTVGROUP

    1143

    15.15.5.4 Displaying the attribute values of a zone in a column chart


    15.15.5.4 Displaying the attribute values of a zone in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.15.6 Editing the boundary of a zone


    A detailed description on how to edit the shape of a zone boundary is given for all polygonal
    network objects (see "Managing boundaries of polygonal network objects" on page 1042).

    15.15.7 Deleting the boundaries of several zones


    You can delete the read in or edited boundaries of all or all active zones.
    1. If required, set the zones active, whose boundaries you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    3. Select the Initialize boundaries entry.
    The Multi-edit zones window opens.
    Tip: If the network object type Zones has been selected, you can also call the Multiedit Zones window via the Edit> Initialize boundaries menu.
    4. Make sure that the Special functions tab has been selected.
    5. Specify whether you want to delete the boundaries of all zones or all active zones.
    Element

    Description

    Only active ones

    If the option has been selected, only active zones will be taken
    into account.

    6. Click the Initialize boundaries button.


    A query opens.
    7. Confirm with OK.
    The boundaries are deleted.
    8. Click the Close button.

    15.15.8 Shifting the centroid of a zone


    1. In the Network window, click the

    1144

    Edit mode icon.

    PTVGROUP

    15.15.9 Splitting zones


    2. Click the Zones button.
    3. In the network, click the centroid that you want to shift and hold down the left mouse button.
    The mouse pointer changes into a cross.
    4. Drag the centroid of the zone to the desired position and release the left mouse button.

    Notes: If you press the ESC key while dragging, you can cancel the action and the centroid is reset to its original position.
    The new position of the centroid is saved. The location and expansion of the boundary
    remains unchanged.
    Tip: You can also change the position of the centroid by editing the coordinates of the
    zone (see "Zones: Basis tab" on page 1137).
    Notes: The centroid should lie within the zone boundary.
    The zone connectors are not adjusted automatically. You have to manually adjust the
    lengths of the connectors and the connector times (see "Managing connectors" on page
    1159).

    15.15.9 Splitting zones


    You can split an existing zone into to new zones.
    Note: If you want to generate three or more zones out of a zone, you need to repeat the
    split operation accordingly.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Zones button.


    3. In the network, click the centroid or within the boundary of the zone that you want to split.
    4. Press F8.
    The Enter split weights for demand matrices window opens.

    5. Make the desired settings.

    PTVGROUP

    1145

    15.15.9 Splitting zones


    Element

    Description

    Zone

    Number of the original zone (first field) and the new zones.
    The new zone numbers are assigned consecutively and numbered from the highest zone number in the network.
    You can overwrite the preset numbers later (see "Properties and
    options of zones" on page 1137).

    Origin weight

    Split factors which, for each new zone, determine the percentage
    of the production of the original total zone (suggested values: 0.5
    each, where 0.5 equals 50%).
    Note
    The split factors need to add up to 1.0 (per 100 % production).

    Destination weight Split factors which, for each new zone, determine the percentage
    of the attraction of the original total zone (suggested values: 0.5
    each, where 0.5 equals 50%).
    Note
    The split factors need to add up to 1.0 (per 100 % attraction).
    6. Confirm with OK.
    A query opens.
    7. Confirm with Yes or Yes for all.
    Element

    Description

    Yes

    The step indicated in the window is executed.

    Yes for all

    Assignment results, rows and columns in the matrix as well as


    connectors are deleted simultaneously.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    8. Confirm a further prompt if you have confirmed the previous prompt with Yes and an assignment result existed.
    The mouse pointer changes into a cross.
    9. In the network, click the position where you want to place the centroid of the first new zone.
    The Edit zone window opens.
    10. In the different tabs, enter the desired data (see "Properties and options of zones" on page
    1137).
    11. Confirm with OK.

    1146

    PTVGROUP

    15.15.10 Aggregating marked or active zones to one zone


    Note: If you close the window with Cancel, your modifications will be discarded and
    the standard settings will be applied.
    12. In the network, click the position where you want to place the centroid of the second new
    zone.
    The Edit zone window opens.
    13. Enter the desired data (see "Properties and options of zones" on page 1137).
    Note: By default, for each new zone, the type and the AddValues of the split zone are
    used.
    14. Confirm with OK.
    Note: If you close the window with Cancel, your modifications will be discarded and
    the standard settings will be applied.
    The existing zone is deleted and the centroids of the new zones are inserted.
    Notes: For each new zone, you have to insert the centroid only. You can specify the zone
    boundary later (see "Managing boundaries of polygonal network objects" on page 1042).
    The connectors of the split zone are used for each new zone.
    For each new zone, the demand matrix is adjusted according to the split factors (see
    "Modeling demand" on page 1606).

    15.15.10 Aggregating marked or active zones to one zone


    There are different possibilities to aggregate multiple zones to one zone.
    Aggregating marked zones to one zone
    Aggregating all active zones to one zone
    15.15.10.1 Aggregating marked zones to one zone
    1. Mark minimum two zones that you want to aggregate (see "Marking zones" on page 1141).
    The selected zones are marked.
    2. Right-click the Zones button.
    The Zones context menu opens.
    3. Select the Aggregate marked zones entry.
    A query opens.
    Tip: The functionality is also provided in the Edit> Aggregate marked zones menu.

    PTVGROUP

    1147

    15.15.10.2 Aggregating all active zones to one zone


    Note: If all zones are active, you have to confirm an additional prompt with OK, before
    proceeding with step 5.
    4. Confirm with Yes or Yes for all.
    Element

    Description

    Yes

    The displayed step is executed.

    Yes for all

    Assignment results, rows and columns in the matrix as well as


    connectors are deleted simultaneously.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    5. Confirm another prompt if you have confirmed the previous prompt with Yes and an assignment result was available.
    The Edit zone window opens.
    6. Enter the desired data (see "Properties and options of zones" on page 1137).
    Note: By default, the type of the aggregated zone is set to 0 and the distribution type
    for connectors to absolute.
    7. Confirm with OK.
    Note: If you close the window with Cancel, your modifications will be discarded and
    the standard settings will be applied.
    The new aggregated zone is inserted.
    Notes: The centroid of the new zone is automatically set to the geometric centroid of the
    centroids of the original zones.
    The zone boundary of the new zone combines all boundaries of the original zones.
    The demand data and the AddValues of the original zones are added up.
    All connecting nodes (nodes via which the zone is connected to the network) are transferred.
    15.15.10.2 Aggregating all active zones to one zone
    You can aggregate all currently active zones to one zone.
    1. If required, set at least two zones active, which you want to aggregate to one zone, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or

    1148

    PTVGROUP

    15.15.10.2 Aggregating all active zones to one zone


    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, click the Zones button.
    3. Press F7.
    A query opens.
    Tip: The functionality is also provided in menu Edit> Aggregate active zones.
    Note: If all zones are active, you have to confirm an additional prompt with OK, before
    proceeding with step 5.
    4. Confirm with Yes or Yes for all.
    Element

    Description

    Yes

    The displayed step is executed.

    Yes for all

    Assignment results, rows and columns in the matrix as well as


    connectors are deleted simultaneously.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    5. Confirm another prompt if you have confirmed the previous prompt with Yes and an assignment result was available.
    The Edit zone window opens.
    6. Enter the desired data (see "Properties and options of zones" on page 1137).
    Note: By default, the type of the aggregated zone is set to 0 and the distribution type
    for connectors to absolute.
    7. Confirm with OK.
    Note: If you close the window with Cancel, your modifications will be discarded and
    the standard settings will be applied.
    The new aggregated zone is inserted.

    PTVGROUP

    1149

    15.15.11 Aggregating zones based on main zones


    Notes: The centroid of the new zone is automatically set to the geometric centroid of the
    centroids of the original zones.
    You can specify the zone boundary later (see "Managing boundaries of polygonal network objects" on page 1042).
    The demand data and the AddValues of the original zones are added up.
    All connecting nodes (nodes via which the zone is connected to the network) are transferred.

    15.15.11 Aggregating zones based on main zones


    You can aggregate zones based on their allocation to main zones (see "Managing main
    zones" on page 1194). All or all active zones, which are allocated to a main zone, are then
    aggregated to a new zone and all previously aggregated zones are deleted. This way, you
    can generate an assignment-enabled model for main zones.
    Notes: At least one main zone needs to be in the network.
    The aggregation generates as many new zones as there are main zones in the network.
    This is not the case if, in the network, there are zones which are not allocated to a main
    zone. These will not be aggregated and remain in the network.
    1. If required, set the zones active, which you want to aggregate, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    3. Select the Aggregation of zones according to main zones entry.
    The Aggregation of zones according to main zones window opens.

    4. Make the desired settings.

    1150

    PTVGROUP

    15.15.11 Aggregating zones based on main zones


    Element

    Description

    Aggregation of
    active zones only

    If the option has been selected, only the active zones will be
    aggregated.

    Centroid positioning for new


    zones

    Use the centroid position of the main zone


    If the option has been selected, the centroids of the main zones
    are used for the new zones.
    Use the position calculated from the centroids of the aggregated zones
    If the option has been selected, the centroids are determined
    based on the centroids of the aggregated zones.

    Zone polygons for Note


    new zones
    If neither zones nor main zones have polygons, you can only
    select the Do not create zone polygons option.
    Use the main zone polygons
    If the option has been selected, the polygon of the main zone to
    which the aggregated zones were allocated is used for the newly
    created zone. If the main zone does not have a polygon or if the
    Aggregation of active zones only option has been selected and
    not all zones of a main zone are active, the polygon will be generated from the set union of the polygons of the aggregated zones.
    Fusion of the polygons of aggregated zones
    If the option has been selected, the polygon created by fusion of
    the aggregated zones is used for the newly created zone. If the
    aggregated zone do not have polygons, for the new zone, no polygons with be created either.
    Do not create zone polygons
    If the option has been selected, no polygon will be inserted for the
    newly created zones.
    5. Confirm with OK.
    The new zones are inserted and all aggregated zones are deleted.
    Notes: The new zones are numbers consecutively.
    During the aggregation the following will happen:
    In the case of demand matrices, the values or the zones to be aggregated are summed up and allocated to the new zone.
    In the case of skim matrices, the values of the zones to be aggregated are averaged.
    If a skim matrix is allocated to a demand segment with demand matrix, the mean
    value is generated according to this demand matrix. Otherwise the unweighted
    mean value is calculated (see "Calculating a main zone matrix from a zone matrix"
    on page 1808).

    PTVGROUP

    1151

    15.15.12 Generating zones

    15.15.12 Generating zones


    For all or all active nodes, you can generate zones and connectors in one step.
    1. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    2. Select the Generate entry.
    The Parameters: Generating zones window opens.

    3. Make the desired settings.


    Section

    Description

    Network statistics Display of the number of zones, nodes, stop areas, and served
    stop areas in the network, as well as information on how many of
    these are connected.
    Note
    Stop areas are considered connected, if a connected node is allocated to them (see "Managing stop areas" on page 1255).

    1152

    Generate zones
    for active nodes
    only

    If the option has been selected, zones are generated for active
    nodes only.

    Zones

    Type of generated zones

    If the option has not been selected, zones are generated for all
    nodes.
    Tip
    If you just want to generate zones for nodes with stop areas or at
    served stop areas, set the node filter accordingly (see "Using filters to set network objects active or passive" on page 1008).

    PTVGROUP

    15.15.13 Setting zone labels to the centroids


    Section

    Description
    Zone type (0..9) for a categorization (see "Zones: General attributes" on page 1137)
    Minimum ZoneNo for generated zones
    Enter the lowest zone number to be generated.
    The default number is the highest zone number in the network +
    1.
    NewZoneNo. := MinZoneNo. 1 + NodeNo.
    Use the option to specify that each new zone number is generated from the lowest zone number 1+ number of the node for
    which the zone is to be generated. The value of the minimum
    zone number for generated zones then functions as an offset.
    Use name of the allocated stop
    Use the option to specify that zones generated for nodes with at
    least one stop area use the name of the respective stop as zone
    name.
    Note
    If the allocated stop has no name, the newly generated zones will
    have no names.

    Connectors

    Type of generated connectors


    The specified type is used to differentiate generated connectors
    from already existing ones (see "Properties and options of
    connectors" on page 1161).
    Connector length
    Distance between the zone centroid and the node (see "Connectors: Basis tab" on page 1162)
    Open connectors for the following TSys
    Use the button to select the transport systems of type PrT or
    PuTWalk, which are permitted on the newly created connectors
    (see "Connectors: Transport systems tab" on page 1163).
    Connector time for all permitted TSys
    Time which is needed to travel the distance between the zone
    centroid and the node, independent of the permitted transport system (see "Connectors: Transport systems tab" on page 1163).

    4. Confirm with OK.


    Zones and connectors are generated to all or all active nodes.

    15.15.13 Setting zone labels to the centroids


    You can move the position of the labels of all zones or all active zones to the geometrical centroid of their zone polygons.

    PTVGROUP

    1153

    15.15.14 Deleting enclaves from zones


    1. If required, set the zones active, whose boundary you want to set to the geometrical centroid, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    3. Select the Recalculate the centroids entry.
    The Multi-edit zones window opens.
    Tip: If the network object type Zones has been selected, you can also call the Multiedit zones window via the Edit> Recalculate the centroids menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to set the label of all zones or just the active zones to the geometrical centroid.
    Element

    Description

    Only active ones

    If the option has been selected, only active zones will be taken
    into account.

    6. Click the Recalculate the centroids from the polygons button.


    A query opens.
    7. Confirm with OK.
    The labels are set to the positions of the geometrical centroids.
    8. Click the Close button.

    15.15.14 Deleting enclaves from zones


    You can delete enclaves, i.e. "holes", from the surfaces of zones. These may occur if the boundaries do not match perfectly when aggregating zones.
    1. If required, set the zones active, whose enclaves you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    1154

    PTVGROUP

    15.15.15 Normalizing surfaces of zones


    3. Select the Delete enclaves entry.
    The Multi-edit zones window opens.
    Tip: If the network object type Zones has been selected, you can also call the Multiedit Zones window via the Edit> Delete enclaves menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to delete the enclaves of all zones or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active zones will be taken
    into account.

    6. Click the Delete enclaves button.


    A query opens.
    7. Confirm with OK.
    The enclaves are deleted.
    Click the Close button.

    15.15.15 Normalizing surfaces of zones


    You can normalize surfaces of zones. In this process, the sizes of the surfaces are calculated
    correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    1. If required, set the zones active whose surfaces you want to normalize via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    3. Select the Normalize surfaces entry.
    The Multi-edit zones window opens.
    Tip: If the network object type Zones has been selected, you can also call the Multiedit zones window via the Edit > Normalize surfaces menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to edit the surfaces of all zones or just the active ones.

    PTVGROUP

    1155

    15.15.16 Fuzzy alignment of zone surfaces


    Element

    Description

    Only active ones

    If the option has been selected, only active zones will be taken
    into account.

    6. Click the Normalize surfaces button.


    A query opens.
    7. Confirm with OK.
    The surfaces are normalized.
    Click the Close button.

    15.15.16 Fuzzy alignment of zone surfaces


    You can perform a fuzzy alignment for zone surfaces in the network. Then the points of a surface are moved, within a defined threshold, towards a reference surface. This allows you to
    remove unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy surface alignment (see "Importing Shapefiles" on page 2221).
    1. If required, set the zones active whose surfaces you want to fuzzy align via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, click the

    Edit mode icon.

    3. Right-click the Zones button.


    A context menu opens.
    4. Select the Fuzzy surface alignment entry.
    The Fuzzy surface alignment window opens.
    5. Make the desired changes.

    1156

    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.

    PTVGROUP

    15.15.17 Deleting zones


    Element

    Description
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    6. Confirm with OK.


    The desired surfaces in the network are aligned.

    15.15.17 Deleting zones


    There are several ways to delete zones.
    15.15.17.1 Deleting a zone
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Zones button.


    3. In the network, click the zone that you want to delete.
    4. Press the ENTER key.
    The zone is deleted.
    Tip: You can also delete the marked zone via the context menu> entry Delete.
    15.15.17.2 Deleting several marked zones
    1. Mark the zones that you want to delete (see "Selecting zones" on page 1141).
    The selected zones are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked zones via the context menu> entry Delete.
    3. Confirm with OK.
    The Delete zones window opens.
    4. Select which zones you want to delete.

    PTVGROUP

    1157

    15.15.17.3 Deleting active zones


    Element

    Description

    Yes

    The zone listed in the window will be deleted, and also all network
    objects with a reference to the zone.

    Yes for all

    All remaining marked zones will be deleted, and also the network
    objects with a reference to the zone.

    No

    Neither the zone listed in the window will be deleted, nor the network
    objects with a reference to the zone.

    No for all

    Neither of the remaining marked zones will be deleted, nor the network
    objects with a reference to the zone.

    Notes: If you click the Yes or No buttons, the query is displayed for the next zone number.
    With the Yes for all or No for all buttons, you only regard the remaining zones, for
    which neither Yes nor No has been clicked.
    The confirmed zones are deleted.
    15.15.17.3 Deleting active zones
    1. Select the zones, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, right-click the Zones button.
    The Zones context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type Zones has been selected, you can also delete all active zones
    via the Edit> Multi-delete menu or by pressing the D EL key.
    4. Confirm with OK.
    The Delete zones window opens.
    5. Select which zones you want to delete.

    1158

    PTVGROUP

    15.16 Managing OD pairs


    Element

    Description

    Yes

    The zone listed in the window will be deleted, and also all network
    objects with a reference to the zone.

    Yes for all

    All remaining active zones will be deleted, and also the network objects
    with a reference to the zone.

    No

    Neither the zone listed in the window will be deleted, nor the network
    objects with a reference to the zone.

    No for all

    Neither of the remaining active zones will be deleted, nor the network
    objects with a reference to the zone.

    Notes: If you click the Yes or No buttons, the query is displayed for the next zone number.
    With the Yes for all or No for all buttons, you only regard the remaining zones, for
    which neither Yes nor No has been clicked.
    The confirmed zones are deleted.

    15.16

    Managing OD pairs
    OD pairs exist between all zones of the network. The values of the matrices refer to one OD
    pair each (see Fundamentals: Chpt. 3.1.5 , page 57).
    You cannot edit OD pairs between zones interactively, but filter them, i.e. set them active or
    passive, and display them graphically (see "Exception: Filter for OD pairs" on page 1026).

    15.17

    Managing main OD pairs


    Main OD pairs exist between all main zones of the network. The values of the matrices refer to
    one OD pair each (see Fundamentals: Chpt. 3.1.8 , page 62).

    15.18

    Managing connectors
    Connectors connect zones to the link network. They represent the distance to be covered between a zones center of gravity and the nodes/stops of the network. For public transport
    demand, the zone has to be connected via a stop area with stop(s) allocated to a node (see
    Fundamentals: Chpt. 3.1.6 , page 58).

    15.18.1 Specifying standard values for connectors


    You can specify standard values for new connectors separately for each, PrT and PuT.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the Network> Connectors entry.

    PTVGROUP

    1159

    15.18.2 Creating a connector

    3. Enter the desired data.


    Element

    Description

    Connector speed

    Speed at which the distance between the zone centroid and the
    node is covered

    Round connector
    time to

    Use the list to select a value for the rounding of the connector
    time.

    4. Confirm with OK.

    15.18.2 Creating a connector


    Note: When creating a connector, the current settings of the standard values in the Edit>
    User Preferences> Network> Connectors menu are applied (see "Specifying standard values for connectors" on page 1159).
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Connectors button.


    3. Mark the objects (zone and node), between which you want to create the connector (see
    "Marking nodes" on page 1066 and "Marking zones" on page 1141).
    The Create connectors window opens.

    1160

    PTVGROUP

    15.18.3 Properties and options of connectors


    Notes: The sequence of the marking is of no significance as you can switch between
    the origin connector and the destination connector (zone node) with the Opp. dir.
    button of the Create connectors window.
    Origin connector: From zone To node
    Destination connector: From node To zone
    If you mark a zone first, all connectors to/from the node will be indicated by directed
    arrows in the network display.
    If you mark a node first, all connectors to/from the zone via the node will be indicated
    by directed arrows in the network display.
    4. Enter the desired data (see "Properties and options of connectors" on page 1161).
    5. Confirm with OK.
    The connector is inserted.
    Tip: You can also generate all connectors to and from nodes at once (see "Generating
    connectors" on page 1166).

    15.18.3 Properties and options of connectors


    Notes: Some of the described properties and options will only be displayed, if you have
    activated the respective add-on module (see "Displaying details on program and license"
    on page 886).
    Attribute values are highlighted that differ from those entered for the opposite direction.

    The upper section of the Create connectors or Edit connectors window contains the general
    attributes of the connector. In the lower section, you can edit specific attributes in various tabs.
    15.18.3.1 Connectors: General attributes

    PTVGROUP

    1161

    15.18.3.2 Connectors: Basis tab


    Element

    Description

    From zone / node


    To node / zone

    Display of the number of the node and of the zone linked by the
    connector

    Type

    The connector type (0...9) categorizes the connectors.

    Further connectors of the zone

    The section is displayed if several connectors have been defined at


    the From zone or at the To node, and you mark a connector with a
    double-click on the From zone or the To node.
    Use the
    zones.

    Opposite

    and

    buttons to switch between the To nodes or the To

    Use this button to switch between the origin connector and the destination connector.

    15.18.3.2 Connectors: Basis tab


    Element

    Description

    Length

    Distance between the zone centroid and the node


    The standard value is the direct distance between the zone centroid
    and the node.

    AddValue1-AddVa- Free attributes which you can use to enter additional values.
    lue3
    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes (see "Managing user-defined
    attributes" on page 973).
    Share PrT

    1162

    Share of the connector of 100 % PrT traffic volume per zone and
    direction
    Notes
    The attribute is only available, if the By shares option has been
    selected for origin and destination connectors for the distribution of
    the PrT demand of the zone (see "Zones: Connections tab" on page
    1138).
    For a zone, the total of the PrT connector shares per direction must
    amount to 100 %.

    PTVGROUP

    15.18.3.3 Connectors: Transport systems tab


    Element

    Description

    Share PuT

    Share of the connector of 100 % PuT traffic volume per zone and
    direction
    Notes
    The attribute is only available, if the By shares option has been
    selected for the distribution of the PuT demand of the zone (see
    "Zones: Connections tab" on page 1138).
    For a zone, the total of the PuT connector shares per direction must
    amount to 100 %.

    Queue length
    [PCU]

    Queue length in car units at the origin connector, which Visum determines after the first simulation phase of the blocking-back model (see
    "Blocking back model settings and calculation" on page 1925).
    The value of the destination connector remains unchanged.

    15.18.3.3 Connectors: Transport systems tab


    Element

    Description

    Permissible

    Use the option to specify which transport systems are permitted on


    the respective direction of the connector.

    TSys

    Transport systems relevant to connectors

    Type

    Type of the transport systems relevant to connectors (PrT or


    PuTWalk)

    t0

    Time which is needed per transport system in order to traverse the


    distance between zone centroid and node.
    Visum calculates the connector time from the length of the connector
    and the connector speed.
    Note
    You can specify the connector speed in the Edit> User
    Preferences> Network> Connectors menu (see "Specifying standard values for connectors" on page 1159).

    Volume

    Assignment result

    15.18.4 Finding a connector


    How to find connectors is described for all network objects (see "Finding network objects in the
    network" on page 999).

    15.18.5 Selecting connectors


    There are several ways to select connectors in order to edit them in another step.
    Marking connectors
    Setting active/passive connectors

    PTVGROUP

    1163

    15.18.5.1 Marking connectors


    15.18.5.1 Marking connectors
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Connectors button.


    You can continue as follows:
    In the network, click next to the connector in the desired direction.
    Click the connector node (node via which the zone is connected to the network) and
    the zone or vice versa.
    Notes: If you mark a zone first, all connectors to/from nodes will be indicated by directed arrows.
    If you mark a node first, all connectors to/from zones via the node will be indicated by
    directed arrows.
    The connector is marked.
    3. If you want to mark additional connectors, press the C TRL key and keep it pressed.
    4. One by one, click the connectors that you want to mark.
    The connectors are marked.
    Tip: Alternatively, you can mark a connector by searching for it (see "Finding a connector"
    on page 1163) or by selecting the respective row in the list of connectors (see "Selecting
    list sections" on page 2319).

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive connectors with the mouse (see "Marking only active network objects" on page
    1005).
    15.18.5.2 Setting active/passive connectors
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.18.6 Editing the attribute values of connectors


    You can edit the attribute values of one connector, all marked connectors or all (active) connectors.
    15.18.6.1 Editing the attribute values of a connector
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Connectors button.


    3. In the network, double-click the connector whose attribute values you want to edit.
    1164

    PTVGROUP

    15.18.6.2 Editing the attribute values of marked connectors


    The Edit connectors window opens.
    Tip: If the connector is marked, you can also call the Edit connectors window via the
    context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of connectors" on
    page 1161).
    5. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of connectors in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.18.6.2 Editing the attribute values of marked connectors
    1. Mark the desired connectors whose attribute values you want to edit (see "Setting active/passive connectors" on page 1164).
    The selected connectors are marked.
    2. Press the ENTER key.
    The Multi-edit connectors: <Number> objects window opens.
    Tip: You can also call theMulti-edit connectors: <Number> objects window via the
    context menu > entry Edit or double-click the last connector which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of connectors" on
    page 1161 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.18.6.3 Editing the attribute values of all or all active connectors
    Note: If there are no passive connectors in the network, all connectors are edited. Markings of connectors are ignored.
    1. If required, set the connectors active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected connectors are active.
    2. In the Network window, right-click the Connectors button.
    The Connectors context menu opens.
    PTVGROUP

    1165

    15.18.6.4 Displaying the attribute values of a connector in a column chart


    3. Select the Multi-editentry.
    The Multi-edit connectors window opens.
    4. Select whether you want to edit the attribute values of all connectors or just the active ones.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active connectors will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes in the Formula tab (see "Properties and options of
    connectors" on page 1161 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.18.6.4 Displaying the attribute values of a connector in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.18.7 Copying the attribute values of a connector to the opposite direction


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Connectors button.


    3. In the network, in the desired direction, click next to the connector whose attribute values
    you want to copy to the opposite direction.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Copy attributes to reverse direction entry.
    The values of all input attributes (except IDs) of the marked connector are transferred to the
    opposite direction.

    15.18.8 Generating connectors


    You can generate connectors automatically for all zones or nodes.
    1. If required, set the zone or nodes active for which you want to generate connectors, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones or nodes are active.
    2. In the Network window, right-click the Connectors button.
    The Connectors context menu opens.
    1166

    PTVGROUP

    15.18.8 Generating connectors


    3. Select the Generate entry.
    The Generate connectors window opens.

    4. Make the desired settings.


    Element

    Description

    PrT

    If the option has been selected, only connectors for the private
    transport are generated in this step.
    Note
    PrT connectors can only be connected to nodes with at least one
    link that is open to a PrT transport system.

    PuT

    If the option has been selected, only connectors for the public
    transport are generated in this step.
    Note
    PuT connectors can be created for the following nodes only:
    Nodes which have at least one link on which a transport system of the type PuTWalk or PuTAux is permitted
    Nodes to which a stop area has been allocated

    Maximum length
    (direct dist.)

    Maximum direct distance in kilometers between the nodes and


    the zone centroids
    Note
    Only connectors whose direct distance is below the specified
    value will be created.

    Maximum number In the current step, for each zone, the maximum specified number
    (current step)
    of connectors will be generated for the selected transport system
    type.
    Maximum total
    number per zone

    In total, for each zone, the maximum specified total number of


    connectors will be generated for the selected transport system
    type.

    Type of generated The specified type is used to differentiate generated connectors


    connectors
    from already existing ones (see "Properties and options of
    connectors" on page 1161).

    PTVGROUP

    1167

    15.18.9 Deleting connectors


    Notes: By default, generated connectors are valid for all transport systems that have
    been defined for the respective transport type (PrT/PuT) in the network.
    If more nodes are used as connector nodes than specified under Maximum number,
    the nodes with the shortest distance to/from the respective zone centroid will be used.
    5. Confirm with OK.
    The connectors are generated.

    15.18.9 Deleting connectors


    There are several ways to delete connectors.
    15.18.9.1 Deleting a connector
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Connectors button.


    3. In the network, click next to the connector that you want to delete.
    4. Press the DEL key.
    The connector is deleted.
    Note: You can also delete the marked connector via the context menu> entry Delete.
    15.18.9.2 Deleting several marked connectors
    1. Mark the connectors that you want to delete (see "Selecting connectors" on page 1163).
    The selected connectors are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked connectors via the context menu> entry Delete.
    3. Confirm with OK.
    The connectors are deleted.
    15.18.9.3 Deleting active connectors
    1. Select the connectors, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected connectors are active.
    2. In the Network window, right-click the Connectors button.

    1168

    PTVGROUP

    15.19 Managing main nodes


    The Connectors context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type Connectors has been selected, you can also delete all active
    connectors via menu Edit> Multi-delete or by pressing the D EL key.
    4. Confirm with OK.
    The connectors are deleted.

    15.19

    Managing main nodes


    Several nodes can be summarized to a main node. Each node can only be part of one main
    node. With the aid of main nodes, you can aggregate and evaluate nodes as desired (see Fundamentals: Chpt. 3.1.7 , page 60).

    15.19.1 Creating a main node


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Main nodes button.


    3. In the network, click the position where you want to insert the centroid of the main node.
    The Create main node window opens.

    4. In the upper section of the Create main node window, enter the desired data.

    PTVGROUP

    1169

    15.19.1 Creating a main node


    Element

    Description

    Number

    Unique number of the main node


    The main nodes are numbered consecutively. You can overwrite
    the preset number with a number that does not yet exist in the network.
    Note
    If you edit the main node number, existing assignment results will
    be deleted for all demand segments.

    Type

    The main node type categorizes the main node (0...99) for the
    definition of turn standards (see "Managing turns" on page 1090).
    The standard type is 0.

    Code

    Code of the main node

    Name

    Name of the main node

    5. In the Basis tab, enter the desired data.


    Element

    Description

    AddValue1-AddVa- Free attributes which you can use to enter additional values.
    lue3
    Tip
    If you want to allocate additional information to a network object,
    you can also create user-defined main node attributes (see
    "Managing user-defined attributes" on page 973).

    1170

    Capacity PrT

    Allowed hourly PrT capacity of the main node

    t0 PrT

    Private transport turning time in an unloaded network

    Position

    Coordinates of the centroid of the main node in the network


    The coordinates are assigned automatically according to the set
    coordinate system (see "Selecting a coordinate system" on page
    2207).
    The label of a main node is always displayed at the position of its
    centroid.

    PTVGROUP

    15.19.1 Creating a main node


    Element

    Description

    Control

    Use the drop-down list to select the control type of the main node:
    Unknown
    Uncontrolled
    Two-way stop
    Two-way yield
    Signalized
    All-way stop
    Roundabout

    Method for impedances at node

    Select the option to activate the drop-down list.


    Use the drop-down list to select a method for impedances for the
    main node which varies from the standard.
    Tip
    You can specify the standard method via menu Calculate> General procedure settings> entry PrT settings> entry Node impedances> list boxStandard method (see "Selecting VDFs for
    node types" on page 1894).

    6. If required, make the desired changes in the Time-varying attributes tab (see "Managing
    time-varying attributes" on page 979).
    7. Confirm with OK.
    The centroid of the main node is inserted. You can now insert a boundary and thus allocate
    partial nodes to the main node (all nodes with coordinates within the boundary).
    Note: The boundary is optional. It is used for the definition of the partial nodes and
    main turns via partial nodes (see "Managing main turns" on page 1188).
    You can continue as follows:
    If you do not want to allocate partial nodes to the main node, press the ESC key. The
    main node is then inserted as centroid without a boundary. You can define the boundary and allocate the partial nodes later (see "Creating a boundary" on page 1042 and
    "Allocating nodes to one or multiple main nodes" on page 1181).
    If you want to allocate nodes to the main node as partial nodes, proceed with the next
    step.
    8. Specify the boundary of the main node by inserting at least three polygon points in a counterclockwise direction in the desired positions.
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the face (see Fundamentals: Chpt. 3.5 , page 120).

    PTVGROUP

    1171

    15.19.2 Properties and options of main nodes

    Note: Even though you can also insert the polygon points in a clockwise direction,
    this would create a so-called negative face (=hole), which cannot be saved as boundary as no surface exists yet from which it can be cut out.
    9. Confirm the definition of the boundary with a right-click or press ENTER.
    The boundary is created and the polygon points are highlighted. The Edit shape window
    opens.
    Note: If you confirm the definition of the boundary with a right-click, the coordinates of
    the position of the click will not be saved as polygon point.
    10. If required, reshape the boundary (see "Editing polygon points" on page 1044).
    11. Confirm with OK.
    A query opens.
    12. Click Yes to confirm.
    The partial nodes that lie within the boundary are allocated to the main node, the main node is
    inserted in the network and the corresponding main turns are generated automatically (see
    "Managing main turns" on page 1188).
    Tip: If you want to insert the main node with a boundary yet without allocated partial
    nodes, click No when prompted by the query. You can also allocate the partial nodes
    later (see "Editing main node attributes in the list view" on page 1447 and "Allocating
    nodes to one or multiple main nodes" on page 1181).

    15.19.2 Properties and options of main nodes


    You can edit all main nodes and their attributes in the junction editor. The junction editor
    opens if you double-click the desired main node (see "Using the Junction editor" on page
    1435).

    15.19.3 Finding a main node


    How to find main nodes, is described for all network object types (see "Finding network objects
    in the network" on page 999).

    1172

    PTVGROUP

    15.19.4 Selecting main nodes

    15.19.4 Selecting main nodes


    There are several ways to select main nodes in order to edit them in another step.
    Marking main nodes
    Setting main nodes active/passive
    15.19.4.1 Marking main nodes
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main nodes button.


    3. In the network, click the centroid or within the boundary of the main node.
    The main node is marked.
    4. If you want to mark additional main nodes, press the C TRL key and keep it pressed.
    5. One after another, click the centroids or within the boundaries of the main nodes that you
    want to mark.
    The main nodes are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive main nodes with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a main node by searching for it (see "Finding a main
    node" on page 1172) or by selecting the respective row in the list of main nodes (see
    "Selecting list sections" on page 2319).
    15.19.4.2 Setting main nodes active/passive
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.19.5 Editing the attribute values of main nodes


    You can edit the attribute values of one main node, all marked main nodes or all (active) main
    nodes.
    15.19.5.1 Editing the attribute values of one main node
    You can edit the attribute values of single main nodes in the junction editor or edit the attribute
    values of all or all active main nodes (see "Using the Junction editor" on page 1435).
    15.19.5.2 Editing the attribute values of marked main nodes
    1. Mark the main nodes whose attribute values you want to edit (see "Marking main nodes" on
    page 1173).

    PTVGROUP

    1173

    15.19.5.3 Editing the attribute values of all or all active main nodes
    The selected main nodes are marked.
    2. Press the ENTER key.
    The Multi-edit main nodes: <Number> objects window opens.
    Tip: You can also call the Multi-edit main nodes: <Number> objects window via the
    context menu> entry Edit or double-click the main node that you mark.
    3. Edit the values of the desired attributes (see "Properties and options of main nodes" on
    page 1172 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.19.5.3 Editing the attribute values of all or all active main nodes
    Note: If there are no passive main nodes in the network, all main nodes are edited. Markings of main nodes are ignored.
    1. If required, set the main nodes active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit main nodes window opens.
    4. Select whether you want to edit the attribute values of all main nodes or just the active
    ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of main nodes" on
    page 1172 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.

    1174

    PTVGROUP

    15.19.5.4 Displaying the attribute values of a main node in a column chart


    15.19.5.4 Displaying the attribute values of a main node in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.19.6 Reshaping the boundary of a main node


    A detailed description on how to edit the shape of a main node boundary is given for all polygonal network objects (see "Managing boundaries of polygonal network objects" on page
    1042).

    15.19.7 Shifting the centroid of a main node


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main nodes button.


    3. In the network, click the centroid that you want to shift and hold down the left mouse button.
    The mouse pointer changes into a cross.
    4. Drag the centroid of the main node to the desired position and release the left mouse button.

    Notes: If you press the ESC key while dragging, you can cancel the action and the centroid is reset to its original position.
    The new position of the centroid is saved. The location and expansion of the boundary
    remains unchanged.
    Tip: You can also change the position of the centroid by editing the coordinates of the
    main node (see "Editing a main node in the Junction editor" on page 1446).
    Notes: The centroid should lie within the boundary of the main node.
    You cannot merge main nodes.

    15.19.8 Specifying major flows at main nodes


    You can specify the major flows of all or all active main nodes, i.e. the direction of the flow
    which has the right of way.
    The links of the main node with the top-ranking link types turn into major flows (see "Specifying
    link types" on page 1099).
    1. If required, set the main nodes active, whose major flows you want to specify, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter (see "Using filters to set network objects active or passive" on page 1008).
    PTVGROUP

    1175

    15.19.9 Setting the polygon allocation of main nodes


    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Major flows entry.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main nodes window via the Edit > Major flows menu.
    4. Make sure that the Special functions tab has been selected and the Major flows entry in
    the drop-down list.
    5. Decide whether you want to specify the major flows of all or all active main nodes.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active main nodes will be taken
    into account.

    6. Click the Specify major flows automatically button.


    A query opens.
    7. Confirm with OK.
    The major flows are specified.
    8. Click the Close button.

    15.19.9 Setting the polygon allocation of main nodes


    Prerequisite is that there are main nodes within a polygon (territory, zone or main zone).
    You can specify that a selected attribute receives the number of the territory, zone, or main
    zone in which the main node lies.
    1. If required, set the main nodes active, whose allocation you want to set, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Set polygon allocation entry.
    The Multi-edit main nodes window opens.

    1176

    PTVGROUP

    15.19.10 Updating the impedances at main nodes


    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main nodes window via the Edit> Set polygon allocation menu.
    4. Make sure that the Special functions tab and the Set polygon allocation entry in the dropdown list have been selected.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.
    If the option has not been selected, all main nodes will be
    taken into account.

    Object

    In the drop-down list, you can select the type of network object
    whose number you want to use as attribute value.

    Attribute to be set Use the drop-down list to select an attribute which shall store the
    number of the selected object.
    6. Click the Set button.
    The main nodes receive the number as attribute value.
    7. Click the Close button.

    15.19.10 Updating the impedances at main nodes


    As an example, you can use this feature to test the performance of main nodes. It is only effective for main nodes for which the impedance method ICA (Intersection Capacity Analysis) is
    specified (see "Calculating and exporting ICA" on page 1499).
    If you want to update the impedance of a main node that has a an associated SC, you can specify that the signal cycle and split optimization is carried out for the SC at the same time.
    1. If required, set the main nodes active, whose impedances you want to update. To do this,
    use
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Update main node impedances entry.
    The Multi-edit main nodes window opens. The Special functions tab is active. In the dropdown list the Update impedances at main node entry is selected.

    PTVGROUP

    1177

    15.19.11 Setting coordination groups for signal controls


    4. Specify whether you want to execute the function for all main nodes or only for active main
    nodes.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    5. If you want to execute the signal cycle and split optimization for main nodes with a SC,
    select the Signal cycle and split optimization option.
    Element

    Description

    Signal cycle and


    green time optimization

    If this option has been selected, Visum checks for all main nodes
    with a SC which optimization method has been specified for the
    SC (see "Properties and options of signal controls" on page
    1465). Dependent on the specified optimization method, no optimization, only the signal split optimization or the signal cycle and
    split optimization is carried out.

    6. Click the Update impedances at (main) node/signal cycle and split optimization button.
    A query opens.
    7. Confirm the query with OK.
    The impedances are updated. If the Signal cycle and split optimization option has been
    selected, for main nodes with SC either no optimization, only the signal split optimization or
    the signal cycle and split optimization is carried out. This depends on the optimization
    method specified for the SC.
    8. Click the Close button.
    Note: If a main node is allocated to a SC, impedances and optimizations are always calculated simultaneously for all nodes and main nodes that are allocated to this SC.

    15.19.11 Setting coordination groups for signal controls


    With this functionality, you can allocate the number of a coordination group to the SC of selected main nodes.
    1. Select the main nodes, whose SC you want to allocate numbers to, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    1178

    PTVGROUP

    15.19.12 Resetting the lane data of main nodes


    3. Select the Set coordination groups for SC entry.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main modes via the Edit > Set coordination groups for SC menu.
    4. Make sure that the Special functions tab has been selected and the Set coordination
    groups for SC entry in the drop-down list.
    5. Select whether you want to edit the SCs of all main nodes or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    6. Make the desired changes.


    Element

    Description

    Coordination
    group

    If the option has been selected, you can allocate a coordination


    group to the SCJ of all selected main nodes. In the drop-down list,
    select the desired coordination group.
    Tip
    You can create and edit signal coordination groups in menu
    Network> Signal coordination groups. (see "Managing signal
    coordination groups" on page 1497).

    Main node attribute

    If the option has been selected, the value of the selected attribute
    will be allocated to all signal coordination group numbers.
    Tip
    You can create user-defined attributes for this purpose (see
    "Managing user-defined attributes" on page 973).

    7. Click the Set button.


    The selected coordination group number or the value of the selected attribute is allocated
    to all selected signal controls.
    8. Click the Close button.
    Tips: You can also edit the Coordination group number attribute in the Signal control>
    SC list for the desired signal control.

    15.19.12 Resetting the lane data of main nodes


    Note: You can edit the lanes of individual main nodes in the junction editor (see "Using
    the Junction editor" on page 1435).

    PTVGROUP

    1179

    15.19.13 Deleting the boundaries of several main nodes


    1. If required, set the main nodes active whose lane data you want to reset to the standard
    values, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Lane definition entry.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main nodes window via the Edit> Lane definition menu.
    4. Make sure that the Special functions tab has been selected and the Lane definition entry
    in the drop-down list.
    5. Specify whether you want to reset the lane data of all nodes or all active main nodes.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    6. Click the Reset lane data button.


    A query opens.
    7. Confirm with OK.
    The lane data are reset.
    8. Click the Close button.

    15.19.13 Deleting the boundaries of several main nodes


    You can delete the read in or edited boundaries of all or all active main nodes.
    1. If required, set the main nodes active, whose boundaries you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Initialize boundaries entry.
    1180

    PTVGROUP

    15.19.14 Allocating nodes to one or multiple main nodes


    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main nodes window via the Edit> Initialize boundaries menu.
    4. Make sure that the Special functions tab has been selected and the Initialize boundaries
    entry in the drop-down list.
    5. Specify whether you want to initialize the boundaries of all or all active main nodes.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    6. Click the Initialize boundaries button.


    A query opens.
    7. Confirm with OK.
    The boundaries are deleted.
    8. Click the Close button.

    15.19.14 Allocating nodes to one or multiple main nodes


    You can allocate nodes to a main node by creating a boundary when inserting a main node
    (see "Creating a main node" on page 1169).
    You can change the allocation of the nodes later on if you allocate them via a list or modify the
    boundaries and allocate all nodes to the main node that lie within its boundary.
    Allocating nodes to a main node
    1. Make sure that the desired main node is displayed in the junction editor (see "Editing main
    node attributes in the list view" on page 1447).
    2. Click the Partial nodes attribute button.
    The Edit partial nodes of main node window opens. The left list displays the nodes that are
    allocated to the main node. The right list displays the nodes that are not allocated to any
    main node.
    3. Edit the allocations with the arrows.
    4. Confirm with OK.
    The allocations are changed.
    Reallocating partial nodes by modifying boundaries
    You can specify either for all or all active main nodes that the nodes which lie within the
    respective boundary are allocated to the main node.

    PTVGROUP

    1181

    15.19.15 Setting main node labels to the centroids


    If a node that is not allocated to a main node lies within several boundaries, it will be allocated
    to the first found boundary.
    If a node is located within the boundary of the main node it is allocated to, its allocation will not
    change.
    1. If required, set the main nodes active, to which you want to allocate nodes based on the
    main node boundaries, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select Recalculate node allocation from polygons.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main nodes window via the Edit> Recalculate node allocation from polygons menu.
    4. Make sure that the Special functions tab is selected and the Recalculate node allocation
    from polygons entry is displayed in the drop-down list.
    5. Specify whether you want to recalculate the allocation of the partial nodes of all or all active
    main nodes.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active main nodes will be taken
    into account.

    6. Click the Recalculate node allocation from polygons button.


    A query opens.
    7. Confirm with OK.
    The nodes are allocated based on the polygons.
    8. Click the Close button.
    Note: If you change the allocation of the partial nodes, any existing PrT assignment
    results will be discarded.

    15.19.15 Setting main node labels to the centroids


    You can move the position of the labels of all or all active main nodes automatically to the geometrical centroid of their main node polygons.

    1182

    PTVGROUP

    15.19.16 Deleting enclaves of main nodes


    1. If required, set the main nodes active, whose boundary you want to set to the geometrical
    centroid, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Recalculate the centroids entry.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main turns has been selected, you can also call the
    Multi-edit main turns window via the Edit> Recalculate the centroids menu.
    4. Make sure that the Special functions tab has been selected and the Recalculate the centroids from the polygons entry in the drop-down list.
    5. Select whether you want to set the label of all main zones or just the active ones to the geometrical centroid.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active main nodes will be taken
    into account.

    6. Click the Recalculate the centroids from the polygons button.


    A query opens.
    7. Confirm with OK.
    The labels are set to the positions of the geometrical centroids.
    8. Click the Close button.

    15.19.16 Deleting enclaves of main nodes


    You can delete enclaves, i.e. "holes", from the surfaces of main nodes.
    1. If required, set the main nodes active, whose enclaves you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    PTVGROUP

    1183

    15.19.17 Normalizing surfaces of main nodes


    3. Select the Delete enclaves entry.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit Main nodes window via the Edit> Delete enclaves menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to the enclaves of all main nodes or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    6. Click the Delete enclaves button.


    A query opens.
    7. Confirm with OK.
    The enclaves are deleted.
    8. Click the Close button.

    15.19.17 Normalizing surfaces of main nodes


    You can normalize surfaces of main nodes. In this process, the sizes of the surfaces are calculated correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    1. If required, set the main nodes active whose boundaries you want to normalize via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Normalize surfaces entry.
    The Multi-edit main nodes window opens.
    Tip: If the network object type Main nodes has been selected, you can also call the
    Multi-edit main nodes window via the Edit > Normalize surfaces menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to edit the surfaces of all main nodes or just the active ones.

    1184

    PTVGROUP

    15.19.18 Fuzzy alignment of main node surfaces


    Element

    Description

    Only active ones

    If the option has been selected, only active main nodes will be
    taken into account.

    6. Click the Normalize surfaces button.


    A query opens.
    7. Confirm with OK.
    The surfaces are normalized.
    Click the Close button.

    15.19.18 Fuzzy alignment of main node surfaces


    You can perform a fuzzy alignment for main node surfaces in the network. Then the points of a
    surface are moved, within a defined threshold, towards a reference surface. This allows you to
    remove unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy surface alignment (see "Importing Shapefiles" on page 2221).
    1. If required, set the main nodes active whose surfaces you want to fuzzy align via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, click the

    Edit mode icon.

    3. Right-click the Main nodes button.


    A context menu opens.
    4. Select the Fuzzy surface alignment entry.
    The Fuzzy surface alignment window opens.
    5. Make the desired changes.
    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.

    PTVGROUP

    1185

    15.19.19 Deleting main nodes


    Element

    Description
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    6. Confirm with OK.


    The desired surfaces in the network are aligned.

    15.19.19 Deleting main nodes


    There are several ways to delete main nodes.
    15.19.19.1 Deleting a main node
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main nodes button.


    3. In the network, click the main node that you want to delete.
    4. Press the ENTER key.
    The main node is deleted.
    Tip: You can also delete the marked main node via the context menu> entry Delete.
    15.19.19.2 Deleting several marked main nodes
    1. Mark the main nodes that you want to delete (see "Marking main nodes" on page 1173).
    The selected main nodes are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked main node via the context menu> entry Delete.
    3. Confirm with OK.
    The main nodes are deleted.
    15.19.19.3 Deleting active main nodes
    1. Select the main nodes, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).

    1186

    PTVGROUP

    15.19.20 Effects of cordon link changes


    The selected main nodes are active.
    2. In the Network window, right-click the Main nodes button.
    The Main nodes context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type Main nodes has been selected, you can also delete all active
    main nodes via the Edit> Multi-delete menu or by pressing the D EL key.
    4. Confirm with OK.
    The main nodes are deleted.

    15.19.20 Effects of cordon link changes


    Editing the cordon links (see Fundamentals: Chpt. 3.1.7.1 , page 60) of a main node (create or
    delete) or the allocations of nodes to main nodes (see "Finding a main node" on page 1172)
    can have an effect on the network and other network objects.
    However, modifications of inner links, nodes and turns, or the deletion of these objects do not
    have an effect on the network or other network objects.
    Modification

    Impact

    Creating a cordon link

    If you create a new cordon link, two new main turns will be generated from the new cordon link to each existing cordon link.
    Based on the turn standards, they provided with default values
    (see "Managing turn standards" on page 1090).

    Deleting a cordon link

    If you delete a cordon link, all associated main turns will also be
    deleted.

    PTVGROUP

    1187

    15.20 Managing main turns


    Modification

    Impact

    Adding a node to a
    main node

    Reassigning a node to a main node has the following effect:


    All links originating from this node which lead to nodes that
    were already assigned to a main node turn into inner links
    (see Fundamentals: Chpt. 3.1.7.1 , page 60).
    All links originating from this node which do not lead to
    nodes that were already assigned to a main node turn into
    new cordon links.
    Main turns between cordon links that were not edited persist.
    Main turns from new cordon links to existing cordon links
    will be generated and preset with data based on the turn
    standards. If no nodes were assigned to the main node beforehand, the turns will be preset with data based on shortest
    paths.
    Main turns from existing cordon links to inner links will be
    deleted.

    Removing nodes from a Removing a node from a main node has the following effect:
    main node
    All links originating from and leading to this node will turn
    into new cordon links.
    All links originating from this node which lead to nodes that
    are not assigned to a main node turn into outer links.
    Main turns between cordon links that were not edited persist.
    Main turns from new cordon links to existing cordon links
    will be generated and preset with data based on the turn
    standards.
    Main turns from existing cordon links to outer links will be
    deleted.

    15.20

    Managing main turns


    Main turns are constituent parts of main nodes. They are created automatically when a main
    node is defined (see "Managing main nodes" on page 1169). You can display main turns in
    the node editor and edit them manually.
    Each movement via a main node is represented by a main turn. Main turns possess the same
    attributes as turns.

    15.20.1 Creating a main turn


    If you insert a new main node, all main turns are created automatically (see "Creating a main
    node" on page 1169). Therefore, you cannot insert main turns manually, but edit them. Main
    turns are edited in the junction editor (see "Editing main turns in the Junction editor" on page
    1454).

    1188

    PTVGROUP

    15.20.2 Properties and options of main turns


    Notes: If a user creates a main node and Visum automatically generates main turns, the
    attributes t0, TSys-Set and Capacity are generated from shortest paths (see "Managing
    turn standards" on page 1090).
    If a user edits the network (for example creating a cordon link or a partial node) and
    Visum generates main turns, default turn values are assigned to the attributes t0, TSysSet and Capacity (see "Managing turn standards" on page 1090).

    15.20.2 Properties and options of main turns


    You can edit main turns and their attributes in the junction editor (see "Editing main turns in the
    Junction editor" on page 1454). To do so, select the main turns of a main node in the network
    (see "Selecting main turns" on page 1189).

    15.20.3 Finding a main turn


    You can only search for the main node associated to the main turn (see "Finding network
    objects in the network" on page 999).

    15.20.4 Selecting main turns


    There are several ways to select main turns in order to edit them in another step.
    Displaying main turns in the Junction editor
    Setting main turns active/passive
    15.20.4.1 Displaying main turns in the Junction editor
    1. In the Network window, click the

    Edit mode icon.

    2. Make sure that main nodes are displayed in the Network editor window (see "Editing the
    display and order of drawing settings for graphic layers" on page 2339).
    3. Click the Main turns button.
    4. Click one main node in the network.
    In the network you see the course of the first main turn of the main node (if required, zoom
    in the node). In the Quick view window you see selected attributes of the main turn.
    5. Click again the main node to display any additional main turns of the main node.
    6. If you want to display and edit all main turns of a main node in the Junction editor, doubleclick the main node.
    The Junction editor opens. A schematic view of the main node is displayed. Below you see a
    list of all main turns of the main node (see "Editing main turns in the Junction editor" on page
    1454).

    15.20.5 Setting main turns active/passive


    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page

    PTVGROUP

    1189

    15.20.6 Editing the attribute values of main turns


    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.20.6 Editing the attribute values of main turns


    You can edit the attribute values of single main turns in the junction editor or edit the attribute
    values of all or all active main turns (see "Using the Junction editor" on page 1435).
    15.20.6.1 Editing the attribute values of all or all active main turns
    Note: If there are no passive main turns in the network, all main turns are edited. Markings of main turns are ignored.
    1. If required, set the main turns active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main turns are active.
    2. In the Network window, right-click the Main turns button.
    The Main turns context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit main turns window opens.
    4. Select whether you want to edit the attribute values of all main turns or just the active ones.
    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active main turns will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Editing main turn attributes in the list view" on
    page 1456 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.20.6.2 Displaying the attribute values of a main turn in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).
    15.20.6.3 Allocating standard data or shortest path data to main turns
    1. Select the main turns, to which you want to allocate data, via

    1190

    PTVGROUP

    15.20.6.3 Allocating standard data or shortest path data to main turns


    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    The selected main turns are active.
    2. In the Network window, right-click the Main turns button.
    The Main turns context menu opens.
    3. Select the Standard values entry.
    The Multi-edit main turns window opens.
    Tip: If the network object type Main turns has been selected, you can also call the
    Multi-edit main turns window via the Edit > Standard values menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to allocate standard data to all main turns or just the active ones.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active main turns will be taken
    into account.

    6. Select the attributes whose values you want to overwrite.


    Note: Use the CTRL key if you want to select several attributes.
    Element

    Description

    Type number

    Number of the main turn type

    Capacity PrT

    Private transport capacity

    t0 PrT

    Private transport turning time in an unloaded network

    7. Click one of the following buttons:

    PTVGROUP

    1191

    15.20.6.4 Recalculating the transport system set of main turns


    Element

    Description

    Use standard
    values

    Use this button to overwrite the selected attributes with the standard values.
    Notes
    The standard values are set in menu Network> Turn standards ,
    where they can be edited as well (see "Managing turn standards"
    on page 1090).

    Use from shortest Use this button to overwrite the selected attributes with the values
    paths
    of the shortest paths.
    Notes
    When a main node is inserted, shortest paths are calculated for
    each pair of cordon links and each PrT transport system.
    If the entry cordon link is not connected to the exit cordon link, i.e.
    if, for none of the transport systems, there is a shortest path from
    the entry to the exit link exclusively via nodes of the main node
    (thus just via inner links), the main turn is preset as follow: t0 = infinite, capacity = 0 and TSys set = empty.
    If a shortest path is found for at least one transport system, the following attributes are assigned to the main turn:
    The Capacity of the main turn is the maximum capacity of the
    transport-specific shortest paths, whereas the Capacity of a
    shortest path is the minimum of the capacities of all its links
    and turns.
    Equally, t0 of the main turn results from the minimum value t0
    of the transport-specific shortest paths, whereas the value t0
    of a shortest path is the sum of the value t0 of all its links and
    turns.
    As for turns, the Type number is set automatically according
    to the geometry (angle between From Cordon Link and To
    Cordon Link).
    8. Click the Close button.
    15.20.6.4 Recalculating the transport system set of main turns
    You can redetermine the transport systems for all or all active main turns in the network. To
    each main turn, including U-turns, all transport systems that are permitted both on the respective From links and To links will then be allocated. This corresponds to the default setting that
    Visum applies when inserting new main turns. You can, for example, use this functionality after
    editing the transport systems of links.
    1. Select the desired main turns via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    1192

    PTVGROUP

    15.20.7 Calculating main turn lengths from shortest paths


    2. In the Network window, right-click the Main turns button.
    The Main turns context menu opens.
    3. In the Network menu, click the Multi-edit entry.
    The Multi-edit main turns window opens.
    4. Select the Special functions tab.
    5. Specify whether you want to recalculate the transport systems for all or all active main turns.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active main turns will be taken
    into account.

    6. In the list, select the Set TSysSet entry.


    7. Click the Calculate the PrT-TSysSet from the PrT-TSysSet of the links button.
    Note: This functionality is not provided for PuT transport systems.
    The PrT transport systems are allocated to the main turns.

    15.20.7 Calculating main turn lengths from shortest paths


    If you allocate main turns from shortest paths, you can save the lengths of the shortest paths to
    a target attribute.
    1. Select the main turns, whose lengths you want to determine, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main turns are active.
    2. In the Network window, right-click the Main turns button.
    The Main turns context menu opens.
    3. Select the Calculate length data from shortest paths.
    The Multi-edit main turns window opens.
    Tip: If the network object type Main turns has been selected, you can also call the
    Multi-edit main turns window via the Edit > Calculate length data from shortest
    paths.
    4. Make sure that the Special functions tab has been selected.
    5. Specify whether you want to calculate the lengths of all or all active main turns from shortest
    paths.

    PTVGROUP

    1193

    15.20.8 Deleting main turns


    Element

    Description

    Only active
    ones

    If the option has been selected, only active main turns will be taken
    into account.

    6. Use the button to select an Attribute which shall save the lengths from the shortest paths.
    7. Click the Calculate button.
    The calculated lengths are saved in the selected attribute.

    15.20.8 Deleting main turns


    Main turns cannot be deleted like other network objects. They are deleted automatically when
    the associated main node is deleted (see "Deleting main nodes" on page 1186).
    Notes: Like turns, main turns are specified per transport system. Consequently, you can
    "delete" a main turn for one, several, or all transport systems if you block it for each transport system.
    You can also block all main turns, if you click the Main turns button in the Network window and press the D EL key.

    15.21

    Managing main zones


    Main zones group multiple zones and allow aggregated evaluations. Each zone can only be
    part of one main zone. A main zone can, for example, illustrate a county which comprises
    several towns (see Fundamentals: Chpt. 3.1.8 , page 62).
    Note: You can aggregate zones according to their allocation to main zones and thus
    generate an assignment-enabled model for main zones (see "Aggregating zones based
    on main zones" on page 1150).

    15.21.1 Creating a main zone


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Main zones button.


    3. In the network, click the position where you want to insert the centroid of the main zone.
    The Create main zone window opens.
    4. Enter the desired data (see "Properties and options of main zones" on page 1195).
    5. Confirm with OK.
    The centroid of the main zone is inserted. You can now insert a boundary and thus allocate
    the partial zones (all zones with a centroid within the boundary).
    Note: The boundary is optional. It defines the partial zones and determines the surface of the main zone i.e. illustrates its extent.

    1194

    PTVGROUP

    15.21.2 Properties and options of main zones


    You can now proceed as follows.
    If you do not want to allocate partial zones to the main node, press the ESC key. The
    main zone is then inserted as centroid without a boundary. You can define the boundary and allocate the partial zones later (see "Creating a boundary" on page 1042).
    If you want to allocate partial zones to the main zone, proceed with the next step.
    6. Specify the boundary of the main zone by inserting at least three polygon points in a counterclockwise direction in the desired positions.
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the face (see Fundamentals: Chpt. 3.5 , page 120).

    Note: Even though you can also insert the polygon points in a clockwise direction,
    this would create a so-called negative face (=hole), which cannot be saved as boundary as no surface exists yet from which it can be cut out (see Fundamentals: Chpt.
    3.5 , page 120).
    7. Confirm the definition of the boundary with a right-click or press ENTER.
    The boundary is created and the polygon points are highlighted. The Edit shape window
    opens.
    Note: If you confirm the definition of the boundary with a right-click, the coordinates of
    the position of the click will not be saved as polygon point.
    8. If required, reshape the boundary (see "Editing polygon points" on page 1044).
    9. Confirm with OK.
    A query opens.
    10. Click Yes to confirm.
    The partial zones which lie within the boundary are allocated to the main zone and the main
    zones is inserted in the network.
    Tip: If you want to insert the main zone with a boundary yet without allocated partial network objects, click No when prompted by the query. In the Edit shape window, you can
    also allocate the partial zones later (see "Editing polygon points" on page 1044).

    15.21.2 Properties and options of main zones

    PTVGROUP

    1195

    15.21.2.1 Main zones: General attributes


    Note: Some of the described properties and options will only be displayed, if you have
    activated the respective add-on module (see "Displaying details on program and license"
    on page 886).

    The upper section of the Create main zone or Edit main zone window contains the general
    attributes of the main zone. In the lower section, you can edit specific attributes in various tabs.
    15.21.2.1 Main zones: General attributes
    Element

    Description

    Number

    Unique number of the main zone


    The main zones are numbered consecutively. You can overwrite the
    preset number with a number that does not yet exist in the network.

    Type

    The main zone type (0...9) categorizes the main zone. The standard
    type is 0.

    Code

    Code of the main zone

    Name

    Name of the main zone

    15.21.2.2 Main zones: Basis tab

    1196

    Element

    Description

    AddValue1AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you can
    also create user-defined attributes (see "Managing user-defined attributes" on page 973).

    Position

    Coordinates of the centroid of the main zone in the network

    PTVGROUP

    15.21.2.3 Main zones: Demand tab


    Element

    Description
    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).
    The label of a main zone is always displayed at the position of its centroid.

    Partial zones

    Display of the partial zones allocated to the main zone


    Note
    You can only edit the allocation of partial zones in the network display.
    Press the CTRL key and click the partial zone whose allocation you want
    to edit.

    15.21.2.3 Main zones: Demand tab


    In the OD demand tab, the current traffic volume of the main zone is displayed per direction
    and demand segment in the network, and totalized per PrT and PuT transport type (see "Modeling demand" on page 1606).

    15.21.3 Finding a main zone


    How to find main zones is described for all network objects (see "Finding network objects in
    the network" on page 999).

    15.21.4 Selecting main zones


    There are several ways to select main zones in order to edit them in another step.
    Marking main zones
    Setting main zones active/passive
    15.21.4.1 Marking main zones
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main zones button.


    3. In the network, click the centroid or within the boundary of the first main zone that you want
    to mark.
    The main zone is marked.
    4. If you want to mark additional main zones, press the C TRL key and keep it pressed.
    5. One after another, click the centroids or within the boundaries of the main zones that you
    want to mark.
    The main zones are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive main zones with the mouse (see "Marking only active network objects" on page
    1005).

    PTVGROUP

    1197

    15.21.4.2 Setting main zones active/passive

    Tip: Alternatively, you can mark a main zone by searching for it (see "Finding a main
    zone" on page 1197) or by selecting the respective row in the list of main zones (see
    "Selecting list sections" on page 2319).
    15.21.4.2 Setting main zones active/passive
    Network objects can be active or passive. They are only active if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.21.5 Editing the attribute values of main zones


    You can edit the attribute values of one main zone, all marked main zones or all (active) main
    zones.
    15.21.5.1 Editing the attribute values of a main zone
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main zones button.


    3. In the network, double-click the centroid or within the boundary of the main zone whose attribute values you want to edit.
    The Edit main zone window opens.
    Tip: If the main zone is marked, you can also call the Edit main zone window via the
    context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of main zones" on
    page 1195).
    5. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of main turns in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.21.5.2 Editing the attribute values of marked main zones
    1. Mark the desired main zones whose attribute values you want to edit (see "Marking main
    zones" on page 1197).
    The selected main zones are marked.
    2. Press the ENTER key.
    The Multi-edit main zones <Number> objects window opens.

    1198

    PTVGROUP

    15.21.5.3 Editing the attribute values of all or all active main zones
    Tip: You can also call the Multi-edit main zones: <Number> objects via the context
    menu> entry Edit or double-click the last main zone that you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of main zones" on
    page 1195 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.21.5.3 Editing the attribute values of all or all active main zones
    Note: If there are no passive main zones in the network, all main zones are edited. Markings of main zones are ignored.
    1. If required, set the main zones active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit main zones window opens.
    4. Select whether you want to edit the attribute values of all main zones or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main zones will be
    taken into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of main zones" on
    page 1195 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.21.5.4 Displaying the attribute values of a main zone in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    PTVGROUP

    1199

    15.21.6 Editing the boundary of a main zone

    15.21.6 Editing the boundary of a main zone


    A detailed description on how to edit the shape of a main zone boundary is given for all polygonal network objects (see "Managing boundaries of polygonal network objects" on page
    1042).

    15.21.7 Shifting the centroid of a main zone


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main zones button.


    3. In the network, click the centroid that you want to shift and hold down the left mouse button.
    The mouse pointer changes into a cross.
    4. Drag the centroid of the main zone to the desired position and release the left mouse button.

    Notes: If you press the ESC key while dragging, you can cancel the action and the centroid is reset to its original position.
    The new position of the centroid is saved. The location and expansion of the boundary
    remains unchanged.
    Tip: You can also change the position of the centroid by editing the coordinates of the
    main zone (see "Main zones: Basis tab" on page 1196).
    Notes: The centroid should lie within the main zone boundary.
    You can neither split nor merge main zones.

    15.21.8 Deleting the boundaries of several main zones


    You can delete the read in or edited boundaries of all or all active main zones.
    1. Select the main zones, whose boundaries you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Initialize boundaries entry.
    1200

    PTVGROUP

    15.21.9 Moving main zone labels to the centroids


    The Multi-edit main zones window opens.
    Tip: If the network object type Main zones has been selected, you can also call the
    Multi-edit main zones window via the Edit> Initialize boundaries window.
    4. Make sure that the Special functions tab has been selected.
    5. Specify whether you want to delete the boundaries of all main zones or all active main
    zones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main zones will be
    taken into account.

    6. Click the Initialize boundaries button.


    A query opens.
    7. Confirm with OK.
    The boundaries are deleted.
    8. Click the Close button.

    15.21.9 Moving main zone labels to the centroids


    You can move the position of the labels of all or all active main zones automatically to the geometrical centroid of their main one polygons.
    1. Select the main zones whose label you want to set to the position of the geometrical centroid, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Recalculate the centroids entry.
    The Multi-edit main zones window opens.
    Tip: If the network object type Main zones has been selected, you can also call the
    Multi-edit main zones window via the Edit> Recalculate the centroids menu.
    4. Make sure that the Special functions tab has been selected.

    PTVGROUP

    1201

    15.21.10 Merging zone polygons


    5. Select whether you want to set the label of all main zones or just the active main zones to
    the geometrical centroid.
    Element

    Description

    Only active ones

    If the option has been selected, only active main zones will be
    taken into account.

    6. Click the Recalculate the centroids from the polygons button.


    A query opens.
    7. Confirm with OK.
    The labels are set to the positions of the geometrical centroids.
    8. Click the Close button.

    15.21.10 Merging zone polygons


    With this functionality you can merge the polygons of all or all active zones of a main zone or
    the polygons of all zones per main zone. For the main zones, the merged polygons of the allocated zones are used as new main zone polygon.
    This functionality is particularly useful if the allocation of the zones to main zones has been
    modified, for example in the zone lists or when reading in a network file, and the main zone
    polygons need to be updated.
    Note: Once the zone polygons have been merged, a main zone polygon can also have
    several faces if the polygons of the zone do not overlap beforehand.
    15.21.10.1 Merging the zone polygons of one main zone
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main zones button.


    3. In the network, double-click the centroid or within the boundary of the main zone whose
    zone polygons you want to merge.
    4. Right-click in the network display.
    The Main zones context menu opens.
    5. Select the Union of zone polygons entry.
    The polygons of the zones of the main zone are merged.
    15.21.10.2 Merging the zone polygons per main zone
    1. If required, set the main zones active, whose zone polygons you want to merge, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    1202

    PTVGROUP

    15.21.10.3 Deleting enclaves from main zones


    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Union of zone polygons entry.
    The Multi-edit main zones window opens.
    4. Click the Union of zone polygons button.
    A query opens.
    5. Confirm the query.
    The zone polygons are recalculated.
    15.21.10.3 Deleting enclaves from main zones
    You can delete enclaves, i.e. "holes", from the surfaces of main zones.
    1. If required, set the main zones active, whose enclaves you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Delete enclaves entry.
    The Multi-edit main zones window opens.
    Tip: If the network object type Main zones has been selected, you can also call the
    Multi-edit main zones window via the Edit> Delete enclaves window.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to delete the enclaves of all main zones or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main zones will be
    taken into account.

    6. Click the Delete enclaves button.


    A query opens.
    7. Confirm with OK.
    The enclaves are deleted.

    PTVGROUP

    1203

    15.21.11 Normalizing surfaces of main zones


    8. Click the Close button.

    15.21.11 Normalizing surfaces of main zones


    You can normalize surfaces of main zones. In this process, the sizes of the surfaces are calculated correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    1. If required, set the main zones active whose surfaces you want to normalize via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Normalize surfaces entry.
    The Multi-edit main zones window opens.
    Tip: If the network object type Main zones has been selected, you can also call the
    Multi-edit main zones window via the Edit > Normalize surfaces menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to edit the surfaces of all main zones or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main zones will be
    taken into account.

    6. Click the Normalize surfaces button.


    A query opens.
    7. Confirm with OK.
    The surfaces are normalized.
    Click the Close button.

    15.21.12 Fuzzy alignment of main zone surfaces


    You can perform a fuzzy alignment for main zone surfaces in the network. Then the points of a
    surface are moved, within a defined threshold, towards a reference surface. This allows you to
    remove unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy surface alignment (see "Importing Shapefiles" on page 2221).
    1. If required, set the main zones active whose surfaces you want to fuzzy align via

    1204

    PTVGROUP

    15.21.13 Deleting main zones


    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, click the

    Edit mode icon.

    3. Right-click the Main zones button.


    A context menu opens.
    4. Select the Fuzzy surface alignment entry.
    The Fuzzy surface alignment window opens.
    5. Make the desired changes.
    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    6. Confirm with OK.


    The desired surfaces in the network are aligned.

    15.21.13 Deleting main zones


    There are several ways to delete main zones.
    15.21.13.1 Deleting a main zone
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Main zones button.


    3. In the network, click the main zone that you want to delete.
    4. Press the ENTER key.
    The main zone is deleted.

    PTVGROUP

    1205

    15.21.13.2 Deleting several marked main zones


    Tip: You can also delete the marked main zone via the context menu> entry Delete.
    15.21.13.2 Deleting several marked main zones
    1. Mark the main zones that you want to delete (see "Marking main zones" on page 1197).
    The selected main zones are marked.
    2. Press the ENTER key.
    A query opens.
    Tip: You can also delete the marked main zone via the context menu> entry Delete.
    3. Confirm with OK.
    The main zones are deleted.
    15.21.13.3 Deleting all active main zones
    1. Select the main zones, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Main zones button.
    The Main zones context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type Main zones has been selected, you can also delete all active
    main zones via the Edit> Multi-delete menu or by pressing the D EL key.
    4. Confirm with OK.
    The main zones are deleted.

    15.22

    Managing territories
    Territories are network objects, which can be used for example, to illustrate districts or counties. Based on a polygon which defines the limit of the territory, PrT and PuT indicators can be
    determined for each territory (e.g. the driven service kilometers within a territory) (see Fundamentals: Chpt. 3.1.9 , page 63).

    15.22.1 Creating a territory


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Territories button.


    1206

    PTVGROUP

    15.22.1 Creating a territory


    3. In the network, click the position where you want to insert the centroid of the territory.
    The Create territory window opens.
    4. Enter the desired data (see "Properties and options of territories" on page 1208).
    5. Confirm with OK.
    The centroid of the territory is inserted. You can now create a boundary.
    Note: The boundary is optional. It allows a precise calculation of territory-related attributes.
    You can now proceed as follows.
    If you do not want to define a boundary for the territory, press the ESC key. The territory
    is then inserted as centroid without a boundary. You can specify the boundary later
    (see "Creating a boundary" on page 1042).
    If you want to define the boundary for the territory, proceed with the next step.
    6. Specify the boundary of the territory by inserting at least three polygon points in a counterclockwise direction in the desired positions.
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the surface (see Fundamentals: Chpt. 3.5.2 , page 124).

    Note: Even though you can also insert the polygon points in a clockwise direction,
    this would create a so-called negative face (=hole), which cannot be saved as boundary as no surface exists yet from which it can be cut out (see Fundamentals: Chpt.
    3.5 , page 120).
    7. Confirm the definition of the boundary with a right-click or press ENTER.
    The boundary is created and the polygon points are highlighted. The Edit shape window
    opens.
    Note: If you confirm the definition of the boundary with a right-click, the coordinates of
    the position of the click will not be saved as polygon point.
    8. If required, reshape the boundary (see "Editing polygon points" on page 1044).
    9. Confirm with OK.
    The territory is inserted in the network.
    PTVGROUP

    1207

    15.22.2 Properties and options of territories

    15.22.2 Properties and options of territories

    The upper section of the Create territory or Edit territory window contains the general attributes of the territory. In the lower section, you can edit specific attributes.
    15.22.2.1 Territories: General attributes
    Element

    Description

    Number

    Unique number of the territory


    The territories are numbered consecutively. You can overwrite the preset number with a number that does not yet exist in the network.

    Type

    The territory type categorizes the territory (0..9). The standard type is 0.

    Code

    Code of the territory

    Name

    Name of the territory

    15.22.2.2 Territories: Basis tab


    Element

    Description

    AddValue1AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you can also create
    user-defined attributes (see "Managing user-defined attributes" on page 973).

    Position

    Coordinates of the territory in the network


    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).
    Note
    The label of a territory is always displayed at the position of its centroid.

    15.22.3 Finding a territory


    How to find territories is described for all network objects (see "Finding network objects in the
    network" on page 999).
    1208

    PTVGROUP

    15.22.4 Selecting territories

    15.22.4 Selecting territories


    There are several ways to select territories in order to edit them in another step.
    Marking territories
    Setting territories active/passive
    15.22.4.1 Marking territories
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Territories button.


    3. In the network, click the first centroid or within the boundary of the first territory that you want
    to mark.
    The territory is marked.
    4. If you want to mark additional territories, press the C TRL key and keep it pressed.
    5. One after another, click the centroids or within the boundaries of the territories that you want
    to mark.
    The territories are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive territories with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a territory by searching for it (see "Finding a territory" on
    page 1208) or by selecting the respective row in the list of territories (see "Selecting list
    sections" on page 2319).
    15.22.4.2 Setting territories active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.22.5 Editing the attribute values of territories


    You can edit the attribute values of one territory, all marked territories or all (active) main territories.
    15.22.5.1 Editing the attribute values of a territory
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Territories button.

    PTVGROUP

    1209

    15.22.5.2 Editing the attribute values of marked territories


    3. In the network, double-click the centroid or within the boundary of the territory whose attribute values you want to edit.
    The Edit territory window opens.
    Tip: If the territory is marked, you can also call the Edit territory window via the context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of territories" on page
    1208).
    5. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of territories in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.22.5.2 Editing the attribute values of marked territories
    1. Mark the desired territories whose attribute values you want to edit (see "Marking territories"
    on page 1209).
    The selected territories are marked.
    2. Press the ENTER key.
    The Multi-edit territories: <Number> objects window opens.
    Tip: You can also call the Multi-edit territories: <Number> objects window via the
    context menu > entry Edit or double-click the last territory which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of territories" on page
    1208 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.22.5.3 Editing the attribute values of all or all active territories
    Note: If there are no passive territories in the network, all territories are edited. Markings
    of territories are ignored.
    1. If required, set the territories active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected territories are active.

    1210

    PTVGROUP

    15.22.5.4 Displaying the attribute values of a territory in a column chart


    2. In the Network window, right-click the Territories button.
    The Territories context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit territories window opens.
    4. Select whether you want to edit the attribute values of all territories or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active territories will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of territories" on page
    1208 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.22.5.4 Displaying the attribute values of a territory in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.22.6 Editing the shape of a territory boundary


    A detailed description on how to edit the shape of a territory boundary is given for all polygonal network objects (see "Creating a boundary" on page 1042).

    15.22.7 Shifting the centroid of a territory


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Territories button.


    3. In the network, click the centroid that you want to shift and hold down the left mouse button.
    The mouse pointer changes into a cross.
    4. Drag the centroid of the territory to the desired position and release the left mouse button.

    Notes: If you press the ESC key while dragging, you can cancel the action and the centroid is reset to its original position.
    The new position of the centroid is saved. The location and expansion of the boundary
    remains unchanged.

    PTVGROUP

    1211

    15.22.8 Aggregating marked or active territories to one territory

    Tip: You can also change the position of the centroid by editing the coordinates of the territory (see "Territories: Basis tab" on page 1208).
    Note: The centroid should lie within the territory boundary.

    15.22.8 Aggregating marked or active territories to one territory


    There are different possibilities to aggregate multiple territories to one territory.
    Aggregating marked territories to one territory
    Aggregating all active territories to one territory
    15.22.8.1 Aggregating marked territories to one territory
    1. Mark minimum two territories that you want to aggregate (see "Marking territories" on page
    1209).
    The selected territories are marked.
    2. Right-click the Territories button.
    The Territories context menu opens.
    3. Select the Aggregate marked territories entry.
    4. A query opens.
    Tip: The functionality is also provided in the Edit> Aggregate marked territories
    menu.
    Note: If all territories are active, you have to confirm an additional prompt with OK,
    before proceeding with step 5.
    5. Confirm with Yes or Yes for all.
    Element

    Description

    Yes

    The displayed step is executed.

    Yes for all

    The results are deleted.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    6. Confirm another prompt if you have confirmed the previous prompt with Yes and an assignment result was available.
    The Edit territory window opens.
    7. Enter the desired data (see "Editing the attribute values of territories" on page 1209).
    1212

    PTVGROUP

    15.22.8.2 Aggregating all active territories to one territory


    8. Confirm with OK.
    Note: If you close the window with Cancel, your modifications will be discarded and
    the standard settings will be applied.
    The new aggregated territory is inserted.
    Notes: The centroid of the new territory is automatically set to the geometric centroid of
    the centroids of the original territories.
    The boundary of the new territory combines all boundaries of the old territories.
    15.22.8.2 Aggregating all active territories to one territory
    You can aggregate all currently active territories to one territory.
    1. If required, set at least two territories active which you want to aggregate to one territory via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected territories are active.
    2. In the Network window, click the Territories button.
    3. Press F7.
    A query opens.
    Tip: The functionality is also provided in the Edit> Aggregate active territories
    menu.
    Note: If all territories are active, you have to confirm an additional prompt with OK,
    before proceeding with step 5.
    4. Confirm with Yes or Yes for all.
    Element

    Description

    Yes

    The displayed step is executed.

    Yes for all

    The results are deleted.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    5. Confirm another prompt if you have confirmed the previous prompt with Yes and a calculation result was available.

    PTVGROUP

    1213

    15.22.9 Setting territory labels to the centroids


    The Edit territory window opens.
    6. Enter the desired data (see "Properties and options of territories" on page 1208).
    7. Confirm with OK.
    Note: If you close the window with Cancel, your modifications will be discarded and
    the standard settings will be applied.
    The new aggregated territory is inserted.
    Notes: The centroid of the new territory is automatically set to the geometric centroid of
    the centroids of the original territories.
    The boundary of the new territory combines all boundaries of the old territories.

    15.22.9 Setting territory labels to the centroids


    You can move the position of the labels of all territories or all active territories automatically to
    the geometrical centroid of their territory polygons.
    1. If required, set the territories active, whose boundary you want to set to the geometrical centroid, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected territories are active.
    2. In the Network window, right-click the Territories button.
    The Territories context menu opens.
    3. Select the Recalculate the centroids entry.
    The Multi-edit territories window opens.
    Tip: If the network object type Territories has been selected, you can also call the
    Multi-edit territories window via the Edit> Recalculate the centroids menu.
    4. Make sure that the Special functions tab has been selected and the Recalculate the centroids from the polygons entry in the drop-down list.
    5. Select whether you want to set the label of all territories or just the active territories to the
    geometrical centroid.
    Element

    Description

    Only active ones

    If the option has been selected, only active territories will be taken
    into account.

    6. Click the Recalculate the centroids from the polygons button.


    1214

    PTVGROUP

    15.22.10 Deleting enclaves from territories


    A query opens.
    7. Confirm with OK.
    The labels are set to the positions of the geometrical centroids.
    8. Click the Close button.

    15.22.10 Deleting enclaves from territories


    You can delete enclaves, i.e. "holes", from the surfaces of territories.
    1. If required, set the territories active, whose enclaves you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected main zones are active.
    2. In the Network window, right-click the Territories button.
    The Territories context menu opens.
    3. Select the Delete enclaves entry.
    The Multi-edit territories window opens.
    Tip: If the network object type Territories has been selected, you can also call the
    Multi-edit territories window via the Edit> Delete enclaves menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to delete the enclaves of all territories or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active territories will be taken
    into account.

    6. Click the Delete enclaves button.


    A query opens.
    7. Confirm with OK.
    The enclaves are deleted.
    8. Click the Close button.

    15.22.11 Normalizing surfaces of territories


    You can normalize surfaces of territories. In this process, the sizes of the surfaces are calculated correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    1. If required, set the territories active whose surfaces you want to normalize via

    PTVGROUP

    1215

    15.22.12 Fuzzy alignment of territory surfaces


    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected territories are active.
    2. In the Network window, right-click the Territories button.
    The Territories context menu opens.
    3. Select the Normalize surfaces entry.
    The Multi-edit territories window opens.
    Tip: If the network object type Territories has been selected, you can also call the
    Multi-edit territories window via the Edit >Normalize surfaces menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to normalize the surfaces of all territories or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active territories will be taken
    into account.

    6. Click the Normalize surfaces button.


    A query opens.
    7. Confirm with OK.
    The surfaces are normalized.
    Click the Close button.

    15.22.12 Fuzzy alignment of territory surfaces


    You can perform a fuzzy alignment for territory surfaces in the network. Then the points of a surface are moved, within a defined threshold, towards a reference surface. This allows you to
    remove unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy surface alignment (see "Importing Shapefiles" on page 2221).
    1. If required, set the territories active whose surfaces you want to fuzzy align via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected territories are active.
    2. In the Network window, click the

    1216

    Edit mode icon.

    PTVGROUP

    15.22.13 Deleting territories


    3. Right-click the Territories button.
    A context menu opens.
    4. Select the Fuzzy surface alignment entry.
    The Fuzzy surface alignment window opens.
    5. Make the desired changes.
    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    6. Confirm with OK.


    The desired surfaces in the network are aligned.

    15.22.13 Deleting territories


    There are several ways to delete territories.
    15.22.13.1 Deleting a territory
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Territories button.


    3. In the network, click the territory that you want to delete.
    4. Press the DEL key.
    The territory is deleted.
    Tip: You can also delete the marked territory via the context menu> entry Delete.
    15.22.13.2 Deleting several marked territories
    1. Mark the territories that you want to delete (see "Marking territories" on page 1209).
    The selected territories are marked.

    PTVGROUP

    1217

    15.22.13.3 Deleting the active territories


    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked territory via the context menu> entry Delete.
    3. Confirm with OK.
    The territories are deleted.
    15.22.13.3 Deleting the active territories
    1. Select the territories, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected territories are active.
    2. In the Network window, right-click the Territories button.
    The Territories context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type Territories has been selected, you can also delete all active
    territories via theEdit> Multi-delete menu or by pressing the D EL key.
    4. Confirm with OK.
    The territories are deleted.

    15.23

    Managing PrT paths and sets of paths


    For assignment calculation, paths are found between the origin and destination zone, and
    their volume is calculated. In the private transport, you can edit the paths and their volumes
    manually. A path is always allocated to a set of paths or to a demand segment and consists of
    several path items (see Fundamentals: Chpt. 3.1.10 , page 63).
    Note: In the network, you can display the volumes of paths based on bars (see "Configuring the display of a PrT path bar" on page 2386).

    15.23.1 Creating a path set


    1. In the Network window, click the

    Insert mode icon.

    2. Click the PrT paths button.


    The Create window opens.
    3. Select the Path set entry.
    1218

    PTVGROUP

    15.23.2 Properties and options of path sets


    4. Click in the network display.
    The Path set window opens.
    5. Enter the desired data (see "Properties and options of path sets" on page 1219).
    6. Confirm with OK.
    The path set is created.

    15.23.2 Properties and options of path sets

    The upper section of the Path set window contains the general attributes of the path set. In the
    lower section, you can edit specific attributes.
    15.23.2.1 PrT path sets: General attributes
    Element

    Description

    Number

    Unique number of the path set


    Note
    The path sets are numbered consecutively. You can overwrite the preset
    number with a number that does not yet exist in the network.

    Code

    Code of the path set

    Name

    Name of the path set

    15.23.2.2 PrT path sets: User-defined attributes


    In this tab, you can modify attribute values of user-defined attributes of path sets (see "Managing user-defined attributes" on page 973).

    15.23.3 Selecting path sets


    There are several ways to select path sets in order to edit them in another step.
    Marking a path set
    Marking several path sets
    Setting active/passive path sets

    PTVGROUP

    1219

    15.23.3.1 Marking a path set


    15.23.3.1 Marking a path set
    Note: You can only mark a path set in the network if at least one path, i.e. a course, has
    been allocated to the path set.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the PrT paths button.


    The Paths window opens.
    Note: Depending on the selected option, the name of the Paths/Path sets window
    changes.

    3. Make sure that the Path sets option has been selected.
    4. In the list, select a set of paths.
    Tip: You can also select the sought path set via the input field. To do this, enter the
    name of the path set in the field. The path set is selected in the list.
    All path courses of the path set are marked in the network.
    5. If required, click the Autozoom button.
    The network section is enlarged and the marked path set is positioned in the middle of the
    section.
    Notes: If you want to remove the previously marked path sets from the selection, click the
    Initialize button.
    You can also mark the path courses of a path set by clicking a node in the network which
    is traversed by a path or a path set.
    15.23.3.2 Marking several path sets
    Note: You can only mark path sets in the network if at least one path, i.e. a course, has
    been allocated to the path set.
    1220

    PTVGROUP

    15.23.3.3 Setting active/passive path sets

    1. In the Network window, click the

    Edit mode icon.

    2. Click the PrT paths button.


    The Paths window opens.
    Note: Depending on the selected option, the name of the Paths/Path sets window
    changes.
    3. Make sure that the Path sets option has been selected.
    4. Press the CTRL key and keep it pressed.
    5. One by one, click the path sets that you want to mark.
    All path courses of the selected path sets are marked in the network. The number of the path
    sets marked in the window is displayed in front of the bracket below the list, for example 2(4).
    15.23.3.3 Setting active/passive path sets
    Network objects can be active or passive. There are several possibilities to set path sets
    active.
    Via the path filter (see "Using filters to set network objects active or passive" on page
    1008)
    Note: The spatial selection of network objects of the path hierarchy (paths, path sets, path
    items) is not possible. You can, however, add or remove the network objects of these network object types to/from the selection in various different ways.
    With a click in the Spatial selection toolbar on the icons Include all objects into the spatial selection, Invert spatial selection or Remove all objects from the spatial selection
    (see "Setting network objects active/passive via the spatial selection" on page 1033)
    Edit IsInSelection attribute per network object, for example, in the list of the respective network object type. If you enter 1, the respective network object will be active, if you enter 0,
    it will be passive.

    15.23.4 Editing the attribute values of path sets


    You can edit the attribute values of one path set, all marked path sets or all (active) path sets.
    15.23.4.1 Editing the attribute values of one path set
    1. In the Network window, click the

    Edit mode icon.

    2. Click the PrT paths button.


    The Paths window opens.
    3. Make sure that the Path sets option has been selected.
    4. In the list, double-click the desired path set.
    The Path set window opens.
    PTVGROUP

    1221

    15.23.4.2 Editing the attribute values of marked path sets


    5. Edit the values of the desired attributes (see "Properties and options of path sets" on page
    1219).
    6. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of path sets in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.23.4.2 Editing the attribute values of marked path sets
    1. Mark the desired path sets whose attribute values you want to edit (see "Marking several
    path sets" on page 1220).
    2. Press the ENTER key.
    The Multi-edit path sets: <Number> objects window opens.
    Tip: You can also call the Multi-edit path sets: <Number> objects window via the
    context menu > entry Edit or double-click the last path sets which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of path sets" on page
    1219 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.23.4.3 Editing the attribute values of all or all active path sets
    Note: If there are no passive path sets in the network, all path sets are edited. Markings of
    path sets are ignored.
    1. If required, set the path sets active via filter criteria, whose attribute values you want to edit
    (see "Using filters to set network objects active or passive" on page 1008).
    The selected path sets are active.
    2. In the Network window, right-click the PrT paths button.
    The Paths context menu opens.
    3. Select the Multi-edit> Path sets entry.
    The Multi-edit path sets window opens.
    4. Select whether you want to edit the attribute values of all path sets or just the active ones.

    1222

    PTVGROUP

    15.23.4.4 Displaying the attribute values of a path set in a column chart


    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active path sets will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of path sets" on page
    1219 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.23.4.4 Displaying the attribute values of a path set in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.23.5 Deleting path sets


    There are several ways to delete path sets.
    Notes: If you delete a path set, all associated paths and path items will also be deleted.
    15.23.5.1 Deleting a path set
    1. Open the Path sets window (see "Opening the Paths window" on page 1228).
    2. Select the path set, which you want to delete.
    3. Press the DEL key.
    The path set is deleted.
    Tip: You can also delete the marked Path set via the context menu> entry Delete.
    15.23.5.2 Deleting several marked path sets
    1. Mark the path sets that you want to delete (see "Marking several path sets" on page 1220).
    The selected path sets are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked path sets via the context menu> entry Delete.
    3. Confirm with OK.
    The path sets are deleted.

    PTVGROUP

    1223

    15.23.5.3 Deleting all path sets


    15.23.5.3 Deleting all path sets
    1. In the Network window, right-click the PrT paths button.
    The Paths context menu opens.
    2. Select the Multi-edit> Path sets entry.
    A query opens.
    3. Confirm with OK.
    All path sets are deleted.

    15.23.6 Creating a PrT path


    Notes: Paths are generated automatically for each demand segment, if you calculate a
    PrT assignment. If you initialize the assignment, the paths generated this way will be deleted again.
    You can also insert paths manually and assign them to demand segments or path sets.
    Paths which are allocated to paths sets are not deleted when initializing assignments. If
    you manually insert paths which are assigned to demand segments, the attributes
    deviate (see "Properties and options of PrT paths" on page 1226). These paths will also
    be deleted if an assignment is initialized for the demand segment.
    1. In the Network window, click the

    Insert mode icon.

    2. Click the PrT paths button.


    The Create window opens.
    3. Select the Path entry.
    4. Click in the network display.
    The Selection of set of paths window opens.

    5. In the drop-down list, select the desired path set for which you want to create a path.
    Note: You can select demand segments or path sets. If you create a path for a
    demand segment (see "Properties and options of PrT paths" on page 1226), the path
    needs to start and end at a zone.
    6. Confirm with OK.
    The Create path window opens.
    7. Enter the desired data (see "Properties and options of PrT paths" on page 1226).
    8. Confirm with OK.
    1224

    PTVGROUP

    15.23.6 Creating a PrT path


    The Edit path shape window opens.
    9. Click the node or zone at which the path shall start and hold down the mouse button.
    Notes: A path needs to start and end at a node or at a zone. If the path starts at a
    node, it also has to end at a node. If it starts at a zone, it must end at a zone.
    Main nodes can also be items of paths. They can however only be selected via the
    partial nodes.
    10. Drag the mouse to the next zone or node via which the path shall run and release the
    mouse button.
    Note: If required, click the Autozoom button in the Edit path shape window, if you
    want to enlarge the section with the course of the path.
    11. If required, proceed in the same manner to create any other sections you wish to create.
    Note: If required, click the Undo button in the Edit path shape window, if you want to
    delete the last section of the path course.
    12. Drag the mouse to the desired endpoint of the path and release the mouse button.
    Tip: You can also drag the mouse from the first zone or node to the desired endpoint.
    The program will then suggest the best path based on the set search criterion (see
    "Paths: specifying parameters for the path search" on page 1225).
    13. Click the OK button in the Edit path shape window.
    The path is inserted.
    Note: You can edit the course of a path later (see "Editing the shape of a path course" on
    page 1232).
    Paths: specifying parameters for the path search
    1. In the Edit path shape window click the Parameters button.
    The Parameters: Path search window opens.

    2. Make the desired changes.


    PTVGROUP

    1225

    15.23.7 Properties and options of PrT paths

    Element

    Description

    Reference transport system

    Select the desired transport system

    Use also closed


    links for routing

    If the option has been selected, the links closed to the transport
    system will be taken into account, as if they were open to the
    transport system.

    Use also closed


    turns for routing

    If the option has been selected, the turns closed to the transport
    system will be taken into account, as if they were open to the
    transport system.

    Search criterion

    From the drop-down list, you can select a criterion for the path
    search. The search finds the best path each between two marked
    (fixed) points.
    Link length (direct distance)
    Direct distance link length from the origin to the destination stop
    point
    Link run time
    Is calculated from the transport system speed of the links
    Time from speed def. by link type
    Is calculated from the transport system speed specified for the
    respective link type
    Link length
    Calculated link length if not manually adjusted by the user

    3. Confirm with OK.

    15.23.7 Properties and options of PrT paths

    The upper section of the Create path or Edit path window contains the general attributes of
    the path. In the lower section, you can edit specific attributes.

    1226

    PTVGROUP

    15.23.7.1 Paths: General attributes (path of a path set)


    Notes: The Edit path window differs depending on whether it is allocated to a path set or
    a demand segment.
    If your network contains user-defined attributes for paths, they are only provided for paths
    of a path set and not for paths resulting from assignments.
    15.23.7.1 Paths: General attributes (path of a path set)
    Element

    Description

    Path set

    Number of the path set the path is allocated to


    Tip
    You can allocate the path to a different path set if you click the ? button.

    Number

    Unique number of the path


    Note
    The paths are numbered consecutively. You can overwrite the preset
    number with a number that does not yet exist in the network.

    From zone

    Number of the zone at which the path starts


    Note
    No number is displayed, if the path starts at a node.

    To zone

    Display of the zone at which the path ends


    Note
    No number is displayed, if the path ends at a node.

    15.23.7.2 Paths: General attributes (path of a demand segment)


    Element

    Description

    Demand segment Demand segment for which the path was determined
    From zone

    Number of the zone at which the path starts

    To zone

    Number of the zone at which the path ends

    Index

    Index number of the path

    15.23.7.3 Paths: Basis tab (path of a path set)


    Element

    Description

    Volume

    Display of the volume of the path


    Tip
    Negative values are also permitted, so that values can be subtracted.

    Length

    Display of the length of the path

    PTVGROUP

    1227

    15.23.7.4 Paths: Basis tab (path of a demand segment)


    Element

    Description

    Share of path set


    target

    Enter a share which shall be taken into account when distributing the
    matrix to paths (see "Distributing a matrix on paths" on page 1236)

    Share of path set

    Display of the actual (calculated) share of the volume of this path


    (see Fundamentals: Chpt. 3.1.10 , page 63)

    15.23.7.4 Paths: Basis tab (path of a demand segment)


    Element

    Description

    Volume

    Display of the volume of the path


    Tip
    You can edit the volume data. Negative values are also permitted, so
    that values can be subtracted.

    Impedance

    Display of the impedance of the path

    AddValue 1-3

    Display of the AddValues of the path

    Toll

    Display of the toll of the path

    15.23.8 Opening the Paths window


    The path to be edited is selected via the identically named window. In order to open the Paths
    window, proceed as follows:
    1. In the Network window, click the

    Edit mode icon.

    2. Click the PrT paths button.


    A new window opens.
    Note: Depending on the selected option, the name of the Paths/Path sets window
    changes.
    3. Make sure that the Paths option has been selected.

    1228

    PTVGROUP

    15.23.9 Selecting paths


    In the Paths window, the paths are displayed according to your selection.

    15.23.9 Selecting paths


    There are several ways to select a path in order to edit it in another step.
    Marking a path
    Marking several paths
    Setting paths active/passive
    15.23.9.1 Marking a path
    1. Open the Paths window (see "Opening the Paths window" on page 1228).

    2. If required, restrict the number of paths which is searched.


    Element

    Description

    Path sets/demand
    segments dropdown list

    Selection of a path set or demand segment


    Notes
    The paths which are allocated to the path set/demand segment
    are displayed.
    Manually inserted paths are issued per path set. Paths generated
    in assignments are issued per demand segment.

    Drop-down list

    You can restrict the display views to the following:


    All routes
    All routes are displayed.
    Flow bundle routes
    All routes of the currently displayed flow bundle are issued.
    Filter for OD pairs
    All routes of the current OD pair filter are displayed.

    PTVGROUP

    1229

    15.23.9.2 Marking several paths


    3. In the list, select a path with a left-click.
    Tip: You can also select the sought path via the input field. To do this, enter the name
    of the path in the field. The path is selected in the list.
    The course of the path is marked in the network.
    4. If required, click the Autozoom button.
    The network section is enlarged and the marked path is positioned in the middle of the section.
    Tips: Use the Initialize button if you want to remove the previously marked paths from the
    selection.
    You can also mark the path courses of a path set by clicking a node or zone which is traversed by a path.
    15.23.9.2 Marking several paths
    1. Open the Paths window (see "Opening the Paths window" on page 1228).
    2. Press the CTRL key and keep it pressed.
    3. One by one, click the paths that you want to mark.
    The selected paths are marked in the network. The number of the paths marked in the window
    is displayed in front of the bracket below the list, for example 1(11).
    Tip: You can also select paths in the Paths) list (see "Opening a list" on page 2299).
    15.23.9.3 Setting paths active/passive
    Network objects can be active or passive. There are several possibilities to set paths active.
    Via the path filter (see "Using filters to set network objects active or passive" on page
    1008)
    Note: The spatial selection of network objects of the path hierarchy (paths, path sets, path
    items) is not possible. You can, however, add or remove the network objects of these network object types to/from the selection in various different ways.
    With a click in the Spatial selection toolbar on the icons Include all objects into the spatial selection, Invert spatial selection or Remove all objects from the spatial selection
    (see "Setting network objects active/passive via the spatial selection" on page 1033)
    Edit IsInSelection attribute per network object, for example, in the list of the respective network object type. If you enter 1, the respective network object will be active, if you enter 0,
    it will be passive.

    15.23.10 Editing the attribute values of PrT paths


    You can edit the attribute values of one path, all marked paths or all (active) paths.

    1230

    PTVGROUP

    15.23.10.1 Editing the attribute values of a path


    15.23.10.1 Editing the attribute values of a path
    1. Open the Paths window (see "Opening the Paths window" on page 1228).
    2. In the list, double-click the desired path.
    The Edit path window opens.
    3. Edit the values of the desired attributes (see "Properties and options of PrT paths" on page
    1226).
    4. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of paths in the Quick view window or in the list of the network object type (see "Quick view window" on page 810 and
    "Working with lists" on page 2299).
    15.23.10.2 Editing the attribute values of marked paths
    1. Mark the desired paths whose attribute values you want to edit (see "Marking several
    paths" on page 1230).
    The selected paths are marked.
    2. Press the ENTER key.
    The Multi-edit paths: <Number> objects window opens.
    Tip: You can also call the Multi-edit paths: <Number> objects window via the context menu> entry Edit or double-click the last path that you mark.
    3. Edit the values of the desired attributes (see "Properties and options of PrT paths" on page
    1226 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.23.10.3 Editing the attribute values of all or all active paths
    Note: If there are no passive paths in the network, all paths are edited. Markings of paths
    are ignored.
    1. If required, set the paths active via filter criteria, whose attribute values you want to edit (see
    "Using filters to set network objects active or passive" on page 1008).
    The selected paths are active.
    2. In the Network window, right-click the PrT paths button.
    The Paths context menu opens.
    3. Select the Multi-edit > Paths entry.
    PTVGROUP

    1231

    15.23.10.4 Displaying the attribute values of a path in a column chart


    The Multi-edit paths window opens.
    4. Select whether you want to edit the attribute values of all paths or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active paths will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of PrT paths" on page
    1226 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.23.10.4 Displaying the attribute values of a path in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.23.11 Editing the shape of a path course


    Note: Please take notice of the rules for editing a course, which are equivalent to the
    ones for line routes (see "Basic rules: Editing a route course" on page 1340).
    1. Open the Paths window (see "Opening the Paths window" on page 1228).
    2. Select the path whose shape you want to edit.
    The path is marked.
    3. Right-click in the network display.
    A shortcut menu opens.
    4. Select the Edit shape entry.
    The Edit path shape window opens.
    5. Specify the parameters for the path search (see "Paths: specifying parameters for the path
    search" on page 1225).
    6. Edit the previous course by dragging the desired points of the course to new positions.
    7. Confirm with OK.
    The new course of the path is saved.

    15.23.12 Converting paths


    You can convert paths as follows (see Fundamentals: Chpt. 3.1.10 , page 63):

    1232

    PTVGROUP

    15.23.12.1 Converting a path


    From assignment result to path set
    From path set to assignment result
    From path set to path set
    From assignment result to assignment result
    15.23.12.1 Converting a path
    1. Select the path that you want to convert (see "Selecting paths" on page 1229).
    2. Right-click in the network display.
    A shortcut menu opens.
    3. Select the Convert entry.
    The Parameters: Convert paths window opens.

    4. Make the desired settings (see "Converting the paths of a path set or demand segment" on
    page 1233).
    5. Confirm with OK.
    The path is converted.
    15.23.12.2 Converting the paths of a path set or demand segment
    1. Select the paths that you want to convert (see "Selecting paths" on page 1229).
    2. Right-click in the network display.
    The PrT paths context menu opens.
    3. Select the Convert all entry.
    The Parameters: Convert paths window opens.
    Tip: You can also call the procedure via the Calculate> Procedure sequence> operation Convert paths menu.

    PTVGROUP

    1233

    15.23.12.2 Converting the paths of a path set or demand segment

    Note: The elements in the window differ depending on whether you called the window via the context menu or in the Procedure sequence window.
    4. Make the desired changes.
    Element

    Description

    Origin

    In the drop-down list, select the path set or demand segment, whose
    paths you want to convert.
    Note
    If you call the procedure via the context menu, this selection will not be
    provided.
    Time interval
    Here you can select a time interval. The volumes of the selected time
    interval will then be converted.
    Selection
    Here you can specify, whether all paths or just the flow bundle routes or
    the relations of the OD pair filter shall be converted.
    Factor
    Here you can enter a factor by which the volumes of the origin paths will
    be multiplied.

    Destination From drop-down list, select the path set or the demand segment to which
    the paths will be transferred.
    Time interval
    Here you can select a time interval, to which the volumes will be transferred.
    Conflict handling
    If the origin path and the destination path are identical, the following options are provided.
    Replace all
    All existing destination paths will be deleted before the conversion.
    Sum
    The volumes of the origin paths and the volumes of the existing destination paths will be added up.

    1234

    PTVGROUP

    15.23.13 Deleting paths


    Element

    Description
    Overwrite
    Identical destination paths will be overwritten by the origin paths.

    5. Confirm with OK.


    The paths are converted.
    Note: If you convert paths resulting from an assignment, the program always creates
    paths which start and end at a zone.

    15.23.13 Deleting paths


    There are several ways to delete paths.
    15.23.13.1 Deleting a path
    1. Open the Paths window (see "Opening the Paths window" on page 1228).
    2. Select the path that you want to delete.
    3. Press the DEL key.
    The path is deleted.
    Tip: You can also delete the selected path via the context menu> Delete entry.
    15.23.13.2 Deleting several marked paths
    1. Mark the paths that you want to delete (see "Marking several paths" on page 1230).
    The selected paths are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked paths via the context menu> entry Delete.
    3. Confirm with OK.
    The paths are deleted.
    15.23.13.3 Deleting all paths
    Note: You can only delete all paths that are allocated to path sets. Paths that are allocated to demand segments cannot be deleted this way.
    1. In the Network window, right-click the PrT paths button.
    The Paths context menu opens.

    PTVGROUP

    1235

    15.23.14 Distributing a matrix on paths


    2. Select the Multi-edit> Paths entry.
    A query opens.
    3. Confirm with OK.
    All paths that are allocated to paths sets are deleted.

    15.23.14 Distributing a matrix on paths


    With this procedure, you can distribute the values of a demand matrix to paths (see Fundamentals: Chpt. 3.1.10 , page 63).
    Notes: Existing volumes will be overwritten during the distribution.
    Matrices will only be distributed to paths if they start and end at matching zones.
    Via attribute Share of path set target, you can specify beforehand the share that shall be
    assigned to each path (see "Properties and options of PrT paths" on page 1226).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the Distribution of demand matrix to paths procedure from the Matrices category to
    the given order of procedures in the procedure sequence (see "Setting up and starting the
    procedure sequence" on page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. From the selection list, select the matrix which is to be distributed to the paths.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The Distribute matrix to paths window opens.

    7. Make the desired changes.

    1236

    Element

    Description

    Only active path


    sets

    If the option has been selected, only the volumes of active paths
    will be distributed.

    Consider OD pair
    filter

    If the option has been selected, the OD pair filter will be taken into
    account (see "Exception: Filter for OD pairs" on page 1026).
    PTVGROUP

    15.23.15 Paths in lists


    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The matrix values are distributed to the paths.

    15.23.15 Paths in lists


    You can display paths and path sets in the following lists and edit volume data directly in the
    lists:
    PrT path sets
    PrT paths
    PrT paths on link level
    Notes: You can use the drop-down lists to restrict the list display to a selection (see "Limiting list display to a selection" on page 2315).
    In the lists PrT paths and PrT paths on link level, you can call the opposite direction via
    the Go to reverse direction entry in the context menu.

    15.24

    Managing stops
    A stop comprises stop areas and therefore stop points. To ensure that a stop can be localized
    and displayed in graphical form, it has a coordinate, but it is not assigned directly to a network
    node or link (see Fundamentals: Chpt. 3.1.11.3 , page 67).
    Notes: You can only allocate stop areas and therefore stop points to a stop if you edit the
    stop area (see "Editing the attribute values of a stop area" on page 1258 and "Creating a
    stop area" on page 1255) or create a stop point and select the Generate stop and stop
    point automatically option (see "Creating a stop point" on page 1266).
    Afterwards you can specify the walk times for the transfers within the stop as well as transfer wait times.

    15.24.1 Creating a stop


    You can insert stops anywhere in the network.

    1. In the Network window, click the

    Insert mode icon.

    2. Click the Stops button.


    3. In the network, click the position where you want to insert the stop.
    The Create stop window opens.
    4. Enter the desired data (see "Properties and options of stops" on page 1238).
    5. Confirm with OK.
    The stop is inserted in the network.

    PTVGROUP

    1237

    15.24.2 Properties and options of stops

    Tip: Alternatively, you can create a stop, stop area or stop point with an identical number
    if you insert a stop point and select the Create stop and stop area automatically option
    (see "Creating a stop point" on page 1266).

    15.24.2 Properties and options of stops

    The upper section of the Create stop or Edit stop window contains the general attributes of
    the stop. In the lower section, you can edit specific attributes in various tabs.
    15.24.2.1 Stops: General attributes
    Element

    Description

    Number

    Unique number of the stop


    Stops are numbered consecutively. You can overwrite the preset
    number with a number that does not yet exist in the network.
    Note
    If you change the stop number, existing assignment results will not
    be deleted.

    Code

    Code of the stop

    Name

    Name of the stop

    Type

    The stop type (0...99) categorizes the stop.

    15.24.2.2 Stops: Basis tab

    1238

    PTVGROUP

    15.24.2.3 Stops: Stop areas tab


    Element

    Description

    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes (see "Managing user-defined
    attributes" on page 973).

    Position

    Coordinates of the stop in the network


    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).

    15.24.2.3 Stops: Stop areas tab


    The list contains the stop areas of the stops with the access node and the number of stops per
    stop area. You cannot edit the list directly.
    Note: A later allocation of a stop area to a stop is only possible when editing the stop
    area or when inserting a stop and selecting the Create stop and stop area automatically option.
    Element

    Description

    Edit

    Edit the attribute values of the marked stop area via this button (see
    "Properties and options of stop areas" on page 1256).
    Tip
    You can also open the Edit stop area window with a double-click in
    the row of the list.

    Note: You have to edit the stop area if you want to remove the allocation of a stop area to
    a stop (see "Editing the attribute values of stop areas" on page 1258).
    15.24.2.4 Stops: Stop points tab
    The list contains the stop points of the stop and their location in the network. You cannot edit
    the list directly.
    Note: Stop points are not allocated to stops, but to stop areas.
    In order to remove the allocation of a stop point to a stop, you have to edit either the stop
    point (see "Editing the attribute values of stop points" on page 1273) or the stop area
    (see "Editing the attribute values of stop areas" on page 1258).

    PTVGROUP

    1239

    15.24.2.5 Stops: Walk times / stop areas tab


    Element

    Description

    Edit

    Edit the attribute values of the marked stop point via this button (see
    "Editing the attribute values of stop points" on page 1273).
    Tip
    You can also open the Edit stop point window with a double-click in
    the row of the list.

    15.24.2.5 Stops: Walk times / stop areas tab


    In the Walk times / stop areas tab, you can edit the matrix of the required transfer walk times
    of each transport system of the type PuTWalk between the stop areas of the stop.
    You can enter the new values with or without a time unit (h, min, s). If you do not enter a unit,
    your entry is interpreted as minutes.
    Element

    Description

    Transport systems of type


    PuTWalk

    Use the drop-down list to select the transport system of type PuTWalk
    for which you want to edit the transfer walk times.

    Notes: A blank field signifies that the transfer between the stop areas is closed.
    If a value is entered, a transfer is possible within the stated time.
    Notes: If, for a stop, both specific walk times for transport system changes as well as walk
    times between stop areas have been defined, Visum will use the specific walk times for
    transport system changes in assignments for transfers between these transport systems.
    If, on top of that, specific walk times have been defined for time profile changes, these will
    be used in assignments for transfers between these time profiles at the stop.
    Notes: All entries of the walk times matrix which exceed the shortest (indirect) path between the two stop areas are highlighted in red. The quick info displays the explanation
    and the time of the shortest path.
    For assignments (headway- based, timetable- based), via different options, you can
    restrict the shortest path search within the stop to specific PuT Walk path legs.
    The options can be found in menu Calculate> General procedure settings> PuT
    settings> Assignment (see "Restricting the walk link search" on page 2000).
    15.24.2.6 Stops: Spec. walk times tab
    In the Spec. walk times tab, you can edit the matrices of the required walk times between the
    stop areas of the stop for transfers with a transport system change or with a time profile
    change.

    1240

    PTVGROUP

    15.24.2.7 Stops: Wait times tab


    Element

    Description

    TSys/time profile

    Use the drop-down list to specify whether you want to edit the matrix
    of specific transfer walk times for transfers with a change of the transport system or with a change of the time profile.

    Create

    Use this button to open the Define time window, which contains the
    drop-down lists From and To for transport systems or time profiles.
    You can restrict the selection list to only active time profiles.
    In the Time field you can enter a value with or without a time unit (h,
    min or s). If you do not enter a unit, your entry is interpreted as minutes.
    Confirmed entries will be saved as matrix rows.

    Delete

    Use this button to delete the marked row from the matrix.

    Notes: A blank field signifies that the transfer between the stop areas is closed.
    If a value is entered, a transfer is possible within the stated time.
    If, for a stop, both specific walk times for transport system changes as well as walk times
    between stop areas have been defined, Visum will use the specific walk times for transport system changes in assignments for transfers between these transport systems.
    If, on top of that, specific walk times have been defined for time profile changes, these will
    be used in assignments for transfers between these time profiles at the stop.
    You can get an overview of all specified transition walk times under Time profiles: Transition walk times and Transport systems: Transition walk times lists.
    15.24.2.7 Stops: Wait times tab
    Note: The Wait times tab is only relevant to the headway-based assignment.
    In the Wait times tab, you can edit the matrices of the required wait times for transfers with a
    change of transport system or time profile.
    Element

    Description

    TSys/time profile

    Use the drop-down list to specify whether you want to edit the matrix
    of wait times for transfers with a change of the transport system or
    with a change of the time profile.

    Create

    Use this button to open the Define time window, which contains the
    drop-down lists From and To for transport systems or time profiles.
    You can restrict the selection list to only active time profiles. Confirmed entries will be saved as matrix rows.

    Delete

    Use this button to delete the marked row from the matrix.

    PTVGROUP

    1241

    15.24.3 Finding a stop


    Notes: If both wait times for time profile changes as well as wait times for transport system
    changes have been specified for transfers at the stop, the wait times for time profile changes are used.
    For the calculation of the transfer wait time indirect passengers transferring with preceding footpath are considered, too.

    15.24.3 Finding a stop


    How to find stops is described for all network objects (see "Finding network objects in the network" on page 999).

    15.24.4 Selecting stops


    There are several ways to select stops in order to edit them in another step.
    Marking stops
    Setting stops active/passive
    15.24.4.1 Marking stops
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stops button.


    3. In the network, click the stop.
    The sought stop is marked.
    4. If you want to mark additional main stops, press the C TRL key and keep it pressed.
    5. One by one, click the stops that you want to mark.
    The stops are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive stops with the mouse (see "Marking only active network objects" on page 1005).
    Tip: Alternatively, you can mark a stop by searching for it (see "Finding a stop" on page
    1242) or by selecting the respective row in the list of stops (see "Selecting list sections"
    on page 2319).
    15.24.4.2 Setting stops active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.24.5 Editing the attribute values of stops


    You can edit the attribute values of one stop, all marked stops or all (active) stops.

    1242

    PTVGROUP

    15.24.5.1 Editing the attribute values of a stop


    15.24.5.1 Editing the attribute values of a stop
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stops button.


    3. In the network, double-click the stop whose attribute values you want to edit.
    The Edit stop window opens.
    Tip: If the stop is marked, you can also call the Edit stop window via the context
    menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes in respective tab (see "Properties and options of
    stops" on page 1238).
    5. Confirm with OK.
    The attribute values are edited.
    Tip: You can also edit the values of the input attributes of stops in the Quick view window
    or in the list of the network object type (see "Quick view window" on page 810 and "Working with lists" on page 2299).
    15.24.5.2 Editing the attribute values of marked stops
    1. Select the stops whose attribute values you want to edit (see "Marking stops" on page
    1242).
    The selected stops are marked.
    2. Press the ENTER key.
    The Multi-edit stops: <Number> objects window opens.
    Tip: You can also call the Multi-edit stops: <Number> objects window via the context menu > entry Edit or double-click the last stop to be marked.
    3. Edit the values of the desired attributes (see "Properties and options of stops" on page
    1238 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.24.5.3 Editing the attribute values of all or all active stops
    Note: If there are no passive stops in the network, all stops are edited. Markings of stops
    are ignored.
    1. If required, set the stops active, whose attribute values you want to edit, via
    PTVGROUP

    1243

    15.24.5.4 Displaying the attribute values of a stop in a column chart


    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stops are active.
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit stops window opens.
    4. Select whether you want to edit the attribute values of all stops or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active stops will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of stop areas" on page
    1256 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.24.5.4 Displaying the attribute values of a stop in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.24.6 Shifting stops


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stops button.


    3. In the network, click the stop that you want to shift, and hold down the mouse button.
    4. Drag the stop to the desired position and release the left mouse button.
    Notes: If you press the ESC key while dragging, you can cancel the action and the
    stop is reset to its original position.
    The stop is shifted to the new position.
    Tip: You can also edit the coordinates of a stop in the Edit stop window (see "Properties
    and options of stops" on page 1238).

    1244

    PTVGROUP

    15.24.7 Merging stops

    15.24.7 Merging stops


    You can pool all or all active stops which are linked by walk links in one single stop and simultaneously use the former walk link time data as transfer walk link matrix for the new stop.
    For each transport system of the type PuTWalk, the procedure determines all directed pairs
    (a,b) of stop areas connected by walk links permitted for the respective Walk transport system.
    If required, you can restrict the path search to the active links.
    For each of the pairs found, let t(a,b) be the walk time on the links. The following applies:
    If s(a) and s(b) denote the stops allocated to the stop areas a and b, and if s(a) <> s(b), then
    the stops are merged by allocating stop area b to stop s(a).
    All other stop areas b also belonging to s(b) are assigned to s(a) as well.
    All previously defined transfer walk link times between stop areas within s(a) and s(b) are
    kept.
    Subsequently, s(b) is an isolated stop, i.e. without stop areas.
    You can delete s(b) automatically, if desired.
    t(a,b) is stored as the transport system-specific transfer walk time between a and b within the
    enlarged stop s(a). This step is dropped, if stop area a and stop area b had already been allocated to the same stop before (i.e. s(a) = s(b)) with a predefined transfer walk time between a
    and b which is < t(a,b).
    Note: If you merge the stops, the current assignment result is deleted.
    1. If required, set the stops active, which you want to merge, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    The selected stops are active.
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Merge stops entry.
    The Multi-edit stops window opens.

    PTVGROUP

    1245

    15.24.8 Stops: Opening the Timetable editor

    Tip: If the network object type Stops has been selected, you can also call the Multiedit stops window via the Edit> Merge stops menu.
    4. Make sure that the Special functions tab has been selected and the Merge stops entry in
    the drop-down list.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, only active stops which are
    connected by walk links will be merged.
    If the option has not been selected, all active and passive
    stops which are connected by walk links will be merged.

    Regard only
    active walk links

    If the option has been selected, only active walk links will be considered during the path search.

    Delete newly crea- If the option has been selected, all stops with no stop areas will
    ted isolated stops be deleted automatically after the merging operation.
    Close used walk
    links

    If the option has been selected, the walk links used for the combination of the walk links will be closed to the transport system
    PuTWalk after the merging operation.

    6. Click the Execute button.


    The stops are merged.
    7. Click the Close button.

    15.24.8 Stops: Opening the Timetable editor


    With this functionality, you can open the Timetable editor (see "Using the Timetable editor" on
    page 1526). The line routes, which have a route point at a stop point of a marked stop, are preselected (see "Managing stop points" on page 1266).

    1246

    PTVGROUP

    15.24.9 Setting the polygon allocation of stops

    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stops button.


    3. Select one or more stops which are served by the desired line routes (see "Marking stops"
    on page 1242).
    The selected stops are marked.
    4. Right-click in the network display.
    The Stops context menu opens.
    5. Select the Timetable editor entry.
    Notes: If the Timetable editor is already open, a query opens (see "Opening the Timetable editor" on page 1526).
    If the network object type Stops has been selected, you can also call the Timetable
    editor via the Edit> Timetable editor menu.
    The Timetable editor window opens.

    15.24.9 Setting the polygon allocation of stops


    Prerequisite is that there are stops within a polygon (territory, zone or main zone).
    You can specify that a selected attribute receives the number of the territory, zone, or main
    zone in which the stop lies.
    1. If required, set the stops active, whose allocation you want to set, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter (see "Using filters to set network objects active or passive" on page 1008).
    The selected stops are active.
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Set polygon allocation entry.
    The Multi-edit stops window opens.
    Tip: If the network object type Stops has been selected, you can also call the Multiedit stops window via the Edit> Set polygon allocation menu.
    4. Make sure that the Special functions tab and the Set polygon allocation entry in the dropdown list have been selected.
    5. Make the desired changes.

    PTVGROUP

    1247

    15.24.10 Setting transition walk times for stop areas


    Element

    Description

    Only active ones

    If the option has been selected, only active stops will be taken
    into account.
    If the option has not been selected, all stops will be taken into
    account.

    Object

    In the drop-down list, you can select the type of network object
    whose number you want to use as attribute value.

    Attribute to be set Use the drop-down list to select an attribute which shall store the
    number of the selected object.
    6. Click the Set button.
    The stops store the number as attribute value.
    7. Click the Close button.

    15.24.10 Setting transition walk times for stop areas


    You can overwrite the current matrix values of the Walk times /stop areas tab for all or all
    active stops and stop areas (see "Stops: Walk times / stop areas tab" on page 1240).
    1. If required, set the stops active, whose walk times you want to overwrite, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter criteria (see "Using filters to set network objects active or passive" on page
    1008).
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Set transition walk times for stop areas entry.
    The Multi-edit stops window opens.

    1248

    PTVGROUP

    15.24.10 Setting transition walk times for stop areas


    Tip: If the network object type Stops has been selected, you can also call the Multiedit stops window via the Edit> Set transition walk times for stop areas menu.
    4. Make sure that the Special functions tab has been selected and the Set transition walk
    times for stop areas entry in the drop-down list.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, only active stops will be taken
    into account.
    If the option has not been selected, all stops will be taken into
    account.

    Walk-TSys

    Use the drop-down list to select the transport system of which you
    want to edit the walk times between stop areas.

    Transfer within
    same stop area

    There are several options for transfers within a stop area.


    Set to
    If the option has been selected, the transfer walk time is set to the
    entered value.
    Close
    If the option has been selected, the transfers will be closed.
    Keep
    If the option has been selected, the transfer walk times will not be
    changed.

    Transfer between There are several options for transfers between different stops.
    different stop
    Set to
    areas
    If the option has been selected, the transfer walk time is set to the
    entered value.
    Close
    If the option has been selected, the transfers will be closed.
    Keep
    If the option has been selected, the transfer walk times will not be
    changed.
    Edit value only for If the option has been selected, only active stop areas will be
    active stop areas taken into account.
    6. Click the Execute button.
    At the selected stops, the matrix of the transfer walk times will be updated for the set transport system.
    7. Click the Close button.

    PTVGROUP

    1249

    15.24.11 Setting specific transition walk times


    Note: You can get an overview of all transition walk times between stop areas under Lists
    Stops > Transfers and walk times between stop areas at stop.

    15.24.11 Setting specific transition walk times


    You can specify specific transfer walk times between the stop areas of stops for transfers with
    a transport system change or time profile change. These are displayed in the Spec. walk
    times tab of the Edit stop window.
    1. If required, set all stops active, for which you want to define specific transition walk times,
    via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stops are active.
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Set specific transfer walk times entry.
    The Multi-edit stops window opens.

    Tip: If the network object type Stops has been selected, you can also call the Multiedit stops window via the Edit> Set specific transfer walk times menu.
    4. Make sure that the Special functions tab has been selected and the Set spec. transition
    walk times entry in the drop-down list.
    5. Make the desired changes.

    1250

    PTVGROUP

    15.24.12 Deleting specific walk and wait times


    Element

    Description

    Set times for

    Select whether specific transition walk times shall be set for TSys
    (transport systems) or Time profiles

    From/To

    Select the transport systems or time profiles between which the


    transfers occur

    Show only active


    time profiles

    If the option has been selected, only active time profiles are displayed.
    Note
    The option is only provided, if you define specific transition walk
    times for time profiles.

    Time

    Enter the desired transition walk time

    6. Click the Execute button.


    New transition walk times are generated at the selected stops. Existing transition walk times
    are overwritten by the new values.
    7. Click the Close button.
    Note: You can get an overview of all transition walk times in the Time profiles: Transition walk times and Transport systems: Transition walk times lists.

    15.24.12 Deleting specific walk and wait times


    You can delete specific walk times, which have been specified in the Spec. walk times tab for
    time profiles or pairs of transport systems for stops (see "Stops: Spec. walk times tab" on page
    1240).
    Likewise, you can delete wait times, which have been specified for time profiles or pairs of
    transport systems in the Wait times tab for the headway-based assignment (see "Stops: Wait
    times tab" on page 1241).
    1. If required, set the stops active whose walk or wait times shall be deleted, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stops are active.
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Delete specific walk and wait times entry.
    The Multi-edit stops window opens.

    PTVGROUP

    1251

    15.24.12 Deleting specific walk and wait times

    Tip: If the network object type Stops has been selected, you can also call the Multiedit stops window via the Edit> Delete specific walk and wait times menu.
    4. Make sure that the Special functions tab is selected and in the drop-down list, the Delete
    specific walk and wait times entry.
    5. Make the desired changes.

    1252

    Section

    Element and description

    Specific walk times

    Use these options to specify whether you want to delete all


    specific walk times in the Spec. walk times tab or just some
    of the walk times.
    Delete TSys-related entries
    If the option has been selected, all transfer walk times for
    transfers with a transport system change will be deleted from
    the transfer walk time matrix.
    Delete time profile-related entries
    If the option has been selected, all transfer walk times for
    transfers with a time profile change will be deleted from the
    transfer walk time matrix.

    Specific wait times


    (headway-based assignment)

    Use these options to specify whether you want to delete all


    specific wait times in the Wait times tab or just some of the
    wait times for the headway-based assignment.
    Delete TSys-related entries
    If the option has been selected, all wait times for transfers
    with a transport system change will be deleted from the transfer walk time matrix.
    Delete time profile-related entries
    If the option has been selected, all wait times for transfers
    with a time profile change will be deleted from the transfer
    walk time matrix.
    PTVGROUP

    15.24.13 Deleting stops


    6. Click the Execute button.
    The matrices of the specific walk and wait times are updated at the selected stops.
    7. Click the Close button.

    15.24.13 Deleting stops


    There are several ways to delete stops.
    15.24.13.1 Deleting a stop
    Notes: If a stop point (or a stop area) is located at the stop to be deleted, the stop point
    (and the stop area) will also be deleted.
    If the stop point is served by a public transport line, this line as well as its line routes, time
    profiles and vehicle journeys will also be deleted, if the stop point is the start or end stop
    point of a line route. Stop points in the course of a line route can be deleted. The line
    route and all route points will still exist. The time profiles and vehicle journeys are automatically adjusted to the new stop sequence.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stops button.


    3. In the network, click the stop that you want to delete.
    4. Press the DEL key.
    Tip: You can also delete the marked stop via the context menu> entry Delete.
    A query opens.
    5. Click Yes to confirm.
    The stop and all associated PuT objects will be deleted.
    15.24.13.2 Deleting several marked stops
    1. Mark the stops that you want to delete (see "Marking stops" on page 1242).
    The selected stops are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked stops via the context menu > entry Delete.
    3. Confirm with OK.
    The Delete stops window opens.
    4. Select which stops you want to delete.

    PTVGROUP

    1253

    15.24.13.3 Deleting all active stops

    Element

    Description

    Yes

    The stop listed in the window will be deleted and also the network
    objects with a reference to the stop.

    Yes for all

    All remaining marked stops will be deleted, and also the network
    objects with a reference to the stop.

    No

    Neither the stop listed in the window will be deleted nor the network objects with a reference to the stop.

    No for all

    Neither of the remaining marked stops will be deleted, nor the network objects with a reference to the stop.

    Notes: If you click the Yes or No buttons, the query is displayed for the next stop number.
    With the Yes for all or No for all buttons, you only regard the remaining stops, for
    which neither Yes nor No has been clicked.
    The confirmed stops are deleted.
    15.24.13.3 Deleting all active stops
    1. If required, set the stops active that you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stops are active.
    2. In the Network window, right-click the Stops button.
    The Stops context menu opens.
    3. Select the Multi-delete entry.

    A query opens.
    4. Confirm with OK.
    The Delete stops window opens.
    5. Select which stops shall be deleted.

    1254

    Element

    Description

    Yes

    The stop listed in the window will be deleted and also the network
    objects with a reference to the stop.

    Yes for all

    All remaining active stops will be deleted, and also the network

    PTVGROUP

    15.25 Managing stop areas


    Element

    Description
    objects with a reference to the stop.

    No

    Neither the stop listed in the window will be deleted nor the network objects with a reference to the stop.

    No for all

    Neither of the remaining active stops will be deleted, nor the network objects with a reference to the stop.

    Notes: If you click the Yes or No buttons, the query is displayed for the next stop number.
    With the Yes for all or No for all buttons, you only regard the remaining stops, for
    which neither Yes nor No has been clicked.
    The confirmed stops are deleted.

    15.25

    Managing stop areas


    Stop areas divide a stop into several areas. An area can, for example, represent a bus or train
    station platform, an intersection with stop points, a car park or a station concourse. A stop area
    is assigned to a single stop and can comprise several stop points. An area can be assigned to
    a network node so that connectors (access or egress) in the link network can be modeled via
    the area. The stop areas of a stop can be connected to each other From area - To area by
    means of a transfer walk time matrix that contains the time required for passenger transfers for
    each transport system of the type PuTWalk (see Fundamentals: Chpt. 3.1.11.2 , page 66).
    Note: You can only allocate stop areas and therefore stop points to a stop if you edit the
    stop area (see "Editing the attribute values of a stop area" on page 1258 and "Creating a
    stop area" on page 1255) or create a stop point and select the Generate stop and stop
    point automatically option (see "Creating a stop point" on page 1266).

    15.25.1 Creating a stop area


    You can insert stop areas anywhere in the network.
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Stop areas button.


    3. In the network, click the position where you want to insert the stop area.
    The Create stop area window opens.
    4. Enter the desired data (see "Properties and options of stop areas" on page 1256).
    5. Confirm with OK.
    The stop area is inserted in the network.

    PTVGROUP

    1255

    15.25.2 Properties and options of stop areas


    Tip: Alternatively, you can create a stop, stop area or stop point with an identical number
    if you insert a stop point and select the Create stop and stop area automatically option
    (see "Creating a stop point" on page 1266).

    15.25.2 Properties and options of stop areas

    The upper section of the Create stop area or Edit stop area window contains the general attributes of the stop area. In the lower section, you can edit specific attributes in various tabs.
    15.25.2.1 Stop areas: General attributes

    1256

    Element

    Description

    Number

    Unique number of the stop area


    The stop areas are numbered consecutively. You can overwrite the
    preset number with a number that does not yet exist in the network.
    Note
    If you edit the number of the stop area, existing assignment results
    will be deleted for all public transport demand segments.

    Code

    Code of the stop area

    Name

    Name of the stop area

    Type

    The type (0...99) categorizes the stop area.

    PTVGROUP

    15.25.2.2 Stop areas: Basis tab


    Element

    Description

    Stop

    Display of the number of the stop to which the stop area is allocated.
    By default, the number of the nearest stop is used. Use the
    ton to allocate the stop area to a different stop.

    Access node

    but-

    Display of the number of the node, to which the stop area is allocated.
    button.
    You can edit the allocation via the
    Tip
    Select a connector node for a zone connector at the stop area.

    15.25.2.2 Stop areas: Basis tab


    Element

    Description

    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes (see "Managing user-defined
    attributes" on page 973).

    Position

    Coordinates of the stop area in the network


    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).

    15.25.2.3 Stop areas: Stop points tab


    The list contains the stop points of the stop area and their location in the network. You cannot
    edit the list directly.
    Note: A later allocation of a stop to a stop area is only possible when editing the stop
    point or when inserting a stop point and selecting the Create stop and stop area automatically option.
    Element

    Description

    Edit

    Edit the attribute values of the marked stop point via this button (see
    "Editing the attribute values of stop points" on page 1273).
    Tip
    You can also open the Edit stop point window with a double-clickin
    the row of the list.

    Note: If you want to edit the allocation of a stop point to a stop area, you need to edit the
    stop point (see "Editing the attribute values of stop points" on page 1273).

    PTVGROUP

    1257

    15.25.3 Finding a stop area

    15.25.3 Finding a stop area


    How to find stop areas is described for all network objects (see "Finding network objects in the
    network" on page 999).

    15.25.4 Selecting stop areas


    There are several ways to select stop areas in order to edit them in another step.
    Marking stop areas
    Setting stop areas active/passive
    15.25.4.1 Marking stop areas
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop areas button.


    3. In the network, click the stop area.
    The stop area is marked.
    4. If you want to mark additional stop areas, press the C TRL key and keep it pressed.
    5. One by one, click the stop areas that you want to mark.
    The stop areas are marked.

    Note: If the
    Click only active objects toolbar icon is activated, you cannot mark passive stop areas with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a stop area by searching for it (see "Finding a stop area"
    on page 1258) or by selecting the respective row in the list of stop areas (see "Selecting
    list sections" on page 2319).
    15.25.4.2 Setting stop areas active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.25.5 Editing the attribute values of stop areas


    You can edit the attribute values of one stop area, all marked stop areas or all (active) stop
    areas.
    15.25.5.1 Editing the attribute values of a stop area
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop areas button.


    1258

    PTVGROUP

    15.25.5.2 Editing the attribute values of marked stop areas


    3. In the network, double-click the stop area whose attribute values you want to edit.
    The Edit stop area window opens.
    Tip: If the stop area is marked, you can also call the Edit stop area window via the
    context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes in respective tab (see "Properties and options of
    stops" on page 1238).
    5. Confirm with OK.
    The attribute values are edited.
    Tip: You can also edit the values of the input attributes of stop areas in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    Alternatively, a stop area can also be selected in the Edit stop window to be edited.
    Here, the Stop areas tab lists all stop areas of the respective stop (see "Stops: Stop
    areas tab" on page 1239).
    Note: If the stop area is assigned to a different stop, the node assigned to the new stop
    will also automatically be used as access node. An access node can be selected independently of the currently marked stop.
    This option is not available, if the Edit stop area window has been selected via the Edit
    button in the Edit stop window.
    15.25.5.2 Editing the attribute values of marked stop areas
    1. Mark the stop areas whose attribute values you want to edit (see "Marking stop areas" on
    page 1258).
    The selected stop areas are marked.
    2. Press the ENTER key.
    The Multi-edit stop areas: <Number> objects window opens.
    Tip: You can also call the Multi-edit stop areas: <Number> objects window via the
    context menu > entry Edit or double-click the last node to be marked.
    3. Edit the values of the desired attributes (see "Properties and options of stop areas" on page
    1256 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.25.5.3 Editing the attribute values of all or all active stop areas

    PTVGROUP

    1259

    15.25.5.4 Displaying the attribute values of a stop area in a column chart


    Note: If there are no passive stop areas in the network, all stop areas are edited. Markings of stop areas are ignored.
    1. If required, set the stop areas active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stop areas are active.
    2. In the Network window, right-click the Stop areas button.
    The Stop areas context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit stop areas window opens.
    4. Select whether you want to edit the attribute values of all stop areas or just the active ones.
    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active stop areas will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of stop areas" on page
    1256 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.25.5.4 Displaying the attribute values of a stop area in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.25.6 Shifting a stop area


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop areas button.


    3. In the network, click the stop area that you want to shift and hold down the mouse button.
    4. Drag the stop area to the desired position and release the left mouse button.
    Notes: If you press the ESC key while dragging, you can cancel the action and the
    stop area is reset to its original position.
    The stop area is shifted to the new position.
    1260

    PTVGROUP

    15.25.7 Stop areas: Opening the Timetable editor

    Tip: You can also edit the coordinates of a stop area in the Edit stop area window (see
    "Properties and options of stops" on page 1238).

    15.25.7 Stop areas: Opening the Timetable editor


    With this functionality, you can open the Timetable editor (see "Using the Timetable editor" on
    page 1526). The line routes, which have a route point at a stop point of a marked stop, are preselected (see "Managing stop points" on page 1266).
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop areas button.


    3. Select the stop areas that are served by the desired line routes (see "Marking stop areas"
    on page 1258).
    The selected stop areas are marked.
    4. Right-click in the network display.
    The Stop areas context menu opens.
    5. Select the Timetable editor entry.
    Notes: If the Timetable editor is already open, a query opens (see "Opening the Timetable editor" on page 1526).
    If the network object type Stop aress has been selected, you can also call the Timetable editor via the Edit> Timetable editor menu.
    The Timetable editor window opens.

    15.25.8 Setting the polygon allocation of stop areas


    Prerequisite is that there are stop areas within a polygon (territory, zone or main zone).
    You can specify that a selected attribute receives the number of the territory, zone, or main
    zone in which the stop area lies.
    1. If required, set the stop areas active, whose allocation you want to set, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    Filter (see "Using filters to set network objects active or passive" on page 1008).
    The selected stop areas are active.
    2. In the Network window, right-click the Stop areas button.
    The Stop areas context menu opens.
    3. Select the Set polygon allocation entry.
    The Multi-edit stop areas window opens.

    PTVGROUP

    1261

    15.25.9 Setting access nodes


    Tip: If the network object type Stop areas has been selected, you can also call the
    Multi-edit stop areas window via the Edit> Set polygon allocation menu.
    4. Make sure that the Special functions tab and the Set polygon allocation entry in the dropdown list have been selected.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, only active stop areas will be
    taken into account.
    If the option has not been selected, all stop areas will be taken
    into account.

    Object

    In the drop-down list, you can select the type of network object
    whose number you want to use as attribute value.

    Attribute to be set Use the drop-down list to select an attribute which shall store the
    number of the selected object.
    6. Click the Set button.
    The stop areas store the number as attribute value.
    7. Click the Close button.

    15.25.9 Setting access nodes


    In order to connect the public transport line network to the regular link network, you can
    connect stop areas automatically to nodes. For a stop area, the program searches for the nearest node within the user-defined snap radius and saves it as access node. If required, you
    can restrict the number of the regarded stop areas and nodes. In case of an identical distance
    to two nodes, the node with the smaller number becomes the new access node. If no node is
    located within the snap radius, the allocation does not change.
    1. If required, set the stop areas active, which you want to connect to the network, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008)
    The selected stop areas are active.
    2. In the Network window, right-click the Stop areas button.
    The Stop areas context menu opens.
    3. Select the Set access node entry.
    The Multi-edit stop areas window opens.

    1262

    PTVGROUP

    15.25.9 Setting access nodes

    Tip: If the network object type Stop areas has been selected, you can also call the
    Multi-edit stop areas window via the Edit> Set access node menu.
    4. Make sure that the Special functions tab has been selected and, in the drop-down list, the
    Set access nodes entry.
    5. Make the desired changes.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active stop areas will be taken
    into account.
    If the option has not been selected, all stop areas will be taken into
    account.

    Snap radius Radius around the coordinate of the stop area in which the nearest
    node is determined as new access node for the stop area. In case of an
    identical distance, the node with the smaller number is used. If no node
    is located within the snap radius, the allocation does not change.
    Adjust only
    isolated
    stop areas

    If the option has been selected, access nodes are only set for stop areas
    which do not have an access node yet.

    Allocate
    only active
    nodes

    If the option has been selected, only active nodes will be considered as
    access nodes. If not, all nodes are considered.

    Execute

    For each selected stop area, an access node is determined within the
    snap radius.

    6. Click the Execute button.


    For each selected stop area, an access node is determined within the snap radius.
    7. Click the Close button.

    PTVGROUP

    1263

    15.25.10 Deleting stop areas

    15.25.10 Deleting stop areas


    There are several ways to delete stop areas.
    15.25.10.1 Deleting a stop area
    Notes: If a stop point is located at a stop area to be deleted, the stop point will also be
    deleted.
    If the stop point is served by a public transport line, this line as well as its line routes, time
    profiles and vehicle journeys will also be deleted, if the stop point is the start or end stop
    point of a line route. Stop points in the course of a line route can be deleted. The line
    route and all route points will still exist; Visum adjusts the time profiles and vehicle journeys automatically to the new stop sequence.

    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop areas button.


    3. In the network, click the stop area that you want to delete.
    4. Press the DEL key.
    Tip: You can also delete the marked stop area via the context menu> entry Delete.
    A query opens.
    5. Click Yes to confirm.
    The stop area and all associated PuT objects are deleted.
    15.25.10.2 Deleting several marked stop areas
    1. Mark the stop areas that you want to delete (see "Marking stop areas" on page 1258).
    The selected stop areas are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked stop areas via the context menu> entry Delete.
    3. Confirm with OK.
    The Delete stop areas window opens.
    4. Select which stop areas you want to delete.

    1264

    PTVGROUP

    15.25.10.3 Deleting active stop areas


    Element

    Description

    Yes

    The stop area listed in the window will be deleted, and also all
    network objects with a reference to the stop area.

    Yes for all

    All remaining marked stop areas will be deleted, and also the network objects with a reference to the stop area.

    No

    Neither the stop area listed in the window will be deleted, nor the
    network objects with a reference to the stop area.

    No for all

    Neither of the remaining marked stop areas will be deleted, nor


    the network objects with a reference to the stop area.

    Notes: If you click the Yes or No buttons, the query is displayed for the next stop area
    number.
    With the Yes for all or No for all buttons, you only regard the remaining stop areas,
    for which neither Yes nor No has been clicked.
    The confirmed stop areas are deleted.
    15.25.10.3 Deleting active stop areas
    1. If required, set the stop areas active that you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stop areas are active.
    2. In the Network window, right-click the Stop areas button.
    The Stop areas context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    4. Confirm with OK.
    The Delete stop areas window opens.
    5. Select which active stop areas you want to delete.
    Element

    Description

    Yes

    The stop area listed in the window will be deleted, and also all
    network objects with a reference to the stop area.

    Yes for all

    All remaining active stop areas will be deleted, and also the network objects with a reference to the stop area.

    No

    Neither the stop area listed in the window will be deleted, nor the

    PTVGROUP

    1265

    15.26 Managing stop points


    Element

    Description
    network objects with a reference to the stop area.

    No for all

    Neither of the remaining active stop areas will be deleted, nor the
    network objects with a reference to the stop area.

    Notes: If you click the Yes or No buttons, the query is displayed for the next stop area
    number.
    With the Yes for all or No for all buttons, you only regard the remaining stop areas,
    for which neither Yes nor No has been clicked.
    The confirmed stop areas are deleted.

    15.26

    Managing stop points


    PuT lines stop at stop points so that passengers can board or alight. A stop point can either lie
    on a node or on a link (see Fundamentals: Chpt. 3.1.11.1 , page 65).
    Notes: You can only allocate stop areas and thus stop points to a stop if you edit the stop
    area (see "Editing the attribute values of a stop area" on page 1258 and "Creating a stop
    area" on page 1255).
    Alternatively, you can create a stop, stop area or stop point with an identical number if
    you insert a stop point and select the Create stop and stop area automatically option.

    15.26.1 Creating a stop point


    In the network, you can create stop points on links or on a node.
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Stop points button.


    The Create stop point (options) window opens.

    3. Select the desired options.

    1266

    Element

    Description

    On node

    If the option has been selected, the stop point will be placed on
    the marked node.

    On link

    If the option has been selected, the stop point will be placed in
    the marked position of the link course. The position can be shifted

    PTVGROUP

    15.26.2 Properties and options of stop points


    Element

    Description
    along the link. The nearest node of the link will automatically be
    used as reference node.

    Directed

    If the option has been selected, the stop point will be displayed
    next to the link in the direction of travel, and can only be served in
    this direction by lines of the public transport.
    If the option has not been selected, the stop point will be displayed on the link undirected and can be served in both directions by lines of the public transport.
    Notes
    This option is only displayed if the On link option has been selected.
    You cannot edit the directed/undirected option of a link stop
    point afterwards.

    Create stop and


    stop point automatically

    If the option has been selected, together with the stop point, a
    stop area and a stop with the same number will be created, as
    long as no existing stop area is selected yet.
    Tip
    We recommend this setting if you want to insert only one stop
    point per stop.
    If the option has not been selected, the nearest stop and the
    associated stop area will be used for the new stop point.

    4. In the network, click the position where you want to insert the stop point.
    The Create stop point window opens.
    5. Enter the desired data (see "Properties and options of stop points" on page 1267).
    6. Confirm with OK.
    The stop point is inserted in the network.

    15.26.2 Properties and options of stop points


    Note: Some of the described properties and options will only be displayed, if you have
    activated the respective add-on module (see "Displaying details on program and license"
    on page 886).

    PTVGROUP

    1267

    15.26.2 Properties and options of stop points

    The upper section of the Create stop point or Edit stop point window contains the general
    attributes of the stop point. In the lower section, you can edit specific attributes in various tabs.
    Note: In addition to the attributes of a stop point on a node, each stop point on a link has
    a Reference node, the option Directed (yes/no) and a Position on the link.

    1268

    PTVGROUP

    15.26.2.1 Stop points: General attributes

    Note: A node stop point can turn into a link stop point if the node has two legs and is deleted. If you confirm the Connect links option when deleting the node, the stop point will be
    placed on the new link.
    15.26.2.1 Stop points: General attributes
    Element

    Description

    Number

    Unique number of the stop point


    Visum suggests the next free number by default. You can overwrite it with
    a number that is not assigned in the network yet. If you enter a new number and automatically create the stop and the stop area, the same number
    will be assigned to them.

    Code

    Code of the stop point

    Name

    Name of the stop point

    Type

    The type (0...99) categorizes the stop point.

    Stop point

    Display of the position of the stop point on a node or on a link


    Note
    The number and the name of the stop point are updated, if the stop point is
    merged with another stop point.

    Reference
    node

    Display of the reference node of the link stop point. The reference node is
    the node nearest to the link on which the stop point is located.

    PTVGROUP

    1269

    15.26.2.2 Stop points: Basis tab


    Element

    Description
    Note
    If the position of the stop point on the link changes, the display of the reference node is updated automatically.

    Directed

    If the option has been selected, the stop point can only be served by
    PuT lines in the chosen direction of the link.
    If the option has not been selected, the stop point can be served in both
    directions by PuT lines.

    Stop

    Display of the network objects to which the stop point is allocated


    Stop area
    If the stop area is created automatically, the number of the stop point is
    button.
    used by default. You can edit the allocation via the
    Stop
    If the stop is created automatically, the number of the stop point is used by
    default to which the stop area is allocated.

    15.26.2.2 Stop points: Basis tab

    1270

    Element

    Description

    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes (see "Managing user-defined
    attributes" on page 973).

    Standard dwell
    time

    The standard dwell time at the stop point is overwritten by time profiles.

    PTVGROUP

    15.26.2.3 Stop points: Transport systems tab


    Element

    Description

    Position

    Absolute pos. before/behind reference node


    Display of the distance to the current reference node
    Relative position on link (0...1)
    You can edit the relative position of the stop point. The marked position is entered as a share of the link length From Node - To Node.
    Enter the share in the form of a decimal place between 0 and 1. The
    following applies: 0.0 = From Node, 0.5 = middle of the link.
    Position
    Alternatively, you can specify the position of the stop point by moving
    the indicator along the scale.
    Note
    The attributes Reference node and Absolute position are updated
    automatically, as well as the graphical or numerical display of the
    relative position.
    Alternatively, you can shift a stop point in the Network editor window
    (see "Shifting or merging stop points" on page 1275).

    15.26.2.3 Stop points: Transport systems tab


    The list contains all transport systems of the public transport in the network. By default, all PuT
    transport systems are allowed to use one new stop point only. Permitted transport systems are
    highlighted.
    Note: You can switch on/off several transport systems, if you hold down the C TRL key.
    15.26.2.4 Stop points: Cost tab
    Notes: The Cost tab is only relevant, if the Line costing calculation add-on is installed
    (see "Displaying details on program and license" on page 886).
    Compared to link costs, stop point costs are not edited per transport system.
    Element

    Description

    Cost 1-3

    Costs of the respective stop point

    15.26.2.5 Stop points: Time profiles tab


    This tab displays all time profiles which include the stop point as route point (see "Line routes:
    Items and time profiles tab" on page 1313). You can restrict the list to all active time profiles.
    Element

    Description

    Show only active


    time profiles

    If the option has been selected, only active time profiles are displayed.

    PTVGROUP

    1271

    15.26.2.6 Stop points: Depot tab


    For each time profile, the earliest and the latest arrival and departure of the vehicle journeys is
    issued.
    Notes: You can reverse the sorting order of the list by clicking the triangle in the column
    header.
    If you select a time profile in the list, the course of the associated line route will be highlighted in the network as long as the Edit stop point window is open.
    15.26.2.6 Stop points: Depot tab
    A depot is a stop point, at which a stop is permitted for at least one vehicle combination. This
    tab lists all vehicle combinations which can be permitted as depot (see Fundamentals: Chpt.
    8.4.3.5 , page 577).
    Element

    Description

    Permissible

    If the option has been selected, the respective vehicle combination is permitted as depot.
    Note
    The first row contains the default values.

    Code

    Code of the vehicle combination

    Capacity

    Enter a capacity per permitted vehicle combination


    Note
    The capacity indicates the number of vehicle combinations which can
    stop simultaneously at the depot. If 0 is set, the number is not limited.
    Such a permitted depot can always be frequented.

    Min. layover

    Enter a minimum layover time in the depot for each vehicle combination

    15.26.3 Finding a stop point


    How to find stop points is described for all network objects (see "Finding network objects in the
    network" on page 999).

    15.26.4 Selecting stop points


    There are several ways to select stop points in order to edit them in another step.
    Marking stop points
    Setting stop points active/passive
    15.26.4.1 Marking stop points
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop points button.


    3. In the network, click the stop point.
    The stop point is marked.

    1272

    PTVGROUP

    15.26.4.2 Setting stop points active/passive


    4. If you want to mark additional stops points, press the C TRL key and keep it pressed.
    5. One by one, click the stop points that you want to mark.
    The stop points are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive stop points with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a stop point by searching for it (see "Finding a stop point"
    on page 1272) or by selecting the respective row in the list of stop points (see "Selecting
    list sections" on page 2319).
    15.26.4.2 Setting stop points active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.26.5 Editing the attribute values of stop points


    You can edit the attribute values of one stop point, all marked stop points or all (active) stop
    points.
    15.26.5.1 Editing the attribute values of a stop point
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop points button.


    3. In the network, double-click the stop point whose attribute values you want to edit.
    The Edit stop point window opens.
    Tip: If the stop point is marked, you can also call the Edit stop point window via the
    context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes in respective tab (see "Properties and options of
    stop points" on page 1267).
    5. Confirm with OK.
    The attribute values are edited.

    PTVGROUP

    1273

    15.26.5.2 Editing the attribute values of marked stop points


    Tips: You can also edit the values of the input attributes of stop points in the Quick view
    window or in the list of the stop points (see "Quick view window" on page 810 and "Working with lists" on page 2299).
    Alternatively, a stop point can also be selected in the Edit stop window to be edited.
    Here, the Stop points tab lists all stop points of the respective stop (see "Stops: Stop
    points tab" on page 1239).
    Alternatively, a stop point can also be selected in the Edit stop area window in order to
    be edited. Here, the Stop points tab lists all stop points of the respective stop area (see
    "Stop areas: Stop points tab" on page 1257).
    Note: If a stop point is assigned to a different stop area, the stop assigned to the new stop
    area is automatically copied as well.
    This option is not available, if the Edit stop point window has been called via the Edit button in the Edit stop window, or in the Edit stop area window.
    15.26.5.2 Editing the attribute values of marked stop points
    1. Mark the desired stop points whose attribute values you want to edit (see "Selecting stop
    points" on page 1272).
    The selected stop points are marked.
    2. Press the ENTER key.
    The Multi-edit stop points: <Number> objects window opens.
    Tip: You can also call the Multi-edit stop points: <Number> objects window via the
    context menu > entry Edit or double-click the last stop point to be marked.
    3. Edit the values of the desired attributes (see "Properties and options of stop points" on page
    1267 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.26.5.3 Editing the attribute values of all or all active stop points
    Note: If there are no passive stop points in the network, all stop points are edited. Markings of stop points are ignored.
    1. If required, set the stop points active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stop points are active.
    2. In the Network window, right-click the Stop points button.
    1274

    PTVGROUP

    15.26.5.4 Displaying the attribute values of a stop point in a column chart


    The Stop points context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit stop points window opens.
    4. Select whether you want to edit the attribute values of all stop points or just the active ones.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active stop points will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of stop points" on page
    1267 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.26.5.4 Displaying the attribute values of a stop point in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.26.6 Shifting or merging stop points


    You can shift a stop point or merge it with another stop point, if required Different conditions
    apply according to whether the stop point is a route point of a line route or not:
    A stop point that is no route point of a line route can be shifted along the existing NodeLink network to another node or another link.
    A stop point that is a route point of one or several line routes can only be shifted along
    these line routes. In this case, the course of the line never changes. Especially the
    sequence of the served stop points does not change.
    If the shifted stop point is located in a position that cannot be reached by one of its line
    routes, the stop point is duplicated. All line routes that cannot reach the new position
    will still use the original stop point. The duplicated stop point is used by all line routes
    that can reach it. It is allocated to the same stop area as the original stop point.
    A start stop point or an end stop point of a line route can only be shifted, if it is a link
    stop point. And it can only be shifted along the same link.
    If you move a stop point to the position of an existing stop point, both stop points are merged
    into one stop point. In this case you can specify the stop point whose attributes you want to
    use. This does not apply to the allocated transport systems: In all cases, the new stop point
    obtains all transport systems of both merged stop points.
    If you shift a stop point to a link, you can specify whether it shall be directed or undirected after
    being shifted. To do this you need to position the mouse pointer either on a link or far beside
    the link. The form of the mouse pointer indicates how the stop point will be inserted.

    PTVGROUP

    1275

    15.26.6 Shifting or merging stop points

    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop points button.


    3. In the network, click the stop that you want to shift and hold down the left mouse button.
    4. Drag the stop point along existing links to its new position.
    Note: The form of the mouse pointer has the following meaning:
    The stop point is currently shifted along a line.
    The stop point is currently shifted across the line. This affects the Directed attribute.
    The stop point can be merged with this stop point.
    The stop point cannot be shifted to this position.
    Please also note the information in the status bar.
    5. Release the mouse button in the desired position.
    Notes: If you press the ESC key while dragging, you can cancel the action and the
    stop point is reset to its original position.
    Note: A message with information on the effects of this operation may open.
    The Merge/shift stop point window opens.
    6. Make the desired changes.
    Element

    Description

    Adjust the lengths


    If the option has been selected, the lengths of the line route eleof the line route
    ments are recalculated.
    elements to new
    If the option has not been selected, the lengths of the line route
    position
    elements remain unchanged.
    Note
    This option is grayed out if the stop point is not a route point of
    any line route.
    Adjust the run
    times to the new
    position

    1276

    If the option has been selected, the run times of the time profile
    elements are recalculated.
    If the option has not been selected, the run times remain
    unchanged.
    Note
    This option is grayed out if the stop point is not a route point of
    any line route.

    PTVGROUP

    15.26.7 Stop points: Opening the Timetable editor


    Element

    Description

    Shift also stop


    (area)

    If the option has been selected, the stop and the stop area of the
    shifted stop point will also get the new co-ordinates.
    Note
    This option is grayed out if the stop point has additional stop
    areas or if the stop area has additional stop points.

    Delete stop(area)

    If the option has been selected, the stop and the stop area of
    the merged stop point are deleted.
    If the option has not been selected, the stop and the stop area
    are preserved in the original position.
    Note
    This option is only available, if you merge two stop points without
    a copy, if the merged stop point is the only stop point of the stop
    area, and if the stop area is the only stop area of the stop.

    Use the attribute


    If the option is selected, the new stop point gets nearly all attridata of the shifted butes of the shifted stop point (exception see note).
    stop point
    If the option has not been selected, the new stop point gets
    nearly all attributes of the stop point the shifted stop point has
    been merged with (exception see note).
    Note
    This option is only available if you merge stop points.
    All transport systems that were allocated to one of the two merged
    stop points are allocated to the new stop point.
    7. Confirm with OK.
    The stop point is shifted and merged with another stop point, if applicable.
    Tip: You also can edit the exact position of a link stop point on a link in the Edit stop
    point window (see "Properties and options of stop points" on page 1267).

    15.26.7 Stop points: Opening the Timetable editor


    With this functionality, you can open the Timetable editor (see "Using the Timetable editor" on
    page 1526). The line routes, which have a route point at a stop point of a marked stop, are preselected.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop points button.


    3. Select one or more stop points which are served by the desired line routes.
    The selected stop points are marked.
    4. Right-click in the network display.

    PTVGROUP

    1277

    15.26.8 Setting the polygon allocation of stop points


    The Stop points context menu opens.
    5. Select the Timetable editor entry.
    The Timetable editor window opens.
    Notes: This functionality is not available if the Timetable editor is already open.
    If the network object type Stop points has been selected, you can also call the Timetable
    editor via menu Edit> Timetable editor.

    15.26.8 Setting the polygon allocation of stop points


    Prerequisite for this functionality is that the stop point lies within a polygon (territory, zone or
    main zone).
    You can specify that a selected attribute receives the number of the territory, zone, or main
    zone in which the stop point lies.
    1. If required, set the stop points active, whose allocation you want to set, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stop points are active.
    2. In the Network window, right-click the Stop points button.
    The Stop points context menu opens.
    3. Select the Set polygon allocation entry.
    The Multi-edit stop points window opens.
    Tip: If the network object type Stop points has been selected, you can also call the
    Multi-edit stop points window via the Edit> Set polygon allocation menu.
    4. Make sure that the Special functions tab has been selected.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, only active stop points will be
    taken into account.
    If the option has not been selected, all stop points will be taken
    into account.

    Object

    In the drop-down list, you can select the type of network object
    whose number you want to use as attribute value.

    Attribute to be set Use the drop-down list to select an attribute which shall store the
    number of the selected object.

    1278

    PTVGROUP

    15.26.9 Deleting stop points


    6. Click the Set button.
    The stop points store the number as attribute value.
    7. Click the Close button.

    15.26.9 Deleting stop points


    You can delete one, several, or all stop points at the same time.
    15.26.9.1 Deleting a stop point
    Note: If the stop point is served by a public transport line, this line as well as its line routes, time profiles and vehicle journeys will also be deleted, if the stop point is the start or
    end stop point of a line route. Stop points in the course of a line route can be deleted.
    The line route and all route points will still exist. The time profiles and vehicle journeys
    are automatically adjusted to the new stop sequence.

    1. In the Network window, click the

    Edit mode icon.

    2. Click the Stop points button.


    3. In the network, click the stop point that you want to delete.
    4. Press the DEL key.
    Tip: You can also delete the marked stop points via the context menu> Delete entry.
    A query opens.
    5. Click Yes to confirm.
    The stop points and all associated PuT objects will be deleted.
    15.26.9.2 Deleting several marked stop points
    1. Mark the stop points that you want to delete (see "Marking stop points" on page 1272).
    The selected stop points are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked stop point via the context menu> entry Delete.
    3. Confirm with OK.
    The Delete stop points window opens.
    4. Select which stop points you want to delete.

    PTVGROUP

    1279

    15.26.9.3 Deleting active stop points


    Element

    Description

    Yes

    The stop point listed in the window will be deleted, and also all network
    objects with a reference to the stop point.

    Yes for all

    All marked stop points are deleted, and also all network objects with a
    reference to them.

    No

    The stop point listed in the window is not deleted, and neither are the
    displayed network objects with a reference to the stop point.

    No for all

    Neither one of the remaining marked stop points nor any network object
    referring to will be deleted.

    Notes: If you click the Yes or No buttons, the query is displayed for the next stop point
    number.
    With the Yes for all or No for all buttons, you only regard the remaining stop points,
    for which neither Yes nor No has been clicked.
    The confirmed stop points are deleted.
    15.26.9.3 Deleting active stop points
    1. If required, set the stop points active that you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected stop points are active.
    2. In the Network window, right-click the Stop points button.
    The Stop points context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    4. Click Yes to confirm.
    The Delete stop points window opens.
    5. Select which stop points shall be deleted.

    1280

    Element

    Description

    Yes

    The stop point listed in the window will be deleted, and also all network
    objects with a reference to the stop point.

    Yes for all

    All active stop points are deleted, and also all network objects with a reference to them.

    No

    The stop point listed in the window is not deleted, and neither are the dis-

    PTVGROUP

    15.27 Managing operators of the public transport


    Element

    Description
    played network objects with a reference to the stop point.

    No for all

    Neither the remaining active stop points nor the network objects referring
    to will be deleted.

    Notes: If you click the Yes or No buttons, the query is displayed for the next stop point
    number.
    With the Yes for all or No for all buttons, you only regard the remaining stop points,
    for which neither Yes nor No has been clicked.
    All confirmed stop points are deleted.

    15.27

    Managing operators of the public transport


    You can create Operators and allocate an operator to each vehicle journey section. If you work
    with the operator model, you can then evaluate the PuT operating indicators per operator (see
    Fundamentals: Chpt. 3.1.12 , page 67).

    15.27.1 Creating an operator


    1. In the Network menu, select the PuT operators entry.
    The Operators window opens.

    2. Click the

    Create button.

    The Create operator window opens.


    3. Make the desired settings.
    Element

    Description

    Number

    The operators are numbered consecutively.

    Name

    Name of the operator The entry of the operator name is optional.

    Cost 1-3

    Costs of the operator

    PTVGROUP

    1281

    15.27.2 Editing the attribute values of operators


    4. Confirm with OK.
    The operator is created.
    Notes: If you have inserted user-defined attributes for operators, these will be displayed
    in an additional User-defined attributes tab (see "Managing user-defined attributes" on
    page 973).

    15.27.2 Editing the attribute values of operators


    1. In the Network menu, select the PuT operators entry.
    The Operators window opens.
    2. In the drop-down list, select the desired operator.
    3. Click the

    Edit button.

    The Edit operator <Number> window opens.


    4. Edit the desired attributes (see "Creating an operator" on page 1281).
    5. Confirm with OK.
    The attributes of the operator are changed.

    15.27.3 Deleting operators


    1. In the Network menu, select the PuT operators entry.
    The Operators window opens.
    2. In the drop-down list, select the desired operator.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the

    Delete button.

    4. Confirm with OK.


    The operator is deleted.

    15.28

    Managing PuT vehicles


    You can create vehicle units (see "Creating a vehicle unit" on page 1283) and vehicle combinations (see "Creating vehicle combinations" on page 1286). Vehicle units are defined for
    the public transport systems of the network. A vehicle combination consists of one or more
    vehicle units. A vehicle combination "Intercity" can, for example, consist of several vehicle
    units "wagon". For each you can specify the number of seats and total seats (see Fundamentals: Chpt. 3.1.13 , page 68).

    1282

    PTVGROUP

    15.28.1 Creating a vehicle unit

    15.28.1 Creating a vehicle unit


    1. In the Network menu, select the PuT vehicles entry.
    The Vehicle units and combinations window opens.

    2. Make sure that the Vehicle units tab is open.


    3. Click the

    Create button.

    The Create vehicle unit window opens.


    4. Make the desired settings (see "Properties and options of vehicle units" on page 1284).
    5. Confirm with OK.
    The vehicle unit is inserted.
    Note: A vehicle unit can be specified for more than one transport system. A railcar can
    thus, for example, be used for trains of the RE transport system and for trains of the IR
    transport system.

    PTVGROUP

    1283

    15.28.2 Properties and options of vehicle units

    15.28.2 Properties and options of vehicle units

    The upper section of the Create vehicle unit or Edit vehicle unit window contains the general
    attributes of the vehicle unit. In the lower section, you can edit specific attributes in various
    tabs.
    Vehicle units: General attributes
    Element

    Description

    Number

    The vehicle units are numbered consecutively.

    Code

    Code of the vehicle unit

    Name

    Name of the vehicle unit

    Generate vehicle If the option has been selected, for each generated vehicle unit, a
    combination auto- vehicle combination of the same name with a vehicle of the vehicle
    matically
    unit will be generated automatically.
    Vehicle units: Basis tab

    1284

    Element

    Description

    Transport systems

    You can open the Transport systems window via this button. In this
    window you can select the permitted transport systems.
    Tip
    You can select several transport systems, if you hold down the Ctrl
    key.

    Powered

    If the option has been selected, the vehicle unit is used as powered
    unit.

    PTVGROUP

    15.28.3 Editing the attributes of vehicle units


    Element

    Description

    Capacities

    Total capacity
    Number of the total capacity
    Seat capacity
    Number of seats

    Vehicle units: Cost rates tab


    Element

    Description

    Vehicle journeys

    Enter the cost rate per hour and per kilometer

    Empty trips

    Enter the cost rate per hour and per kilometer

    Depot

    Enter the cost rate for one hour in the depot

    Layover

    Enter the cost rate for a layover hour

    Per vehicle

    Enter the cost rate per vehicle


    Example: Costs of acquisition or depreciation costs.
    The cost rate per vehicle is used once per vehicle in the line costing
    calculation and line blocking.

    Reference period

    In the drop-down list you can select the reference period of the cost
    rate per vehicle.

    15.28.3 Editing the attributes of vehicle units


    1. In the Network menu, select the PuT vehicles entry.
    The Vehicle units and combinations window opens.
    2. Make sure that the Vehicle units tab is open.
    3. In the list, click the desired vehicle unit.
    4. Click the

    Edit button.

    The Edit vehicle unit <Number> window opens.


    5. Edit the desired attributes (see "Properties and options of vehicle units" on page 1284).
    6. Confirm with OK.
    The attributes of the vehicle unit are changed.

    15.28.4 Deleting vehicle units


    1. In the Network menu, select the PuT vehicles entry.
    The Vehicle units and combinations window opens.
    2. Make sure that the Vehicle units tab is open.
    3. In the list, click the desired vehicle unit.
    PTVGROUP

    1285

    15.28.5 Creating vehicle combinations

    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    4. Click the

    Delete button.

    5. Confirm with OK.


    The vehicle unit is deleted.

    15.28.5 Creating vehicle combinations


    You can create vehicle combinations in order to allocate them to a vehicle journey or a vehicle
    journey section afterwards.
    Tip: You can generate a vehicle combination automatically when creating a vehicle unit
    (see "Creating a vehicle unit" on page 1283).
    1. In the Network menu, select the PuT vehicles entry.
    The Vehicle units and combinations window opens.
    2. Make sure that the Vehicle combinations tab is open.
    3. Click the

    Create button.

    The Create vehicle combination window opens.


    4. Make the desired settings (see "Properties and options of vehicle combinations" on page
    1287).
    5. Confirm with OK.
    The vehicle combination is inserted.

    1286

    PTVGROUP

    15.28.6 Properties and options of vehicle combinations

    15.28.6 Properties and options of vehicle combinations

    The upper section of the Create vehicle combination or Edit vehicle combination window
    contains the general attributes of the vehicle combination. In the lower section, you can edit
    specific attributes.
    15.28.6.1 Vehicle combinations: General attributes
    Element

    Description

    Number

    The vehicle combinations are numbered consecutively.

    Code

    Code of the vehicle combination

    Name

    Name of the vehicle combination

    PTVGROUP

    1287

    15.28.6.2 Vehicle combinations: Basis tab


    15.28.6.2 Vehicle combinations: Basis tab
    Element

    Description

    Vehicle units

    Here you can


    create vehicle units for the vehicle combinations (see "Adding
    vehicle units to vehicle combinations" on page 1288) and delete
    them (see "Deleting a vehicle unit from a vehicle combination"
    on page 1289)
    edit the number of the associated vehicle units (see "Editing the
    number of vehicle units" on page 1288).
    Tip
    You can generate a vehicle combination of different vehicle units or
    of several identical vehicle units. This way you can, for example,
    model trains more accurately. The vehicle combination Tram-Short
    train, for example, consists of one vehicle unit "Tram" whereas a
    Tram-Long train may consist of two vehicle units "Tram".
    Set of transport systems
    Displays the transport systems which are contained in all vehicle
    combinations of the allocated vehicle units.

    Vehicle combination set

    Here you can specify the vehicle combination set as attribute of the
    vehicle combination (see "Specifying a vehicle combination set" on
    page 1289). This functionality is only available, if you have the Detailed line blocking add-on activated.

    Adding vehicle units to vehicle combinations


    1. Make sure that the Basis tab is open.
    2. Click the Create button.
    The Allocated vehicle unit window opens.
    3. Select the desired vehicle unit.
    4. Enter the desired Number of vehicle units.
    5. Confirm with OK.
    The vehicle unit is inserted.
    Editing the number of vehicle units
    1. Make sure that the Basis tab is open.
    2. Select the desired vehicle unit.
    3. Click the Edit button.
    The Allocated vehicle unit window opens.
    4. Edit the Number of vehicle units.
    5. Confirm with OK.
    1288

    PTVGROUP

    15.28.6.3 Vehicle combinations: Cost rates tab


    The number is changed.
    Deleting a vehicle unit from a vehicle combination
    1. Make sure that the Basis tab is open.
    2. Select the desired vehicle unit.
    3. Click the Delete button.
    The vehicle unit is deleted.
    Specifying a vehicle combination set
    Here you can specify the vehicle combination set as an attribute of the vehicle combination.
    1. Click the button next to Vehicle combination set.
    The Vehicle combination set window opens.
    2. Select the vehicle combinations that the vehicle combination set should comprise.
    3. Click OK.
    The numbers of the selected vehicle combinations are displayed on the Vehicle combination
    set button and stored as vehicle combination attributes.
    Notes: Vehicle combination sets are useful, if you have many vehicle journey sections
    and if you want to use the Multi-edit feature to quickly allocate vehicle combination sets
    (see "Allocating an attribute value to a different attribute" on page 988). This way you do
    not have to manually enter vehicle combination sets. Visum uses the vehicle combination set of a vehicle journey section for the line blocking with vehicle interchange
    (see "Executing the PuT line blocking procedure" on page 2104).
    15.28.6.3 Vehicle combinations: Cost rates tab
    Element

    Description

    Vehicle journeys

    Enter the cost rate per hour and per kilometer

    Empty trips

    Enter the cost rate per hour and per kilometer

    Depot

    Enter the cost rate for one hour in the depot

    Layover

    Enter the cost rate for a layover hour

    15.28.7 Editing the attribute values of vehicle combinations


    1. In the Network menu, select the PuT vehicles entry.
    The Vehicle units and combinations window opens.
    2. Make sure that the Vehicle combinations tab is open.
    3. In the list, select the desired vehicle combination.
    4. Click the

    PTVGROUP

    Edit button.

    1289

    15.28.8 Deleting vehicle combinations


    The Edit vehicle combination <Number> window opens.
    5. Edit the desired attributes (see "Properties and options of vehicle combinations" on page
    1287).
    6. Confirm with OK.
    The attributes of the vehicle combination are changed.
    Tip: You can edit vehicle combinations in the block view as well (see "Displaying line
    blocks in the block view" on page 2119).

    15.28.8 Deleting vehicle combinations


    1. In the Network menu, select the PuT vehicles entry.
    The Vehicle units and combinations window opens.
    2. Make sure that the Vehicle combinations tab is open.
    3. In the list, select the desired vehicle combination.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    4. Click the

    Delete button.

    5. Confirm with OK.


    The vehicle combination is deleted.
    Tip: You can delete vehicle combinations in the block view as well (see "Displaying line
    blocks in the block view" on page 2119).

    15.29

    Managing PuT directions


    In Visum, two opposite directions are provided for the public transport. You can allocate a
    code and a number to each direction.
    1. In the Network menu, select the PuT directions entry.
    The PuT directions window opens.

    2. In the Direction: up and Direction: down section, enter the desired data.
    3. Confirm with OK.
    1290

    PTVGROUP

    15.30 Managing lines


    Note: If you make changes in this window, they are applied to existing line routes (see
    "Managing line routes and time profiles" on page 1306).

    15.30

    Managing lines
    A line is a PuT network object. It structures the public transport supply. In Visum the line itself
    has no course in space. Rather, it has the purpose to combine the following network objects
    which are on a lower level in the line hierarchy (see Fundamentals: Chpt. 3.1.14 , page 68):
    Line routes
    One or several line routes which are allocated to a line specify a line's course in space.
    Time profiles
    Time profiles specify the travel times between the stop points of a line route.
    Vehicle journeys
    You can display and edit vehicle journeys in the Timetable editor (see "Managing vehicle
    journeys and vehicle journey sections" on page 1531).
    Vehicle journey sections
    You can display and edit vehicle journey sections in the Timetable editor (see "Managing
    vehicle journeys and vehicle journey sections" on page 1531).
    Several lines can be allocated to a main line (see "Managing line routes and time profiles" on
    page 1306).

    15.30.1 Specifying default values for lines and line routes


    Before you create a line, a line route or a time profile, you can specify the following standard
    values.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the entry Network> Lines.
    3. Enter the desired data.
    Element

    Description

    Specify line route Round to


    course run
    Here you can specify how the run time between two profile points
    times between pro- is to be rounded when specifying the line route course.
    file points
    Minimum
    Here you can select a minimum value for the run time between
    two profile points.
    Automatic numbering of vehicle
    journeys

    PTVGROUP

    Here you can specify how the vehicle journeys of a line route will
    be numbered when vehicle journeys are inserted, copied or coupled. Select one of the following options:
    Next available number
    Direction 'Up' = even, opposite direction 'Down' = odd

    1291

    15.30.2 Creating a line


    Element

    Description
    Direction 'Up' = odd, opposite direction 'Down' = even

    Default parameters for 'Specify course'

    Here you can specify standard settings for the path search, which
    will be used when specifying the course of line routes (see "Creating a line route" on page 1307).

    4. Confirm with OK.

    15.30.2 Creating a line


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Lines button.


    The Create window opens.
    3. Select the Line entry.
    4. Click in the network display.
    The Create line window opens.
    5. Enter the desired data (see "Properties and options of lines" on page 1292).
    6. Confirm with OK.
    The line is inserted. With the line route you specify the course of a line (see "Creating a line
    route" on page 1307).

    15.30.3 Properties and options of lines

    In the Edit line <Name> window you can display and edit line attributes. You can change here
    a line's transport system, for example. The upper section of the window contains the general
    attributes of the line. The lower section contains special attributes.

    1292

    PTVGROUP

    15.30.3 Properties and options of lines


    Lines: General attributes
    Element

    Description

    Name

    Name of the line

    Transport system In the drop-down list you can change the transport system of a line.
    You can select any public transport system that exists in the network.
    A change has these consequences:
    In the network:
    Visum permits the relevant links and turns in the new transport
    system.
    Visum permits the relevant stop points in the new transport system, if the time profile permits the boarding or alighting on this
    stop point.
    Visum discards assignments and results of the line costing and
    revenue calculation (if available).
    Within the line hierarchy:
    Visum checks the vehicle combination. If the allocated vehicle
    combination is not permitted for the new transport system, Visum
    removes the previous vehicle combination. This applies for the
    line, the time profile and the vehicle journey section. If the
    vehicle combination of a vehicle journey section is changed, line
    blocks get the status "Vehicle error".
    Main line

    Display of the main line if the line has been allocated to a main line
    Tip
    You can allocate a line to a main line via the Network> PuT main
    lines menu (see "Managing main lines" on page 1364).

    Standard vehicle
    combination

    In the drop-down list, you can select a standard vehicle combination


    for the line. When creating new vehicle journeys, it will then be suggested as standard value.
    Tip
    You can create vehicle combinations via the Network> PuT vehicles menu (see "Creating vehicle combinations" on page 1286).

    Standard operator In the drop-down list, you can select a standard operator for the line.
    Notes
    When creating new vehicle journeys, it will then be suggested as
    standard value.
    If you modify the standard operator of a line, the operator will not be
    adjusted for associated existing vehicle journeys.
    Tip
    You can create operators via the Network> PuT operators menu
    (see "Creating an operator" on page 1281).
    Fare systems

    PTVGROUP

    Here you can allocate a fare system or change it (see "Defining fare
    zones" on page 2169).
    1293

    15.30.4 Finding lines


    Lines: Basis tab
    Element

    Description

    Number of line rou- Display of the number of allocated line routes


    tes
    Number of time
    profiles

    Display of the number of time profiles of the allocated line route

    Number of vehicle Display of the number of vehicle journeys of the allocated line route
    journeys
    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes. Advantage: You can name
    user-defined attributes appropriately.

    15.30.4 Finding lines


    There are different possibilities to find lines:
    Finding a line directly
    Finding a line by vehicle journey
    15.30.4.1 Finding a line directly
    How to find lines directly is described for all network objects (see "Finding network objects in
    the network" on page 999).
    15.30.4.2 Finding a line by vehicle journey
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Press the hotkey SHIFT + F3.
    The Find a network object window opens.
    Tip: Alternatively, you can click the Find vehicle journey entry in the context-menu of
    the Lines button.
    4. In the list box, select the attribute you want to find.
    Note: The search by Name is only possible if a name has been entered for at least
    one vehicle journey.
    5. In the input field, enter the value or text you want to find.

    1294

    PTVGROUP

    15.30.5 Selecting lines


    As you type, the list automatically displays and marks the first attribute value that corresponds to the entered value or text.
    Note: If you click a vehicle journey in the list, the corresponding line will be marked in
    the network.
    6. If you want to enlarge the network section, click Autozoom.
    The network section is enlarged and the line is positioned in the middle of the section.
    7. In the list, double-click the desired search result.
    8. The Edit line route window opens.
    9. Click the Timetable editor button.
    The Timetable editor opens. All lines are displayed that contain a vehicle journey with the
    selected attribute. All vehicle journeys that have the selected attribute value are marked.

    15.30.5 Selecting lines


    There are several ways to select a line in order to edit it in another step.
    Marking lines
    Setting lines active/passive
    15.30.5.1 Marking lines
    You can only mark a line in the network if at least one line route and thus a course has been
    allocated to the line.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    Note: Depending on the selected option, the name of the Lines/Line routes window
    changes.

    PTVGROUP

    1295

    15.30.5.2 Setting lines active/passive


    3. Make sure that the Lines option has been selected.
    4. If required, restrict the number of lines which is searched.
    Element

    Description

    Only active ones

    If the option has been selected, only active lines are displayed.
    If the option has not been selected, all lines will be taken into
    account.

    5. In the Lines window click one line in the list. If you want to mark additional lines, press the
    CTRL key and keep it pressed. One by one, click the lines you want to mark.
    Tip: You can also use the input field to mark the line you are looking for. To do this,
    enter the name of the line in the field. The line is marked in the list.
    The marked lines' line route courses are highlighted in the network. Below the list you see a
    value (for example: 1(11)) that specifies the number of lines you have marked and the number of all lines.
    6. If required, click the Autozoom button.
    The current display of the network section is adjusted and the marked lines are in the
    middle of the network section.
    Tips: If you want to remove all marked lines from the selection, click the Initialize button.
    You can also mark the line route courses of a line, if you click on a stop point in the network which is traversed by a line route of the line.
    Alternatively, you can mark a line by selecting the respective row in the list of lines (see
    "Selecting list sections" on page 2319).
    15.30.5.2 Setting lines active/passive
    Network objects can be active or passive. There are several possibilities to set lines active:
    Via the line filter (see "Using filters to set network objects active or passive" on page 1008)
    Note: The spatial selection of select network objects of the line hierarchy (lines, line routes, line route items, time profiles, time profile items, vehicle journeys, vehicle journey sections) is not possible.
    By selecting the option for the desired lines in the Lines window, In selection column.
    In the Spatial selection toolbar, with a click on one of the following icons: Include all
    objects into the spatial selection, Invert spatial selection or Remove all objects from
    the spatial selection. (see "Setting network objects active/passive via the spatial selection" on page 1033)
    By editing the IsInSelection attribute per network object, for example, in the list of the
    respective network object. If you enter 1, the respective network object will be active, if you
    enter 0, it will be passive.
    1296

    PTVGROUP

    15.30.6 Editing the attribute values of lines

    15.30.6 Editing the attribute values of lines


    You can edit the attribute values of one line, all marked lines or all (active) lines.
    15.30.6.1 Editing the attribute values of a line
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Make sure that the Lines option has been selected.
    4. In the list, double-click the desired line.
    Tip: Alternatively, you can search for the desired line (see "Finding lines" on page
    1294).
    The Edit line window opens.
    5. Edit the values of the desired attributes (see "Properties and options of lines" on page
    1292).
    6. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of lines in the Quick view window or in the list of the network object type (see "Quick view window" on page 810 and
    "Working with lists" on page 2299).
    15.30.6.2 Editing the attribute values of marked lines
    1. Mark the desired lines whose attribute values you want to edit (see "Marking lines" on page
    1295).
    2. Press the ENTER key.
    The Multi-edit lines: <Number> objects window opens.
    Tip: You can also call the Multi-edit lines: <Number> objects window via the context
    menu > entry Edit or double-click the last line which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of lines" on page 1292
    and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.30.6.3 Editing the attribute values of all or all active lines

    PTVGROUP

    1297

    15.30.6.4 Displaying the attribute values of a line in a column chart


    Note: If there are no passive lines in the network, all lines are edited. Markings of lines
    are ignored.
    1. If required, set the lines active, whose attribute values you want to edit, via filter criteria (see
    "Using filters to set network objects active or passive" on page 1008).
    The selected lines are active.
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Lines entry.
    The Multi-edit lines window opens.
    4. Select whether you want to edit the attribute values of all lines or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active lines will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of lines" on page 1292
    and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.30.6.4 Displaying the attribute values of a line in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.30.7 Copying lines


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Make sure that the Lines option has been selected.
    4. In the Lines window, mark the line that you want to copy.
    5. Right-click in the network display.
    A shortcut menu opens.
    6. Select the Copy line entry.
    The Copy line window opens.

    1298

    PTVGROUP

    15.30.8 Lines: Opening the Timetable editor


    Element

    Description

    Line

    Enter the name of the new line. The name needs to be unique.

    Copy also all


    vehicle journeys

    Select this option if you want to copy all vehicle journeys as well.

    Also copy walk


    and wait times at
    stops

    Select this option if you want to copy walk and wait times as well.

    7. Confirm with OK.


    The line and all its attributes and line routes are copied. The line is listed in the Lines window.
    Note: Couplings that already exist on the original line are not copied.

    15.30.8 Lines: Opening the Timetable editor


    You can select lines in the Network editor and display them in the Timetable editor (see "Using
    the Timetable editor" on page 1526).
    Calling the timetable editor with selected lines
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Make sure that the Lines option has been selected.
    4. Press the CTRL key and keep it pressed.
    5. In the list, click the lines, one by one, which you want to display.
    6. Click the Timetable editor button.
    Notes: If the Timetable editor is already open, a query opens (see "Opening the Timetable editor" on page 1526).
    Alternatively, you can open the Timetable editor via the context menu.
    The Timetable editor opens. The selected lines are displayed.
    Calling the Timetable editor by a search for a vehicle journey
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Press the hotkey SHIFT + F3.
    The Find a network object window opens.
    PTVGROUP

    1299

    15.30.9 Aggregating lines

    Tip: Alternatively, you can click the Find vehicle journey entry in the context-menu of
    the Lines button.
    4. In the list box, select the attribute you want to find.
    Note: The search by Name is only possible if a name has been entered for at least
    one vehicle journey.
    5. In the input field, enter the value or text you want to find.
    As you type, the list automatically displays and marks the first attribute value that corresponds to the entered value or text.
    Note: If you click a vehicle journey in the list, the corresponding line will be marked in
    the network.
    6. If you want to enlarge the network section, click Autozoom.
    The network section is enlarged and the line is positioned in the middle of the section.
    7. In the list, double-click the desired search result.
    8. The Edit line route window opens.
    9. Click the Timetable editor button.
    The Timetable editor opens. All lines are displayed that contain a vehicle journey with the
    selected attribute. All vehicle journeys that have the selected attribute value are marked.
    Note: If the Timetable editor is already open, the view will change according to the
    search result.

    15.30.9 Aggregating lines


    With this functionality you can aggregate line routes and/or time profiles of one or several
    lines. Line routes and/or time profiles can be aggregated within one line or over several lines
    (see Fundamentals: Chpt. 3.1.14 , page 68).
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Make sure that the Lines option has been selected.
    4. If required, select the line in the list whose line routes you want to aggregate.
    Note: If you do not select a line, all lines will be included.
    5. Right-click in the network display.

    1300

    PTVGROUP

    15.30.9 Aggregating lines


    A context menu opens.
    6. Select the Aggregate entry.
    Note: If you have not selected a line in the Lines window beforehand, the menu entry
    is Aggregate all and all lines in the network will be included.
    The Aggregate line routes and time profiles window opens.
    Tip: Alternatively the window can be opened by pressing the F7 key.
    7. Make the desired changes:
    Element

    Description

    Aggregate only
    active line routes

    If the option has been selected, only the currently active line routes will be aggregated.
    Note
    The option is only available, if you have not selected a line in the
    list of the Lines window beforehand.

    Objects to be
    aggregated

    Aggregate line routes and time profiles


    If the option has been selected, all line routes and time profiles of
    the selected line(s) will be aggregated.
    Aggregate the belonging time profiles separately within line
    route
    If the option has been selected, the time profiles are aggregated
    separately per line route.

    Name of the aggre- If you have selected the Aggregate line routes and time profiles
    gated line route
    option, you can select one of the following options in the dropdown list:
    From line route with max. no. of vehicle journeys
    If the option has been selected, the name of the line route with the
    most vehicle journeys will be given to the aggregated line route.
    Note
    We recommend this option if you read in a large number of line
    routes with similar data from an external source which you want
    to aggregate.
    Generated name
    If the option has been selected, the aggregate line route receives
    a new generated name consisting of GEN + first available integer,
    for example GEN1.
    Line route criteria If you have selected the Aggregate line routes and time profiles
    option, you can select the following options:

    PTVGROUP

    1301

    15.30.9 Aggregating lines


    Element

    Description
    Aggregate only line routes of the same line
    If the option has been selected, only line routes of the same line
    will be aggregated.
    Line routes with identical direction
    If the option has been selected, only line routes with the same
    direction will be aggregated.
    Line routes with identical length of the section in common
    If the option has been selected, only line routes with identical
    lengths on common sections will be aggregated.
    Line routes have to have identical start stop points
    If the option has been selected, only line routes with the same
    start stop point will be aggregated.
    Line routes have to have identical end stop points
    If the option has been selected, only line routes with the same
    end stop point will be aggregated.
    Minimal route course share in common (measured in link
    length)
    If the option has been selected, only line routes whose items
    match a certain section of the same link will be aggregated.

    1302

    Time profile criteria

    For time profiles, you can select the following options:


    Time profiles with identical in-vehicle times and dwell times
    If the option has been selected, only those time profiles with identical run and dwell times between/at stop points will be aggregated.
    Time profiles with identical board/alight settings
    If the option has been selected, only time profiles with stop points
    with identical board/alight settings will be aggregated.
    Time profiles with identical vehicle combinations
    If the option has been selected, only time profiles with identical
    vehicle combinations will be aggregated.
    Note
    When aggregating, no distinction is made between coupled and
    non-coupled time profiles. Coupled time profiles are aggregated
    with uncoupled ones. The couplings are solved. Messages on solved couplings are saved to the log file (see "Using protocol files"
    on page 876).

    Lines

    Delete lines without line routes at the end of the procedure


    If the option has been selected, all lines with no line routes are
    deleted at the end of the operation.

    PTVGROUP

    15.30.10 Disaggregate lines


    Element

    Description
    Note
    It is not relevant, whether the line has no line route any more due
    to the aggregation or whether this was the case even before.

    Undo stack

    Clear Undo stack to save RAM


    If the option has been selected, no commands will be saved
    during the aggregation.

    8. Confirm with OK.


    The lines are aggregated and a window opens. It contains the name and the path of the
    aggregation protocol.
    9. Confirm with OK.
    Tip: You can open the aggregation protocol immediately, if you click the Open button.

    15.30.10 Disaggregate lines


    With this functionality you can disaggregate line routes and/or time profiles of one or multiple
    lines. Line routes and/or time profiles can be disaggregated within one line or over multiple
    lines.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    3. Make sure that the Lines option has been selected.
    4. If required, select the line in the list whose line routes you want to disaggregate.
    Note: If you do not select a line, all lines will be included.
    5. Right-click in the network display.
    A context menu opens.
    6. Select the Disaggregate entry.
    Note: If you have not selected a line in the Lines window beforehand, the menu entry
    is Disaggregate all and all lines in the network will be included.
    The Disaggregation of lines, line routes, and time profiles window opens.
    7. Make the desired changes.

    PTVGROUP

    1303

    15.30.10 Disaggregate lines


    Element

    Description

    Disaggregate only If the option has been selected, only the currently active network
    active network
    objects will be disaggregated.
    objects
    Note
    The option is only available, if you have not selected a line or line
    route in the Lines window beforehand.
    Disaggregate time If this option has been selected, a time profile will be created for
    profiles
    each vehicle journey.
    Note
    Couplings and specific walk and wait times of time profiles are
    duplicated and remain unchanged.
    Suffix for names
    of new time profiles

    Via this button you can select an attribute of the network object
    from the underlying line hierarchy as suffix. The suffix is appended to the name of the newly created network object.
    Note
    The button is only available if the Disaggregate time profiles
    option has been selected.

    Disaggregate line
    routes

    If this option has been selected, a line route is created for each
    time profile.

    Shorten the line


    route course to
    the vehicle journey course

    If this option has been selected, all created line routes are shortened to the vehicle journey course.
    Note
    This option is only available if you have selected the Disaggregate time profiles and Disaggregate line routes options.

    Suffix for names


    of new line routes

    Via this button you can select an attribute of the network object
    from the underlying line hierarchy as suffix. The suffix is appended to the name of the newly created network object.
    Note
    The button is only active if the Disaggregate line routes option
    has been selected.

    Disaggregate
    lines

    If this option has been selected, a line is created for each line
    route.

    Suffix for names


    of new lines

    Via this button you can select an attribute of the network object
    from the underlying line hierarchy as suffix. The suffix is appended to the name of the newly created network object.
    Note
    The button is only active if the Disaggregate lines option has
    been selected.

    8. Confirm with OK.


    The lines are disaggregated.
    1304

    PTVGROUP

    15.30.11 Deleting lines

    15.30.11 Deleting lines


    There are several ways to delete lines.
    Notes: If you delete a line, all associated line routes, time profiles and vehicle journeys
    will also be deleted.
    If you delete lines, existing public transport assignment results will be reset.
    15.30.11.1 Deleting marked lines
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Lines window opens.
    Note: Depending on the selected option, the name of the Lines/Line routes window
    changes.
    3. Make sure that the Lines option has been selected.
    4. Mark the lines you want to delete.
    5. Press the DEL key.
    The Delete lines window opens. There you find a description of the scope of the delete process.
    6. Confirm with OK.
    If you have selected one line, it will be deleted.
    If you have selected several lines, a window opens. It describes the first line that you want
    to delete and all associated network objects that will be deleted with the line.
    7. Click one of the following buttons:
    Element

    Description

    Yes

    Confirm each line that will be deleted with the associated network
    objects.

    Yes for all

    Confirm the deletion of all remaining selected lines with the associated network objects.

    No

    The displayed line will not be deleted. The next line is displayed
    for deletion.

    No for all

    None of the remaining selected lines will be deleted.

    The confirmed lines are deleted.

    PTVGROUP

    1305

    15.30.11.2 Deleting active lines


    15.30.11.2 Deleting active lines
    1. Select the lines, which you want to delete. To do this, use filter criteria (see "Using filters to
    set network objects active or passive" on page 1008).
    The selected lines are active.
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-delete> Lines entry.
    A query opens.
    Tip: If the network type Lines has been selected, you can also delete all active lines
    via the Edit> Multi-delete > Lines menu or by pressing the D EL key.
    4. Confirm with OK.
    The Delete lines window opens.
    5. Select which lines you want to delete.
    Element

    Description

    Yes

    Confirm each line that will be deleted with the associated network
    objects.

    Yes for all

    Confirm the deletion of all remaining active lines with the associated network objects.

    No

    The displayed line will not be deleted. The next active line is displayed for deletion.

    No for all

    None of the remaining active lines will be deleted.

    The confirmed lines are deleted.

    15.31

    Managing line routes and time profiles


    A line route is part of exactly one line and describes one local route course of the line for one
    direction (see Fundamentals: Chpt. 3.1.14 , page 68). It is a sequence of route points and contains one or more time profiles (see "Creating a time profile" on page 1320).

    15.31.1 Opening the Line routes window


    The line route to be edited is selected via the identically named window. To open the Line routes window, proceed as follows.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Lines button.


    The Line routes or Lines window opens.
    Note: Depending on the selected option, the name of the window changes.
    1306

    PTVGROUP

    15.31.2 Creating a line route


    3. Make sure that the Line routes option has been selected.

    The Line routes window lists all line routes which exist in the network.

    15.31.2 Creating a line route


    Note: Please take notice of the rules for editing a course (see "Basic rules: Editing a route
    course" on page 1340).
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Lines button.


    The Create window opens.
    3. Select the Line route entry.
    4. Click in the network display.
    The Create line route window opens.

    5. Enter the desired data.

    PTVGROUP

    1307

    15.31.2 Creating a line route


    Element

    Description

    Line

    In the drop-down list, select the line to which you want to allocate
    the line route.
    Only active lines
    If the option has been selected, only active lines can be selected.

    Name

    Enter a name for the line route


    Note
    The drop-down list contains the names of all line routes in the network. The name of the new line route must differ from the existing
    ones.

    Direction

    Use the drop-down list to select a direction (see "Managing PuT


    directions" on page 1290).

    Transport system Display of the transport system of the selected line


    Standard operator Display of the standard operator of the selected line
    Main line

    Display of the main line, if the selected line has been allocated to
    a main line (see "Managing main lines" on page 1364)

    6. Confirm with OK.


    The Edit shape of line route window opens.
    7. Click the stop point where you want the line route to start and hold down the mouse button.
    Note: A line route must start and end at a stop point.
    8. Drag the mouse to the next stop point or node, via which the line route shall run and
    release the mouse button.
    Notes: Preferably, you should select nodes. This way, you avoid inadvertently selecting a stop point of the opposite direction.
    If required, click the Autozoom button in the Edit shape of line route window, if you
    want to enlarge the section with the course.
    9. If required, proceed in the same manner to create any other sections you wish to create.
    Notes: If required, click the Undo button in the Edit shape of line route window, if you
    want to delete the last section of the line route course.
    If a stop point or a node is traversed more than once, the Line route: edit shape window opens. In the window, select the node/stop point that you want to traverse.
    10. Drag the mouse button to the desired endpoint of the line route and release the mouse button.

    1308

    PTVGROUP

    15.31.2 Creating a line route


    Tip: You can also drag the mouse directly from the first stop point to the desired end
    stop point. The program will then suggest the best path based on the set search criterion (see "Line routes: specifying parameters for the path search" on page 1309).
    11. Click the OK button in the Edit shape of line route window.
    The line route is inserted.
    Note: You can create the opposite direction of the line route via the context menu (see
    "Creating the opposite direction of a line route" on page 1357).
    If system routes exist in the network and you have specified the first stop point, you can
    use the Tabular editing button to create a line route course based on the route courses
    of system routes (see "Tabular editing of a line route course" on page 1347).
    You can edit the course of a line route later (see "Editing the shape of a line route
    course" on page 1338).
    Line routes: specifying parameters for the path search
    Note: In the Edit> User Preferences menu, first of all, you can specify the standard
    values for the path search (see "Specifying default values for lines and line routes" on
    page 1291).
    1. Make sure that the Edit shape of line route window is open (see "Editing the shape of a
    line route" on page 1338).
    2. In the Edit shape of line route window, click the Parameters button.
    The Parameters: Line route course search window opens.

    3. Make the desired changes.


    Element

    Description

    Use also closed


    links for routing

    If the option has been selected, the links closed to the transport
    system will be taken into account, as if they were open to the
    transport system.

    Use also closed

    If the option has been selected, the turns closed to the transport

    PTVGROUP

    1309

    15.31.2 Creating a line route


    Element

    Description

    turns for routing

    system will be taken into account, as if they were open to the


    transport system.

    Serve stop points


    of new route

    If the option has been selected, the stop points of the new
    course will also be served.
    If the option has not been selected, the new line route will only
    serve the stop points that existed before the rerouting of the
    course.

    Serve only active


    stop points

    If the option has been selected, passive stop points are not taken
    into account.
    Note
    The option is only available, if you have selected the Serve stop
    points of new route option.

    For the re-routed


    section, generate
    the run time from
    the link network

    Note
    This option is only provided when editing a line route course.
    When creating a new course, the transport system-specific link
    run time is used.
    If the option has been selected, the transport system-specific
    link run time is used for the transport system of the line and for all
    traversed links.
    If the option has not been selected, the run times of the time
    profile are kept. In the new course, they are distributed proportional to the length.

    1310

    Lengthen vehicle
    journeys automatically

    If this option has been selected, the vehicle journeys of the line
    route are also lengthened if the line route is lengthened.

    Search criterion

    From the drop-down list, you can select a criterion for the path
    search. The search finds the best path each between two marked
    (fixed) stop points.
    Link length (direct distance)
    Direct distance link length from the origin to the destination stop
    point
    Link run time
    Is calculated from the transport system speed of the links
    Time from speed def. by link type
    Is calculated from the transport system speed specified for the
    respective link type
    Link length
    Calculated link length if not manually adjusted by the user

    If this option has not been selected, the extension of the


    vehicle journeys remains unchanged.

    PTVGROUP

    15.31.3 Properties and options of line routes and time profiles


    4. Confirm with OK.

    15.31.3 Properties and options of line routes and time profiles

    The upper section of the Edit line route window contains the general attributes of the lines
    route. In the lower section, you can edit specific attributes in various tabs. In the User-defined
    attributes: Line route and User-defined attributes: Time profiles , all user-defined attributes
    for line routes and time profile are displayed (see "Managing user-defined attributes" on page
    973).
    Use the Edit shape button to open the identically named window, in which you can edit the
    course of a line route manually or with the aid of tables (see "Tabular editing of a line route
    course" on page 1347).
    Use the Timetable editor window to open the currently selected line route in the Timetable editor. Changes will be applied in this case.
    Note: You can apply your changes anytime without exiting the Edit line route window by
    clicking the Apply button.
    15.31.3.1 Line routes: General attributes
    Element

    Description

    Line

    Select the line to which the line route is allocated

    Show only active


    lines

    If the option has been selected, only active lines are displayed in the
    list.

    PTVGROUP

    1311

    15.31.3.2 Line routes: Basis tab


    Element

    Description

    Name

    Name of the line

    Direction

    Use the drop-down list to select a direction (see "Managing PuT directions" on page 1290).

    15.31.3.2 Line routes: Basis tab


    Element

    Description

    Transport system Display of the transport system of the selected line


    Start stop point

    Display of the name of the start stop point of the line route. It consists
    of the stop point attributes number and code or number and name, if
    no code is specified.

    End stop point

    Display of the name of the end stop point of the line route. It consists
    of the stop point attributes number and code or number and name, if
    no code is specified.

    Number of stop
    points

    Display of the number of the stop points in the course of the line route

    Number of stop
    points TSys

    Display of the stop points in the course of the line route, which of the
    stop points specified under Number stop points are permitted for the
    line.

    Line route length

    Display of the total length of the traversed links

    Link run time

    Display of the transport system run time of the line route, determined
    from the length and the speed per transport system

    Standard dwell
    time

    Display of the standard stop times at served stop points (without start
    stop point and end stop point)
    Tip
    In the time profile, you can edit the stop time per stop point (see "Line
    routes: Items and time profiles tab" on page 1313).

    Number of vehicle Display of the number of vehicle journeys of the line route
    journeys
    Coupling defined

    1312

    Yes/No
    Display whether the line route contains couplings

    PTVGROUP

    15.31.3.3 Line routes: Items and time profiles tab


    Element

    Description

    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes. Advantage: You can name
    user-defined attributes appropriately.

    Circle line

    If this option has been selected, no transfer time penalty will be considered for a line if the journey is continued with the same line, starting from the end stop point of the line route.
    Note
    This option is only available if the start stop point and the end stop
    point of a line route are identical.

    15.31.3.3 Line routes: Items and time profiles tab


    In this tab, on the left, you can edit the line route items, on the right, you can edit the corresponding time profiles. The sections correspond with each other.

    Note: You can adjust the partition of the sections by dragging the divider with the mouse.
    Editing line route items
    To edit the line route items, the following icons are provided on the left:

    PTVGROUP

    1313

    15.31.3.3 Line routes: Items and time profiles tab


    Element Description
    Use the Recalculate lengths icon to calculate the lengths between the network
    objects currently set as IsRoutePoint after redefining the route points.
    The Recreate route point property for one or several rows icon opens the
    Set route points window. In the window, check the desired option to specify
    which stop points shall be route points (see "Setting route points" on page
    1314).
    The Select rows to be displayed icon opens the Select visible rows window.
    In the window, you can specify which rows shall be displayed in the Items and
    time profiles window.
    Note
    If the All option has been selected, all stop points and nodes along the way of
    the line route, i.e. all line route items, will be displayed.
    Use the Select attributes for table to the left icon to open the Attribute selection window, in which you can select the desired line route item attributes (see
    "The window used for the selection of one attribute" on page 963).
    Notes
    The Index column provides information on the line route items. The number 1 is
    allocated to the start stop point, the highest number is allocated to the end stop
    point.
    The number of line route items displayed here in accordance with the current
    settings is indicated at the bottom left of the window.

    Note: The link attribute Number of touching line routes indicates the number of the line
    routes that traverse an arbitrarily small section of a link. You can, for example, use it in
    the link list or in the link filter.
    Setting route points
    The course of the line route is issued as a classified series of route points. A route point is a
    reference to a node or a stop point in the network. Specify as follows for which stop points you
    want to set route points.
    Note: If you only want to select specific stop points as route points, in the list of route
    points, check the respective box in the Is route point column.
    1. In the Items and time profiles tab, click the
    several rows icon.

    Recreate route point property for one or

    The Set route points window opens.


    2. Make the desired changes.

    1314

    PTVGROUP

    15.31.4 Finding line routes


    Element

    Description

    Setting route points Select the desired option:


    For all
    For all stop points
    For all stop points of TSys
    For all active stop points
    Set route point proIf the option has been selected, the property is set for the selected group.
    perty to
    If the option has not been selected, the property is only set for
    the start stop point and the end stop point.
    Apply

    Adds the route points of the selection to the existing selection and
    closes the Set route points window.

    Set exclusively

    Sets the route points of the selection exclusively and closes the
    Set route points window.

    3. Confirm with OK.


    The selection is set as route points.
    Note: If not all desired items are displayed, you can edit the display via the Select visible
    rows icon.
    Adjusting time profiles automatically
    You can specify that, on the right side, a profile point is set automatically for all time profiles of
    the line route, when inserting a route point on the left side.
    In the Items and time profiles window, select the Adapt time profiles automatically
    option.

    15.31.4 Finding line routes


    There are several ways to find line routes.
    Finding a line route directly
    Searching a line route by vehicle journey
    15.31.4.1 Finding a line route directly
    How to find line routes directly is described for all network objects (see "Finding network
    objects in the network" on page 999).
    15.31.4.2 Searching a line route by vehicle journey
    1. In the Network window, click the

    Edit mode window.

    2. Click the Lines button.


    The Lines window opens.
    3. Press the hotkey SHIFT + F3.
    PTVGROUP

    1315

    15.31.5 Managing time profiles


    The Find a network object window opens.
    Tip: Alternatively, you can click the Find vehicle journey entry in the context-menu of
    the Lines button.
    4. In the list box, select the attribute you want to find.
    Note: The search by Name is only possible if a name has been entered for at least
    one vehicle journey.
    5. In the input field, enter the value or text you want to find.
    As you type, the list automatically displays and marks the first attribute value that corresponds to the entered value or text.
    Note: If you click a vehicle journey in the list, the corresponding line will be marked in
    the network.
    6. If you want to enlarge the network section, click Autozoom.
    The network section is enlarged and the line is positioned in the middle of the section.
    7. In the list, double-click the desired search result.
    8. The Edit line route window opens.
    9. Click the desired button.
    Element

    Description

    Timetable editor

    The button opens the timetable editor. All lines are displayed that
    contain a vehicle journey with the selected attribute. All vehicle
    journeys that have the selected attribute value are marked.

    Edit line route

    The button opens the window to edit line routes and time profiles
    (see "Properties and options of line routes and time profiles" on
    page 1311).

    The Timetable editor opens. All lines are displayed that contain a vehicle journey with the
    selected attribute. All vehicle journeys that have the selected attribute value are marked.

    15.31.5 Managing time profiles


    Time profiles specify the lengths of the run times between the stop points of a line route and
    indicate, whether boarding or alighting is permitted at the stop points of the line route. They
    are displayed in the right section of the Items and time profiles tab of the Edit line route window (see "Line routes: Items and time profiles tab" on page 1313).
    Note: The time profiles of a line route are edited in separate tabs. You can switch between the tabs (similar to Excel).

    1316

    PTVGROUP

    15.31.5 Managing time profiles


    Note: If you edit the course of a line route, the vehicle journeys and vehicle journey sections of the line route are affected (see "Editing the shape of a line route course" on page
    1338 and "Effects on vehicle journeys and vehicle journey sections" on page 1344).
    Accessing time profiles
    Each line route has one or more time profiles. A (time) profile describes the temporal
    sequence of the line along the line route, yet without specific departure times and thus vehicle
    journeys. The time profiles created for a line route are displayed in different tabs. The names
    of time profiles set passive are displayed in italics here. If the selected line route has more
    than one time profile, a Multiple tab is displayed (see "Multiple display of time profiles" on
    page 1333).
    In the Items and time profiles tab of the Edit line routes window, click the name of the
    desired profile, for example 2.

    The desired time profile is displayed.


    Editing time profile items
    On the right of the Items and time profiles tab, the following icons are provided to edit the time
    profile items:
    Element

    Description
    Use the Create new time profile icon to create a new time profile (see "Creating a time profile" on page 1320).
    Use the Copy current time profile icon to copy an existing time profile (see
    "Copying a time profile" on page 1320).
    Use the Edit current time profile icon to edit an existing time profile (see
    "Editing a time profile" on page 1321)
    Use the Delete current time profile icon to delete an existing time profile
    (see "Deleting a time profile" on page 1334).
    Use the Set new times for current time profile icon to open the Set times
    for time profile <Number> window. Here you can recalculate the run and
    dwell times of a time profile (see "Editing a time profile" on page 1321).
    Use the Change times of the current time profile's vehicle journeys icon to
    postpone all vehicle journeys by a desired time (see "Shifting the departure
    times of vehicle journeys" on page 1327).
    Use the Couple selection with other time profiles icon to combine different
    time profiles on common sections (see "Coupling multiple time profiles" on
    page 1331).
    Use the Remove coupling of selection icon to remove the coupling of combined time profiles (see "Coupling multiple time profiles" on page 1331).

    PTVGROUP

    1317

    15.31.5.1 Setting the reference journey for a time profile


    Element

    Description
    Use the Specify the time profiles to be displayed in the multi-view icon to
    display multiple time profiles next to each other in order to compare their attributes (see "Multiple display of time profiles" on page 1333).
    Use the Select attributes for table to the right icon to open the Attribute
    selection window, in which you can select the desired time profile item attributes (see "The window used for the selection of one attribute" on page 963).

    Deleting time profile items


    You can delete individual or all time profile items.
    1. If required, set the time profile items active that you want to delete
    Via the line filter (see "Using filters to set network objects active or passive" on page
    1008)
    Note: The spatial selection of network objects of the line hierarchy (lines, line routes, line
    route items, time profiles, time profile items, vehicle journeys, vehicle journey sections) is
    not possible. You can, however, add or remove the network objects of these network
    object types to/from the selection in various different ways (see "Setting active/passive
    line routes" on page 1336).
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-delete> Time profile items entry.
    A query opens.
    4. Confirm the query by OK or OK for all.
    All time profile items are deleted.
    Tip: If the network object type Lines has been selected, all active time profile items can
    be deleted via the Edit> Multi-delete menu.
    15.31.5.1 Setting the reference journey for a time profile
    In the Items and time profiles tab, you can specify a reference journey per time profile via a
    drop-down list. The output of the times in the Arrival and Departure columns, which you can
    select for display, depends on this vehicle journey.
    Note: You can edit the times in the Arrival and Departure rows later, apart from the arrival at the first item and the departure at the last item.
    1. Click the time profile that you want to edit.

    2. In the drop-down list below the divided window, select a Reference journey.
    1318

    PTVGROUP

    15.31.5.1 Setting the reference journey for a time profile

    Note: If No reference journey is selected in the list or if a time profile does not have
    any vehicle journeys, the displayed arrival and departure times are standardized and
    thus refer to a presumed start departure time of 00:00 at the beginning of the profile.
    The specific times of the reference journey are displayed in the Arrival and Departure
    columns instead of the usual values.
    Notes: If a vehicle journey does not cover the full course of a time profile, virtualtimes
    are issued at the missing time profile items. Virtual times are displayed in italics.
    As long as the Edit line route <Name> window is open,
    for each time profile, the program saves which Reference journey has been selected,
    the Arrival and Departure display is adjusted automatically, if you select a new time
    profile.
    The information is not saved once the window is closed.
    When opening the window or switching to a time profile which has not yet been displayed, the reference journey is automatically set to No reference journey or to the First
    journey of the time profile, based on the setting under Edit> User Preferences> GUI>
    Miscellaneous (see "Standard setting for reference journeys" on page 1319).
    Standard setting for reference journeys
    Before you create a time profile, you can specify the standard setting for reference journeys.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select GUI> Miscellaneous.
    3. Select the desired option.
    Default setting for
    reference journey
    in time profile dialog

    No reference journey
    If the option has been selected, the displayed arrival and departure times are standardized and thus refer to a presumed departure time of 00:00 at the beginning of the profile.
    First vehicle journey
    If the option has been selected, the times of the first vehicle journey listed in the Reference journey drop-down list will be displayed in the Edit line route <Name>> Items and time profiles
    window, whose absolute temporal position influences the displayed Arrival and Departure attributes (see "Setting reference
    stop points" on page 1327).

    4. Confirm with OK.

    PTVGROUP

    1319

    15.31.5.2 Creating a time profile


    15.31.5.2 Creating a time profile
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. In the list, double-click the desired line route.
    The Edit line route window opens.
    3. Select the Items and time profiles tab.
    The tab contains all time profiles of the line route that exist in the network.
    4. Click the

    Create new time profile icon.

    The Create time profile window opens.


    5. Make the desired changes.
    Element

    Description

    Line

    Display of the line to which the time profile is allocated

    Line route

    Display of the line route to which the time profile is allocated

    Direction

    Display of the direction allocated to the time profile (see "Managing PuT directions" on page 1290)

    Name

    Enter a name for the new time profile in the input field.

    VehComb.

    In the drop-down list, select the desired vehicle combination.

    6. Confirm with OK.


    The time profile is inserted.
    Note: All stop points of the route points marked when editing the shape of the line route
    turn into profile points.
    Tip: Time profiles are also listed in the Time profiles tab of the stop point windows which
    are included in the course of the respective time profile (see "Managing stop points" on
    page 1266).
    15.31.5.3 Copying a time profile
    You can also create a new time profile by copying the currently selected time profile.
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. In the list, double-click the desired line route.
    The Edit line route window opens.
    3. Select the Items and time profiles tab.
    The tab contains all time profiles of the selected line route.
    4. Click the time profile that you want to copy.

    1320

    PTVGROUP

    15.31.5.4 Editing a time profile

    5. Click the

    Copy current time profile icon.

    The Copy time profile <Name> window.


    6. Make the desired changes.
    Element

    Description

    Line

    Display of the line to which the time profile is allocated

    Line route

    Display of the line route to which the time profile is allocated

    Direction

    Display of the direction allocated to the time profile (see "Managing PuT directions" on page 1290)

    Name

    Enter a name for the new time profile in the input field.

    VehComb.

    In the drop-down list, select the desired vehicle combination.

    Copy also all


    vehicle journeys

    If the option has been selected, together with the time profile, all
    vehicle journeys will be copied.
    Note
    If you change the vehicle combination to a vehicle combination
    deviating from a vehicle journey, the new vehicle journey still
    adopts the vehicle combination of the vehicle journey that is
    copied.

    Also copy walk


    and wait times at
    stops

    If the option has been selected, the walk and wait times at stops
    are copied together with the time profile.

    7. Confirm with OK.


    The time profile is copied and inserted.
    15.31.5.4 Editing a time profile
    You can edit an existing time profile in the Items and time profiles tab of the Edit line route
    window.
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. In the list, double-click the desired line route.
    The Edit line route window opens.
    3. Select the Items and time profiles tab.
    The tab contains all time profiles of the selected line route.

    PTVGROUP

    1321

    15.31.5.4 Editing a time profile


    Notes: You can edit the values in the white fields immediately if you double-click in the
    desired field.
    You can also call the Items and time profiles tab in the Timetable editor by marking the
    corresponding vehicle journey and selecting the Edit time profile entry in the context
    menu. In the Timetable editor only one vehicle journey is allowed to be marked.
    Editing the name or the vehicle combination of a time profile
    You can edit the name or the vehicle combination of a time profile.
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window.
    2. Click the time profile that you want to edit.

    3. Click the

    Edit current time profile button

    The Edit time profile <Name> window opens.


    4. Edit the name and/or the vehicle combination of the time profile.
    5. Confirm with OK.
    The time profile is modified.
    Setting the times for a time profile
    You can recalculate the run and dwell times of a time profile.
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window.
    2. Click the time profile that you want to edit.

    3. Click the

    Set new times for current time profile button.

    The Set times for time profile <Name> window opens.

    1322

    PTVGROUP

    15.31.5.4 Editing a time profile

    4. Make the desired changes.


    Element

    Description

    Only active
    time profile
    items

    If the option has been selected, passive time profile items are not
    taken into account.

    Sum up
    values

    If the option has been selected, new values are added to existing
    values.
    If the option has not been selected, existing values are replaced by
    new values.

    Add values
    If the option has been selected, new values are added to existing
    (only time pro- values. For a time profile item without vehicle journey the values are
    file items with set to zero.
    vehicle jourIf the option has not been selected, existing values are replaced by
    neys, set
    new values.
    those without
    veh. journ. =0)
    Time profile
    items without
    vehicle journeys

    PTVGROUP

    There are the following possibilities to treat time profile items which
    are not used by vehicle journeys.
    Set times for all (active) time profile items
    If this option has been selected, new run and dwell times are set for all

    1323

    15.31.5.4 Editing a time profile


    Element

    Description
    (active) time profile items.
    Set run and dwell time = 0 for time profile items without vehicle journeys
    If this option has been selected, the run and dwell time of time profile
    items without vehicle journeys are set to 0.
    Delete time profile items without vehicle journeys, if possible, otherwise set times = 0
    If this option has been selected, time profile items without vehicle journeys will be deleted. If this is not possible, the run and dwell times will
    be set to 0. Note
    This is not possible for the first or the last item of a time profile if a
    vehicle journey or a vehicle journey section starts or ends there, or if a
    coupling or coordination group starts or ends at this time profile item.

    Travel times

    Update
    If the option has been selected, the respective run times of the selected time profile are recalculated and issued according to the current
    settings.
    From link run time
    If the option has been selected, the run times of the link run times are
    used.
    From system routes
    If the option has been selected, the times from the system routes are
    used.
    From link attribute
    If the option has been selected, you can specify a weighting factor and
    a link attribute or subattribute, based on which the run time will be calculated.
    From time profile item attribute
    If the option has been selected, you can specify a weighting factor and
    a time profile item attribute or subattribute, based on which the run
    time will be calculated.
    Constant
    If the option has been selected, you can enter a constant run time.
    Round to
    Use the drop-down list to select the number of seconds to which you
    want to round.
    Set times only if VehComb fits
    If the option has been selected, the specific vehicle combination times
    will be used instead of the dwell time of the system route.

    1324

    PTVGROUP

    15.31.5.4 Editing a time profile


    Element

    Description
    Note
    The option is only available, if the From system routes option has
    been selected.
    Regard only active links
    If the option has been selected, passive links will not be taken into
    account.
    Note
    The option is only available, if the From link times or the From link
    attribute option has been selected.

    Dwell times

    Update
    If the option has been selected, the respective dwell times of the selected time profile are recalculated and issued according to the current
    settings.
    Notes
    An update of the dwell times can have the following effect on the rounding of the run times:
    When updating the dwell times, despite rounding the current run time
    will still be the sum of the run times From stop point - To stop point. A
    run time = 0 can be allocated to a section, if necessary.
    If the dwell times are not updated, rounded times may deviate from previous run times.
    From stop point time
    If the option has been selected, the standard dwell times of single stop
    points can be used.
    From stop point attribute
    If the option has been selected, you can specify a weighting factor and
    a stop attribute or subattribute, based on which the dwell time will be
    calculated.
    From time profile item attribute
    If the option has been selected, you can specify a weighting factor and
    a time profile item attribute or subattribute, based on which the dwell
    time will be calculated.
    Constant
    If the option has been selected, you can enter a constant dwell time.
    Round to
    Use the drop-down list to select the number of seconds to which you
    want to round.

    5. Confirm with OK.


    The selected rows are updated.
    PTVGROUP

    1325

    15.31.5.4 Editing a time profile

    Note: You can edit the Arrival and Departure later in the Edit line route window, apart
    from the arrival and the departure at the first item and the departure at the last item.
    Setting time profile times during a procedure sequence
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the desired position of the procedure sequence, insert the Set run and dwell times operation of the Miscellaneous category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The Set time data for time profiles window opens.
    4. Make the desired settings (see "Setting the times for a time profile" on page 1322).
    5. Confirm with OK.
    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The times for the time profiles are set.
    Setting times for time profile items
    You can generate run and dwell times for time profile items.
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Set time data for time profiles entry.
    The Multi-edit time profile items window opens.
    Tip: If the network object type Lines has been selected, you can also open the Multiedit time profile items window via the Edit> Set time data for time profiles menu.
    3. Make sure that the Special functions tab is selected.
    4. Specify whether you want to generate times for all or all active time profile items.
    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active time profile items will be taken
    into account.

    5. Click the Set times button.


    The Set time data for time profiles window opens.
    1326

    PTVGROUP

    15.31.5.4 Editing a time profile


    6. Make the desired settings (see "Setting the times for a time profile" on page 1322).
    7. Confirm with OK.
    Run and dwell times are generated for all or all active time profile items.
    8. Click the Close button.
    Shifting the departure times of vehicle journeys
    You can shift all vehicle journeys of a selected time profile.
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window.
    2. Click the time profile that you want to edit.
    3. Click the

    Change times of the current time profile's vehicle journeys button.

    The Shift vehicle journey(s) window opens.

    4. Make the desired changes.


    Element

    Description

    Shift vehicle journey(s) by

    Enter the time by which you want to shift the vehicle journeys.
    Notes
    If you do not enter a unit, the value is interpreted as minutes.
    You cannot change the time of a vehicle journey to a earlier point
    in time which is before 00:00 (12:00 a.m.). If you try to do this, a
    warning is displayed. The current time will not be changed.

    Earlier/later

    Depending on the selected option, the vehicle journeys are shifted in the desired direction.

    5. Confirm with OK.


    The vehicle journeys are shifted.
    Setting reference stop points
    All vehicle journeys have a reference stop point at which the departure and arrival times are
    fixed for all vehicle journeys if the run time or stop time changes.
    Note: If no reference stop point is set, the first stop point becomes the reference stop
    point.
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window.
    PTVGROUP

    1327

    15.31.5.4 Editing a time profile


    2. Click the time profile that you want to edit.
    3. In the right section of the window, right-click in the row that you want to fix.
    A context menu opens.
    4. Fix either the departure time or the arrival time by selecting the entry Fix departure time or
    Fix arrival time.
    The selected row is highlighted.
    Notes: You can undo the fixing with another right-click in the fixed row.
    The reference stop point correlates with the Reference item index attribute, which you
    can access in the time profile lists (see "Working with lists" on page 2299).
    Changes to the reference stop point do not take effect immediately but after subsequent
    operations.
    The reference stop point is not considered when shifting vehicle journeys. This applies to
    both, explicit shifting, for example in the Timetable editor (see "Using the Timetable editor" on page 1526), or in case of adjustment shifting of vehicle journeys in different time
    profiles attributable to couplings (see "Coupling multiple time profiles" on page 1331).
    Editing the run and dwell times of a section
    The buttons you see in the <> column (comparison of run and dwell times), inform you about
    identical and deviating run times on a common section (from stop point to stop point). They
    serve for adjusting the run and dwell times on this section. Use the button so edit the run and
    dwell times of individual sections. They have the following meanings:
    Element Description
    Several line routes with identical run times serve this section.
    Several line routes with deviating run times serve this section.
    This route section is contained in the currently selected time profile only.
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window.
    2. Click the tab of the time profile you want to edit.

    3. In the <> column click the

    or

    button.

    The Comparison of run times and dwell times of parallel lines between SP <Name> and
    SP <Name> window opens.
    Note: The window does not open, if you click the
    button. You cannot edit the times
    of this section in a separate window, as the section is only contained in the current
    time profile.

    1328

    PTVGROUP

    15.31.5.4 Editing a time profile

    The window lists all time profiles which serve this section. If system routes serve the section, they are also listed in the window. For each vehicle journey combination, a system
    route entry is listed, also for the default. System route entries are highlighted.
    Note: In the window, you can also edit the run times of system routes.
    4. Make the desired changes.
    Note: If you do not enter a unit, your entry is interpreted as minutes.
    Element

    Description

    Check boxes

    Use the check boxes at the beginning of the row to select each
    time profile and each system route separately in order to edit the
    run and dwell times.
    Tip
    You can also edit single cells individually, if you double-click the
    cell.

    Check all /
    Uncheck all

    Use the buttons to select all time profiles and system routes at the
    same time or to remove them from the selection.

    Show only active


    time profiles

    If the option has been selected, only active time profiles are listed
    in the window.

    As dwell time for


    all

    You can enter a dwell time in the input field at the bottom left and
    apply this time to all selected time profiles by clicking the As
    dwell time for all button. The dwell time is then saved for all selected rows.
    Note
    You cannot specify dwell times for system routes.

    PTVGROUP

    1329

    15.31.5.4 Editing a time profile


    Element

    Description

    As run time for all You can enter a run time in the input field at the bottom left and
    apply this time to all selected time profiles and system routes by
    clicking the As run time for all button. The run time is then saved
    for all selected rows.
    For all

    You can transfer a time specified in the Run time column to all
    other rows, if you click the For all button in the relevant row.

    5. Confirm with OK.


    The changed times are applied.
    Specifying fare points for time profiles
    You can use fare points to model fares. They enter the impedance function and are used in the
    revenue calculation.
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window.
    2. Click the tab of the time profile you want to edit.

    3. Use the
    Select attributes for table to the right icon to select the following attributes
    and specify the desired values.
    Element

    Description

    Number of fare
    points

    Number of fare points that are assigned when using the time profile item

    Number of fare
    Number of fare points that are assigned when alighting at this
    points for alighting time profile item
    Number of fare
    points for boarding

    Number of fare points that are assigned when boarding at this


    time profile item

    Number of fare
    Number of fare points that are assigned when passing through
    points for passing this time profile item
    through

    1330

    PTVGROUP

    15.31.5.5 Coupling multiple time profiles


    Notes: The parameters may also take negative values.
    During assignment all fare points of a time profiles are summed up. In this process, for
    each time profile, Visum checks if the total is greater or equal to zero.
    In the Number of link fare points column you can display the number of fare points resulting at the time profile item from totaling the fare points of all links (see "Links: PuT TSys
    tab" on page 1109).
    You can, for example, also edit the values via the Multi-edit functionality (see "Editing
    attribute values of network objects" on page 983).
    Deleting unused profile points
    You can delete all run time profile points which are not used for the vehicle journeys.
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Delete unused time profile points entry.
    The Multi-edit time profile items window opens.
    Tip: If the network object type Lines has been selected, you can also open the Multiedit time profile items window via the Edit> Delete unused time profile points
    menu.
    3. Make sure that the Special functions tab is selected.
    4. Specify whether you want to delete the unused profile points of all or of all active time profile items.
    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active time profile items will be taken
    into account.

    5. Click the Delete unused profile points button.


    The unused profile points of all or all active time profile items are deleted.
    6. Click the Close button.
    15.31.5.5 Coupling multiple time profiles
    You can couple time profiles of different line routes on jointly served sections of any desired
    length (see Fundamentals: Chpt. 3.1.14.6 , page 77).
    Tip: Alternatively, you can couple vehicle journeys in pairs in the Timetable editor (see
    "Coupling vehicle journeys in pairs" on page 1544).
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).

    PTVGROUP

    1331

    15.31.5.5 Coupling multiple time profiles


    2. In the list, double-click the desired line route.
    The Edit line route window opens.
    3. Select the Items and time profiles tab.
    The tab contains all sections of the selected line route.
    4. If required, edit the display of the attributes via the
    Select attributes for table to the
    right icon (see "The window used for the selection of one attribute" on page 963).
    5. Select the sections to be coupled by marking the desired rows.

    6. Click the

    Couple selection with other time profiles icon.

    The Select time profiles to be coupled window opens. All time profiles (also time profiles
    of other transport systems) for which couplings are possible are displayed.
    7. You can restrict the list of time profiles by selecting one or several of the following options:
    Element

    Description

    Same transport
    system

    If the option is selected, only time profiles with the same transport
    system are suggested.

    Same operator

    If the option has been selected, only time profiles with the same
    operator are suggested.

    Same run and


    dwell times

    If the option has been selected, only time profiles are suggested,
    which have the same run and dwell times.

    Identical vehicle
    journeys in the
    coupling section

    If the option has been selected, only time profiles are suggested
    that possess equivalent vehicle journeys and vehicle journey sections. If you couple the suggested time profiles, no vehicle journeys or vehicle journey sections are inserted or deleted.
    Note
    This option can be selected in addition to other options.

    8. Select one or more time profiles from the list of qualified time profiles.
    9. Confirm with OK.
    If the time profiles do not possess the same number of vehicle journeys, a query opens.
    10. Confirm the query.
    The time profiles are coupled and possibly missing vehicle journeys are generated.

    1332

    PTVGROUP

    15.31.5.6 Deleting couplings of time profiles


    Notes: In the Items and time profiles tab, the Coupled time profiles attribute indicates
    which profiles are coupled. Select theattribute via the
    Select attributes for table to
    the right icon.
    If you want to separate coupled time profiles, select the desired profile points and click
    the

    Remove coupling of selection icon.

    If you change the items of line routes, couplings continue to exist, where possible (see
    "Editing the shape of a line route course" on page 1338).
    You can delete profile points within the couplings by deactivating the related check box.
    15.31.5.6 Deleting couplings of time profiles
    You can delete individual couplings or all couplings of time profiles.
    Deleting individual couplings of time profiles
    1. Open the Coupling sections list (see "Opening a list" on page 2299).
    2. Select the desired couplings.
    3. Right-click in the network display.
    The context menu opens.
    4. Select the Delete entry.
    The selected couplings are deleted.
    Deleting all couplings of time profiles
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Multi-delete> Coupling sections entry.
    A query opens.
    3. Confirm the query.
    All couplings are deleted.
    Note: Only couplings of active time profiles are deleted. If there are couplings on passive
    time profiles, you can delete them one by one in the list of coupling sections.
    15.31.5.7 Multiple display of time profiles
    You can display the attributes of selected time profiles side by side in the list of the profiles and
    compare them immediately. If the selected line route has more than one time profile, a Multiple
    tab is displayed. You can restrict the selection of the time profiles displayed in the Multiple tab
    as follows.
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. In the list, double-click the desired line route.
    PTVGROUP

    1333

    15.31.5.8 Deleting a time profile


    The Edit line route window opens.
    3. Select the Items and time profiles tab.
    The tab contains all profiles of the selected line route.
    4. Click the

    Specify the time profiles to be displayed in the multi-view icon.

    The Select time profiles for multi-view window opens.


    5. Select the time profiles, whose attributes you want to compare.
    6. Confirm with OK.
    In the Multiple tab, each displayed attribute is displayed several times, depending on the number of selected profiles.
    Notes: If you have selected the profiles 1, 2 and 3 for the multiple display, the attributes
    Departure 1, Departure 2 and Departure 3 will be displayed in the Multiple tab.
    The multiple display does not provide all the functions that are provided in the regular display of the individual profiles.
    15.31.5.8 Deleting a time profile
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. In the list, double-click the desired line route.
    The Edit line route window opens.
    3. Select the Items and time profiles tab.
    The tab contains all time profiles of the selected line route.
    4. Click the time profile that you want to delete.

    5. Click the

    Delete current time profile icon.

    A query opens.
    6. Confirm the query.
    The selected time profile is deleted.

    15.31.6 Selecting line routes


    There are several ways to select a line route in order to edit it in another step.
    Marking a line route
    Marking several line routes
    Setting active/passive line routes

    1334

    PTVGROUP

    15.31.6.1 Marking a line route


    15.31.6.1 Marking a line route
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).

    2. If required, restrict the number of line routes which is searched.


    Element

    Description

    Only active ones

    If the option has been selected, only active line routes are displayed.
    If the option has not been selected, all line routes will be taken
    into account.

    3. From the list, select a line route with a left-click.


    Tip: You can also select the sought line route set via the input field. To do this, enter
    the name of the line route in the field. The line route is selected in the list.
    The course of the line route is marked in the network.
    4. If required, click the Autozoom button.
    The network section is enlarged and the marked line route is positioned in the middle of the
    section.
    Tips: Use the Initialize button if you want to remove the previously marked line routes
    from the selection.
    You can also mark the line route courses of a line, if you click on a stop point in the network which is traversed by a line route.
    Alternatively, you can mark a line route by selecting the respective row in the list of line
    routes (see "Selecting list sections" on page 2319).

    PTVGROUP

    1335

    15.31.6.2 Marking several line routes


    15.31.6.2 Marking several line routes
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. Press the CTRL key and keep it pressed.
    3. One by one, click the line routes that you want to mark.
    The selected line routes are marked in the network. The number of the line routes marked in
    the window is displayed in front of the bracket below the list, for example 1(11).
    Tip: You can also mark several line routes, if you mark one or more stop points in the network. Then all line routes will be marked, which traverse these stop points.
    15.31.6.3 Setting active/passive line routes
    Network objects can be active or passive. There are several possibilities to set line routes
    active:
    Via the line filter (see "Using filters to set network objects active or passive" on page 1008)
    By selecting the option for the desired line route in the Line routes window, In selection
    column.
    Note: The spatial selection of network objects of the line hierarchy (lines, line routes, line
    route items, time profiles, time profile items, vehicle journeys, vehicle journey sections) is
    not possible. You can, however, add or remove the network objects of these network
    object types to/from the selection in various different ways.
    With a click in the Spatial selection toolbar on the Include all objects into the spatial
    selection, Invert spatial selection or Remove all objects from the spatial selection
    icons. (see "Setting network objects active/passive via the spatial selection" on page
    1033)
    Edit IsInSelection attribute per network object, for example, in the list of the respective network object. If you enter 1, the respective network object will be active, if you enter 0, it will
    be passive.

    15.31.7 Editing attribute values of line routes


    You can edit the attribute values of one line route, all marked line routes or all (active) line routes.
    15.31.7.1 Editing the attribute values of line routes
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. In the list, double-click the desired line route.
    Tip: Alternatively, you can search for the desired line route (see "Finding network
    objects in the network" on page 999).
    The Edit line route window opens.

    1336

    PTVGROUP

    15.31.7.2 Editing the attribute values of marked line routes


    3. Edit the values of the desired attributes (see "Properties and options of line routes and time
    profiles" on page 1311).
    4. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of line routes in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.31.7.2 Editing the attribute values of marked line routes
    1. Mark the desired line routes whose attribute values you want to edit (see "Marking several
    line routes" on page 1336).
    The selected line routes are marked.
    2. Press the ENTER key.
    The Multi-edit line routes: <Number> objects window opens.
    Tip: You can also call the Multi-edit line routes: <Number> objects window via the
    context menu > entry Edit or double-click the last line route which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of line routes and time
    profiles" on page 1311 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.31.7.3 Editing the attribute values of all or all active line routes
    Note: If there are no passive line routes in the network, all line routes are edited. Markings of line routes are ignored.
    1. If required, set the line routes active, whose attribute values you want to edit, via filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected line routes are active.
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Line routes entry.
    The Multi-edit line routes window opens.
    4. Select whether you want to edit the attribute values of all line routes or just the active ones.

    PTVGROUP

    1337

    15.31.7.4 Displaying the attribute values of a line route in a column chart


    Element

    Description

    Only active ones

    If the option has been selected, only active line routes will be
    taken into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of line routes and time
    profiles" on page 1311 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.31.7.4 Displaying the attribute values of a line route in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.31.8 Editing the shape of a line route course


    You can either edit the shape of individual line routes or the course of several line routes at
    the same time (see "Editing the course of several line routes at the same time" on page 1339).
    Notes: Please take notice of the rules for editing a course (see "Basic rules: Editing a
    route course" on page 1340).
    If you edit the course of a line route, the vehicle journeys and vehicle journey sections of
    the line route are affected (see "Effects on vehicle journeys and vehicle journey sections"
    on page 1344). The vehicle journeys are adjusted in such a way, that they keep their
    departure/arrival at the reference stop point (see "Editing a time profile" on page 1321).
    When editing the shape of a line route, couplings continue to exist, where possible (see
    "Coupling multiple time profiles" on page 1331).
    15.31.8.1 Editing the shape of a line route
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. Select the line routes whose shape you want to edit.
    The line route is marked.
    3. Right-click in the network display.
    A shortcut menu opens.
    4. Select the Edit shape entry.
    The Edit shape of line route window opens.
    5. Specify the parameters for the path search (see "Line routes: specifying parameters for the
    path search" on page 1309).
    6. Modify the previous course.

    1338

    PTVGROUP

    15.31.8.2 Editing the course of several line routes at the same time
    Note: You can fix items first in order to keep them. Then you can modify the course between two fixed items by dragging the desired points to new positions while keeping
    the mouse button pressed (see "Basic rules: Editing a route course" on page 1340).
    7. Confirm with OK.
    Note: If coupled time profiles exist for the modified course, a window opens with further information. Here you can decide which couplings you want to keep (see "Effects
    on coupled time profiles" on page 1346).
    The new course of the line route is saved. Depending on your setting the line routes of coupled time profiles are equally changed.
    Tip: You can also edit the course of individual line routes with the aid of tables (see
    "Tabular editing of a line route course" on page 1347).
    15.31.8.2 Editing the course of several line routes at the same time
    You can edit the course of several line routes at the same time. Each modification then has the
    same effect on the selected line routes which would be affected if the line routes were edited
    separately.
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. Mark the line routes whose shape you want to edit.
    Tips: You can, for example, also mark several line routes, if you mark one or more
    stop points in the network. Then all line routes will be marked, which traverse these
    stop points.
    Alternatively, you can mark several line routes in the Line routes window or one by
    one in the network (see "Marking several line routes" on page 1336).
    The line routes are marked.
    3. Right-click in the network display.
    A context menu opens.
    4. Select the Edit shape entry.
    The Edit shape of line route window opens.
    Note: At the top of the window, the <Number> line routes is displayed, which are marked.
    5. Specify the parameters for the path search (see "Line routes: specifying parameters for the
    path search" on page 1309).

    PTVGROUP

    1339

    15.31.8.3 Basic rules: Editing a route course


    Note: If necessary, click the Autozoom button in the Edit shape of line route window,
    if you want to enlarge the section with the courses of all marked line routes.
    6. Modify the previous courses.
    Note: You can fix items first in order to keep them. Then you can modify the course between two fixed items by dragging the desired points to new positions while keeping
    the mouse button pressed (see "Basic rules: Editing a route course" on page 1340).
    The course of all line routes which traverse the route points is changed.
    7. Confirm with OK.
    Note: If coupled time profiles exist for the modified course, a window opens with further information. Here you can decide whether and which couplings you want to keep
    (see "Effects on coupled time profiles" on page 1346).
    The new course of the line routes is saved.
    15.31.8.3 Basic rules: Editing a route course
    Notes: The following rules apply when editing the course of a line route and when editing
    the course of a system route.
    The rules also apply when editing the course of a path. However, only nodes and zones,
    and no stop points, can be part of the course (see "Editing the shape of a path course" on
    page 1232).
    In the route path, fixed and non-fixed (=free) items are distinguished. When you are in the Edit
    shape mode, you can fix items in the route course.
    Fixed items cannot be shifted. They are taken into account during the shortest path
    search. The route course runs via these stop points or nodes.
    Free items can be shifted, i.e. the route no longer runs via the free item but via the object
    (stop point/node/link) to which the first free item is shifted.
    Start and end stop points are regarded as fixed stop points in the route path as long as
    they are not shifted.
    Note: Free and fixed items are displayed in different colors. You can set the color for the
    display via the Graphics> Edit graphic parameters menu on the Basis page. Free
    items are displayed in the color set for Marking 1, fixed items are displayed in the color
    set for Marking 2 (see "Specifying basic settings for the network window" on page 2337).
    Fixing a node or a stop point
    1. Select the desired line route or system route.
    2. Activate the Edit shape mode with F5.

    1340

    PTVGROUP

    15.31.8.3 Basic rules: Editing a route course


    3. Click on the node or stop of the highlighted route that you want to fix in the network, or
    press the Fix all profile points button to fix all nodes or stops on the desired line route.
    The item is fixed and highlighted in marking color 2.
    Note: You can also revert the fixing by clicking on the item again, or by pressing the
    Undo all fixed settings button.
    Editing a route course or a route section
    You can edit a route course as follows.
    Procedure

    Description

    Editing the entire


    route course

    In this case, you do not have to fix stop points, as the start stop point
    and the end stop point are regarded as fixed.

    Editing a section
    of the course

    Extending a route
    course

    If the respective section is at the beginning or at the end of the


    current route path, you only have to fix one stop point/node. You
    can then edit the section between the start stop point or end stop
    point and the fixed item without changing the remaining section
    of the route course.
    If the respective section is at the center of the route course, that
    is, if a section at the beginning and a section at the end of the current route course shall remain unchanged, you have to fix two
    items which define the beginning and the end of the changeable
    route section (see "Example 2: Rerouting the route path in the
    middle" on page 1342).
    Fix the previous start or end stop point and drag the route course
    from the previous start or end stop point to the desired stop point
    while holding down the mouse button. Then release the mouse button.

    Shortening a route Fix the stop point which shall be the new start or end stop point of the
    course
    route and drag the previous start or end stop point to the fixed stop
    point while holding down the mouse button. Then release mouse button (see "Example 1: Shortening the route path at the start" on page
    1342).
    Visum provides four path search criteria for the route path search from or to fixed stop points/nodes (see "Line routes: specifying parameters for the path search" on page 1309) and,
    based on the specified search criterion, searches the best path from a fixed stop point/node or
    from the start stop point of the route to the next fixed stop point/node or to the end stop point
    and displays the new course of the edited route path.

    PTVGROUP

    1341

    15.31.8.3 Basic rules: Editing a route course


    Note: The following applies to edited courses of system routes:
    The length and the run time are transferred to the new sections according to the current system route attributes.
    The lengths and run times of the other sections remain the same because the route
    path has not changed on these sections.
    Example 1: Shortening the route path at the start
    The route course to be shortened has the original course (stop points or nodes) 1 > 2 > 3 > 8 >
    9 > 4 > 5.
    Procedure 1

    1. Fix the stop point 3 (see "Fixing a node or a stop point" on page 1340).
    2. Drag the start stop point 1 to the stop point 3.

    The fixed stop point 3 is the new start stop point of the course. A shortest path search was not
    carried out.
    Procedure 2

    1. Drag the start stop point 1 to the stop point 3 without fixing an item.

    The new route path is 3 > 4 > 5. A shortest path search is carried out.
    Example 2: Rerouting the route path in the middle
    The route course to be rerouted has the original course (stop point or node) 1 > 2 > 3 > 8 > 9 >
    4 > 5.
    Procedure 1

    1342

    PTVGROUP

    15.31.8.3 Basic rules: Editing a route course

    1. Fix the stop points 2 and 9 (see "Fixing a node or a stop point" on page 1340).
    2. Drag the stop point 8 to the stop point 12.

    The new route path is 1 > 2 > 7 > 12 > 13 > 14 > 9 > 4 > 5.
    Procedure 2

    1. Fix the stop point 2 and the stop point 8 (see "Fixing a node or a stop point" on page 1340).
    2. Drag the stop point 3 to the stop point 7.

    3. Undo the fixing of stop point 7 by clicking the stop point once more.
    Note: Stop point 2 and stop point 8 remain fixed.
    4. Drag the stop point 7 to the stop point 13.

    PTVGROUP

    1343

    15.31.8.3 Basic rules: Editing a route course

    The new route path is 1 > 2 > 7 > 12 > 13 > 8 > 9 > 4 > 5.
    Effects on vehicle journeys and vehicle journey sections
    If you edit the course of a line route, the vehicle journeys and vehicle journey sections of the
    line route are affected.
    If the route path is changed in such a way that the start and the end item of a vehicle journey (or a vehicle journey section) are no longer included in the new route path, the
    vehicle journey (or vehicle journey section) will be deleted.
    If a vehicle journey (or vehicle journey section) has the same start and end item due to the
    application of the rules below, it will be deleted.
    If all vehicle journey sections of a vehicle journey are lost because of the rules below, it
    will be deleted.
    The following applies when editing the beginning of a course:
    Operation

    Description

    Shortening
    If the course is shortened at the start, all affected vehicle journeys
    (a starting section (vehicle journey sections) are shortened accordingly and thus start at
    of the new course the new first item of the course after the modification.
    is completely enclosed in the former
    course)
    Lengthen
    (a starting section
    of the former
    course is completely enclosed in
    the new course)

    Vehicle journeys (vehicle journey sections), which used to start at the


    first item of the course, will also be extended. They will thus again
    start at the first item of the new course. All other vehicle journeys
    (vehicle journey sections) remain unchanged.

    Rerouting
    (all other changes
    within the start section)

    Vehicle journeys (vehicle journey sections), which used to start at the


    first item of the course, will also be rerouted. They will thus again start
    at the first item of the new course. All other vehicle journeys (vehicle
    journey sections) affected are treated as if shortened. They thus start
    at the first remaining item of the former course.

    The following applies when editing the end of a course:


    1344

    PTVGROUP

    15.31.8.3 Basic rules: Editing a route course

    Operation

    Description

    Shortening
    (an end section of
    the new course is
    completely enclosed in the former
    course)

    If the course is shortened at the end, all affected vehicle journeys


    (vehicle journey sections) are shortened accordingly and thus end at
    the new last item of the course after the modification.

    Lengthening
    (an end section of
    the former course
    is completely enclosed in the new
    course)

    Vehicle journeys (vehicle journey sections), which used to start at the


    last item of the course, will also be extended. They will thus again
    end at the last item of the new course. All other vehicle journeys
    (vehicle journey sections) remain unchanged.

    Rerouting
    (all other changes
    within the end section)

    Vehicle journeys (vehicle journey sections), which used to start at the


    last item of the course, will also be rerouted They will thus again end
    at the first item of the new course. All other vehicle journeys (vehicle
    journey sections) affected are treated as if shortened. They thus start
    at the first remaining item of the former course.

    The following applies when editing the middle of a course:


    Note: Due to the first basic rule above, it is irrelevant whether a start and an end item of a
    vehicle journey (vehicle journey section) are included in the altered section of a course.
    If the modified section lies entirely in between the start item and the end item of a vehicle
    journey (vehicle journey section), the vehicle journey (or vehicle journey section) will also
    be rerouted. It depends on the location of the reference point whether its departure time
    needs to be adjusted. Calculated departure and arrival times past the modified section
    are always subject to change.
    If the modified section contains exactly one outer item of a vehicle journey (or a vehicle
    journey section), the procedure is the same as when shortening a vehicle journey. If only
    the start item lies within the modified section, the vehicle journey (or the vehicle journey
    section) will subsequently start at the first item past the modified section. If only the end
    item lies within the altered section, the vehicle journey (or the vehicle journey section) will
    subsequently end at the last item before the modified section.
    Adjusting departure times of vehicle journeys
    When rerouting a line route, the departure times of vehicle journeys may have to be adjusted
    so that their temporal positions are not changed.
    If the time profile has a reference item which is not lost, you should fix the virtual departure/arrival time at the reference item for each vehicle journey and restore it after rerouting
    and set the new time profile times by adjusting the departure time of the vehicle journey.

    PTVGROUP

    1345

    15.31.8.3 Basic rules: Editing a route course


    If the time profile has a reference item which gets lost, proceed as follows: If the start item
    of the vehicle journey changes, fix the departure time at the first remaining item of the
    vehicle journey. If the start item of the vehicle journey does not change, an adjustment is
    not necessary. The departure time at the start item is fixed.
    If the time profile has no reference item, proceed as follows: If the start item of the vehicle
    journey changes, fix the departure time at the first remaining item of the vehicle journey. If
    the start item of the vehicle journey does not change, an adjustment is not necessary. The
    departure time at the start item is fixed.
    Effects on coupled time profiles
    If you modify the course of a line route which contains coupled time profiles, you can keep the
    affected coupling sections in many cases by rerouting the line routes of the coupled time profiles as well.
    1. Edit the shape of a coupled section of a line route.
    2. Confirm with OK.
    The Selection of coupling sections window opens.

    The upper list displays all coupling sections affected by the rerouting. The lower list indicates which line routes are copied when keeping the coupling.
    Note: A line route is copied, if it possesses multiple time profiles of which some are rerouted because the coupling is kept. The previous line route keeps the unchanged
    time profiles which reroute the copied line route.
    3. Make the desired changes.

    1346

    PTVGROUP

    15.31.8.4 Tabular editing of a line route course


    Element

    Description

    Retain coup- Use the check boxes to specify between which stop points you want to
    ling
    keep the coupling.
    If the option has been selected, the coupled time profiles are rerouted as well.
    If the option has not been selected, the coupling is removed and the
    course of the time profiles does not change.
    Note
    You can retain couplings if one of the below conditions applies:
    After rerouting, the start and end point of the coupling section are
    still part of the line route.
    A line route is shortened and at least two time profile items of the
    coupling section are retained.
    Check all

    Use the button to check all checkboxes in the Retain coupling column
    that can be activated.

    Uncheck all Use the button to uncheck all checkboxes in the Retain coupling
    column.
    4. Click the Finish button.
    Note: Use the Cancel button to get back to the Edit shape mode.
    The line route is rerouted. According to your settings, line routes with coupled time profiles are
    also rerouted.
    15.31.8.4 Tabular editing of a line route course
    Note: You can only edit line route courses via tables, if system route courses already
    exist (see "Managing system routes" on page 1368).
    Instead of manually editing line routes or creating line routes, you can extend single line routes via tables (see "Tabular extension of a line route" on page 1348) or reroute them (see
    "Tabular rerouting of line routes" on page 1352). This is done based on system route courses
    that already exist in the network.
    Note: If you create a new line route via tables, the run times of the system route are used
    as run times for the new time profile.
    Total = TStartStop + passage time + TEndStop
    Note: System route courses can in turn be generated from time profiles (see "Managing
    system routes" on page 1368).

    PTVGROUP

    1347

    15.31.8.4 Tabular editing of a line route course


    You can attach system route courses at the start stop point and at the end stop point of a line
    route in order to lengthen it. You can also use system course routes, in order to reroute particular line route sections. In the course of this, please note:
    Since system routes always start and end at stop points, a tabular extension is only possible if the start point and the end point of the line route coincide with stop points. If just
    one of these points is a stop point, only from here you can extend the course via tables.
    If the transport system of the system route differs from the transport system of the line
    route, you might have to open links, turns and stop points to the transport system of the
    line route.
    No route points are generated on the new section of the course (apart from the start stop
    point and the end stop point). The length of the new section is taken from the system
    route.
    If an existing line route is edited, the run times of all time profiles of the line route are adjusted. By default, the system route times are used.
    Tabular extension of a line route
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. Mark the line route that you want to edit.
    3. Right-click in the network display.
    A shortcut menu opens.
    4. Select the Edit shape entry.
    The Edit shape of line route window opens.

    5. Click the Tabular editing button.


    Note: This button is not provided if there are no suited system routes in the network.
    The Tabular editing of line route window opens.

    1348

    PTVGROUP

    15.31.8.4 Tabular editing of a line route course

    For each system route, the columns From SP, To SP, Name, TSys, Vehicle combination
    and Run time are issued.
    Note: The Run time defines the total of TNonStop, TStartStop and TEndStop.
    6. Make the desired changes.
    Element

    Description

    Extend at the start Depending on the selected option, the window contains a list of
    all possible extensions of the line route course at the start or at
    Lengthen at the
    the end. You can extend the course by selecting one of the folend
    lowing options and a system route section in the list:
    Extend at the start
    If the option has been selected, the system route section selected
    in the list is attached at the start of the previous course.
    Lengthen at the end
    If the option has been selected, the system route section selected
    in the list is attached at the end of the previous course.
    Rerouting

    Use this button to reroute the line route (see "Tabular rerouting of
    line routes" on page 1352).

    Show only active


    system routes

    If the option has been selected, only active system routes will be
    listed.

    Propose also
    loops

    If the option is selected, system routes that imply a return to the


    last stop will also be suggested.

    Filters

    You can use the filters to reduce the list of the system route sections.
    Note
    In case of a restriction, the respective label is red afterwards.
    From SP/To SP

    PTVGROUP

    1349

    15.31.8.4 Tabular editing of a line route course


    Element

    Description
    Use this button to open the Find stop point window. You can
    select only one stop point.
    Note
    Depending on the selected Extend at the start/lengthen at the
    end option, the button is labeled From SP or To SP.
    TSys
    Use this button to open the Select transport systems window.
    Select the allowed transport systems.
    Notes
    You can select several transport systems, if you hold down the
    CTRL key.
    If you do not reduce the selection, all transport systems of the line
    will be displayed.
    Vehicle combination
    Use this button to open the Selection: Vehicle combinations window. Select the allowed vehicle combinations.
    Notes
    You can select several vehicle combinations, if you hold down
    the CTRL key.
    If you do not reduce the selection, all vehicle combinations will be
    displayed.

    Undo

    Use this button to und to the last step and remove the last section
    added.

    Autozoom

    Use this button to display the entire route course of the marked
    line route.

    Lengthen

    Use this button to confirm the extended course via the section
    marked in the list.
    Tip
    You can also add a section to the line route by double-clicking
    the respective row.

    Note: Depending on the parameter setting for the path search, associated vehicle journeys will automatically be lengthened if a line route is extended (see "Line routes:
    specifying parameters for the path search" on page 1309). The current setting can be
    taken from a message in the Tabular editing of line route window.
    7. Click the Lengthen button.
    The line route is extended and the system route selection is updated accordingly.

    1350

    PTVGROUP

    15.31.8.4 Tabular editing of a line route course


    Note: You can extend the line route by sections without closing the Tabular editing of
    line route window in the meantime.
    8. Confirm with Close.
    The Edit shape mode is activated anew.
    Note: You can switch between the Edit shape mode and the Tabular editing of line route
    window as often as you like. Complete editing the course by clicking the OK in the Edit
    shape of line route window.
    Example
    The course of the selected line route is marked in the network.

    The dark marking indicates the possible extension, which corresponds with the row selected
    in the Tabular editing of line route window. The light marking indicates the previous course of
    the line route. If the above course is accepted via a double-click the respective row or via the
    Lengthen button (here Tannenstr - Weinbergweg), further potential extensions will be suggested afterwards from the stop point Weinbergweg (= the new From stop point).

    These are again listed in the Tabular editing of line route window.

    PTVGROUP

    1351

    15.31.8.4 Tabular editing of a line route course

    Tabular rerouting of line routes


    If you want to reroute a section of the selected line route, proceed as follows.
    1. In the Tabular editing of line route window, click the Rerouting button.
    The Tabular rerouting window opens.

    2. Specify the section that you want to reroute.


    Element

    Description

    From stop point/To Use the selection lists to select the From stop point and the To
    stop point
    stop point of the section to be rerouted.
    Notes
    All route points with stop points can be selected.
    Since two existing route points of the line route must be selected,
    you can edit neither the start stop nor the end stop. Neither the
    start nor the end can thus be rerouted.
    3. Confirm with OK.
    The Tabular editing of line route window opens.

    1352

    PTVGROUP

    15.31.9 Copying a line route

    The section to be rerouted is highlighted in red in the window. In the network display, the
    suggested course of the line route selected in the window is displayed in the color specified
    for Marking 2.

    4. In the drop-down list, select the desired section.


    5. Click the Add button.
    The suggested route is saved and the line route is rerouted.
    6. Reroute further sections, if required.
    Note: The rerouting is completed automatically when the selected To stop point is reached.
    7. Confirm your changes by clicking the Close button.

    15.31.9 Copying a line route


    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. From the list of line routes, select the one you want to copy.
    3. Right-click in the network display.
    PTVGROUP

    1353

    15.31.9 Copying a line route


    A shortcut menu opens.
    4. Select the Copy line route entry.
    The Copy line route window opens.

    5. Make the desired changes.

    1354

    Element

    Description

    Line

    Use the drop-down list to select the line to which the line route
    shall be allocated.

    Name

    In the input field, enter a name for the new line route.
    Note
    By default, the name of the copied line route is displayed.
    The name of the new line route must not exist in the network for
    the same direction. If you select the opposite direction, you can
    name the line route exactly like the other direction.

    Direction

    Use the drop-down list to select a direction for the new line route.

    Copy also all


    vehicle journeys

    If the option has been selected, all vehicle journeys and journey
    sections are copied with the line route.

    PTVGROUP

    15.31.10 Connecting a line route


    Element

    Description

    Also copy walk


    and wait times at
    stops

    If the option has been selected, all wait and walk times at stops
    are copied together with the line route.

    Restrict course

    The line route can be shortened by selecting a From stop point or


    a To stop point.
    From stop point
    Use the drop-down list to select a From stop point for the new line
    route.
    To stop point
    Use the drop-down list to select a To stop point for the new line
    route.
    Suggest route points only
    If the option has been selected, you can only select route points
    with a stop point.

    6. Confirm with OK.


    The line route is copied including all its attributes. The new line route is listed in the Line routes window.

    15.31.10 Connecting a line route


    Note: Existing assignment results are deleted when connecting line routes.
    With this functionality, you can generate a new line route from two adjoining line routes. The
    line routes to be connected need to meet the following requirements:
    Both have the same transport system.
    The start stop point of one of the line routes is the end stop point of the other one.
    None of the time profiles of the line routes are coupled.
    Notes: You cannot connect a line route, if it contains more than one time profile and no
    time profiles with identical names exist on other line routes.
    If the stop point at which two line routes shall be connected is an undirected link stop
    point (see "Creating a stop point" on page 1266), the outgoing line route must point in the
    opposite direction of the incoming one, since the line route cannot turn on a link stop
    point.
    Note: Line routes of the same line, like the opposing directions of a line route, can also
    be connected.
    If you want to connect line routes, proceed as follows.
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. From the list of line routes, select the one you want to connect to another line route.
    PTVGROUP

    1355

    15.31.10 Connecting a line route


    3. Right-click in the network display.
    A context menu opens.
    4. Select the Connect line route entry.
    The Connect line route <Name> window opens.

    5. Make the desired changes.


    Element

    Description

    Line route to be
    connected

    In this section, you can specify whether the selected line route
    shall be extended at the start or at the end.
    Lengthen at the end by
    If the option has been selected, you can pick the line route which
    you want to use for the extension at the end.
    Lengthen at the beginning by
    If the option has been selected, you can pick the line route which
    you want to use for the extension at the start.

    Combination type

    Edit line routes


    If the option has been selected, the line, the direction, and the
    name of the selected line route will be used. The newly created
    line route is then a combination of the two line routes. The line
    route selected at the top of the window will be deleted.
    Create new line route
    If the option has been selected, the combination parameters are
    enabled.

    Combination para- Line of the new line route


    meters
    Use the drop-down list to select a line to which the new line route
    shall be allocated.
    Name of the new line route

    1356

    PTVGROUP

    15.31.11 Creating the opposite direction of a line route


    Element

    Description
    Enter the name of the new line route
    Direction of the new line route
    Use the drop-down list to allocate a direction to the new line
    route.
    Discard combined line routes
    If the option has been selected, the two original line routes will
    be deleted.
    If the option has not been selected, the new line route will be
    created in addition to the two combined line routes.
    Copy also vehicle journeys
    If the option has been selected, all vehicle journeys will be
    copied.
    Notes
    The copied vehicle journeys keep their original course and are
    thus not even lengthened if they start or end at the connecting
    stop point.
    User-defined attributes and AddValues are copied from the selected line route.

    6. Confirm with OK.


    The line routes are connected.

    15.31.11 Creating the opposite direction of a line route


    With this functionality you can create the opposite direction of a line route. It is generated as a
    new line route with the corresponding course and identical attributes.
    Note: If you enter a new name for the line route and allocate the direction of the selected
    line route to it, a copy of the line route originates.
    1. Open the Lines routes window (see "Opening the Line routes window" on page 1306).
    2. From the list, select the line route for which you want to create an opposite direction.
    3. Right-click in the network display.
    A context menu opens.
    4. Select the Create opposite direction entry.
    The Create opposite direction window opens.

    PTVGROUP

    1357

    15.31.12 Line routes: Opening the Timetable editor

    5. Make the desired changes.


    Element

    Description

    Line

    Display of the line to which the line route is allocated

    Name

    In the input field, enter a name for the new line route.
    Note
    If you select the opposite direction, you can name the line route
    exactly like the other direction.

    Direction

    Select the opposite direction of the selected line.

    Transport system Display of the transport system of the selected line route
    Copy also all
    vehicle journeys

    If the option has been selected, all vehicle journeys and journey
    sections are copied with the line route.

    6. Confirm with OK.


    The line route in the opposite direction is inserted. For each time profile of the selected line
    route, a time profile in the opposite direction is created.
    Note: If the original line route starts or ends at a directed link stop point (see "Managing
    stop points" on page 1266), the stop point will also be inserted for the opposite direction
    when confirming a query. If there are further link stop points in the course, you can also
    transfer them to the opposite direction.

    15.31.12 Line routes: Opening the Timetable editor


    You can select line routes in the Network editor and display them in the Timetable editor (see
    "Using the Timetable editor" on page 1526).
    Calling the timetable editor with selected line routes
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. Press the CTRL key and keep it pressed.
    3. One by one, click the line routes that you want to mark.
    4. Click the Timetable editor button.
    Notes: If the Timetable editor is already open, a query opens (see "Opening the Timetable editor" on page 1526).
    Alternatively, you can click the Timetable editor entry in the context-menu of the list.
    1358

    PTVGROUP

    15.31.12 Line routes: Opening the Timetable editor


    The Timetable editor opens. The selected line routes are displayed.
    Calling the Timetable editor by a search for a vehicle journey
    1. Open the Line routes window. (see "Opening the Line routes window" on page 1306)
    2. Press the hotkey SHIFT + F3.
    3. The Find a network object window opens.
    Tip: Alternatively, you can click the Find vehicle journey entry in the context-menu of
    the Lines button.
    4. In the list box, select the attribute you want to find.
    Note: The search by Name is only possible if a name has been entered for at least
    one vehicle journey.
    5. In the input field, enter the value or text you want to find.
    As you type, the list automatically displays and marks the first attribute value that corresponds to the entered value or text.
    Note: If you click a vehicle journey in the list, the corresponding line will be marked in
    the network.
    6. If you want to enlarge the network section, click Autozoom.
    The network section is enlarged and the line is positioned in the middle of the section.
    7. In the list, double-click the desired search result.
    8. The Edit line route window opens.
    9. Click the desired button.
    Element

    Description

    Timetable editor

    The button opens the timetable editor. All lines are displayed that
    contain a vehicle journey with the selected attribute. All vehicle
    journeys that have the selected attribute value are marked.

    Edit line route

    The button opens the window to edit line routes and time profiles
    (see "Properties and options of line routes and time profiles" on
    page 1311).

    The Timetable editor opens. All lines are displayed that contain a vehicle journey with the
    selected attribute. All vehicle journeys that have the selected attribute value are marked.

    PTVGROUP

    1359

    15.31.13 Aggregating line routes


    Calling the timetable editor from the Edit line route window
    1. Make sure that the Items and time profiles tab is selected in the Edit line route window
    (see "Managing time profiles" on page 1316).
    2. If required, select one or several time profiles.
    3. Click the Timetable editor button.
    The window closes and all changes are saved. The Timetable editor opens. The Lines tab displays exactly the line route that was open in the Edit line route window. The selected time profiles are displayed. If a reference journey has been selected, it is marked.

    15.31.13 Aggregating line routes


    With this functionality you can aggregate line routes and/or time profiles of one or several
    lines. Line routes and/or time profiles can be aggregated within one line or over several lines
    (see "Aggregating lines" on page 1300).

    15.31.14 Specifying the lengths of line routes


    With this functionality, you can generate the length of line routes based on the link attribute
    Length.
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Set lengths for line routes entry.
    The Multi-edit line routes window opens.
    Tip: If the network object type lines has been selected, you can also open the Multiedit line routes window via the Edit> Set lengths for line routes menu.
    3. Make sure that the Special functions tab is selected.
    4. Specify whether you want to set the lengths of all or all active line routes.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active line routes will be taken
    into account.

    5. Click the Set lengths button.


    The route section lengths of all or all active line routes are generated from the link attribute
    Length.
    6. Click the Close button.

    15.31.15 Specifying the direction of the line route


    With this functionality you can allocate a direction to all or all active line routes.
    1. In the Network window, right-click the Lines button.
    1360

    PTVGROUP

    15.31.16 Generating profile points for line route items


    The Lines context menu opens.
    2. Select the Multi-edit> Line routes entry.
    The Multi-edit line routes window opens.
    Tip: If the network object type lines has been selected, you can also open the Multiedit line routes window via the Edit> Set direction for line routes menu.
    3. Make sure that the Special functions tab is selected.
    4. Select whether you want to allocate a direction to all line routes or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active line routes will be
    taken into account.

    5. Click the Set direction button.


    The Set direction window opens.
    6. Make the desired changes.
    Element

    Description

    Set direction to

    If the option has been selected, you can allocate both directions
    via the drop-down list.

    Invert direction

    If the option has been selected, the opposite direction of the current direction will be allocated to the line routes.

    7. Confirm with OK.


    The desired direction is allocated to all or all active line routes.
    8. Click the Close button.

    15.31.16 Generating profile points for line route items


    With this functionality you can generate profile points on existing route points.
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Generate profile points for line route items entry.
    The Multi-edit line route items window opens.
    Tip: If the network object type lines has been selected, you can also open the Multiedit line route items window via the Edit> Generate profile points for line route
    items menu.

    PTVGROUP

    1361

    15.31.17 Deleting line routes


    3. Make sure that the Special functions tab is selected.
    4. Specify whether you want to generate profile points for all or all active line route items.
    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active line route items will be taken
    into account.

    5. Click the Create profile points button.


    For existing route points, time profile items are created and the run times of the time profiles
    are adjusted.
    6. Click the Close button.

    15.31.17 Deleting line routes


    There are several ways to delete line routes.
    Notes: If you delete a line route, all associated time profiles and vehicle journeys will also
    be deleted.
    If you delete line routes, existing public transport assignment results will be reset.
    15.31.17.1 Deleting a line route
    1. Open the Line routes window (see "Opening the Line routes window" on page 1306).
    2. Select the line route that you want to delete.
    3. Press the ENTER key.
    The Delete line routes window opens.
    4. Confirm with Yes.
    The line route is deleted.
    Tip: You can also delete the marked line route via the context menu> entry Delete.
    15.31.17.2 Deleting several marked line routes
    1. Mark the line routes that you want to delete (see "Marking several line routes" on page
    1336).
    The selected line routes are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked line routes via the context menu> entry Delete.

    1362

    PTVGROUP

    15.31.17.3 Deleting active line routes


    3. Confirm with OK.
    The Delete line routes window opens.
    4. Select which line routes you want to delete.
    Element

    Description

    Yes

    The line route listed in the window will be deleted and also the network
    objects with a reference to the line route.

    Yes for all All remaining marked line routes will be deleted, and also the network
    objects with a reference to the line route.
    No

    Neither the line route listed in the window will be deleted nor the network
    objects with a reference to the line route.

    No for all

    Neither of the remaining marked line routes will be deleted, nor the network objects with a reference to the line route.

    Notes: If you click the Yes or No buttons, the query is displayed for the next line route
    number.
    With the Yes for all or No for all buttons, you only regard the remaining line routes,
    for which neither Yes nor No has been clicked.
    The confirmed line routes are deleted.
    15.31.17.3 Deleting active line routes
    1. Select the line route that you want to delete. To do this, use filter criteria (see "Using filters
    to set network objects active or passive" on page 1008).
    The selected line routes are active.
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-delete> Line routes entry.
    A query opens.
    Tip: If the network type Lines has been selected, you can also delete all active lines
    via the Edit> Multi-delete > Line routes menu or by pressing the D EL key.
    4. Confirm with OK.
    The Delete line routes window opens.
    5. Select which line routes you want to delete.

    PTVGROUP

    1363

    15.32 Managing main lines


    Element

    Description

    Yes

    The line route listed in the window will be deleted and also the network
    objects with a reference to the line route.

    Yes for all

    All remaining active line routes will be deleted, and also the network
    objects with a reference to the line route.

    No

    Neither the line route listed in the window will be deleted nor the network
    objects with a reference to the line route.

    No for all

    Neither of the remaining active line routes will be deleted, nor the network objects with a reference to the line route.

    Notes: If you click the Yes or No buttons, the query is displayed for the next line route
    number.
    With the Yes for all or No for all buttons, you only regard the remaining line routes,
    for which neither Yes nor No has been clicked.
    The confirmed line routes are deleted.

    15.32

    Managing main lines


    Several lines can be combined in one main line and then be evaluated together.

    15.32.1 Creating a main line


    1. In the Network menu, select the PuT main lines entry.
    The PuT main lines window opens.
    2. Click the

    Create button.

    The Create main line window opens.


    3. Enter the desired data (see "Properties and options of main lines" on page 1365).
    4. Confirm with OK.
    The main line is inserted.

    1364

    PTVGROUP

    15.32.2 Properties and options of main lines

    15.32.2 Properties and options of main lines

    The upper section of the Create main line or Edit main line window contains the general attributes of main lines. In the lower section you can allocate lines to main lines or remove them
    from the allocation.
    Element

    Description

    Name

    Name of the main line

    Comment

    Enter an arbitrary text

    Lines

    In this section, you can allocate lines to main lines. Click the buttons
    or
    (see "Allocating a line to a main line" on page 1365 and "Removing a
    line from a main line allocation" on page 1366).
    Note
    A line can be assigned to only one main line.
    Tip
    You can also change the allocation of lines to main lines in the MainLineName column of the Lines list (see "Working with lists" on page 2299).

    Only active
    ones

    If the option has been selected, only active lines will be listed under Not
    allocated.

    Allocating a line to a main line


    1. Make sure that the Edit main line window is open.
    2. From the Not allocated list, select the desired line.
    3. Click the

    button.

    The line is added to the Allocated list and thus to the main line.
    4. Add further lines to the main line, if required.
    5. Confirm with OK.

    PTVGROUP

    1365

    15.32.3 Setting active/passive main lines


    Removing a line from a main line allocation
    1. Make sure that the Edit main line window is open.
    2. From the Allocated list, select the desired line.
    3. Click the

    button.

    The line is removed from the Allocated list and thus from the allocation.
    4. Remove further lines, if required.
    5. Confirm with OK.

    15.32.3 Setting active/passive main lines


    You cannot set active/passive main lines via filter criteria or the spatial selection. You can,
    however, set active/passive main lines as follows:
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Multi-edit> Main lines entry.
    The Multi-edit main lines window opens.
    3. Select the IsInselection attribute.
    4. Click the Constant button.
    The Attribute: Constant value window opens.
    5. Select No.
    6. Confirm with OK.
    The main lines are set passive.
    Tips: If you select Yes, the main lines are active.
    You can also edit the IsInSelection attribute in the Main lines list. If you enter 1 , the
    respective main line will be active, if you enter 0, it will be passive.

    15.32.4 Editing the attribute values of main lines


    You can edit the attribute values of one main line or of all (active) main lines.
    15.32.4.1 Editing the attribute values of a main line
    1. In the Network menu, select the PuT main lines entry.
    The PuT main lines window opens.
    2. In the list, click the desired main line.
    3. Click the

    Edit button.

    The Edit main line <Name> window opens.

    1366

    PTVGROUP

    15.32.4.2 Editing the attribute values of all or all active main lines
    4. Make the desired settings (see "Properties and options of main lines" on page 1365).
    5. Confirm with OK.
    The attribute values are edited.
    15.32.4.2 Editing the attribute values of all or all active main lines
    1. If required, set the desired main lines active (see "Setting active/passive main lines" on
    page 1366).
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Main lines entry.
    The Multi-edit main lines window opens.
    4. Select whether you want to edit the attribute values of all main lines or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active main lines will be
    taken into account.

    5. Edit the values of the desired attributes (see "Properties and options of main lines" on page
    1365 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    6. Click the Close button.

    15.32.5 Deleting main lines


    There are several ways to delete main lines.
    15.32.5.1 Deleting a main line
    1. In the Network menu, select the PuT main lines entry.
    The PuT main lines window opens.
    2. Select the desired main line.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the

    Delete button.

    4. Confirm with OK.


    The main line is deleted.

    PTVGROUP

    1367

    15.32.5.2 Deleting all or all active main lines


    15.32.5.2 Deleting all or all active main lines
    1. If required, set the desired main lines active (see "Setting active/passive main lines" on
    page 1366).
    2. Make sure that in the View menu, the Network is selected.
    3. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    4. Select the Multi-edit> Main lines entry.
    A query opens if the network contains passive main lines. Otherwise all main lines are deleted.
    5. Confirm with OK.
    The main lines are deleted.

    15.33

    Managing system routes


    A system route describes the run time and the course between two stop points (see Fundamentals: Chpt. 3.1.15 , page 80). In contrast to a line route, it is not allocated to a line or to a
    specific vehicle journey. With their path and run time information, system routes serve as templates for efficient editing of the courses of line routes and for setting run times of the time profile.

    15.33.1 Creating a system route


    Note: Please take notice of the rules for editing a course (see "Basic rules: Editing a route
    course" on page 1340).
    1. In the Network window, click the

    Insert mode icon.

    2. Click the System routes button.


    3. Click in the network display.
    The Create system route window opens.

    4. Enter the desired data.


    Element

    Description

    Name

    Enter a name for the system route

    Transport system Select a transport system for the system route


    5. Confirm with OK.
    1368

    PTVGROUP

    15.33.1 Creating a system route


    The Edit shape of system route window opens.

    6. Click the stop point where you want the system route to start and hold down the mouse button.
    Note: A system route must start and end at a stop point.
    7. Drag the mouse to the next stop point or node, via which the system route shall run and
    release the mouse button.
    The system route is highlighted.
    Note: If required, click the Autozoom button in the Edit shape of system route window, if you want to enlarge the section with the course.
    8. If required, proceed in the same manner to create any other sections you wish to create.
    Notes: If required, click the Undo button in the Edit shape of system route window, if
    you want to delete the last section of the system route course.
    If a stop point or a node is traversed more than once, theEdit shape of system route
    window opens. In the window, select the passage that you want to traverse.
    9. Drag the mouse button to the desired end stop point of the system route and release the
    mouse button.
    Tip: You can also drag the mouse directly from the first stop point to the desired end
    stop point. The program will then suggest the best path based on the set search criterion (see "Line routes: specifying parameters for the path search" on page 1309).
    10. Click the OK button in the Edit shape of system route window.
    The system route is inserted.
    Notes: You can create the opposite direction of the system route via the context menu
    (see "Creating the opposite direction of a system route" on page 1377).
    You can edit the course of a system route later (see "Editing the course of a system route"
    on page 1375).

    PTVGROUP

    1369

    15.33.1 Creating a system route


    System routes: Specifying parameters for the path search
    1. Click the Parameters button in the Edit shape of system route window.
    The Parameters: System route course search window opens.

    2. Make the desired changes.


    Element

    Description

    Use also closed


    links for routing

    If the option has been selected, the links closed to the transport
    system will be taken into account, as if they were open to the
    transport system.

    Use also closed


    turns for routing

    If the option has been selected, the turns closed to the transport
    system will be taken into account, as if they were open to the
    transport system.

    Search criterion

    From the drop-down list, you can select a criterion for the path
    search. The search finds the best path each between two marked
    (fixed) stop points.
    Link length (direct distance)
    Direct distance link length from the origin to the destination stop
    point
    Link run time
    Is calculated from the transport system speed of the links
    Time from speed def. by link type
    Is calculated from the transport system speed specified for the
    respective link type
    Link length
    Calculated link length if not manually adjusted by the user

    3. Confirm with OK.

    1370

    PTVGROUP

    15.33.2 Properties and options of system routes

    15.33.2 Properties and options of system routes

    The upper section of the Edit system route window contains the general attributes of the system route. In the lower section, you can edit specific attributes in various tabs.
    15.33.2.1 System routes: General attributes
    Element

    Description

    Name

    Name of the system route

    15.33.2.2 System routes: Basis tab


    Note: If you do not enter a unit, the entry is interpreted as minutes.
    Element

    Description

    Transport system

    Display of the transport system of the selected system route

    Start stop point

    Display of the name of the start stop point It consists of the number
    and the code of the start stop point or the number and the name of
    the start stop point, if no code exists.

    End stop point

    Display of the name of the end stop point of the line route. It consists of the number and the code of the end stop point or the number and the name of the end stop point, if no code exists.

    Link run time

    Display of the transport system run time of the system route, determined from the length and the speed per transport system

    Link length

    Display of the total length of the traversed links

    Passage time

    User-defined run time of the system route

    TStartStop/TEndStop

    Enter a time penalty for each starting and stopping procedure

    Length

    Enter a system route length for the transport system

    PTVGROUP

    1371

    15.33.2.3 System routes: Vehicle combinations tab


    15.33.2.3 System routes: Vehicle combinations tab
    You can overwrite the time attributes of the system route for each vehicle combination of the
    transport system and use them for time profiles of line routes with this vehicle combination.
    Note: If you want to use system route times for line routes, select the From system routes option in the Edit line route> window, Items and profiles tab >, Set new times for
    current time profile icon (see "Setting the times for a time profile" on page 1322).
    Element

    Description

    Create

    Use this button to create a new run time. In a separate window, enter
    the desired data (see "Properties and options of system routes" on
    page 1371) and confirm with OK.
    Note
    For each system route, you can create just one non-stop run time per
    vehicle combination.

    Delete

    Removes the selected row from the window

    Delete all

    Deletes all run times of the system route

    15.33.3 Selecting system routes


    There are several ways to select a system route in order to edit it in another step:
    Marking a system route
    Marking several system routes
    Setting system routes active or passive
    15.33.3.1 Marking a system route
    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.

    3. If required, restrict the number of system routes which is searched.


    1372

    PTVGROUP

    15.33.3.2 Marking several system routes

    Element

    Description

    Only active ones

    If the option has been selected, only active time profiles will be
    displayed.

    4. From the list, select a system route.


    Tip: You can also select the sought system route set via the input field. To do this,
    enter the name of the system route in the field. The system route is selected in the list.
    The course of the system route is marked in the network.
    5. If required, click the Autozoom button.
    The network section is enlarged and the marked system route is positioned in the middle of
    the section.
    Tips: Use the Initialize button if you want to remove the previously marked system routes
    from the selection.
    You can also mark system route items by clicking a stop point in the network which is traversed by a system route.
    Alternatively, you can mark a system route by selecting the respective row in the list of
    system routes (see "Selecting list sections" on page 2319).
    15.33.3.2 Marking several system routes
    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.
    3. Press the CTRL key and keep it pressed.
    4. One by one, click the system routes that you want to mark.
    The selected system routes are marked in the network. The number of the system routes marked in the window is displayed in front of the bracket below the list, for example 1(11).
    15.33.3.3 Setting system routes active or passive
    Network objects can be active or passive. There are several possibilities to set system routes
    active.
    Via the system routes filter (see "Using filters to set network objects active or passive" on
    page 1008)
    Note: The spatial selection of system routes is not possible. You can, however, add or
    remove system routes to/from the selection in various different ways.

    PTVGROUP

    1373

    15.33.4 Editing the attribute values of system routes


    With a click in the Spatial selection toolbar on the icons Include all objects into the spatial selection, Invert spatial selection or Remove all objects from the spatial selection
    (see "Setting network objects active/passive via the spatial selection" on page 1033)
    Edit IsInSelection attribute per network object, for example, in the list of the respective network object. If you enter 1, the respective network object will be active, if you enter 0, it will
    be passive.

    15.33.4 Editing the attribute values of system routes


    You can edit the attribute values of one system route, all marked system routes or all (active)
    system routes.
    15.33.4.1 Editing the attribute values of a system route
    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.
    3. In the list, double-click the desired system route.
    The Edit system route window opens.
    4. Edit the values of the desired attributes (see "Properties and options of system routes" on
    page 1371).
    5. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of system routes in the Quick
    view window or in the list of the network object type (see "Quick view window" on page
    810 and "Working with lists" on page 2299).
    15.33.4.2 Editing the attribute values of marked system routes
    1. Mark the system routes whose attribute values you want to edit (see "Marking several system routes" on page 1373).
    The selected system routes are marked.
    2. Press the ENTER key.
    The Multi-edit system routes: <Number> objects window opens.
    Tip: You can also call the Multi-edit system routes: <Number> objects window via
    the context menu > entry Edit or double-click the last line which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of system routes" on
    page 1371 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.

    1374

    PTVGROUP

    15.33.4.3 Editing the attribute values of all or all active system routes
    4. Click the Close button.
    15.33.4.3 Editing the attribute values of all or all active system routes
    Note: If there are no passive system routes in the network, all system routes are changed.
    Markings of system routes are ignored.
    1. If required, set the system routes active, whose attribute values you want to edit, via filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected system routes are active.
    2. In the Network window, right-click the System routes button.
    The System routes context menu opens.
    3. Select the Multi-edit> System routes entry.
    The Multi-edit system routes window opens.
    4. Select whether you want to edit the attribute values of all system routes or just the active
    ones.
    Element

    Description

    Only
    active
    ones

    If the option has been selected, only active system routes will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of system routes" on
    page 1371 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.33.4.4 Displaying the attribute values of a system route in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.33.5 Editing the course of a system route


    Note: Please take notice of the rules for editing a course (see "Basic rules: Editing a route
    course" on page 1340).
    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.
    3. Select the system route whose course you want to edit.

    PTVGROUP

    1375

    15.33.6 Copying a system route


    The system route is marked.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Edit shape entry.
    The Edit shape of system route window opens.
    6. Specify the parameters for the path search (see "System routes: Specifying parameters for
    the path search" on page 1370).
    7. Edit the previous course by dragging the desired points of the course to new positions.
    8. Confirm with OK.
    The new course of the system route is saved.
    Note: The following applies to edited courses of system routes:
    The length and the run time are transferred to the new sections according to the current system route attributes.
    The lengths and run times of the other sections remain the same because the route
    path has not changed on these sections.

    15.33.6 Copying a system route


    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.
    3. From the list of system routes, select the one you want to copy.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Copy system route entry.
    The Copy system route window opens.

    6. Make the desired changes.

    1376

    PTVGROUP

    15.33.7 Creating the opposite direction of a system route


    Element

    Description

    Name

    In the input field, enter a name for the new system route.
    Note
    The name of the new system route must not exist in the network
    for the same direction.

    Transport system Use the drop-down list to select a transport system.


    7. Confirm with OK.
    The system route is copied including all its attributes. The new system route is listed in the System routes window.

    15.33.7 Creating the opposite direction of a system route


    With this functionality you can create the opposite direction of a system route. It is generated
    as a new system route with the corresponding course and identical attributes.
    Tip: If you enter a new name for the system route and allocate the direction of the selected system route to it, a copy of the system route originates.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.
    3. In the list, click the system route for which you want to create the opposite direction.
    4. Right-click in the network display.
    A context menu opens.
    5. Select the Create opposite direction entry.
    The Create opposite direction window opens.

    6. In the input field, enter a name for the new system route.
    7. Confirm with OK.
    The system route in the opposite direction is inserted.
    Note: If the original system route starts or ends at a directed link stop point (see "Managing stop points" on page 1266), the stop point will also be inserted for the opposite direction when confirming a query. If there are further link stop points in the course, you can
    also apply them in the opposite direction.

    PTVGROUP

    1377

    15.33.8 Creating system routes

    15.33.8 Creating system routes


    You can create system routes automatically from available time profiles (see "Creating system
    routes from time profiles " on page 1378) or for pairs of stop points (see "Creating system routes for pairs of stop points" on page 1380).
    15.33.8.1 Creating system routes from time profiles
    You can create system routes automatically from existing time profiles. The course and run
    times of the time profiles will be used.
    Notes: System routes are created per stop-stop section, i.e. in between any consecutive
    stop points.
    Since time profiles always start and end at stop points, the complete course of a time profile is turned into system routes.
    System routes are created broken down by transport system and items. This means that,
    should there be any time profiles with identical attributes except for the transport system,
    several system routes will be created from them.
    If there are any time profiles with different items between two stop points within a transport system, several system routes will be created, too.
    1. In the Network window, right-click the System routes button.
    The System routes context menu opens.
    2. Select the Create from time profiles entry.
    The Create system routes from time profileswindow opens.

    3. Make the desired changes.

    1378

    PTVGROUP

    15.33.8.1 Creating system routes from time profiles


    Element

    Description

    Naming

    The following components of names of the system route to be


    generated can be selected and edited:
    Prefix
    Enter an arbitrary text
    Transport system
    Select a transport system attribute
    Start stop point
    Select a stop point attribute
    End stop point
    Select a stop point attribute
    Notes
    The following naming rules are effective if there is no system
    route within the network yet with an identical transport system and
    course:
    A generated system route could, for example, result in the following name, if all four elements are selected: Sys_T_20_40.
    In order to avoid that identical names are assigned to different system routes that are generated at the same time, a
    number is attached to the end of the name in case a combination already exists. The numbering begins with 1, for
    example Sys_B_20_40_1.
    Existing system routes can be overridden or updated when given
    a new name:
    A system route with an identical transport system and course
    will be overridden, if its name is identical to the components
    listed above. If the system route data of a network is supposed to be updated only, the same parameters as for the
    existing system routes thus need to be entered in the window.
    If you want to prevent that existing system routes are overwritten, you need to specify a new combination of name components. No existing system routes will then be found in the
    network. All objects are then created anew, in addition to the
    existing system routes.

    Determination of
    the system route
    run time

    Select one of the following options for the run times of the system
    routes:
    Minimum
    If the option has been selected, the minimum run time will be
    determined.
    Maximum

    PTVGROUP

    1379

    15.33.8.2 Creating system routes for pairs of stop points


    Element

    Description
    If the option has been selected, the maximum run time will be
    determined.
    Average
    If the option has been selected, the mean run time will be determined.

    Determination of
    system route
    length

    Select one of the following options for the lengths of the system
    routes:
    Minimum
    If the option has been selected, the minimum length will be determined.
    Maximum
    If the option has been selected, the maximum length will be determined.
    Average
    If the option has been selected, the mean length will be determined.

    Use only active


    time profiles

    If the option has been selected, system routes will only be generated from active time profiles.

    Note: For several time profiles with an identical transport system and an identical
    course, the resulting attributes of the system route emerge as follows:
    The Transport system is used, as it is identical for all time profiles.
    The course (specifically start stop point and end stop point) is used, as it is identical for all time profiles.
    The Name is generated according to the naming settings.
    The Length is an aggregate of the lengths of the stop sections (of the line routes
    of all time profiles).
    The Passage time in the Basis tab is an aggregate of the run times of the stop
    sections (of all time profiles).
    The Passage time in the Vehicle combination tab is an aggregate of the run
    times of the stop sections (of all time profiles of this vehicle combination).
    The TStartStop, TEndStop is always set to zero.
    User-defined attributes are not adopted.
    4. Confirm with OK.
    The system routes are generated.
    15.33.8.2 Creating system routes for pairs of stop points
    You can create system routes for pairs of stop points which are not connected to a system
    route.

    1380

    PTVGROUP

    15.33.8.2 Creating system routes for pairs of stop points


    1. In the Network window, right-click the System routes button.
    The System routes context menu opens.
    2. Select the Create for stop point pairs entry.
    The Create system routes for pairs of stop points window opens.

    3. Make the desired changes.

    PTVGROUP

    1381

    15.33.8.2 Creating system routes for pairs of stop points


    Element

    Description

    Naming

    The following components of names of the system route to be


    generated can be selected and edited:
    Prefix
    Enter an arbitrary text
    Transport system
    Select a transport system attribute
    Start stop point
    Select a stop point attribute
    End stop point
    Select a stop point attribute
    Notes
    The following naming rules are effective if there is no system
    route within the network yet with an identical transport system and
    course:
    A generated system route could, for example, result in the following name, if all four elements are selected: Sys_T_20_40.
    In order to avoid that identical names are assigned to different system routes that are generated at the same time, a
    number is attached to the end of the name in case a combination already exists. The numbering begins with 1, for
    example Sys_B_20_40_1.
    Existing system routes can be overridden or updated when given
    a new name:
    A system route with an identical transport system and course
    will be overridden, if its name is identical to the components
    listed above. If the system route data of a network is supposed to be updated only, the same parameters as for the
    existing system routes thus need to be entered in the window.
    If you want to prevent that existing system routes are overwritten, you need to specify a new combination of name components. No existing system routes will then be found in the
    network. All objects are then created anew, in addition to the
    existing system routes.

    Distance criterion Selection of a link attribute as distance criterion


    (link attribute)
    Note
    The system routes are determined via shortest path searches
    which are carried out based on the distance criterion and the
    transport system indicated.
    Select one of the following attributes:

    1382

    PTVGROUP

    15.33.9 Deleting system routes


    Element

    Description
    Length, t-PuTSys, AddValue1, AddValue2, AddValue3 and
    AddVal_TSys.

    Transport system Selection of a stop point attribute


    Note
    The system routes are determined via shortest path searches
    which are carried out based on the distance criterion and the
    transport system indicated.
    Use only active
    stop points

    If the option has been selected, system routes will only be created
    between active stop points.

    4. Confirm with OK.


    System routes are created for all or all active pairs of stop points which are not yet connected
    by an active system route.

    15.33.9 Deleting system routes


    There are several ways to delete system routes.
    15.33.9.1 Deleting a system route
    1. In the Network window, click the

    Edit mode icon.

    2. Click the System routes button.


    The System routes window opens.
    3. From the list of system routes, select the one you want to delete.
    4. Press the DEL key.
    The system route is deleted.
    Tip: You can also delete the selected System route via the context menu> entry Delete.
    15.33.9.2 Deleting several system routes
    1. Mark the system routes that you want to delete (see "Marking several system routes" on
    page 1373).
    The selected system routes are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked System routes via the context menu> entry
    Delete.
    3. Confirm with OK.
    PTVGROUP

    1383

    15.33.9.3 Deleting the active system routes


    A query opens.
    4. Confirm the query.
    The system routes are deleted.
    15.33.9.3 Deleting the active system routes
    1. Select the system routes that you want to delete. To do this, use filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected system routes are active.
    2. In the Network window, right-click the System routes button.
    The System routes context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type System routes has been selected, you can also delete all
    active system routes via the Edit> Multi-delete menu or by pressing the D EL key.
    4. Confirm with OK.
    The system routes are deleted.

    15.34

    Managing Points of Interest (POIs)


    POIs are user-defined network objects which are of special interest, like car parks or schools.
    You can use POIs to display facilities with special usage, for data management, or for reachability analyses, for example.
    POIs have a spatial reference and are managed in categories which you can define. Therefore, you must create at least one POI category, if you want to create a POI (see "Creating a
    POI category" on page 1384).
    POIs are fixed in the coordinate system. Furthermore, they can have a surface, for example, to
    display an industrial area. POIs can also be linear, for example, to display the course of a river.
    However, you cannot insert linear POIs manually. You can import linear POIs with the network
    file or a shapefile.

    15.34.1 Creating a POI category


    1. In the Network menu, select the POI categories entry.
    The Edit POI categories window opens.
    2. Click the

    Create button.

    The Create POI category window opens.

    1384

    PTVGROUP

    15.34.2 Editing a POI category

    3. Make the desired changes.


    Element

    Description

    No.

    Categories are numbered consecutively

    Code

    Code of the category

    Name

    Name of the category

    Comment

    Comment on the category (free text entry)

    Super category

    Use the drop-down list to select a superordinated category (if


    available).
    If no superordinated category has been selected, the inserted
    category becomes the superordinated category.

    4. Confirm with OK.


    The POI category is created.
    Note: POI categories with active POIs only will be saved in the network file.

    15.34.2 Editing a POI category


    1. In the Network menu, select the POI categories entry.
    The Edit POI categories window opens.
    2. Click the desired category.
    3. Click the

    Edit button.

    4. Edit the desired attributes (see "Creating a POI category" on page 1384).
    5. Confirm with OK.
    The POI category is changed.

    15.34.3 Deleting a POI category


    If you delete a POI category, all POIs that are allocated to this category are deleted automatically. If the POI category has subcategories, they will not be deleted and move up one
    level.
    1. In the Network menu, select the POI categories entry.

    PTVGROUP

    1385

    15.34.4 Using user-defined attributes for POI categories


    The Edit POI categories window opens.
    2. Click the desired category.
    Delete button.

    3. Click the

    If POI objects are allocated to this category, a security prompt opens.


    4. Confirm this query.
    The POI category will be deleted with all allocated POI objects.

    15.34.4 Using user-defined attributes for POI categories


    If you assign a user-defined attribute to a POI category (see "Creating a user-defined attribute"
    on page 973), it is automatically applied to all subcategories of this super category. This function is useful, if you want to trace or analyze a common feature of POIs in several categories
    and subcategories.
    Example: You create the POI category education centersand assign it the user-defined attribute number of students. In this case, you can trace and analyze the number of students of
    all education centers you defined in the subcategories and POIs of this category.
    You can edit a user-defined attribute of POI category only on the level on which you created it.

    15.34.5 Creating a POI


    Note: Before you create a POI, you need to create a POI category (see "Creating a POI
    category" on page 1384).
    1. In the Network window, click the

    Insert mode icon.

    2. Click the POIs button.


    3. In the network, click the position on which you want to insert the POI.
    The Create POI window opens.
    Note: You can edit the position of the POI afterwards.
    4. Make the desired changes.
    Element

    Description

    Category

    Use the drop-down list to allocate a category to the POI.

    Area

    If the option has been selected, you can define a polygon for the POI.

    Manage
    Click this button, if you want to open the Edit POI categories window and
    categories edit the POI categories (see "Editing a POI category" on page 1385).
    Tip
    You can select the category for the POI also via the Category management window.

    1386

    PTVGROUP

    15.34.6 Properties and options of POIs


    5. Confirm with OK.
    The Create POI window opens.
    6. Enter the desired data (see "Properties and options of POIs" on page 1387).
    7. Confirm with OK.
    8. If you have selected the Polygon check box, you are now in the Create mode and can
    insert the polygon boundary (see "Creating a boundary" on page 1042).
    The POI is inserted.
    Note: If you want to define the display of POIs, select the Graphics> Edit graphic parameters > menu, Points of Interest entry (see "Displaying POIs" on page 1388).

    15.34.6 Properties and options of POIs

    The upper section of the Create POI or Edit POI window contains the general attributes of the
    POI. In the lower section, you can edit specific attributes in various tabs.
    POIs: General attributes
    Element

    Description

    Number

    The POIs are numbered consecutively per category.

    Category

    Display of the category to which the POI is allocated.

    Code

    Code of the POIs

    Name

    Name of the POIs

    POIs: Basis tab

    PTVGROUP

    1387

    15.34.7 Displaying POIs


    Element

    Description

    Comment

    Enter an arbitrary text

    Position

    You can edit the position of the POI in the network (see "Shifting POIs" on
    page 1392).

    Display

    You can use an image file to display a POI.


    Use separate image
    etc.) to display this POI. Afterwards, you still have to activate the display
    of images in the graphics parameters (see "Displaying Points of Interest" on
    page 2348).
    If the option has not been selected, all POIs of a POI category are illustrated by the same graphic (see "Editing the display settings of a POI category" on page 2350).
    Use separate height and angle
    If the option has been selected, you can specify a standard height and
    angle for the display of the POI.
    Note
    POIs are only displayed, if the graphic parameters are set accordingly (see
    "Displaying Points of Interest" on page 2348).

    Note: If you want to insert images, we recommend to save all image files in one directory
    and to specify this directory in the project directory file (see "Opening and saving a project directories file" on page 838). A image file you inserted will not be saved together
    with the version file (*.ver). If Visum does not find the path to the version file the next time
    it is opened, a warning is issued and the graphic will not be displayed.
    POIs: Allocations tab
    You can allocate the POIs to different network objects (see "Allocating network objects to a
    POI" on page 1398). Example: A POI which represents a parking lot in a downtown area can
    be allocated to links to show to which links the parking lot's exits lead to.
    Note: You can graphically display the allocations to associated network objects (see
    "Showing POI connections" on page 2351).

    15.34.7 Displaying POIs


    For all POIs of a specific type or for each POI category, you can specify how to display the POIs
    (see "Displaying Points of Interest" on page 2348). In addition, you can modify the display of
    individual POIs.
    15.34.7.1 Hiding or showing POIs
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.

    1388

    PTVGROUP

    15.34.7.2 Changing the symbol of an individual POI


    2. In the Edit graphic parameters window, select the entry Points of Interest.
    On this page you can specify, which POIs shall be displayed and how they will be displayed
    (see "Displaying Points of Interest" on page 2348).
    15.34.7.2 Changing the symbol of an individual POI
    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.


    3. In the network, double-click the POI.
    The Edit POI window opens.
    4. Select the Basis tab.
    5. In the Display section, make the desired settings (see "POIs: Basis tab" on page 1387).
    The POI is displayed according to your settings.
    15.34.7.3 Changing image size and rotation angle of a POI
    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.


    3. Click the POI to mark it.
    4. Right-click the POI.
    A shortcut menu opens.
    5. Select the Edit image size and rotation angle entry.
    The POI is displayed as follows:

    6. Enlarge or reduce the size of the POI by dragging one of the corners while holding down
    the mouse button.
    7. Rotate the POI by clicking one of its arrow heads, hold down the mouse button and drag it
    in the desired direction.
    8. Confirm with OK.
    The image size and/or the rotation angle are changed.
    Tip: You can also edit the image size and the rotation angle in the Edit POI window via
    the Use separate height and angle option (see "POIs: Basis tab" on page 1387).

    PTVGROUP

    1389

    15.34.8 Finding POIs

    15.34.8 Finding POIs


    How to find POIs is described for all network objects (see "Finding network objects in the network" on page 999).

    15.34.9 Selecting POIs


    There are several ways to select POIs in order to edit them in another step.
    Marking POIs
    Setting POIs active/passive
    15.34.9.1 Marking POIs
    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.


    3. In the network, click the POI.
    The POI is marked.
    4. If you want to mark additional POIs, press the C TRL key and keep it pressed.
    5. One by one, click the POIs that you want to mark.
    The POIs are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive POIs with the mouse (see "Marking only active network objects" on page 1005).
    Tip: Alternatively, you can mark a POI by searching for it (see "Finding network objects in
    the network" on page 999) or by selecting the respective row in the list of POIs (see
    "Selecting list sections" on page 2319).
    15.34.9.2 Setting POIs active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).
    Note: POI categories with active POIs only will be saved in the network file.

    15.34.10 Editing the attribute values of POIs


    You can edit the attribute values of one POI, all marked POIs or all (active) POIs.
    15.34.10.1 Editing the attribute values of POIs
    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.


    1390

    PTVGROUP

    15.34.10.2 Editing the attribute values of marked POIs


    3. In the network, double-click the POI that you want to edit.
    The Edit POI window opens.
    Tip: Alternatively, you can call the window from the list of POIs via the context menu>
    entry Edit.
    4. Edit the values of the desired attributes (see "Properties and options of POIs" on page
    1387).
    5. Confirm with OK.
    The attribute values of the POI are changed.
    Tip: You can also edit the attribute values in the Quick view window or in the list of the
    network object type (see "Quick view window" on page 810 and "Working with lists" on
    page 2299).
    15.34.10.2 Editing the attribute values of marked POIs
    1. Mark the POIs whose attribute values you want to edit (see "Marking POIs" on page 1390).
    The selected POIs are marked.
    2. Press the ENTER key.
    The Multi-edit points of interest: <Number> objects window opens.
    Tip: You can also call the Multi-editpoints of interest: <Number> objects window
    via the context menu> Edit entry or by double-clicking the last point of interest that
    you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of POIs" on page 1387
    and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.34.10.3 Editing the attribute values of all or all active POIs
    Note: If there are no passive POIs in the network, all POIs will be edited. Markings of POIs
    are ignored.
    1. If required, set the POIs active, whose attribute values you want to edit. To do this, use
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected POIs are active.
    2. In the Network window, right-click the POIs button.
    PTVGROUP

    1391

    15.34.10.4 Displaying the attribute values of a POI in a column chart


    The Points of Interest context menu opens.
    3. Select the Multi-edit entry and then the desired category.
    Note: You can edit either All POIs or select a category. All existing categories as well
    as all categories with their subcategories can be selected. For more than twelve categories select the category above the Select category entry in a separate window. In
    this window you can also specify whether all POIs of the subcategories shall be edited.
    The Multi-edit points of interest <Number>: <Category> window opens.
    4. Specify whether you want to set the lengths of all or all active POIs.
    Element

    Description

    Only active ones

    If the option has been selected, only active POIs will be taken into
    account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of POIs" on page 1387
    and "Editing attribute values of network objects" on page 983).
    The attribute values of the selected category/categories are changed.
    7. Click the Close button.
    15.34.10.4 Displaying the attribute values of a POI in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.34.11 Shifting POIs


    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.


    3. Click the first POI in the network, which you want to shift.
    The POI is marked.
    4. Click and hold down the left mouse button.
    5. Drag the POI to the desired position and release the left mouse button.
    Notes: If you press the ESC key while dragging, you can cancel the action and the POI
    is reset to its original position.
    The POI is shifted to the new position.

    1392

    PTVGROUP

    15.34.12 Aggregating marked or active POIs to one POI


    Tip: You can also edit the position of the POI in the Edit POI window. (see "Properties
    and options of POIs" on page 1387).

    15.34.12 Aggregating marked or active POIs to one POI


    You have different possibilities to aggregate multiple POIs to one POI.
    Aggregating marked POIs to one POI
    Aggregating all active POIs to one POI
    15.34.12.1 Aggregating marked POIs to one POI
    1. Mark minimum two POIs that you want to aggregate to one POI (see "Marking POIs" on
    page 1390).
    The selected POIs are marked.
    2. Right-click the POIs button.
    The POIs context menu opens.
    3. Select the Aggregate POIs entry.
    The Edit POIs window opens.
    Tip: The functionality is also provided in the Edit> Aggregate POIs menu.
    4. Enter the desired data (see "Editing the attribute values of POIs" on page 1390).
    Note: If all marked POIs have the same category, this category will be preselected.
    5. Confirm with OK.
    The new aggregated POI is inserted.
    15.34.12.2 Aggregating all active POIs to one POI
    1. If required, set the POIs active, whose attribute values you want to edit. To do this, use
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected POIs are active.
    2. In the Network window, click the POIs button.
    3. Press F7.
    The Edit POIs window opens.
    Tip: The functionality is also provided in the Edit> Aggregate POIs menu.

    PTVGROUP

    1393

    15.34.13 Deleting enclaves of POIs


    Note: If all POIs are active, you have to confirm an additional prompt with OK before
    proceeding.
    4. Enter the desired data (see "Editing the attribute values of POIs" on page 1390).
    Note: If all marked POIs have the same category, this category will be preselected.
    5. Confirm with OK.
    The new aggregated POI is inserted.

    15.34.13 Deleting enclaves of POIs


    You can delete enclaves, i.e. "holes" from the surfaces of POIs.
    1. If required, set the POIs active, whose enclaves you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected POIs are active.
    2. In the Network window, right-click the POIs button.
    The Points of Interest context menu opens.
    3. Select the Delete enclaves entry.
    The Multi-edit points of interest window opens.
    Tip: If the network object type POIs has been selected, you can also call the Multi-edit
    points of interest window via the Edit> Delete enclaves menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to delete the enclaves of all POIs or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active POIs will be taken into
    account.

    6. Click the Delete enclaves button.


    A query opens.
    7. Confirm with OK.
    The enclaves are deleted.
    8. Click the Close button.

    1394

    PTVGROUP

    15.34.14 Normalizing surfaces of POIs

    15.34.14 Normalizing surfaces of POIs


    You can normalize surfaces of POIs. In this process, the sizes of the surfaces are calculated
    correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    1. If required, set the POIs active, whose surfaces you want to normalize, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected POIs are active.
    2. In the Network window, right-click the POIs button.
    The POIs context menu opens.
    3. Select the Normalize surfaces entry.
    The Multi-edit POIs window opens.
    Tip: If the network object type POIs has been selected, you can also call the MultieditPOIs window via the Edit> Normalize surfaces menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to normalize the surfaces of all POIs or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active POIs will be taken into
    account.

    6. Click the Normalize surfaces button.


    A query opens.
    7. Confirm with OK.
    The surfaces are normalized.
    8. Click the Close button.

    15.34.15 Fuzzy alignment of POIs surfaces


    You can perform a fuzzy alignment for POIs surfaces in the network. Then the points of a surface are moved, within a defined threshold, towards a reference surface. This allows you to
    remove unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy surface alignment (see "Importing Shapefiles" on page 2221).
    1. If required, set the POIS active whose surfaces you want to fuzzy align via

    PTVGROUP

    1395

    15.34.16 Allocating a POI to a different category


    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected zones are active.
    2. In the Network window, click the

    Edit mode icon.

    3. Right-click the POIs button.


    A context menu opens.
    4. Select the Fuzzy surface alignment entry.
    The Fuzzy surface alignment window opens.
    5. Make the desired changes.
    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    6. Confirm with OK.


    The desired surfaces in the network are aligned.

    15.34.16 Allocating a POI to a different category


    You can allocate POIs to a different POI category.
    Notes: If a POI has a user-defined attribute that does not exist in the new category, it will
    be lost. Create the corresponding attributes beforehand, if required.
    When modifying the category, a POI gets a new number, if the number is allocated
    already.
    If a POI has an allocation to the category to which it will be moved, the allocation is
    moved to the category it originates from (see "Allocating network objects to a POI" on
    page 1398).

    1396

    PTVGROUP

    15.34.16 Allocating a POI to a different category


    Allocating an individual POI to a different category
    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.


    3. Right-click the desired POI.
    The context menu opens.
    4. Select the Edit category entry.
    The Select the POI category window opens.
    Tip: Alternatively, you can call the window from the list of POIs via the context menu>
    Edit category entry.
    5. From the drop-down list, select the desired category.
    6. Confirm with OK.
    The POI is allocated to the other category.
    Allocating multiple POIs to a different category
    You can allocate multiple POIs to a different POI category. To do this you can select the POIs
    by setting them active beforehand. Or you can select them by category.
    1. If required, mark the desired POIs (see "Selecting POIs" on page 1390).
    2. In the Network window, click the

    Edit mode icon.

    3. Right-click the POIs button.


    The Points of Interest context menu opens.
    4. Select the Multi-edit entry and then the desired category under the desired entry.
    Element

    Description

    All POIs...

    Allocates a new category to all or all active POIs

    Select category...

    Opens the Select the POI category window. From the selection
    list select the category whose POIs a new category is to be allocated to.
    With the Edit also the POIs of sub-categories option, you can
    specify whether also the POIs of the subcategories are to be edited.
    Note
    This option is available if more there are more than 12 categories.

    Category POI

    Allocates a new category to all or all active POIs of the selected

    PTVGROUP

    1397

    15.34.17 Allocating network objects to a POI


    Element

    Description

    <name>

    category. POIs in the subcategories are not changed.

    Category POI
    <Name> and subcategories

    Allocates a new category to all or all active POIs of the selected


    category and all subcategories.

    The Multi-edit window opens.


    5. Select the Special functions tab.
    6. Specify whether you want to change the category for all or all active POIs.
    Element

    Description

    Only active ones

    If the option has been selected, only active POIs will be taken into
    account.

    7. From the drop-down list, select the desired category.


    8. Confirm with Edit category.
    The POIs are allocated to the new category.

    15.34.17 Allocating network objects to a POI


    You can allocate network objects to a POI. You can select the network objects graphically or in
    a list.
    Note: You can display the allocations with connecting lines in the Network editor window (see "Showing POI connections" on page 2351).
    15.34.17.1 Allocating network objects in a list
    1. In the Network window, click the

    Edit mode window.

    2. Click the POIs button.


    3. In the network, double-click the POI whose attribute values you want to edit.
    The Edit POI window opens.

    1398

    PTVGROUP

    15.34.17.1 Allocating network objects in a list

    4. Select the Allocations tab.


    5. In the Network object type list, select the network object type to which you want to allocate
    a POI or whose allocation you want to edit or delete.
    Note: All allocated network objects of the selected network object type are listed in
    the Allocated list. All allocated network objects of the selected network object type
    are listed in the Allocatable list.
    6. Choose the desired setting for the Edit values right now option.
    Note: The option is only relevant for links and nodes.
    If the option has been selected, a window for additional settings opens directly after
    allocating the network object (see "Specifying settings for POI allocations" on page
    1401). You can also open this window with the Edit button.
    7. Allocate the POI to a network object by selecting it in the Allocatable list and click the
    icon.
    Note: Depending on the setting a window opens in which you can specify further settings .(see "Specifying settings for POI allocations" on page 1401).
    The entry is added to the Allocated list.
    8. Remove an allocation by selecting the network object in the Allocated list and click the
    icon.
    The allocation will be removed once you have confirmed a query.

    PTVGROUP

    1399

    15.34.17.2 Allocating network objects graphically


    15.34.17.2 Allocating network objects graphically
    1. In the Network window, click the

    Edit mode window.

    2. Click the POIs button.


    3. Click the POI you want to delete.
    4. Right-click the POI.
    A context menu opens.
    5. Select the Allocate entry.
    The Allocate POI window opens.

    6. In the Target network object drop-down list, select the desired network object type.
    7. Select one of the following options:
    Element

    Description

    Create

    If the option has been selected, you can allocate a network object.
    Note
    In the case of links and nodes a window opens in which you can specify
    further settings (see "Specifying settings for POI allocations" on page
    1401).

    Edit

    If the option has been selected, you can edit the settings of an allocation to
    a link or a node (see "Specifying settings for POI allocations" on page
    1401).

    Delete

    If the option has been selected, you can remove an allocation.

    8. Choose the desired setting for the Edit details option.


    Note: This option is only active when allocating links.
    If the option has been selected, a window for additional settings opens directly after
    allocating the network object (see "Specifying settings for POI allocations" on page
    1401).
    9. Click the desired network object.
    1400

    PTVGROUP

    15.34.17.3 Specifying settings for POI allocations

    Notes: In the case of links and nodes a window opens in which you can specify further settings (see "Specifying settings for POI allocations" on page 1401).
    If you allocate a link, the position of the click will be saved in the settings.
    10. Confirm with OK.
    The allocation is created, edited or deleted.
    15.34.17.3 Specifying settings for POI allocations
    For allocations between POIs and links or nodes you can specify particular settings.
    1. Open the window with the settings.
    In the Edit POI window, select the desired allocation and click the Edit button (see
    "Allocating network objects in a list" on page 1398).
    In the Allocate POI window, select the Edit option and click the desired network object
    (see "Allocating network objects graphically" on page 1400).
    The Allocation values (for links) or Transport systems (for nodes) window opens.
    2. Make the desired changes.
    Settings for allocations between POI and link
    Element

    Description

    Transport systems

    The button opens the Transport systems window in which you can
    select the transport systems that are assigned to the allocation.

    Type of allocation Use the drop-down list to specify the direction the allocation applies
    to.
    Position

    Use the slider to specify the exact position where the allocation line
    crosses the link. Modifications are displayed directly in the Network
    editor window.

    Settings for allocations between POI and node


    Element

    Description

    Transport systems

    In this window you select the transport systems that are assigned to
    the allocation.

    15.34.18 Deleting POIs


    There are several ways to delete POIs.
    15.34.18.1 Deleting a POI
    1. In the Network window, click the

    Edit mode icon.

    2. Click the POIs button.

    PTVGROUP

    1401

    15.34.18.2 Deleting several marked POIs


    3. Click the POI in the network, which you want to delete.
    4. Press the DEL key.
    The POI is deleted.
    Tip: You can also delete the marked POI via the Delete entry in the context menu.
    15.34.18.2 Deleting several marked POIs
    1. Mark the POIs that you want to delete (see "Marking POIs" on page 1390).
    The selected POIs are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked POIs via the Delete entry in the context menu.
    3. Confirm with OK.
    The marked POIs are deleted.
    15.34.18.3 Deleting all POIs of a category
    1. In the Network window, right-click the POIs button.
    The Points of Interest context menu opens.
    2. Select the Multi-delete entry and the desired category.
    Note: All existing categories as well as all categories with their subcategories can be
    selected. For more than twelve categories select the category above the Select category entry in a separate window. In this window you can specify whether all POIs of
    the subcategories shall be deleted, too.
    All POIs of the selected categories and, where applicable, all subcategories are deleted.
    15.34.18.4 Deleting all active POIs
    1. Select the POIs, which you want to delete. To do this, use
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected POIs are active.
    2. In the Network window, right-click the POIs button.
    The Points of Interest context menu opens.
    3. Select the Multi-delete > All POIs entry.
    A query opens.
    1402

    PTVGROUP

    15.35 Managing GIS objects


    4. Confirm with OK.
    All active POIs are deleted.

    15.35

    Managing GIS objects


    GIS objects (GIS = geographic information system) extend the network model by special layers
    which are directly incorporated from GIS ArcGIS and can be linked with the Visum network
    data, via blending features. The objects are only available while you are connected to a Personal Geodatabase (PGD) (see "GIS objects" on page 2211).

    15.36

    Managing count locations


    Count locations serve for data management and display of counted link data. Count locations
    are independent network objects which are allocated to one direction of a particular link.
    Notes: You can create several count locations on a link.
    You can allocate detectors to a count location (see "Managing detectors" on page 1410).

    15.36.1 Creating a count location


    Note: You can create count locations on links only.
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Count locations button.


    3. In the desired direction of the desired link, click the position where you want to insert the
    count location.
    A red rectangle is displayed at the position and the Edit count location window opens.
    Note: You can edit the position of the count location afterwards.
    4. Enter the desired data (see "Properties and options of count locations" on page 1404).
    5. Confirm with OK.
    The count location is inserted in the network.

    PTVGROUP

    1403

    15.36.2 Properties and options of count locations

    15.36.2 Properties and options of count locations

    The upper section of the Create count location or Edit count location window contains the
    general attributes of the count location. In the lower section, you can edit specific attributes.
    15.36.2.1 Count locations: General attributes
    Element

    Description

    Number

    Unique number of the count location


    The count locations are numbered consecutively. The preset number
    can be overwritten by a number which has not yet been assigned in
    the network.

    Type

    The count location type (00...99) serves the categorization of the


    count locations.

    Code

    Code of the count location

    Name

    Name of the count location

    15.36.2.2 Count locations: Basis tab

    1404

    Element

    Description

    AddValue1 AddValue5

    Free attributes to which you can allocate values


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes. The advantage is that you
    can name used-defined attributes appropriately.

    Position count

    Link

    PTVGROUP

    15.36.3 Finding a count location


    Element

    Description

    location

    Display of the number of the link on which the count location is positioned
    Rel. pos. (0...1)
    You can edit the relative position of the count location. The marked
    position is entered as a share of the link length From Node - To
    Node. Enter the share in the form of a decimal place between 0 and
    1. The following applies: 0.0 = From Node, 0.5 = middle of the link.
    Position
    Alternatively, you can determine the position of the count location
    with the scroll bar (see "Shifting a count location" on page 1407).

    15.36.3 Finding a count location


    How to find a count location is described for all network objects (see "Finding network objects
    in the network" on page 999).

    15.36.4 Selecting count locations


    There are several ways to select count locations in order to edit them in another step.
    Marking count locations
    Setting count locations active/passive
    15.36.4.1 Marking count locations
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Count locations button.


    3. In the network, click the count location that you want to mark.
    The count location is marked.
    4. If you want to mark additional count locations, press the C TRL key and keep it pressed.
    5. One by one, click the count locations that you want to mark.
    The count locations are marked.

    Note: If the
    Click only active objects icon is pressed in the toolbar, you cannot mark
    passive count locations with the mouse (see "Marking only active network objects" on
    page 1005).
    Tip: Alternatively, you can mark a count location by searching for it (see "Finding network
    objects in the network" on page 999) or by selecting the respective row in the list of count
    locations (see "Selecting list sections" on page 2319).

    PTVGROUP

    1405

    15.36.4.2 Setting count locations active/passive


    15.36.4.2 Setting count locations active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.36.5 Editing attribute values of count locations


    You can edit the attribute values of one count location, all marked count locations or all
    (active) count locations.
    15.36.5.1 Editing the attribute values of a count location
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Count locations button.


    3. In the network, double-click the count location whose attribute values you want to edit.
    The Edit count location window opens.
    Tip: If the count location is marked, you can also call the Edit count location window
    via the context menu> Edit entry or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of count locations" on
    page 1404).
    5. Confirm with OK.
    The attribute values are edited.
    Tip: You can also edit the values of the input attributes of count locations in the Quick
    view window or in the list of the network object type (see "Quick view window" on page
    810 and "Working with lists" on page 2299).
    15.36.5.2 Editing attribute values of marked count locations
    1. Mark the count locations whose attribute values you want to edit (see "Marking count locations" on page 1405).
    The selected count locations are marked.
    2. Press the ENTER key.
    The Multi-edit count locations: <Number> objects window opens.
    Tip: You can also call the Multi-edit count locations: <Number> objects window via
    the context menu > Edit entry or by double-clicking the last count location which you
    want to mark.

    1406

    PTVGROUP

    15.36.5.3 Editing the attribute values of all or all active count locations
    3. Edit the values of the desired attributes (see "Properties and options of count locations" on
    page 1404 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.36.5.3 Editing the attribute values of all or all active count locations
    Note: If there are no passive count locations in the network, all count locations are edited.
    Markings of count locations are ignored.
    1. If required, set the count locations active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected count locations are active.
    2. In the Network window, right-click the Count locations button.
    The Count locations context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit count locations window opens.
    4. Select whether you want to edit the attribute values of all count locations or just the active
    ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active count locations will be
    taken into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of count locations" on
    page 1404 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.36.5.4 Displaying the attribute values of a count location in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.36.6 Shifting a count location


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Count locations button.

    PTVGROUP

    1407

    15.36.7 Setting the polygon allocation of count locations


    3. In the network, click the count location that you want to shift, and hold down the mouse button.
    4. Drag the count location along the link to the desired position and release the left mouse button.
    Notes: If you press the ESC key while dragging, you can cancel the action and the
    count location is reset to its original position.
    The count location is moved to the new position.
    Tip: Alternatively, you can edit the position of the count location in the Edit count location
    window (see "Properties and options of count locations" on page 1404).

    15.36.7 Setting the polygon allocation of count locations


    Prerequisite is that there are count locations within a polygon (territory, zone or main zone).
    You can specify that a selected attribute receives the number of the territory, zone, or main
    zone in which the count location lies.
    1. If required, set the count locations active, whose allocation you want to set, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected count locations are active.
    2. In the Network window, right-click the Count locations button.
    The Count locations context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit count locations window opens.
    4. Make sure that the Special functions tab has been selected.
    5. Make the desired changes.
    Element

    Description

    Only active ones

    If the option has been selected, only active count locations will
    be taken into account.
    If the option has not been selected, all count locations will be
    taken into account.

    Object

    In the drop-down list, you can select the type of network object
    whose number you want to use as attribute value.

    Attribute to be set Use the drop-down list to select an attribute which shall store the
    number of the selected object.

    1408

    PTVGROUP

    15.36.8 Deleting count locations


    6. Click the Set button.
    The count locations store the number as attribute value.
    7. Click the Close button.

    15.36.8 Deleting count locations


    There are several ways to delete count locations.
    15.36.8.1 Deleting a count location
    Note: If you delete a count location to which a detector has been allocated, the detector
    will not automatically be deleted. It just loses its allocation.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Count locations button.


    3. In the network, click the first count location that you want to delete.
    4. Press the DEL key.
    The count location is deleted.
    15.36.8.2 Deleting several marked count locations
    1. Mark the count locations that you want to delete (see "Marking count locations" on page
    1405).
    The selected count locations are marked.
    2. Press the DEL key.
    A query opens.
    3. Confirm with OK.
    The marked count locations are deleted.
    15.36.8.3 Deleting all active count locations
    1. Select the count locations, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected count locations are active.
    2. In the Network window, right-click the Count locations button.
    The Count locations context menu opens.
    3. Select the Multi-delete entry.
    A query opens.

    PTVGROUP

    1409

    15.37 Managing detectors


    Tip: Alternatively, you can press the DEL key.
    4. Confirm with OK.
    All active count locations are deleted.

    15.37

    Managing detectors
    In Visum, there are the following types of detectors:
    Detectors which are used for lane-based data management of counted values. You can
    insert them anywhere in the network and allocate them to count locations (see Fundamentals: Chpt. 3.1.17 , page 84).
    Detectors which serve to model signal control. You can insert them in the node and main
    node section of the Junction editor and allocate them to signal control (see "Creating
    detectors" on page 1478). These detectors cannot be allocated to count locations (see
    Fundamentals: Chpt. 3.1.17 , page 84).
    Note: Data provided by detectors of the second type can be exported to Vissim using the
    ANM export function (see "ANM interface" on page 2511).

    15.37.1 Creating a detector


    There are several ways to create detectors.
    15.37.1.1 Creating a detector for a count location
    If you want to create a detector which is allocated to a count locations, proceed as follows:
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Detectors button.


    3. In the network, click the position where you want to position the detector.
    The Create detector window opens.
    Note: You can edit the position of the detector afterwards.
    4. Enter the desired data (see "Properties and options of detectors" on page 1411).
    5. Confirm with OK.
    The detector is inserted.
    15.37.1.2 Creating a detector in the node and main node section
    Use the Junction editor if you want to create a detector in the node or main node section (see
    "Creating detectors" on page 1478).

    1410

    PTVGROUP

    15.37.2 Properties and options of detectors

    15.37.2 Properties and options of detectors


    Creating a detector for a count location

    Creating a detector in the node and main


    node section (see "Creating detectors" on
    page 1478)

    The upper section of the Create detector or Edit detector window contains the general attributes of the detector. In the lower section, you can edit specific attributes.
    15.37.2.1 Detectors: General attributes
    Element

    Description

    Number

    Unique number of the detector


    The detectors are numbered consecutively. The preset number can be overwritten by a number which has not yet been assigned in the network.

    Type

    The detector type (00...99) serves the categorization of the detectors.

    Code

    Code of the detector

    Name

    Name of the detector

    PTVGROUP

    1411

    15.37.2.2 Detectors: Basis tab


    Element

    Description

    SCJ

    Drop-down list of the signal controlled junction which is allocated to the detector

    Count loca- Use the drop-down list to allocate the detector to a count location.
    tion
    Note
    This drop-down list will not be displayed if you create or edit detectors in the
    node or main node section (see "Creating detectors" on page 1478).
    Tip
    In the network display, you can label the count locations with numbers via the
    Graphics> Edit graphic parameters> menu and the Count locations >
    Table entry (see "Specifying basic settings for the network window" on page
    2337).
    15.37.2.2 Detectors: Basis tab
    Note: The elements Nodes, Main nodes, Lanes, Crosswalks and Distance from stop
    line will only be displayed if you create or edit in the node or main node section.
    Element

    Description

    Node

    Number of the allocated node

    Main node

    Number of the allocated main node

    Lanes

    Selection of one or several lanes covered by the detector

    Crosswalks

    Selection of one or several crosswalks covered by the detector

    Distance from
    stop line

    Distance between leading edge of the detector and the next signal
    head of the signal control junction on the lane covered (if there is a
    signal head)
    Note
    This value is relevant for the export of the data to Vissim (see "ANM
    interface" on page 2511).

    Lane pos.

    Number of lane the detector loop is placed on (first covered lane)

    Observed lanes

    Number of lanes covered by the detector

    Enabled

    If the option has been selected, the detector is activated.

    Position

    You can edit the coordinates of the detector in the network by entering new values (see "Shifting a detector" on page 1415).

    15.37.2.3 Detectors: Data tab


    Note: The Data tab will only be displayed if you create or edit a detector in the node or
    main node area (see "Creating detectors" on page 1478).

    1412

    PTVGROUP

    15.37.3 Finding a detector


    Element

    Description

    Transport systems

    Via this button you can open the Transport system window in which
    you can allocate transport systems to the detector.

    Channel no.

    This number indicates the physical channel number of the detector


    given to it in the control strategy.

    Enabled

    If the option has been selected, the detector is activated.

    15.37.3 Finding a detector


    How to find a detector is described for all network objects (see "Finding network objects in the
    network" on page 999).

    15.37.4 Selecting detectors


    There are several ways to select detectors in order to edit them in another step.
    Marking detectors
    Setting active/passive detectors
    15.37.4.1 Marking detectors
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Detectors button.


    3. In the network, click the detector.
    The detector is marked.
    4. If you want to mark additional detectors, press the C TRL key and keep it pressed.
    5. One by one, click the detectors that you want to mark.
    The detectors are marked.

    Note: If the
    Click only active objects icon is pressed in the tool bar, you cannot mark
    passive detectors with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a detector by searching for it (see "Finding network
    objects in the network" on page 999) or by selecting the respective row in the list of detectors (see "Selecting list sections" on page 2319).
    15.37.4.2 Setting active/passive detectors
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    PTVGROUP

    1413

    15.37.5 Editing attribute values of detectors

    15.37.5 Editing attribute values of detectors


    You can edit the attribute values of one detector, all marked detectors or all (active) detectors.
    15.37.5.1 Editing a detector attribute
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Detectors button.


    3. In the network, double-click the detector that you want to edit.
    The Edit detectors window opens.
    Tip: If the detector is marked, you can also call the Edit detector window via the context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of detectors" on page
    1411).
    5. Confirm with OK.
    The attribute values are edited.
    Tip: You can also edit the attribute values in the Quick view window or in the list of the
    network object type (see "Quick view window" on page 810 and "Working with lists" on
    page 2299).
    15.37.5.2 Editing the attribute values of marked detectors
    1. Mark the detectors whose attribute values you want to edit (see "Marking detectors" on
    page 1413).
    The selected detectors are marked.
    2. Press the ENTER key.
    The Multi-edit detectors: <Number> objects window opens.
    Tip: You can also call the Multi-editdetectors: <Number> objects via the context
    menu> entry Edit or double-click the last detector that you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of detectors" on page
    1411 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.37.5.3 Editing the attribute values of all or all active detectors
    Note: If there are no passive detectors in the network, all detectors are edited. Markings
    of detectors are ignored.
    1414

    PTVGROUP

    15.37.5.4 Displaying the attribute values of a detector in a column chart


    1. If required, set the detectors active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected detectors are active.
    2. In the Network window, right-click the Detectors button.
    The Detectors context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit detectors window opens.
    4. Specify whether you want to edit all or all active detectors.
    Element

    Description

    Only active ones

    If the option has been selected, only active detectors will be taken
    into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of detectors" on page
    1411 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.37.5.4 Displaying the attribute values of a detector in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.37.6 Shifting a detector


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Detectors button.


    3. In the network, click the detector that you want to shift and hold down the left mouse button.
    4. Drag the detector to the desired position and release the left mouse button.
    Notes: If you press the ESC key while dragging, you can cancel the action and the
    detector is reset to its original position.
    The detector is shifted to the new position.
    Tip: You can also edit the position of the detector in the Edit detector window (see "Properties and options of detectors" on page 1411).

    PTVGROUP

    1415

    15.37.7 Deleting detectors

    15.37.7 Deleting detectors


    There are several ways to delete detectors.
    15.37.7.1 Deleting a detector
    Note: If you delete a count location to which a detector has been allocated, the detector
    will not automatically be deleted. It just loses its allocation.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Detectors button.


    3. Click the detector in the network, which you want to delete.
    4. Press the DEL key.
    The detector is deleted.
    Tip: You can also delete the marked detector via the Delete entry in the context menu.
    15.37.7.2 Deleting several marked detectors
    1. Mark the detectors that you want to delete (see "Marking detectors" on page 1413).
    The selected detectors are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked detectors via the Delete entry in the context
    menu.
    3. Confirm with OK.
    The marked detectors are deleted.
    15.37.7.3 Deleting all active detectors
    1. Select the detectors, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected detectors are active.
    2. In the Network window, right-click the Detectors button.
    The Detectors context menu opens.
    3. Select the Multi-delete entry.
    A query opens.

    1416

    PTVGROUP

    15.38 Managing toll systems


    Tip: Alternatively, press the DEL key.
    4. Confirm with OK.
    All active detectors are deleted.

    15.38

    Managing toll systems


    Toll systems are network objects with which you can insert toll zones in the network (see Fundamentals: Chpt. 3.1.18 , page 85).

    15.38.1 Creating a toll system


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Toll systems button.


    3. In the network, click the position where you want to insert the centroid of the toll system.
    The Create toll systems window opens.
    4. Enter the desired data (see "Properties and options of toll systems" on page 1418).
    5. Confirm with OK.
    The centroid of the toll system is inserted. You can now create a boundary.
    Note: The optional boundary is used to calculate the area of the toll system and
    shows its spatial extent.
    You can continue as follows:
    If you do not want to define a boundary for the toll system, press the ESC key. The toll
    system is then inserted as centroid without a boundary. You can specify the boundary
    later (see "Creating a boundary" on page 1042).
    If you want to define the boundary for the toll system, proceed with the next step.
    6. Specify the boundary of the toll system by inserting at least three polygon points in a counterclockwise direction in the desired positions.
    The edges of the boundary polygon are displayed as a rubber band. The hatching and the
    arrows indicate the direction of the surface (see Fundamentals: Chpt. 3.5.2 , page 124).

    PTVGROUP

    1417

    15.38.2 Properties and options of toll systems


    Note: Even though you can also insert the polygon points in a clockwise direction,
    this would create a so-called negative face (=hole), which cannot be saved as boundary as no surface exists yet from which it can be cut out.
    7. Confirm the definition of the boundary with a right-click or press ENTER.
    The boundary is created and the polygon points are highlighted. The Edit shape window
    opens.
    Note: If you confirm the definition of the boundary with a right-click, the coordinates of
    the position of the click will not be saved as polygon point.
    8. If required, reshape the boundary (see "Editing polygon points" on page 1044).
    9. Confirm with OK.
    A query opens.
    10. Click Yes to confirm.
    The links which lie within the boundary are allocated to the toll system and the toll system is
    inserted in the network.
    Notes: If a link has a toll system assigned, the value of the link attribute Toll-PrTSys is not
    used for the TRIBUT learning procedure (see "TRIBUT - Equilibrium_Lohse (static)" on
    page 1966).
    If you want to insert the toll system with a boundary yet without allocated links, click No
    when prompted by the query. You can also allocate links to a toll system later by allocating either a 0, i.e. no toll system, to the link attribute Toll system number in the link list
    or the number of the desired toll system.

    15.38.2 Properties and options of toll systems

    1418

    PTVGROUP

    15.38.2.1 Toll systems: General attributes


    The upper section of the Create toll system or Edit toll system window contains the general
    attributes of the toll system. In the lower section, you can edit specific attributes in theArea toll
    tab.
    15.38.2.1 Toll systems: General attributes
    Element

    Description

    Number

    Unique number of the toll system


    The toll systems are numbered consecutively. You can overwrite the preset
    number with a number that does not yet exist in the network.

    Type

    Select a toll type


    Area toll
    In case of an area toll, a distance-independent fixed amount is charged, if a
    section of the route runs through the toll zone.
    Matrix toll
    In case of a matrix toll, tolls are not the sums of link tolls but randomly set
    amounts specified for pairs (entry exit).

    Code

    Code of the toll system

    Name

    Name of the toll system

    15.38.2.2 Toll systems: Area toll tab


    Note: This tab is also displayed, if you select type Matrix toll.
    Element

    Description

    Name PrT Sys

    List of all PrT transport systems that exist in the network

    Area toll for


    PrT-Sys

    Enter a toll for each transport system


    Note
    This entry is only relevant for toll systems of the type area toll. For toll
    systems of the type matrix toll, you need to specify the tolls elsewhere
    (see "Specifying the matrix toll of a toll system" on page 1422).

    15.38.3 Finding a toll system


    1. How to find a toll system is described for all network objects (see "Finding network objects
    in the network" on page 999).

    15.38.4 Selecting toll systems


    There are several ways to select toll systems in order to edit them in another step.
    Marking toll systems
    Setting toll systems active/passive

    PTVGROUP

    1419

    15.38.4.1 Marking toll systems


    15.38.4.1 Marking toll systems
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Toll systems button.


    3. In the network, click the centroid or within the boundary of the toll system.
    The toll system is marked.
    4. If you want to mark additional toll systems, press the C TRL key and keep it pressed.
    5. One after another, click the centroids or within the boundaries of the toll systems that you
    want to mark.
    The toll systems are marked.

    Note: If the
    Click only active objects icon is pressed in the tool bar, you cannot
    mark passive toll systems with the mouse (see "Marking only active network objects" on
    page 1005).
    Tip: Alternatively, you can mark a toll system by searching for it (see "Finding network
    objects in the network" on page 999) or by selecting the respective row in the list of toll
    systems (see "Selecting list sections" on page 2319).
    15.38.4.2 Setting toll systems active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033).

    15.38.5 Editing attribute values of toll systems


    You can edit the attribute values of one toll system, all marked toll systems or all (active) toll
    systems.
    15.38.5.1 Editing the attribute values of a toll system
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Toll systems button.


    3. In the network, double-click the centroid or within the boundary of the toll system whose attribute values you want to edit.
    The Edit toll system window opens.
    Tip: If the toll system is marked, you can also call the Edit toll system window via the
    context menu> entry Edit or by pressing the ENTER key.

    1420

    PTVGROUP

    15.38.5.2 Editing attribute values of marked toll systems


    4. Edit the values of the desired attributes (see "Properties and options of toll systems" on
    page 1418).
    5. Confirm with OK.
    The attribute values are edited.
    Note: You can also edit the values of the input attributes of toll systems in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.38.5.2 Editing attribute values of marked toll systems
    1. Mark the toll systems whose attribute values you want to edit (see "Setting toll systems active/passive" on page 1420).
    The selected toll systems are marked.
    2. Press the ENTER key.
    The Multi-edit toll systems: <Number> objects window opens.
    Tip: You can also call the Multi-edittoll systems: <Number> objects window via the
    context menu > entry Edit or double-click the last toll system which you want to mark.
    3. Edit the values of the desired attributes (see "Properties and options of toll systems" on
    page 1418 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.38.5.3 Editing the attribute values of all or all active toll systems
    Note: If there are no passive toll systems in the network, all toll systems are edited. Markings of toll systems are ignored.
    1. If required, set the toll systems, whose attribute values you want to edit, active via the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033).
    The selected toll systems are active.
    2. In the Network window, right-click the Toll systems button.
    The Toll systems context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit toll systems window opens.
    4. Select whether you want to edit the attribute values of all toll systems or just the active ones.

    PTVGROUP

    1421

    15.38.5.4 Displaying the attribute values of a toll system in a column chart


    Element

    Description

    Only active ones

    If the option has been selected, only active toll systems will be
    taken into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of toll systems" on
    page 1418 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.38.5.4 Displaying the attribute values of a toll system in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.38.6 Specifying the matrix toll of a toll system


    For the TRIBUT learning procedure, you can use toll systems. For toll systems of the type
    matrix toll, you have to explicitly specify a toll for each possible relation of cordon nodes and
    per transport system. A cordon node is a (main) node on the edge of a toll system. On the one
    hand, it is connected to links of the toll system, on the other hand, it is connected to links that
    are not part of the toll system, or to a connection. Visum provides all relations of cordon nodes
    in a list.
    Note: For two reasons it is advisable to limit the number of cordon nodes and thus, the
    number of relations. On the one hand, it saves computing time, on the other hand, you
    need to define less tolls. To reduce the number, you can take the following measures:
    Combine nodes to main nodes, for example at motorway junctions.
    Incorporate entry and exit links of motorways into the toll system.
    1. Make sure that your model contains a toll system of the type matrix toll (see "Creating a toll
    system" on page 1417).
    2. Open the toll matrices list (see "Opening a list" on page 2299).
    3. In the toolbar of the list, click the button next to the Toll system label.
    The Find toll system window opens.
    4. Select one or more toll systems.
    5. Confirm with Show selection.
    The list automatically contains all relations of cordon nodes of the selected toll systems. If
    you allocate further links to the toll system, the list is updated automatically.

    1422

    PTVGROUP

    15.38.7 Editing the shape of a toll system boundary


    Notes: If you synchronize the list with the Network editor window, the items that
    belong to the currently selected relation are highlighted in the Network editor window. Multiple routes (=straps) can be part of a relation, depending on the entry and
    exit link and also on the transport system.
    In the list, you can display different characteristics of the straps as attributes.
    If you edit particular characteristics of the network, like for example closing links or
    changing speeds, the most recently calculated straps may not represent the shortest
    routes any more. To recalculate the straps and update the corresponding values in
    the list, click the Recalculate straps button.
    Additionally you can specify that straps shall be recalculated automatically whenever
    needed, for example, to display the length (menu Edit> User Preferences> entry
    Network> Matrix toll> option Recalculate straps automatically).
    Prior to an assignment which takes toll systems into account, the straps are always
    recalculated automatically.
    6. In the Toll_PrTSys and Toll reverse direction-PrTSys columns, for each transport system
    and relation, enter the desired tolls.
    7. Specify the tolls for all toll systems of the type matrix toll.
    The settings for the matrix toll are specified.

    15.38.7 Editing the shape of a toll system boundary


    A detailed description on how to edit the shape of a toll system boundary is given for all polygonal network objects (see "Creating a boundary" on page 1042).

    15.38.8 Shifting the centroid of a toll system


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Toll systems button.


    3. In the network, click the centroid that you want to shift and hold down the left mouse button.
    The mouse pointer changes into a cross.
    4. Drag the centroid of the toll system to the desired position and release the left mouse button.

    Notes: If you press the ESC key while dragging, you can cancel the action and the
    count location is reset to its original position.

    PTVGROUP

    1423

    15.38.9 Setting toll system labels to the centroids


    The new position of the centroid is saved. The location and expansion of the boundary
    remains unchanged.
    Note: The centroid should lie within the toll system boundary.

    15.38.9 Setting toll system labels to the centroids


    You can move the position of the labels of all or all active toll systems automatically to the geometrical centroid of their polygons.
    1. If required, via the spatial selection, set the toll systems active, whose label you want to set
    to the geometrical centroid (see "Setting network objects active/passive via the spatial selection" on page 1033).
    The selected toll systems are active.
    2. In the Network window, right-click the Toll systems button.
    The Toll systems context menu opens.
    3. Select the Recalculate the centroids entry.
    The Multi-edit toll systems window opens.
    Tip: If the network object type Toll systems has been selected, you can also call the
    Multi-edit toll systems window via the Edit> Recalculate the centroids menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to set the label of all toll systems or just the active toll systems to
    the geometrical centroid.
    Element

    Description

    Only active
    ones

    If the option has been selected, only active toll systems will be taken
    into account.

    6. Click the Recalculate the centroids from the polygons button.


    A query opens.
    7. Confirm with OK.
    The labels are set to the positions of the geometrical centroids.
    8. Click the Close button.

    15.38.10 Deleting enclaves from toll systems


    You can delete enclaves, i.e. "holes" from the surfaces of toll systems.
    1. If required, set the toll systems active, whose enclaves you want to delete, via

    1424

    PTVGROUP

    15.38.11 Normalizing surfaces of toll systems


    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected toll systems are active.
    2. In the Network window, right-click the Toll systems button.
    The Toll systems context menu opens.
    3. Select the Delete enclaves entry.
    The Multi-edit toll systems window opens.
    Tip: If the network object type Toll systems has been selected, you can also call the
    Multi-edit toll systems window via the Edit> Delete enclaves menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to edit the enclaves of all toll systems or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active toll systems will be
    taken into account.

    6. Click the Delete enclaves button.


    A query opens.
    7. Confirm with OK.
    The enclaves are deleted.
    8. Click the Close button.

    15.38.11 Normalizing surfaces of toll systems


    You can normalize surfaces of toll systems. In this process, the sizes of the surfaces are calculated correctly (see Fundamentals: Chpt. 3.5.2 , page 124).
    1. If required, set the toll systems active whose surfaces you want to normalize via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected toll systems are active.
    2. In the Network window, right-click the Toll systems button.
    The Toll systems context menu opens.
    3. Select the Normalize surfaces entry.
    The Multi-edit toll systems window opens.

    PTVGROUP

    1425

    15.38.12 Fuzzy alignment of toll system surfaces


    Tip: If the network object type Toll systems has been selected, you can also call the
    Multi-edit toll systems window via the Edit> Normalize surfaces menu.
    4. Make sure that the Special functions tab has been selected.
    5. Select whether you want to normalize the surfaces of all toll systems or just the active ones.
    Element

    Description

    Only active ones

    If the option has been selected, only active toll systems will be
    taken into account.

    6. Click the Normalize surfaces button.


    A query opens.
    7. Confirm with OK.
    The surfaces are normalized.
    Click the Close button.

    15.38.12 Fuzzy alignment of toll system surfaces


    You can perform a fuzzy alignment for toll system surfaces in the network. Then the points of a
    surface are moved, within a defined threshold, towards a reference surface. This allows you to
    remove unwanted overlaps or gaps (see Fundamentals: Chpt. 3.5.4 , page 127).
    Note: When importing shapefiles, you can specify whether you want to perform a fuzzy surface alignment (see "Importing Shapefiles" on page 2221).
    1. If required, set the toll systems active whose surfaces you want to fuzzy align via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected toll systems are active.
    2. In the Network window, click the

    Edit mode icon.

    3. Right-click the Toll systems button.


    A context menu opens.
    4. Select the Fuzzy surface alignment entry.
    The Fuzzy surface alignment window opens.
    5. Make the desired changes.

    1426

    PTVGROUP

    15.38.13 Deleting toll systems


    Element

    Description

    Surface set
    column

    Selection of surfaces that are edited (see Editing surface set page
    1054).

    Tolerance column

    Enter a value for the tolerance range. The tolerance range specifies the radius within which the points of a surface may be
    moved. If you enter 0 for a surface set, it becomes a reference set
    and is not moved.
    Adds an additional surface set.
    Deletes the surface set selected.
    Note
    To select multiple surface sets, hold down the C TRL key and click
    the desired entries.

    6. Confirm with OK.


    The desired surfaces in the network are aligned.

    15.38.13 Deleting toll systems


    There are several ways to delete toll systems.
    15.38.13.1 Deleting a toll system
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Toll systems button.


    3. In the network, click the toll system that you want to delete.
    4. Press the DEL key.
    The toll system is deleted.
    Tip: You can also delete the marked toll system via the context menu> entry Delete.
    15.38.13.2 Deleting several marked toll systems
    1. Mark the toll systems that you want to delete (see "Setting toll systems active/passive" on
    page 1420).
    The selected toll systems are marked.
    2. Press the DEL key.
    A query opens.
    Tip: You can also delete the marked toll system via the context menu> entry Delete.
    3. Confirm with OK.
    The toll systems are deleted.
    PTVGROUP

    1427

    15.38.13.3 Deleting active toll systems


    15.38.13.3 Deleting active toll systems
    1. Use the spatial selection to select the toll systems which you want to delete (see "Setting
    network objects active/passive via the spatial selection" on page 1033).
    The selected toll systems are active.
    2. In the Network window, right-click the Toll systems button.
    The Toll systems context menu opens.
    3. Select the Multi-delete entry.
    A query opens.
    Tip: If the network type Toll systems has been selected, you can also delete all
    active toll systems via menu Edit> Multi-delete or by pressing the D EL key.
    4. Confirm with OK.
    The toll systems are deleted.

    15.39

    Managing screenlines
    Screenlines serve to determine volumes which cross virtual lines in the network.

    15.39.1 Creating a screenline


    Notes: A screenline always has a direction. Depending on the order in which the polygon
    points are inserted, the direction always points to the right in the direction of creating.
    Arrow heads along the course indicate the direction.
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Screenlines button.


    3. In the network, click the position where the screenline shall start.
    4. In the network, click the position where the screenline shall end.
    Tip: If you want to edit the shape of the screenline while inserting it, you can specify
    the course with consecutive mouse clicks.
    5. Confirm the definition of the course with the right mouse button or by pressing ENTER.
    The Create screenline window opens.
    6. Enter the desired data (see "Properties and options of screenlines" on page 1429).
    7. Confirm with OK.
    The screenline is inserted.

    1428

    PTVGROUP

    15.39.2 Properties and options of screenlines

    15.39.2 Properties and options of screenlines

    The upper section of the Create screenline or Edit screenline window contains the general
    attributes of the screenline. In the lower section, you can edit specific attributes.
    15.39.2.1 Screenlines: General attributes
    Element

    Description

    Number

    Unique number of the screenline


    The screenlines are numbered consecutively. The preset number can be
    overwritten by a number which has not yet been assigned in the network.

    Code

    Code of the screenline

    Name

    Name of the screenline

    15.39.2.2 Screenlines: Link attributes tab


    Element

    Description

    Rows

    Use this button to open the Attribute selection window. In the Attribute
    selection window you can select indirect attributes which will be listed in
    the Link attributes tab.
    Notes
    The tab contains the respective number of links for the three following possibilities:
    All links
    Links in screenline orientation
    Links against screenline orientation
    You can, for example, determine volumes which result directly from the
    volume data of the links that intersect the screenline when using these three
    possibilities and their aggregation functions.

    Note: Even if a screenline intersects a link several times, the link will be evaluated only
    once.
    PTVGROUP

    1429

    15.39.3 Finding a screenline

    15.39.3 Finding a screenline


    How to find screenlines is described for all network objects (see "Finding network objects in
    the network" on page 999).

    15.39.4 Selecting screenlines


    There are several ways to select screenlines in order to edit them in another step.
    Marking a screenline
    Marking several screenlines
    Setting screenlines active/passive
    15.39.4.1 Marking a screenline
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Screenlines button.


    3. In the network, click the screenline.
    The screenline is marked.
    Note: If the
    Click only active objects icon is pressed in the tool bar, you cannot mark
    passive screenlines with the mouse (see "Marking only active network objects" on page
    1005).
    Tip: Alternatively, you can mark a screenline by searching for it (see "Finding network
    objects in the network" on page 999) or by selecting the respective row in the list of
    screenlines (see "Selecting list sections" on page 2319).
    15.39.4.2 Marking several screenlines
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Screenlines button.


    3. In the network, click the first screenline that you want to mark.
    The screenline is marked.
    4. Press the CTRL key and keep it pressed.
    5. One by one, click the screenlines that you want to mark.
    The screenlines are marked.

    Note: If the
    Click only active objects icon is pressed in the tool bar, you cannot mark
    passive screenlines with the mouse (see "Marking only active network objects" on page
    1005).

    1430

    PTVGROUP

    15.39.4.3 Setting screenlines active/passive


    Tip: You can also mark several screenlines in the network if you select the respective
    rows in the screenline list (see "Working with lists" on page 2299).
    15.39.4.3 Setting screenlines active/passive
    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    15.39.5 Editing attribute values of screenlines


    You can edit the attribute values of one screenline, all marked screenlines or all (active)
    screenlines.
    15.39.5.1 Editing the attribute values of a screenline
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Screenlines button.


    3. In the network, double-click the screenline whose attribute values you want to edit.
    The Edit screenline window opens.
    Tip: If the screenline is marked, you can also call the Edit screenline window via the
    context menu> entry Edit or by pressing the ENTER key.
    4. Edit the values of the desired attributes (see "Properties and options of screenlines" on
    page 1429).
    5. Confirm with OK.
    The attribute values are edited.
    Tip: You can also edit the values of the input attributes of screenlines in the Quick view
    window or in the list of the network object type (see "Quick view window" on page 810
    and "Working with lists" on page 2299).
    15.39.5.2 Editing the attribute values of marked screenlines
    1. Mark the screenlines whose attribute values you want to edit (see "Marking several screenlines" on page 1430).
    The selected screenlines are marked.
    2. Press the ENTER key.
    The Multi-edit screenlines: <Number> objects window opens.
    Tip: You can also call the Multi-edit screenlines: <Number> objects window via the
    context menu > entry Edit or with a double-click on the last screenline which you
    want to mark.

    PTVGROUP

    1431

    15.39.5.3 Editing the attribute values of all or all active screenlines


    3. Edit the values of the desired attributes (see "Properties and options of screenlines" on
    page 1429 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    4. Click the Close button.
    15.39.5.3 Editing the attribute values of all or all active screenlines
    Note: If there are no passive screenlines in the network, all screenlines are edited. Markings of screenlines are ignored.
    1. If required, set the screenlines active, whose attribute values you want to edit, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected screenlines are active.
    2. In the Network window, right-click the Screenlines button.
    The Screenlines context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit screenlines window opens.
    4. Specify whether you want to edit all or all active screenlines.
    Element

    Description

    Only active ones

    If the option has been selected, only active screenlines will be


    taken into account.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Properties and options of screenlines" on
    page 1429 and "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    7. Click the Close button.
    15.39.5.4 Displaying the attribute values of a screenline in a column chart
    You can generate column charts with attribute values for network objects and then export the
    column charts (see "Creating column charts" on page 2492).

    15.39.6 Editing the shape of a screenline course


    Tip: You can already edit the course of a screenline when creating it (see "Creating a
    screenline" on page 1428).
    1. In the Network window, click the
    1432

    Edit mode icon.


    PTVGROUP

    15.39.6.1 Resetting the course of a screenline


    2. Click the Screenlines button.
    3. In the network, click the screenline whose shape you want to edit.
    The screenline is marked.
    4. Right-click in the network display.
    The Screenlines context menu opens.
    5. Select the Edit shape entry.
    The Specify screenline window opens.

    Tip: Alternatively, press the F5 key.


    6. In the network, click the polygon point that you want to shift and hold down the mouse button.
    7. Drag the polygon point to the desired position and release the left mouse button.
    8. If required, drag further polygon points to new positions.
    9. Delete existing polygon points, if required, by pressing the C TRL key and clicking the polygon point.
    10. Insert further polygon points, if required, by pressing the C TRL key and clicking the course.
    11. Confirm with OK.
    Tip: Alternatively, click in the network display to confirm the new course.
    The course is adjusted.
    15.39.6.1 Resetting the course of a screenline
    You can reset the course of a screenline which has just been edited.
    1. Make sure that the Edit screenline window is open.
    2. Click the Initialize button.
    The course of the screenline is reset to the previous course.
    Tip: Alternatively, you can restore the course with F2.

    15.39.7 Creating the opposite direction


    With this functionality you can generate a new screenline in the opposite direction, which has
    the same course and the same attributes as the existing one.

    PTVGROUP

    1433

    15.39.8 Deleting screenlines

    1. In the Network window, click the

    Edit mode icon.

    2. Click the Screenlines button.


    3. In the network, click the screenline of which you want to generate the opposite direction.
    The screenline is marked.
    4. Right-click in the network display.
    The Screenlines context menu opens.
    5. Select the Create opposite direction entry.
    The Create screenline window opens.
    6. Make the desired settings (see "Properties and options of screenlines" on page 1429).
    7. Confirm with OK.
    The screenline is inserted.

    15.39.8 Deleting screenlines


    There are several ways to delete screenlines.
    15.39.8.1 Deleting a screenline
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Screenlines button.


    3. In the network, click the screenline that you want to delete.
    4. Press the DEL key.
    Tip: Alternatively, you can delete the marked screenline via the Delete entry in the
    context menu.
    The screenline is deleted.
    15.39.8.2 Deleting several marked screenlines
    1. Mark the screenlines that you want to delete (see "Marking several screenlines" on page
    1430).
    The selected screenlines are marked.
    2. Press the DEL key.
    Tip: Alternatively, you can delete the marked screenlines via the Delete entry in the
    context menu.
    A query opens.
    3. Confirm with OK.

    1434

    PTVGROUP

    15.39.8.3 Deleting all active screenlines


    The marked screenlines are deleted.
    15.39.8.3 Deleting all active screenlines
    1. Select the screenlines, which you want to delete, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected screenlines are active.
    2. In the Network window, right-click the Screenlines button.
    The Screenlines context menu opens.
    3. Select the Multi-delete entry.
    Tip: Alternatively, press the DEL key.
    A query opens.
    4. Confirm with OK.
    All active screenlines are deleted.

    15.40

    Using the Junction editor


    If you are in the network in the edit mode and double-click on one of the network objects
    nodes, main nodes, turns or main turn, the Junction editor opens. Here you can further model
    the network object (see Fundamentals: Chpt. 3.1.21 , page 88).
    You have several possibilities to edit network objects in the junction editor:
    Editing a node in the Junction editor
    Editing a main node in the Junction editor
    Editing turns in the Junction editor
    Editing main turns in the Junction editor
    Editing links in the Junction editor
    Managing signal controls
    Managing signal groups
    Editing the geometry of a node
    Editing the signal timing of a node
    Managing signal coordination groups
    Edit time-varying attributes
    Calculating and exporting ICA
    Optimizing signal cycles and split of a single signal control
    Displaying turn volumes in the Junction editor

    PTVGROUP

    1435

    15.40 Using the Junction editor

    (1) Menu bar


    As soon as the Junction editor window is open, the menu bar displays the Junction editor
    menu. Among others, it contains all functionalities of the junction editor toolbar.
    (2) Junction editor tool bar
    In the toolbar, the following functions are provided:
    Icon

    1436

    Name

    Description

    No synchronization with
    network editor

    The Network editor and the Junction editor are not


    synchronized.

    Check synchronization
    with Network editor

    The Network editor and the Junction editor are synchronized.

    Attribute selection

    Selection of the attributes which are displayed in


    the list view of the Junction editor
    Note
    The standard selection is the one of the node
    editing window of olderVisum versions.

    Execute ICA calculation

    Starts the ICA calculation (see "Starting an ICA calculation" on page 1499).

    PTVGROUP

    15.40 Using the Junction editor


    Icon

    Name

    Description

    Open/close ICA report


    window

    Opens/closes an Excel sheet with a report (see


    "Displaying the ICA calculation in the report window" on page 1500).

    Enable/disable automatic If this function is activated, Visum recalculates the


    ICA calculation after net- ICA automatically each time an object or attribute is
    work changes
    changed (see "Recalculating ICA automatically" on
    page 1500).

    PTVGROUP

    Export ICA report to


    Excel

    You can save the current ICA calculation to an


    Excel file by clicking the icon (see "Exporting an
    ICA report" on page 1500).

    ICA calculation status

    Checks whether an ICA calculation can be run (see


    "Checking the status of ICA calculations" on page
    1499).

    ICA Signal Cycle and


    Split Optimization

    Via the icon, you can optimize the signal cycle and
    split (see "Optimizing signal cycles and split of a single signal control" on page 1501).

    Vissim node preview

    Opens the VISSIM export preview.

    Create SC

    Use the icon to create a signal control.


    Note
    The signal control will automatically be allocated to
    the currently displayed node/main node, if the
    Signalized control type has been selected.

    Edit SC

    Use the icon to edit a signal control.

    Edit VISSIG controller/edit RBC controller

    If the SC is type Vissig or RBC, the external program or the RBC editor opens. These are available
    only if the particular add-on has been activated.

    Delete LSA

    Use the icon to delete a signal control.

    Create a signal group

    Use the icon to create a signal group.

    Delete signal group

    Use the icon to delete a signal group.

    1437

    15.40 Using the Junction editor


    Icon

    Name

    Description

    Convert LSA to external


    control/
    Convert LSA to Visum
    control

    Via the icon, you can convert an existing signal control into an external controller and edit it with the
    Vissig program, or convert an external controller
    into a Visum controller.
    Note
    This function is only provided with the Vissig addon activated.

    Update control data of


    the SC

    Use the icon to read current data from the control


    file.
    Note
    The icon is only provided for signal controls of type
    Vissig.

    Use stage templates

    You can use the icon to apply existing stage templates to generate stages in the Signal timing view
    (see "Generating stages from templates" on page
    1496).

    Create stage

    Use the icon to create a stage.

    Delete stage

    Use the icon to delete a stage.

    Edit time-varying attributes

    Use the icon to edit time-varying attributes of the


    currently displayed network object, if time-varying
    attributes have been created beforehand (see "Edit
    time-varying attributes" on page 1499).

    (3) Schematic view of the selected object


    The schematic view displays the currently selected object. In the views Node, Main node,
    Links , Turns , Main turns and Geometry , you can edit the object via colored buttons and
    switch to objects that are associated to the currently marked network object. In the Signal
    timing and Turn volumes views, you cannot make any changes.
    You can change the section displayed in the Junction editor window. Similar functionalities as
    those in the Network editorwindow are provided for this(see "Network editor window" on page
    818).
    (4) List view of the selected object
    The list view shows the attributes of the selected object. You can edit the attribute values of editable attributes right in the list.
    Notes: You can select a font for the list view and specify, whether the Short name or the
    Long name of the attributes shall be displayed in the list view (see "Adjusting the display
    and the input options of the list view" on page 1440).
    The Signal timing view does not show attributes below the node but the signal times of
    the node, which you can edit (see "Editing the signal timing of a node" on page 1487).
    1438

    PTVGROUP

    15.40.1 Displaying a network object in the Junction editor


    (5) The Views window
    Here you can select an object type. If you switch to another object type in the Views or Marking window, the schematic view and the list view will display the new object. The following
    views are provided:
    Node
    Main node
    Links
    Turn
    Main turns
    Geometry
    Signal times
    Turn volumes
    Note: The Node, Main node, Links, Turns, Main turns and Turn volumes views are
    available to all users, as they replace the former Edit node and Edit turn windows. The
    Geometry and Signal timing view are available with the Junction editor and control
    add-on (see "Displaying details on program and license" on page 886).
    (6) Window selection
    Via the list box, you can switch between all open windows.

    15.40.1 Displaying a network object in the Junction editor


    Switch to the Edit mode of the network object you want to display. In the network, doubleclick the node, main node, turn or main turn that you want to display in the Junction editor.
    The Junction editor window opens and displays the selected object.
    Notes: If you click the
    Arrange windows vertically icon, the Network editor window
    and the Junction editor are displayed next to each other. This way, you can switch to
    other nodes in the network and edit them directly in the Junction editor, as the view is
    instantly adjusted.
    You can enlarge or reduce the schematic view of the selected network object by clicking
    in the view and scrolling the mouse wheel.

    15.40.2 Switching to a different network object


    There are several possibilities to switch from the current network object to another network
    object:
    Select an object in the schematic view via the buttons
    Select an object type in the Views or Marking window
    Mark a new object in the network display
    In the schematic view, change from the partial nodes to main node and from turn to main
    turn.
    Note: If you switch to another network object, both the schematic view as well as the list
    view will be adjusted.
    PTVGROUP

    1439

    15.40.3 Adjusting the attribute selection in the Junction editor

    15.40.3 Adjusting the attribute selection in the Junction editor


    For the selected object type, you can edit the attribute selection in the list view of the Junction
    editor.
    Notes: You can specify a different attribute selection for each network object type. It will
    then apply to all objects of this type.
    1. In the tool bar of the Junction editor, click the

    Select attributes icon.

    The Attribute selection window opens.


    2. Make the desired settings (see "The window used for the selection of one attribute" on page
    963).
    3. Confirm with OK.
    The selected attributes and their values are displayed in the list in the specified order.
    Note: The selection is saved, even if you close the Junction editor in the meantime.

    15.40.4 Adjusting the display and the input options of the list view
    You can specify basic settings for all list views of the Junction editor.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the GUI> Junction editor page.
    3. Make the desired settings.
    Element

    Description

    Font for the Junction editor

    Select font
    Use the button to select a font, style and font size in a separate
    window for all list views.
    Note
    You can reset the font to the Visum standard setting (see "Resetting fonts" on page 828).

    Extended input
    options

    1440

    If the option has been selected, the input possibilities in list view
    change as follows:
    Logical values are activated/deactivated via buttons labeled
    with the selection. Green checkmarks and red crosses stand
    for activated/deactivated values, for example Auto link orientation.
    The values of a set can be edited in drop-down lists, for example Control type.
    Values of a set of which you can select multiple items, are dis-

    PTVGROUP

    15.40.5 Editing a node in the Junction editor


    Element

    Description
    played as buttons labeled with the current selection. They
    open a new window. In the window, you can select multiple
    items, for example TSysSet.
    Values for user-defined attributes of type File are displayed
    as button, which are labeled with the name of the selected
    file. The button opens the Open file window, where you can
    make a new selection.

    Row labels

    Here you can specify whether the attributes in the row headers
    are displayed as short names or as long names.
    Short name
    If the option has been selected, all attributes are displayed with
    their short names.
    Long name
    If the option has been selected, all attributes are displayed with
    their long names.

    4. Confirm with OK.


    The settings are applied.

    15.40.5 Editing a node in the Junction editor


    You can edit nodes in the schematic view and in the corresponding list below. In the Node
    view, you can, for example, edit the major flow.
    Notes: You can calculate ICA for nodes and add signal controls to signalized nodes (see
    "Editing the signal timing of a node" on page 1487 and "Calculating and exporting ICA"
    on page 1499).
    You can edit the geometry and the signal times of the displayed node (see "Editing the
    geometry of a node" on page 1475 and "Managing signal groups" on page 1473).
    15.40.5.1 Editing nodes in the schematic view
    Notes: A quick info is provided for all buttons of the schematic view, which describes the
    action triggered when clicking the button.
    1. In the network, double-click the node that you want to edit.
    The Junction editor opens and displays the selected node.

    PTVGROUP

    1441

    15.40.5.1 Editing nodes in the schematic view

    2. Make sure that in the Views window the Node view is selected.
    3. Make the desired changes.
    Note: If the node is part of a main node, you can switch to the view of the related main
    node.
    Specifying major flow and link orientations
    For nodes with 2 to 8 legs, you can specify a major flow, which describes the course of the priority flow. The major flow of a node can be set automatically or manually.
    Note: In the schematic view, the major flow is indicated by arrows.
    Make the desired changes to the schematic view of the node.
    Element

    Description

    Major flow
    manually

    If the option has been selected, the major flow can be set manually.
    Note
    Use the option to activate the colored buttons. In this view, you can set
    the major flow manually by clicking the button of the desired direction.
    If the option has not been selected, the major flow is set automatically.
    Note
    The major flow is determined by the user-defined rank per link type. The
    highest-ranking links which are connected to the node constitute the
    major flow.

    1442

    PTVGROUP

    15.40.5.2 Editing node attributes in the list view


    Notes: A major flow cannot refer twice to the same leg of a node or a main node.
    Adjacent one-way streets which point in opposite directions can be given the same orientation and thus be combined in one leg. The number of legs at a node thus depends
    on the directions allocated.
    15.40.5.2 Editing node attributes in the list view
    In the list view, each row describes a node property.
    Notes: You can edit the width of the rows and columns by dragging the mouse in the desired direction.
    You can edit the attribute selection of the list (see "Adjusting the attribute selection in the
    Junction editor" on page 1440).
    The context menu of the list is nearly identical to the context menu of the regular lists (see
    "Adjusting the column width to the contents" on page 2310).
    1. In the network, double-click the node that you want to edit.
    The Junction editor displays the selected node.

    2. Make the desired changes.


    Editing node attributes
    You can edit the editable attributes of the node in the list in different ways, depending on the
    attribute:
    Double-click the desired row and enter the new value.
    Perform an arithmetic operation for one or multiple values (see "Editing attribute values in
    the Quick view with arithmetic operations" on page 995)
    Select the desired value via a drop-down list
    Select/deselect an option per mouse click
    Note: The input options of the list view depend on the setting under Edit> User
    Preferences> entry GUI> Junction editor (see "Adjusting the display and the input options of the list view" on page 1440).
    PTVGROUP

    1443

    15.40.5.2 Editing node attributes in the list view


    You can, for example, display the following node attributes in the list view.

    1444

    Element

    Description

    Number

    Unique number of the node


    The nodes are numbered consecutively. You can overwrite the preset
    number with a number that does not yet exist in the network.
    Note
    If you edit the node number, existing assignment results will be deleted
    for all demand segments.

    Type number

    The node type (0...99) categorizes the node for the definition of turn standards (see "Managing turns" on page 1090).
    Note
    The standard type is 0.

    Code

    Code of the node

    Name

    Name of the node

    AddValue1 AddValue3

    Free attributes which you can use to enter additional values.


    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined attributes (see "Managing user-defined
    attributes" on page 973).

    Capacity PrT

    Allowed hourly PrT capacity of the node

    t0 PrT

    Private transport turning time in an unloaded network

    X-Coordinate
    Y-Coordinate
    Z-Coordinate

    Coordinates of the node in the network


    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).
    Tip
    You need Z-coordinates (height) for the 3D display in Vissim The elevation data are exported during an ANM export.

    Control type

    Use the drop-down list to select the control type of the node.
    Unknown
    Uncontrolled
    Two-way stop
    Two-way yield
    Signalized
    All-way stop
    Roundabout

    Use preset
    method for
    impedance at
    node

    If the option has been selected, the method set under attribute
    Method for impedances at node will be used.
    If the option has not been selected, the Standard method will be
    used that is set under the Calculate> General procedure settings>

    PTVGROUP

    15.40.5.2 Editing node attributes in the list view


    Element

    Description
    menu, PrT settings> Node impedances page (see "Selecting the
    method for node impedance calculation" on page 1911).

    Method for
    impedance at
    node

    You can use the list box to select a method for the impedance calculation of the displayed node, if the Use preset method for impedance at node option has been selected (see "Selecting the method for
    node impedance calculation" on page 1911).

    ICA sneakers

    Minimum number of vehicles in [veh/cycle], which make a successful left


    turn (right-hand traffic) or a successful right turn (left-hand traffic)
    Note
    One value applies to all movements at the node.

    ICA peak hour


    factor volume
    adjustment

    Factor for adjustment of the initial volume to the peak period


    Enter a value between 0.25 and 1.
    Note
    Volumes are multiplied by both node and turn adjustment factors.

    ICA is central
    business district

    Specify whether the main node lies within the CBD

    ICA use preset


    loss time

    If the option has been selected, the set ICA loss time is used.
    If the option has not been selected, the internally calculated value is
    used.

    ICA loss time

    For nodes with a signal group based control, to which no SCJ has been
    allocated, you can specify a user-defined loss time.

    Design volume

    Sum of the volumes of all turns in vehicles and car units

    Design volume
    capacity ratio
    PrT

    The definition of this value depends on the impedance calculation at the


    node.
    By default it equals the quotient of the total volume and the total capacity of the node, i.e. in each case the total of the respective values of all
    turns.

    Turn tCur mean Mean waiting time per car unit


    Turn tCur total

    Total of the wait times of all turns within the design time interval

    Turn tCur maxi- Maximum waiting time for a car unit


    mum
    Has automatic
    major flow

    PTVGROUP

    Calculated attribute which indicates whether a manual or an automatic


    major flow exists

    1445

    15.40.6 Editing a main node in the Junction editor


    Element

    Description

    SC

    Here you can edit the allocation of the node to a signal control.
    Tips
    The control type of the node must be signalized.
    You have to create a signal control, before you allocate a node to it (see
    "Creating a signal control" on page 1464).

    Main node

    Here you can edit the allocation of the node to a main node.

    The following attribute is only displayed, if a geometry template has been defined:
    Element

    Description

    Apply geometry
    template

    Here you can select a geometry template which shall be used for the
    node.
    Tip
    Geometry templates can be created in the Geometry view (see
    "Editing the geometry of a node" on page 1475).

    15.40.6 Editing a main node in the Junction editor


    You can edit main nodes in the schematic view and in the corresponding list below.
    Notes: You can calculate ICA for main nodes and add signal controls to signalized main
    nodes (see "Editing the signal timing of a node" on page 1487 and "Calculating and
    exporting ICA" on page 1499).
    You can edit the geometry and the signal times of the displayed main node (see "Editing
    the geometry of a node" on page 1475 and "Managing signal groups" on page 1473).
    15.40.6.1 Editing main nodes in the schematic view
    Note: A quick info is provided for all buttons of the schematic view, which describes the
    action triggered when clicking the button.
    1. In the network, double-click the main node that you want to edit.
    The Junction editor opens and displays the selected main node.
    2. Make sure that the Main node view is selected in the Views window.
    3. Make the desired changes.
    Specifying major flow and link orientations
    For each main node, you can specify a major flow, which describes the course of the priority
    flow. The major flow of a main node can be set automatically or manually. The option is described for nodes (see "Specifying major flow and link orientations" on page 1442).

    1446

    PTVGROUP

    15.40.6.2 Editing main node attributes in the list view


    15.40.6.2 Editing main node attributes in the list view
    In the list view, each column describes a main node and each row describes an attribute of
    this object.
    Notes: You can edit the width of the rows and columns by dragging the mouse in the desired direction.
    You can edit the attribute selection of the list (see "Adjusting the attribute selection in the
    Junction editor" on page 1440).
    The context menu of the list is nearly identical to the context menu of the regular lists (see
    "Adjusting the column width to the contents" on page 2310).
    1. In the network, double-click the main node that you want to edit.
    The Junction editor displays the selected main node.

    2. Make the desired changes.


    Editing main node attributes
    You can edit the editable attributes of the main node in the list in different ways, depending on
    the attribute:
    Double-click the desired row and enter the new value.
    Perform an arithmetic operation for one or multiple values (see "Editing attribute values in
    the Quick view with arithmetic operations" on page 995)
    Select the desired value via a drop-down list
    Select/deselect an option per mouse click
    Use buttons to select values in a separate window
    Note: The input options of the list view depend on the setting under Edit> User
    Preferences> entry GUI> Junction editor (see "Adjusting the display and the input options of the list view" on page 1440).
    You can, for example, display the following main node attributes in the list view:

    PTVGROUP

    1447

    15.40.6.2 Editing main node attributes in the list view


    Element

    Description

    Number

    Unique number of the main node


    The main nodes are numbered consecutively. You can overwrite the
    preset number with a number that does not yet exist in the network.
    Note
    If you edit the main node number, existing assignment results will be
    deleted for all demand segments.

    Type number

    The main node type categorizes the main node (0...99) for the definition of turn standards (see "Managing turns" on page 1090).
    The standard type is 0.

    Code

    Code of the main node

    Name

    Name of the main node

    AddValue1-AddVa- Free attributes which you can use to enter additional values.
    lue3
    Tip
    If you want to allocate additional information to a network object, you
    can also create user-defined main node attributes (see "Managing
    user-defined attributes" on page 973).

    1448

    Capacity PrT

    Allowed hourly PrT capacity of the main node

    t0 PrT

    Private transport turning time in an unloaded network

    X-Coordinate
    Y-Coordinate

    Coordinates of the centroid of the main node in the network


    The coordinates are assigned automatically according to the set coordinate system (see "Selecting a coordinate system" on page 2207).
    The label of a main node is always displayed at the position of its centroid.

    Control type

    Use the drop-down list to select the control type of the main node.
    Unknown
    Uncontrolled
    Two-way stop
    Two-way yield
    Signalized
    All-way stop
    Roundabout

    Use preset
    method for impedance at node

    If the option has been selected, the method set under attribute
    Method for impedances at node will be used.
    If the option has not been selected, the Standard method will be
    used that is set under the Calculate> General procedure settings>
    menu, PrT settings> Node impedances page (see "Selecting the
    method for node impedance calculation" on page 1911).

    PTVGROUP

    15.40.6.2 Editing main node attributes in the list view


    Element

    Description

    Method for impedance at node

    You can use the list box to select a method for the impedance calculation of the main node, if the Use preset method for impedance
    at node option has been selected (see "Selecting the method for
    node impedance calculation" on page 1911).

    ICA sneakers

    Minimum number of vehicles in [veh/cycle], which make a successful


    left turn (right-hand traffic) or a successful right turn (left-hand traffic)
    Note
    One value applies to all movements at the main node.

    ICA peak hour fac- Factor for adjustment of the initial volume to the peak period
    tor volume adjustment
    ICA is central busi- Specify if the main node lies within the CBD
    ness district
    ICA use preset
    loss time

    If the option has been selected, the set ICA loss time is used.
    If the option has not been selected, the internally calculated value
    is used.

    ICA loss time

    For main nodes with a signal group based control, to which no SCJ
    has been allocated, you can specify a user-defined loss time.

    Design volume

    Sum of the volumes of all turns in vehicles and car units

    Design volume
    The definition of this value depends on the impedance calculation at
    capacity ratio PrT the node.
    By default it equals the quotient of the total volume and the total capacity of the main node, i.e. in each case the total of the respective
    values of all turns.
    Turn tCur mean

    Mean waiting time per car unit

    Turn tCur total

    Total of the wait times of all turns within the design time interval

    Turn tCur maximum

    Maximum waiting time for a car unit

    Has automatic
    major flow

    Calculated attribute which indicates whether a manual or an automatic major flow exists at the main node

    PTVGROUP

    1449

    15.40.7 Editing turns in the Junction editor


    Element

    Description

    SC

    Here you can edit the allocation of the main node to a signal control.
    Tip
    You have to create a signal control before you allocate a main node
    to it (see "Creating a signal control" on page 1464).

    Partial nodes

    Use these buttons to allocate or remove partial nodes to the main


    node in a separate window.
    Notes
    A node can only be allocated to a one main node.
    If you edit the allocation of partial nodes, other cordon links may
    evolve (see "Effects of cordon link changes" on page 1187) and existing PrT assignment results will be deleted.
    Tips
    You can also allocate nodes to main nodes as follows:

    In the node list (column Main node number)


    Via the Main node number attribute for several nodes (see
    "Editing attribute values of network objects" on page 983)
    In the Edit> Recalculate node allocation from polygons menu
    (see "Allocating nodes to one or multiple main nodes" on page
    1181)
    The following attribute is only displayed, if a geometry template has been defined:
    Element

    Description

    Apply geometry
    template

    Here you can select a geometry template which shall be used for the
    main node.
    Tip
    Geometry templates can be created in the Geometry view (see
    "Editing the geometry of a node" on page 1475).

    15.40.7 Editing turns in the Junction editor


    In the turn view of the Junction editor, you can edit the attribute values of all turns at a node.
    You can edit turns in the schematic view and in the corresponding list below.
    15.40.7.1 Editing turns in the schematic view
    Notes: A quick info is provided for all buttons of the schematic view, which describes the
    action triggered when clicking the button.
    Turns of links which are closed in both directions are displayed as dashed lines in the
    Junction editor, if you select the Show also turns of closed links option in the context
    menu of the list view.
    1. In the network select the node whose turns you want to edit.

    1450

    PTVGROUP

    15.40.7.1 Editing turns in the schematic view


    The Junction editor opens and displays the selected node.

    2. In the Views window, select the Turns view.


    3. Make the desired changes.
    Note: If the turn belongs to the partial node of a main node, you can switch to the view of
    the related main node view via a link.
    Marking a link
    You can mark individual links in the schematic view via the colored buttons next to the links.
    Click the desired button.
    The Junction editor displays all turns of the link at this node and the buttons for the turns.
    Marking a turn
    As soon as you have marked a link in the schematic view, the buttons for the turns will be displayed. Use the button for turns to mark the individual turns of the node in the schematic view.
    1. Click the button of the desired turn.
    The turn is indicated by a red arrow and marked in the list view.

    PTVGROUP

    1451

    15.40.7.2 Editing main node attributes in the list view


    Note: You can edit the attributes of the marked turn right in the list.
    2. If required, select further turns.
    Note: You can remove markings if you click the button of the respective turn again.
    15.40.7.2 Editing main node attributes in the list view
    In the list view, each column describes a turn and each row describes an attribute of this
    object.
    Notes: You can edit the width of the rows and columns by dragging the mouse in the desired direction.
    You can edit the attribute selection of the list (see "Adjusting the attribute selection in the
    Junction editor" on page 1440).
    The context menu of the list is nearly identical to the context menu of the regular lists (see
    "Adjusting the column width to the contents" on page 2310).
    1. In the network select the node whose turns you want to edit.
    The Junction editor opens and displays the selected node.
    2. In the Views window, select the Turns view.
    The Junction editor displays the node and all turns belonging to this node.
    3. Make the desired changes.
    Editing turn attributes
    You can edit the editable attributes of the turn in the list in different ways, depending on the
    attribute:
    Double-click the desired row and enter the new value.
    Perform an arithmetic operation for one or multiple values (see "Editing attribute values in
    the Quick view with arithmetic operations" on page 995)
    Select the desired value via a drop-down list
    Select/deselect an option per mouse click
    Use buttons to select values in a separate window
    Note: The input options of the list view depend on the setting under Edit> User
    Preferences> entry GUI> Junction editor (see "Adjusting the display and the input options of the list view" on page 1440).
    You can, for example, display the following turn attributes in the list view:

    1452

    PTVGROUP

    15.40.7.2 Editing main node attributes in the list view


    Element

    Description

    From node number

    Display of the From node number of the turn

    From link Number Display of the From link number of the turn
    From link\To node Display of the To node orientation of the From link of the turn
    orientation
    To link Number

    Display of the To link number of the turn

    To link\To node
    number

    Display of the To node number of the To link of the turn

    To node number

    Display of the To node number of the turn

    Type number

    A click in the cell opens the drop-down list. Use the drop-down list to
    specify the turn type.
    Notes
    The value range is 0 to 9.
    You can edit the values in menu Network> Turn standards (see
    "Managing turn standards" on page 1090).

    TSys set

    Use the button to select one or more transport systems for the turn in
    a separate window.
    Tip
    In the TSysSet window, use the C TRL key to select several transport
    systems.

    Capacity PrT

    Enter a PrT capacity

    Volume PrT

    Display of the volume of the turn of all PrT vehicles

    tCur_PrTSys

    Display of the in-vehicle time in the loaded network

    AddValue 1-3

    Free attributes to which you can allocate values

    Closing turns
    Use the context menu of the list view to close individual turns.
    1. In the list, right-click the column of the turn that you want to close.
    A shortcut menu opens.
    2. Select the Close entry.
    The turn is closed and, in the schematic view, illustrated as a dashed line.
    Note: Closed turns are only displayed, if you have selected the Show also closed turns
    option (see "Displaying:closed turns" on page 1453).
    Displaying:closed turns
    In the list view, you can either show or hide closed turns.

    PTVGROUP

    1453

    15.40.8 Editing main turns in the Junction editor


    1. In the list, right-click the header of a column. Alternatively, you can right-click in the empty
    section of the table.
    A shortcut menu opens.
    2. Select the Show also closed turns entry.
    All closed turns of the node are displayed in the list.
    Displaying turns of closed links
    In the list view, you can either show or hide turns of closed links.
    1. In the list, right-click the header of a column. Alternatively, you can right-click in the empty
    section of the table.
    A shortcut menu opens.
    2. Select the Show also turns of blocked links entry.
    All turns of closed links are displayed in the list.
    Copying attributes to the reverse direction
    You can copy the attributes of a turn to the reverse direction.
    1. In the list, right-click the column of the turn whose attributes you want to copy.
    A shortcut menu opens.
    2. Select the Copy attributes to reverse direction entry.
    The attribute values are copied.
    Note: Display the reverse direction of the selected turn by using the Mark reverse direction entry (see "Marking the reverse direction" on page 1454).
    Marking the reverse direction
    1. Right-click the column of the desired turn.
    A shortcut menu opens.
    2. Select the Mark reverse direction entry.
    The turn which represents the reverse direction is marked in the schematic view and in the list.

    15.40.8 Editing main turns in the Junction editor


    In the main turn view of the Junction editor, you can edit the attribute values of all main turns at
    a main node. You can edit main turns in the schematic view and in the corresponding list
    below.

    1454

    PTVGROUP

    15.40.8.1 Displaying main turns in the schematic view


    15.40.8.1 Displaying main turns in the schematic view
    Notes: A quick info is provided for all buttons of the schematic view, which describes the
    action triggered when clicking the button.
    Main turns of links which are closed in both directions are displayed as dashed lines in
    the Junction editor, if you select the Show also turns of closed links option in the context
    menu of the list view.
    1. In the network, select the main turn that you want to edit (see "Selecting main turns" on
    page 1189).
    The Junction editor opens. In the Views window the Main turns button is selected. In the
    upper section of the view a schematic view of the main node is displayed. Below you see a
    list of all main turns of the main node.

    2. Click one of the small Mark link buttons that are displayed next to the links.
    All main turns of the link on this main node and the Mark turn buttons are displayed for this
    main turn.
    3. Click the button of the desired main turns.
    The turn is indicated by a red arrow and marked in the list view.
    4. If required, select further main turns.
    Note: You can remove markings if you click the checkbox of the respective turn again.

    PTVGROUP

    1455

    15.40.8.2 Editing main turn attributes in the list view


    15.40.8.2 Editing main turn attributes in the list view
    In the list view, each column describes a main turn and each row describes an attribute of this
    object.
    Notes: You can edit the attribute selection of the list (see "Adjusting the attribute selection
    in the Junction editor" on page 1440).
    The context menu of the list is nearly identical to the context menu of the regular lists (see
    "Adjusting the column width to the contents" on page 2310).
    1. In the network select the main node whose main turns you want to edit (see "Selecting main
    turns" on page 1189).
    The Junction editor opens and displays the selected main node.
    2. In the Views window, select the Main turns view.
    The Junction editor displays the main node and all related main turns of this main node.
    3. Make the desired changes.
    Editing main turn attributes
    You can edit the editable attributes of the main turn in the list in different ways, depending on
    the attribute:
    Double-click the desired row and enter the new value.
    Perform an arithmetic operation for one or multiple values (see "Editing attribute values in
    the Quick view with arithmetic operations" on page 995)
    Select the desired value via a drop-down list
    Select/deselect an option per mouse click
    Use buttons to select values in a separate window
    Note: The input options of the list view depend on the setting under Edit> User
    Preferences> entry GUI> Junction editor (see "Adjusting the display and the input options of the list view" on page 1440).
    You can, for example, display the following main turn attributes in the list view.

    1456

    Element

    Description

    From node number

    Display of the From Node Number of the main turn

    From Cordon
    Node Number

    Display of the From Cordon Node Number of the main turn

    To node number

    Display of the To node number of the main turn

    To cordon node
    number

    Display of the To cordon node number of the main turn

    PTVGROUP

    15.40.8.2 Editing main turn attributes in the list view


    Element

    Description

    From link number

    Display of the From link number of the main turn

    To link Number

    Display of the To link number of the main turn

    Orientation

    Display of the orientation of the main turn (From-To)


    Note
    You can edit the orientation if the Auto link orientation in the Link
    view has not been selected.

    Type number

    A click in the cell opens the drop-down list. Use the drop-down list to
    specify the main turn type.
    Notes
    The value range is 0 to 9.
    You can edit the values in menu Network> Turn standards (see
    "Managing turn standards" on page 1090).

    TSys set

    Use the button to select one or more transport systems for the main
    turn in a separate window.
    Tip
    In the TSysSet window, use the C TRL key to select several transport
    systems.

    Capacity PrT

    Enter a PrT capacity

    Volume PrT

    Display of the volume of the main turn of all PrT vehicles

    AddValue 1-3

    Free attributes to which you can allocate values

    Closing main turns


    Use the context menu of the list view to close individual main turns.
    1. In the list, right-click the column of the main turn that you want to close.
    A context menu opens.
    2. Select the Close entry.
    The main turn is closed.
    Displaying closed main turns
    In the list view, you can either show or hide closed main turns.
    1. In the list, right-click the header of a column. Alternatively, you can right-click in the empty
    section of the table.
    A context menu opens.
    2. Select the Show also closed turns entry.
    All closed main turns of the main node are displayed in the list.

    PTVGROUP

    1457

    15.40.9 Editing links in the Junction editor


    Displaying main turns of closed links
    In the list view, you can either show or hide main turns of closed links.
    1. In the list, right-click the header of a column. Alternatively, you can right-click in the empty
    section of the table.
    A context menu opens.
    2. Select the Show also turns of blocked links entry.
    All main turns of closed links are displayed in the list.
    Marking the reverse direction
    1. Right-click the column of the desired main turn.
    A context menu opens.
    2. Select the Mark reverse direction entry.
    The main turn which represents the reverse direction is marked in the schematic view and in
    the list.

    15.40.9 Editing links in the Junction editor


    In the links view, you can edit the attributes of all approach links of the selected node, such as
    the number of lanes or the geographic orientation.
    You can edit links in the schematic view and in the corresponding list below. In the Links view,
    you can, for example, edit the Auto link orientation attribute of the selected node or main
    node.
    15.40.9.1 Editing links in the schematic view
    Notes: A quick info is provided for all buttons of the schematic view, which describes the
    action triggered when clicking the button.
    Links which are closed in both directions are displayed as dashed lines in the Junction
    editor, if you select the Show also closed links option in the context menu of the list view.
    One-way roads are displayed as arrows.
    1. In the network, double-click the node whose links you want to edit.
    The Junction editor opens and displays the selected node.
    2. Make sure that the Links view is selected in the Views window.
    The Junction editor displays all approach links of the selected node.

    1458

    PTVGROUP

    15.40.9.1 Editing links in the schematic view

    3. Make the desired changes.


    Specifying link orientations
    For each link, an orientation can be specified. The orientation of a link can be set automatically
    or manually.
    Make the desired changes in the schematic Links view.
    Element

    Description

    Auto link orientation

    If the option has been selected, the link orientations are set
    automatically with default values, depending on the setting under
    Network > Network settings > Network objects > Link orientations (see "Specifying the number of link orientations" on
    page 1103).
    If the option has not been selected, you can edit the orientation
    of each link of the selected node. Next to each link, a drop-down
    list will then be displayed, in which you can select the desired orientation. The selection depends on the setting under Network >
    Network settings > Network objects > Link orientations (see
    "Specifying the number of link orientations" on page 1103).
    Tip
    Adjacent one-way streets which point in opposite directions can
    be given the same orientation and thus be combined in one leg.

    1. In the schematic view, click the Apply link orientations button.


    The changed link orientations are applied.

    PTVGROUP

    1459

    15.40.9.2 Editing link attributes in the list view


    Notes: In the Node list, the Auto link orientation attribute indicates whether the link orientations have been changed manually: 1=automatic, 0=manual.
    In the Links list, the attributes From node orientation, From main node orientation, To
    node orientation and To main node orientation indicate the location in the network, for
    example W, E, or NW. You can edit these attributes.
    Based on the link orientations, the calculated direction is displayed in list type Turns and
    Main turns via the Orientation attribute, for example WW (=from the West to the West).
    Marking a link
    You can mark individual links in the schematic view via the colored buttons next to the links.
    1. Click the desired button.
    The selected link is marked in the list view.
    Note: You can edit the attributes of the marked link right in the list.
    2. If required, select further links.
    Note: You can remove markings if you click the button of the respective turn again.
    15.40.9.2 Editing link attributes in the list view
    In the list view, each column describes a link and each row describes an attribute of this
    object.
    Notes: You can edit the width of the rows and columns by dragging the mouse in the desired direction.
    You can edit the attribute selection of the list (see "Adjusting the attribute selection in the
    Junction editor" on page 1440).
    The context menu of the list is nearly identical to the context menu of the regular lists (see
    "Adjusting the column width to the contents" on page 2310).
    1. In the network, double-click the node whose links you want to edit.
    The Junction editor opens and displays the selected node.
    2. Make sure that the Links view is selected in the Views window.
    The list view displays all links of the selected node.

    1460

    PTVGROUP

    15.40.9.2 Editing link attributes in the list view


    3. Make the desired changes.
    Editing link attributes
    You can edit the editable attributes of the links in the list in different ways, depending on the
    attribute:
    Double-click the desired row and enter the new value.
    Perform an arithmetic operation for one or multiple values (see "Editing attribute values in
    the Quick view with arithmetic operations" on page 995)
    Select the desired value via a drop-down list
    Select/deselect an option per mouse click
    Use buttons to select values in a separate window
    Tip: You can also edit the attributes of the respective link in the Edit link window. The window of the currently selected link is called via the Edit entry in the context menu.
    The input options of the list view depend on the setting under Edit> User Preferences>
    entry GUI> Junction editor (see "Adjusting the display and the input options of the list
    view" on page 1440).
    You can, for example, display the following link attributes in the list view:
    Element

    Description

    Number

    Unique number of the link


    The links are numbered consecutively. The preset number can be
    overwritten by a number which has not yet been assigned in the network.
    Note
    The number is identical for both directions of the link.

    Name

    Name of the link

    From node number

    Display of the number of the node at which the link starts

    To node number

    Display of the number of the node at which the link ends

    Type number

    A click in the cell opens the drop-down list. Use the drop-down list to
    specify the link type.
    Note
    The value range is 00 to 99 (see "Specifying link types" on page
    1099).

    TSys set

    Use the button to select one or more transport systems for the link in
    a separate window.
    Tip
    In the TSysSet window, use the C TRL key to select several transport
    systems.

    PTVGROUP

    1461

    15.40.9.2 Editing link attributes in the list view


    Element

    Description

    Number of lanes

    Enter the number of lanes of the link

    Capacity PrT

    Capacity of the link in car units

    v0 PrT

    Enter the PrT speed on the link in an unloaded network

    Volume PrT

    Display of the volume of the link of all PrT PCUs

    Editing TModel attributes


    In addition to the node and turn attributes, which are considered in the calculation (capacity, t0
    and type), you can mark one or several of the incoming links as special links with an extra turn
    penalty.
    Turns whose From links are marked as special links, receive a particular turn penalty. For all
    others, the turn-specific time is the penalty.
    Element

    Description

    TModel delay link


    for turns

    Enter value 0 or 1
    Notes
    A turn whose From link has the value 0, only gets t0/tCur according
    to the turn VD function.
    A turn whose From link has the value 1, also gets a t0/tCur according
    to the node VD function in addition to the t0/tCur according to the
    turn VD function.
    If the attribute has the value 0 on all incoming links of a node, the
    node is treated as if the value of all incoming links was 1.

    TModel delay link


    for main turns

    Enter value 0 or 1
    Notes
    A main turn whose From link has the value 0, only gets t0/tCur according to the turn VD function.
    A main turn whose From link has the value 1, also gets a t0/tCur
    according to the turn VD function in addition to the t0/tCur according
    to the node VD function.

    Note: For nodes of the control type All-way stop, special links with turn penalties are not
    used. The same penalty applies to all turns.
    Examples
    Two-way stop node
    Use special links to assign a turn penalty to minor turns.
    Signalized node
    You can model the node with or without special links:
    Without special links, only the turn-specific time is assigned to the turns which have the
    right of way.
    1462

    PTVGROUP

    15.40.10 Managing signal controls


    With special links, you assign the same penalty to the turns which have the right of way
    as to minor turns (=turn penalty).
    Note: You cannot specify different penalties for minor and major turns.
    Copying attributes to the reverse direction
    You can copy the attributes of a link to the reverse direction.
    1. In the list, right-click the column of the link whose attributes you want to copy.
    A context menu opens.
    2. Select the Copy attributes to reverse direction entry.
    The attribute values are copied.
    Displaying closed links
    In the list view, you can either hide or show closed links.
    1. In the list, right-click the header of a column. Alternatively, you can right-click in the empty
    section of the table.
    A context menu opens.
    2. Select the Show also closed links entry.
    The closed links of the node are displayed in the list.
    Switching on/off the label of a link
    You can individually switch on/off the bar label of each link (see "Switching on/off the bar label
    of a link" on page 1121).
    1. Right-click the column of the desired link.
    A context menu opens.
    2. Select the Switch bar label on/off entry.
    The bar label of the selected link is switched off, if it was switched on before. It is switched on,
    if it was switched off before.

    15.40.10 Managing signal controls


    Note: The feature for managing signal controls is only available, if the Junction editor
    and control add-on is activated (see "Enabling or disabling installed add-ons" on page
    886).
    A signal control (SC) describes the total of all signal control data at one or more nodes or main
    nodes. There are four types of signal controls: signal-group based signal controls, stagebased signal controls, RBC and externally managed signal controls (see Fundamentals: Chpt.
    3.1.21.3 , page 92).

    PTVGROUP

    1463

    15.40.10.1 Creating a signal control


    15.40.10.1 Creating a signal control
    Creating a signal control in the overview
    1. In the Network menu, select the SC entry.
    The SC window opens.
    2. Click the

    Create button.

    The Create SC window opens.


    3. Make the desired settings (see "Properties and options of signal controls" on page 1465).
    4. Confirm with OK.
    The signal control is inserted.
    Inserting a signal control at a (main) node
    Note: You can allocate just one signal control to a node or main node each; a signal control, however, can be allocated to several nodes or main nodes (see "Editing node attributes" on page 1443).
    1. Open the desired (main) node in the Junction editor (see "Displaying a network object in
    the Junction editor" on page 1439).
    Note: The signal control will only be allocated to the (main) node, if no other signal
    control is allocated to the it.
    2. In the toolbar of the Junction editor, click the

    Create SC icon.

    The Create SC window opens.


    3. Make the desired settings (see "Properties and options of signal controls" on page 1465).
    4. Confirm with OK.
    The signal control is created and allocated to the displayed node or main node. Together with
    the signal control, all possible crosswalks are automatically inserted, as long as none exist yet.

    1464

    PTVGROUP

    15.40.10.2 Properties and options of signal controls


    15.40.10.2 Properties and options of signal controls

    In the Create SC or Edit SC window, you can edit the properties and options of a signal control.
    Signal controls: Basis tab
    Element

    Description

    Number

    Unique number of the signal control


    The signal controls are numbered consecutively. The preset number can
    be overwritten by a number which has not yet been assigned in the network.

    Code

    Code of the signal control


    Note
    The option is not provided if you have selected the signal control type
    RBC.

    Name

    Name of the signal control


    Note
    The option is not provided if you have selected the signal control type
    RBC.

    Cycle time

    Duration of the cycle time in seconds


    Note
    The option is not provided if you have selected the signal control type
    RBC.

    PTVGROUP

    1465

    15.40.10.2 Properties and options of signal controls


    Element

    Description

    Signal control Use the drop-down list do specify the control type of the signal control.
    type
    Signal group-based
    The control of the SC is based on signal groups.
    Stage-based
    The control of the SC is based on stages to which signal groups are
    allocated.
    Vissig
    The control of the SC is edited with the external Vissig program(see
    "Editing a signal control in Vissig" on page 2528).
    Notes
    This type is only available with the Vissig add-on.
    The External tab provides further information on the external control.
    RBC
    The control of the SC is edited with the RBC editor (see "Editing a
    signal control of the RBC type" on page 1470).
    Note
    This type is only available with the RBC controllers add-on.
    Note
    With this list you cannot convert an internal control into an external control
    (see "Converting an existing Visum-internal signal control for Vissig" on
    page 2529).
    Switched off

    If the option has been selected, the signal control is currently switched off.

    Signal controls: Node tab


    Element

    Description

    Allocated nodes

    The list displays all nodes that are allocated to the signal control.

    Free nodes

    The list displays all nodes that are not allocated to the signal control.
    Note
    You can only allocate nodes to a signal control which are not yet allocated to a signal control. To remove an allocation, you have to
    access and edit the signal control of the desired node in the Junction
    editor (see "Editing signal a control in the Junction editor" on page
    1470).
    Use the button to allocate the nodes selected on the right to the
    signal control.
    Use the button to remove the nodes selected on the left from the
    signal control.

    Signal controls: Main node tab


    Note: This tab is only displayed if the network contains main nodes.

    1466

    PTVGROUP

    15.40.10.2 Properties and options of signal controls


    Element

    Description

    Allocated main
    nodes

    The list displays all main nodes that are allocated to the signal control.

    Free main nodes

    The list displays all main nodes that are not allocated to the signal
    control.
    Note
    You can only allocate main nodes to a signal control which are not
    yet allocated to a signal control. To remove an allocation, you have to
    access and edit the signal control of the desired main node in the
    Junction editor (see "Editing signal a control in the Junction editor"
    on page 1470).
    Use the button to allocate the main nodes selected on the right to the
    signal control.
    Use the button to remove the main nodes selected on the left from
    the signal control.

    Signal controls: Optimization tab


    Element

    Description

    Optimization
    method

    Use the drop-down list to specify whether and how you want to execute a signal cycle and split optimization the SC (see Fundamentals:
    Chpt. 6.5.4 , page 298).
    None
    No optimization method is used.
    Green time
    Only the green time (signal split) is optimized.
    Cycle time and green time
    The signal cycle and split (green time) are optimized.
    Note
    The option is not provided if you have selected the signal control type
    RBC.

    Minimum cycle
    time

    Minimum cycle time in seconds


    Note
    The option is not provided if you have selected the signal control type
    RBC.

    Maximum cycle
    time

    Maximum cycle time in seconds


    Note
    The option is not provided if you have selected the signal control type
    RBC.

    Used intergreen
    method

    Use the drop-down list to specify the desired intergreen method for
    the optimization.

    PTVGROUP

    1467

    15.40.10.2 Properties and options of signal controls


    Element

    Description
    Intergreen matrix
    If this option has been selected, the intergreen matrix will be
    used for optimization (Intergreens button).
    Amber and allred
    If this option has been selected, the amber and allred time will be
    used for optimization.
    Note
    The option is not provided if you have selected the signal control type
    Vissig.

    Intergreens

    The button opens a window with a matrix in which you can specify
    the intergreens of the signal groups.
    Note
    The option is not provided if you have selected the signal control type
    Vissig.

    Standard intergreen

    Intergreen in seconds which is used for optimization if the intergreen


    matrix is empty (see "Optimizing signal cycle and split times for active
    nodes" on page 1921)
    Note
    The option is not provided if you have selected the signal control type
    Vissig.

    Level of Service

    Level of Service of the SC


    Note
    This value is calculated during the optimization (see "Signal timing
    optimization and coordination" on page 1921).

    Level of Service mean wait time

    Mean wait time of a vehicle in seconds


    Note
    This value is calculated during the optimization (see "Signal timing
    optimization and coordination" on page 1921).

    Signal controls: Coordination tab


    Element

    Description

    Coordination
    group number

    Number of the coordination group the signal control is allocated to.


    (see "Managing signal coordination groups" on page 1497)

    Is reference signal If this options is selected, the SC is the reference SC for the opticontrol
    mization of the offset of a signal coordination group. After the offset
    optimization this SC has the offset 0. If there are several reference
    SCs in a signal coordination group, the SC with the smallest number
    is the reference SC.
    Time offset

    1468

    Time offset for the begin of the cycle in seconds

    PTVGROUP

    15.40.10.3 Editing the attribute values of a signal control


    Signal controls: External tab
    Note: This tab is only provided for external signal controls.
    Element

    Description

    File name

    Use the button to select the file with the external signal control data.

    Signal program
    number

    Use the drop-down list to select the signal program.


    Notes
    You can also change the signal program in the Junction editor (see
    "Switching off or manually changing signal programs in Visum" on
    page 2558) or set it automatically in the procedure sequence (see
    "Adding procedures to the procedure sequence" on page 1848).
    The procedures ICA assignment, signal offset optimization and cycle
    and green time optimization use the currently selected signal program.

    15.40.10.3 Editing the attribute values of a signal control


    Note: Edit the control data of a signal control with an external controller in the corresponding external Vissig program (see "Editing the external control of a signal control"
    on page 1471).
    Editing a signal control in the overview
    1. In the Network menu, select the SC entry.
    The SC window opens.
    2. Select the desired signal control.
    3. Click the

    Edit button.

    The Edit SC window opens.


    Note: In case of signal controls with an external control, the data will be reloaded from
    file (External tab) when opening the window.
    4. Make the desired settings (see "Properties and options of signal controls" on page 1465).
    Note: If you want to change an allocation between a (main) node and a signal control,
    you need to specify the settings in the Junction editor (see "Editing signal a control in
    the Junction editor" on page 1470).
    5. Confirm with OK.
    The changes are saved.
    Tip: Alternatively, you can edit the attributes directly in the list of signal controls.

    PTVGROUP

    1469

    15.40.10.4 Editing a signal control of the RBC type


    Editing signal a control in the Junction editor
    1. Open the desired (main) node in the Junction editor (see "Displaying a network object in
    the Junction editor" on page 1439).
    2. In the toolbar of the Junction editor, click the

    Edit SC icon.

    The Edit SC window opens.


    Note: In case of signal controls with an external control, the data will be reloaded from
    file (External tab) when opening the window.
    3. Make the desired settings (see "Properties and options of signal controls" on page 1465).
    4. Confirm with OK.
    The changes are saved.
    15.40.10.4 Editing a signal control of the RBC type
    Note: This function is only provided with the RBC controllers add-on (see "Enabling or
    disabling installed add-ons" on page 886).
    If a signal control has the control type RBC, you edit the control data in a special editor. The
    editor is described in the separate documentation Manual_ RBC.pdf which is stored in the
    ...\PTV Visum 13\Doc\... subfolder of your installation folder.
    1. Open the desired (main) node in the Junction editor (see "Displaying a network object in
    the Junction editor" on page 1439).
    2. In the toolbar of the Junction editor, click the

    Edit RBC controller icon.

    The RBC editor opens in which you can edit the control.
    Switching off or manually changing signal programs in Visum
    In Visum, just one signal program is allocated to a signal control. If in RBC a signal control
    includes several signal programs then only the currently allocated signal program will be displayed in the junction editor. You can switch to another signal program or switch the signal
    control off.
    1. Open the Signal timing view of the Junction editor (see "Using the Junction editor" on page
    1435).
    2. In the Signal program drop-down list in the top right corner, select the desired signal program.
    The signal program is changed. The signal timing is displayed in the lower section of the junction editor. The currently selected signal program is taken into account by the concerned procedures, i.e. assignment with ICA, signal cycle and split optimization and signal offset
    optimization.

    1470

    PTVGROUP

    15.40.10.5 Editing the external control of a signal control


    Automatically changing or switching off signal programs in Visum
    In the Visum procedure sequence you can automatically change the signal programs of RBC
    controllers. Hereby Visum uses the desired time of day to identify the number of the corresponding signal program. For RBC controllers, the number of the daily signal program list to
    be used will be ignored. Visum then converts all signal controls to the signal program which
    applies for that time. If no signal program exists for the chosen time, the signal control will be
    switched off.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Select the desired position in the procedure sequence and add the procedure Set signal
    programs from the Assignments category.
    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Set signal programs window opens.

    4. Make the desired changes.


    Element

    Description

    Reset the signal programs of external controls to the signal program that is active at
    the following time

    Time to be set for all external controllers

    Number of the daily signal program list to


    be used

    RBC does not regard this setting.

    Note: These settings apply to Vissig controllers, too.


    5. Confirm with OK.
    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The signal programs are changed. The currently selected signal programs are taken into
    account by the concerned procedures, i.e. assignment with ICA, signal cycle and split optimization and signal offset optimization.
    15.40.10.5 Editing the external control of a signal control
    If a signal control has the control type Vissig, you edit the control data in an external program.
    PTVGROUP

    1471

    15.40.10.6 Deleting a signal control


    Opening external control data from the overview
    1. In the Network menu, select the SC entry.
    The SC window opens.
    2. Select the desired signal control.
    3. Click the Edit external data button.
    A query opens.
    4. Confirm the query with Continue.
    The external program opens in which you can edit the control (see "Editing a signal control in
    Vissig" on page 2528).
    Opening external control data in the Junction editor
    1. Open the desired (main) node in the Junction editor (see "Displaying a network object in
    the Junction editor" on page 1439).
    2. In the toolbar of the Junction editor, click the

    Edit Vissig controller icon.

    The external program opens in which you can edit the control (see "Editing a signal control in
    Vissig" on page 2528).
    15.40.10.6 Deleting a signal control
    Deleting signal controls in the overview
    1. In the Network menu, select the SC entry.
    The SC window opens.
    2. Select the desired signal controls.
    3. Click the

    Delete button.

    The signal controls are removed from the list.


    4. Confirm with OK.
    The signal controls are deleted.
    Tip: Alternatively, you can click the Delete entry in the context menu of the list of the
    signal controls.
    Deleting a signal control in the Junction editor
    You can delete a signal control that is allocated to a (main) node in the Junction editor.
    1. Open the desired (main) node in the Junction editor (see "Displaying a network object in
    the Junction editor" on page 1439).
    2. Click the

    1472

    Delete SC icon.

    PTVGROUP

    15.40.11 Managing signal groups


    A query opens.
    3. Confirm the query with OK.
    The signal control is deleted.

    15.40.11 Managing signal groups


    Note: This functionality is only available, while the Junction editor and control add-on is
    active (see "Enabling or disabling installed add-ons" on page 886).
    You can create signal groups for signal group-based and stage-based signal controls (see
    Fundamentals: Chpt. 3.1.21.3 , page 92).
    Note: A stage-based signal control needs to have at least one stage, so that a signal
    group can be allocated to it.
    Tip: You can edit signal groups in the respective list under Lists (see "Opening a list" on
    page 2299).
    15.40.11.1 Creating a signal group
    1. Open the desired (main) node in the Junction editor.
    2. Make sure that a signal control has been allocated to the node or main node (see "Creating
    a signal control" on page 1464).

    Note: If a signal control has been allocated, the

    Delete SC icon is active.

    3. In the Views window, select the Signal timing view.


    4. In the toolbar of the Junction editor, click the

    Create signal group icon.

    The Create signal group window opens.


    5. Make the desired settings (see "Properties and options of signal groups" on page 1474).
    6. Confirm with OK.
    The signal group is inserted and displayed in the lower child window of the Junction editor.
    7. Create further signal groups, if required.

    PTVGROUP

    1473

    15.40.11.2 Properties and options of signal groups


    15.40.11.2 Properties and options of signal groups

    1474

    Element

    Description

    Number

    Unique number of the signal group


    The signal groups are numbered consecutively. The preset number
    can be overwritten by a number which has not yet been assigned in
    the network.

    Name

    Name of the signal group

    Green time start

    If you create a signal group for a signal group-based signal control,


    you enter here the green time start in seconds.
    If you create a signal group for a stage-based SC, this field is disabled. The green time start of the selected stage is used.

    Green time end

    If you create a signal group for a signal group-based signal control,


    you enter here the green time end in seconds.
    If you create a signal group for a stage-based SC, this field is disabled. The green time end of the selected stage is used.

    Minimum green
    time

    Enter the minimum green time in seconds.


    Note
    The value takes effect during green time optimization (see "Optimizing signal cycles and split of a single signal control" on page
    1501).

    Amber

    Enter the amber time in seconds.

    Allred

    Enter the Allred time in seconds.


    Note
    Time after the amber time of a signal group, in which no other signal
    group can have a green light.

    Stages

    If you create a signal group for a stage-based SC, you have to allocate one or several stages to the signal group.
    Note
    The signal group must be allocated to at least one stage.

    PTVGROUP

    15.40.11.3 Deleting a signal group


    15.40.11.3 Deleting a signal group
    1. Make sure that the Signal timing view is selected in the Views window.
    2. In the lower window of the Junction editor, right-click the bar of the signal group that you
    want to delete.
    A shortcut menu opens.
    3. Select the Delete signal group entry.
    The signal group is deleted.
    Tip: Alternatively, you can delete the desired signal group in the Signal times view, by
    marking the associated column and selecting the Delete entry in the context menu.

    15.40.12 Editing the geometry of a node


    Note: This functionality is only available, while the Junction editor and control add-on is
    active (see "Enabling or disabling installed add-ons" on page 886).
    If you select the Geometry view in the Views window, you can edit the following objects of the
    displayed node or main node in the schematic view and in the corresponding list below:
    Legs
    Lanes
    Lane turns
    Crosswalks
    Signal groups
    Detectors
    Stages
    Note: The objects Signal groups and Stages are only displayed, if signal groups or stages have been inserted.
    15.40.12.1 Editing the geometry in the schematic view
    In the schematic view, you can, for example, create or delete lane pockets.
    1. In the network, double-click the node or main node that you want to edit.
    The Junction editor opens and displays the selected node or main node.
    2. Make sure that the Geometry view is selected in the Views window.
    The node is displayed in the Geometry view.

    PTVGROUP

    1475

    15.40.12.1 Editing the geometry in the schematic view

    3. Make the desired changes.


    Note: The Signal groups and Stages options are only displayed in the schematic view, if
    signal groups or stages have been created.
    Marking legs
    You can mark individual legs in the schematic view via the colored buttons next to the legs.
    1. Click the desired button.
    The selected leg is marked in the list view.
    Note: You can edit the attributes of the marked leg right in the list.
    2. If required, select further legs.
    Creating pockets
    In the schematic view, you can add pockets to the left or to the right of individual legs.
    1. Make sure that the Geometry view is selected in the Views window.
    2. Make sure that the Lanes option has been selected in the schematic view.
    3. Click the button of the leg to which you want to add a pocket.
    The buttons to create pockets are displayed at the selected leg. The buttons display a plus
    sign.
    4. Click the button to create the desired pocket.
    The pocket is inserted.

    1476

    PTVGROUP

    15.40.12.1 Editing the geometry in the schematic view

    Note: You can remove the pocket again if you click the button next to the pocket anew.
    The button displays an x.
    Marking lanes and lane turns
    As soon as you have marked a leg, you can mark the individual lanes
    1. Make sure that the Geometry view is selected in the Views window.
    2. Make sure that the Lanes option has been selected in the schematic view.
    3. Mark the desired leg by clicking the respective button.
    Note: A quick info is provided for all buttons of the schematic view, which describes
    the action triggered when clicking the button.
    The lanes display further buttons to mark lanes.
    4. Mark the desired lane by clicking the Mark lane buttons.
    The lane turn and further buttons to mark lane turns are displayed, if the lane provides lane
    turns.
    5. If required, mark the desired lane turn by clicking the Mark lane turn button.
    Further buttons are displayed to delete lane turns.

    PTVGROUP

    1477

    15.40.12.1 Editing the geometry in the schematic view


    Notes: Use the Delete lane turns and Create lane turns buttons to delete or create lane
    turns.
    You can edit the attributes of marked lane turns right in the list view. A lane that is marked
    in the schematic view, is also marked in the list view.
    Creating crosswalks
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Crosswalks option.
    Possible crosswalks are displayed as dashed lines.

    3. Create a crosswalk by clicking the desired Create crosswalk button with the + sign.
    The crosswalk is inserted.
    4. Create further crosswalks, if required.
    Notes: You can remove a crosswalk again by clicking the Delete crosswalk button
    which displays an x.
    If you insert a signal control, all crosswalks are inserted automatically at the node or main
    node, as long as none exist so far.
    Creating detectors
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Detectors option.
    Lane on which you can insert detectors are marked by a +.

    1478

    PTVGROUP

    15.40.12.2 Editing the geometry in the list view

    3. Create a detector by clicking the desired button Create detector for this lane with the +
    icon.
    The Create detector window opens.
    4. Enter the desired data (see "Properties and options of detectors" on page 1411).
    5. Confirm with OK.
    The detector is inserted and in the display shown as a small square at the node.
    6. Create further detectors, if required.
    Tip: You can remove a detector by marking it in the list view and pressing the D EL key.
    15.40.12.2 Editing the geometry in the list view
    Notes: You can edit the width of the rows and columns by dragging the mouse in the desired direction.
    You can edit the attribute selection of the list (see "Adjusting the attribute selection in the
    Junction editor" on page 1440).
    The context menu of the list is nearly identical to the context menu of the regular lists (see
    "Adjusting the column width to the contents" on page 2310).
    Displaying leg attributes
    In the list view, each column describes a leg and each row describes an attribute of this object.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Legs option.
    The list view displays all legs of the selected node.

    PTVGROUP

    1479

    15.40.12.2 Editing the geometry in the list view


    3. Make the desired changes.
    Editing leg attributes
    You can edit the editable attributes of legs in the list. You can, for example, display the following leg attributes in the list view.
    Element

    Description

    Orientation

    Display of the orientation of the leg

    Stop line position

    Enter a stop line distance.


    Tip
    The entry is relevant when exporting to Vissim.

    Center island
    length

    Enter the desired length of the center island in meters


    Tips
    If you want to create a center island, the Center Island Length and
    the Center Island Width need to be > 0.
    The entry is relevant when exporting to Vissim.

    Center island
    width

    Enter the desired width of the center island in meters


    Tip
    The entry is relevant when exporting to Vissim.

    Channelized turn
    length

    You can add a channelized turn to the marked leg by entering the
    desired length of the channelized island.

    The following attributes are only displayed, if you have defined leg templates and geometry
    templates and the node has signal groups:
    Element

    Description

    Use leg template

    Here you can select a leg template which shall be used for the marked leg.
    Tip
    You can create leg templates in a separate window (see "Creating a
    leg template" on page 1485).

    Apply geometry
    template

    Here you can select a geometry template which shall be used for the
    marked leg.
    Tip
    You can create geometry templates in a separate window (see "Creating a geometry template" on page 1486).

    Signal groups

    Here you can select the desired signal group for the leg.

    Displaying lane attributes


    In the list view, each column describes a main node and each row describes an attribute of
    this object. Here, for example, you can edit pocket lengths.
    1480

    PTVGROUP

    15.40.12.2 Editing the geometry in the list view


    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Lanes option.
    The list view displays all lanes of the selected node.

    3. Make the desired changes.


    Editing lane attributes
    You can edit the editable attributes of the lanes in the list in different ways, depending on the
    attribute: You can, for example, display the following lane attributes in the list view.
    Element

    Description

    Link number

    Display of the number of the link

    Approach type

    Display of the approach type (outflow/inflow)

    Width

    Enter the width of the lane

    Length

    Enter the length of the lane

    TSys set

    Use the button to select one or more transport systems for the lane in
    a separate window.
    Tip
    In the TSysSet window, use the C TRL key to select several transport
    systems.

    ICA preset saturation flow rate

    Enter the desired saturation flow rate


    Notes
    The values of all lanes or a lane group are added. If both turns and
    lanes exist for a lane group, whose attribute ICA use preset saturation flow rate has been selected, the values of the lanes are used.

    ICA use preset


    saturation flow
    rate

    If the option has been selected, you can edit the value or the attribute
    ICA preset saturation flow rate and the specified value is used.

    Detectors

    Display of the name of the allocated detector


    Note
    This row will only be displayed if detectors are defined. You can allocate one or several detectors to the lane by clicking the corresponding column.
    Tip
    Alternatively you can specify the allocation to the lanes directly when
    inserting the detectors.

    PTVGROUP

    1481

    15.40.12.2 Editing the geometry in the list view


    The following properties are always displayed in the list view of the geometry, if you select the
    Lanes option and signal groups are defined:
    Element

    Description

    Signal groups

    Here you can select the desired signal group for the lane.

    Displaying lane attributes


    In the list view, each column describes a lane turn and each row describes an attribute of this
    object.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Lane turns option.
    The list view displays all lane turns of the selected node.
    3. Make the desired changes.
    Editing lane turn attributes
    You can, for example, display the following lane turn attributes in the list view:
    Element

    Description

    From link number

    Display of the number of the link on which the lane turn starts

    From lane number Display of the number of the lane on which the lane turn starts
    To link Number

    Display of the number of the line which the lane turn enters

    To lane number

    Display of the number of the lane which the lane turns enters

    TSys set

    You can select one or more transport systems for the lane turn.

    The following property is always displayed in the list view of the geometry, if you select the
    Lane turn option and signal groups are defined:
    Element

    Description

    Signal groups

    Here you can select the desired signal group for the lane turn.

    Displaying attributes of crosswalks


    In the list view, each column describes a crosswalk and each row describes an attribute of this
    object.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Crosswalks option.
    The list view displays all crosswalks of the selected node.
    3. Make the desired changes.

    1482

    PTVGROUP

    15.40.12.2 Editing the geometry in the list view


    Editing attributes of crosswalks
    You can, for example, display the following attributes of crosswalks in the list view:
    Element

    Description

    Orientation

    Display of the orientation of the crosswalk

    Width

    Enter the width of the crosswalk

    Pedestrian
    volume

    Enter the pedestrian volume on this crosswalk

    Detector

    Long name of the allocated detector


    Note
    This row will only be displayed if detectors are defined. You can allocate the desired detector to the crosswalk via a selection list if you
    click the column.
    Tip
    Alternatively you can define the allocation to the crosswalks directly
    when inserting the detectors.

    The following properties are always displayed in the list view of the geometry, if you select the
    Crosswalks option and signal groups are defined:
    Element

    Description

    Signal group

    Here you can select the desired signal group for the crosswalk.

    Displaying attributes of detectors


    In the list view, each column describes a detector and each row describes an attribute of this
    object.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Detectors option.
    The list view displays the detectors of the selected node.
    3. Make the desired changes.
    Editing attributes of detectors
    You can, for example, display the following attributes of detectors in the list view:
    Element

    Description

    Number

    Number of the detector

    Name

    Long name of the detector

    Code

    Code of the detector

    PTVGROUP

    1483

    15.40.12.2 Editing the geometry in the list view


    Element

    Description

    Lanes

    Here you can select the lanes which shall be allocated to the detector.
    Note
    You can allocate detectors to one or several lanes by clicking the
    column.
    Tip
    Alternatively the allocation to the lanes can be defined directly when
    inserting the detectors.

    Crosswalks

    Here you can select the crosswalks which shall be allocated to detector.
    Note
    You can allocate detectors to one or several crosswalks by clicking
    the column.
    Tip
    Alternatively the allocation to crosswalks can be defined directly
    when inserting the detectors.

    Allocating signal groups to lane turns or crosswalks


    You have to allocate signal groups either to lane turns or to crosswalks so that the signal
    groups have a spatial reference.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Lane turns or Crosswalks option.
    3. In the list view, click the desired cell under Signal groups.
    The Signal groups window opens.
    4. Select the desired signal group
    5. Confirm with OK.
    The signal group is allocated to the lane turn or crosswalk.
    Note: You can check the allocations of a signal group if you select the Signal groups
    option in the Geometry view, and open the respective selection window under Lane
    turns and Crosswalks for the desired signal group (see "Editing signal group attributes"
    on page 1485).
    Allocating signal groups to lanes or legs
    You can also allocate signal groups to lane turns by allocating them to all lane turns of a leg or
    lane in one step.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Lanes or Legs option.

    1484

    PTVGROUP

    15.40.12.2 Editing the geometry in the list view


    3. In the list view, click the desired cell under Signal groups.
    The Signal groups window opens.
    4. Select the desired signal group
    5. Confirm with OK.
    The signal group is allocated to all lane turns of the selected lane or leg.
    Displaying signal group attributes
    In the list view, each column describes a signal group and each row describes an attribute of
    this object.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Signal groups option.
    The list view displays all signal groups of the selected node.
    3. Make the desired changes.
    Editing signal group attributes
    You can, for example, display the following attributes of signal groups in the list view.
    Element

    Description

    Number

    Display of the number of the signal group

    Name

    Name of the signal group

    Green time start

    Display of the green time start in seconds

    Green time end

    Display of the green time end in seconds

    The following properties are always displayed in the list view of the geometry, if you select the
    Signal groups option:
    Element

    Description

    Lane turns

    Here you can select the lane turns, which shall be allocated to the
    signal group.

    Crosswalks

    Here you can select the crosswalks, which shall be allocated to the
    signal group.

    Creating a leg template


    You can specify leg templates for the selected node. When using a leg template, a predefined
    set of lanes, lane turns and crosswalks are generated at a leg.
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Legs option.

    PTVGROUP

    1485

    15.40.12.2 Editing the geometry in the list view


    3. In the list view, right-click the column of the leg that you want to use to specify a leg template.
    A context menu opens.
    4. Select the Leg template definition.
    The Create template window opens.

    5. Make the desired changes.


    Element

    Description

    Number

    Number of the leg template

    Name

    Name of the leg template

    Comment

    Specify the leg from which the template has been created

    6. Confirm with OK.


    The leg template is inserted.
    Note: Afterwards, you can allocate the inserted leg template to a leg, if you select the
    Legs option in the schematic view and allocate the leg template to the desired leg via
    Use leg template in the list view.
    Creating a geometry template
    Contrary to leg templates, geometry templates can be applied to all legs of the selected node
    (see Fundamentals: Chpt. 3.1.21.2 , page 90).
    1. Make sure that the Geometry view is selected in the Views window.
    2. In the schematic view, select the Legs option.
    3. In the list view, right-click the column of the leg that you want to use to specify a geometry
    template.
    Note: The selected leg becomes the reference leg of the geometry template.

    1486

    PTVGROUP

    15.40.13 Editing the signal timing of a node


    A context menu opens.
    4. Select the Define geometry template entry.
    The Create template window opens.

    5. Make the desired changes.


    Element

    Description

    Number

    Number of the geometry template

    Name

    Name of the geometry template

    Comment

    Specify the node from which the template has been created.

    6. Confirm with OK.


    The geometry template is inserted.

    15.40.13 Editing the signal timing of a node


    Note: This functionality is only available, while the Junction editor and control add-on is
    active (see "Enabling or disabling installed add-ons" on page 886).
    You can display nodes in the signal timing view. The signal timing view changes according to
    the selected signal-control type.
    If the control is signal group-based, green bars will indicate the green times of each
    signal group.
    If the control is stage-based, the geometry will be replaced by a schematic view of the
    stage sequence and the bar display shows one bar per stage.
    Notes: If the SC of the node has the signal control type Vissig or RBC, you need to open
    an external program or the RBC editor to edit the signal timing (see "Editing a signal control in Vissig" on page 2528 and "Editing a signal control of the RBC type" on page
    1470).
    You can also edit the offset times in the signal time-space diagram (see "Displaying
    signal time-space diagrams" on page 2479).
    PTVGROUP

    1487

    15.40.13.1 Switching off signal programs


    15.40.13.1 Switching off signal programs
    You can switch off a signal control. In the affected procedures ICA assignment, signal offset
    optimization and cycle and green time optimization, the respective nodes will then be treated
    like two-way stops.
    1. Make sure that the Signal timing view is selected in the Views window.
    2. In the schematic view, click the Switched on/switched off on top right.
    The signal control is switched off. The effective control type of the node is set to two-way stop.
    Note: External signal controls and signal controls of type RBC can have several signal
    programs (see "Editing a signal control in Vissig" on page 2528 and "Editing a signal control of the RBC type" on page 1470). In this case you can switch the signal program in the
    top right corner of the window in the Signal program drop-down list. The No signal program corresponds to the Switched off option.
    15.40.13.2 Editing the signal times of signal group-based controls
    You can edit the signal times in the lower section of the Junction editor as follows. The wide
    green bars indicate the green times, the thin red ones the red times. The schematic view in the
    upper window displays the lane turns and crosswalks to which the signal times are allocated.
    1. Make sure that the Signal timing view is selected in the Views window.
    The lower window displays the signal times. Each row corresponds to a signal group.

    2. Make the desired changes.

    1488

    PTVGROUP

    15.40.13.2 Editing the signal times of signal group-based controls


    Element

    Description

    Cycle time

    Here you can enter the desired cycle time in seconds.

    Offset

    Here you can enter the desired offset in seconds.


    Note
    The entire signal plan will then be postponed by the entered time.

    3. If required, make further changes via the context menu.


    Adjusting the column display
    You can edit the display of the items as follows.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    2. Select the Edit columns entry.
    A window opens.
    3. Select the items that you want to display as columns.
    4. Confirm with OK.
    All selected items are displayed as columns.
    Setting the signal times display
    There are three display options for the signal times.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    2. Under Appearance, select the desired entry.
    Element

    Description

    Classic

    The signal times are displayed classically.

    3d tubes

    The signal times are displayed as 3d tubes.

    3d boxes

    The signal times are displayed as 3d boxes.

    The signal times are displayed as desired.


    Resize automatically
    The display of the signal groups adjusts automatically to the window size, even if it is changed.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    2. Select the Resize automatically entry.
    The display of the window size is adjusted automatically.

    PTVGROUP

    1489

    15.40.13.2 Editing the signal times of signal group-based controls


    Show entire signal program
    In the lower section of the Signal timing view, you can display all existing signal times of the
    selected node or main node and expand the display to the entire section.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    2. Select the Show entire signal program entry.
    All signal times are displayed and adjusted to the size of the display.
    Note: You can change the height of the individual rows by dragging the borders of the
    row headers up or down.
    Editing signal times in the graphics
    You can edit the signal times of signal groups directly in the graphics.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    1. Select the Edit signal states entry.
    2. Click the desired row of the signal program.
    3. Move the mouse over the signal states of the selected row.
    Depending on the location, the mouse pointer has a different form.
    Element

    Description
    If a hand is displayed, you can shift the entire signal state while
    holding down the mouse key.
    If arrows are displayed, you can shift the start time or end time of
    the signal state while holding down the mouse key.

    Notes: You can only shift signal states with a variable duration. You cannot shift
    signal states with a fixed duration (amber states) on their own.
    As long as a signal state is shifted, reserve times are indicated by a green background and intergreen violations are indicated by an orange background.
    4. Make the desired changes.
    Notes: You can also edit the signal states individually in the table to the right of the
    graphics. You can also overwrite standard times.
    If you move the mouse over the signal times column, you can shift the entire signal program while holding down the mouse key.

    1490

    PTVGROUP

    15.40.13.2 Editing the signal times of signal group-based controls


    Stretching or compressing signal programs
    You can stretch or compress a signal program.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    2. Select Stretch/compress entry.
    3. Move the mouse over the labels of the time axis of the signal program.
    The mouse pointer changes into a double arrow.

    4. Stretch or compress the signal program as follows.


    Element

    Description
    Compressing a signal program:
    If you move the mouse within the axis labels to the left while holding down
    the left mouse key, the signal program is compressed. The section highlighted in red is cut out.
    Stretching a signal program:
    If you move the mouse within the axis labels to the right while holding
    down the left mouse key, the signal program is stretched. The duration of
    the section highlighted in green is inserted at the beginning of the section
    highlighted in green.
    Note
    If the marked section is grey, you cannot stretch or compress the signal program, because at least one minimum duration is violated.

    Allocating lane turns


    You can edit the allocation of selected signal groups as follows.
    1. Right-click the row of the signal group whose lane turn you want to edit.
    A context menu opens.
    2. Select the Edit lane turns entry.
    The Lane turns window opens.
    3. Select the desired lane turns.
    4. Confirm with OK.
    The signal group is allocated to the selected lane turns.
    Allocating crosswalks
    You can edit the allocation of selected crosswalks as follows.
    1. Right-click the row of the signal group whose crosswalks you want to edit.
    PTVGROUP

    1491

    15.40.13.3 Editing the signal times of stage-based controls


    A context menu opens.
    2. Select the Edit crosswalks entry.
    The Crosswalks window opens.
    3. Select the desired crosswalks.
    4. Confirm with OK.
    The signal group is allocated to the selected crosswalks.
    Adding a signal group
    You can add further signal groups to the displayed signal program.
    1. Right-click in the lower section of the Signal timing view.
    A context menu opens.
    2. Select the Add signal group entry.
    The Create signal group window opens.
    3. Make the desired settings (see "Creating a signal group" on page 1473).
    4. Confirm with OK.
    The signal group is inserted.
    Deleting a signal group
    You can delete signal groups from the signal program.
    1. Right-click the signal group that you want to delete.
    A context menu opens.
    2. Select the Delete signal group entry.
    The signal group is deleted.
    15.40.13.3 Editing the signal times of stage-based controls
    In case of stage-based signal controls, the geometry is replaced by a schematic view of the
    stage sequence. The bar display shows one bar per stage.
    1. Make sure that the Signal timing view is selected in the Views window.
    For each stage, a child window is displayed in the upper section and a corresponding bar
    in the lower section.

    1492

    PTVGROUP

    15.40.13.3 Editing the signal times of stage-based controls

    2. Make the desired changes.


    Note: Some of the entries in the context menu correspond to the ones for signal groupbased controls. They are explained in the respective section (see "Editing the signal
    times of signal group-based controls" on page 1488).
    Editing the allocation of signal groups to stages
    Each square in the upper section illustrates a stage. The arrows illustrate signal groups. You
    can regulate the allocation of signal groups to stages by clicking these arrows. All signal
    groups allocated to a stage, have a green light.
    1. In the upper section, mark the square of the stage whose signal group allocation you want
    to edit.
    Note: If you point the mouse at an arrow, the arrow and all arrows that represent the
    same signal group are highlighted in a different color.
    2. Edit the color of the desired arrows from red to green or from green to red by clicking the
    desired arrow.
    The arrows change their color and the allocation to the stage.
    Creating stages
    You can create stages for stage-based controls for nodes.
    Tip: Alternatively, you can use stage templates (see "Generating stages from templates"
    on page 1496).
    1. Make sure that the Signal timing view is selected in the Views window.

    PTVGROUP

    1493

    15.40.13.3 Editing the signal times of stage-based controls

    2. In the toolbar of the Junction editor, click the

    Create stage icon.

    Tip: Alternatively, you can create further stages via the Add stage entry in the context
    menu.
    The Create stage window opens.

    3. Make the desired changes.


    Element

    Description

    Number

    Unique number of the stage

    Name

    Name of the stage

    Green time start

    Enter the green time start of the stage

    Green time end

    Enter the green time end of the stage

    Minimum green
    time

    Enter the minimum green time in seconds.


    Note
    The value takes effect during green time optimization (see "Optimizing signal cycles and split of a single signal control" on page
    1501).

    4. Confirm with OK.


    The stage is inserted and displayed as a bar in the bar display.
    Editing stages
    You can manually edit stages in the Signal timing view by dragging the bar with the mouse to
    the desired width. The difference with the signal group view is that shifting green times affects
    all signal groups of a stage (see "Editing the signal times of signal group-based controls" on
    page 1488).
    Tip: Moreover, you can edit the attributes of stages in the list of the Geometry view or in
    the Stages list (see "Opening a list" on page 2299).
    Deleting stages
    1. Make sure that the Signal timing view is selected in the Views window.

    1494

    PTVGROUP

    15.40.13.3 Editing the signal times of stage-based controls


    2. In the lower window of the Junction editor, right-click the bar of the stage that you want to
    delete.
    A context menu opens.
    3. Select the Delete stage entry.
    The stage is deleted.
    Tip: Alternatively, you can delete a stage by clicking the
    bar.

    Delete stage icon in the tool-

    Reading stage templates


    Instead of creating stages and signal groups manually, you can use predefined stage templates (see "Generating stages from templates" on page 1496). These can be read additively
    in *.net format.
    1. In the File menu, place the pointer on the Open entry.
    2. Select the Network entry.
    The Open network window opens.
    Notes: The predefined stage templates are contained the ...\PTV Visum 13\Data\Node_Templates folder of your Visum installation directory.
    The names of the stage template files are Signaltemplateslefthandtraffic.net and
    Signaltemplatesrighthandtraffic.net.
    3. Select the desired file.
    4. Click the Open button.
    The Read network window opens.
    5. Read the network additively (see "Reading network data additionally" on page 851).
    The network data are read in.
    Notes: You can edit the standard data in the Network> Stage templates menu.
    You can change the names of the stage templates by double-clicking the desired row in
    the Templates window.
    Deleting stage templates or stage templates sets
    1. In the Network menu, select the Stage templates entry
    The Templates window opens. All stage templates and stage template sets existing in the
    network are displayed.

    PTVGROUP

    1495

    15.40.13.3 Editing the signal times of stage-based controls

    2. In the drop-down list, select the desired entry.


    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.

    3. Click the

    Delete button.

    4. Confirm with OK.


    The selected entries are deleted.
    Generating stages from templates
    Instead of creating stages and signal groups manually, you can use predefined stage templates. Predefined stage templates ease the definition of a signal-controlled junction or main
    node (see Fundamentals: Chpt. 3.1.21.3 , page 92).
    1. Make sure that the Signal timing view is selected in the Views window.
    2. Right-click in the lower window of the Junction editor.
    A context menu opens.
    3. Select the Use stage template entry.

    Note: Alternatively, you can open the window via the


    in the tool bar.

    Use stage templates icon

    The Create stages from template window opens.

    1496

    PTVGROUP

    15.40.14 Managing signal coordination groups

    4. Make the desired changes.


    Element

    Description

    Number of stages Specify the desired number of stages


    Note
    If, for example, you enter a 4, only stages with four stages will be
    displayed.
    Template

    Select a stage template (see "Reading stage templates" on page


    1495)

    Reference link

    Select a reference link for the template


    Tip
    and
    Use the
    the node.

    Stage reference

    buttons to switch to the previous or next link of

    Use the drop-down list to specify the order of the stages.

    5. Confirm with OK.


    The stages are generated based on the selected template.

    15.40.14 Managing signal coordination groups


    For the coordination of the signal controls, you can create and edit signal coordination groups.
    15.40.14.1 Creating a signal coordination group
    1. In the Network menu, select the Signal coordination groups entry.
    The Signal coordination groups window opens.
    2. Click the

    Create button.

    The Create signal coordination group <Number> window opens.


    3. Make the desired settings (see "Properties and options of signal coordination groups" on
    page 1498).
    4. Confirm with OK.
    The coordination group is created.

    PTVGROUP

    1497

    15.40.14.2 Properties and options of signal coordination groups


    15.40.14.2 Properties and options of signal coordination groups

    Element

    Description

    No.

    Unique number of the signal coordination group

    Code

    Code of the signal coordination group

    Name

    Name of the signal coordination group

    Cycle time family

    Enter the cycle times in seconds

    15.40.14.3 Editing signal coordination groups


    1. In the Network menu, select the Signal coordination groups entry.
    The Signal coordination groups window opens.
    2. In the list, click the signal coordination group of your choice.
    3. Click the

    Edit button.

    The Edit signal coordination group <Number> window opens.


    4. Make the desired settings (see "Properties and options of signal coordination groups" on
    page 1498).
    5. Confirm with OK.
    The changes are saved.
    15.40.14.4 Deleting a signal coordination group
    1. In the Network menu, select the Signal coordination groups entry.
    The Signal coordination groups window opens.
    2. In the list, click the signal coordination group of your choice.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the

    Delete button.

    4. Confirm with OK.


    The signal coordination group is deleted.
    1498

    PTVGROUP

    15.40.15 Edit time-varying attributes

    15.40.15 Edit time-varying attributes


    In the Junction editor, you can create, edit, and delete time-varying attributes of nodes, main
    nodes, turns and main turns, if you have created time-varying attributes for the respective network object type beforehand (see "Managing time-varying attributes" on page 979).
    1. In the toolbar of the Junction editor, click the

    Edit time-varying attributes icon.

    The Edit time-varying attributes window opens.


    2. Make the desired settings (see "Entering and editing time-varying data for time-varying attributes" on page 980).
    3. Confirm with OK.
    The changes are applied.

    15.40.16 Calculating and exporting ICA


    In the Junction editor, you can start ICA calculations (ICA, Intersection Capacity Analysis) for
    the displayed node or main node, open ICA reports, recalculate ICA automatically and export
    ICA reports.
    Notes: You can only make ICA calculations for nodes or main nodes of the type signalized, two-way stop, all-way-stop or roundabout. Signalized nodes without a signal control or with a switched off signal control are calculated with the control type two-way stop.
    In addition, the Node impedance calculation (ICA) needs to be set as Method for impedance at node in the list of the Node view or in menu Calculate> General procedure
    settings> PrT settings> Node impedances.
    Under menu Calculate> Network check, for the entire network, you can check if the ICA
    calculation is possible for the nodes or main nodes and if the respective nodes are modeled correctly (see "Checking the network and fixing errors" on page 1504). For a single
    node or main node, you can check the status to find out whether the calculation can be
    done (see "Checking the status of ICA calculations" on page 1499).
    15.40.16.1 Checking the status of ICA calculations
    You can check whether an ICA calculation is possible for a node or main node. An ICA calculation can only be done if a signal control is allocated to the node or main node.
    1. Make sure that the desired main node is open in the junction editor.
    2. In the toolbar of the Junction editor, click the

    ICA calculation status icon.

    A message indicates whether a calculation is possible for the displayed node or main node. If
    the calculation is not possible, the message states reasons for it. If it is possible, further information on the relevant data is given.
    15.40.16.2 Starting an ICA calculation
    1. Make sure that the desired node or main node is open in the junction editor.

    PTVGROUP

    1499

    15.40.16.3 Displaying the ICA calculation in the report window


    2. Make sure that the node is modeled correctly for an ICA calculation (see "Checking the status of ICA calculations" on page 1499).
    3. In the tool bar of the Junction editor, click the

    Execute ICA calculation icon.

    Note: The icon is disabled, if the ICA calculation is not possible for the node (see
    "Checking the status of ICA calculations" on page 1499).
    The ICA calculation is started. If the signal control of a node or main node is allocated to multiple nodes or main nodes when calculating ICA, the ICA calculation is executed simultaneously at all corresponding nodes and main nodes.
    15.40.16.3 Displaying the ICA calculation in the report window
    You can display the ICA calculation results of a node in Excel. The display therein is updated
    as soon as you make a new ICA calculation.
    1. Make sure that the desired node or main node is open in the junction editor.
    2. In the toolbar of the Junction editor, click the

    Open/close ICA report window icon.

    The ICA report window is opened in Excel.


    Notes: The window is empty if you have made no ICA calculation.
    If you switch to a different node or main node, the report window will not be refreshed.
    You can refresh the display by starting a new calculation (see "Starting an ICA calculation" on page 1499).
    You can close the ICA report window by clicking the
    icon again.

    Open/close ICA report window

    The ICA report window is closed automatically if you close the Junction editor or the
    Visumwindow.
    15.40.16.4 Recalculating ICA automatically
    This functionality refreshes the Excel sheet of the ICA calculation each time you make a
    change in the Junction editor.
    In the toolbar of the Junction editor click the
    culation after network changes icon.

    Enable/disable automatic ICA cal-

    If this function is activated, ICA is recalculated after each action, this also applies to any Undo
    action.
    15.40.16.5 Exporting an ICA report
    You can make an ICA calculation and save the results to an Excel file.
    1. Make sure that the desired node or main node is open in the junction editor.

    1500

    PTVGROUP

    15.40.17 Optimizing signal cycles and split of a single signal control

    2. In the toolbar of the Junction editor, click the

    Export ICA report to Excel icon.

    Note: The icon is disabled, if the ICA calculation is not possible for the node (see
    "Checking the status of ICA calculations" on page 1499).
    ICA is calculated and the Save ICA calculation window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The result of the calculation is saved to an *.xml file.

    15.40.17 Optimizing signal cycles and split of a single signal control


    Within the scope of the intersection capacity analysis using ICA, you can optimize the signal
    cycle and split for an individual signal control (see Fundamentals: Chpt. 6.5.4 , page 298).
    Notes: The optimization is always done for all (main) nodes of a signal control.
    The settings under menu Calculate > General procedure settings > entry PrT
    settings> Signal cycle and split optimization apply (see "Optimizing signal cycle and
    split times for active nodes" on page 1921).
    You can also execute the signal cycle and split optimization for multiple or all active
    nodes (see "Updating impedances at nodes" on page 1072 and "Optimizing signal cycle
    and split times for active nodes" on page 1921).
    1. Make sure that the desired node or main node is open in the Junction editor.
    2. In the toolbar of the Junction editor, click the
    icon.

    ICA signal cycle and split optimization

    Note: The icon is disabled, if the ICA calculation is not possible for the node (see
    "Checking the status of ICA calculations" on page 1499).
    The ICA calculations and optimizations are done for all nodes that are allocated to the signal
    control.

    15.40.18 Displaying turn volumes in the Junction editor


    In the Junction editor, you can display turn volumes and export multiple turn volume displays
    as graphics. You can now proceed as follows:
    Displaying turn volumes in the Junction editor
    Specifying settings for the print frame of turn volumes
    Positioning link labels along links
    Exporting turn volumes as graphics

    PTVGROUP

    1501

    15.40.18.1 Displaying turn volumes in the Junction editor


    15.40.18.1 Displaying turn volumes in the Junction editor
    In the Junction editor, the display of turn volumes is standardized by default. In this display, the
    angles of the legs are taken from the link orientations. The link orientation is a link attribute in
    Visum.
    Alternatively, you can specify a turn volumes display where the angles of the legs are taken
    from the link geometry in the network, i.e. their coordinates in the network.
    The type of display specified here is used not only for the display of turn volumes, but also for
    the graphic display after an export or Multi-export. The setting is saved with the version file.
    Displaying and outputting standardized turn volumes
    1. Double-click the desired node or main node in the network.
    The Junction editor opens.
    2. Make sure that the Views tab is selected in the Overview window.
    3. Click the Turn volumes button.
    4. In the Junction editor menu, select the Angle from link orientation entry.
    The turn volume is displayed and the angles of the legs are taken from the link orientations.
    Displaying and outputting turn volumes based on the link geometry of the network
    1. Double-click the desired node or main node in the network.
    The Junction editor opens.
    2. Make sure that the Views tab is selected in the Overview window.
    3. Click the Turn volumes button.
    4. In the Junction editor menu, deselect the Angle from link orientation entry.
    The turn volume is displayed and the angles of the legs are taken from the link orientations in
    the network.
    Notes: The settings of the graphic parameters for turn volumes of the network editor are
    applied (see "Displaying turns, main turns, and turn volumes" on page 2435). Switch to
    the Network editor window to adjust the display in the Graphics > Graphic parameters
    menu. Even turn volumes that shall not be displayed in the network editor, are displayed
    in the Junction editor. Each node which can be displayed is shown as turn volume.
    In the graphic parameters, you can, for example, specify, that just incoming or outgoing
    turns shall be labeled.
    In the Turn volumes view, use the Nodes, Links and Turns options to select whether the
    list view shall display node, turn or link attributes.
    15.40.18.2 Specifying settings for the print frame of turn volumes
    In the Junction editor, turn volumes are displayed in the preview mode. You can edit the settings of the preview as follows:

    1502

    PTVGROUP

    15.40.18.3 Positioning link labels along links


    1. In the Junction editor menu, select the Print frame entry.
    The Print frame parameters window opens.
    2. Make the desired changes in the Print frame, Header and Footer tabs.
    Note: The settings are nearly identical to those of the network display (see "Setting
    the print frame" on page 2504).
    3. Confirm with OK.
    The print frame is displayed according to your chosen settings.
    15.40.18.3 Positioning link labels along links
    In the Turn volumes view, you can position link labels at turn volumes in such a way, that they
    are issued parallel to the link. This setting is saved in the version file.
    Notes: The settings of the graphic parameters for link labels of the network editor are applied.
    The displayed link width in the Turn volumes view depends on the settings in the Parameters for the export of multiple turn volumes window, Size > Circle size tab. Here
    you can enter the desired size of the circle in percent. The display of the node legs
    covers the remaining share.
    1. In the Junction editor, open the Turn volumes view.
    2. In the Junction editor menu, select the Link label along link entry.
    The link labels are positioned along the link. The label always displays the undirected value of
    both link directions.
    15.40.18.4 Exporting turn volumes as graphics
    Before exporting one or multiple turn volumes as graphics, you can specify different settings
    for the export.
    1. In the Junction editor menu, select the Export the turn volumes as image entry.
    The Save: Exported turn volumes window opens.
    2. Enter the file name and the path, if required.
    3. Select the desired file type.
    4. Click the Save button.
    The Parameters: Multi-export of turn volumes window opens.
    5. In the Size tab, make the desired changes.

    PTVGROUP

    1503

    15.41 Checking the network and fixing errors


    Element

    Description

    Parameters

    Here you can specify the proportions for the export. All changes
    are immediately visible in the preview.
    Width
    Enter the output width of the entire graphics in the desired unit
    Height
    Enter the output height of the entire graphics in the desired unit
    Margin
    Enter the width of the margin
    Circle size
    Enter the ratio of label and circle in percent
    Portrait/landscape
    Select the export format of the turn volume

    Preview

    Graphic preview of the size and width-to-height ratio of the turn


    volume circle

    6. In the File tab, make the desired changes.


    Element

    Description

    File type

    Here you can select the file type of the graphics to be saved.

    Resolution

    Select the desired resolution.


    Note
    The default dpi value is the specified resolution or a multiple of
    the user's screen. The option is not provided, if you have selected
    the file type *.svg.

    Quality

    If you have selected the file type *.jpg, you can specify the desired
    quality for the exported graphics.

    Print frame

    If you click this button, the Print frame parameters window


    opens (see "Specifying settings for the print frame of turn volumes" on page 1502).

    7. Click the Start the export button.


    The turn volume view is saved in the chosen format.

    15.41

    Checking the network and fixing errors


    Errors in the network have impacts on calculations and analyses. Therefore, after editing the
    network you should check it for consistency. With the network check, you can detect errors in
    the network and partly fix them right away.

    15.41.1 Checking the network


    You can check the consistency of your network model.
    1504

    PTVGROUP

    15.41.1 Checking the network


    1. In the Calculate menu, select the Check network entry.
    The Check network window opens.

    2. Select what you want to check the network for.


    Section General
    Element

    Description

    Isolated nodes

    The option checks the network for nodes which are not
    connected to any link.
    Note
    These are irrelevant to the model and can be deleted.

    Turns and main turns


    which do not make
    sense

    The option checks whether the network contains turns or


    main turns which are open to a transport system which is
    yet closed to the From link or To link.
    Use the Relevant transport systems button to select the
    transport systems for the check in a separate window. The
    button is labeled with the selected transport systems.
    Note
    Only PrT and PuT transport systems can be selected, yet
    no PuT Walk transport systems.

    Multiple straight turns

    The option checks the network for nodes which with more

    PTVGROUP

    1505

    15.41.1 Checking the network


    Section General
    Element

    Description

    and main turns

    than one straight (main) turn per incoming link.


    Note
    This option does not work if you have selected the Preset
    values do only regard the angle of a turn option in the
    Network > Network settings > Network objects > Turn
    types menu.

    Section PrT
    Element

    Description

    Zones not connected for PrT

    The option checks the network for zones without PrT connectors. It checks for the existence of connectors and whether they
    are open to PrT transport systems. For zones with demand distribution as percentages, the connector shares are also
    checked.

    Check network con- The option checks for consistent paths between object pairs for
    sistency between
    the selected transport system selection.
    Use the drop-down list to specify the object pairs for which you
    want to run the check.
    Zone pairs (all zones)
    Pairs of nodes which are connected to different zones (all
    connector nodes)
    Pairs of zones with no connector weights or with connector
    weights for the entire OD demand, or pairs of nodes which
    are connected to a zone with connector weights for each
    single relation (all connector nodes with weight > 0)
    Use the Relevant transport systems button to select the transport systems for the check in a separate window. The button is
    labeled with the selected transport systems.
    Dead-end roads PrT The option checks whether the network contains dead-end
    roads with no connection to the network and no U-turn or opposite direction.
    Use the Relevant transport systems button to select the transport systems for the check in a separate window. The button is
    labeled with the selected transport systems.
    Links without succeed. link

    1506

    The option checks whether the network contains links with no


    connection to the network, which are closed to the selected
    transport systems.
    Notes

    PTVGROUP

    15.41.1 Checking the network


    Section PrT
    Element

    Description
    These are links which yet have a succeeding link but at the To
    node, the turns or the succeeding links are closed to the transport system. These links should be checked and edited.
    Use the Relevant transport systems button to select the transport systems for the check in a separate window. The button is
    labeled with the selected transport systems.

    Links with capacity


    PrT=0 or v0=0

    The option checks the network for PrT links with a capacity PrT
    = 0, or a speed v0 = 0.
    Note
    Such links are like closed links, so that no traffic can traverse
    them during assignments.

    Viability for ICA

    The option checks the network for nodes or main nodes of the
    type two-way stop, signalized, or all-way stop, which have not
    been modeled correctly for an ICA calculation. The program
    also checks whether the green time of a signal group is zero
    and if files exist for all external signal controls.
    Notes
    Partial nodes of main nodes are not checked. Only those nodes
    and main nodes are checked, for which ICA has been selected
    as impedance calculation method.

    Check node geometries

    The option checks the network for lane turns with closed incoming or outgoing lanes or incoming lanes with transport systems without any possible turns.

    Section PuT
    Element

    Description

    Zones not connected for The option checks the network for zones without PuT
    PuT
    connectors. It checks for the existence of connectors and
    whether they are open to PuT transport systems.
    Note
    For zones with demand distribution as percentages, the
    connector shares are also checked.
    Links with PuT Walk
    time=0

    The option checks the network for PuT Walk links with a
    time = 0.

    Links with PuT aux


    time=0

    The option checks the network for PuT Aux links with a time
    = 0.

    Links with PuT run

    The option checks the network for links with a PuT run time

    PTVGROUP

    1507

    15.41.1 Checking the network


    Section PuT
    Element

    Description

    time=0

    = 0, i.e. links, which are traversed by a line route of a specific transport system which has a link run time of 0s for the
    transport system and, in addition, a length or link type
    speed = 0 for the transport system.

    Links traversed multiple The option checks the network for links which a line route
    times by a line route
    traverses more than once in one direction.
    Vehicle combinations
    without vehicle unit

    The option checks the network for vehicle combinations


    without vehicle units.

    Inconsistent couplings

    The option checks the network for couplings that are not
    consistent. Those are couplings with valid days which do
    not overlap. If a vehicle journey operates, for example, Monday to Friday and the coupled vehicle journey operates at
    the weekend only, the coupling has no effect.

    Stop areas with identical The option checks the network for stop areas of the same
    node
    stop which have the same access node and thus permit
    direct transfers in zero time.
    PuT connector nodes
    without stop area

    1508

    The option checks the network for PuT connectors which


    lead to nodes without a stop area.
    Tip
    We recommend this check if you have selected the Force
    boarding/alighting at connected node option in the menu
    Calculate> General procedure settings> entry PuT settings> entry Assignment for the Walk links from/to
    connectors option.

    PTVGROUP

    15.41.1 Checking the network


    Section PuT
    Element

    Description

    PuT connector nodes


    without lines

    The option checks the network for PuT connectors which


    lead to nodes with stop areas which are not served by any
    lines as alighting or boarding is not permitted at any of the
    stop points.
    Note
    If the connector node has no stop area or no line serves the
    node, passengers use walk links before / after using the
    connector.
    Tip
    We recommend this check if you have selected the Force
    boarding/alighting at connected node option in the menu
    Calculate> General procedure settings> entry PuT settings> entry Assignment for the Walk links from/to
    connectors option.

    Forced chainings

    The option checks whether the network contains invalid forced chainings of which origin or destination vehicle journey
    section do not run on the planned calendar day or the destination vehicle journey section is used repeatedly on the
    same calendar day.

    Notes: Use the Check all and Uncheck all buttons to select or deselect all check options at the same time.
    You can display a quick info with an abstract of the check option by moving the
    mouse pointer over the respective
    button. You can also open the information in a
    separate window if you click the respective button.
    3. Click the Run tests button.
    The test operation is executed. Behind each check option, a button is displayed which you can
    use to open the results of the check (see "Displaying the results of the check and fixing errors"
    on page 1510).

    PTVGROUP

    1509

    15.41.2 Displaying the results of the check and fixing errors

    15.41.2 Displaying the results of the check and fixing errors


    1. Make sure that check has been run and that the Check network window is open (see
    "Checking the network" on page 1504).
    Separate buttons indicate the results of each option.
    Element

    Description

    ok

    No errors could be found

    An error has been found.

    2. Click the ! button of the option you need.


    A window opens. It contains the error description and, for some check options, suggestions
    for immediate error corrections.
    Note: If you click the ok button of an option for which no error has been found, a
    notice opens indicating that no error could be found.
    3. Click the desired button.

    1510

    Element

    Description

    OK

    Closes the window. You have to correct the error manually after
    closing the Check network window.

    Set to the active


    state

    Use the button to set active all network objects for which an error
    has been found. All other network objects of these network object
    types are set passive. In the network, you can easily make out the
    corrupt network objects and edit them afterwards in order to correct the mistakes.

    Immediate error
    correction

    Use the respective button to correct errors immediately in the network.


    Delete
    Corrupt nodes are deleted in the network.
    Close
    The corrupt turns or main turns are closed to the set transport system selection.
    Redefine
    Correct values are allocated to turn types at corrupt nodes.
    Open
    U-turns are inserted for the corrupt links or the opposite direction
    is opened.
    Calculate times
    For the corrupt links, the times are calculated from the respective
    standard speed.
    PTVGROUP

    15.42 Specifying a calendar and valid days


    4. Correct further errors, if required.
    5. Repeat the check operation, if required, until all errors have been corrected.
    6. Click the Close button.
    A notice opens. A detailed error report is saved to the file Messages.TXT.
    You can now proceed as follows.
    If you want to open the error report, click the Open button. The message file will then
    be opened in the editor registered for text files.
    If you do not want to open the error report, click the OK button. You can also open the
    message file later (see "Using protocol files" on page 876).

    15.42

    Specifying a calendar and valid days


    You can specify a calendar and valid days for your network (see Fundamentals: Chpt. 3.2.1 ,
    page 94).
    Note: Valid days can only be inserted, if you have activated the Calendar / valid days
    add-on (see "Enabling or disabling installed add-ons" on page 886).

    15.42.1 Selecting a calendar


    With the aid of the calendar, you can model the transport supply and demand in much greater
    detail. You can not only model any day, but also any combinations of weekdays or single
    days.
    Note: Use of the calendar is optional.
    Valid days are closely linked to the calendar (see "Creating a valid day" on page 1512)as they
    can be specified for the corresponding calendar
    The calendar has an effect on the dynamic assignment (PrT) and the PuT analysis, (see
    "Using the Timetable editor" on page 1526) as valid days can be allocated to individual
    vehicle journeys in the Timetable editor.
    1. In the Network menu, select the Network settings entry.
    The Network settings window opens.
    2. Select the Calendar tab.

    PTVGROUP

    1511

    15.42.2 Creating a valid day

    3. Select one of the following options:


    Element

    Description

    No calendar

    PuT supply and demand are modeled for an unspecified recurring day. A standard given valid day (daily) is used for this purpose.

    Weekly calendar

    PuT supply and demand are modeled separately for the individual weekdays Monday - Sunday.

    Annual calendar

    PuT supply and demand are modeled for any time period within
    the calendar period.
    Calendar start, calendar end
    Via the
    button you can open a calendar and select the beginning or the end of the calendar period with a mouse click on the
    desired date.

    Notes: For each network or version file, only one calendar option can be selected.
    If the calendar settings are changed, all previously created valid days, blocks and
    PuT analyses will be deleted.
    4. Confirm with OK.
    The settings are applied.

    15.42.2 Creating a valid day


    Notes: Valid days can only be inserted, if you have activated the Calendar / valid days
    add-on (see "Enabling or disabling installed add-ons" on page 886).
    You can only create further valid days if you are using a weekly or annual calendar (see
    "Selecting a calendar " on page 1511).
    The valid day daily is predefined by default.
    1512

    PTVGROUP

    15.42.3 Properties and options of valid days


    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Make sure that the Valid days tab is selected.

    3. Click the

    Create button.

    The Create valid day window opens.


    4. Enter the desired data (see "Properties and options of valid days" on page 1513).
    5. Confirm with OK.
    The valid day is inserted.

    15.42.3 Properties and options of valid days


    Different properties and options are displayed, depending on the selected calendar (see
    "Selecting a calendar " on page 1511).
    15.42.3.1 No calendar

    Element

    Description

    Number

    Unique number of the valid day

    Code

    Code of the valid day

    Name

    Name of the valid day

    Transport supply

    Projection factor for skims of the transport supply from the assignment period to a longer time period, for example 1 year

    Hour cost

    Projection factor for hourly costs from the assignment period to a longer time period, for example 1 year

    PTVGROUP

    1513

    15.42.3.2 Weekly calendar


    15.42.3.2 Weekly calendar

    Section

    Description

    Basis

    Number
    Unique number of the valid day
    Code
    Code of the valid day
    Name
    Name of the valid day
    Transport supply
    Projection factor for skims of the transport supply from the assignment period to a longer time period, for example 1 year
    Hour cost
    Projection factor for hourly costs from the assignment period to a longer time period, for example 1 year

    Weekly calendar

    Monday - Sunday
    If a weekday has been selected, it will be allocated to the valid day
    as a relevant day.
    If the weekday has not been selected, it will not be allocated to the
    valid day.

    1514

    PTVGROUP

    15.42.3.3 Annual calendar


    15.42.3.3 Annual calendar

    Section Basis
    Element

    Description

    Number

    Unique number of the valid day

    Code

    Code of the valid day

    Name

    Name of the valid day

    Transport supply

    Projection factor for skims of the transport supply from the assignment period to a longer time period, for example 1 year

    Hour cost

    Projection factor for hourly costs from the assignment period to a longer time period, for example 1 year

    Validity from

    Display of the start and the end of the calendar period


    You can specify the duration of the calendar period in the Network>
    Network settings> menu, Calendar tab (see "Selecting a calendar "
    on page 1511).

    Number

    Display of the number of calendar days allocated to the valid day.

    PTVGROUP

    1515

    15.42.3.3 Annual calendar


    Section Calendar days
    Element

    Description

    Calendar

    Section where you can allocate relevant calendar days to the valid
    day.
    You can select calendar days by clicking the desired date in the
    calendar.
    Selected calendar days are highlighted in green.
    Weekdays and Sundays that have not been selected are white,
    Saturdays that have not been selected are highlighted in gray.
    Days outside of the calendar period are red and cannot be selected.
    Note
    If you click a calendar day which is selected already, the allocation of
    the calendar day will be canceled.
    Tip
    You can also select calendar days using additional options, which
    you open via the Extend button (see "Additional options" on page
    1517).

    Display holidays

    If the option has been selected, already specified valid days will be
    displayed in the calendar (dark blue).
    Use the drop-down list to specify the holidays to be displayed.
    Note
    The displays only use is to provide information. The displayed holidays will not be allocated to the valid day as relevant calendar days.

    Display vacations If the option has been selected, already specified vacation days will
    be displayed in the calendar (light blue).
    Use the drop-down list to specify the vacation days to be displayed.
    Note
    The displays only use is to provide information. The displayed vacation days will not be allocated to the valid day as relevant calendar
    days.
    Extend/reduce

    1516

    Use the Extend button to display additional options for the selection
    of calendar days (see "Additional options" on page 1517). Use the
    Reduce button to hide the additional options.

    PTVGROUP

    15.42.3.3 Annual calendar


    Additional options

    Use the additional options to select calendar days that meet specific requirements. You can
    add or remove the selected calendar days from the calendar.
    There are four types of requirements:
    Time period (all days within a certain period)
    Weekdays (certain weekdays)
    Valid days: same selection as an existing valid day
    Vacation days: use existing vacation day calendar
    Buttons in the lower right section
    Element

    Description

    Apply

    Use the button to display the days selected according to the set options as days which shall be added to the selection as relevant calendar days. These days are highlighted in light green.
    Note
    The display is just a preview. The displayed days will only be allocated to the valid day as relevant calendar days, if you click the Show
    selection button.

    Delete

    Use the button to display the days selected according to the set options as days which shall be removed from the selection as relevant
    calendar days. These days are highlighted in light red.
    Note
    The display is just a preview. The displayed days will only be removed from the selection of relevant calendar days, if you click the
    Show selection button.

    PTVGROUP

    1517

    15.42.3.3 Annual calendar


    Buttons in the lower right section
    Element

    Description

    Show selection

    The selection of calendar days set via the Apply or Delete buttons is
    applied, i.e. the calendar days are added to or removed from the previous selection of relevant calendar days.

    Section

    Description

    Time period

    Validity from
    Time period within the calendar period for which calendar days are
    selected.
    Use the
    button to display a calendar in which you can mark the
    beginning or the end of the time period.

    Weekdays

    Mon-Sun
    Select the weekdays which shall be taken into account for the selection.
    Uncheck all/check all
    Use the buttons to select all weekdays simultaneously or to switch off
    the selection of all weekdays.
    Each < n >th occurrence
    Use the option to specify the recurrence pattern with which the selected weekdays will be used for the selection.
    Example
    If the week days Tuesday and Thursday are selected and every 3rd
    occurrence is set, the Tuesdays and Thursdays are selected every
    three weeks in the desired period.
    Week
    Use the option to determine specific weeks per month, whose selected weekdays will be used for the selection.
    1 corresponds to the first week of the month, 2 to the second week
    and so on.
    L always means the last week of the month, whether the month has
    four or five weeks.
    Example
    If the weekdays Monday and Tuesday and week 1 and 2 have been
    selected, all Mondays and Tuesdays of the first two weeks of the
    month will be selected within the desired time period.
    Note
    If the month starts with a Thursday, the selection starts with the Monday and Tuesday of the second week.

    1518

    PTVGROUP

    15.42.4 Editing attribute values of valid days


    Section

    Description

    Valid days

    Apply
    If the option has been selected, the same selection of calendar days
    will be used as for an existing valid day.
    Use the drop-down list, to select the valid day that shall be used as
    selection criterion.
    on valid days
    If the option has been selected, the selection of calendar days is
    exactly the same as the one for the set valid day.
    Except valid days
    If the option has been selected, the selection of calendar days corresponds to the days which are not selected for the set valid day
    (complement).

    Vacation days

    Apply
    If the option has been selected, the same selection of calendar days
    will be used as for an existing vacation day.
    Use the drop-down list, to select the vacation day that shall be used
    as selection criterion.
    On vacation days
    If the option has been selected, the selection of calendar days is
    exactly the same as the one for the set vacation day.
    Except vacation days
    If the option has been selected, the selection of calendar days corresponds to the days which are not selected for the set vacation day
    (complement).

    Note: The four conditions must always apply simultaneously, i.e. no calendar days will be
    selected if a time period has been specified but no weekday has been selected.

    15.42.4 Editing attribute values of valid days


    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Make sure that the Valid days tab is selected.
    3. In the list, select the desired valid day.
    4. Click the

    Edit button.

    The Edit valid day window opens.

    PTVGROUP

    1519

    15.42.5 Deleting valid days


    Tip: You can also open the window in the tabular timetable or in the block view by
    right-clicking a vehicle journey or line block and selecting the Edit valid day entry in
    the context-menu (see "The Timetable editor window" on page 1530 and "Opening
    the block view" on page 2120).
    5. Edit the values of the desired attributes (see "Properties and options of valid days" on page
    1513).
    Note: Of the standard valid day daily, you can only edit the name, the code, and the
    projection factor.
    6. Confirm with OK.
    The attribute values are edited.

    15.42.5 Deleting valid days


    Note: You cannot delete the standard valid day daily.
    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Make sure that the Valid days tab is selected.
    3. In the list, select the desired valid day.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    4. Click the

    Delete button.

    5. Confirm with OK.


    The valid day is deleted.
    Note: If you delete a valid day, all vehicle journeys which use this valid day, will be set to
    the standard valid day daily.

    15.42.6 Collate valid days


    You can collate valid days for traffic on the same day to a single valid day.
    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Make sure that the Valid days tab is selected.
    3. In the list, select the valid days of your choice.

    1520

    PTVGROUP

    15.42.7 Creating a vacation day


    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    4. Click the

    Group button.

    5. Confirm with OK.


    The valid days are collated to a single valid day.
    Note: When you combine valid days, all regular vehicle journeys are set to the remaining
    valid days that use this valid day, and are set daily to the default valid day.

    15.42.7 Creating a vacation day


    Notes: Vacation days can only be created, if you have activated the Calendar / valid
    days add-on (see "Enabling or disabling installed add-ons" on page 886).
    You can only create vacation days when using an annual calendar.
    You can also create vacation days that lie outside of the calendar period.
    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Select the Vacations days tab.
    3. Click the

    Create button.

    The Create vacation/holiday window opens.


    4. Enter the desired data (see "Properties and options of vacation days" on page 1521).
    5. Confirm with OK.
    The vacation day is inserted.

    15.42.8 Properties and options of vacation days

    PTVGROUP

    1521

    15.42.8 Properties and options of vacation days


    Section Basis
    Element

    Description

    Number

    Unique number of the vacation day

    Code

    Code of the vacation day

    Name

    Name of the vacation day

    Validity from

    Time period in which calendar days can be allocated to the vacation


    day
    button to display a calendar in which you can mark the
    Use the
    beginning or the end of the time period.
    Note
    The time period can also lie outside of the calendar period.

    Section Calendar days

    1522

    Element

    Description

    Calendar

    Section where you can allocate relevant calendar days to the vacation day.
    You can select calendar days by clicking the desired date in the
    calendar.
    Selected calendar days are highlighted in green.
    Weekdays and Sundays that have not been selected are white,
    Saturdays that have not been selected are highlighted in gray.
    Days outside of the valid time period are red and cannot be
    selected.
    Note
    If you click a calendar day which is selected already, the allocation of
    the calendar day will be canceled.
    Tip
    You can also select calendar days using additional options, which
    you open via the Extend button (see "Additional options" on page
    1523).

    Extend/
    reduce

    Use the Extend button to display additional options for the selection
    of calendar days (see "Additional options" on page 1523). Use the
    Reduce button to hide the additional options.

    PTVGROUP

    15.42.8 Properties and options of vacation days


    Additional options

    Use the additional options to select calendar days that meet specific requirements. You can
    add or remove the selected calendar days from the calendar.
    There are three kinds of rules:
    Time period (all days within a certain period)
    Weekdays (certain weekdays)
    Vacation days (use existing vacation day calendar)
    Buttons in the lower right section
    Element

    Description

    Apply

    Use the button to display the days selected according to the set options as days which shall be added to the selection as relevant calendar days. These days are highlighted in light green.
    Note
    The display is just a preview. The displayed days will only be allocated to the vacation day as relevant calendar days, if you click the
    Show selection button.

    Delete

    Use the button to display the days selected according to the set options as days which shall be removed from the selection as relevant
    calendar days. These days are highlighted in light red.
    Note
    The display is just a preview. The displayed days will only be removed from the selection of relevant calendar days, if you click the
    Show selection button.

    Show selection

    The selection of calendar days set via the Apply or Delete buttons is
    applied, i.e. the calendar days are added to or removed from the previous selection of relevant calendar days.

    PTVGROUP

    1523

    15.42.8 Properties and options of vacation days


    Section

    Description

    Time period

    Validity from
    Time period within the calendar period for which calendar days are
    selected
    button to display a calendar in which you can mark the
    Use the
    beginning or the end of the time period.

    Weekdays

    Mon-Sun
    Select the weekdays which shall be taken into account for the selection.
    Uncheck all/check all
    Use the buttons to select all weekdays simultaneously or to switch off
    the selection of all weekdays.
    Each < n >th occurrence
    Use the option to specify the recurrence pattern with which the selected weekdays will be used for the selection.
    Example
    If you select the weekdays Tuesday and Thursday and specify each
    3rd occurrence, Tuesdays and Thursdays will be selected every
    three weeks within the desired time period.
    Week
    Use the option to determine specific weeks per month, whose selected weekdays will be used for the selection.
    1 corresponds to the first week of the month, 2 to the second week
    and so on.
    L always means the last week of the month, whether the month has
    four or five weeks.
    Example
    If the weekdays Monday and Tuesday and week 1 and 2 have been
    selected, all Mondays and Tuesdays of the first two weeks of the
    month will be selected within the desired time period.
    Note
    If the month starts with a Thursday, the selection starts with the Monday and Tuesday of the second week.

    1524

    PTVGROUP

    15.42.9 Editing attribute values of vacation days


    Section

    Description

    Vacation days

    Apply
    If the option has been selected, the same selection of calendar days
    will be used as for an existing vacation day.
    Use the drop-down list, to select the vacation day that shall be used
    as selection criterion.
    On vacation days
    If the option has been selected, the selection of calendar days is
    exactly the same as the one for the set vacation day.
    Except vacation days
    If the option has been selected, the selection of calendar days corresponds to the days which are not selected for the set vacation day
    (complement).

    15.42.9 Editing attribute values of vacation days


    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Select the Vacations days tab.
    3. In the drop-down list, select the desired vacation day.
    4. Click the

    Edit button.

    The Edit vacation/holiday window opens.


    5. Edit the values of the desired attributes (see "Properties and options of vacation days" on
    page 1521).
    6. Confirm with OK.
    The attribute values are edited.

    15.42.10 Deleting vacation days


    1. In the Network menu, select the PuT valid days entry.
    The Valid days window opens.
    2. Select the Vacations days tab.
    3. In the drop-down list, select the desired vacation day.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    4. Click the

    PTVGROUP

    Delete button.

    1525

    15.43 Using the Timetable editor


    5. Confirm with OK.
    The vacation day is deleted.

    15.43

    Using the Timetable editor


    According to the line hierarchy the timetable in PuT in Visum is set up hierarchically. The line
    route contains the information on the location, the time profile accounts for relative time specifications and the vehicle journeys and their vehicle journey sections provide valid day, departure time and the traversed sections of the line route. All four object types together provide the
    timetable and thus information, where and when PuT vehicle journeys take place (see Fundamentals: Chpt. 3.1.14.1 , page 68).
    In the Timetable editor, you can display and edit the vehicle journeys or vehicle journey sections of selected lines, line routes and time profiles and edit them. On the one hand, the tabular timetable provides a tabular view of all timetable data, on the one hand, the graphical
    timetable provides a graphical view of the vehicle journey items (see Fundamentals: Chpt.
    12.16 , page 776). In the Timetable editor you find these features, among others:
    Different views of selected timetable data
    User-defined layout and graphic settings
    Editing timetable data (creating, shifting, deleting vehicle journeys)
    Creating of timetables
    Sorting displayed vehicle journeys in various ways
    Saving timetable data and export to other programs
    Graphically displaying the results of the line blocking operation (see "Displaying line
    blocks in the block view" on page 2119)
    Notes: You can modify the network as desired while the Timetable editor is open.
    Changes resulting from the modification of the network will be visible immediately in the
    Timetable editor.

    15.43.1 Opening the Timetable editor


    In Visum the Timetable editor opens in a separate window.
    1. In the Windows toolbar, click the

    Open Timetable editor icon.

    Tip: Alternatively, from the Edit menu, choose Timetable editor.


    The Timetable editor window opens. If a Timetable editor has already been opened, a
    query opens. The options displayed depend on the context in which the Timetable editor
    has been opened.
    2. Confirm the selected option.

    1526

    PTVGROUP

    15.43.2 Selecting line(s) to be displayed in the Timetable editor


    Element

    Description

    Delete line selection

    Discards current line selection. In the Timetable editor no lines


    are displayed.

    Replace line selec- Discards current line selection. In the Timetable editor only the
    tion
    time profiles of the selected lines are displayed.
    Extend line selec- The time profiles of the currently selected lines are displayed in
    tion
    addition to those of the already displayed line routes.
    Go to open Timetable editor

    The current selection persists. The Timetable editor is displayed


    on top.

    Tips: You can also display network objects marked in the network directly in the Timetable editor (see "Stops: Opening the Timetable editor" on page 1246 and "Stop areas:
    Opening the Timetable editor" on page 1261), (see "Line routes: Opening the Timetable
    editor" on page 1358 and "Lines: Opening the Timetable editor" on page 1299).
    Additionally you can open the Timetable editor with the current selection in the context
    menu of the lists of the line hierarchy.

    15.43.2 Selecting line(s) to be displayed in the Timetable editor


    You can select lines that shall be displayed in the Timetable editor.
    1. In the toolbar of the navigator (see "The Timetable editor window" on page 1530) , click the
    Basic line selection.
    The Line selection window opens. The window lists all lines which exist in the network.

    PTVGROUP

    1527

    15.43.2 Selecting line(s) to be displayed in the Timetable editor


    Notes: Click the plus sign to display subordinate elements.
    In case of a large number of lines, you can find a line by entering the beginning of the
    line name in the input field. In the navigator, the line will be displayed at the top of the
    list and can be selected.
    If vehicle journeys are marked in the Timetable editor, the related entries are displayed in bold in the line selection window.
    2. Select the lines, line routes, time profiles and directions whose vehicle journeys you want to
    display in the Timetable editor.
    Element

    Description
    Show or hide, so that only active lines are shown in the navigator (see
    "Using filters to set network objects active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page 1033).
    Right-click the icon to open the filter editing window for lines.
    Note
    The function is activated if the icon is pressed (red).
    Selects all lines and subordinated network objects in the network for the display
    Removes all lines and subordinated network objects in the network from the
    selection
    Invert the current selection

    3. Confirm with OK.


    The selected lines are displayed in the navigator and in child window (4).
    4. If required, adjust your selection by selecting or removing single objects with the mouse.
    5. If required, adjust the display of the navigator using the following icons or via the context
    menu:
    Element Description
    Open all subordinated entries in the navigator
    Tips
    If you want to open the subordinated entries one by one, click the icon.
    If you want to open all subordinated entries, select the Expand partial tree
    entry in the context menu.
    Close all subordinated entries in the navigator
    Tips
    If you want to close the subordinated entries one by one, click the

    1528

    icon.

    PTVGROUP

    15.43.2 Selecting line(s) to be displayed in the Timetable editor


    Element Description
    f you want to close all subordinated entries, select the Reduce partial tree
    entry in the context menu.
    Display all vehicle journeys of the displayed line and all subordinated network objects in window 8 and 9
    Display no vehicle journey
    Invert the current selection
    Hide the line selection display
    Tip
    When the navigator is hidden, the icon is located to the left of the window. A
    further click on the icon reopens the navigator.
    The vehicle journeys of the selected objects are displayed in window 7 and 8.
    Notes: You can edit lines, line routes, time profiles and directions directly in the Timetable editor, if you open the context menu of the navigator with a right-click on the desired
    object.
    For individual time profiles you can insert vehicle journeys directly in the navigator via
    the Create vehicle journey(s) entry of the context menu.
    Use the Delete entry to delete the selected object (not the directions). Use the Edit entry
    to open the edit window of the respective object. The Timetable display is updated
    immediately.
    Time profiles coupled with the currently selected time profile, can be displayed via the
    Show coupled time profiles entry in the context menu in the timetable.

    PTVGROUP

    1529

    15.43.3 The Timetable editor window

    15.43.3 The Timetable editor window

    (1) The Timetable editor toolbar


    Use the Timetable editor toolbar to call specific program functionalities.
    Note: You can adjust the position and the size of the Timetable editor toolbar individually
    (see "Modifying toolbars and windows" on page 824).
    (2) The navigator
    Here you can select the lines whose vehicle journeys you want to display, and, if necessary,
    edit in the tabular or graphical timetable.
    (3) The navigator toolbar
    Use the toolbar to select lines and specify the display in the navigator.
    (4) The tabs
    Tab: Tabular timetable
    The tab displays the vehicle journeys and vehicle journey sections of the selected lines in the
    form of a table. The tabular timetable is divided in four child windows.

    1530

    PTVGROUP

    15.43.4 Managing vehicle journeys and vehicle journey sections


    Tabs: Graphical timetable (vertical), graphical timetable (horizontal)
    The tabs display the vehicle journeys and vehicle journey sections of the selected lines graphically.
    Tab: Block view PuT line blocks
    Here you can graphically display the results of the line blocking operation (see "Displaying
    line blocks in the block view" on page 2119).
    (5) Attributes of vehicle journeys and vehicle journey sections
    Here you can select the attributes of vehicle journeys and vehicle journey sections that you
    want to display in the tabular timetable.
    (6) The sequence of stop events
    Here, the stop events (stops or stop points) of the selected lines are listed. In this child window,
    you can specify the order of the displayed stop events and select the stop event attributes that
    you want to display.
    (7) Vehicle journeys and vehicle journey sections
    Here, the vehicle journeys and vehicle journey sections of the selected lines are displayed
    with their attribute values. If required, you can edit the attribute values right here. You can also
    edit vehicle journeys and vehicle journey sections.
    (8) Attributes of vehicle journey items
    Here, you can select the attributes of the vehicle journey items, whose values you want to display per stop event.
    Note: The columns of window (7) and (8) can only be scrolled together, as they correspond.

    15.43.4 Managing vehicle journeys and vehicle journey sections


    Vehicle journeys are the basic objects to describe the timetable. Each vehicle journey uses
    exactly one time profile. In most cases, all vehicle journeys of a line route use the same time
    profile if the time profile does not vary in the time of day, for example (see Fundamentals: Chpt.
    3.1.14.1 , page 68).
    Vehicle journey sections divide a vehicle journey, if attributes of the vehicle journey differ on
    a section. For the vehicle journey sections of a vehicle journey, you can specify different valid
    days and vehicle combinations (see Fundamentals: Chpt. 3.1.14.1 , page 68).
    You can create vehicle journeys and vehicle journey sections (see "Creating a vehicle journey" on page 1534 and "Creating vehicle journey sections" on page 1551), edit their attributes
    (see "Editing vehicle journeys" on page 1541) and delete them (see "Deleting vehicle journey
    sections" on page 1557). Moreover, you can create and display regular services.
    Both, in the tabular timetable and in the graphical timetable, you can switch between the
    Vehicle journeys view and the Vehicle journey sections view.
    In the Timetable editor toolbar, select the desired view from the drop-down list.

    PTVGROUP

    1531

    15.43.4 Managing vehicle journeys and vehicle journey sections

    The desired selection is displayed.


    Note: The views only differ, if vehicle journey sections were inserted in vehicle journey
    (see "Creating vehicle journey sections" on page 1551).
    Example: Vehicle journeys
    If you select the Vehicle journeys view, the Timetable editor displays the selected vehicle journeys.

    In the Vehicle journeys view, each column of windows 7 and 8 corresponds to a vehicle journey. The example shows three vehicle journeys. Window 7 displays the attributes of the
    vehicle journey, window 8 displays the stop points of the vehicle journey.
    In the Vehicle journey sections row, you can see that vehicle journey number 2 has two
    vehicle journey sections and the other two vehicle journeys have just one.
    Example: Vehicle journey sections
    If you select the Vehicle journey sections view, the Timetable editor displays the selected
    vehicle journey sections.

    1532

    PTVGROUP

    15.43.4.1 Showing only active vehicle journeys

    In the Vehicle journey sections view, you can see the vehicle journeys and their attributes as
    well as the vehicle journey sections of each vehicle journey. In the example, the vehicle journey number 2 has two vehicle journey sections. The first one has the start stop point 10 A-village and the end stop point 20 B-village, the second one has the start stop point 20 B-village
    and the end stop point 40 X-city. The names of start and end stop points consist of the stop
    point attributes number and code or number and name, if no code is specified.
    The arrival and departure times are calculated automatically.
    Note: The views of the vehicle journeys 1 and 3 are identical to the Vehicle journeys
    view, as both vehicle journeys have only one vehicle journey section.
    15.43.4.1 Showing only active vehicle journeys
    You can restrict the display of the Timetable editor to active vehicle journeys only.
    1. Make sure that the desired lines are displayed in the Timetable editor (see "Selecting line
    (s) to be displayed in the Timetable editor" on page 1527).
    2. In the Timetable editor toolbar, click the

    Show only active vehicle journeys icon.

    Note: The Timetable editor considers the settings of the line filter set for vehicle journeys
    (see "Working with hierarchical filters" on page 1016).
    The timetable shows active vehicle journeys only.

    PTVGROUP

    1533

    15.43.4.2 Creating a vehicle journey


    15.43.4.2 Creating a vehicle journey
    You can create either a single vehicle journey or multiple regular services (see "Creating regular services" on page 1536). If you want to insert a single vehicle journey, proceed as follows.
    1. Make sure that the desired lines are displayed in the Timetable editor (see "Selecting line
    (s) to be displayed in the Timetable editor" on page 1527).
    2. In the Timetable editor toolbar, click the

    Create new vehicle journey(s) icon.

    Tip: Alternatively you can call the function via the Timetable editor> Create vehicle
    journey menu or via the context menu of the navigator for individual time profiles.
    The Create vehicle journey(s) window opens.

    3. Select the Basis tab.


    4. Make the desired changes.
    Element

    Description

    Number

    Display of the vehicle journey number


    Note
    Visum automatically allocates the next free number after the
    highest existing number. You can edit the number. However,
    each number can only exist once.

    Name

    1534

    Name of the vehicle journey

    PTVGROUP

    15.43.4.2 Creating a vehicle journey


    Element

    Description

    Line

    Line to which the vehicle journey shall be allocated

    Direction

    Direction of the line route

    Line route

    Line route which is displayed in the timetable

    Time profile

    Time profile which is displayed in the timetable

    Operator

    Operator of the line


    Note
    If you modify the standard operator of a line, the operator will
    not be adjusted for associated existing vehicle journeys.

    Service trip pattern


    no.

    Number of the service trip pattern

    Vehicle combination Vehicle combination


    Valid day

    Valid day of the vehicle journey

    AddValue 1-3

    Free attributes which you can use to enter additional values.

    Start stop point

    Stop point of the selected line route, at which the vehicle journey begins. Enter a departure time at the selected start stop
    point.
    Notes
    The name of the start stop point consists of the stop point attributes number and code or number and name, if no code is specified.
    If the line route or the time profile of a vehicle journey is modified, the previous start stop point is kept, if possible.

    End stop point

    Stop point of the selected line route, at which the vehicle journey ends
    Notes
    The arrival time at the end stop point is calculated automatically.
    The name of the end stop point consists of the stop point attributes number and code or number and name, if no code is specified.
    If the line route or the time profile of a vehicle journey is modified, the previous end stop point is kept, if possible.

    Ref stop point

    Stop point of the selected line route, used to fixate the departure time (see "Setting reference stop points" on page 1327)
    Note
    By default, the start stop point is the reference stop point. Enter
    the departure time at the chosen reference stop point if it deviates from the start stop point. The departure time at the start stop
    point will then be updated.

    PTVGROUP

    1535

    15.43.4.3 Duplicating vehicle journey


    5. Confirm with OK.
    The vehicle journey is added to the timetable.
    Note: If you insert a vehicle journey which lies within a coupled section, a synchronized
    vehicle journey will be inserted on the coupled time profile, too. Once you confirm a
    query, the Edit coupled vehicle journey window opens, where you can directly edit the
    attributes of the new vehicle journey on the coupled time profile.
    15.43.4.3 Duplicating vehicle journey
    You can duplicate an already existing vehicle journey. All related vehicle journey sections will
    equally be duplicated. If the vehicle journey is coupled to another vehicle journey, the coupled
    vehicle journey is also duplicated with all attributes.
    1. Mark the vehicle journey that you want to duplicate (see "Marking vehicle journeys" on
    page 1539).
    Notes: This functionality is only available as long as just a single vehicle journey has
    been marked.
    In the regular service mode, this functionality is not available.
    2. Right-click the marked vehicle journey.
    A shortcut menu opens.
    3. Select the Duplicate vehicle journey entry.
    The new vehicle journey is inserted and marked.
    Note: The number of the newly created vehicle journey is allocated according to the setting under Edit> User Preferences>, Network> Lines entry.
    15.43.4.4 Finding vehicle journeys
    Finding vehicle journeys in the tabular timetable or in the graphical timetable
    1. Click in the tabular timetable or in the graphical timetable.
    2. Press F3.
    The Find vehicle journey window opens (see Finding network objects in the network page
    999).
    Finding vehicle journeys in the Network editor window
    You can search for vehicle journeys in the Network editor window (see "Finding network
    objects in the network" on page 999).
    15.43.4.5 Creating regular services
    You can create multiple vehicle journeys which depart in regular intervals.

    1536

    PTVGROUP

    15.43.4.5 Creating regular services


    1. Make sure that the desired lines are displayed in the Timetable editor (see "Selecting line
    (s) to be displayed in the Timetable editor" on page 1527).
    2. In the Timetable editor toolbar, click the

    Create new vehicle journey(s) icon.

    Tip: Alternatively, you can call the function via the Edit> Create vehicle journey
    menu.
    The Create vehicle journey(s) window opens.
    3. Make the desired changes in the Basis tab (see "Creating a vehicle journey" on page
    1534).
    Note: The settings in the Basis tab apply to all regular services. Only the Number and
    the start time apply to the first regular service. Visum automatically numbers the regular services consecutively. If you have specified the respective setting, only odd or
    only even numbers will be allocated (see "Specifying default values for lines and line
    routes" on page 1291). Already allocated numbers will be skipped.
    4. Select the Regular services tab.

    5. Make the desired changes.

    PTVGROUP

    1537

    15.43.4.6 Editing the values of vehicle journey attributes


    Element

    Description

    Create regular ser- If the option has been selected, you can specify settings in the
    vices
    Regular services tab to insert multiple vehicle journeys.
    Note
    As soon as you switch back to the Basis tab to modify settings,
    the label of the Regular services tab will be displayed in red, if
    the option has been selected.
    Time interval for
    regular service

    Headway start
    Departure time of the first regular service The departure time corresponds to the departure time at the start stop point, which will
    also be changed if the headway start is changed.
    Headway end
    Time of the last departure

    Time difference to Regular service


    previous vehicle
    Enter up to 3 regular service times (in minutes) which are each
    journey
    interpreted as difference to the previous vehicle journey.
    Note
    The input boxes are accessible one after the other (left to right), if
    you click in the list of the generated vehicle journeys or in other
    input fields in the meantime. The vehicle journeys will then be listed with their departure times. The list is adjusted upon changes
    to the input data.
    Example
    If you enter a headway start of 2:00, and regular services of 30
    and 10 min, the first regular service will depart at 2:00 o'clock, the
    second on after 30 min at 2:30, the third one after 10 min at 2:40
    and the fourth on after 30 min at 3:10 etc.
    Check all/Uncheck all

    Use these buttons to select all listed vehicle journeys at the same
    time or to remove them from the selection.

    Notes: If you do not want to create a vehicle journey, deselect the Generate vehicle
    journey option.
    At the lower right of the window, the number of vehicle journeys to be inserted is displayed.
    6. Confirm with OK.
    The regular services are added to the timetable.
    15.43.4.6 Editing the values of vehicle journey attributes
    You can create user-defined attributes for vehicle journeys (see "Managing user-defined attributes" on page 973). If user-defined vehicle journey attributes have been created, you can

    1538

    PTVGROUP

    15.43.4.7 Marking vehicle journeys


    allocate values to the attributes when creating new vehicle journeys and edit them afterwards.
    1. In the Timetable editor, mark the vehicle journeys whose attribute values you want to edit
    (see "Marking vehicle journeys" on page 1539).
    2. In the Timetable editor toolbar, click the

    Edit marked vehicle journeys icon.

    The Edit vehicle journey(s) window opens.


    3. Select the User-defined attributes tab.
    4. If required, select the attributes whose values you want to edit by clicking the Attribute
    selection button (see "The window used for the selection of one attribute" on page 963).
    5. Enter the desired values for the user-defined attributes right in the list.
    6. Confirm with OK.
    The new values are applied.
    Tip: You can also enter values for user-defined vehicle journey attributes when creating
    a vehicle journey (see "Creating a vehicle journey" on page 1534).
    15.43.4.7 Marking vehicle journeys
    You can mark vehicle journeys as follows in order to edit them afterwards.
    Notes: Marked vehicle journeys are highlighted. You can edit the settings of the markings
    (see "Setting the graphic parameters of the tabular timetable" on page 1573).
    Vehicle journeys marked in the tabular timetable are also marked in the graphical timetable and vice versa.
    If vehicle journeys are marked, all associated vehicle journey sections of the marked
    vehicle journeys are also marked.
    If vehicle journeys are marked in the Timetable editor, the related entries are displayed in
    bold in the line selection window.
    Marking

    Description

    Marking one
    vehicle journey

    Tabular timetable
    Mark a vehicle journey by clicking the desired column.
    Tip
    If you click the column once more, it will no longer be marked.
    Graphical timetable
    Click the vehicle journey items to mark a vehicle journey.

    Marking multiple
    vehicle journeys.

    PTVGROUP

    Tabular timetable
    Mark multiple vehicle journeys by holding down the C TRL key and
    clicking several columns one after the other. All marked columns will

    1539

    15.43.4.7 Marking vehicle journeys


    Marking

    Description
    be marked apart from the last one where only the header will be highlighted.
    Tip
    If you click a marked column once more, it will no longer be marked.
    Graphical timetable
    To mark several vehicle journeys, keep the C TRL key pressed and
    click the desired vehicle journey items in turn.
    Tip
    Alternatively, you can draw a rectangle with the mouse in the Graphical timetable. The vehicle journeys contained in the rectangle will
    be marked.

    Marking several
    adjoining vehicle
    journeys

    Tabular timetable
    Mark several adjoining vehicle journeys by clicking the first column,
    holding down the SHIFT key and then clicking the last column.

    Marking coupled
    vehicle journeys.

    You can mark all vehicle journeys which are coupled with the
    currently marked vehicle journey by selecting the Find coupled
    vehicle journey entry in the context menu.
    Notes
    If a coupled vehicle journey has not been displayed in the timetable
    so far, a query opens. When you confirm the query, the vehicle journey will be displayed and marked. Even indirectly coupled vehicle
    journeys are marked, i.e. vehicle journeys which are not coupled
    directly but with a joint other vehicle journey.
    Tip
    Alternatively, you can call the functionality via C TRL + F3.

    Marking all vehicle Tabular timetable and Graphical timetable


    journeys
    If you want to mark all vehicle journeys, click the
    journeys icon.
    Inverting vehicle
    journey markings

    Mark all vehicle

    Tabular timetable and Graphical timetable


    If you want to invert the current markings of vehicle journeys, click the
    Invert vehicle journey markings icon.
    Tip
    Alternatively, you can invert the markings in the Tabular timetable
    via the Invert vehicle journey markings entry in the context menu.

    Removing marking Tabular timetable and Graphical timetable


    (s)
    If you want to deactivate all vehicle journey markings, click the
    Delete vehicle journey markings icon.

    1540

    PTVGROUP

    15.43.4.8 Editing vehicle journeys


    15.43.4.8 Editing vehicle journeys
    You can edit the attribute values of multiple vehicle journeys at the same time. This also applies to user-defined attributes (if provided).
    Tips: You can also edit the attribute values of a vehicle journey directly in the list.
    If you want to edit only a single vehicle trip, you can open the edit window by doubleclicking the corresponding vehicle journey.
    1. Mark the vehicle journey(s) that you want to edit by clicking the respective header of the
    column (see "Marking vehicle journeys" on page 1539).
    2. In the Timetable editor toolbar, click the

    Edit marked vehicle journeys icon.

    The Edit vehicle journey or Create vehicle journeys window opens.


    Note: The attributes in the Edit vehicle journey(s) and the Create vehicle journey(s)
    window are identical.
    3. Make the desired settings (see "Creating a vehicle journey" on page 1534).
    Notes: If attributes of marked vehicle journeys differ, a * is displayed.
    If a single vehicle journey is marked, you can create regular services afterwards (see
    "Creating regular services" on page 1536).
    If you modify a line or a line route of a vehicle journey in this manner, the vehicle journey will be moved to the first time profile of the target line or line route. This might lead
    to a change in the course of the vehicle journey. You can also move a vehicle journey
    together with its line routes and time profiles (see "Shifting vehicle journeys to a different line" on page 1543).
    4. Confirm with OK.
    The changes are applied.
    Note: In the Timetable editor you can also open the edit window for time profiles of a
    vehicle journey and edit them directly. The Edit time profile entry in the context menu is
    available if exactly one vehicle journey or vehicle journey sections of a vehicle journey
    are marked in the Timetable editor.
    15.43.4.9 Editing the attribute values of all or all active vehicle journeys
    Note: If there are no passive vehicle journeys in the network, all vehicle journeys will be
    changed. Markings of vehicle journeys are ignored.
    1. If required, use the line filter to set active the vehicle journeys (see "Using filters to set network objects active or passive" on page 1008), whose attribute values you want to edit.
    The selected vehicle journeys are active.

    PTVGROUP

    1541

    15.43.4.10 Shifting vehicle journeys temporally


    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Vehicle journeys entry.
    The Multi-edit vehicle journeys window opens.
    4. Specify whether you want to edit all or all active vehicle journeys.
    Element

    Description

    Only active If the option has been selected, only active vehicle journeys will be taken
    ones
    into account.
    5. Edit the values of the desired attributes (see "Creating a vehicle journey" on page 1534 and
    "Editing attribute values of network objects" on page 983).
    The attribute values are edited.
    6. Click the Close button.
    15.43.4.10 Shifting vehicle journeys temporally
    You can shift vehicle journeys in the tabular or in the graphical timetable.
    1. Mark the vehicle journeys that you want to edit (see "Marking vehicle journeys" on page
    1539).
    2. In the Timetable editor toolbar, click the

    Shift marked vehicle journeys icon.

    Tip: Alternatively, you can call the functionality via the Shift marked vehicle journeys
    entry in the context menu.
    The Shift vehicle journey(s) window opens.

    3. Make the desired changes.

    1542

    PTVGROUP

    15.43.4.11 Shifting vehicle journeys to a different line


    Element

    Description

    Shift vehicle journey(s) by

    Enter the time by which you want to shift the marked vehicle journeys. You can enter a time in hours (h), minutes (min) and
    seconds (s).
    Example: 1h1min1s.
    Tip
    If you do not enter a unit, the value is interpreted as minutes.
    Note
    You cannot change the time of a vehicle journey to a earlier point
    in time which is before 00:00 (12:00 AM). If you try to do this, a
    warning is displayed. The current time will not be changed.

    Earlier/later

    Depending on the selected option, the selected vehicle journeys


    are shifted on the time axis in the desired direction.

    4. Confirm with OK.


    The vehicle journeys are shifted.
    15.43.4.11 Shifting vehicle journeys to a different line
    You can shift vehicle journeys and their line routes and time profiles to a different line.
    1. Mark the vehicle journeys that you want to shift (see "Marking vehicle journeys" on page
    1539).
    2. With the right mouse button, click the column header of a marked vehicle journey.
    The shortcut menu opens.
    3. Select the Shift vehicle journey to a different line entry.
    The Shift vehicle journey to a different line window opens.
    4. Make the desired changes.
    Element

    Description

    Target line

    Use the drop-down list to select the line to which you want to
    shift the vehicle journey.

    Show only active lines

    If this option is selected, only for lines will be displayed in the


    list.

    After shifting, delete


    empty time profiles
    and line routes

    If the option has been selected, empty time profiles and line
    routes of the marked vehicle journeys will be deleted after
    shifting.

    5. Confirm with OK.


    The vehicle journeys and their line routes and time profiles are shifted to the desired line. If
    necessary, stop points, links and turns of the vehicle journeys will be opened for the transport

    PTVGROUP

    1543

    15.43.4.12 Coupling vehicle journeys in pairs


    system of the target line. Couplings will not be copied. Vehicle journeys with coupled time profiles will be deleted, where applicable.
    15.43.4.12 Coupling vehicle journeys in pairs
    In the tabular timetable, you can couple two marked vehicle journeys of different time profiles
    that overlap.
    1. Mark the vehicle journeys that you want to edit (see "Marking vehicle journeys" on page
    1539).
    The desired vehicle journeys are marked.
    2. Right-click the marked vehicle journeys.
    A shortcut menu opens.
    3. Select the Couple marked vehicle journeys entry.
    The Couple the vehicle journeys <Number> and <Number> window opens.

    4. Make the desired changes.


    Element

    Description

    Coupled section

    From/to
    Here you select the section on which you want to couple the
    vehicle journeys.

    Vehicle journey
    pairs in the coupled section

    In the Coupling column, you can specify for each vehicle journey
    pair, that the respective vehicle journeys shall be coupled.
    Note
    Via the Check all and Uncheck all buttons you can select or
    deselect all vehicle journey pairs simultaneously.

    5. Confirm with OK.

    1544

    PTVGROUP

    15.43.4.13 Separating coupled vehicle journeys or shortening the coupling


    The vehicle journeys are coupled.
    Note: The Coupled row in the Vehicle journeys view indicates, whether a vehicle journey is coupled (1) or not (0).
    15.43.4.13 Separating coupled vehicle journeys or shortening the coupling
    In the tabular timetable, you can separate coupled vehicle journeys or shorten the coupled section as follows.
    1. Mark the vehicle journeys that you want to separate (see "Marking vehicle journeys" on
    page 1539).
    2. Right-click the marked vehicle journeys.
    A context menu opens.
    3. Select the Separate marked vehicle journeys entry.
    The Separate vehicle journeys <Number> and <Number> window opens.

    4. Make the desired changes.


    Element

    Description

    Coupling

    Release
    If the option has been selected, the coupling is removed.
    Shorten to
    If the option has been selected, you can shorten the coupled section From/To .

    Coupled section

    From/to
    Here you select the section on which you want to shorten the
    coupling.

    PTVGROUP

    1545

    15.43.4.14 Editing regular services


    Element

    Description

    Vehicle journey
    pairs in the coupled section

    In the Separate column, you can specify for each vehicle journey
    pair, that the respective coupling shall be removed.
    Note
    Via the Check all and Uncheck all buttons you can select or
    deselect all vehicle journey pairs simultaneously.

    5. Confirm with OK.


    The coupling is removed or the coupling is shortened.
    15.43.4.14 Editing regular services
    In the tabular timetable, you can display regular vehicle journeys individually or in the regular
    services mode. If you want to display the vehicle journeys in the regular services mode, proceed as follows.
    In the toolbar, click the

    Regular services mode on/off icon.

    The regular services are displayed in the regular services mode.


    Example
    The display of individual vehicle journeys looks, for example, like this:

    In the regular service mode, the display of the same vehicle journeys looks like this:

    1546

    PTVGROUP

    15.43.4.14 Editing regular services

    The first four rows are grayed out. They provide information on the Headway start (departure
    time of the first vehicle journey at the current start stop point), the Headway end (departure
    time of the last vehicle journey at the current start stop point), the Headway time (interval between two regular services) and the Number of vehicle journeys.
    Notes: If attributes of marked vehicle journeys differ, a * is displayed.
    In case of irregular vehicle journeys, the headway start is identical to the headway end
    and the headway time is 0.
    Editing times of regular services
    You can also edit regular services directly in the tabular timetable if you double-click the desired cell. The following applies to temporal changes of regular services:
    The number of vehicle journeys resulting from a changed headway time is automatically
    calculated and displayed.
    If you edit the headway start, the interval is shifted while the length and the headway time
    remain the same.
    If you edit the headway end, the vehicle journey supply changes, taking into account the
    current headway time. A 1h headway from 6 to 10 oclock, for example, generates a new
    headway end of 11 o'clock which results in an additional vehicle journey.
    If you want to shorten a regular service supply at the beginning, you should first increase
    the headway start, i.e. move it forward, and then delete the vehicle journeys which have
    moved to the end by resetting the headway end.
    Displaying service trip patterns
    The Calculate service trip patterns operation divides vehicle journeys into service trip patterns (see "Calculate service trip patterns" on page 2086). If you have calculated the procedure or have allocated service trip pattern numbers from other sources, you can display the
    regular services in the tabular timetable arranged by service trip pattern numbers.

    PTVGROUP

    1547

    15.43.4.14 Editing regular services


    1. In the Timetable editor menu, select the Parameters entry.
    The Parameters window opens.
    2. Make the desired changes.
    Element

    Description

    Service trip patterns

    If the option has been selected, vehicle journeys with the same
    service trip pattern number are displayed in a shared column
    (see "Display by service trip pattern numbers" on page 1549).
    Tip
    You can edit the Service trip pattern number row in the tabular
    timetable, if you double-click the respective row (see "Editing the
    service trip pattern number" on page 1550)

    Automatically cal- If the option has been selected, the vehicle journeys are disculated
    played independently of their service trip pattern numbers.
    Consider spatial trip dimensions
    If the option has been selected, only vehicle journeys with identical start and end stops are put together in one regular service
    pattern.
    Note
    In the occurrence of shortened vehicle journeys during off-peak
    hours which match a regular service, the option should not be
    selected so that these vehicle journeys also enter the service pattern.
    Maximize number of vehicle journeys in headway pattern
    If the option has been selected, the regular services with the maximum number of vehicle journeys are displayed as a headway patterns.
    Notes
    Besides constant temporal distances of vehicle journeys changing headway patterns are also permitted. Each time difference
    may occur multiple times (for example, the headway pattern
    6/7/7).
    Maximize temporal dimensions of headway patterns
    If this option has been selected, the regular services which span
    the longest period of time are displayed as headway patterns.
    Identifying service trip patterns with any service interval
    Select this option to group vehicle journeys with the same differences into service trip patterns. The time differences may differ
    between trip patterns.
    Note
    This option is available, if the option Set coordinates of existing

    1548

    PTVGROUP

    15.43.4.14 Editing regular services


    Element

    Description
    centroids is selected.
    Only fractured multiples of the base headway are permitted as
    service intervals for a service trip pattern
    Select this option to specify a base headway that limits the service trip patterns possible. The time difference between vehicle
    journeys of a service trip pattern must be a multiple of the base
    headway or a multiple of half, a third, or a quarter of the base
    headway.
    Note
    This option is available, if the option Set coordinates of existing
    centroids is selected.
    Note
    The following example illustrates the options (see "Example" on
    page 1549).

    3. Confirm with OK.


    Note: The settings in the Line block view tab are described with the line blocking operation (see "Editing the time of the day change" on page 2121).
    Example
    Vehicle jour- A
    ney

    Departure

    6:10
    a.m.

    6:20
    a.m.

    6:30
    a.m.

    6:40
    a.m.

    6:50
    a.m.

    7:00
    a.m.

    7:20
    a.m.

    6:00
    a.m.

    When picking option Maximize number of vehicle journeys in headway pattern, Visum
    displays the A-B-C-D-E-F-G (6 vehicle journeys) headway of 10 minutes and vehicle journey H as single vehicle journey. The A-C-E-G-H headway of 20 minutes contains just 5
    vehicle journeys and is thus not displayed.
    When picking option Maximize temporal dimensions of headway patterns, the 20 minutes headways A-C-E-G-H (1 hour 20 minutes) and B-D-F (40 minutes) will be displayed.
    Display by service trip pattern numbers
    This display is based on the Service trip pattern number as the only criterion for the graphical depiction of the vehicle journeys of a time profile. Vehicle journeys with the same service
    trip pattern number are displayed in one joint column if the data are consistent.
    A service trip pattern is considered consistent if the (possibly virtual) departure times of its
    vehicle journeys fit into a service pattern at the start stop point of the time profile, i.e. the service trip pattern consists of four vehicle journeys at least and all departures have a recurring
    pattern, which must be less than four hours.

    PTVGROUP

    1549

    15.43.4.15 Deleting vehicle journeys


    If these requirements are not met, there has been an input error, since the calculation algorithm does not produce any inconsistent values. They can only result from incorrect manual
    post-processing.
    In this case, a warning will be issued and the service trip pattern numbers of the vehicle journeys concerned are set to 0. Thus, all vehicle journeys of the faulty service trip patterns are displayed individually.
    The Timetable editor interprets a service trip pattern number of zero as if the vehicle journeys does not match any pattern and therefore has to be displayed separately.
    Editing the service trip pattern number
    Since vehicle journeys grouped according to their service trip pattern numbers have less
    attributes in common than vehicle journeys grouped according to the rules applicable so far,
    the number of editable attributes has to be limited considerably.
    Attributes of vehicle journey sections are never modified when edited in this display mode.
    Items are only deleted or added if the headway end is changed.
    Hereby, new vehicle journeys with default values are generated, i.e. on the whole time profile
    and with exactly one vehicle journey section, the valid day daily, the standard operator of the
    associated line and the standard vehicle combination of the time profile.
    15.43.4.15 Deleting vehicle journeys
    Note: Deleting vehicle journeys might affect coupled time profiles (see "Coupling multiple
    time profiles" on page 1331).
    There are several ways to delete vehicle journeys.
    Deleting marked vehicle journeys
    1. Mark the vehicle journeys that you want to delete (see "Marking vehicle journeys" on page
    1539).
    2. Click the

    Delete the marked vehicle journeys icon.

    The marked vehicle journeys are deleted.


    Note: If you want to delete vehicle journeys in the graphical timetable, mark the desired
    vehicle journeys and press the D EL key.
    Deleting all active vehicle journeys
    1. Via filter criteria, set active the vehicle journeys that you want to delete. Filter criteria for
    vehicle journeys can be defined via the hierarchical filter on lines (see "Working with hierarchical filters" on page 1016).
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Vehicle journeys entry.

    1550

    PTVGROUP

    15.43.4.16 Creating vehicle journey sections


    A query opens.
    4. Confirm with OK.
    All active vehicle journeys are deleted.
    15.43.4.16 Creating vehicle journey sections
    Usually there is exactly one vehicle journey section per vehicle journey. It is created automatically when inserting a vehicle journey. But in same cases it makes sense to create several
    vehicle journey sections for one vehicle journey (see Fundamentals: Chpt. 3.1.14.1 , page 68).
    Notes: You can only see the individual vehicle journey sections of a vehicle journey, if
    the Vehicle journey sections view has been selected (see "Managing vehicle journeys
    and vehicle journey sections" on page 1531).
    Creating vehicle journey sections might affect coupled time profiles (see "Coupling multiple time profiles" on page 1331).
    1. Make sure that the desired lines are displayed in the Timetable editor (see "Selecting line
    (s) to be displayed in the Timetable editor" on page 1527).
    2. Mark the vehicle journey section for which you want to create a vehicle journey section by
    clicking the header of the column.
    3. In the Timetable editor toolbar, click the
    vehicle journeys icon.

    Create vehicle journey sections for selected

    Tip: Alternatively, you can add a vehicle journey section to the vehicle journey under
    menu Timetable editor> Create vehicle journey section.
    The vehicle journey section and thus another column is added to the vehicle journey.
    Notes: Based on the line route and the time profile of the vehicle journey, the first
    vehicle journey section column of a vehicle journey contains the original vehicle journey section attributes of the vehicle journey.
    Vehicle journey section attributes which can differ, are marked by a #.
    4. Edit the desired attributes of the newly inserted vehicle journey section by (double)clicking
    the desired cells (see "Editing a vehicle journey section" on page 1551).
    Note: A new vehicle journey section is inserted as a copy of the original vehicle journey. It differs, if one or more attribute values have been changed.
    5. Create further vehicle journey sections, if required.
    15.43.4.17 Editing a vehicle journey section
    Note: Make sure that the Vehicle journey sections view has been selected. Vehicle journey sections are not displayed in the regular services mode.

    PTVGROUP

    1551

    15.43.4.17 Editing a vehicle journey section


    You can edit a vehicle journey section either directly in the tabular timetable or in the Edit
    vehicle journey section <Number vehicle journey (name vehicle journey section)> window. This window is described below.
    1. Make sure that the tabular timetable is open and that vehicle journey sections exist.
    2. In the tabular timetable, right-click the column of the vehicle journey section that you want to
    edit.
    The shortcut menu opens.
    3. In the context menu, select the Edit vehicle journey section <Number vehicle journey
    (name vehicle journey section)> entry.
    Tip: Alternatively, you can right-click the respective vehicle journey in the graphical
    timetable and select the desired subentry under entry Edit vehicle journey sections.
    The Edit vehicle journey section <Number vehicle journey (name vehicle journey section)> window opens. The upper section of the window displays general information on the
    vehicle journey and vehicle journey section which cannot be edited.

    4. Specify the desired settings in the lower section of the window on the Basis tab.

    1552

    Element

    Description

    Vehicle combination

    In the drop-down list, you can select a different vehicle combination for the vehicle journey section.

    Vehicle combination set

    Click the button to change the vehicle combination set.

    Valid day

    In the drop-down list, you can specify a different setting for the
    valid day, if the vehicle journey section is served on deviating

    PTVGROUP

    15.43.4.17 Editing a vehicle journey section


    Element

    Description
    days.

    Pre-preparation
    time

    Here you can specify the specific pre preparation time of the
    vehicle journey section for the line blocking. Line blocking is
    based on vehicle journey sections.
    Note
    You can set a specific preparation time in the Specific layover
    times tab.

    Post preparation
    time

    Here you can specify the specific post preparation time of the
    vehicle journey section for the line blocking. Line blocking is
    based on vehicle journey sections.
    Note
    You can set a specific post preparation time in the Specific layover times tab.

    Start stop point

    Select the start stop point for the vehicle journey section.

    End stop point

    Select the end stop point for the vehicle journey section.

    5. Select the Specific layover times tab.


    6. Make the desired changes.
    Element

    Description

    Use specific preparation time

    If the option has been selected, for each vehicle combination


    the list displays a row for the preparation time. In the Value
    column, you can enter a specific preparation time each.
    If the option has not been selected, the preparation time from
    the Basis tab will be used for all vehicle combinations.

    Use the specific


    post-preparation
    time

    If the option has been selected, for each vehicle combination


    the list displays a row for the post preparation time. In the Value
    column, you can enter a specific post preparation time each.
    If the option has not been selected, the post-preparation time
    from the Basis tab will be used for all vehicle combinations.

    Note: The In vehicle journey set column indicates whether the vehicle combination is
    permitted on the vehicle journey section. The rows are highlighted in yellow accordingly. You can identify allocated vehicle combinations in the Allocated vehicle combinations tab. They are shown in bold. You can sort the entries of the columns In
    vehicle combination set and Allocated vehicle combinations.
    7. Confirm with OK.
    The vehicle journey section is modified according to your specifications.

    PTVGROUP

    1553

    15.43.4.18 Editing the attribute values of all or all active vehicle journey sections
    Note: Based on the line route of the vehicle journey, served stop points of the vehicle journey section are marked by an X in the lower child window. The times of this window are
    generated on the basis of the respective time profile.
    15.43.4.18 Editing the attribute values of all or all active vehicle journey sections
    Note: You can only edit individual vehicle journey sections or all/all active vehicle journey sections. If there are no passive vehicle journey sections in the network, all vehicle
    journey sections will be changed. Markings of vehicle journey sections are ignored.
    1. If required, use the line filter to set active the vehicle journey sections (see "Using filters to
    set network objects active or passive" on page 1008), whose attribute values you want to
    edit.
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Vehicle journey sections entry.
    The Multi-edit vehicle journey sections window opens.
    4. Specify whether you want to edit all or all active vehicle journey sections.
    Element

    Description

    Only active If the option has been selected, only active vehicle journey sections will
    ones
    be taken into account.
    5. Select the Formula tab.
    6. Edit the values of the desired attributes (see "Editing attribute values of network objects" on
    page 983).
    The attribute values are edited.
    7. Click the Close button.
    Note: In the Special functions tab of the same window, you can also Normalize vehicle
    journey sections (see "Normalizing vehicle journey sections" on page 1556), Replace
    vehicle combinations on vehicle journey sections or Delete forced chainings (see
    "Deleting forced chainings" on page 2148).
    15.43.4.19 Replacing vehicle journey combinations on vehicle journey sections
    This functionality is useful if you want to replace a particular vehicle journey combination with
    one or more vehicle journey combinations. Example: If you replace the vehicle combination
    Train on a vehicle journey section with the two vehicle combinations TrainA and TrainB, you
    can treat them separately in line blocking.
    Note: Please note that this feature can lead to changes in costs. In the above example
    the costs of Train are probably not identical with the costs of TrainA and TrainB.

    1554

    PTVGROUP

    15.43.4.19 Replacing vehicle journey combinations on vehicle journey sections


    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Replace vehicle combinations on vehicle journey sections entry.
    The Multi-edit vehicle journey sections window opens. The Special functions tab is displayed. In the drop-down list the Replace vehicle combinations on vehicle journey sections entry is selected.

    3. Make the desired changes.


    Element

    Description

    Only active ones

    If the option has been selected, only active vehicle journey sections will be taken into account.

    Vehicle combination

    Here you select the vehicle combination you want to replace.


    No vehicle combination
    Select this option, if you want to specify a vehicle combination for
    all vehicle journey sections that have no vehicle combination
    (vehicle combination number 0).
    <number and code of vehicle combination>
    Select the vehicle combination you want to replace.
    Example:
    You want to replace the vehicle combination 1Train with the two
    vehicle combinations 2TrainA and 3TrainB. Enter here 1Train.

    Replace by

    <n> x <number and code of vehicle combination>


    or
    <n> x <No vehicle combination>
    Here you select one or several vehicle combinations that are to
    replace the initial vehicle combination. If you replace one vehicle
    combination with several vehicle combinations, for each additional vehicle combination a copy of the initial vehicle journey sec-

    PTVGROUP

    1555

    15.43.4.20 Normalizing vehicle journey sections


    Element

    Description
    tion is created.
    Example (continued):
    Under Replace by specify the following: 1x2TrainA and
    1x3TrainB. In this case Visum replaces the vehicle combination
    1Train by 2TrainA and 3TrainB. You have replaced one
    vehicle combination with two vehicle combinations. Therefore
    Visum creates an additional vehicle journey section.

    4. Click the Replace vehicle combination button.


    The vehicle combination is replaced according to your settings. If you have replaced one
    vehicle combination by several vehicle combinations, Visum creates additional vehicle journey sections.
    15.43.4.20 Normalizing vehicle journey sections
    The normalization is useful for the line blocking procedure. It ensures that each vehicle journey section has the maximum length and removes redundant vehicle journey sections. The
    normalization thus prevents that, during line blocking, an undesirable vehicle change takes
    place at a vehicle journey that has multiple adjoining vehicle journey sections that do not overlap.
    Tip: You can achieve the same effect if you define forced chainings between two adjoining vehicle journey sections (see "Creating a forced chaining " on page 2144).
    Vehicle journey sections with identical vehicle combinations are normalized as a separate
    group.
    The normalization of vehicle journey sections is particularly useful when reading in HAFAS
    data.
    Example: You create a vehicle journey for a bus line with two vehicle journey sections with the
    same vehicle combination. The first vehicle journey section covers the distance between A
    and B where the bus runs from Monday to Friday. The second vehicle journey section covers
    the distance between B and C where the bus runs every day (Monday to Sunday). If you normalize these vehicle journey sections, Visum generates a vehicle journey section of maximum
    length for the distance between A and C for the days Monday to Friday and a second vehicle
    journey section for the distance between B and C for Saturday and Sunday.
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Normalize vehicle journey sections entry.
    The Multi-edit vehicle journey sections window opens. The Special functions tab is displayed. In the drop-down list, the Normalize vehicle journey sections entry is selected.
    3. Specify whether you want to normalize all or all active vehicle journey sections.

    1556

    PTVGROUP

    15.43.4.21 Deleting vehicle journey sections


    Element

    Description

    Only active If the option has been selected, inactive vehicle journey sections are ignoones
    red during the normalization.
    4. Click the Normalize button.
    The vehicle journey sections are normalized.
    15.43.4.21 Deleting vehicle journey sections
    Note: Creating vehicle journey sections might affect coupled time profiles (see "Coupling
    multiple time profiles" on page 1331).
    There are several ways to delete vehicle journey sections.
    Deleting a vehicle journey section
    1. In the tabular timetable, right-click the vehicle journey section that you want to delete.
    A shortcut menu opens.
    2. Select the Delete vehicle journey section <Number vehicle journey; number vehicle
    journey section> entry.
    Tip: Alternatively, you can right-click the respective vehicle journey in the graphical
    timetable and select the desired subentry under entry Delete vehicle journey sections.
    The vehicle journey section is deleted.
    Deleting vehicle journey sections of marked vehicle journeys
    1. Mark the vehicle journeys whose vehicle journey sections you want to delete by clicking the
    header of the column.
    2. Click the

    Delete vehicle journey sections of marked vehicle journeys icon.

    Tip: Alternatively you can delete the vehicle journey sections via the Timetable
    editor> Delete vehicle journey section menu command.
    The vehicle journey sections are deleted.
    Deleting all active vehicle journey sections
    1. Select the vehicle journey sections that you want to delete via filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    2. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    3. Select the Multi-edit> Vehicle journey sections entry.
    PTVGROUP

    1557

    15.43.5 Calculating stop sequences hierarchically


    A query opens.
    4. Confirm with OK.
    All active vehicle journey sections are deleted.

    15.43.5 Calculating stop sequences hierarchically


    Note: In the timetable, you can either display the stop event sequence based on stop
    points or based on stops. You can switch between the two views using the
    sequence according to stop points/stops icon.

    Stop

    You can calculate the stop sequence hierarchically. The display of the tabular timetable and
    the graphical timetable changes accordingly.
    1. Make sure that the desired lines are displayed in the Timetable editor (see "Selecting line
    (s) to be displayed in the Timetable editor" on page 1527).
    2. In the Timetable editor menu, select the Parameters entry.
    The Parameters window opens.
    3. Select the Hierarchical option.
    Element

    Description

    Stop sequence Classical


    calculation
    If the option has been selected, the stop sequence is displayed as
    usual.
    Hierarchical
    If the option has been selected, the stop sequence is calculated hierarchically.
    Note
    Please take note of the following example (see "Example of a hierarchical sequence" on page 1558).
    4. Confirm with OK.
    The hierarchical sequence is calculated and a stop sequence with a sort station is displayed.
    Example of a hierarchical sequence
    The example illustrates the concept of the hierarchical sequence on the basis of one line.
    The network display shows a line 1 with a trunk V-W-X-Y-Z and several branches (for example
    A-B-V or Z-N-O-P).

    1558

    PTVGROUP

    15.43.5 Calculating stop sequences hierarchically

    The trunk is the most traversed section of the line (V-Z). At both ends of the trunk, the line branches out. As a result, branch-off stations are generated here (V and Z). All further attached sections are branches.
    A sort station (exemplified by V) which is determined by the highest number of virtual vehicle
    journeys at a stop or a stop point, regulates the sorting of the vehicle journeys. Virtual means
    that even those vehicle journeys of a line route which end before or commence past the sort
    station are taken into account. In the process, Visum considers the amount of vehicle journeys
    that comprises all vehicle journeys of all time profiles currently displayed in the navigator of
    lines in the Timetable editor.
    Note: For the calculation, it is irrelevant, which time profiles are selected in the navigator.
    In the hierarchical display mode, selecting a large number of lines might lead to unclear
    results and is thus not recommended.
    The line displayed in the example yields the following result in the tabular timetable for a hierarchical stop point sequence:

    PTVGROUP

    1559

    15.43.5 Calculating stop sequences hierarchically

    The determined sort station 3V is highlighted in red in window (6). The right-hand windows display the vehicle journeys that call virtually at the sort station. Vehicle journeys that do not call
    at the sort station are then attached in ascending order by departure times.
    The trunk V-Z of line 1 is highlighted. Each line comprises just one trunk and one sort station. If
    several lines are selected for the hierarchical sequence, there will be several trunks, too. In the
    example, the vehicle journeys of line 1 and line 2 are issued. The trunk of line 2 reaches from
    ff-jj.
    The vehicle journeys of the lines are displayed in blocks. In the example, the vehicle journeys
    of line 1 and line 2 each correspond to one block.
    All sequences of stop points that are completely congruent before and past the trunk are summed up in one branch in the window (6) of the tabular timetable.
    Note: You can edit the sort station manually and sort the vehicle journeys by a different
    stop (see "Sorting vehicle journeys in the tabular timetable" on page 1563).
    In the classical display of the graphical timetable, all vehicle journeys of line 1 are displayed
    as follows. Each vehicle journey is drawn through.

    1560

    PTVGROUP

    15.43.5 Calculating stop sequences hierarchically

    The hierarchical display of the same vehicle journeys looks like this:

    In the example, all vehicle journeys serve the trunk V-Z, which includes the sort station 3V. The
    vehicle journeys are displayed one below the other in section V-Z. A section that is not served
    by a certain vehicle journey is displayed as a broken line in the hierarchical display mode, if
    the section is served by one or more other vehicle journeys. The broken line connects the
    branch-off stations past which a vehicle journey continues. A sort station (for example 7Z) is
    drawn twice: before and past the broken line, and, in the grid, indicated by double horizontal
    lines.

    PTVGROUP

    1561

    15.43.5 Calculating stop sequences hierarchically


    Notes: If all stops on a branch are hidden because none of the stops on this branch shall
    be displayed and the
    Hide selected stop events icon is pressed, the complete
    branch will be hidden and the double branch-off station will be dropped.
    The stop sequence will be recalculated, if you select new lines in the navigator, or if you
    reopen the Timetable editor.
    If the amount of vehicle journeys is not suitable for a hierarchical stop/stop point
    sequence, a classical sequence is calculated automatically without the parameter being
    reset.
    Shifting branches in the display
    Note: Please take note of the following example.
    If a hierarchical stop sequence has been calculated, by default, the branches in the tabular
    timetable are sorted by length, i.e. by the number of stops above/below the trunk of the line
    route existing at a branch. The shortest branch thus adjoins to the trunk, all succeeding branches increase in length.
    You can edit the sequence of the branches in the hierarchical view as follows.
    Note: Manual modifications of the stop sequence are lost when recalculating the stop
    sequence, for example when changing the line selection.
    1. In the Timetable editor menu, select the Edit sequence of stop events entry.
    Tip: Alternatively, you can use the

    Edit sequence of stop events entry.

    The Edit sequence of stop events window opens. It displays all branches of the selected
    lines. The window displays level, course, and name of the allocated line routes of the branches.
    2. In the window, select the branch, whose position you want to change.
    Note: You can only change the position of branches that are located on the same side
    of the trunk and have the same level.
    3. If required, edit the order of the stops in the list with the aid of the

    and

    buttons.

    4. If required, check your settings by clicking the Apply button.


    5. Confirm with OK.
    The new sequence is applied both to the tabular timetable and the graphical timetable.
    Note: You can save the sequence of the branches with the layout file (see "Saving the layout of the Timetable editor" on page 1571).

    1562

    PTVGROUP

    15.43.6 Sorting vehicle journeys in the tabular timetable


    Example

    The example shows three line routes (green, red, blue). Section 6-7 marks the trunk, which
    has level 0. In the Edit sequence of stop events window, the section corresponds to the position 5.

    You can change the positions of branches of the same level, which adjoin to the trunk. You
    can, for example, move the branch on position 4 of the window (From SP 5 - To SP 6) to the
    position of the branch on position 1 (here 1-2). The branch is then moved to the position of the
    branch on position 1, which is moved to position 2.
    When shifting a section which has got subordinated branches, these will be shifted together
    with the higher-level branch. If, for example, the branch on position 7 in the lower section of
    the window is moved up, all its subordinated branches (on position 8 and 9 of the dialog box)
    move up as well. The new sequence then corresponds to formerly 7, 8, 9, 6.

    15.43.6 Sorting vehicle journeys in the tabular timetable


    In contrast to the graphical timetable, you can sort the vehicle journey display in the tabular
    timetable. The following possibilities are provided:
    No sorting (standard sorting)
    Sorting by a sort station
    Sorting by vehicle journey attribute

    PTVGROUP

    1563

    15.43.6.1 No sorting (standard sorting)


    Note: You can cancel the respective sorting, if you select the Discard sorting entry in window (6).
    15.43.6.1 No sorting (standard sorting)
    By default, vehicle journeys are sorted by their virtual departure times in ascending order at
    the first stop event of the time profile. The virtual departure time of a vehicle journey is the
    departure time at the start stop point of the time profile even if the actual vehicle journey does
    not serve this stop point. In the case of identical virtual departures of two vehicle journeys, the
    vehicle journey number (ID of a vehicle journey) determines the sorting.
    15.43.6.2 Sorting by a sort station
    When selecting this sorting, the display is sorted by sort station (see "Calculating stop
    sequences hierarchically" on page 1558). If you calculate a hierarchical stop sequence, the
    display is automatically sorted by sort station. It is highlighted in red. You can change it manually.
    Note: A sorting by attribute overrides a sorting by sort station and vice versa.
    1. Calculate a hierarchical stop sequence (see "Calculating stop sequences hierarchically" on
    page 1558).
    2. In the tabular timetable, in child window (6), right-click the stop by which you want to sort
    the vehicle journeys.
    A context menu opens.
    3. Select the Select as sort station entry.
    The stop becomes the new sort station and is highlighted in red. The vehicle journeys that call
    at this stop are displayed in groups and the display in window (8) is re-arranged.
    Note: You can sort by the originally calculated sort station again, if you select the Select
    recursive sort station entry in the context menu.
    15.43.6.3 Sorting by vehicle journey attribute
    This sorting arranges the display by one or more selected vehicle journey attributes. The
    vehicle journeys will then be evaluated and sorted by these attributes.
    Note: A sorting by attribute overrides a sorting by sort station and vice versa.
    1. In window (5), right-click the attribute, by which you want to sort the display.
    A shortcut menu opens.

    1564

    PTVGROUP

    15.43.7 Special functions of the graphical timetable

    2. Select the Sort attribute <Name> entry.


    The display is sorted by the attribute and the attribute is highlighted in red. In the context
    menu the Sort attribute <Name> is set active.
    3. If required, select further attributes by which you want to sort the display.
    Notes: If two vehicle journeys have the same value for, for example, the first attribute
    (here Line BUS1), the display is sorted by the second attribute (here Length).
    If you want to remove a single attribute from the sorting, right-click the desired attribute and select the Do no longer regard attribute <Name> for sorting entry in the
    context menu. Alternatively, you can add or remove attribute from the sorting by double-clicking the desired attribute.
    The display is sorted by the selected attributes.
    Note: If you want to cancel the sorting by vehicle journey attribute, select the Nullify
    selection entry in the context menu.

    15.43.7 Special functions of the graphical timetable


    Note: This functionality is only available with the Graphical timetable editor add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    The graphical timetable displays the vehicle journeys or vehicle journey sections vertically or
    horizontally. The difference between the two views Graphical timetable vertical and Graphical timetable horizontal is that the X-axis and the Y-axis are exchanged. Times are issued
    on the y-axis of the vertical display, and on the x-axis of the horizontal display.
    In the graphical timetable, each vehicle journey section is displayed exactly where it belongs
    according to its temporal/spatial position. Temporal overlapping of sections leads to visual
    overlapping in the graphical timetable. The numbers of the vehicle journey sections are overlap in this case, like the vehicle journeys 1 and 13 in the following example.

    PTVGROUP

    1565

    15.43.7.1 Adjusting the display of the graphical timetable

    Note: The graphical timetable displays all distances correctly.


    15.43.7.1 Adjusting the display of the graphical timetable
    There are several ways to adjust the display of the graphical timetable to your needs and display attribute values (see "Setting the graphic parameters of the tabular timetable" on page
    1573).
    In the graphical timetable, you can adjust the display just like in the network display. You can,
    for example, zoom or shift the view (see "Network editor window" on page 818).
    Additionally you can stretch or compress the axes. If you position the mouse pointer on the
    label of an axis, the label is displayed in red. Click and move the mouse pointer parallel to the
    axis to stretch or compress it.
    You can edit the graphical timetable using the following icons:
    Element Description
    Enlarge/reduce distance between stop events
    Enlarge or reduce the distance between the stop points in the display
    Show all stop points
    Adjust view so that all stop points are displayed
    Straighten out stop event labels
    Equalize distances disproportionally
    Note
    The distances are only increased where labels overlap.
    Stop distance proportional to the distances from network data
    Generate proportional distances between stop events

    Note: As in the tabular timetable, you can select the stops and specify their sequence
    (see "Specifying the display of stop events" on page 1570).

    1566

    PTVGROUP

    15.43.7.2 Marking and editing vehicle journeys in the graphical timetable


    15.43.7.2 Marking and editing vehicle journeys in the graphical timetable
    In the graphical timetable, you can also mark and edit vehicle journeys (see "Editing vehicle
    journeys" on page 1541).
    Contrary to the tabular timetable, the following access possibilities are provided in the graphical timetable:
    To delete one or multiple marked vehicle journeys, press the D EL key.
    To create a new vehicle journey, press the INS key. The Create vehicle journey(s) (see
    "Creating a vehicle journey" on page 1534) window opens.
    To edit a vehicle journey, double-click the desired vehicle journey. To edit multiple vehicle
    journeys, mark the desired vehicle journeys and press ENTER.The Edit vehicle journeys
    (see "Creating a vehicle journey" on page 1534) window opens.
    15.43.7.3 Displaying and adjusting margins
    You can display up to four margins in the graphical timetable.
    1. Right-click in the graphical timetable.
    A shortcut menu opens.
    2. Select the desired entry.
    Element

    Description

    Upper margin visible An axis is displayed at the upper margin.


    Lower margin visible An axis is displayed at the lower margin.
    Left margin visible

    An axis is displayed at the left margin.

    Right margin visible

    An axis is displayed at the right margin.

    3. Open the context menu again if you want to display further margins.
    The margins are displayed.
    Note: You can remove margins if you select the respective entry again in the context
    menu.
    Shifting items
    You can move the items on each axis.
    1. Click the stop or time you wish to move and hold down the mouse button.
    2. Drag the item to the desired position and release the mouse button.
    The label is moved.

    PTVGROUP

    1567

    15.43.7.4 Saving graphical timetable as graphics file


    Notes: You cannot move items past other items.
    If you shift a time, the distances of all times are adjusted proportionally.
    If you shift a stop or stop point, the distance to all adjacent items remains constant. However, you can shift individual stop/stop points, if you hold down the C TRL button and drag
    the desired stop or stop point.
    15.43.7.4 Saving graphical timetable as graphics file
    You can save the current display of the graphical timetable directly to a *.svg or *.dxf file.
    1. In the Timetable editor menu, select one of the SVG Export or DXF Export entries.
    The Save SVG file or Save DXF file window opens.
    2. Select the SVG export or DXF export entry.
    The Save SVG file or Save DXF file window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The SVG export or DXF export window opens.
    5. Make the desired settings (see "SVG export" on page 2656 and "DXF export" on page
    2654).
    6. Confirm with OK.
    The graphical timetable is saved to a *.svg or *.dxf file.
    Tip: You can also save the view by selecting the JPG export (screenshot) entry in the
    Timetable editor menu or by clicking the
    JPG export (screenshot) icon in the toolbar of the Timetable editor window (see "Exporting screenshots" on page 2663).
    You can also print the graphical timetable (see "Printing the graphical timetable" on page
    1600).

    15.43.8 Specifying the layout of the Timetable editor


    For the Timetable editor, you can specify a layout which you can save and read in again.
    Moreover, you can edit the size of the child windows by dragging the respective divider.
    15.43.8.1 Selecting the attributes to be displayed
    For the individual child windows, you can specify which attributes shall be displayed.
    Note: You can discard your selection of displayed attributes and further settings by selecting the Reset layout of columns and rows entry in the Timetable editor menu. The
    internally saved, user-defined layout settings will be discarded and the standard layout
    will be loaded.

    1568

    PTVGROUP

    15.43.8.1 Selecting the attributes to be displayed


    Displaying attributes of vehicle journeys and vehicle journey sections
    Window (5) of the tabular timetable displays the attributes of both vehicle journeys and vehicle
    journey sections (see "The Timetable editor window" on page 1530). The vehicle journey attributes are displayed at the top, below are common attributes of vehicle journeys and vehicle
    journey sections, and at the bottom, the vehicle journey section attributes are listed. You can
    adjust the selection of displayed attributes.
    Note: The attributes highlighted in gray at the very top are only displayed in the regular
    services mode (see "Editing regular services" on page 1546).
    1. Right-click in child window (5).
    A shortcut menu opens.
    2. Select the entry Select vehicle journey attributes or Select vehicle journey section attributes.
    The Attribute selection window opens.
    3. Make the desired settings (see "The window used for the selection of one attribute" on page
    963).
    Note: Some of the attributes displayed in the timetable editor have different names in
    the selection window:
    Start stop point (number and code of the stop point): corresponds to the attribute
    From time profile index in the selection window
    End stop point (number and code of the stop point): corresponds to the attribute
    To time profile index in the selection window
    Vehicle journey sections: corresponds to the attribute Count:Vehicle journey
    sections in the selection window
    4. Confirm with OK.
    The desired attributes are displayed in the tabular timetable.
    Display of stop point attributes and stop attributes
    You can either select stop point or stop attributes in the lower left window, according to whether you are in the stop point or stop mode. The respective selection is saved separately, even
    if you change the mode.
    Note: You can change the mode via the context menu or the

    icon.

    You can adjust the selection of displayed attributes.


    1. Right-click in child window (6).
    A shortcut menu opens.
    2. Select the Select stop point attributes or Select stop attributes entry.

    PTVGROUP

    1569

    15.43.8.2 Specifying the display of stop events


    Note: The entry in the context menu changes according to whether you are in the stop
    point or stop mode.
    The Attribute selection window opens.
    3. Make the desired settings (see "The window used for the selection of one attribute" on page
    963).
    4. Confirm with OK.
    The desired attributes are displayed in the tabular timetable.
    Display of vehicle journey item attributes
    The lower right child window of the tabular timetable displays the attributes of the vehicle journey items. You can specify which attributes shall be displayed.
    1. Right-click the column header of the child window (8).
    A shortcut menu opens.
    2. Select the Select vehicle journey item attributes entry.
    3. Edit the attribute selection (see "The window used for the selection of one attribute" on
    page 963).
    4. Confirm with OK.
    The desired attributes are displayed in the tabular timetable.
    15.43.8.2 Specifying the display of stop events
    In the windows (6) and (8) you can design the display of the stop events according to your wishes. You can edit the display using the context menu or via the following icons:
    Element Description
    Select all stop events
    Selects all stop events in the Filter column of window (6)
    Do not select any stop event
    Does not select any stop events in the Filter column of window (6)
    Invert selection of stop events
    Inverts the selection of stops in the Filter column of window (6).
    Select passive stop events
    Selects all passive stop events
    Hide selected stop events or Show hidden stop events
    In the Filter column you can select individual stop events via check boxes and
    then reduce the display to the remaining stop events.
    Hide stops without stop event
    Hides all stops without stop events

    1570

    PTVGROUP

    15.43.8.3 Saving the layout of the Timetable editor


    Element Description
    Note
    Served stops are all stops where boarding and alighting is permitted.
    Recalculate sequence of stop events
    Recalculates the sequence of stop events based on the current line selection
    Stop sequence according to stop points / stops
    Switches between the display of stop events as stop points and stops
    Invert sequence of stop events
    Inverts sequence of stop events in the display

    15.43.8.3 Saving the layout of the Timetable editor


    You can save your layout settings to a *.tly file and read them in again.
    Note: The graphic parameter settings of the timetable are saved separately to a graphic
    parameters file (see "Setting the graphic parameters of the tabular timetable" on page
    1573).
    In the tabular timetable, the following settings are saved to the layout file:
    Line selection
    Size and position of the child windows
    Displayed attribute rows and columns
    Stop sequence
    Column width of the vehicle journeys and vehicle journey sections
    Parameters classical/hierarchical stop sequence
    In the graphical timetable, the following settings are saved to the layout file:
    Visibility of the stop events
    Scaling of the time axis (i.e. the width of an hour)
    Distance between stop events on the spatial axis
    Scroll position in the graphical timetable window (horizontal and vertical)
    Zoom condition and margin settings
    Note: The data of the vertical graphical timetable are saved independently of the data of
    the horizontal graphical timetable.
    1. In the Timetable editor menu, select the Save layout entry.
    Tip: Alternatively, click the

    Save layout icon in the toolbar of the Timetable editor.

    The Save Timetable editor layout window opens.


    2. Enter the file name and the path, if required.

    PTVGROUP

    1571

    15.43.8.4 Reading the layout of the Timetable editor


    3. Click the Save button.
    The layout settings are saved.
    Note: When closing the Timetable editor, Visum internally saves all network-independent
    layout settings of the timetable. The same settings will be adjusted automatically when
    opening the Timetable editor the next time.
    15.43.8.4 Reading the layout of the Timetable editor
    If you have saved your settings to a *.tly file, you can read in your layout settings as follows.
    1. In the Timetable editor menu, select the Open layout entry.
    Tip: Alternatively, click the

    Read layout icon in the toolbar of the Timetable editor.

    The Open Timetable editor layout window opens.


    2. Select the desired file.
    3. Click the Open button.
    The Selective layout reading window opens.

    4. Make the desired changes.

    1572

    Element

    Description

    Line selection

    If the option has been selected, the saved line selection and the
    selection status (checked/not checked) is read in.

    Line block selection

    If the option has been selected, the saved line block selection
    and the selection status (checked/not checked) is read in.

    Stop sequence

    If the option has been selected, the saved stop event sequence,
    the visibility of the stop events, and the marking status are read in.

    Attribute selections

    If the option has been selected, the saved attribute columns and
    rows will be displayed.

    Dialog layout

    If the option has been selected, the saved sizes and positions of
    the child windows, the selected tabs, and the settings of the
    graphical timetable will be applied.

    Modes and para-

    If the option has been selected, the properties vehicle jour-

    PTVGROUP

    15.43.9 Setting the graphic parameters of the tabular timetable


    Element

    Description

    meters

    neys/vehicle journey sections mode, stop/stop point sequence


    mode, regular services mode on/off, and parameters classical/hierarchical sequence of stop events will be applied.

    Check all

    Use this button to select all options.

    Uncheck all

    Use this button to remove all options from the selection.

    Invert

    Use this button to deselect all selected options and select all nonselected options.

    Note: The Line selection, Line block selection, and Stop sequence options are network-dependent.
    5. Click the Read button.
    The desired settings are read in.

    15.43.9 Setting the graphic parameters of the tabular timetable


    Similar to the network display, you can specify graphic parameters for the tabular timetable, in
    order to configure the timetable according to your needs. Afterwards, you can save the graphic
    parameters to a file and reuse them. In the tabular timetable, you can specify the following settings:
    The font of the tabular timetable
    The background colors of the columns of the tabular timetable

    PTVGROUP

    1573

    15.43.9.1 Specifying the background of the table


    Example

    15.43.9.1 Specifying the background of the table


    In the tabular timetable you can specify different background colors for displaying active, passive, and marked vehicle journeys. Apart from this, you can define classes of vehicle journeys
    and assign them different colors.
    1. In the Timetable editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.

    1574

    PTVGROUP

    15.43.9.1 Specifying the background of the table

    Note: The graphic parameters for the display of active, passive, and marked vehicle
    journeys and vehicle journey sections are set separately in the respective tabs. The
    settings of the Passive and Marked tabs are almost identical with the settings you
    can specify on the Active tab. Therefore only the settings of the Active tab are described.
    2. Select Tabular timetable> Table background>, tab Active.
    3. Make the desired changes.
    Element

    Description

    Uniform display

    If the option has been selected, the backgrounds of all active


    vehicle journeys are displayed consistently. In the Display section, select the Color in which you want to display the background.

    Classified display If this option has been selected, you can classify the active
    vehicle journeys using their attribute values. First you specify the
    number of classes. Then you assign them different colors.
    Example: Your network comprises two operators. You want to display them with different colors. You classify the vehicle journeys
    by the attribute operator number. That means, you define one
    class for operator 1 and a second class for operator 2. Then you
    allocate the color red to the class of operator 1, and the color
    green to the class of operator 2. The vehicle journeys of operator

    PTVGROUP

    1575

    15.43.9.2 Specifying the table font


    Element

    Description
    1 are displayed in red, the vehicle journeys of operator 2 are displayed in green (see "Displaying classified objects based on attribute values" on page 2411).

    15.43.9.2 Specifying the table font


    In the tabular timetable you can define different fonts, font sizes, and font colors for active, passive, and marked vehicle journeys. Additionally, you can define classes of vehicle journeys
    and assign them different fonts, font sizes, and font colors.
    1. In the Timetable editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. Select the page Tabular timetable> Table font>, tab Active.
    3. Make the desired changes.
    Element

    Description

    Uniform display

    If the option has been selected, all active fonts are displayed uniformly. In the Display section, select the Font style, the font size
    and the color in which you want to display the font.

    Classified display If this option has been selected, you can classify the active
    vehicle journeys using their attribute values. First you specify the
    number of classes. Then you assign them different fonts, font
    sizes, and font colors (see "Displaying classified objects based
    on attribute values" on page 2411).
    Tip
    The classification of the table font can be done according to a different attribute than the one selected on tab Table background.
    Display

    In the Display section you specify the table font to be displayed.


    Font
    Click in the field. A window opens. Here you can specify the font
    type and style.
    Size
    Font size in mm
    Color
    Click the button. A window for selecting the font color opens.

    4. If required, in the same way, edit the settings for passive and marked vehicle journeys in
    the respective tab.
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.

    1576

    PTVGROUP

    15.43.10 Setting the graphic parameters of the graphical timetable


    5. Confirm with OK.
    The fonts are displayed according to your settings.

    15.43.10 Setting the graphic parameters of the graphical timetable


    Similar to the network display, you can specify graphic parameters for the tabular and the
    graphical timetable, in order to configure the timetable according to your needs (see "Setting
    the graphic parameters of the tabular timetable" on page 1573). Afterwards, you can save the
    graphic parameters to a file and reuse them. In the graphical timetable, you can, for example,
    specify settings for the following items.
    Axes labeling
    Different display of active, marked, and passive vehicle journeys/vehicle journey sections
    Vehicle journey items texts and bars
    15.43.10.1 Setting the print frame
    If you want to print the graphical timetable, you can specify the following settings for the print
    frame.
    1. In the Timetable editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Print frame page.
    3. Make the desired settings.
    Element

    Description

    Draw

    If the option has been selected, a print frame is drawn.


    Note
    If the option has been selected, a single frame is drawn, if the Header
    and Footer options are not selected on the respective page.

    Boundary

    You can specify the boundary style in a separate window. To do so, click
    in the field (see "Specifying the line style of the frame" on page 1580).

    4. Select the Print frame> Header page, if you want to insert a header.
    Note: The header is a row that extends over the complete width of the print frame.
    5. Make the desired settings.
    Element

    Description

    Draw

    If the option has been selected, a header is displayed.

    Font

    You can specify the font and the style in a separate window by
    clicking in the field.

    Text size

    Text size in mm

    PTVGROUP

    1577

    15.43.10.1 Setting the print frame


    Element

    Description

    Color

    In a separate window, you can specify a color for the header by


    clicking in the field.
    Note
    You can position the header left, right or centered, if you click the
    respective icon on the right.

    Minimum line
    height

    If the option has been selected, you can enter a minimum height for
    the row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    Text

    Use the drop-down list to select text entries which will be inserted in
    the header.
    user-defined
    Here you can enter a text into the empty field.
    empty
    [VISUM version]
    Created on: [Date]
    Created on: [Date] / [Time]
    [Date] / [Time]
    [File name]
    [Scale]
    [Scale factor]

    Help

    Use the button to open a window with all available auto values.
    Note
    The entries in squared brackets are pre-defined by the program (auto
    values). They are replaced with the current values when drawing the
    print frame. Auto values are language-dependent and can also be utilized as user-defined entries.

    6. Select the Print frame> Footer page, if you want to insert a footer.
    Note: The footer consists of two rows with three columns each, and is displayed at the
    bottom of the print area.
    7. Make the desired settings.

    1578

    Element

    Description

    Draw

    If the option has been selected, a footer will be drawn.

    Font

    You can specify the font and the style of the footer in a separate
    window by clicking in the field.

    PTVGROUP

    15.43.10.1 Setting the print frame


    Element

    Description

    Text size

    Text size in mm

    Color

    In a separate window, you can specify a color for the label of the
    footer by clicking in the field.

    Minimum line
    height

    If the option has been selected, you can enter a minimum height
    for the row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    Column format

    You can regulate the width of each column by entering a percentage.


    Notes
    The total need not amount to 100%. The width will be calculated
    proportionately.
    You can position the column contents left aligned, centered or
    right aligned by clicking the respective icon below.

    Text

    Use the drop-down list to select text entries which will be inserted
    in the header.
    user-defined
    Here you can enter a text into the empty field.
    empty
    Hide cell
    Select this option to hide the respective field.
    [VISUM version]
    Created on: [Date]
    Created on: [Date] / [Time]
    [Date] / [Time]
    [File name]
    [Scale]
    [Scale factor]

    Help

    Use the button to open a window with all available auto values.
    Notes
    The entries in squared brackets are pre-defined by the program
    (auto values). They are replaced with the current values when drawing the print frame. Auto values are language-dependent and
    can also be utilized as user-defined entries.

    Note: Click the Preview button to immediately show your changes without closing the
    Edit graphic parameters window.
    8. Confirm with OK.

    PTVGROUP

    1579

    15.43.10.1 Setting the print frame


    9. If required, start the print output (see "Printing the network display" on page 2499).
    The print frame is printed according to your settings.
    Note: Together with the other timetable graphic parameter settings, the settings for the
    print frame are saved to a graphic parameters file *.gpt (see "Saving the graphic parameters of the timetable" on page 1599).
    Specifying the line style of the frame
    You can specify the line style display of the print frame, if you click in the Boundary field.
    1. On the Print frame page, click in the Boundary field.
    The Line style parameters window opens.

    2. Make the desired settings.

    1580

    Element

    Description

    Preview

    Here you can see how the frame line will be displayed when printed.

    Width

    Line width in mm

    PTVGROUP

    15.43.10.2 Specifying the axes labeling


    Element

    Description

    Color

    In a separate window, you can specify a color for the frame line by
    clicking in the field.

    Line style

    The line style is composed of individual square units that determine the
    lengths and the distance of the displayed points or lines. You can also
    set a user-defined line style if you move the indicator along the scale
    and check single units.
    Alternatively, you can select a line style template.
    Notes
    Active units (black) are displayed as points or lines in the selected
    color and line width. Inactive units (white) are transparent and indicate
    the distance between two points or lines.
    The length of an individual line or a distance is based on the number of
    units per line or distance width of a single element. A line consisting
    of four units, for example, will be displayed at a length of 4 mm in the
    network display, if the width of the element is 1 mm.
    The height of each unit is determined by the set line width (=Width).
    Width of a single element
    Length of each unit in mm
    Note
    The indicator determines the total length of the pattern (= number of
    units width of the element).
    Line style templates
    Via this button, the Line style templates window opens. In the window,
    you can select a template which shall be used for the frame.
    Note
    The user-defined line style will be overwritten if you select a template.
    Line width and line color remain unchanged.

    3. Confirm with OK.


    The frame line is displayed according to your settings.
    15.43.10.2 Specifying the axes labeling
    For stop points and stops, you can set different axes labels in two different tabs.
    Note: The parameter settings are the same. They are described using the example of
    stop points.
    1. In the Timetable editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. Select page Axes labeling> tab Stop points.

    PTVGROUP

    1581

    15.43.10.2 Specifying the axes labeling


    3. Make the desired changes.
    Element

    Description

    Uniform display

    If the option has been selected, all axes labels are displayed uniformly. In the Display section, select the Draw text option and
    make further changes.

    Classified display If the option has been selected, you can classify and display the
    axes labeling by an attribute (see "Displaying classified objects
    based on attribute values" on page 2411).
    Display

    Draw text
    If the option has been selected, axes labels will be drawn.
    In the Text section, you can specify how the text of the axes labeling shall be displayed.
    Content
    Use the button to select the attribute with which you want to label
    the axis (see "The window used for the selection of one attribute"
    on page 963).
    Size
    Text size in mm
    Color
    If you click in the field, you can select a color for the axes labeling.
    Round
    Rounding factor for the attribute values
    Transparent
    If the option has been selected, the label is displayed without the
    white background, as text only.
    Frame
    If you select this option, the axes labeling will be framed. You can
    specify a color for the frame if you click in the field.
    Decimal places
    Enter the number of decimal places for the display of the attribute
    values.
    Note
    The option is only available for numerical attributes of the type
    decimal place.

    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    4. Confirm with OK.
    The axes are labeled according to your settings.
    1582

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Notes: The settings for the display of vehicle journeys and vehicle journey sections in the
    graphical timetable are identical.
    However, you can specify different settings in different tabs for active, passive and marked vehicle journeys and vehicle journey sections. The settings are described on the
    basis of active vehicle journeys.
    Specifying the header text
    Each displayed vehicle journey can be labeled with a Header text which is positioned right
    above the first vehicle journey item. The text can be any vehicle journey attribute, such as the
    vehicle journey number.
    1. In the Timetable editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. Select the page Vehicle journeys> Header text.

    3. Make the desired changes.


    Element

    Description

    Uniform display

    If the option has been selected, all header labels are displayed
    uniformly. In the Display section, select the Draw text option and
    make further changes.

    Classified display If the option has been selected, you can classify and display the

    PTVGROUP

    1583

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    header text by an attribute (see "Displaying classified objects
    based on attribute values" on page 2411).

    Display

    In this section, you can specify the following settings for the header text:
    Draw text
    If the option has been selected, a header text will be displayed.
    Draw until scale
    If the option has been selected, the text will be drawn up to the
    set scale when zooming out (see "Editing the network scale" on
    page 2209).
    If the option has not been selected, the text will always be displayed, irrespective of the network scale.
    Slanted text
    If the option has been selected, the text is not displayed horizontally, but as slanted text.

    Text

    In the Text section, you can specify the display of the header text.
    Content
    Use this button to select a vehicle journey attribute in a separate
    window for the header text (see "The window used for the selection of one attribute" on page 963).
    Size
    Text size in mm
    Font
    You can specify the font and the style in a separate window by
    clicking in the field.
    Transparent
    If the option has been selected, the text is displayed without the
    white background, as text only.
    Color
    In a separate window, you can specify a color for the header text
    by clicking in the field.
    Frame
    If you select this option, the header text will be framed. You can
    specify a color for the frame if you click in the field.
    Round
    Rounding factor for the attribute values
    Decimal places
    Enter the number of decimal places for the display of the attribute
    values.

    1584

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    Note
    The option is only available for numerical attributes of the type
    decimal place.

    4. If required, in the same way, edit the settings for passive and marked vehicle journeys in
    the respective tab.
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    5. Confirm with OK.
    The header text is displayed according to your settings.
    Setting the line style properties
    You can specify the Line style properties for vehicle journeys and vehicle journey sections,
    i.e. a line style, in which the vehicle journeys or vehicle journey sections will be displayed.
    1. Select the Vehicle journeys> Line style properties page.
    2. Make the desired changes.
    Element

    Description

    Uniform display If the option has been selected, all vehicle journey items are displayed uniformly. In the Display section, select the Draw option and
    make further changes.
    Classified display

    If the option has been selected, you can classify and display the line
    display by an attribute (see "Displaying classified objects based on
    attribute values" on page 2411).

    Display

    In this section, you can specify the following settings for the line display:
    Draw object
    If the option has been selected, a line will be drawn.
    Draw until scale
    If the option has been selected, a line will be drawn up to the set
    scale when zooming out (see "Editing the network scale" on page
    2209).
    If the option has not been selected, a line will always be displayed, irrespective of the network scale.
    Line style
    You can specify the font and the style of the line in a separate window by clicking in the field (see "Setting the line style" on page

    PTVGROUP

    1585

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    1586).
    Draw arrow head
    If the option has been selected, an arrow head is drawn.

    Draw arrow
    head

    If the option has been selected, you can specify the following settings.
    Use the drop-down list, to select the symbol that will be displayed as
    arrow head.
    Size
    Size of arrow head in mm
    Color
    In a separate window, you can specify a color for the arrow head by
    clicking in the field.
    Sign
    If you select Circle or Square for the arrow head, you may activate
    an input field via the checkbox. In the input field, you can enter a
    sign which will be displayed inside the circle or square. You can
    specify the color of the GPS signal in a separate window by clicking
    in the color field.

    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    3. Confirm with OK.
    The line is displayed according to your settings.
    Setting the line style
    You can specify the line style of vehicle journeys.
    1. On page Vehicle journeys> Line style properties, click in the Line style field.
    The Line style parameters window opens.

    1586

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections

    2. Make the desired changes.


    Element

    Description

    Total preview

    Here you can see the display of all stroke layers together.

    Stroke layer

    Here you can see the individual layers which are drawn on top of
    each other.
    Tips
    Via the

    and

    buttons, you can insert or delete single layers.

    Via the
    and
    buttons, you can edit the order in which the
    layers are drawn.

    PTVGROUP

    1587

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description

    Line style properties

    Here you can specify settings for the individual layer when
    clicking the desired layer in the list.
    Preview
    Here you can see how the line will be drawn.
    Width
    Line width in mm.
    Color
    In a separate window, you can specify a color for the respective
    line by clicking in the field.

    Line style

    The line style is composed of individual square units that determine the lengths and the distance of the displayed points or lines.
    You can specify a user-defined line style by moving the indicator
    along the scale and checking individual units.
    Alternatively, you can select a line style template.
    Notes
    Active units (black) are displayed as points or lines in the selected color and line width. Inactive units (white) are transparent and
    indicate the distance between two points or lines.
    The length of an individual line or a distance is based on the number of units per line or distance width of a single element. A line
    consisting of four units, for example, will be displayed at a length
    of 4 mm in the network display, if the width of the element is 1
    mm.
    The height of each unit is determined by the set line width
    (=Width).
    Width of a single element
    Enter the length of each unit in mm.
    Note
    The indicator determines the total length of the pattern (= number
    of units width of the element).
    Line style templates
    Via this button, the Line style templates window opens. In this
    window, you can select a template for the line display.
    Note
    The user-defined line style will be overwritten if you select a template. Line width and line color remain unchanged.

    3. Confirm with OK.


    The line style is displayed according to your chosen settings.

    1588

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Displaying departure and arrival times
    In addition, you can display Departure and arrival times (or any other vehicle journey attribute) before and past each stop. By default, the departure minute is displayed in red and the
    arrival minute in green.
    1. Select page Vehicle journeys> Departure and arrival times.
    2. Make the desired changes.
    Element

    Description

    Uniform display

    If the option has been selected, all times are displayed uniformly.
    In the Display section, select the Draw option and make further
    changes.

    Classified display If the option has been selected, the display can be classified by
    an attribute (see "Displaying classified objects based on attribute
    values" on page 2411).

    PTVGROUP

    1589

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description

    Display

    In this section, you can specify the following settings for the display:
    Draw
    If the option has been selected, the selected attribute will be displayed at stops.
    Use vehicle journey items text format
    If the option has been selected, the formats specified under Item
    labels will be applied.
    Draw until scale
    If the option has been selected, the attribute will be drawn up
    to the set scale when zooming out (see "Editing the network
    scale" on page 2209).
    If the option has not been selected, the attribute will always be
    displayed, irrespective of the network scale.

    Dep. times/arrival The parameters of the two tabs are identical. In both, you can spetimes
    cify the following settings in the Draw text section:
    Content
    Use the button to select a vehicle journey attribute for the label in
    a separate window (see "The window used for the selection of
    one attribute" on page 963). By default, the Departure Minute or
    the Arrival Minute is selected.
    Size
    Enter the desired text size in mm
    Font
    You can specify the font and the style of the label in a separate
    window by clicking in the field.
    Transparent
    If the option has been selected, the text is displayed without the
    white background, as text only.
    Color
    In a separate window, you can specify a color for the label by
    clicking in the field.
    Frame
    If you select this option, the labels will be framed. You can specify
    a color for the frame if you click in the field.
    Round
    Enter a rounding factor for the attribute values
    Decimal places
    Enter the number of decimal places for the display of the attribute

    1590

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    values.
    Note
    The option is only available for numerical attributes of the type
    decimal place.

    3. If required, in the same way, edit the settings for passive and marked vehicle journeys in
    the respective tab.
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    4. Confirm with OK.
    The arrival and departure times are displayed according to your settings.
    Displaying journey item symbols
    Vehicle journey items can be displayed by symbols. You can select a symbol and specify further settings.
    1. Select page Vehicle journeys> Journey item symbols.
    2. Make the desired changes.
    Element

    Description

    Uniform display

    If the option has been selected, all symbols are displayed uniformly. In the Display section, select the Draw symbol option and
    specify further settings.

    Classified display If the option has been selected, the display can be classified by
    an attribute (see "Displaying classified objects based on attribute
    values" on page 2411).
    Display

    PTVGROUP

    Draw symbol
    If the option has been selected, vehicle journey items are displayed by the selected symbol.
    In the Drawsymbol section, you can specify, which symbol will be
    displayed and specify further settings.
    In the drop down list, you can select one of the following symbols:
    Circle
    Square
    Triangle
    Open arrow
    Cross
    Stop German
    Stop English

    1591

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    POI
    Signal controlled junction
    Stop sign
    Two-way stop
    Roundabout
    Two-way yield
    Size
    Symbol size in mm
    Color
    In a separate window, you can specify a color for the symbol by
    clicking in the field.
    Sign
    If you select the Circle or Square symbol, you can activate the
    input field by checking the box. In the input field, you can enter a
    sign which will be displayed inside the circle or square. You can
    specify the color of the GPS signal in a separate window by
    clicking in the color field.

    3. If required, in the same way, edit the settings for passive and marked vehicle journeys in
    the respective tab.
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    4. Confirm with OK.
    The symbols are displayed according to your settings.
    Hidden starts/ends of vehicle journeys
    Vehicle journeys which start or end at a hidden stop can be provided with an auxiliary line at
    the first/last visible stop at the beginning or at the end of that vehicle journey.

    1. Select page Vehicle journeys> Hidden starts/ends of vehicle journeys.


    2. Make the desired changes.

    1592

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description

    Uniform display

    If the option has been selected, all items are displayed uniformly.
    In the Display section, select the Draw option and specify further
    settings.

    Classified display If the option has been selected, the display can be classified by
    an attribute (see "Displaying classified objects based on attribute
    values" on page 2411).

    PTVGROUP

    1593

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description

    Display

    In this section, you can specify the following settings for hidden
    starts/ends of vehicle journeys:
    Draw
    If the option has been selected, hidden starts/ends will be drawn.
    Draw until scale
    If the option has been selected, hidden starts/ends of vehicle
    journeys will be drawn up to the set scale when zooming out (see
    "Editing the network scale" on page 2209).
    If the option has not been selected, hidden starts/ends will
    always be displayed, independently of the network scale.

    Trip start/
    Trip end

    The parameters of the two tabs are identical. In both, you can
    make the following changes:
    Draw
    If the option has been selected, the respective auxiliary lines and
    arrow heads will be drawn.
    Auxiliary line
    In this section, you can specify the display of the line as well as
    the length in mm. The setting parameters of the line correspond to
    those of the frame line of the print frame (see "Specifying the line
    style of the frame" on page 1580).
    Arrow head
    In this section, you can specify the color and the size of the arrow
    head.
    Description
    If the option has been selected, a label is drawn for the hidden
    stop events.
    In the Draw label section, you can specify the following settings:
    Content
    Use the button to select a vehicle journey attribute for the label in
    a separate window (see "The window used for the selection of
    one attribute" on page 963).
    Size
    Text size in mm
    Font
    You can specify the font and the style of the label in a separate
    window if you click in this field.
    Transparent
    If the option has been selected, the text is displayed without the
    white background, as text only.

    1594

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    Color
    In a separate window, you can specify a color for the label by
    clicking in the field.
    Frame
    If you select this option, the labels will be framed. You can specify
    a color for the frame if you click in the field.
    Round
    Rounding factor for the attribute values
    Decimal places
    Enter the number of decimal places for the display of the attribute
    values.
    Note
    The option is only available for numerical attributes of type decimal place.

    3. If required, in the same way, edit the settings for passive and marked vehicle journeys in
    the respective tab.
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    4. Confirm with OK.
    The beginnings and ends of the vehicle journeys are displayed according to your settings.
    Specifying item labels
    You can label vehicle journeys with item data. For each item, a label can be issued for any
    vehicle journey item attribute. It will then be displayed at every stop-stop section.
    1. Select page Vehicle journeys> Item labels.
    2. Make the desired changes.
    Element

    Description

    Layer vehicle jour- If the option has been selected, the vehicle journey items are labeney items label
    led.
    Display identical
    texts together

    If the option has been selected, adjacent vehicle journey item


    labels with the same text are displayed together.

    Grouping

    Placing the text in common


    You can either display grouped texts At the first course item or
    In the middle of the group.
    Dividing line

    PTVGROUP

    1595

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description
    If the option has been selected, a dividing line of the specified
    Length and Color will be displayed between sections with the
    same label.

    3. Select page Vehicle journeys> Item labels > Text by item.


    4. Make the desired changes.
    Note: The parameter settings are identical to those of the header text (see "Specifying
    the header text" on page 1583).
    5. If required, in the same way, edit the settings for passive and marked vehicle journeys in
    the respective tab.
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    6. Confirm with OK.
    The item labels are displayed according to your settings.
    Specifying items bars
    You can display any vehicle journey items attributes between to stop events as bars along the
    course.
    Note: The program thus offers another possibility of displaying item attributes, namely in
    the form of bars, in addition to vehicle journey item labels and arrival and departure time
    labels.

    1596

    PTVGROUP

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Note: If you want to display volumes of vehicle journeys along the course, you need to
    select the Additionally for vehicle journeys options under Save volumes on the PuT
    settings > Assignment page of the General procedure settings window before calculating a PuT assignment (see "Setting and calculating PuT assignment parameters" on
    page 2006).
    You can specify and display bar labels for item bars.
    1. In the navigator, select the Vehicle journeys> Item bars entry.
    2. Select the Layer control tab.
    3. Make the desired changes.
    Element

    Description

    Bar layer

    If the option has been selected, bars and their labels can be displayed at vehicle journey items.

    Draw bars

    If the option has been selected, bars can be displayed at vehicle


    journey items.

    Draw bar labels

    If the option has been selected, bar labels can be displayed at


    vehicle journey items.

    4. Select the General settings tab.


    5. Make the desired changes.
    Element

    Description

    Distance
    between
    bars

    Distance between the item bars in mm

    Text posiNext to bar


    tioning: ver- If the option has been selected, the label is displayed next to the bar.
    tical
    Within bar
    If the option has been selected, the label is displayed within the bar.
    Text distance
    Distance of labels in mm
    Note
    If the Next to bar option is selected, the distance to the bar is displayed.
    If the Within bar option is selected, the distance to the link is indicated.

    6. Select the Text format tab.


    7. Make the desired changes.

    PTVGROUP

    1597

    15.43.10.3 Specifying the display of vehicle journeys and vehicle journey sections
    Element

    Description

    Font and Font


    color
    You can specify a Font and a Style in a separate window. To do so, click in
    the field.
    Text size
    Text size in mm
    Note
    If the text size is 0.0mm, no bar label is issued.
    Color like bar
    If the option has been selected, the text is displayed in the same color as
    the bar.
    Tip
    We recommend this option, if several bars are displayed.
    If the option has not been selected, you can select a color in the drop-down
    list.
    Text
    entry

    Transparent
    If the option has been selected, the bar label is displayed without the white
    background, as text only.
    Draw frame
    If the option has been selected, the label is drawn with a frame. From the
    selection list, you can select the color.
    Alignment
    You can specify the alignment and the display of several bar labels via the
    drop-down list:
    Horizontal
    The labels are displayed in a row.
    Vertical
    The labels are displayed one below the other.
    Vertical + Sum
    All labels are displayed one below the other and underneath, the sum of
    the values is displayed.
    Sum only
    Only the values of the sum are displayed.
    Line spacing
    Line distance in percent of the current text size

    8. Select the Bar selection tab.


    9. Make the desired changes.

    1598

    PTVGROUP

    15.43.10.4 Resetting the graphic parameters of the timetable


    Element

    Description

    Draw bars only on


    active vehicle journey items

    If the option has been selected, bars are not drawn at passive
    vehicle journey items.

    For the vehicle journey items, bars are in principle displayed and the basic settings are specified.
    10. Select the Item bars> Display page.
    11. Insert the desired bars (see "Defining one or multiple bars" on page 2373).
    12. Specify the desired display settings for the bars (see "Setting the display properties of a
    bar" on page 2374).
    Note: Item bars can be of the type standard bar or difference bar.
    13. Confirm with OK.
    The item bars are displayed according to your settings.
    15.43.10.4 Resetting the graphic parameters of the timetable
    You can reset your settings of the graphic parameters and restore the original settings.
    In the Timetable editor menu, select the Reset graphic parameters entry.
    The standard settings are restored.
    15.43.10.5 Saving the graphic parameters of the timetable
    You can save your graphic parameter settings to a Timetable editor graphic parameters file
    *.gpt.
    In the tabular timetable, the following settings are saved to the graphic parameters file:
    Table backgrounds
    Table fonts
    In the graphical timetable, the following settings are saved to the graphic parameters file:
    Texts of vehicle journeys
    Line style properties of vehicle journeys
    Labels of vehicle journey items
    Text of vehicle journey sections
    Line properties of vehicle journey sections
    Note: The graphic parameter settings of the timetable are saved separately to a layout
    file (see "Saving the layout of the Timetable editor" on page 1571)
    1. Edit the graphic settings as desired.
    2. In the Timetable editor menu, select the Save graphic parameters as... entry.

    PTVGROUP

    1599

    15.43.10.6 Reading graphic parameters for the timetable


    The Save Timetable editor graphics parameters window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The graphic settings are saved.
    Note: When closing the Timetable editor Visum internally saves all network-independent
    graphic settings of the timetable. The same settings will be adjusted automatically when
    opening the Timetable editor the next time.
    15.43.10.6 Reading graphic parameters for the timetable
    If you have saved your settings to a Timetable editor graphic parameter file *.gpt, you can read
    in your graphic settings as follows.
    1. In the Timetable editor menu, select the Open graphic parameters entry.
    The Open Timetable editor graphics parameters window opens.
    2. Select the desired file.
    3. Click the Open button.
    The desired settings are read in.

    15.43.11 Printing the graphical timetable


    1. Right-click in the graphical timetable.
    A shortcut menu opens.
    2. Select the Print entry.
    The Print Timetable editor window opens.
    3. Make the desired settings (see "Starting print output" on page 2508).
    4. Confirm with OK.
    The graphical timetable is printed.

    15.43.12 Printing the tabular timetable


    Note: You cannot print the tabular timetable directly. If required, you can export it in order
    to print it.
    You can export the timetable as follows:
    Save the graphical timetable to a graphics file *.svg (see "Saving graphical timetable as
    graphics file" on page 1568)
    Export vehicle journeys via the clipboard
    If you want to export individual vehicle journeys to another program, such as Excel, proceed
    as follows.

    1600

    PTVGROUP

    15.44 Using the subnetwork generator


    1. Mark the desired vehicle journeys in the tabular or graphical timetable (see "Marking
    vehicle journeys" on page 1539).
    2. In the Timetable editor toolbar, click the

    Copy timetable into clipboard icon.

    Tip: Alternatively, you can call the functionality via the context menu.
    The marked vehicle journeys and the current layout settings are copied to the clipboard.
    3. Use the Insert mode of the desired program to insert the data.
    The marked vehicle journeys are deleted.
    4. Use the functionality of the respective program to print the data.
    Example: Export to Excel

    15.44

    Using the subnetwork generator


    Note: This functionality is only available with the Subnetwork generator add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    With the subnetwork generator, Visum provides the possibility of singling out a section of an
    entire network, such as a city area, and regarding it separately. A smaller subnetwork gives
    you a better overview of the network items and their relations, and the procedures are calculated faster.

    PTVGROUP

    1601

    15.44.1 Subnetwork generation


    You can generate a subnetwork in such a way that you obtain the same assignment results as
    in the original network (see Fundamentals: Chpt. 3.4 , page 117).
    Subjects
    Subnetwork generation
    Selecting options for line routes

    15.44.1 Subnetwork generation


    1. Select the network objects that shall be included in the subnetwork, via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected network objects are active.
    2. In the Calculate menu, select the Subnetwork generator entry.
    The Parameters subnetwork generator window opens.
    3. Make the desired changes.
    Element

    Description

    Version file

    Enter or select a path and file name under which you want to
    save the version file.

    Options for cutting


    PuT line routes

    Selection of a procedure to deal with line routes which intersect


    the limits of the subnetwork (see "Selecting options for line routes" on page 1604).

    Matrices for assi- Note


    gned demand seg- This selection is only available if an assignment has already
    ments
    been calculated.
    Selection of the partial matrices (of internal and private traffic) for
    the existing demand segments, which shall be saved with the subnetwork under the specified name.
    Include the
    demand model in
    the subnetwork

    If the option has been selected, all demand models that currently
    exist in the network and the related data objects will be saved to
    the subnetwork.
    Note
    All demand strata that exist in the original network are transferred
    to the subnetwork. For zones that are identical in the original network and in the subnetwork, the zone attributes Attraction and
    Production are also transferred for each demand stratum.

    Subnetwork cordon zones section


    Use connector
    links

    1602

    Note
    The option is only relevant to PrT networks. If you do not select

    PTVGROUP

    15.44.1 Subnetwork generation


    Element

    Description
    the option, the turn attributes (turn prohibitions and penalties) of
    the flows from the cordon zones will be lost.
    If the option has been selected, all paths that enter the subnetwork at a node, obtain a connector link that is based on the
    link used last outside of the subnetwork. The To node of the
    connector link will be the first node in the subnetwork; the From
    node is newly created. The connector link, cordon node, and cordon zone receive the same number.

    Numbering of cor- Note


    don zones with off- Make sure that zone numbers do not occur twice in the subset
    network.
    If the option has been selected, the numbers of the cordon zones
    will be generated based on the number of the connector node
    and the specified offset.
    Offset + ConnNodeNo.
    Enter an offset value
    Example
    Number of the connector node: 105
    Offset value: 10000
    Number of the cordon zone in the subnetwork: 10105
    Continuous numbering of subnetwork cordon
    zones

    Note
    Make sure that zone numbers do not occur twice in the subnetwork.
    If the option has been selected, the cordon zones are numbered
    consecutively.
    Minimum No. for generated cordon zones
    Enter the number at which the numbering starts

    Zone type for cor- Enter the number of the zone type (0..9), to which the cordon
    don zones
    zones shall be allocated
    Generate only
    required PrT cordon zones

    If the option has been selected, only those cordon zones will be
    generated to the subnetwork that are required according to the
    assignment.

    Generate all possible PrT cordon


    zones (for subsequent Vissim
    export)

    If this option has been selected, all possible cordon zones or


    connector links are generated, independently from the subnetwork. All geometry data at nodes will thus be conserved after
    the import in Vissim.

    PTVGROUP

    1603

    15.44.2 Selecting options for line routes


    Element

    Description

    Open

    Opening a subnetwork generator parameter file of the type *.xml.

    Save

    You can save your settings and re-use them later. The defined settings are saved as a subnetwork generator parameter file of the
    type *.xml.

    15.44.2 Selecting options for line routes


    In the Subnetwork generator parameter window, you can set different options:
    Entire line route from start stop point to end stop point
    The line route from start stop point to end stop point will be transferred to the subnetwork.

    Cut off the line route at the boundaries of the analysis polygon
    The line route starts within the subnetwork at the first stop point with a stop and ends within
    the subnetwork at the last stop point with a stop.

    Cut line route, include subnetwork cordon stops


    If the first or the last stop point has a stop within the subnetwork, the line route starts or ends
    at this stop. Otherwise, the line route is extended to the next stop point with a stop.

    Note: If a PuT assignment has been calculated, the following options are provided.
    Create stop point matrix (regarding path legs)
    For each path leg within the subnetwork, a cordon zone is generated at the start stop point
    and at the last stop point.
    The demand data are saved per path leg to the matrix (see Fundamentals: Chpt. 3.4 , page
    117).
    Note: The zones that were originally in the network are not stored in the matrix.

    1604

    PTVGROUP

    15.44.2 Selecting options for line routes


    Create stop point matrix (regarding paths)
    For each path within the subnetwork, a cordon zone is created for the first stop point (start).
    If the path exits the subnetwork or if a path leg is followed by a walk link which lies outside
    of the subnetwork, a cordon zone is generated at the last stop point in the subnetwork (destination). If the path enters the subnetwork again, a cordon zone is generated at the first
    stop point in the network (start).
    The demand data are saved per path to the matrix (see Fundamentals: Chpt. 3.4 , page
    117).
    Note: The zones that were originally in the network are not stored in the matrix.

    PTVGROUP

    1605

    16 Modeling demand

    16

    Modeling demand
    Travel demand develops when a sequence of activities (home- work- shopping- home) cannot be carried out at the same location and thus requires a trip (see Fundamentals: Chpt. 2.2 ,
    page 17).
    The number of movements, i.e. the number of trips between zones or main zones, is coded in
    demand matrices. These are calculated from socio-demographic data and can be reconciled
    with traffic census data.
    The temporal distribution of trips within each time interval of an observed time period is described by a start time and a demand distribution curve, which is considered as time series in
    PuT assignments and in dynamic PrT assignment. The demand distribution is ignored in the
    case of static PrT assignments.
    Demand models are used to compute the number of trips. These demand models include
    various demand objects.
    Activities, from which activity pairs and activity chains can be formed
    Person groups, in which the population is distinguished by traffic behavior
    Demand strata, connecting activity chains and person groups
    Structural properties, describing the potential of zones as origin or destination of a trip
    (only for demand models of the types EVA-P and tour-based model)
    Based on these demand models and on skim matrices, the three classic steps of traffic modeling (trip generation, trip distribution and mode choice) are calculated (see Fundamentals:
    Chpt. 4 , page 129).
    All demand data (matrices, time series, allocated demand segments and demand model data)
    constitute the demand description and are saved to demand data files *.dmd.
    Subjects
    Managing demand objects
    Calculating trip demand
    Managing, showing and analyzing matrices
    Editing matrix values
    Using matrix values for calculations
    Changing the structure of matrices
    Correcting matrices
    Reading and saving demand data

    16.1

    Managing demand objects


    A demand model consists of a set of demand objects which contain all relevant demand data,
    for example, the origin and destination of demands and the number of them in demand matrices. The demand object types in Visum are described below.
    Subjects
    Managing matrices
    Managing time series
    Managing demand objects

    1606

    PTVGROUP

    16.1.1 Managing matrices


    Managing person groups
    Managing structural properties
    Managing activities, activity pairs and activity chains
    Managing demand strata

    16.1.1

    Managing matrices
    Matrices are separate objects in Visum and part of the demand description (see Fundamentals: Chpt. 4.1.1 , page 130). Demand modeling uses different types of matrices. They
    are edited and managed fairly similarly.
    Demand matrices contain the number of trips between zones or main zones per demand
    segment.
    Skim matrices contain skim data for pairs of zones or main zones, for example travel time.
    Weighting matrices which are only used for the calculation of step Weighting of demand
    models of the type EVA-P (see "Managing weighting matrices" on page 1677)
    Note: Besides managing Visum matrices, Visum also allows you to manage matrices
    created with other programs (see "Managing, showing and analyzing matrices" on page
    1715 and "Editing matrix values" on page 1761).

    16.1.1.1

    Working with matrices


    Visum provides various functions for editing and calculating matrices. These are described
    separately:
    Managing and displaying matrices (see "Managing, showing and analyzing matrices" on
    page 1715)
    Editing and copying matrix values(see "Editing matrix values" on page 1761)
    Applying arithmetic operations to matrix values (see "Using matrix values for calculations"
    on page 1776)
    Changing the matrix dimension (see "Changing the structure of matrices" on page 1810)
    Correcting matrices (see "Correcting matrices" on page 1816)

    16.1.1.2

    Connecting demand matrices and demand segments


    For an assignment, you connect the demand (available as demand matrix per demand segment) to the demand segment of your choice. During assignment, Visum considers the
    demand stored in the allocated matrix for each of the demand segments you specified.
    Note: You can allocate the same demand matrix to several demand segments.
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Demand segments tab.
    3. In the desired demand segment row, click on the button in the Matrix column.
    The Select matrix window opens.
    4. Select the desired demand matrix.

    PTVGROUP

    1607

    16.1.2 Managing time series


    Tip: Click outside the matrix tree, if you do not want to select a matrix.
    5. Confirm with OK.
    The demand matrix is allocated to the demand segment.
    Tip: To open a Matrix editor window or access matrix data, right-click the matrix of
    your choice and select Edit or Create histogram (see "Managing, showing and analyzing matrices" on page 1715).
    6. Confirm again with OK.

    16.1.2

    Managing time series


    Time series describe the temporal distribution of trip demand within the analysis time slice
    (see Fundamentals: Chpt. 2.2 , page 17). They are taken into account for PuT assignments
    and dynamic PrT assignments. For static PrT assignments, time series are not taken into
    account (see Fundamentals: Chpt. 4.1.3 , page 131).

    16.1.2.1

    Creating standard time series


    In Visum, time series are modeled as standard time series, coding the temporal distribution of
    trip demand.
    You can create two types of standard time series:
    Time series of matrix numbers: The distribution of trip demand is defined by a selection of
    several matrices.
    Time series by percentage: The distribution of trip demand is defined by shares and can
    include a deviating distribution for OD relations between certain zone types.
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Standard time series tab.
    3. Click the Create button.
    A new standard time series is added.
    4. Make the desired settings (see "Properties and options of standard time series" on page
    1608).
    5. Confirm with OK.
    The standard time series is saved.

    16.1.2.2

    1608

    Properties and options of standard time series


    Element

    Description

    No.

    Freely selectable number for standard time series

    Name

    Name of the standard time series

    PTVGROUP

    16.1.2.3 Editing attribute data of standard time series

    16.1.2.3

    Element

    Description

    Type

    From the list, you can select the standard time series type.
    1 Time series by percentage
    2 Time series of matrix numbers
    Note
    You can only change the standard time series type if no time intervals have
    been defined (see "Creating time intervals for standard time series" on
    page 1609).

    From

    Start time of first time interval with defined OD demand (see "Creating time
    intervals for standard time series" on page 1609)
    Note
    If you connect the standard time series to a demand segment via demand
    time series (see "Combining demand time series and demand segment" on
    page 1616), the start time is counted from the start of the standard time
    series. This is set under menu Demand> Demand data > in tab Demand
    segments > Start at (see "Editing the first day (start) and start time of standard time series" on page 1613).

    To

    End time of last time interval with defined OD demand (see "Creating time
    intervals for standard time series" on page 1609)

    Editing attribute data of standard time series


    Note: The following describes how to edit the attribute values No, Name and Type. To
    edit the values of the attributes from and to, edit the time intervals defined for the standard time series (see "Editing time intervals of standard time series" on page 1612).
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Standard time series tab.
    3. Make the desired settings (see "Properties and options of standard time series" on page
    1608).
    4. Confirm with OK.
    The changes are applied.

    16.1.2.4

    Creating time intervals for standard time series


    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Standard time series tab.

    PTVGROUP

    1609

    16.1.2.4 Creating time intervals for standard time series


    3. In the list, click the standard time series you want to define time intervals for and allocate
    demand to.
    4. Click the Edit button.
    The Edit time series window opens.
    5. Click the Create button.
    A time interval is added.
    6. Make the desired changes.
    Standard time series of the type: time series by percentage
    Element

    Description

    From day

    First day (start) of the time interval

    From time

    Start time of the time interval in time format (hh or hh:mm or hh:mm:ss)

    To day

    Last day (end) of the time interval


    Note
    The time series may cover multiple days.

    To time

    End time of the time interval in time format (hh or hh:mm or hh:mm:ss)

    Weight

    Relative share of travel demand of total volume with desired departure time in respective time interval

    Share

    Percentage of travel demand with desired departure time in respective time interval
    Note
    Based on the weight, this value is calculated automatically.

    Percentages
    total

    Cumulative percentage of travel demand with desired departure time


    in respective time interval
    Note
    Based on the calculated percentage shares, this value is calculated
    automatically.

    Standard time series of the time series of matrix numbers type

    1610

    Element

    Description

    From day

    First day (start) of the time interval

    From time

    Start time of the time interval in time format (hh or hh:mm or hh:mm:ss)

    To day

    Last day (end) of the time interval


    Note
    The time series may cover multiple days.

    PTVGROUP

    16.1.2.5 Creating multiple time intervals of identical length


    Standard time series of the time series of matrix numbers type
    Element

    Description

    To time

    End time of the time interval in time format (hh or hh:mm or hh:mm:ss)

    Matrix

    You can use the button to assign each time interval a demand matrix
    that contains the OD demand and the desired departure time within
    the respective time interval.

    Note: If you connect the standard time series to a demand segment via demand time
    series (see "Combining demand time series and demand segment" on page 1616),
    From day, From time, To day and To time are counted from start day and start time
    of the standard time series. These are set under the menu Demand> Demand data>
    in the Demand segments tab > Start at (see "Editing the first day (start) and start
    time of standard time series" on page 1613).
    7. Add further time intervals, if applicable.
    Note: The time intervals need to be in ascending order and may not overlap.
    8. Confirm with OK.
    The time intervals and OD demand are saved. In the Standard time series tab, the values of
    the attributes from and to are adjusted.
    Tip: Alternatively, you can create multiple time intervals with the same duration (see
    "Creating multiple time intervals of identical length" on page 1611).
    Note: For a timetable-based assignment, you can refine the intervals by dividing them
    into time spans of equal length (homogeneous distribution of OD demand) (see "Timetable-based assignment:Basis tab" on page 2022).
    16.1.2.5

    Creating multiple time intervals of identical length


    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Standard time series tab.
    3. In the list, click the standard time series you want divide into multiple intervals of the same
    length.
    4. Click the Edit button.
    The Edit time series window opens.
    5. Click the Multiple button.
    The Create multiple time series entries window opens.

    PTVGROUP

    1611

    16.1.2.6 Editing time intervals of standard time series


    6. Make the desired changes.
    Element

    Description

    From day

    First day (start) of the first time interval of the set of intervals

    From time

    Start time in time format (hh or hh:mm or hh:mm:ss) of the first time interval of the set of intervals on start day

    To day

    Last day (end) of the last time interval of the set of intervals

    To time

    End time in time format (hh or hh:mm or hh:mm:ss) of the last time interval of the set of intervals on last day

    Time period

    Duration (in [minutes]) of the time intervals you want to insert.

    Note: If you connect the standard time series to a demand segment via demand time
    series (see "Combining demand time series and demand segment" on page 1616),
    From day, From time, To day and To time are counted from start day and start time
    of the standard time series. These are set under the menu Demand> Demand data>
    in the Demand segments tab > Start at (see "Editing the first day (start) and start
    time of standard time series" on page 1613).
    7. Confirm with OK.
    The time intervals are created.
    16.1.2.6

    Editing time intervals of standard time series


    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Standard time series tab.
    3. In the list, click the standard time series with the time interval data you want to edit.
    4. Click the Edit button.
    The Edit time series window opens.
    5. In the list, click the time interval that you want to change.
    6. Make the desired changes (see "Creating time intervals for standard time series" on page
    1609).
    7. Edit other time intervals, if applicable.
    8. Confirm with OK.
    The changes are applied to the standard time series.

    16.1.2.7

    Deleting time intervals of standard time series


    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.

    1612

    PTVGROUP

    16.1.2.8 Editing the first day (start) and start time of standard time series
    2. Select the Standard time series tab.
    3. In the list, click the standard time series with the time intervals you want to delete.
    4. Click the Edit button.
    The Edit time series window opens.
    5. In the list, click the time interval you want to delete.
    6. Click the Delete button.
    The time interval is deleted.
    7. Delete other time intervals, if applicable.
    8. Confirm with OK.
    The changes are applied to the standard time series.
    16.1.2.8

    Editing the first day (start) and start time of standard time series
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Demand segments tab.
    3. In the list, click the demand segment which is - via demand time series - connected to the
    standard time series whose start day and start time you want to edit (see "Combining
    demand time series and demand segment" on page 1616).
    4. Make the desired changes.
    Element

    Description

    First day
    (start)

    Day of the week or date when the standard time series starts that is
    connected to the demand segment via demand time series (see "Combining demand time series and demand segment" on page 1616)
    Note
    This option is only provided if a weekly or annual calendar is used (see
    "Selecting a calendar " on page 1511).

    Start at

    Start time of the standard time series that is connected to the demand
    segment via demand time series (see "Combining demand time series
    and demand segment" on page 1616).
    Entry in time format (hh or hh:mm or hh:mm:ss).
    Note
    The start time is added to the From time of the first time interval of the
    standard time series (see "Creating time intervals for standard time
    series" on page 1609).
    Example
    If the start time of a time series is 12:00:00 and the first From time is
    12:00:00, the time series will start at 00:00:00.

    PTVGROUP

    1613

    16.1.2.9 Deleting standard time series


    5. Confirm with OK.
    The changes are applied.
    16.1.2.9

    Deleting standard time series


    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Standard time series tab.
    3. From the list of standard time series, select the one you want to delete.
    4. Click the Delete button.
    If this standard time series has been connected to a time series by pair of zone types and/or
    to demand time series, a security query opens (see "Allocating different standard time
    series to relations between certain zone types" on page 1615 and "Creating demand time
    series" on page 1614).
    5. Confirm the query with Yes.
    The standard time series and the particular zone type-based time series and/or demand time
    series are deleted.

    16.1.2.10 Creating demand time series


    For assignment, the temporal distribution of trip demand needs to be connected to the OD
    demand. The OD demand is stored as demand matrix per demand segment (see Fundamentals: Chpt. 4.1.1 , page 130). To make the connection, specify a standard time series as
    demand time series and assign it to a demand segment (see "Combining demand time series
    and demand segment" on page 1616).
    Note: You can edit the standard time series for OD pairs of selected zone types. To do so,
    assign the OD pairs of your choice to different standard time series (see "Allocating different standard time series to relations between certain zone types" on page 1615).
    However, you can only do so for time series in percent.
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Demand time series tab.
    3. Click the Create button.
    A new demand time series is added.
    4. Make the desired changes.

    1614

    PTVGROUP

    16.1.2.11 Allocating different standard time series to relations between certain zone types
    Element

    Description

    No.

    Freely selectable number for demand time series

    Code

    Short name of the demand time series

    Name

    Long name of the demand time series

    Standard time
    series

    From the selection list, you can allocate a standard time series to
    the demand time series.

    5. Confirm with OK.


    The demand time series is saved.
    16.1.2.11 Allocating different standard time series to relations between certain zone types
    Note: To edit the standard time series, the demand time series must first be assigned a
    standard time series in percent (see "Properties and options of standard time series" on
    page 1608).
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Demand time series tab.
    3. In the list, select the demand time series whose standard time series you want to edit between certain zone types.
    4. Click the Edit button.
    The Edit time series per pair of zone types window opens.
    5. Click the Create button.
    The Create zone type time series window opens.
    6. Make the desired changes.
    Element

    Description

    From type

    Zone type of the origin zone

    To type

    Zone type of the destination zone

    Standard time
    series

    Use the list box to select a different standard time series (than the
    one in percent you previously chose) for the respective OD pair.

    7. Confirm with OK.


    A new row is added to the list. It shows the desired zone type pair and the allocated standard time series.
    8. Add further pairs of zone types, if required.

    PTVGROUP

    1615

    16.1.2.12 Combining demand time series and demand segment


    9. To edit the standard time series of a zone type pair in the list, use the respective Standard
    time series list.
    10. If required, in the list, click the row you want to delete.
    11. Click the Delete button.
    The row is deleted.
    12. Confirm with OK.
    The changes are applied.
    16.1.2.12 Combining demand time series and demand segment
    The distribution of travel demand is coded in standard time series and trip demand is coded in
    matrices. To combine both data, you need to allocate each standard time series to a demand
    time series first (see "Creating demand time series" on page 1614) . Furthermore, each
    demand matrix needs to be combined with a demand segment (see "Connecting demand
    matrices and demand segments" on page 1607). Then each demand time series needs to be
    combined with the corresponding demand segment.
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Demand segments tab.
    3. In the list, select the demand segment you would like to combine with a demand time
    series.
    4. In the Demand time series selection list, click the desired demand time series.
    The demand time series is connected to the demand segment.
    16.1.2.13 Deleting demand time series
    1. In the Demand menu, click the Demand data entry.
    The OD demand data window opens.
    2. Select the Demand time series tab.
    3. From the list of demand time series, select the one you want to delete.
    4. Click the Delete button.
    If this demand time series has been connected to time series by pair of zone types and
    demand segments, a security query opens (see "Allocating different standard time series to
    relations between certain zone types" on page 1615 and "Combining demand time series
    and demand segment" on page 1616).
    5. Confirm the query with Yes.
    The demand time series, its zone type-based time series and references to demand segments
    are deleted.

    1616

    PTVGROUP

    16.1.3 Managing demand objects

    16.1.3

    Managing demand objects


    Demand models are particular Visum demand objects to which further demand objects (person groups, activities, activity pairs and activity chains, demand strata, structural properties)
    are assigned (see Fundamentals: Chpt. 4.1.4 , page 131). They allow to define and store
    various computation models for demand modeling in Visum(see Fundamentals: Chpt. 2.2 ,
    page 17).

    16.1.3.1

    Creating a demand model


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Click the Create button.
    A new demand model is added.
    4. Make the desired settings (see "Properties and options of demand models" on page 1617).
    Tip: Alternatively, you can read a pre-defined demand model and corresponding data
    from a demand data file (see "Importing predefined demand models *.dmd" on page
    1619).
    5. Confirm with OK.
    The demand model is saved.

    16.1.3.2

    Properties and options of demand models


    Element

    Description

    Code

    Short name of the demand model

    Name

    Long name of the demand model

    Type

    From the selection list, you can select the type of demand model computation (see Fundamentals: Chpt. 2.2 , page 17).
    Standard 4-Step
    EVA-P
    Tour-based model
    Notes
    To make the computation types EVA-P and Tour-based model available, check the add-ons EVA for passenger demand and Tour-based
    model (see "Enabling or disabling installed add-ons" on page 886).
    You cannot edit the demand model type Tour-based model after the definition of activity chains for the demand model (see "Creating an activity
    chain" on page 1631).

    PTVGROUP

    1617

    16.1.3.3 Editing attribute data of demand models

    16.1.3.3

    Element

    Description

    Modes

    Relevant modes for the demand model

    Balancing executed (EVA)

    The checkbox indicates whether or not the constraint balancing has


    been calculated for at least one demand stratum of the demand model
    (see Fundamentals: Chpt. 4.2.2.2 , page 146).
    Note
    This option is only provided for demand models of the EVA-P type.

    Editing attribute data of demand models


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. In the list, select the demand model whose attribute values you would like to edit.
    4. Make the desired settings (see "Properties and options of demand models" on page 1617).
    5. Confirm with OK.
    The changes are applied.

    16.1.3.4

    Deleting demand models


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. From the list of demand models, select the one you want to delete.
    Tip: To mark multiple demand models press the C TRL key and keep it pressed while
    clicking the desired entries one by one.
    4. Click the Delete button.
    If demand objects have been allocated to the demand models, a security prompt opens.
    5. Select the demand models to be deleted.

    1618

    Element

    Description

    Yes

    The demand model listed in the window is deleted and also the
    demand objects allocated to it.

    Yes for all

    All remaining demand models are deleted and also the demand
    objects allocated to them.

    PTVGROUP

    16.1.3.5 Importing predefined demand models *.dmd


    Element

    Description

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    The demand models and allocated demand objects are deleted.


    Note: You may not delete all of the demand models in the network. At least one demand
    model needs to be defined.
    16.1.3.5

    Importing predefined demand models *.dmd


    A quick and easy way to supply a version file with data is to read pre-defined demand models
    and their corresponding data from a demand data file *.dmd.
    Tip: Here you can find the demand model templates provided with the program: ...\Program files\PTV Vision\PTV Visum 13\Data\Demand_Templates.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Click the Load model template button.
    The Open model template window opens.
    4. Select the demand data file you want to use.
    5. Click the Open button.
    A query opens.
    6. Confirm with Yes.
    The demand model and corresponding demand objects are read additionally.
    Tip: Alternatively, you can read tour-based demand models and their corresponding data
    from tour-based model data files (see "Reading tour-based demand models from VISEM
    data files (*.vhd)" on page 1619).

    16.1.3.6

    Reading tour-based demand models from VISEM data files (*.vhd)


    In the demand calculation program VISEM 8.X, model data are stored in input data files *.vhd.
    In Visum, you can read tour-based demand models, all corresponding demand objects and
    the procedure parameters required for the operation Tour-based model - Trip generation from
    a VISEM input data file *.vhd. VISEM input matrices are read as skim matrices.
    Note: In Visum, a tour-based model input data file *.vhd you can read from file only additionally to an existing network.

    PTVGROUP

    1619

    16.1.4 Managing person groups


    1. In the Demand menu, click the entry Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Click the Load model template button.
    The Open model template window opens.
    4. Select the *.vhd file of your choice.
    5. Click the Open button.
    A query opens.
    6. Confirm with Yes.
    A tour-based demand model and its corresponding demand objects are created. All modes
    defined in the existing network are selected as relevant modes. For each VISEM input matrix a
    new skim matrix is created. The procedure Tour-based model - Trip generation is automatically added at the end of the procedure sequence and the parameters are set automatically.

    16.1.4

    Managing person groups


    The population living in the planning area is broken down into so-called "behavior- homogeneous" groups (see Fundamentals: Chpt. 2.2 , page 17). The traffic behavior of the different
    groups should be clearly different, but within the individual groups it should be as homogeneous as possible (see Fundamentals: Chpt. 4.1.5 , page 132).

    16.1.4.1

    Creating a person group


    1. In the Demand menu, click the entry Demand models entry.
    The Demand models window opens.
    2. Select the Person groups tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. Click the Create button.
    A new person group is created.
    5. Make the desired settings (see "Properties and options of person groups" on page 1620).
    6. Confirm with OK.
    The person group is saved.

    16.1.4.2

    1620

    Properties and options of person groups


    Element

    Description

    Code

    Short name of the person group

    Name

    Long name of the person group

    PTVGROUP

    16.1.4.3 Editing attribute data of person groups


    16.1.4.3

    Editing attribute data of person groups


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Person groups tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list, select the person group whose attribute values you would like to edit.
    5. Make the desired settings (see "Properties and options of person groups" on page 1620).
    6. Confirm with OK.
    The changes are applied.

    16.1.4.4

    Editing the number of persons in a person group


    In the zones list, you can show and edit the Number of persons attribute for any zone or person group (see "Adjusting the list layout" on page 2308 and "Editing the properties of objects
    in lists" on page 2321).
    Tip: If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. Open the Zones list (see "Opening a list" on page 2299).
    2. From the selection list, select the pre-defined list layout Person groups and Structural properties.
    For each person group, a column with attribute Number of persons is displayed.
    3. Edit the attribute value for each desired zone and person group (see "Editing the properties
    of objects in lists" on page 2321).
    4. Confirm with OK.
    The changes are applied.

    16.1.4.5

    Deleting person groups


    1. In the Demand menu, click the entry Demand models entry.
    The Demand models window opens.
    2. Select the Person groups tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list of person groups, select the one you want to delete.
    Tip: To select multiple person groups, press the C TRL key and keep it pressed while
    clicking the desired person groups one by one.

    PTVGROUP

    1621

    16.1.5 Managing structural properties


    5. Click the Delete button.
    If a person group has been allocated to a demand stratum, a security query opens.
    6. Select the person groups to be deleted.
    Element

    Description

    Yes

    The person group listed in the window is deleted and also the
    demand strata allocated to it.

    Yes for all

    All remaining marked person groups are deleted and also the
    demand strata which refer to them.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    The person groups and corresponding demand strata are deleted.

    16.1.5

    Managing structural properties


    Structural properties are used to measure the zone attractiveness as origin or destination of a
    journey. They, for example, include sales floor areas or the number of school places.
    Note: You can define structural properties for demand model of EVA-P (see Fundamentals: Chpt. 4.2.2.1 , page 142) or tour-based model type (see Fundamentals: Chpt.
    4.2.3.1 , page 175).

    16.1.5.1

    Creating a structural property


    1. In the Demand menu, click the entry Demand models entry.
    The Demand models window opens.
    2. Select the Structural properties tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. Click the Create button.
    A new structural property is added.
    5. Make the desired settings (see "Properties and options of structural properties" on page
    1622).
    6. Confirm with OK.
    The structural property is saved.

    16.1.5.2

    1622

    Properties and options of structural properties

    PTVGROUP

    16.1.5.3 Editing attribute data of structural properties

    16.1.5.3

    Element

    Description

    Code

    Short name of the structural property

    Name

    Long name of the structural property

    Editing attribute data of structural properties


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Structural properties tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list, select the structural property whose attribute values you would like to edit.
    5. Make the desired settings (see "Properties and options of structural properties" on page
    1622).
    6. Confirm with OK.
    The changes are applied.

    16.1.5.4

    Editing structural property data


    For each zone you can display and edit the values of the structural properties in the zones list
    (see "Adjusting the list layout" on page 2308 and "Editing the properties of objects in lists" on
    page 2321).
    Tip: If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. Open the Zones list (see "Opening a list" on page 2299).
    2. From the selection list, select the pre-defined list layout Person groups and Structural properties.
    A column with the ValStructuralProp <Structural property code> attribute is displayed for
    each structural property.
    3. Edit the attribute values for each desired zone and structural property (see "Editing the properties of objects in lists" on page 2321).
    4. Confirm with OK.
    The changes are applied.

    16.1.5.5

    Deleting structural properties


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Structural properties tab.

    PTVGROUP

    1623

    16.1.6 Managing activities, activity pairs and activity chains


    3. In the Select demand model list, click the demand model of your choice.
    4. From the list of structural properties, select the ones you want to delete.
    Tip: To select multiple structural properties, press the C TRL key and keep it pressed
    while clicking the desired structural properties one by one.
    5. Click the Delete button.
    If a structural property has been allocated to a demand object, a security query opens.
    6. Select the structural properties to be deleted.
    Element

    Description

    Yes

    The structural property listed in the window is deleted and also


    the demand objects allocated to it.

    Yes for all

    All remaining marked structural properties are deleted and also


    the demand objects allocated to them.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    The structural properties and corresponding demand objects are deleted.

    16.1.6

    Managing activities, activity pairs and activity chains


    The demand model is based on the assumption that trip purposes or external activities cause
    mobility (see Fundamentals: Chpt. 2.2 , page 17).
    An activity pair corresponds to the trip between two successive activities in the daily routine of
    a person.
    An activity chain describes a sequence of typified activities in the daily routine of a person. For
    example, the chain home work shopping home (HWOH). Such a sequence of activity
    pairs implies trips, in this example here three different trips: HW, WO, OH (see Fundamentals:
    Chpt. 4.1.6 , page 132).

    16.1.6.1

    Creating an activity
    Note: Interactively, you may define activities only for demand models of the EVA-P type
    or of the tour-based model type. In the case of Standard 4-step models, one activity corresponds to exactly one activity pair.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activities tab.
    3. In the Select demand model list, click the demand model of your choice.

    1624

    PTVGROUP

    16.1.6.2 Properties and options of activities


    4. Click the Create button.
    A new activity is added.
    5. Make the desired settings (see "Properties and options of activities" on page 1625).
    6. Confirm with OK.
    The activity is saved.
    16.1.6.2

    Properties and options of activities


    Demand models of the EVA-P type
    Element

    Description

    Code

    Short name of the activity

    Name

    Long name of the activity

    HOME activity

    If this option has been selected, the activity is defined as home location of traveling persons.
    Note
    You can select only one activity as HOME activity.

    Structural properties

    This button opens a separate window for the respective activity. Here
    you can select the production or attraction potential properties for trip
    generation (see Fundamentals: Chpt. 4.2.2.1 , page 142).

    Demand models of the tour-based model type


    Element

    Description

    Code

    Short name of the activity

    Name

    Long name of the activity

    HOME activity

    If this option has been selected, the activity is defined as home location of traveling persons.
    Note
    You can select only one activity as HOME activity.

    Structural property

    This button opens a separate window for the respective activity. Here
    you can select the attraction potential properties for trip distribution
    (see Fundamentals: Chpt. 4.2.3.1 , page 175).

    Destination-bound If this option has been selected, Tour-based model - Trip distribution
    binding
    will regard the destination binding for the particular activity (see Fundamentals: Chpt. 4.2.3.1 , page 175).
    Note
    For the home activity, destination binding is always regarded.
    CF DMin

    PTVGROUP

    Factor for the lower limit of the attraction (see Fundamentals: Chpt.
    4.2.3.1 , page 175)

    1625

    16.1.6.3 Editing attribute data of activities


    Demand models of the tour-based model type
    Element

    Description
    Notes
    This option is only provided, if option Destination-bound binding has
    been selected for this activity.
    For the home activity, the factor is always 1.0.

    CF DMax

    Factor for the upper limit of the attraction (see Fundamentals: Chpt.
    4.2.3.1 , page 175)
    Notes
    This option is only provided, if option Destination-bound binding has
    been selected for this activity.
    For the home activity, the factor is always 1.0.

    Note: The factors CF DMin and CF DMax define a constraint for the destination side. For
    the origin side, the constraint is always hard. Then the (origin and destination bound) distribution is calculated for each activity pair according to the constraint factors chosen for
    the destination side (see Fundamentals: Chpt. 4.2.3.3 , page 178).
    16.1.6.3

    Editing attribute data of activities


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activities tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list, select the activity whose attribute values you would like to edit.
    5. Make the desired settings (see "Properties and options of activities" on page 1625).
    6. Confirm with OK.
    The changes are applied.

    16.1.6.4

    Deleting activities
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activities tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list of activities, select the ones you want to delete.
    Tip: To mark multiple activities, press the C TRL key and keep it pressed while clicking
    the desired entries one by one.

    1626

    PTVGROUP

    16.1.6.5 Creating an activity pair


    5. Click the Delete button.
    If the activities have been connected with activity pairs, a security query opens.
    6. Select the activities to be deleted.
    Element

    Description

    Yes

    The activity listed in the window is deleted and also the activity pairs
    and sequences of activities of activity chains which refer to the activity.

    Yes for all

    All remaining marked activities are deleted and also the activity pairs
    and sequences of activities of activity chains which refer to the activity.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    The activities and the corresponding activity pairs as well as the sequences of activities of activity chains are deleted.
    16.1.6.5

    Creating an activity pair


    There are two ways to create activity pairs:
    One by one
    Automatically for marked activities
    Note: For demand models of the tour-based model type, activity pairs are created automatically if you define the sequence of activities of an activity chain (see "Properties and
    options of activity chains" on page 1632). You may also create activity pairs individually
    or have them inserted automatically for selected activities.
    Creating activity pairs one by one
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity pairs tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. Click the Create button.
    A new activity pair is added.
    5. Make the desired settings (see "Properties and options of activity pairs" on page 1628).
    6. Confirm with OK.
    The activity pair is saved.
    Having activity pairs inserted for selected activities
    You can have the respective activity pairs inserted automatically for the activities you select.

    PTVGROUP

    1627

    16.1.6.6 Properties and options of activity pairs


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activities tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the activities you would like to create the corresponding activity pairs for.
    Tip: To mark multiple activities, press the C TRL key and keep it pressed while clicking
    the desired entries one by one.
    5. Click the Create activity pairs button.
    For each combination of the selected activities with any other activity in the list, two activity
    pairs are created - one for each direction. In addition, another activity pair is created for
    each selected activity, where the selected activity is both origin and destination.
    Note: If you select several activities, a message is displayed informing you about activity pairs that already exist.
    6. Confirm the message with OK for all.
    7. Make the desired settings (see "Properties and options of activity pairs" on page 1628).
    8. Confirm with OK.
    The activity pairs are saved.
    16.1.6.6

    Properties and options of activity pairs


    Demand models of the Standard 4-step type
    Element

    Description

    Code

    Short name of the activity pair

    Name

    Long name of the activity pair

    Demand models of the EVA-P type


    Element

    Description

    Code

    Short name of the activity pair

    Name

    Long name of the activity pair

    Origin activity Via the particular selection list you define the trip's source activity of the
    activity pair.
    Note
    An empty entry is permitted.
    Destination

    1628

    Via the particular selection list you define the trip's target activity of the acti-

    PTVGROUP

    16.1.6.7 Editing attribute data of activity pairs


    Demand models of the EVA-P type
    Element

    Description

    activity

    vity pair.
    Note
    An empty entry is permitted.

    OD type

    Display of the direction of the activity pair with regard to the HOME activity
    (see Fundamentals: Chpt. 4.2.2.2 , page 146).
    1 = Origin activity is HOME activity, e.g. HOME-Work
    2 = Destination activity is HOME activity, e.g. Shopping-HOME
    3 = Neither origin nor destination activity is HOME activity, e.g. WorkShopping
    By default, the direction is derived from the activity that has been selected
    as HOME activity (see "Properties and options of activities" on page
    1625). Via the selection list you can change the current direction settings.

    Demand models of the tour-based model type


    Element

    Description

    Code

    Short name of the activity pair

    Name

    Long name of the activity pair

    Origin activity Via the particular selection list you define the trip's source activity of the
    activity pair.
    Note
    An empty entry is permitted.

    16.1.6.7

    Destination
    activity

    Via the particular selection list you define the trip's target activity of the activity pair.
    Note
    An empty entry is permitted.

    Time series

    Via this button you can - in a separate window - allocate person groups to
    input standard time series as percentages for the computation of OD
    demand by the hour (see "Connecting activity pairs and standard time
    series" on page 1630).

    Editing attribute data of activity pairs


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity pairs tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the activity pair whose attribute values you would like to edit.

    PTVGROUP

    1629

    16.1.6.8 Connecting activity pairs and standard time series


    5. Make the desired settings (see "Properties and options of activity pairs" on page 1628).
    6. Confirm with OK.
    The changes are applied.
    16.1.6.8

    Connecting activity pairs and standard time series


    With the demand model of the tour-based model type you can calculate the OD demand even
    by the hour; therefore you need to connect the standard time series as percentages with activity pairs and person groups (see "Properties and options of standard time series" on page
    1608).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity pairs tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the activity pair you would like to combine with standard time series and
    person groups.
    5. In the Time series column, click the corresponding button.
    The Select time series window opens.
    6. Make the desired changes.
    Element

    Description

    The same time


    series for all person groups

    If this option has been selected, the same standard time series is
    allocated to all person groups. From the selection list, you can
    select the standard time series.

    Separate time
    If this option has been selected, you can select a specific stanseries per person dard time series for each person group; therefore, you need to
    group
    mark the desired person group in the list and select the standard
    time series from the particular selection list in the Time series
    column.
    7. Confirm with OK.
    Allocation is applied.
    16.1.6.9

    Deleting activity pairs


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity pairs tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list of activity pairs, select the ones you want to delete.

    1630

    PTVGROUP

    16.1.6.10 Creating an activity chain


    Tip: To mark multiple activity pairs press the C TRL key and keep it pressed while
    clicking the desired entries one by one.
    5. Click the Delete button.
    If the activity pairs have been allocated to demand strata or belong to an activity chain, a
    security query opens.
    6. Select the activity pairs to be deleted.
    Element

    Description

    Yes

    The activity pair listed in the window is deleted and also the demand
    strata or sequences of activities of activity chains which refer to the activity pair.

    Yes for all

    All remaining marked activity pairs and also the demand strata or
    sequences of activities of activity chains which refer to the activity pairs.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    The activity pairs and also the corresponding demand strata and sequences of activities of activity chains are deleted.
    16.1.6.10 Creating an activity chain
    Note: Interactively, you can define activity chains only for demand models of the tourbased model type. In the case of Standard 4-step models and EVA-P models one activity
    chain corresponds to exactly one activity pair (see Fundamentals: Chpt. 4.1.6 , page
    132).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity chains tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. Click the Create button.
    The Create activity chain window opens. The Sequence section contains an activities field
    for the desired activities of the activity chain. The home activity is displayed before and after
    the field.
    5. In the Create activity section, select the first activity of your choice.
    6. Click the

    Create activity icon.

    The activity code is entered in the upper field.


    7. Add further activities in the sequence required.
    PTVGROUP

    1631

    16.1.6.11 Properties and options of activity chains

    Note: The activity codes are automatically separated by a comma.


    Tip: You can also enter or edit the activity codes manually. Make sure you separate
    them using a comma.
    8. Confirm with OK.
    The activity chain is saved.
    16.1.6.11 Properties and options of activity chains
    Element

    Description

    Code

    Short name of the activity chain

    Name

    Long name of the activity chain

    Sequence of activities

    Comma-separated list of the codes of those activities forming the


    chain.
    Notes
    HOME activity is always the first and the last activity of a chain (see
    "Properties and options of activities" on page 1625).
    As soon as you enter a sequence of activities, the corresponding activity pairs are created automatically.

    16.1.6.12 Editing attribute data of activity chains


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity chains tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the activity chain whose attribute values you would like to edit.
    5. Make the desired settings (see "Properties and options of activity chains" on page 1632).
    6. Confirm with OK.
    The changes are applied.
    16.1.6.13 Deleting activity chains
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity chains tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list of activity chains, select the ones you want to delete.

    1632

    PTVGROUP

    16.1.7 Managing demand strata


    Tip: To mark multiple activity chains press the C TRL key and keep it pressed while
    clicking the desired entries one by one.
    5. Click the Delete button.
    If the activity chains have been connected with demand strata, a security query opens.
    6. Select the activity chains to be deleted.
    Element

    Description

    Yes

    The activity chain listed in the window is deleted and also the demand
    strata which refer to it.

    Yes for all

    All remaining marked activity chains are deleted and also the demand
    strata which refer to them.

    No

    The action is cancelled.

    No for all

    The action is cancelled.

    Cancel

    The action is cancelled.

    The activity chains and corresponding demand strata are deleted.

    16.1.7

    Managing demand strata


    The demand stratum constitutes the basic demand object for calculating trip generation, trip
    distribution and mode choice (see Fundamentals: Chpt. 2.2 , page 17). It links an activity chain
    to one or several person groups (see Fundamentals: Chpt. 4.1.7 , page 134).
    For the complete list of demand strata, call menu Lists (see "Opening a list" on page 2299).

    16.1.7.1

    Creating a demand stratum


    There are several ways to create demand strata.
    Creating demand strata one by one
    Creating demand strata automatically for marked activity pairs
    Creating demand strata automatically for marked person groups
    Creating demand strata automatically for marked activity chains
    Note: If you create demand strata for a demand model of the EVA-P type, Visum can
    create a weighting matrix for each mode per demand stratum (see "Managing weighting
    matrices" on page 1677). In the EVA weighting procedure, values are assigned to the
    weighting matrices (see "Calculating EVA weighting" on page 1671).
    Creating demand strata one by one
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Demand strata tab.
    3. In the Select demand model list, click the demand model of your choice.

    PTVGROUP

    1633

    16.1.7.1 Creating a demand stratum


    4. Click the Create button.
    A new demand stratum is added.
    5. Make the desired settings (see "Properties and options of demand strata" on page 1635).
    6. Confirm with OK.
    The demand stratum is saved.
    Creating demand strata automatically for marked activity pairs
    If you would like to create multiple demand strata you can create the corresponding demand
    strata automatically for selected activity pairs of demand models of the Standard 4-step type or
    of the EVA-P type.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity pairs tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the activity pairs you would like to create the corresponding demand strata
    for.
    Tip: To mark multiple activity pairs press the C TRL key and keep it pressed while
    clicking the desired entries one by one.
    5. Click the Create demand strata button.
    For the selected activity pairs as many demand strata are created as person groups have
    been defined (see "Managing person groups" on page 1620).
    6. Make the desired settings (see "Properties and options of demand strata" on page 1635).
    7. Confirm with OK.
    The demand strata are saved.
    Creating demand strata automatically for marked person groups
    If you would like to create multiple demand strata you can create the corresponding demand
    strata automatically for person groups.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Person groups tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the person groups you would like to create the corresponding demand
    strata for.

    1634

    PTVGROUP

    16.1.7.2 Properties and options of demand strata


    Tip: To select multiple person groups, press the C TRL key and keep it pressed while
    clicking the desired person groups one by one.
    5. Click the Create demand strata button.
    For the marked person groups as many demand strata are created as activity pairs (Standard 4-step and EVA-P) or activity chains (tour-based model) have been defined (see
    "Managing activities, activity pairs and activity chains" on page 1624).
    6. Make the desired settings (see "Properties and options of demand strata" on page 1635).
    7. Confirm with OK.
    The demand strata are saved.
    Creating demand strata automatically for marked activity chains
    If you would like to create multiple demand strata you can create the corresponding demand
    strata automatically for selected activity chains of demand models of the tour-based model
    type.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Activity chains tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the activity chains you would like to create the corresponding demand
    strata for.
    Tip: To mark multiple activity chains press the C TRL key and keep it pressed while
    clicking the desired entries one by one.
    5. Click the Create Demand strata button.
    For the marked activity chains as many demand strata are created as person groups have
    been defined (see "Managing person groups" on page 1620).
    6. Make the desired settings (see "Properties and options of demand strata" on page 1635).
    7. Confirm with OK.
    The demand strata are saved.
    16.1.7.2

    Properties and options of demand strata


    Demand models of the Standard 4-step type
    Element

    Description

    Code

    Short name of the demand stratum

    Name

    Long name of the demand stratum

    PTVGROUP

    1635

    16.1.7.2 Properties and options of demand strata


    Demand models of the Standard 4-step type
    Element

    Description

    Person groups

    Via this button, you may - in a separate window - select the person
    groups the demand stratum refers to.

    Activity pair

    In the selection list, you may select the activity pair the demand stratum
    refers to.

    Demand matrix
    (result of distribution)

    Using the button you can select the demand matrix for storing the
    results of trip distribution for the particular demand stratum (see "Calculating trip distribution" on page 1643).

    DSeg

    Demand segment allocated to the result demand matrix (see "Connecting demand matrices and demand segments" on page 1607).

    Demand models of the EVA-P type


    Element

    Description

    Code

    Short name of the demand stratum

    Name

    Long name of the demand stratum

    Person groups

    Via this button, you may - in a separate window - select the person
    groups the demand stratum refers to.

    Activity pair

    In the selection list, you may select the activity pair the demand stratum refers to.

    OD type

    Direction of the corresponding activity pair (see "Properties and options of activity pairs" on page 1628)

    Structural properties - origin

    You can use the button to select the values from which the production is computed in trip generation for the respective demand stratum in a separate window (see Fundamentals: Chpt. 4.2.2.1 , page
    142).

    Structural properties - destination

    You can use the button to select the values from which the production is computed in trip generation for the respective demand stratum in a separate window (see Fundamentals: Chpt. 4.2.2.1 , page
    142).

    Demand models of the tour-based model type

    1636

    Element

    Description

    Code

    Short name of the demand stratum

    Name

    Long name of the demand stratum

    Person groups

    Via this button, you can select the person group the demand stratum
    refers to.

    Activity chain

    In the selection list, you can select the activity chain the demand stratum refers to.
    PTVGROUP

    16.1.7.3 Editing attribute data of demand strata


    16.1.7.3

    Editing attribute data of demand strata


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. In the Select demand model list, click the demand model of your choice.
    3. Select the Demand strata tab.
    4. In the list, select the demand stratum whose attribute values you would like to edit.
    5. Make the desired settings (see "Properties and options of demand strata" on page 1635).
    6. Confirm with OK.
    The changes are applied.
    Tip: Alternatively, you can open the Demand strata list and edit the values in it (see "Opening a list" on page 2299 and "Working with lists" on page 2299).

    16.1.7.4

    Deleting demand strata


    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Demand strata tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. From the list of demand strata, select the ones you want to delete.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    5. Click the Delete button.
    The demand strata are deleted.

    16.2

    Calculating trip demand


    For modeling realistic demand scenarios, mathematical models are used for computation of
    the interzonal flows within the planning area. The computation is based on structural properties and behavior data of the population and also takes the utilization of the area and the
    transport supply side into account (see Fundamentals: Chpt. 4.2 , page 136).
    In Visum, you can use the following methods for trip demand calculation:
    Standard 4-step model (see "Calculating demand with the Standard 4-step model" on
    page 1638)
    EVA (see "Calculating demand with the EVA-P model" on page 1661)
    Tour-based model (see "Demand calculation with the tour-based model (VISEM)" on
    page 1683)

    PTVGROUP

    1637

    16.2.1 Calculating demand with the Standard 4-step model


    Note: You can only calculate trip demand with matrices of the zone matrix type (see "Showing and editing matrix attribute values" on page 1731).
    There are also the following functions available for travel demand calculations:
    Estimate gravitation parameters (KALIBRI)
    Creating a procedure sequence automatically
    Starting the iterative repetition
    In addition, you can calculate a standardized assessment:
    Managing, showing and analyzing matrices

    16.2.1

    Calculating demand with the Standard 4-step model


    The following step-by-step instruction illustrates the typical work flow for demand calculation
    with the help of the Standard 4-step model (see Fundamentals: Chpt. 4.2.1 , page 136).
    1. Construct the network model (transport supply) (see "Editing the network" on page 957).
    2. Create zones (see "Creating a zone" on page 1136).
    3. Connect the zones to nodes in the network (see "Creating a connector" on page 1160).
    4. Create a demand model, activity pairs, person groups and demand strata and define their
    properties (see "Managing demand objects" on page 1606).
    5. Create a procedure sequence with the model operations Trip generation, Trip distribution
    and Mode choice or Nested mode choice (see "Setting up and starting the procedure
    sequence" on page 1847).
    6. For each procedure, set the parameters.
    7. Add procedures to the procedure sequence, e.g. procedures for departure time calculation
    (see "Calculating Time-of-day choice" on page 1658), skim matrix calculation (see "Calculating:PrT skims" on page 1984 and "Calculating PuT skims" on page 2073) and, if required, for assignment and iterative repetition of the procedure sequence (see "Starting the
    iterative repetition" on page 1697).
    8. Execute the procedure sequence (see "Executing procedures in the procedure sequence"
    on page 1857).

    16.2.1.1

    Calculating trip generation


    Trip generation means the calculation of the production and attraction values per zone.
    Production and attraction result from the total of a variable set of numerical zone attributes, for
    example number of inhabitants or jobs, multiplied by coefficients (see Fundamentals: Chpt.
    4.2.1.1 , page 138).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.

    1638

    PTVGROUP

    16.2.1.1 Calculating trip generation


    2. To the procedure sequence, at the position of your choice, add the procedure Trip generation which is provided in the Demand model category (see "Setting up and starting the
    procedure sequence" on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Demand strata selection window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    5. In the Demand stratum selection list, select the demand strata you would like to calculate
    the trip generation for.
    Tip: To select multiple demand strata, hold down the C TRL while clicking the desired
    entries one by one.
    6. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Trip generation parameters window opens.
    8. Make the desired settings for all demand strata.
    Element

    Description

    Linear combination of attributes for active


    zones only

    Select this option to have the attribute values calculated for active
    zones only.

    Use 0 to initialize
    the passive zone
    attributes

    Select this option to set the attribute values of passive zones to


    zero.

    Matrix balancing
    for active zones
    only

    Select this option to consider active zones only for scaling of


    sums.

    Sum up values

    Select this option to add the calculated values to the existing


    attribute values.

    If the option is not activated, the attribute values of the passive


    zones remain unchanged.

    If this option is not selected, the existing attribute values are


    replaced by the calculated values.
    9. Specify per demand stratum how you want Visum to calculate trip generation.

    PTVGROUP

    1639

    16.2.1.1 Calculating trip generation


    Element

    Description

    Demand stratum

    In this column, the selected demand strata are listed. For each
    demand stratum, separate settings can be made.

    Matrix balancing

    If the production and attraction sums differ, use the drop-down list
    to specify the sum (productions, attractions) you want to base the
    trip generation on.

    Production rate

    The button opens the Production rate for <demand stratum>


    window.
    The production rate is a coefficient by which the attribute value is
    multiplied for the calculation of the production.
    You can specify a different production rate for each demand stratum.
    Create: Adds a new entry for the calculation of the production
    rate
    Delete: Removes the marked entry from the list
    Use the icons to move up or down in the list of
    demand strata.
    >Attraction rate: Use the button to switch to the Attraction
    rate for <demand stratum> window.
    Attribute column: Click this button to select a numerical zone
    attribute (and subattribute, if available) in a separate window
    (see "The window used for the selection of one attribute" on
    page 963).
    Note
    If you want to use absolute production and attraction rate values,
    select the constant value 1.0 instead of a zone attribute.

    Attraction rate

    The button opens the Attraction rate for demand stratum window.
    The attraction rate is a coefficient by which the attribute value is
    multiplied for the calculation of the attraction.
    You can specify a different attraction rate for each demand stratum.
    Create: Adds a new entry for the calculation of the attraction
    rate
    Delete: Removes the marked entry from the list
    Use the icons to move up or down in the list of
    demand strata.
    <Production rate: The button opens the Production rate for
    demand stratum window.
    Attribute column: Click this button to select a numerical zone
    attribute (and subattribute, if available) in a separate window

    1640

    PTVGROUP

    16.2.1.2 Editing the demand of Standard 4-step demand strata


    Element

    Description
    (see "The window used for the selection of one attribute" on
    page 963).
    Note
    If you want to use absolute production and attraction rate values,
    select the constant value 1.0 instead of a zone attribute.

    Apply to all
    DStrata

    Click this button to adopt the current settings for the matrix balancing and the production and attraction rates in all demand strata.

    10. Confirm with OK.


    11. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Trip generation is calculated. For each demand stratum the calculation results are stored as
    zone attributes Production and Attraction (see "Zones: DStrata tab" on page 1140 and
    "Editing the demand of Standard 4-step demand strata" on page 1641).
    Tip: You can display the results in zone lists or in the network graphics (see "Displaying
    data graphically and in lists" on page 2299).
    16.2.1.2

    Editing the demand of Standard 4-step demand strata


    You can edit the values calculated in the trip generation step for a demand stratum's production or attraction rate (see "Starting the iterative repetition" on page 1697).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Demand strata tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the demand stratum whose production and attraction rate values you
    would like to edit.
    5. Click the Productions/Attractions button.
    The Define productions/attractions window opens.
    6. Make the desired changes.
    Element

    Description

    Production

    Number of trips starting from the given zone by demand stratum


    The value is calculated in the trip generation step.

    Attraction

    Number of trips heading to the given zone by demand stratum


    The value is calculated in the trip generation step.

    PTVGROUP

    1641

    16.2.1.3 Generating demand matrices for Standard 4-step trip distribution


    7. Confirm with OK.
    The edited values are stored with the demand stratum
    Tip: Alternatively you can edit the production and attraction rate of demand strata by zone
    (see "Zones: DStrata tab" on page 1140).
    16.2.1.3

    Generating demand matrices for Standard 4-step trip distribution


    As long as no demand matrices have been selected for demand strata, to which the trip distribution result shall be saved for the particular demand stratum (see "Properties and options
    of demand strata" on page 1635), you can create new demand matrices and allocate these to
    the demand strata for trip distribution automatically.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Select the desired demand model.
    4. Click the Create demand matrices button.
    The Create and allocate demand matrices window opens.
    5. Make the desired changes.
    Element

    Description

    Create distribution Visum creates distribution matrices


    matrices
    Create mode
    choice matrices

    One matrix per mode


    Visum creates one matrix per mode of the demand model
    Separate matrices for demand strata
    Visum creates a separate matrix per demand stratum and mode

    Tip: Below a message is returned that informs you about how many matrices have
    been created according to your settings.
    6. Confirm with OK.
    New demand matrices are created and allocated to all objects that have not been assigned a
    demand matrix yet.

    1642

    PTVGROUP

    16.2.1.4 Calculating trip distribution


    Tips: Alternatively you may - for selected demand strata - create demand matrices via
    menu Demand> Demand models> tab Demand strata> button Create demand matrices.
    In the Demand strata tab, you can change the allocation of demand matrices to demand
    strata (see "Properties and options of demand strata" on page 1635).
    In the Mode choice matrices tab, you can change the allocations made for demand
    matrices to demand strata and mode (see "Allocating demand matrices to modes for
    mode choice" on page 1648).
    16.2.1.4

    Calculating trip distribution


    Trip distribution means the determination of a total demand matrix per demand stratum from
    available origin and destination demands of the individual zones by means of relevant skims
    (e.g. journey times, fares) (see Fundamentals: Chpt. 4.2.1.2 , page 139).
    Trip distribution is calculated with the help of the gravity model (see Fundamentals: Chpt. 4.2.5
    , page 188). You can estimate the gravity model parameters in advance (see "Estimate gravitation parameters (KALIBRI)" on page 1703).
    1. Make sure that for each zone, the production and attraction rate per demand stratum are
    available as zone attributes Productions and Attractions (see "Starting the iterative repetition" on page 1697 and "Editing the demand of Standard 4-step demand strata" on page
    1641).
    2. Each demand stratum for which you want to calculate trip distribution must be allocated to a
    demand matrix where the results are saved (see "Properties and options of demand strata"
    on page 1635 and "Generating demand matrices for Standard 4-step trip distribution" on
    page 1642).
    3. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    4. To the procedure sequence, at the position of your choice, add the procedure Trip distribution of the Demand model category (see "Setting up and starting the procedure
    sequence" on page 1847).
    5. In the row of the added procedure, click the button in the Reference object(s) column.
    The Demand strata selection window opens.
    6. In the Select demand model list, click the demand model the demand strata belong to.
    7. In the Demand stratum selection list, select the demand strata you would like to calculate
    the trip distribution for.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    8. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    PTVGROUP

    1643

    16.2.1.4 Calculating trip distribution


    9. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Demand distribution window opens.
    10. Make the desired settings.
    Element

    Description

    For active OD pairs


    only

    If this option has been checked, only those relations which are
    in the active state are considered (see "Exception: Filter for OD
    pairs" on page 1026).

    Exclude OD pairs
    If this option has been selected, only OD pairs between active
    connecting passive zones are considered (see "Using filters to set network objects
    zones
    active or passive" on page 1008 and "Setting network objects
    active/passive via the spatial selection" on page 1033).
    Set any result
    demand matrix to 0
    prior to calculation

    If this option has been selected, all demand matrices allocated


    to the demand strata are set to 0 prior to summing up the calculated OD demand.
    Note
    You should check this option if trip distribution is to be calculated for all demand strata allocated to the same demand
    matrix.

    Apply estimated
    parameters

    Select this option to use the parameters a, b, c and the function type of the demand stratum attributes.
    If you do not select this option, specify the parameters and
    the function type per demand stratum in the list of demand
    strata.

    Apply to all DStrata

    Use this button to apply the current combination of matrices and


    attribute vectors settings and the utility function set up for the
    currently selected activity to all other demand strata.

    Result demand
    matrix

    Reference to the demand matrix to which the trip distribution


    result is saved for the selected demand stratum (see "Properties
    and options of demand strata" on page 1635 and "Generating
    demand matrices for Standard 4-step trip distribution" on page
    1642).

    Function type

    Use the drop-down list to select the type of utility function you
    want to use for the calculation of the trip distribution.
    Note
    If you have selected the Apply estimated parameters option,
    the Logit option is grayed out.
    Tip
    Alternatively, you can specify the function type in the Options
    tab of the Choice model for <demand stratum> window. The

    1644

    PTVGROUP

    16.2.1.4 Calculating trip distribution


    Element

    Description

    Parameters

    a, b, c
    Estimated parameter values for the utility function modeling the
    response of travelers to distance or time conditions. The parameters can take negative values.
    Notes
    If you have selected the Apply estimated parameters option,
    the cells are grayed out.
    If the initial matrix contained impedance data such as distances
    or travel times, negative exponents need to be entered for the
    utility function.
    Tip
    Alternatively, you can specify the values in the Options tab of
    the Choice model for <demand stratum> window. The window

    window opens via the icon

    opens via the icon


    DirectionParameters

    (quick info: Other parameters).

    Use this option to select the distribution model to be calculated.


    Constrained production
    If this option has been selected, trip distribution is calculated singly constrained for production.
    The Production zone attribute is taken into account for each
    zone.
    Constrained attraction
    If this option has been selected, trip distribution is calculated singly constrained for attraction.
    The Attraction zone attribute is taken into account for each
    zone.
    Tip
    Alternatively, you can specify the values in the Options tab of
    the Choice model for <demand stratum> window. The window
    opens via the icon

    11. Click the

    (quick info: Other parameters).

    (quick info: Other parameters).

    (quick info: Other parameters) button.

    12. The Choice model for <demand stratum> window opens.


    13. Select the Options tab.
    Note: Only those items are described here that cannot be specified in the Parameters: Demand distribution window.
    14. Make the desired changes.

    PTVGROUP

    1645

    16.2.1.4 Calculating trip distribution

    Element

    Description

    Doubly consIf this option has been checked, matrix balancing by multi-protrained: Balancing cedure is calculated additionally after the first iteration (see Funby multi-prodamentals: Chpt. 4.3.12 , page 203).
    cedure
    Initial matrix balan- Via this option you select the totals to be used for multi procedure
    cing according to calculation in case of different production and attraction totals
    ...
    (see Fundamentals: Chpt. 4.3.12 , page 203).
    Sum of productions
    Multi procedure regards the production total.
    Sum of attractions
    Multi procedure regards the attraction total.
    Mean of both sums
    Multi-procedure uses the mean value calculated from production
    total and attraction total as a basis.
    Minimum of both sums
    Multi-procedure uses the smaller value of production and attraction totals as a basis.
    Maximum of both sums
    Multi-procedure uses the greater value of production and attraction totals as a basis.
    Note
    This option is only provided for doubly constrained balancing.
    Multi-Parameters

    Parameters for multi procedure calculation (see Fundamentals:


    Chpt. 4.3.12 , page 203)
    Max. number of iterations: After the user-defined number of iterations the iteration process is cancelled though convergence
    has not been reached yet.
    Quality factor: Criterion for termination of the multi-procedure
    Note
    These options are only provided for doubly constrained balancing.

    15. Select the Function graph tab.


    The Function graph tab displays the curve progression of the utility function with the
    currently set parameters a, b and c.
    16. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.

    1646

    PTVGROUP

    16.2.1.4 Calculating trip distribution


    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    17. If required, in the Parameters section, edit the parameters a, b, and c of the utility function.
    18. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    Tip: To reset the utility function parameter values and the curve progression to standard values, click the Reset button.
    19. Confirm with OK.
    20. Click the Utility function button.
    The Utility definition for demand stratum <> window opens.
    Note: The utility definition is a linear combination of matrices, attribute vectors and/or
    constants that describes the accessibility of the individual zones (see "Combining
    matrices and attribute vectors in the Matrix window" on page 1799). For each demand
    stratum, you can specify a different utility definition which serves for transformation of
    the values resulting from the combination.
    21. Make the desired changes.
    Element

    Description

    Transformation
    selection list

    From this selection list you can pick a function for transformation
    of the final result of the combination (Utility U) (see "Editing matrix
    values" on page 1761).

    Create

    Insert row in list

    Delete

    Delete marked row from list


    Use the icons to move up or down in the list of demand strata.

    1st column

    PTVGROUP

    If the list contains more than one entry, the + sign indicates that
    the entries are added row by row.

    1647

    16.2.1.5 Allocating demand matrices to modes for mode choice


    Element

    Description

    Matrix / Attribute / This button opens a window that allows you to select a Visum
    Constant
    skim matrix, zone attribute or constant. You can use a function to
    convert the values of the object selected (Transformation
    column). You can further multiply them by a factor (Coefficient
    column).
    Transformation
    column

    In the list box of the Transformation column, click the function of


    your choice to convert the values selected in the Matrix / Attribute / Constant column (see "Editing matrix values" on page
    1761).

    Coefficient

    Factor by which the values are multiplied one element at a time.

    22. Confirm with OK.


    23. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Trip distribution is calculated and its results are saved per demand stratum to the results matrix
    assigned.
    Tip: You can view and edit the result matrices (see "Managing, showing and analyzing
    matrices" on page 1715).
    16.2.1.5

    Allocating demand matrices to modes for mode choice


    For each mode, you may define to which of the demand matrices the demand stratum's trip
    demand of this mode is to be added during mode choice (see "Calculate mode choice" on
    page 1649).
    Note: This is only provided for demand strata to which no demand matrix for saving the
    trip distribution result has been allocated (see "Properties and options of demand strata"
    on page 1635 and "Generating demand matrices for Standard 4-step trip distribution" on
    page 1642).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Mode choice matrices tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the Demand matrix column, click the matrix you want to add the demand to during mode
    choice.
    5. Confirm with OK.
    The demand matrices are allocated to the modes.

    1648

    PTVGROUP

    16.2.1.6 Calculate mode choice


    Note: If for a particular mode, you select the same demand matrix for multiple demand
    strata, the individual result matrices are added up during mode choice.
    16.2.1.6

    Calculate mode choice


    Mode choice is the distribution of the total demand (total demand matrix) per demand stratum
    onto the individual traffic modes (e.g. PrT, PuT) on the basis of mode-specific skims.
    There are two types of demand strata:
    Those referring directly to a demand matrix allocated to one single demand segment or
    several demand segments
    Those whose demand matrix is not related to any demand segment
    No mode choice will be calculated for demand strata referring directly to a matrix with demand
    segment(s).
    For demand strata whose demand matrix is not related to any demand segment it is determined per mode to which demand matrix the demand calculated for that mode has to be
    added during mode choice (see Fundamentals: Chpt. 4.2.1.3 , page 139).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the procedure Mode choice
    of the Demand model category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the newly inserted procedure, in the Reference object(s) column, click the button.
    The Demand strata selection window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    5. In the Demand stratum selection list, select the demand strata you would like to calculate
    the mode choice for.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    6. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    7. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The Mode choice parameters window opens.
    8. Make the desired changes.

    PTVGROUP

    1649

    16.2.1.6 Calculate mode choice

    1650

    Element

    Description

    Set any result


    demand matrix to
    0 prior to calculation

    If this option has been selected, all demand matrices allocated to


    the demand strata are set to 0 prior to summing up the calculated
    OD demand.
    Note
    Select this option, if all pairs formed from demand stratum and
    mode which have been allocated to the same demand matrix conjointly are regarded for mode choice.

    Apply to all
    DStrata

    Via this button you can apply the combination of matrices and attribute vectors settings and the utility function selected for the
    currently selected demand stratum to all demand strata of the
    demand model.

    Key

    Unique value generated by Visum for each combination of


    Demand stratum and Mode.

    Mode

    List of all modes of the selected demand strata

    Demand stratum

    The table displays important settings for each mode of a demand


    stratum. The table enables you to directly access all demand
    strata.

    Input demand
    matrix

    Reference to the demand matrix, which - as trip distribution result


    - is distributed to the modes

    Result demand
    matrix

    Reference to the demand matrix to which the mode choice result


    is saved for the selected demand stratum and the selected mode
    (see "Allocating demand matrices to modes for mode choice" on
    page 1648)

    Function type

    From a list you can select the type of utility function used for the
    calculation of the mode choice.
    Note
    The setting applies to all modes of the demand stratum.

    Parameters

    a, b, c
    Estimated parameter values for the utility function modeling the
    response of travelers to distance or time conditions. The parameters can take negative values.
    Notes
    The settings apply to all modes of the demand stratum.
    The Function graph tab of the Choice model for <demand stratum> window shows the curve progression of the utility function
    due to current parameter settings.
    If the initial matrix contained impedance data such as distances
    or travel times, negative exponents need to be entered for the utility function.

    PTVGROUP

    16.2.1.6 Calculate mode choice


    9. Click the

    (quick info: Other parameters) button.

    The Choice model for <demand stratum> window opens. You can specify a utility function
    which serves for transformation of the values resulting from the combination.
    10. Select the Options tab.
    11. Make the desired changes.
    Element

    Description

    Function type

    Type of the utility function for the mode choice calculation

    Parameters

    a, b, c
    Estimated parameter values for the utility function modeling the
    response of travelers to distance or time conditions. The parameters can take negative values.

    12. Select the Function graph tab.


    The Function graph tab displays the curve progression of the utility function with the
    currently set parameters a, b and c.
    13. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.
    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    14. If required, in the Parameters section, edit the parameters a, b, and c of the utility function.
    15. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    Tip: To reset the utility function parameter values and the curve progression to standard values, click the Reset button.
    16. Confirm with OK.
    The Parameters: Mode choice window is displayed.

    PTVGROUP

    1651

    16.2.1.6 Calculate mode choice


    17. Click the Utility function button

    The Utility definition for demand stratum/mode <> window opens.


    Note: The utility definition is a linear combination of matrices, attribute vectors and/or
    constants per mode (see "Combining matrices and attribute vectors in the Matrix window" on page 1799). The result of the combination is interpreted as utility matrix. For
    each demand stratum, you can specify a different utility definition which serves for
    transformation of the values resulting from the combination.
    18. Make the desired changes.
    Element

    Description

    Transformation
    selection list

    From this selection list you can pick a function for transformation
    of the final result of the combination (Utility U) (see "Editing matrix
    values" on page 1761).

    Create

    Insert row in list

    Delete

    Delete marked row from list


    Use the icons to move up or down in the list of demand strata.

    1st column

    If the list contains more than one entry, the + sign indicates that
    the entries are added row by row.

    Matrix / Attribute / This button opens a window that allows you to select a Visum
    Constant
    skim matrix, zone attribute or constant. You can use a function to
    convert the values of the object selected (Transformation
    column). You can further multiply them by a factor (Coefficient
    column).
    Transformation
    column

    In the list box of the Transformation column, click the function of


    your choice to convert the values selected in the Matrix / Attribute / Constant column (see "Editing matrix values" on page
    1761).

    Coefficient

    Factor by which the values are multiplied one element at a time.

    19. Confirm with OK.


    The Parameters: Mode choice window is displayed.
    20. Confirm with OK.
    21. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Mode choice is calculated and its results are saved, per demand stratum and mode combination, to the result matrix assigned.

    1652

    PTVGROUP

    16.2.1.7 Calculating nested mode choice


    Tip: You can view and edit the result matrices (see "Managing, showing and analyzing
    matrices" on page 1715).
    16.2.1.7

    Calculating nested mode choice


    Besides single-step mode choice you can calculate a nested mode choice model. To do so,
    you need to construct a decision tree with modes as leaves and nests at the inner nodes. By
    default, Visum automatically determines the demand matrices for the nests. The utility of a nest
    always corresponds to the LogSum of the utilities of its children. You can override these temporary matrices if you wish to inspect the nest matrices or set up a non-standard sequential
    choice model (see Fundamentals: Chpt. 4.2.1.4 , page 140).

    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the procedure Nested
    mode choice of the Demand model category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Demand strata selection window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    5. In the Demand stratum selection list, select the demand strata you would like to calculate
    the nested mode choice for.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.

    PTVGROUP

    1653

    16.2.1.7 Calculating nested mode choice


    6. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Nested mode choice window opens.

    8. Make the desired changes.


    Section Decision tree

    1654

    Element

    Description

    Create nest

    Creates a new nest node in the decision tree


    Via this button, a separate window opens: Enter the name of the
    nest.
    Note
    If only leaves (modes) are created underneath the root and the
    parameters are set accordingly, a simple (multi-nominal) mode
    choice can be computed (see "Calculate mode choice" on page
    1649).

    Create mode

    Select one of the modes defined in the network and allocate it to


    the nest.
    Note
    For a nest, you can create modes only until all modes defined in
    the network have been allocated.

    PTVGROUP

    16.2.1.7 Calculating nested mode choice


    Section Decision tree
    Element

    Description

    Shift

    Select a new parent node for the marked entry and all of its children (sub-nodes).

    Delete

    Removes the marked entry from the decision tree.

    Edit name

    In a separate window, the name of the selected entry can be edited.

    Element

    Description

    Set any result


    demand matrix to
    0 prior to calculation

    If this option has been selected, all demand matrices allocated to


    the demand strata are set to 0 prior to summing up the calculated
    OD demand.
    Note
    Select this option, if all pairs formed from demand stratum and
    mode which have been allocated to the same demand matrix conjointly are regarded for mode choice.

    Demand stratum

    In the selection list, for each nest or leaf you can select the
    demand stratum to which the settings refer.

    Mode choice
    model

    Via this button you can select a utility function which serves for
    transformation of the values resulting from the combination (see
    "Setting utility function parameters for nested mode choice" on
    page 1657).

    Marked nest / Mar- Display of the nest or mode currently marked in the decision tree
    ked mode
    Input demand
    matrix

    Reference to the demand matrix, which - for the current level of


    decision - is distributed to the corresponding sub-nodes.
    Note
    The input matrix is equivalent to the parent node's result matrix.

    Result demand
    matrix

    Reference to the demand matrix, which - for the current level of


    decision - is saved by decision route tree entry.

    Matrix selection

    Via this button, you may - in a separate window - select a result


    matrix for the currently marked nest.
    Note
    This button is only provided for nests.

    Automatic utility
    scaling for subnodes

    If the LogSum coefficient of a nest is neither 1 nor 0, the coefficients of the corresponding sub-nodes (column coefficient)
    need to be scaled with the quotient 1/LogSumCoefficient.
    Via this option you can specify whether the coefficients of subnodes are to be scaled automatically or not.

    PTVGROUP

    1655

    16.2.1.7 Calculating nested mode choice


    Element

    Description
    Notes
    This option is only provided for nests.
    If the LogSumCoefficient is 0, all of the coefficients of the subnodes remain unchanged.

    Utility U

    Linear combination of matrices, attribute vectors and/or constants


    per mode or nest (see "Combining matrices and attribute vectors
    in the Matrix window" on page 1799)
    For nests, the utility function additionally includes the LogSum
    summed up from all subnodes, which can be smoothed by any
    coefficient, if a Logit function has been selected as mode choice
    model (see Fundamentals: Chpt. 4.2.1.4 , page 140).
    Note
    The result of the linear combination is interpreted as utility matrix.

    Create

    Insert row in list

    Delete

    Delete marked row from list

    1st column

    If the list contains more than one entry, the + sign indicates that
    the entries are added row by row.

    Matrix / Attribute / This button opens a window that allows you to select a Visum
    Constant
    skim matrix, zone attribute or constant. You can use a function to
    convert the values of the object selected (Transformation
    column). You can further multiply them by a factor (Coefficient
    column).
    Transformation

    In the list box, click the function of your choice to convert the
    values selected in the Matrix / Attribute / Constant column (see
    "Editing matrix values" on page 1761).

    Coefficient

    Factor by which the values are multiplied one element at a time

    Save utility matrix If this option has been selected, the calculated utility is saved as
    as
    skim matrix for future use. This matrix you can select in a selection list.
    Apply to all
    DStrata

    Via this button you can apply the combination of matrices and attribute vectors settings and the utility function selected for the
    currently selected demand stratum to all demand strata of the
    demand model.

    9. Confirm with OK.


    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Nested mode choice is calculated. The results are saved, per combination of demand stratum
    and mode, to the result matrix assigned.

    1656

    PTVGROUP

    16.2.1.7 Calculating nested mode choice


    Tip: You can view and edit the result matrices (see "Managing, showing and analyzing
    matrices" on page 1715).
    Setting utility function parameters for nested mode choice
    1. Make sure that the Parameters: Nested mode choice window is open (see "Calculating
    nested mode choice" on page 1653).
    2. Make sure that the desired demand stratum has been selected.
    3. Click the Mode choice model button.
    The Choice model for <DStratum> window opens.
    4. Select the Options tab.
    5. Make the desired changes.
    Element

    Description

    Function
    type

    Utility function type for nested mode choice calculation

    Parameters a, b, c
    Estimated parameter values for the utility function modeling the
    response of travelers to distance or time conditions. The parameters can
    take negative values.
    Notes
    The Function graph tab shows the curve progression of the utility function due to current parameter settings.
    If the initial matrix contained impedance data such as distances or travel
    times, negative exponents need to be entered for the utility function.
    6. Select the Function graph tab.
    The curve progression of the utility function is shown with the currently set parameters a, b,
    and c.
    7. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.
    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    8. If required, in the Parameters section, edit the parameters a, b, and c of the utility function.
    PTVGROUP

    1657

    16.2.1.8 Calculating Time-of-day choice

    Tip: Alternatively, you can edit the parameters in the Options tab.
    9. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    Tip: To reset the utility function parameter values and the curve progression to standard values, click the Reset button.
    10. Confirm with OK.
    The changes are applied.
    16.2.1.8

    Calculating Time-of-day choice


    The time-of- day choice is another optional choice level following the mode choice. Per
    demand segment, the total demand is distributed in the time dimension according to time interval-specific utility matrices. This results in a demand matrix with a demand time profile that you
    can immediately use in PuT assignments or in dynamic PrT assignments (see Fundamentals:
    Chpt. 4.2.1.5 , page 141).
    Note: Demand strata are not required for this procedure. Thus, you can execute it independently from other steps of the Standard 4-step model.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Time-of-day choice procedure of the Demand model category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. In the row of the newly inserted procedure, in the Reference object(s) column, click the button.
    The Select matrix window opens.
    4. In the list, click the matrix whose values you want to use for demand calculation.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the procedure inserted is marked. In the Operations section, click the Edit button.
    The Time-of-day choice parameters window opens.
    7. Make the desired changes.

    1658

    PTVGROUP

    16.2.1.8 Calculating Time-of-day choice


    Element

    Description

    Set all interval


    If this option has been selected, all values of the time intervals
    allocated to the standard time series are set to 0 prior to the calvalues to zero
    prior to calculation culation.
    If this option has not been selected, the following values are
    added to the weight of the selected time interval (see "Managing
    time series" on page 1608).
    For time series as percentages the sum of the demand
    matrices is added by time interval to the current weight of the
    time interval.
    For time series of matrix numbers the demand matrix calculated by means of the time choice model is added to the
    matrix allocated to the particular time interval.
    Time choice
    model

    Via this button you can select a utility function which serves for
    transformation of the values resulting from the combination (see
    "Setting utility function parameters for time-of-day choice" on
    page 1660).

    Selection of a stan- Via the list box, you can select a standard time series. The
    dard time series
    demand matrix selected as reference object will be distributed to
    the time intervals of the selected standard time series (see "Managing time series" on page 1608).
    For time series by percentages the interval weights (matrix
    totals) are re-calculated. For each time interval, temporary
    demand matrices are calculated by means of the time choice
    model. The matrix sum of such an demand matrix results in
    the weighting of the respective time interval.
    For time series of matrix numbers the values of the intervalspecific demand matrices are re-calculated by time interval.
    Time interval

    Via the list box, you can select the desired time interval of the standard time series (see "Creating time intervals for standard time
    series" on page 1609).

    Result demand
    matrix

    Reference to the demand matrix being allocated to the particular


    time interval of the standard time series (see "Creating time intervals for standard time series" on page 1609).
    Note
    The allocated result matrix is only displayed for time series of
    matrix numbers.

    Utility U

    Linear combination of matrices, attribute vectors and/or constants


    per time interval (see "Combining matrices and attribute vectors
    in the Matrix window" on page 1799)
    Note
    The result of the combination is interpreted as utility matrix.

    PTVGROUP

    1659

    16.2.1.8 Calculating Time-of-day choice


    Element

    Description

    Create

    Insert row in list

    Delete

    Delete marked row from list

    1st column

    If the list contains more than one entry, the + sign indicates that
    the entries are added row by row.

    Matrix / Attribute / This button opens a window that allows you to select a Visum
    Constant
    skim matrix, zone attribute or constant. You can use a function to
    convert the values of the object selected (Transformation
    column). You can further multiply them by a factor (Coefficient
    column).
    Transformation

    In the list box, click the function of your choice to convert the
    values selected in the Matrix / Attribute / Constant column (see
    "Editing matrix values" on page 1761).

    Coefficient

    Factor by which the values are multiplied one element at a time

    8. Confirm with OK.


    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The time-of-day choice is calculated and the results are saved per time interval to the result
    matrix (time series of matrix numbers) or to the Weight column of the Edit time series window
    (Time series by percentage) (see "Creating time intervals for standard time series" on page
    1609).
    Setting utility function parameters for time-of-day choice
    1. Make sure that the Time-of-day choice parameters window is open (see "Calculating
    Time-of-day choice" on page 1658).
    2. Make sure that the desired demand matrix has been selected.
    3. Click the Time choice model button.
    The Choice model for <Matrix name> window opens.
    4. Select the Options tab.
    5. Make the desired changes.

    1660

    Element

    Description

    Function
    type

    Utility function type for calculation of time-of-day choice

    Parameters

    a, b, c
    Estimated parameter values for the utility function. The parameters can
    take negative values.

    PTVGROUP

    16.2.2 Calculating demand with the EVA-P model


    Element

    Description
    Notes
    The Function graph tab shows the curve progression of the utility function due to current parameter settings.
    If the initial matrix contained impedance data such as distances or travel times, negative exponents need to be entered for the utility function.

    6. Select the Function graph tab.


    The curve progression of the utility function is shown with the currently set parameters a, b,
    and c.
    7. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.
    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    8. If required, in the Parameters section, edit the parameters a, b, and c of the utility function.
    Tip: Alternatively, you can edit the parameters in the Options tab.
    9. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    Tip: To reset the utility function parameter values and the curve progression to standard values, click the Reset button.
    10. Confirm with OK.
    The changes are applied.

    16.2.2

    Calculating demand with the EVA-P model


    Note: This functionality is only available if you have activated the EVA-P add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    The following step-by-step instruction illustrates the typical work flow for demand calculation
    with the help of the EVA-P model (see Fundamentals: Chpt. 4.2.2 , page 142).

    PTVGROUP

    1661

    16.2.2.1 Defining constraints


    1. Construct the network model (transport supply) (see "Editing the network" on page 957).
    2. Create zones (see "Creating a zone" on page 1136).
    3. Connect the zones to nodes in the network (see "Creating a connector" on page 1160).
    4. Create a demand model, activities, activity pairs, person groups, structural properties and
    demand strata and define their properties (see "Managing demand objects" on page 1606).
    5. Define constraints (see "Defining constraints" on page 1662).
    6. Enter zone attributes: population figures by person group (see "Editing the number of persons in a person group" on page 1621), the values of the structural properties (see "Editing
    structural property data" on page 1623) and the values of zone-specific procedure parameters (see "Editing non-constant constraint factors values" on page 1665 and "Editing
    values for non-constant rates and factors" on page 1668), if required.
    7. Define the exchangeable modes (see "Properties and options of modes" on page 1060).
    8. Create a procedure sequence consisting of the steps EVA trip generation, EVA weighting
    and EVA distribution/mode choice (see "Setting up and starting the procedure sequence"
    on page 1847).
    9. For each procedure, set the parameters.
    EVA trip generation (see "Calculating EVA trip generation" on page 1666)
    EVA weighting (see "Calculating EVA weighting" on page 1671)
    EVA distribution/mode choice (see "Calculating EVA trip distribution and mode
    choice" on page 1680)
    10. To the procedure sequence, add procedures for skim matrix calculation (see "Calculating:PrT skims" on page 1984 and "Calculating PuT skims" on page 2073) and, if required, for assignment and iterative repetition of the procedure sequence (see "Starting the
    iterative repetition" on page 1697).
    11. Execute the procedure sequence (see "Executing procedures in the procedure sequence"
    on page 1857).
    12. With the help of various statistical evaluations you may check the plausibility of the results
    (see "Calculating EVA trip generation" on page 1666 and "Calculating EVA trip distribution
    and mode choice" on page 1680).
    16.2.2.1

    Defining constraints
    For demand calculation by means of EVA-P demand models you have to define so-called
    constraints by demand stratum. The steps EVA trip generation and EVA distribution/mode
    choice will consider these constraints (see Fundamentals: Chpt. 4.2.2.2 , page 146).
    1. In the Demand menu, click the entry Demand models entry.
    The Demand models window opens.
    2. In the Select demand model list, click the demand model of your choice.
    3. Select the Constraints tab.
    4. Make the desired changes.

    1662

    PTVGROUP

    16.2.2.1 Defining constraints

    Element

    Description

    DStrataCode

    Short name of the demand stratum

    OD type

    OD type of the corresponding activity pair of the demand stratum


    (see "Properties and options of activity pairs" on page 1628)

    Balancing

    Via this option you select the demand strata the balancing of constraints is to be performed for.
    Note
    You can only select this option for a demand stratum with OD type
    3.

    Constraint origin Type of constraint on origin side.


    For selection, use the selection list.
    Hard
    CF OMin = CF OMax = 1. Thus, the production rate needs to be fully
    considered for trip distribution.
    Soft
    CF OMin = 0, CF OMax 1 for a constant constraint factor.
    If CF DMax is not constant, but zone-dependent, the zone attribute
    value is applied.
    Elastic
    CF OMin 0 and CF OMax 0 for constant constraint factors.
    If CF OMax or CF DMax is not constant, but zone-dependent, the
    zone attribute value is applied.
    Open
    CF OMin = 0 and CF OMax is not limited.
    Note
    The constraint type of demand strata with OD type 1 is always hard
    on the origin side.
    CF OMin constant

    If this option has been selected, the factor for the lower limit of
    the origin rate is identical for all zones (constant).
    If this option has not been selected, the factor for the lower limit
    differs by zone (from zone attribute).
    Note
    This option is only provided for the Elastic constraint type.

    CF OMin

    PTVGROUP

    Factor for the lower limit of productions.


    Note
    You can edit this factor value according to the constraint type and
    the constant factor settings (see "Editing non-constant constraint factors values" on page 1665).

    1663

    16.2.2.1 Defining constraints


    Element

    Description

    CF OMax constant

    If this option has been selected, the factor for the upper limit of
    the origin rate is identical for all zones (constant).
    If this option has not been selected, the factor for the upper limit
    differs by zone (from zone attribute).
    This option is only provided for the constraint types Weak and Elastic.

    CF OMax

    Factor for the upper limit of productions.


    Note
    You can edit this factor value according to the constraint type and
    the constant factor settings (see "Editing non-constant constraint factors values" on page 1665).

    Constraint destination

    Type of constraint on destination side.


    For selection, use the selection list.
    Hard
    CF DMin = CF DMax = 1. Thus, the attractions need to be fully considered for trip distribution.
    Soft
    CF DMin = 0, CF DMax 1 for a constant constraint factor.
    If CF DMax is not constant, but zone-dependent, the zone attribute
    value is applied.
    Elastic
    CF DMin 0 and CF DMax 0 for constant constraint factors.
    If CF DMin or CF DMax is not constant, i.e. zone-dependent, the
    zone attribute value is applied.
    Open
    CF DMin = 0 and CF DMax is not limited.
    Note
    The constraint type of demand strata with OD type 2 is always hard
    on the destination side.

    CF DMin constant

    If this option has been selected, the factor for the lower limit of
    the destination rate is identical for all zones (constant).
    If this option has not been selected, the factor for the lower limit
    differs by zone (from zone attribute).
    Note
    This option is only provided for the Elastic constraint type.

    CF DMin

    1664

    Factor for the lower limit of destination demand.


    Note
    You can edit this factor value according to the constraint type and

    PTVGROUP

    16.2.2.2 Editing non-constant constraint factors values


    Element

    Description
    the constant factor settings (see "Editing non-constant constraint factors values" on page 1665).

    CF DMax is conIf this option has been selected, the factor for the upper limit of
    stant
    the destination rate is identical for all zones (constant).
    If this option has not been selected, the factor for the upper limit
    differs by zone (from zone attribute).
    This option is only provided for the constraint types Weak and Elastic.
    CF DMax

    Factor for the upper limit of the attractions.


    Note
    You can edit this factor value according to the constraint type and
    the constant factor settings (see "Editing non-constant constraint factors values" on page 1665).

    Quantity as
    potential

    If the option is selected, productions or attractions also define the


    structural potential (attractiveness) of the zone for the demand stratum on the respective side if constraints are not defined as hard
    constraints.
    If the option is not selected, the production and/or attraction constraints need to be kept during trip distribution but attractiveness is
    zero. Instead, all zones have the same structural potential.
    Note
    This option is relevant only if hard constraints have been set for just
    one side - either for productions or for attractions.

    5. Confirm with OK.


    The constraints are stored for the demand strata of the selected demand model.
    16.2.2.2

    Editing non-constant constraint factors values


    If a factor for the lower or upper production or attraction limit is not a constant value, i.e. a specific value count for each zone, then you need to define - for all zones and for all demand
    strata - its values with constraint type Weak or Elastic (see "Defining constraints" on page
    1662) in the zone list (see "Editing the properties of objects in lists" on page 2321).
    Tip: If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. Open the Zones list (see "Opening a list" on page 2299).
    2. From the selection list, select the pre-defined list layout EVA constraints.
    For each demand stratum, columns with the corresponding factors are listed.

    PTVGROUP

    1665

    16.2.2.3 Calculating EVA trip generation


    3. Edit the factor values for the desired zones and demand strata (see "Editing the properties
    of objects in lists" on page 2321).
    Note: The values from the zone list are not taken into account for constant factors.
    16.2.2.3

    Calculating EVA trip generation


    Similarly to the trip generation of the Standard 4-step model (see "Calculating trip generation"
    on page 1638), the EVA trip generation calculates the production and attraction of each zone
    per demand stratum. Additionally, the model determines the home trips of each zone per
    demand stratum. On this basis, the productions and attractions are standardized. For demand
    strata of OD type 1, the productions are equal to the home trips, for those of OD type 2, the
    attractions are equal to the home trips. Those cases do not require separate parameters for
    the calculation of the productions and attractions (see Fundamentals: Chpt. 4.2.2.2 , page
    146).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the procedure EVA trip
    generation of the Demand model category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. In the row of the newly inserted procedure, in the Reference object(s) column, click the button.
    The Demand strata selection window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    5. In the Demand stratum selection list, select the demand strata you would like to calculate
    the EVA Trip distribution for.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    6. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    7. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The Parameters: EVA trip generation window opens.
    8. Make the desired changes.

    1666

    PTVGROUP

    16.2.2.3 Calculating EVA trip generation


    Element

    Description

    For active zones


    only

    If this option has been selected, EVA trip generation is performed


    for active zones only (see "Using filters to set network objects
    active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page 1033).

    Set all result attri- If this option has been selected, all output attribute values are set
    bute values to 0
    to zero prior to the calculation.
    prior to calculation
    Execute balancing If this option has been selected, balancing is performed at the
    end of the EVA trip generation run (see Fundamentals: Chpt.
    4.2.2.2 , page 146).
    Notes
    This option is only available if you have selected balancing for a
    demand stratum.
    You can define the demand stratum (OD type 3) for which to compute balancing via the Constraints tab in the Demand > Demand
    models > menu (see "Defining constraints" on page 1662).
    If the constraints are weak, elastic or open for at least one
    demand stratum on origin or destination side, balancing cannot
    be calculated at the end of the EVA trip generation. The same
    applies if there is at least one mode that cannot be exchanged in
    the demand model. However, balancing can be calculated at the
    end of the EVA trip distribution and mode choice operation (see
    "Calculating EVA trip distribution and mode choice" on page
    1680).
    Key

    Unique value generated by Visum for each combination of


    Demand stratum, Kind of trip and Person group / Structural
    property.

    Demand stratum

    List of all demand strata selected for the procedure. One row per
    key.

    Type (origin destination type)

    Display of the direction of the activity pair with regard to the


    HOME activity (see Fundamentals: Chpt. 4.2.2.2 , page 146), (see
    "Properties and options of activities" on page 1625)

    Kind of trip

    Kind of trip of the respective combination of demand stratum and


    person group / structural property

    Person group /
    Structural property

    Person group / Structural property of the demand stratum

    Rate constant

    If this option has been checked, the mobility rate of the person
    group is constant for the demand stratum, i.e. it is the same for all
    zones.

    PTVGROUP

    1667

    16.2.2.4 Editing values for non-constant rates and factors


    Element

    Description
    If the option is not selected, a specific value (from zone attribute) is regarded for each zone.

    Rate

    If you select the Rate constant option for a person group, you
    can enter a value 0 for the specific demand of this group.

    SA factor constant

    If this option is selected, the value of the intrazonal demand is


    constant for the attraction rate, i.e. it is the same for all zones.
    If the option is not selected, a specific value (from zone attribute) is regarded for each zone.
    Note
    SA = study area

    Study area share

    If you select the SA factor constant option, you can enter a value
    0 for the intrazonal share for the mobility rate or for the attraction
    rate.

    9. Confirm with OK.


    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    EVA Trip generation is calculated and its results are saved per demand stratum to the zone
    attributes Productions and Attractions (see "Editing the demand of EVA-P demand strata" on
    page 1669).
    Tips: You can display the results in zone lists (see "Viewing the demand of EVA-P
    demand strata in lists" on page 1670) or in the network graphics (see "Displaying data
    graphically and in lists" on page 2299). If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create
    some list layout files when a zone list is opened. Using these files, you can quickly view
    the most important demand data.
    Furthermore, you can use an add-in to generate a statistical overview of all results in
    tabular form (see "Running script files" on page 2664). The values gained for number of
    persons, structural properties, mobility and production rates as well as the demand calculated on this basis you can check for plausibility this way. You can find the add-in EVA
    analysis provided with the program under Scripts> Script menu> VisumAddIn>
    Demand.
    16.2.2.4

    1668

    Editing values for non-constant rates and factors


    In case of rates (mobility rate, production rate, attraction rate) or factors (study area factor
    HOME or production or attraction) that are not identical for all zones, in the zone list, you must
    define or change specific values for all zones, demand strata and person groups (mobility rate
    and SAfactor HOME) or for all structural properties (production rate and attraction rate as well

    PTVGROUP

    16.2.2.5 Editing the demand of EVA-P demand strata


    as SAfactor production and attraction) (see "Editing the properties of objects in lists" on page
    2321).
    Tip: If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. Open the Zones list (see "Opening a list" on page 2299).
    2. From the selection list, select the pre-defined list layout EVA production rates or EVA
    study area factors.
    For each demand stratum and person group or structural property, columns with the corresponding rates or factors are listed.
    3. Edit the rate or factor data for the desired zones, demand strata and person groups or structural properties (see "Editing the properties of objects in lists" on page 2321).
    Note: The values from the zone list are not regarded for constant rates or factors.
    16.2.2.5

    Editing the demand of EVA-P demand strata


    You can edit the production and attraction values calculated by means of EVA trip generation
    and further data by demand stratum (see "Calculating EVA trip generation" on page 1666).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Demand strata tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the demand stratum whose production and attraction rate values you
    would like to edit.
    5. Click the Productions/Attractions button.
    The Define productions/attractions window opens.
    6. Make the desired changes.
    Element

    Description

    Production

    Number of trips starting from the given zone by demand stratum


    EVA trip generation calculates this value. If no hard constraints have
    been defined, it can also be calculated by EVA distribution/mode
    choice (see "Calculating EVA trip generation" on page 1666 and
    "Calculating EVA trip distribution and mode choice" on page 1680).

    Attraction

    Number of trips heading to the given zone by demand stratum


    EVA trip generation calculates this value. If no hard constraints have
    been defined, it can also be calculated by EVA distribution/mode

    PTVGROUP

    1669

    16.2.2.6 Viewing the demand of EVA-P demand strata in lists


    Element

    Description
    choice (see "Calculating EVA trip generation" on page 1666 and
    "Calculating EVA trip distribution and mode choice" on page 1680).

    Home trips

    Number of trips by demand stratum, starting from the particular zone


    and ending there
    The value is calculated in the EVA trip generation step (see "Calculating EVA trip generation" on page 1666).

    Productions tar- Number of trips by demand stratum starting from the particular zone,
    get
    the value is calculated in the EVA trip generation step before constraints are regarded (see "Calculating EVA trip generation" on page
    1666 and "Defining constraints" on page 1662).
    Attractions tar- Number of trips by demand stratum heading to the particular zone,
    get
    the value is calculated in the EVA trip generation step before constraints are regarded (see "Calculating EVA trip generation" on page
    1666 and "Defining constraints" on page 1662).
    Balance factor
    productions

    Factor which is calculated optionally when solving the trilinear equation system during EVA distribution/mode choice for the production
    side (see Fundamentals: Chpt. 4.2.2.3 , page 165)(see "Calculating
    EVA trip distribution and mode choice" on page 1680).

    Balance factor
    attractions

    Factor which is calculated optionally when solving the trilinear equation system during EVA distribution/mode choice for the attraction
    side (see Fundamentals: Chpt. 4.2.2.3 , page 165)(see "Calculating
    EVA trip distribution and mode choice" on page 1680).

    7. Confirm with OK.


    The edited values are stored with the demand stratum
    Tips: Alternatively, you can edit production and attraction rates of demand strata by zone
    (see "Zones: DStrata tab" on page 1140), or via menu Demand> Demand models> tab
    Constraints> button Productions/attractions or in displayed lists (see "Viewing the
    demand of EVA-P demand strata in lists" on page 1670).
    16.2.2.6

    Viewing the demand of EVA-P demand strata in lists


    In a zone list you can view and edit the values of production, attraction and HOME rates and
    other data for all zones and all demand strata (see "Adjusting the list layout" on page 2308
    and "Editing the properties of objects in lists" on page 2321).
    Tip: If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. From the selection list, select the pre-defined list layout EVA trip generation output.
    For each demand stratum, a column with the corresponding demand is displayed.

    1670

    PTVGROUP

    16.2.2.7 Calculating EVA weighting


    2. If applicable, edit the values of production, attraction and HOME rates for desired zones
    and demand strata (see "Editing the properties of objects in lists" on page 2321).
    16.2.2.7

    Calculating EVA weighting


    Prior to distributing the zones productions and attractions calculated in the EVA trip generation, the relations need to be weighted. For weighting, assessment types have to be defined.
    Assessment types are shares of the total costs of a trip, for example journey time, egress/access time, monetary costs, number of PuT transfers etc.
    During EVA weighting, skim matrices are transformed per mode, per demand stratum and per
    assessment type by means of an evaluation function and multiplied subsequently. Exception:
    For the assessment type journey time, the transformed walking time (competing walking time)
    multiplied by a factor is subtracted from the result of the transformation. The results are aggregated per demand stratum in an overall weighting matrix (see Fundamentals: Chpt. 4.2.2.3 ,
    page 165).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the procedure EVA weighting of the Demand model category (see "Setting up and starting the procedure sequence"
    on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Demand strata selection window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    5. In the Demand stratum selection list, select the demand strata you would like to calculate
    the EVA weighting operation for.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    6. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: EVA weighting window opens.
    8. Make the desired changes.

    PTVGROUP

    1671

    16.2.2.7 Calculating EVA weighting


    Element

    Description

    For active OD
    pairs only

    If this option has been selected, EVA weighting is performed for


    active OD pairs only (see "Exception: Filter for OD pairs" on page
    1026).

    Exclude OD pairs
    connecting passive zones

    If this option has been selected, only OD pairs with at least one
    active zone are regarded.

    Prior to the calculation, set all


    output weighting
    matrices to 0

    If this option has been selected, the matrix data of output weighting matrices are set to zero prior to the calculation.

    Consider home
    zone for demand
    strata of type 3

    If this option has been selected, the home zone of the traveler
    is regarded as potential for demand strata of OD type 3.
    If this option has not been selected, the home zone is ignored.

    Save weight matri- Select this option to automatically save the weighting matrices calces to file
    culated through the procedures to the version file.
    Note
    By default, the option is not selected. For version files of previous
    program versions, this option is automatically deactivated.
    Maximum number
    of OD pairs with
    negative weighting
    in log file

    This value specifies the detail level of the data written to the log
    file. If the number of OD pairs with a negative weighting is less
    than the value specified, the OD pairs are listed individually. If it is
    higher, the OD pairs are summarized.
    Note
    For this list output, select the log file output option (see "Specifying settings for protocol files" on page 876).

    Apply to all
    DStrata

    Use this button to apply the settings of the currently selected


    demand stratum to all demand strata with identical combinations
    of mode and assessment type.

    9. Click the Define assessment types... button.


    The Define assessment types window opens.
    10. Make the desired changes.

    1672

    Element

    Description

    Assessment
    type

    List of all defined assessment types

    Relevant
    modes

    Via this button, you can - by assessment type - select another mode or
    other modes in a separate window.
    Note

    PTVGROUP

    16.2.2.7 Calculating EVA weighting


    Element

    Description
    The fields of assessment types Competing walk time and External
    weighting matrix can be left blank. For Journey time, all modes are
    always selected.

    Create

    Use this button to create a new assessment type. You can enter a
    name for it in a separate window.
    Tip
    You can change the name of a user-defined assessment type by overwriting it in the respective column.

    Delete

    Deletes the selected assessment type


    Note
    The assessment types Competing walk time, External weighting
    matrix and Journey time are predefined. You cannot delete them.

    11. Confirm with OK


    The assessment type is set.
    12. Make further changes in the Parameters: EVA weighting window.
    Element

    Description

    Key

    Unique value generated by Visum for each combination of Mode,


    Assessment type and Demand stratum.

    Demand stratum

    Shows the demand stratum for which you are specifying the parameters. One row per key.

    Type (origin destination type)

    Direction of the corresponding activity pair (see "Properties and


    options of activity pairs" on page 1628)

    Mode

    Shows the mode for which the evaluation is calculated.

    Mode availability

    Via this button you can select the numerical zone attribute, that
    indicates the availability of the selected mode in the particular
    zone.
    The OD type of the corresponding activity pair controls whether
    the attribute effects the origin side and/or the destination side
    (see "Properties and options of activity pairs" on page 1628).
    Type 1 for origin side
    Type 2 for destination side
    Type 3 for home trips
    Tip
    The attribute value should lie between 0 and 1. Thereby 0 means
    "not available" and 1 means "100% available".

    Capacity uti-

    Via this button you can select the numerical zone attribute, that

    PTVGROUP

    1673

    16.2.2.7 Calculating EVA weighting


    Element

    Description

    lization

    indicates the maximum share a structural property may be utilized. Example: For the activity pair Home-Shopping you may
    define to which extent the available retail sales area on the destination side may be utilized.
    The OD type of the corresponding activity pair controls whether
    the attribute effects the origin side and/or the destination side
    (see "Properties and options of activity pairs" on page 1628).
    Type 1 for destination side
    Type 2 for origin side
    Type 3 for both sides
    Tip
    The attribute value should lie between 0 and 1. Thereby 0 means
    "no capacity utilization" and 1 means "100% capacity utilization".

    Assessment type Display of the assessment type the weighting is calculated for.
    The assessment types are selected via the Define assessment
    types button.
    Gen. Costs

    Activate this option to specify generalized costs in the


    SkimMat / ZoneAttr / LinComb. column.
    If this option is not activated, in the SkimMat / ZoneAttr /
    LinComb. column, select a Visum skim matrix, a zone attribute or
    a constant.

    1674

    SkimMat /
    ZoneAttr /
    LinComb

    Click this button to specify the values used for cost calculation.
    If Gen. Costs option is not selected, a window will be opened
    by pressing the button. You can select a Visum skim matrix, a
    zone attribute or a constant.
    If the Gen. Costs option is selected, pressing the button
    opens a window. Here you can specify a linear combination
    of Visum skim matrices, attribute vectors and/or constants
    (see "Combining matrices and attribute vectors in the Matrix
    window" on page 1799).

    Functionality

    In the list box, click the weighting function type for transformation
    (see Fundamentals: Chpt. 4.2.2.3 , page 165).

    a, b, c

    You can edit the parameters of the weighting function in the cells
    (see Fundamentals: Chpt. 4.2.2.3 , page 165).
    Note
    If you select No transformation as the function, these parameters
    are grayed out.
    Tip
    Alternatively, you can edit the parameters under Graph (see "Viewing and editing the curve progression of the weighting function"

    PTVGROUP

    16.2.2.7 Calculating EVA weighting


    Element

    Description
    on page 1675).

    Max. imp.

    Threshold for impedance


    Notes
    If the impedance exceeds the threshold for an assessment type,
    the overall weighting is set to 0.
    Blank entry permitted (no upper limit for the impedance).

    PKF

    Factor for the competing walking time (see Fundamentals: Chpt.


    4.2.2.3 , page 165)
    Note
    The factor is regarded for the assessment type Journey time.

    Graph

    View the curve progression of the weighting function in a separate window and edit it, if necessary (see "Viewing and editing the
    curve progression of the weighting function" on page 1675)

    Comparison

    Show the curve progression of the weighting function for each


    mode simultaneously in separate windows. If required, select a
    mode to edit it (see "Viewing and editing the curve progression of
    the weighting function for all modes" on page 1676).

    13. Confirm with OK.


    14. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    EVA weighting is calculated. The calculation results are saved per demand stratum to the
    weighting matrix (see "Managing weighting matrices" on page 1677).
    Tip: You can show and edit the weighting matrices (see "Managing, showing and analyzing matrices" on page 1715)
    Viewing and editing the curve progression of the weighting function
    1. Make sure that the Parameters: EVA weighting window is open (see "Calculating EVA
    weighting" on page 1671).
    2. For the desired demand stratum, click the corresponding Graph button.
    The Function graph window opens and the curve progression of the utility function is
    shown with the currently set parameters a, b, and c.
    3. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.

    PTVGROUP

    1675

    16.2.2.7 Calculating EVA weighting


    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    4. Edit the weighting function parameters a, b, and c in the Parameters section, if applicable.
    Tip: Alternatively, you can change the parameters directly in the table of the Parameters: EVA weighting window.
    5. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    6. Confirm with OK.
    Viewing and editing the curve progression of the weighting function for all modes
    1. Make sure that the Parameters: EVA weighting window is open (see "Calculating EVA
    weighting" on page 1671).
    2. For the desired demand stratum, click the respective Comparison button in the All modes
    column.
    The Function graph window opens; for each mode, the curve progression and the weighting function with current a, b, and c parameter settings are displayed.
    3. In the color legend to the right, click the color of the particular mode.
    The curve of this mode is highlighted for processing.
    4. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.
    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    5. Edit the weighting function parameters a, b, and c in the Parameters section, if applicable.

    1676

    PTVGROUP

    16.2.2.8 Managing weighting matrices


    Tip: Alternatively, you can change the parameters directly in the table of the Parameters: EVA weighting window.
    6. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    7. Confirm with OK.
    16.2.2.8

    Managing weighting matrices


    Weighting matrices are specific matrices resulting from the EVA weighting step. They are created and saved per demand stratum (see "Calculating EVA weighting" on page 1671).
    For each demand stratum, weighting matrices contain the number of trips from zone i to zone j
    per mode, i.e. they are three-dimensional.
    Weighting matrices consist of individual skim matrices of a demand stratum. Visum generates
    the skim matrices per mode when the demand stratum is created (see "Creating a demand
    stratum" on page 1633). You can edit weighting matrices similarly to the way you edit demand
    matrices or skim matrices (see "Managing, showing and analyzing matrices" on page 1715).
    Note: Weighting matrices are not saved with demand data files *.dmd.
    Saving a weighting matrix in Visum
    You can save the weighting matrix calculated by demand stratum as weighting matrix file
    *.wmt.
    1. In the File menu, point at the Save as entry.
    2. Then click EVA weighting matrix.
    The Save EVA weighting matrix window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The Demand strata selection window opens.
    5. Select the demand stratum, you want to save the weighting matrix for.
    6. Confirm with OK.
    The weighting matrix is saved to file.
    Reading a weighting matrix in Visum
    1. Click the

    Open icon.

    The Select file type window opens.


    Tip: To open the window, you can also click menu File > Open > EVA weighting
    matrix.
    PTVGROUP

    1677

    16.2.2.8 Managing weighting matrices


    2. Then click EVA weighting matrix.
    3. Confirm with OK.
    The Open EVA weighting matrix window opens.
    4. Select the desired file.
    5. Click the Open button.
    The Demand strata selection window opens.
    6. Confirm with OK.
    The weighting matrix is read from file.
    Editing a weighting matrix
    1. In the Demand menu, select the EVA weighting matrices entry.
    The EVA weighting matrices window opens.
    2. In the Select demand model selection list, select the demand model the weighting matrices
    belong to.
    All demand strata of the selected demand model are listed. To each demand stratum a
    weighting matrix corresponds.
    3. In the list, select the weighting matrix you want to edit.
    4. Click the Edit button.
    For each mode, a Matrix editor window is opened that contains the mode-specific skim
    matrix of the demand stratum selected.
    Tip: Alternatively you can open each of the mode-specific skim matrices directly in the
    matrix editor (see "Opening matrices" on page 1721).
    5. Make the desired changes by mode (see "Managing, showing and analyzing matrices" on
    page 1715).
    Tip: On the Window toolbar, in the list box, you can switch between the individual Matrix
    editor windows (see "Toggling between windows" on page 828).
    Setting weighting matrix data to zero
    1. In the Demand menu, select the EVA weighting matrices entry.
    The EVA weighting matrices window opens.
    2. In the Select demand model selection list, select the demand model the weighting matrices
    belong to.
    All demand strata of the selected demand model are listed. To each demand stratum a
    weighting matrix corresponds.

    1678

    PTVGROUP

    16.2.2.9 Creating demand matrices for EVA trip distribution


    3. In the list, mark the weighting matrices you would like to edit by replacing all matrix data by
    0 irrevocably.
    4. Click the Initialize button.
    A query opens.
    5. Confirm the query with Yes.
    The matrix values are irrevocably set to 0.
    16.2.2.9

    Creating demand matrices for EVA trip distribution


    You can create new demand matrices and automatically allocate them to the demand strata
    before calculating EVA trip distribution and mode choice, if no demand matrices have been
    selected yet for the demand strata, to which the demand stratum-specific result of EVA trip distribution and mode choice is to be saved (see "Properties and options of demand strata" on
    page 1635).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Select the desired demand model.
    4. Click the Create demand matrices button.
    The Create and allocate demand matrices window opens.
    5. Make the desired changes.
    Element

    Description

    Create mode
    choice matrices

    One matrix per mode


    Visum creates one matrix per mode of the demand model.
    Separate matrices for demand strata
    Visum creates a separate matrix per demand stratum and mode.

    Tip: Below a message is returned that informs you about how many matrices have
    been created according to your settings.
    6. Confirm with OK.
    New demand matrices are created and allocated to all objects that have not been assigned a
    demand matrix yet.

    PTVGROUP

    1679

    16.2.2.10 Allocating demand matrices to modes for EVA mode choice


    Tips: Alternatively you may - for selected demand strata - create demand matrices via
    menu Demand> Demand models> tab Demand strata> button Create demand matrices.
    In the Mode choice matrices tab, you can change the allocations made for demand
    matrices (see "Allocating demand matrices to modes for EVA mode choice" on page
    1680).
    16.2.2.10 Allocating demand matrices to modes for EVA mode choice
    For each mode you can define to which of the demand matrices the demand stratum's demand
    applying to this mode shall be added during EVA mode choice (see "Calculating EVA trip distribution and mode choice" on page 1680).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Mode choice matrices tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the desired row, click the button in the Demand matrix column.
    The Select matrix window opens.
    5. Select the matrix you want to add the respective demand to during mode choice.
    6. Confirm with OK.
    The demand matrix is allocated to the mode.
    7. In the same way, select the matrix of your choice for all person groups and modes.
    Note: If for a certain mode you select the same demand matrix for several demand strata,
    the individual result matrices are added up during EVA mode choice.
    16.2.2.11 Calculating EVA trip distribution and mode choice
    In the procedure EVA trip distribution and mode choice, Visum calculates demand matrices on
    the basis of each zone's production and attraction determined in the trip generation step.
    Those matrices contain the number of trips between two zones each by demand stratum and
    mode. In contrast to the Standard 4-step model, the calculation of trip distribution and mode
    choice is performed simultaneously in an interlinked procedure. Two different iteration algorithms are provided for the approximate calculation (see Fundamentals: Chpt. 4.2.2.3 , page
    165).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the EVA distribution/mode
    choice procedure of the Demand model category (see "Setting up and starting the procedure sequence" on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.

    1680

    PTVGROUP

    16.2.2.11 Calculating EVA trip distribution and mode choice


    The Demand strata selection window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    5. In the Demand stratum list, click the demand strata for which you want to calculate EVA trip
    distribution and mode choice.
    Tip: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    6. Confirm with OK.
    The demand strata selected are listed in the DStrata input field and in the Reference
    object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters EVA distribution/mode choice window opens.
    8. Select the General parameters tab.
    9. Make the desired changes.
    Element

    Description

    Project type

    Via this option, you decide how to handle the mode shares
    Analysis
    You use the analysis to calculate the balance factors for mode
    choice.
    Select this option to enter the global mode shares of the total
    demand in the Modal split tab.
    Forecast
    Select this option to use the existing balance factors for mode
    choice as a basis for calculation (see Fundamentals: Chpt.
    4.2.2.3 , page 165).

    Execute balancing If this option has been checked, balancing is performed at the
    end of EVA Distribution and Mode choice (see Fundamentals:
    Chpt. 4.2.2.3 , page 165).
    Notes
    This option is only available if you have selected balancing for a
    demand stratum.
    You can define the demand stratum (OD type 3) for which to compute balancing via the Constraints tab in the Demand > Demand
    models > menu (see "Defining constraints" on page 1662).
    If balancing has already been calculated at the end of the EVA
    Trip generation step, it is not calculated anew at this point (see

    PTVGROUP

    1681

    16.2.2.11 Calculating EVA trip distribution and mode choice


    Element

    Description
    "Calculating EVA trip generation" on page 1666).

    Maximum number Number of iterations as a termination criterion, if the procedure


    of iterations
    cannot reach convergence with the selected iteration algorithm.
    Tolerance for hard Factor of precision for hard constraints (see Fundamentals: Chpt.
    constraints
    4.2.2.2 , page 146)
    Tolerance for non- Factor of precision for non-hard constraints (i.e. Soft, Elastic or
    hard constraints
    Open) (see Fundamentals: Chpt. 4.2.2.2 , page 146)
    Use saved
    Note
    balance factors as This option is available after you select the project type Analysis.
    initial solution
    Select this option to include the existing balance factors for productions, attractions and mode choice in the calculation (see
    "Editing the demand of EVA-P demand strata" on page 1669 and
    "Allocating demand matrices to modes for EVA mode choice" on
    page 1680).
    If you do not select this option, the balance factors will not be
    taken into account for calculation.
    Use saved
    balance factors
    for productions
    and attractions as
    initial solution

    Note
    This option is available after you select the project type Forecast.
    Select this option to include the existing balance factors for productions, attractions and mode choice in the calculation (see
    "Editing the demand of EVA-P demand strata" on page 1669 and
    "Allocating demand matrices to modes for EVA mode choice" on
    page 1680).
    If you do not select this option, only the balance factors for
    mode choice will be taken into account for calculation.

    Store calculated
    balance factors
    for productions
    and attractions

    Select this option to save the balance factors for productions


    and attractions (see Fundamentals: Chpt. 4.2.2.3 , page 165).
    If you do not select this option, the balance factors for productions and attractions are not saved.
    Note
    The balance factors for mode choice are always saved during
    analysis, but not during the forecast!

    10. Select the Procedure tab.


    11. Make the desired changes.

    1682

    PTVGROUP

    16.2.3 Demand calculation with the tour-based model (VISEM)


    Element

    Description

    Procedure Via this selection list, you may - for each demand stratum - select the iterative procedure for solving the trilinear equation system (see Fundamentals: Chpt. 4.2.2.3 , page 165).
    Fixing

    For acceleration of the multi procedure convergence you may fix either
    productions or attractions - thus, these remain constant during the iterative procedure.
    From the selection list, select the type of fixing.
    Note
    This option is only provided for the Multi procedure.

    Tip: You can adopt the entries made in one row for all other rows. To do so, right-click
    the row of your choice and select Use all attributes for all demand strata.
    12. Select the Modal split tab.
    Note: The Modal split tab is only provided, if - in the General parameters tab -option
    Analysis has been selected for project type.
    13. For each mode, specify the mode's share of the total demand of the demand stratum.
    14. If applicable, click the Standardize rows button.
    Per demand stratum, all shares are standardized this way, that their sum = 1.
    15. Confirm with OK.
    16. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    EVA distribution and mode choice are calculated and their results are saved per demand stratum and mode to separate demand matrices (see "Allocating demand matrices to modes for
    EVA mode choice" on page 1680).
    Tips: You can show and edit the demand matrices (see "Editing matrix values" on page
    1761).
    For plausibilization of results we recommend to create a trip length distribution by classification of demand matrices with the help of a skim matrix coding the distance (see
    "Showing matrices in a histogram" on page 1752).

    16.2.3

    Demand calculation with the tour-based model (VISEM)


    Note: This function is only available if you have activated the Tour-based demand model
    add-on (see "Enabling or disabling installed add-ons" on page 886).

    PTVGROUP

    1683

    16.2.3.1 Calculating Tour-based model - Trip generation


    The following step-by-step instruction illustrates the typical work flow for demand calculation
    with the help of the Tour-based model (see Fundamentals: Chpt. 4.2.3 , page 174).
    1. Construct the network model (transport supply) (see "Editing the network" on page 957).
    2. Create zones (see "Creating a zone" on page 1136).
    3. Connect the zones to nodes in the network (see "Creating a connector" on page 1160).
    4. Create a demand model, activities, activity pairs, activity chains, person groups, structural
    properties and demand strata and define their properties (see "Managing demand objects"
    on page 1606).
    5. Enter zone attributes: population figures by person group (see "Editing the number of persons in a person group" on page 1621), the values of the strucutral properties (see "Editing
    structural property data" on page 1623) and the values of zone-specific procedure parameters (see "Editing values for non-constant mobility rates and study area shares" on page
    1686), if required.
    6. Define the exchangeable modes (see "Properties and options of modes" on page 1060).
    7. Specify a procedure sequence consisting of the following steps: Tour-based model - Trip
    generation and Tour-based model - Combined trip distribution / mode choice (see "Setting up and starting the procedure sequence" on page 1847).
    8. For each procedure, set the parameters.
    9. To the procedure sequence, add procedures for skim matrix calculation (see "Calculating:PrT skims" on page 1984 and "Calculating PuT skims" on page 2073) and, if required, for assignment and iterative repetition of the procedure sequence (see "Starting the
    iterative repetition" on page 1697).
    10. Start the procedure sequence (see "Executing procedures in the procedure sequence" on
    page 1857).
    The demand is calculated using the tour-based model.
    16.2.3.1

    Calculating Tour-based model - Trip generation


    Similarly to the EVA trip generation method in the EVA model for passenger demand (see "Calculating EVA trip generation" on page 1666), the Tour-based model - Trip generation method
    calculates the number of home trips by demand stratum for each zone (see Fundamentals:
    Chpt. 4.2.3.2 , page 176).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the procedure Tour-based
    model - Trip generation of the Demand model category (see "Setting up and starting the
    procedure sequence" on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Demand strata selection Tour-based model window opens.
    4. In the Select demand model list, click the demand model the demand strata belong to.
    1684

    PTVGROUP

    16.2.3.1 Calculating Tour-based model - Trip generation


    5. In the Demand strata selection list, select the demand strata you would like to calculate the
    Tour-based model - Trip generation for.
    Tips: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    Alternatively, you may pre- select corresponding demand strata for certain person
    groups and activity pairs. Therefore, select the desired demand objects in the Person
    groups and Activity pairs selection lists and click the Accept pre-selection button.
    6. Confirm with OK.
    The demand strata selected are listed in the Reference object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Tour-based model - Trip generation window opens.
    8. Make the desired changes.
    Element

    Description

    For active zones


    only

    If this option has been checked, Tour-based model - Trip generation is calculated only for active zones (see "Using filters to set
    network objects active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page
    1033).

    Sum up values

    If this option has been checked, the output attribute values are
    added to the given values.

    Section Home trips


    Element

    Description

    Mobility rate constant

    If this option has been checked, the mobility rate of the person
    group is constant for the demand stratum, i.e. it is the same for all
    zones.
    If the option is not selected, a specific value (from zone attribute) is considered for each zone (see "Editing values for nonconstant mobility rates and study area shares" on page 1686).

    Mobility rate

    If you select the Mobility rate constant option for a person group,
    you can enter a value 0 for the specific demand of this group.

    SA factor home
    constant

    If this option is checked, the value of the intrazonal demand is


    constant for the mobility rate, i.e. it is the same for all zones.
    If the option is not selected, a specific value (from zone attribute) is considered for each zone (see "Editing values for nonconstant mobility rates and study area shares" on page 1686).

    PTVGROUP

    1685

    16.2.3.2 Editing values for non-constant mobility rates and study area shares
    Section Home trips
    Element

    Description
    Note
    SA = study area

    SA factor home

    If you select the SA factor home constant option for a person


    group, you can enter a value 0 as mobility rate for the specific
    HOME demand.

    9. Confirm with OK.


    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Tour-based model - trip generation is calculated. The calculation results are saved per
    demand stratum to the zone attribute Home trips (see "Editing the demand of tour-based
    demand strata" on page 1687).
    Tip: You can display the results in zone lists (see "Viewing the demand of Tour-based
    model demand strata in lists" on page 1687) or in the network graphics (see "Displaying
    data graphically and in lists" on page 2299).
    16.2.3.2

    Editing values for non-constant mobility rates and study area shares
    If a mobility rate value or a study area factor for Home is not constant (i.e. each zone has its
    own value), you need to specify or edit its values for all zones and demand strata in the Zones
    list(see "Editing the properties of objects in lists" on page 2321).
    Tip: If you make the appropriate setting before opening a zone list (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. Open the Zones list (see "Opening a list" on page 2299).
    2. From the selection list, select the pre-defined list layout Tour-based model - Generation
    rates or Tour-based model - Analysis area shares.
    For each demand stratum, columns with the mobility rate or the study area share HOME are
    listed.
    3. Edit the mobility rate values or the study area factors HOME for the desired zones and
    demand strata (see "Editing the properties of objects in lists" on page 2321).
    Note: For constant mobility rates or SAfactors, the values from the zone list are not regarded.

    1686

    PTVGROUP

    16.2.3.3 Editing the demand of tour-based demand strata


    16.2.3.3

    Editing the demand of tour-based demand strata


    You may edit the HOME trips by demand stratum values which are calculation results of the
    Tour-based model - Trip generation step (see "Calculating Tour-based model - Trip generation" on page 1684).
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Demand strata tab.
    3. In the Select demand model list, click the demand model of your choice.
    4. In the list, select the demand stratum whose HOME trips value you would like to edit.
    5. Click the HOME trips button.
    The Set number of home trips window opens.
    6. Make the desired changes.
    Element

    Description

    Home trips

    Number of trips by demand stratum, starting from the particular


    zone and ending there
    The value is calculated in the Tour-based model - Trip generation
    step (see "Calculating Tour-based model - Trip generation" on
    page 1684).

    7. Confirm with OK.


    The edited values are stored with the demand stratum
    Tip: Alternatively, you may view and edit the number of HOME trips by demand stratum in
    lists (see "Viewing the demand of Tour-based model demand strata in lists" on page
    1687).
    16.2.3.4

    Viewing the demand of Tour-based model demand strata in lists


    For all zones and all demand strata, you may view and edit the number of HOME trips in a
    zone list (see "Adjusting the list layout" on page 2308 and "Editing the properties of objects in
    lists" on page 2321).
    Tip: If you make the appropriate setting before opening a zone list, (see "Setting list options" on page 2306), Visum will automatically create some list layout files when a zone
    list is opened. Using these files, you can quickly view the most important demand data.
    1. Open the Zones list (see "Opening a list" on page 2299).
    2. From the selection list, select the pre-defined list layout Tour-based model - Generation
    results.

    PTVGROUP

    1687

    16.2.3.5 Creating demand matrices for tour-based model - trip distribution and mode choice
    For each demand stratum, a column with the corresponding number of HOME trips is displayed
    3. If applicable, edit the number of HOME trips for desired zones and demand strata (see
    "Editing the properties of objects in lists" on page 2321).
    16.2.3.5

    Creating demand matrices for tour-based model - trip distribution and mode choice
    If no demand matrices have been selected yet, to which the result of the Tour-based model Trip distribution and Mode choice is to be saved to by person group, you may create new
    demand matrices for Trip distribution and Mode choice and allocate them to the person groups
    automatically.
    1. In the Demand menu, click the Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Select the desired demand model.
    4. Click the Create procedure sequence button.
    The Create procedure sequence window opens.
    5. Click the Demand matrices button.
    The window Options for the creation of demand matrices opens.
    6. Make the desired changes.
    Element

    Description

    Distribution matri- Do not create distribution matrices


    ces
    Select this option if you do not want Visum to generate distribution matrices.
    Generate distribution matrices (one matrix per person group)
    Select this option if you want Visum to generate a distribution
    matrix per person group.
    Mode choice matri- Create a matrix per mode
    ces
    Select this option if you want Visum to generate a separate matrix
    per mode of the demand model.
    Create a matrix per mode and furthermore a matrix per mode
    and person group
    Select this option if you want Visum to create a separate matrix
    per mode and per combination of mode and person group.
    Activity matrices

    1688

    Do not create activity matrices


    Select this option if you do not want Visum to generate activity
    matrices.
    Create a matrix per destination activity

    PTVGROUP

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Element

    Description
    Select this option if you want Visum to generate a matrix for each
    destination activity.
    Create a matrix per destination activity and furthermore a
    matrix per destination activity and person group
    Select this option if you want Visum to create a separate matrix
    per destination activity and per combination of destination activity
    and person group.

    Note: For each matrix type, you are informed of how many matrices have been generated based on your settings.
    7. Confirm with OK.
    New demand matrices are created and allocated to all objects that have not been assigned a
    demand matrix yet.
    16.2.3.6

    Calculating tour-based model - combined trip distribution and mode choice


    For each transition in an activity chain, the Tour-based model - Combined trip distribution and
    mode choice calculates an overall demand matrix and mode-specific demand matrices simultaneously (see Fundamentals: Chpt. 4.2.3.3 , page 178).
    1. Make sure, that the zone-specific demand by demand stratum is available as zone attribute
    Home trips (see "Calculating Tour-based model - Trip generation" on page 1684 and
    "Editing the demand of tour-based demand strata" on page 1687).
    2. Make sure that - to each person group the Tour-based model - Trip distribution and Mode
    choice is to be calculated for - a demand matrix has been allocated to which the results are
    to be stored (see "Creating demand matrices for tour-based model - trip distribution and
    mode choice" on page 1688).
    3. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    4. To the procedure sequence, at the position of your choice, add the Tour-based model Combined trip distribution / mode choice procedure of the Demand model category (see
    "Setting up and starting the procedure sequence" on page 1847).
    5. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Demand strata selection Tour-based model window opens.
    6. In the Select demand model list, click the demand model the demand strata belong to.
    7. In the Demand strata list, click the demand strata for which you want to calculate the Tourbased model - Combined trip distribution and mode choice.

    PTVGROUP

    1689

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Tips: To select multiple demand strata, hold down the C TRL key while clicking the desired entries one by one.
    Alternatively, you may pre- select corresponding demand strata for certain person
    groups and activity pairs. Therefore, select the desired demand objects in the Person
    groups and Activity pairs selection lists and click the Accept pre-selection button.
    8. Confirm with OK.
    The demand strata selected are listed in the DStrata input field and in the Reference
    object(s) column.
    9. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Tour-based model - Combined trip distribution / mode choice window
    opens.
    10. Make the desired changes.
    Note: If within a row, data is missing that is required for the calculation, Visum highlights the fields in red. If you, e.g., choose to save a utility matrix, you must specify an
    output matrix. Otherwise, the filed in the Utility output matrix is highlighted in red.
    Element

    Description

    Mode choice:
    Define utility per
    destination activity

    Select this option to specify a different parameter for each destination activity. Select this option to show an additional Activity
    column in the Mode choice utility tab. For each destination activity, you can now specify a separate utility function (see "Setting
    utility function parameters for tour-based model - trip distribution
    or tour-based model - mode choice" on page 1695).

    Maximum number Number of iterations as a termination criterion, if the procedure


    of iterations
    cannot reach convergence with the selected iteration algorithm.
    Tolerance for hard Factor of precision for hard constraints (see "Properties and opticonstraints
    ons of activities" on page 1625)
    Tolerance for non- Factor of precision for non-hard constraints (see "Properties and
    hard constraints
    options of activities" on page 1625)

    1690

    PTVGROUP

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Distribution utility tab
    Element

    Description

    Key

    Unique value generated by Visum for each combination of Person


    group and Activity.

    Person group

    Person group of the trip distribution

    Activity

    Destination activity of the trip distribution

    Utility definition

    Via this button, you may - in a separate window - define a combination of matrices and attribute vectors which will be used as utility
    matrix for the particular person group and activity during Trip distribution (see "Setting utility function parameters for tour-based model
    - trip distribution or tour-based model - mode choice" on page 1695).

    Function type

    Type of the utility function for trip distribution calculation (see Fundamentals: Chpt. 4.2.3.3 , page 178)
    For selection, use the selection list.
    Note
    The function type can be set individually or for a combination of person groups and activities. To do so, select the desired combination
    by holding down the C TRL key and clicking on the desired rows.

    a, b, c

    Utility function parameters for trip distribution (see Fundamentals:


    Chpt. 4.2.3.3 , page 178)

    Graph

    Use this button to open a separate window in which you can show
    and edit the curve progression of the utility function (see "Viewing
    and editing the curve progression of the utility function" on page
    1696).

    Save utility
    matrix

    Select this option to save the destination choice utility matrix.

    Utility output
    matrix

    Click this button to choose the output matrix you want to save the destination choice utility matrix to.
    In the Save utility matrix column, use the respective symbols to
    select all highlighted rows or undo the selection.
    Click the symbol to create a new output matrix for the row selected, if
    in the Utility output matrix column, no output matrix is specified.

    PTVGROUP

    1691

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Mode choice utility tab
    Element

    Description

    Key

    Unique value generated by Visum for each combination of Person


    group and Mode.
    Note
    If the option Mode choice: Define utility per destination activity has
    been selected, the key also contains the Activity.

    Person group

    Person group of mode choice

    Activity

    Destination activity of mode choice


    Note
    This option is only available for the utility function of the mode choice,
    if you have selected the Mode choice: Define utility per destination
    activity option.

    Mode

    Mode selected

    Utility defi-

    Via this button, you may - in a separate window - define a combination of matrices and attribute vectors which will be used as utility
    matrix for the particular person group and mode during Mode choice
    (see "Setting utility function parameters for tour-based model - trip distribution or tour-based model - mode choice" on page 1695).

    nition

    Function type

    Type of the utility function for mode choice calculation (see Fundamentals: Chpt. 4.2.3.3 , page 178)
    For selection, use the selection list.
    Note
    The function type can be set individually or for person group and
    mode combinations. To do so, select the desired combination by holding down the C TRL key and clicking on the desired rows.

    a, b, c

    Utility function parameters for mode choice (see Fundamentals: Chpt.


    4.2.3.3 , page 178)

    Graph

    Use this button to open a separate window in which you can show
    and edit the curve progression of the utility function (see "Viewing
    and editing the curve progression of the utility function" on page
    1696).

    Output demand matrices tab

    1692

    Element

    Description

    Calculate

    Select this option to have Visum calculate a demand matrix for


    the combination of person group, modes, and activity chain of this
    table row.

    Person groups

    Click this button to specify the person groups of trip distribution for

    PTVGROUP

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Output demand matrices tab
    Element

    Description
    which you want to calculate an output matrix.

    Modes

    Click this button to specify the modes for which you want to calculate a matrix.

    Origin activities

    Click this button to specify the origin activities for which you want
    to calculate an output matrix.

    Destination activities

    Click this button to specify the destination activities for which you
    want to calculate an output matrix.

    From time

    Start time of the time interval, for which the calculation is to be performed (format: hh or hh:mm or hh:mm:ss)

    To time

    End time of the time interval, for which the calculation is to be performed (format: hh or hh:mm or hh:mm:ss)

    Type

    Shows the matrix type that is calculated. This data depends on


    the settings you made under Modes, Origin activity, and Destination activity.
    Distribution matrix
    You have selected all modes, origin activities and destination activities.
    Mode choice matrix
    You have no selected all modes, but all origin and destination
    activities.
    Activity matrix
    You have no selected all destination activities, but all origin activities and modes.
    Other
    For all other combinations of modes, origin activity, and destination activity

    Output matrix

    Click this button to show the matrix the results are saved to.

    You can use the symbols at the bottom section of the Output demand matrices tab to edit the
    table of output elements.
    Icon

    Name

    Description

    Insert output element

    Inserts a new row

    Copy selected out- Copies all rows selected


    put elements

    PTVGROUP

    1693

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Icon

    Name

    Description

    Delete selected
    output elements

    Deleted all rows selected

    Move selected
    output elements
    up/down

    Moves all rows selected up/down

    Sort output elements in default


    order

    Sorts the table in default order

    Calculate/Do not In the Calculate column, use the symbols to choose all
    calculate selected selected rows or undo the selection.
    output elements
    Separate output
    matrices for selected output elements...

    Click this button to create the table using the output


    matrices of your choice. In the table, select the rows of
    your choice and click the respective symbol. Then
    choose one of the following options:
    Separate matrices per person group
    A separate row is created for each person group. Entries
    in the Modes, Origin activities, and Destination activities columns are adopted.
    Separate matrices per mode
    A separate row is created for each mode. Entries in the
    Person group, Origin activities, and Destination activities columns are adopted.
    Separate matrices per origin activity
    A separate row is created for each origin activity. Entries
    in the Mode, Person group, and Destination activities
    columns are adopted.
    Separate matrices per destination activity
    A separate row is created for each destination activity.
    Entries in the Modes, Person group and Destination
    activities columns are adopted.
    Tip
    To easily set up a table, in the empty table, click the
    symbol to insert a default row. The default row contains
    all person groups, modes, origin activities, and destination activities. Using the options described, you can
    extend the default row to create the table required.

    Inserting missing Click the symbol to create a new output matrix for the
    matrices for selec- row selected, if in the Output matrix column, no output
    ted output elematrix is specified.
    ments
    1694

    PTVGROUP

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    11. Confirm with OK.
    12. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Tour-based model - Combined trip distribution and mode choice are calculated for the time
    interval specified. The results for trip distribution are saved to demand matrices per person
    group and target activity. The results for mode choice are saved to demand matrices per person group and mode (see "Creating demand matrices for tour-based model - trip distribution
    and mode choice" on page 1688).
    Tip: You can show and edit the demand matrices (see "Managing, showing and analyzing matrices" on page 1715).
    Note: If you want to calculate the demand matrices for multiple time intervals you need to
    execute the Tour-based model - Combined Trip distribution and Mode choice repeatedly
    and to set various demand matrices to which the calculation results per time interval are
    to be saved.
    Setting utility function parameters for tour-based model - trip distribution or tour-based
    model - mode choice
    1. Open the Parameters: Tour-based model - Combined trip distribution/mode choice window (see "Calculating tour-based model - combined trip distribution and mode choice" on
    page 1689).
    2. Click the Distribution utility or Mode choice utility tab.
    3. For the desired person group, click the corresponding Utility definition button

    The Utility definition for person group/destination activity <key> or Utility definition for
    person group/mode <key> window opens.
    Note: If you selected the option Mode choice: Define utility per destination, in the
    Mode choice utility tab, the window Utility definition for person group/mode/destination activity <key> opens. Then you can specify a separate utility definition for each destination activity.
    4. Make the desired changes.

    PTVGROUP

    1695

    16.2.3.6 Calculating tour-based model - combined trip distribution and mode choice
    Element

    Description

    Utility U =

    In this list, click the desired linear combination of matrices, attribute


    vectors and/or constants (see "Combining matrices and attribute
    vectors in the Matrix window" on page 1799).
    The utility function of trip distribution also contains the LogSum of
    mode-specific utility (as the first term) that you can multiply by a factor.

    Transformation
    selection list

    In the list box, click the function you want to use to transform the
    final combination result (result matrix) (see "Editing matrix values"
    on page 1761).

    1st column

    If the list contains more than one entry, the + sign indicates that the
    entries are added row by row.

    Matrix / Attribute This button opens a window that allows you to select a Visum skim
    / Constant
    matrix, zone attribute or constant. You can use a function to convert
    the values of the object selected (Transformation column). You
    can further multiply them by a factor (Coefficient column).
    Transformation
    column

    In the list box, click the function of your choice to convert the values
    selected in the Matrix / Attribute / Constant column (see "Editing
    matrix values" on page 1761).

    Coefficient

    Factor by which the values are multiplied one element at a time

    Create

    Insert row in list

    Delete

    Delete marked row from list


    Use the icons to move up or down in the list of utility functions of
    the selected tab.

    5. Confirm with OK.


    The changes are applied.
    Viewing and editing the curve progression of the utility function
    1. Open the window Parameters: Tour-based model - Combined trip distribution / mode
    choice and select the Distribution utility or Mode choice utility tab (see "Calculating tourbased model - combined trip distribution and mode choice" on page 1689).
    2. Click - for the desired person group - on the corresponding Graph button.
    The Function graph window opens. The curve progression of the utility function is shown
    with the currently set parameters a, b, and c.
    3. In the Range section, you may edit the scaling of the x axis and the y axis, if applicable.

    1696

    PTVGROUP

    16.2.4 Starting the iterative repetition


    Element

    Description

    X Min

    Minimum value for x-axis (negative values allowed)

    X Max

    Maximum value for x-axis

    Y Min

    Minimum value for y-axis (negative values allowed)

    Y Max

    Maximum value for y-axis

    Apply

    Click this button to use the entered values for the graph and to
    update the curve progression.

    4. If required, in the Parameters section, edit the parameters a, b, and c of the utility function.
    Tip: Alternatively, edit the parameters in the Distribution utility or Mode choice utility
    tab (see "Calculating tour-based model - combined trip distribution and mode choice"
    on page 1689).
    5. Click the Apply button.
    The entered parameter values are applied to the graph and will thus update the curve progression.
    6. Confirm with OK.

    16.2.4

    Starting the iterative repetition


    In typical cases, the use of the four-stage-model requires loading skim matrices calculated in
    the assignment for earlier model stages (trip distribution, mode choice).
    Iterative repetition allows the repetition of the different steps of a procedure and therefore can
    be used to re-incorporate (attribute or matrix) values calculated during the assignment into previous stages.

    16.2.4.1

    Go to a procedure in the procedure sequence (GoTo procedure)


    With the GoTo procedure, a convergence check is performed. It is checked whether a specific
    condition has been satisfied or a maximum number of iterations has been performed (see Fundamentals: Chpt. 4.2.6.1 , page 196).
    1. On the toolbar, click the

    button Open 'Procedure sequence' window.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Go to the procedure of
    the Miscellaneous category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Procedure selection window opens.
    4. Select the procedure you want to go to.

    PTVGROUP

    1697

    16.2.4.1 Go to a procedure in the procedure sequence (GoTo procedure)


    Note: If you enter a group as GoTo target, the procedure sequence is repeated from
    the first procedure of the group.
    5. Confirm with OK.
    The procedure selected is adopted into the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Go to procedure window opens.

    7. Make the desired changes.

    1698

    PTVGROUP

    16.2.4.1 Go to a procedure in the procedure sequence (GoTo procedure)


    Element

    Description

    for at least one


    network object

    Select this option if you want to use the formula below it to define
    the convergence check threshold. Thereby x is the link attribute or
    matrix specified below.
    In the entry fields, enter the parameters of your choice (see Fundamentals: Chpt. 4.2.6.1 , page 196).
    Note
    Convergence is considered reached when all matrix values or
    link attribute values in the network differ by less than the threshold from their previous value.
    Link attribute
    If you select this option, the attribute values of iteration step N and
    iteration step n-1 are compared. Thereby it is checked whether
    they have changed by less than the threshold defined and if the
    maximum number of iterations has been performed.
    Click this button to select an attribute (and subattribute, if available) in a separate window (see "The window used for the selection of one attribute" on page 963).
    Matrix
    If you select this option, the matrix values of iteration step N and
    iteration step n-1 are compared. Thereby it is checked whether
    they have changed by less than the defined threshold during the
    last iteration and if the maximum number of iterations has been
    performed.
    Using the button, click the matrix of your choice.

    The value of the


    network attribute

    Select this option to use a user-defined attribute of the network


    object for the convergence check.
    Click this button to select an attribute (and subattribute, if available) in a separate window (see "The window used for the selection of one attribute" on page 963).
    In the entry field, enter the comparative value of your choice.
    Note
    This option is recommended when you use a script to calculate
    the attribute value.

    Number of iterations

    Number of iterations as a termination criterion, if the convergence


    check cannot reach convergence.

    8. Confirm with OK.


    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).

    PTVGROUP

    1699

    16.2.4.2 Calculating the weighted mean of matrices


    The convergence check is performed. Visum goes back to a previous procedure until convergence is reached or the maximum number of iterations is calculated.
    16.2.4.2

    Calculating the weighted mean of matrices


    Using MSA (method of successive averages), you can calculate the mean value of two matrices (demand or skim matrices) (see Fundamentals: Chpt. 4.2.6.2 , page 198). In several iterations, the weighted mean value between the averaged matrix of the last iteration and the
    matrix of the current iteration is calculated.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the procedure sequence, at the position of your choice, add the procedure Method of
    Successive Averages (MSA) for matrices of the Matrices category (see "Setting up and
    starting the procedure sequence" on page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix you want to save the average values to.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Method of successive averages (MSA) for matrices window opens.

    7. Make the desired changes.


    Element

    Description

    Initialize result Activate this option to set the values of the result matrix selected in the
    matrix with 0 Reference object(s) column to 0 prior to the start of the procedure
    sequence.
    Buttons

    1700

    Click the top button to select the result matrix. It automatically corresponds to the first matrix on the right of the equation.
    Click the bottom button to select the matrix of the current iteration.

    PTVGROUP

    16.2.4.3 Calculating the weighted mean of attributes


    Element

    Description

    Drop-down list In the drop-down list, click the weighting factor with which you want to
    multiply the values in the result matrix.
    i/(i+1)
    By element, the result matrix is multiplied by the iteration index number i and divided by (i+1). The weighting factor of the other matrix is
    automatically changed to 1/(i+1). This is the default setting for MSA
    calculation.
    1/(i+1)
    By element, the result matrix is multiplied by 1 and divided by (i+1).
    The weighting factor of the other matrix is automatically changed to i/
    (i+1).
    Go to the procedure

    Here you can see the row of procedure sequence specified for the
    GoTo procedure when interactive calculation is performed.

    Iteration

    Here you can see the iteration step the procedure is currently at.

    8. Confirm with OK.


    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The matrices selected are averaged.
    16.2.4.3

    Calculating the weighted mean of attributes


    As for matrices, the average values of attributes can be determined by means of MSA (Method
    of Successive Averages) (see Fundamentals: Chpt. 4.2.6.3 , page 198). In several iterations,
    the average mean between the averaged attribute of the last iteration and the attribute of the
    current iteration is calculated.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the procedure sequence, at the position of your choice, add the procedure Method of
    Successive Averages (MSA) for attributes of the Miscellaneous category (see "Setting
    up and starting the procedure sequence" on page 1847).
    3. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Method of successive averages (MSA) for attributes window opens.

    PTVGROUP

    1701

    16.2.4.3 Calculating the weighted mean of attributes

    4. Make the desired changes.

    1702

    Element

    Description

    Network object
    type

    Network object type of the attributes for MSA


    From the selection list, you can select the network object type.

    Initialize result
    attribute with 0

    Select this option to set the value of the target attribute to 0 before
    the procedure sequence is started.

    Only active ones

    If this option has been checked, only attribute values of active network objects of the selected network object type are averaged.

    Cut off

    If this option has been checked, the calculated value is stored


    without decimal places as target attribute value.
    Note
    This option is only provided for target attributes of the Integer data
    type.

    Round

    If this option has been checked, the calculated value is rounded


    and stored as target attribute value. Rounds up to and including
    4; rounds off from 5.
    Note
    This option is only provided for target attributes of the Integer data
    type.

    Top button (target)

    Attribute you want to save the MSA result to and use as input for
    the next iteration step.
    Click this button to select an attribute (and subattribute, if available) in a separate window (see "The window used for the selection of one attribute" on page 963).

    Bottom button
    (source)

    Attribute used for average mean calculation


    Click this button to select an attribute (and subattribute, if available) in a separate window (see "The window used for the selection of one attribute" on page 963).

    Drop-down list

    i/(i+1)
    The result attribute value is multiplied by the iteration index number i and divided by (i+1). The weighting factor of the other attri-

    PTVGROUP

    16.2.5 Estimate gravitation parameters (KALIBRI)


    Element

    Description
    bute is automatically changed to 1/(i+1). This is the default setting
    for MSA calculation.
    1/(i+1)
    The result attribute value is multiplied by 1 and divided by (i+1).
    The weighting factor of the other attribute is automatically changed to i/(i+1).

    Go to the procedure

    Here you can see the row of procedure sequence specified for
    the GoTo procedure when interactive calculation is performed.

    Iteration

    Here you can see the iteration step the procedure is currently at.

    Note: Cutting or respectively rounding decimal places of calculated results during an


    iteration may lead either to a late completion or even the non-completion of the convergence criterion. Thus we recommend to use a user-defined attribute of the Number
    with decimal places data type instead of an attribute of the Integer data type.
    5. Confirm with OK.
    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The attribute values are averaged.

    16.2.5

    Estimate gravitation parameters (KALIBRI)


    The Estimate gravitation parameters (KALIBRI) function allows you to estimate the distribution
    parameters a, b and c for a utility function for the gravity model calculation of trip distribution
    (see "Calculating trip distribution" on page 1643 and "Calculating tour-based model - combined trip distribution and mode choice" on page 1689) (see Fundamentals: Chpt. 4.2.4 , page
    187).
    1. Make sure that for each zone, the production and attraction rate per demand stratum are
    available as zone attributes Productions and Attractions.
    2. Each demand stratum for which you want to calculate trip distribution must be allocated to a
    demand matrix where the results are saved.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Estimate gravitation
    parameters (KALIBRI) procedure of the Demand model category (see "Setting up and starting the procedure sequence" on page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Demand strata selection window opens.
    4. Select the desired demand stratum.
    PTVGROUP

    1703

    16.2.5.1 Estimate gravitation parameters

    Note: The demand stratum must belong to a 4-stage or tour-based model.


    5. Confirm with OK.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Estimate gravitation parameters window opens.
    7. Set the desired parameters (see "Estimate gravitation parameters" on page 1704).
    8. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The gravitation parameters are estimated.
    16.2.5.1

    Estimate gravitation parameters


    KALIBRI: Utility definition
    Element

    Description

    Utility U

    Linear combination of matrices, attribute vectors and/or constants that


    describes the utility of OD pairs

    Create

    Insert row in list

    Delete

    Delete marked row from list

    1st column

    If the list contains more than one entry, the + sign indicates that the entries are added row by row.

    Matrix / Attribute This button opens a window that allows you to select a Visum skim
    / Constant
    matrix, zone attribute or constant. You can use a function to convert the
    values of the object selected (Transformation column). You can further
    multiply them by a factor (Coefficient column).
    Transformation
    column

    In the drop-down list, click the function of your choice to convert the
    values selected in the Matrix / Attribute / Constant column.

    Transformation

    In the list box, click the function of your choice to convert the values
    selected in the Matrix / Attribute / Constant column (see "Editing
    matrix values" on page 1761).

    Coefficient

    Factor by which the values are multiplied one element at a time

    KALIBRI: Distribution
    Here you specify the desired trip distribution with regard to the utility values.

    1704

    PTVGROUP

    16.2.5.1 Estimate gravitation parameters


    Element

    Description

    From

    Lower threshold of the interval


    Notes
    The threshold is included in the interval.
    The first interval must have an empty field as From value and an empty
    field as To value 0. The last interval must have the maximum value as
    From value and an empty field as To value.

    To

    Upper threshold of the interval


    Notes
    The upper limit does not belong to the interval.
    The first interval must have an empty field as From value and an empty
    field as To value 0. The last interval must have the maximum value as
    From value and an empty field as To value.

    Share

    Percentage of matrix values that belong to the interval

    Cum. share

    Percentage of matrix values accumulated from top to bottom

    Number of
    trips

    Number of matrix values covered by the interval [Lower limit, Upper limit[

    Create

    Use this button to add a new interval to the end.

    Delete

    Use this button to delete the selected intervals.

    Read from file Use this button to delete all existing classes and import new classes and
    shares from an interval file (*.cod or *.att) into the list.
    From interval Select this option to use an interval file with classes and shares. Click the
    file
    button to choose a file.
    Notes
    This option allows you to use data that is not calculated until during the
    procedure sequence run.
    Interval files have the extensions *.cod or *.att.
    KALIBRI: Function type
    Element

    Description

    Function type

    Utility function type for which you want to calibrate the parameters
    f(U) = a U^b e^(c U)
    Select this option to calculate the parameters a, b and c.
    f(U) = a e^(c U)
    If this option has been checked, the distribution parameters a and c
    are calculated, whereas parameter b remains constant = 0.

    Weighted by the
    Select this option to weigh the utility function by the number of trips in
    number of trips in each class.

    PTVGROUP

    1705

    16.2.5.1 Estimate gravitation parameters


    Element

    Description

    each class
    Doubly consIf this option has been checked, matrix balancing by multi-protrained: Balancing cedure is calculated additionally after the first iteration (see Fundamentals: Chpt. 4.2.5 , page 188).
    by multi-procedure
    If you do not select this option, trip distribution is calculated singly
    constrained for production.
    Note
    The origin demand (Production) value is regarded for each zone.
    Multi-Parameters

    Parameters for multi procedure calculation


    Note
    These options are only available for doubly constrained gravity
    model calculation.
    Max. number of iterations
    After the user-defined number of iterations the internal iteration process is cancelled though convergence has not been reached yet.
    Quality factor
    Criterion for termination of the multi-procedure

    Max. number of ite- Without reaching convergence, the calculation is cancelled after the
    rations for Kalibri specified number of iterations.
    calculation
    Note
    Sometimes the procedure does not reach the convergence state. In
    this case, the number of KALIBRI iterations should be reduced,
    though this might cause less precise calculations.

    KALIBRI: Outputs
    Element

    Description

    Result
    matrix

    Save the calculated matrix as distribution matrix of the demand stratum


    The result matrix calculated during calibration is saved as a distribution
    matrix of the demand stratum.
    Store the calculated matrix in matrix
    The result matrix calculated during calibration is saved to a Visum matrix.
    Click the button to select the matrix of your choice.
    Do not save calculated matrix
    The result matrix calculated during calibration is not saved.

    Protocol

    1706

    Protocol output to log file


    A protocol of the calculation is output to a log file (see "Using protocol files"
    on page 876).

    PTVGROUP

    16.2.6 Creating a procedure sequence automatically


    Element

    Description
    Protocol output to file
    A protocol of the calculation is output to a file. Click the
    a file.
    No protocol output
    Visum does not output a protocol.

    16.2.6

    button to choose

    Creating a procedure sequence automatically


    You can automatically create a standard procedure sequence, including all steps and corresponding parameters for demand calculation.
    1. In the Demand menu, click the entry Demand models entry.
    The Demand models window opens.
    2. Select the Basis tab.
    3. Click the desired demand model.
    4. Click the Create procedure sequence button.
    The Create procedure sequence window opens. Based on the modes currently selected
    for the demand model (see "Properties and options of demand models" on page 1617)
    each demand stratum (standard 4-step and EVA models) or person group (tour-based
    models) of the demand model is connected to these relevant modes. For each combination
    of demand stratum and mode or person group and mode, the respective demand segment
    is allocated.
    Notes: For demand models of the EVA-P type, the mode type (PrT or PuT) of the relevant modes determines which assessment types are to be used consistently for the
    EVA Weighting step (see "Calculating EVA weighting" on page 1671).
    Travel time for modes of the PrT type
    Journey time and Adaptation time for PuT modes (Adaptation time only with the
    timetable-based assignment)
    By default, the predefined assessment type Competing walking time is not used but
    can be selected subsequently (see "Calculating EVA weighting" on page 1671).
    5. Make the desired changes.

    PTVGROUP

    1707

    16.2.6 Creating a procedure sequence automatically


    Element

    Description

    Demand matrices This button opens a separate window in which you can specify
    the demand matrices that are created during the procedure
    sequence generation. The same settings are available as for
    direct generation of demand matrices:
    Standard 4-step (see "Generating demand matrices for Standard 4-step trip distribution" on page 1642)
    EVA-P (see "Creating demand matrices for EVA trip distribution" on page 1679)
    Tour-based model (see "Creating demand matrices for tourbased model - trip distribution and mode choice" on page
    1688)
    PrT assignment
    procedure

    Procedures for PrT assignment calculation in the procedure


    sequence (see "Setting and calculating the parameters for PrT
    assignment" on page 1931)
    From the selection list, you can select a procedure.

    PuT assignment
    procedure

    Procedure for PuT assignment calculation in the procedure


    sequence (see "Setting and calculating PuT assignment parameters" on page 2006)
    From the selection list, you can select a procedure.
    Note
    You cannot automatically add a transport system-based assignment method to the procedure sequence, but you can select it
    prior to the procedure sequence execution (see "Adding procedures to the procedure sequence" on page 1848).

    Including GoTo
    procedure

    Select this option to add the group named Iterative repetition


    (including the GoTo procedure) to the end of the procedure
    sequence (see "Go to a procedure in the procedure sequence
    (GoTo procedure)" on page 1697).
    If this option has not been checked, the GoTo procedure is not
    added.

    1708

    DSegs used for


    feedback

    Via this button, you may - in a separate window - select the


    demand segments you would like to average - by an MSA operation - the calculated skim values in the iteration (see "Calculating the weighted mean of matrices" on page 1700 and
    "Calculating the weighted mean of attributes" on page 1701).
    Note
    This option is only available if the Including GoTo procedure
    option is activated.

    DSeg for convergence check

    From the list box, you may select the demand segment which is in the next GoTo procedure - to be used for convergence check

    PTVGROUP

    16.2.6 Creating a procedure sequence automatically


    Element

    Description
    execution (see "Go to a procedure in the procedure sequence
    (GoTo procedure)" on page 1697).
    Note
    This option is only available if the Including GoTo procedure
    option is activated.

    Calculate demand
    matrices by time
    interval additionally (Tourbased model)

    If this option has been checked, you can - additionally to the Tourbased model - Combined Trip distribution and Mode choice procedure for a standard 24-h time interval (0 a.m. - 12 p.m) - calculate a Tour-based model - Combined Trip distribution and
    Mode choice for a user-defined time interval.
    Note
    This option is only provided for demand models of the Tourbased model type.

    From time, To time Start time and end time of the user-defined time interval for additional calculation of the Tour-based model - Combined Trip distribution and Mode choice method (in time format: hh or hh:mm or
    hh:mm:ss)
    Note
    This option is only provided for demand models of the Tourbased model type and only if option Calculate demand matrices
    by time interval additionally (Tour-based model) has been
    selected.
    6. Confirm with OK.
    Based on the settings, the procedure sequence for demand calculation is created accordingly.
    Notes: For each demand segment (and each specified assessment type for demand
    models of the EVA-P type) two skim matrices are generated - one for the current calculation results (current matrix) and one that stores averaged values (averaged matrix).
    If demand matrices for demand calculation are missing, they are generated according to
    the settings made and are allocated to the respective demand strata. If a demand segment has not been allocated to a demand matrix for assignment, a demand matrix will
    also be generated.
    Steps of the Standard 4-step model calculation
    The table below lists the steps which are added automatically when a procedure sequence is
    generated for a demand model of the Standard 4-step type.

    PTVGROUP

    1709

    16.2.6 Creating a procedure sequence automatically


    Step

    Parameters

    ProcedureTrip generation

    For the model's demand strata with standard settings

    Group <demand model code>: Distribution and mode choice


    Calculate PrT skim matrix pro- A procedure for each PrT demand segment allocated
    cedure
    The skim tCur-PrTSys is saved to file.
    Calculate PuT skim matrix
    procedure

    A procedure for each PuT demand segment allocated


    The skim Perceived journey time is saved to file, this
    also applies to the skim Adaptation time in case of a
    timetable-based assignment (Assignment calculated with
    default parameters).

    Trip distribution procedure

    For the model's demand strata with standard settings

    Mode choice procedure

    For the model's demand strata with standard settings

    Group <demand model code>: Matrix aggregation


    Combination of matrices and
    vectors procedure

    A procedure for each demand segment allocated


    Result matrix = Sum of demand matrices allocated
    (demand stratum x mode) / occupancy rate of demand
    segment

    Combination of matrices and


    vectors procedure

    For each averaged skim matrix


    Result matrix = current skim matrix

    Group <demand model code>: Assignment


    Procedure PrT assignment

    For allocated PrT demand segments


    Procedure according to settings, using default parameter
    settings

    Procedure PuT assignment

    For allocated PuT demand segments


    Timetable-based or headway-based (according to settings), with standard parameters, including skim calculation for the demand segment currently being
    selected in the Parameters: Assignment procedure in
    the Demand segments tab (see "Headway-based assignment:Demand segments tab" on page 2018 and "Timetable-based assignment:Demand segments tab" on page
    2034)

    Group <demand model code>: Averaging skim matrices


    Calculate PuT skim matrix
    procedure

    1710

    Procedure for each PuT demand segment allocated, with


    the DSegs used for feedback option selected.

    PTVGROUP

    16.2.6 Creating a procedure sequence automatically


    Step

    Parameters
    The skim Perceived journey time is saved to file, this
    also applies to the skim Adaptation time in case of a
    timetable-based assignment (Assignment calculated with
    default parameters).

    Calculate PrT skim matrix pro- A procedure for each PrT demand segment allocated
    cedure
    The skim tCur-PrTSys is saved to file.
    Method of successive averages over matrices procedure

    Procedure for any current skim matrix


    Result matrix = i/(i+1) averaged skim matrix + 1/(i+1)
    current skim matrix

    Group <demand model code>: The group is only added if the Including GoTo procedure
    Iterative repetition
    option is selected (see "Creating a procedure sequence
    automatically" on page 1707).
    GoTo procedure procedure

    The procedure is only added if the Including GoTo procedure option is selected (see "Creating a procedure
    sequence automatically" on page 1707).
    Goes to procedure Trip distribution and compares the current skim matrices of the journey time averaged by MSA
    for any allocated PrT demand segment (with 5 = max.
    number of iterations)

    EVA-P model calculation steps


    The table below lists the steps which are added automatically when a procedure sequence is
    generated for a demand model of the EVA-P type.
    Step

    Parameters

    Procedure EVA trip generation

    For all demand strata of the model


    All production rates and study area factors are set to 0 as
    a constant value. The option Execute balancing is only
    checked if hard constraints have been defined for all
    demand strata (see "Calculating EVA trip generation" on
    page 1666).

    Group <demand model code>: Distribution and mode choice


    Calculate PuT skim matrix
    procedure

    A procedure for each PuT demand segment allocated


    The skim Perceived journey time is saved to file, this
    also applies to the skim Adaptation time in case of a
    timetable-based assignment (Assignment calculated with
    default parameters).

    Calculate PrT skim matrix pro- A procedure for each PrT demand segment allocated
    cedure
    The skim tCur-PrTSys is saved to file.

    PTVGROUP

    1711

    16.2.6 Creating a procedure sequence automatically


    Step

    Parameters

    Procedure EVA weighting

    For all demand strata of the model


    The assessment types are defined according to the mode
    type of the relevant modes (see "Calculating EVA weighting" on page 1671).
    The current skim matrix generated for the previously allocated demand segment is allocated to each combination
    of demand stratum, mode, and assessment type.
    The mode availability is set to 1.0 for all modes, and so is
    the volume-capacity ratio.
    The option Consider home zone for demand strata of
    type 3 is unchecked.

    EVA distribution/mode choice For the model's demand strata with standard settings
    procedure
    Group <demand model code>: Matrix aggregation
    Combination of matrices and
    vectors procedure

    A procedure for each demand segment allocated


    Result matrix = Sum of demand matrices allocated
    (demand stratum x mode) / occupancy rate of demand
    segment

    Combination of matrices and


    vectors procedure

    For each averaged skim matrix


    Result matrix = current skim matrix

    Group <demand model code>: Assignment


    Procedure PrT assignment

    For allocated PrT demand segments


    Procedure according to settings, using default parameter
    settings

    Procedure PuT assignment

    For allocated PuT demand segments


    Timetable-based or headway-based (according to settings), with standard parameters, including skim calculation for the demand segment currently being
    selected in the Parameters: Assignment procedure in
    the Demand segments tab (see "Headway-based assignment:Demand segments tab" on page 2018 and "Timetable-based assignment:Demand segments tab" on page
    2034)

    Group <demand model code>: Averaging skim matrices


    Calculate PrT skim matrix pro- A procedure for each PrT demand segment allocated
    cedure
    The skim tCur-PrTSys is saved to file.

    1712

    PTVGROUP

    16.2.6 Creating a procedure sequence automatically


    Step

    Parameters

    Method of successive aveProcedure for any current skim matrix


    rages (MSA) for matrices pro- Result matrix = i/(i+1) averaged skim matrix + 1/(i+1)
    cedure
    current skim matrix
    Group <demand model code>: The group is only added, if the Including GoTo proIterative repetition
    cedure option is selected (see "Creating a procedure
    sequence automatically" on page 1707).
    GoTo procedure procedure

    The procedure is only added if the Including GoTo procedure option is selected (see "Creating a procedure
    sequence automatically" on page 1707).
    Goes to procedure EVA Weighting and compares the current skim matrices of the journey time averaged by MSA
    for any allocated PrT demand segment (with 5 = max.
    number of iterations)

    Steps of Tour-based model calculations


    The table below lists the steps which are added automatically when a procedure sequence is
    generated for a demand model of the Tour-based model type.
    Step

    Parameters

    Procedure Tour-based Model - For the model's demand strata with standard settings
    Trip Generation
    Group <demand model code>: Distribution and mode choice
    Calculate PrT skim matrix pro- A procedure for each PrT demand segment allocated
    cedure
    The skim tCur-PrTSys is saved to file.
    Calculate PuT skim matrix
    procedure

    A procedure for each PuT demand segment allocated


    The skim Perceived journey time is saved to file, this
    also applies to the skim Adaptation time in case of a
    timetable-based assignment (Assignment calculated with
    default parameters).

    Tour-based model - Combined trip distribution / mode


    choice procedure

    For the model's demand strata with standard settings

    Group <demand model code>: Matrix aggregation


    Combination of matrices and
    vectors procedure

    A procedure for each demand segment allocated


    Result matrix = Sum of demand matrices allocated (person group x mode) / occupancy rate of demand segment

    Combination of matrices and

    For each averaged skim matrix

    PTVGROUP

    1713

    16.2.6 Creating a procedure sequence automatically


    Step

    Parameters

    vectors procedure

    Result matrix = current skim matrix

    Group <demand model code>: Assignment


    Procedure PrT assignment

    For allocated PrT demand segments


    Procedure according to settings, using default parameter
    settings

    Procedure PuT assignment

    For allocated PuT demand segments


    Timetable-based or headway-based (according to settings), with standard parameters, including skim calculation for the demand segment currently being
    selected in the Parameters: Assignment procedure in
    the Demand segments tab (see "Headway-based assignment:Demand segments tab" on page 2018 and "Timetable-based assignment:Demand segments tab" on page
    2034)

    Group <demand model code>: Averaging skim matrices


    Calculate PrT skim matrix pro- A procedure for each PrT demand segment allocated
    cedure
    The skim tCur-PrTSys is saved to file.
    Method of successive aveProcedure for any current skim matrix
    rages (MSA) for matrices pro- Result matrix = i/(i+1) averaged skim matrix + 1/(i+1)
    cedure
    current skim matrix
    Group <demand model code>: The group is only added if the Including GoTo procedure
    Iterative repetition
    option is selected (see "Creating a procedure sequence
    automatically" on page 1707).
    GoTo procedure procedure

    The procedure is only added if the Including GoTo procedure option is selected (see "Creating a procedure
    sequence automatically" on page 1707).
    Goes to procedure Tour-based model - Combined Trip
    distribution / Mode choice and compares the current skim
    matrices of the journey time averaged by MSA for any
    allocated PrT demand segment (with 5 = max. number of
    iterations)

    Group <Demand model code>: This group is only added if option Additionally, calculate
    Time-varying demand
    demand matrices for time interval (Tour-based model)
    has been selected (see "Creating a procedure sequence
    automatically" on page 1707)

    1714

    PTVGROUP

    16.3 Managing, showing and analyzing matrices

    16.3

    Step

    Parameters

    Tour-based model - Combined trip distribution / mode


    choice procedure

    For the model's demand strata for a user-defined time


    interval (see "Creating a procedure sequence automatically" on page 1707)

    Combination of matrices and


    vectors procedure

    Procedure for each demand segment allocated for a


    user-defined time interval (see "Creating a procedure
    sequence automatically" on page 1707)
    Result matrix = Sum of demand matrices allocated (person group x mode) / occupancy rate of demand segment

    Managing, showing and analyzing matrices


    In Visum you can create new matrices, edit matrix values, use matrices for calculation purposes and save the changes you made.
    Notes: In demand matrices and skim matrices as well, relations may connect either
    zones or main zones. Matrix file management and editing functionality is provided for
    zone matrices as well as for main zone matrices.
    For arithmetic operations you may not mix zone matrices and main zone matrices, since
    they have different dimensions.
    Subjects
    Matrices overview
    Opening matrices
    Managing matrices in the Matrix window or Histogram window
    Generating new matrix
    Editing formula matrices
    Reading an external matrix into a network model
    Showing and editing matrix attribute values
    Saving matrices
    Filtering and aggregating matrix data, changing the view
    Saving and loading the layout of a Matrix editor or Histogram window
    Setting graphic parameters for the Matrix editor window
    Showing matrices in a histogram
    Comparing two matrices in a scatter plot
    Deleting Visum matrices
    Basic settings for matrices

    16.3.1

    Matrices overview
    Matrices are independent Visum objects. As part of demand description they are also part of
    the version file. Besides the Visum matrices (demand, skim, and weighting matrices), you can
    also edit external matrices available as a file.
    The row objects of a matrix are called origin or origin objects. The column objects of a matrix
    are called destination or destination objects. This is how so-called OD pairs are created.

    PTVGROUP

    1715

    16.3.1.1 Showing matrices in the Matrices window


    Visum matrices represent the relations between zones and main zones in a network and are
    always quadratic.
    16.3.1.1

    Showing matrices in the Matrices window


    The Matrices window is organized with a navigator, showing the matrices available in the version. The matrices are divided by matrix type (demand or skim matrix). The latter are further
    subdivided into reference type (zone or main zone matrix) and data and formula matrices.
    Visum matrices are always displayed with a number and code.
    In addition, all external matrices that you open with this version during the current session are
    displayed. The code is displayed for external, unsaved matrices, the name is displayed for all
    saved matrices.

    The matrices currently open are displayed in bold. If you move the mouse pointer over a matrix
    name, a tooltip with information on the matrix will appear.
    From here, you can open a matrix for editing or either create a new matrix or delete an existing
    one via the context menu or the toolbar. Furthermore, you can start simple arithmetic operations without opening the matrix before.

    1716

    PTVGROUP

    16.3.1.2 The Matrix editor window


    Notes: To open a list of all Visum matrices, in the Matrices window, right-click next to the
    navigator. From the shortcut menu, choose List or from the Lists menu, choose List (see
    "Opening a list" on page 2299). In the list, you can search for matrices and change matrix
    attribute values (see "Working with lists" on page 2299 and "Showing and editing matrix
    attribute values" on page 1731).
    If you select a matrix in the Matrices window, the matrix attributes selected are displayed
    in the Quick view window (see "Selecting attributes for the Quick view display" on page
    811). Here you can also change attribute values (see "Showing and editing matrix attribute values" on page 1731). Attribute values of external matrices are only displayed for
    opened matrices.
    In the navigator, you can hide the entries of external matrices that are not open. To do so,
    right-click next to the navigator and select Hide external matrices which are no longer
    open.
    Toolbar of the Matrices window
    Use the toolbar to call specific program functions.
    Icon

    16.3.1.2

    Name

    Description

    Create matrices

    Create new matrices

    Open external matrix

    Open matrix file

    Edit

    Open matrices selected in Matrix editor window

    Create histogram

    Create histogram for matrices selected

    Delete

    Delete selected Visum matrices

    The Matrix editor window


    When you open a matrix, it is displayed in a Matrix editor window (see "Opening matrices" on
    page 1721).

    PTVGROUP

    1717

    16.3.1.2 The Matrix editor window

    (1) Title bar


    The title bar shows the numbers and names of Visum matrices. When you open several matrices, the number of matrices opened is displayed in the title bar. It further shows the file name
    of external matrices. You can change the number and name of a matrix (see "Showing and
    editing matrix attribute values" on page 1731).

    (2) Menu bar


    As soon as a Matrix editor window becomes active, an additional Matrix editor menu is
    shown. This menu item provides matrix-specific functions.
    (3) Matrix values
    Here the matrix values of one or several matrices opened are displayed. The values in the
    matrix diagonals are highlighted in yellow. The shortcut menu offers various editing options.
    You can change the matrix display using various options (see "Filtering and aggregating
    matrix data, changing the view" on page 1742 and "Basic settings for matrices" on page 1758).
    Alternatively, you can show and edit the matrices in lists (see "Opening matrices in the List
    view" on page 1722).
    (4) Toolbars of the Matrix editor window
    The toolbars allow you to call specific program functions.
    Tip: You can customize their size and position (see "Modifying toolbars and windows" on
    page 824).

    1718

    PTVGROUP

    16.3.1.2 The Matrix editor window


    Icon

    Name

    Description

    Select matrices

    Manage the matrices opened in the Matrix editor window

    Options

    Edit display properties of the Matrix editor window

    Matrix view/List view

    Switches between the Matrix view and the List view

    Filter the matrix data


    view

    Hide or show certain columns or rows according to filter criteria

    Find matrix cell

    Find the matrix cell in the opened matrix

    Recalculate dynamically Recalculate data in aggregated view if classification


    aggregated view
    was made according to indirect (main) zone attribute
    and matrix values were subsequently changed
    Read matrix content
    from file

    Import data from another matrix into the matrix shown


    in the Matrix editor window

    Save to file/Save as

    Save Visum matrix opened in the Matrix editor window as a file or save the external matrix opened
    under a different name

    Export of the current


    view to the clipboard

    Copy matrix values to the clipboard

    Export current view to


    database

    Save matrix values in a database

    No synchronization with
    network editor

    The Matrix editor window is not synchronized with


    the Network editor window.

    Synchronization with net- OD pairs highlighted in the Matrix editor window are
    work editor: Mark (main) also highlighted in the Network editor window.
    zones
    Synchronization with net- OD pairs highlighted in the Matrix editor window are
    work editor: Mark (main) also highlighted in the Network editor window. If
    zones and shift view
    required, the network section is shifted in such a way
    that all marked objects are visible.
    Synchronization with net- OD pairs highlighted in the Matrix editor window are
    work editor: Mark (main) also highlighted in the Network editor window. Addizones and autozoom
    tionally, in the network an auto zoom is carried out for
    the marked objects.
    Initialize

    PTVGROUP

    Set all matrix values to 0

    1719

    16.3.1.2 The Matrix editor window


    Icon

    Name

    Description

    Set value(s)

    Overwrite matrix with a constant or another value of different matrix

    Add

    To the matrix values add a constant or other value of another matrix

    Subtract

    From the matrix values subtract a constant or other value of


    another matrix

    Multiply

    Multiply the matrix values by a constant or other value of


    another matrix

    Divide

    Divide the matrix values by a constant or other value of another matrix

    Form the minimum Replace matrix values by the minimum of the respective
    matrix value and a constant or value with the same OD pair,
    but of another matrix
    Form the maximum

    Replace matrix values by the maximum of the respective


    matrix value and a constant or value with the same OD pair,
    but of another matrix

    Raise to power

    Raise matrix values (by element) to the power of a constant


    or other value of another matrix

    Round

    Round matrix values to a specified precision

    Exponential function

    Replace matrix values (by element) by a matrix exponential


    function

    Apply natural loga- Replace matrix values (by element) by their natural logarithm
    rithm
    Form reciprocal

    Replace matrix values (by element) by their reciprocal


    value

    Transpose

    Transpose the matrix values from columns into rows and


    vice versa

    Set diagonal

    Set diagonal matrix values to a constant value

    Reflect lower triangle

    Copy matrix values below the diagonal to the respective


    OD pairs in the upper triangle

    Reflect upper triangle

    Copy matrix values above the diagonal to the respective


    OD pairs in the bottom triangle

    Make symmetrical Replace matrix values by the mean value formed by pairs
    of the two laterally reversed matrix values
    Combination of
    matrices and vectors

    1720

    Linkage of matrices and vectors by arithmetic operations

    PTVGROUP

    16.3.2 Opening matrices


    Icon

    Name

    Description

    Set values conditionally

    Replace matrix values which satisfy a certain condition by a


    particular value.

    Aggregate

    Group, renumber or delete rows and/or columns of a matrix

    Disaggregate

    Subdivide rows and/or columns of a matrix into several


    rows and/or columns

    Projection

    Use a factor to project matrix values per row, column or


    both to a new target value

    Projection by territory

    Use different factors depending on territory or territory relation to project matrix values

    (5) Window selection


    Use the list box to switch between the opened windows.
    (6) Tab bar
    Using tabs, you can switch between all opened matrices.

    16.3.2

    Opening matrices
    You can open several matrices at the same time - in the same window or in separate windows.
    You can open Visum matrices and external matrices.
    Notes: You can also display the matrix values in a histogram (see "Showing matrices in a
    histogram" on page 1752).
    You can change the matrix display using various options (see "Filtering and aggregating
    matrix data, changing the view" on page 1742 and "Basic settings for matrices" on page
    1758). You can also show matrices in the List view (see "Opening matrices in the List
    view" on page 1722).
    Opening a Visum matrix
    Opening an external matrix
    Opening matrices in the List view
    Opening several matrices in separate windows
    Opening several matrices in one window
    Opening the same matrix several times

    16.3.2.1

    Opening a Visum matrix


    You can open a Visum matrix, i.e. a matrix of this version, for editing.
    In the Matrices window, in the navigator, double-click the matrix of your choice.

    PTVGROUP

    1721

    16.3.2.2 Opening an external matrix

    Tips: Alternatively, to select a matrix, on the window toolbar, click


    Edit matrix or
    from the shortcut menu, choose Edit. You will also find both options in the Matrices
    list (see "Opening a list" on page 2299).
    Or simply open the matrices in the OD demand data window (see "Connecting
    demand matrices and demand segments" on page 1607).
    A Matrix editor window opens with the selected matrix (see "The Matrix editor window" on
    page 1717).
    Note: Use the
    Select matrices icon to edit the displayed matrices in this window
    (see "Managing matrices in the Matrix window or Histogram window" on page 1724).
    16.3.2.2

    Opening an external matrix


    You can open a matrix file in Visum.
    1. On the Matrices window toolbar, click

    Open external matrix.

    The Open external matrices window opens.


    Tips: Alternatively, from the Edit menu, choose Matrix editor> Open external matrix.
    Alternatively, in the Matrices window, right-click next to the navigator. Then from the
    shortcut menu, choose Open external matrix.
    2. Select the desired file.
    3. Click the Open button.
    Note: Alternatively, you may enter path and file name.
    A Matrix editor window opens with the selected matrix (see "The Matrix editor window" on
    page 1717).
    Notes: In a network model, you can read in an external matrix when opening it (see "Reading an external matrix into a network model" on page 1731).
    Use the
    Select matrices icon to edit the displayed matrices (see "Managing matrices in the Matrix window or Histogram window" on page 1724).
    When you open an external matrix, it is listed in the navigator window Matrices . The
    matrix name remains visible after closing this matrix. Subsequently you can double-click
    the matrix name to re-open the external matrix.
    16.3.2.3

    1722

    Opening matrices in the List view


    In the Matrix Editor, you can show matrices in the matrix or list format. The List view also allows
    you to edit Visum matrices and external matrices, apply arithmetic operations, and simultaneously work with several matrices.

    PTVGROUP

    16.3.2.4 Opening several matrices in separate windows


    1. In the Matrices window, in the navigator, select the matrices of your choice.
    2. Right-click one of the matrices you selected.
    The shortcut menu opens.
    3. Choose Edit in list view.
    The matrices are opened in the List view.

    Notes: The
    Matrix view/List view icon allows you to switch between the two views.
    In the List view, you can also use specific filter criteria to show and hide matrix data of
    Visum matrices (see "Filtering matrix data" on page 1742) and you can display matrix
    data of Visum matrices in an aggregated form (see "Showing matrix values in an aggregated form" on page 1744).
    16.3.2.4

    Opening several matrices in separate windows


    1. In the Matrices window, in the navigator, select the matrices of your choice.
    2. Right-click one of the matrices you selected.
    The shortcut menu opens.
    3. Click Edit separately.
    The matrices are opened in separate Matrix editor windows.
    Note: Use the
    Select matrices icon to edit the matrices shown in a window (see
    "Managing matrices in the Matrix window or Histogram window" on page 1724)

    16.3.2.5

    Opening several matrices in one window


    Several matrices with identical OD pairs can be opened simultaneously in the same Matrix editor window.
    1. In the Matrices window, in the navigator, select the matrices of your choice.
    2. Right-click one of the matrices you selected.
    The shortcut menu opens.
    3. Click Edit.

    Tip: Alternatively, on the tab toolbar, click

    Edit.

    The matrices are opened in a Matrix editor window.

    PTVGROUP

    1723

    16.3.2.6 Opening the same matrix several times


    Notes: The Matrix editor title bar and tab bar show how many matrices have been opened simultaneously.
    Matrix values with the same OD relation are displayed next to each other. The matrix
    number displayed at the top of each column indicates where the matrix values come
    from.
    Use the
    Select matrices icon to edit the displayed matrices (see "Managing matrices in the Matrix window or Histogram window" on page 1724)
    16.3.2.6

    Opening the same matrix several times


    1. Open the desired matrix (see "Opening a Visum matrix" on page 1721 and "Opening an
    external matrix" on page 1722).
    2. In the Matrices window, in the navigator, select the matrix of your choice.
    3. Right-click the matrix.
    The shortcut menu opens.
    4. Choose Edit in new window.
    The matrix is opened in a separate Matrix editor window.
    Note: Use the
    Select matrices icon to edit the matrices shown in a window (see
    "Managing matrices in the Matrix window or Histogram window" on page 1724)

    16.3.3

    Managing matrices in the Matrix window or Histogram window


    1. Open a Matrix editor or Histogram window (see "Opening matrices" on page 1721 and "Showing matrices in a histogram" on page 1752).
    Tip: To show another matrix in a Matrix editor or Matrix histogram window, use the
    drag-and-drop operation to drag the matrix from the navigator to the respective window.
    2. On the window toolbar, click the

    Select matrices icon.

    The Matrix list window opens.


    Tip: Alternatively, from the Matrix editor menu, choose Select matrices.

    1724

    PTVGROUP

    16.3.4 Generating new matrix

    Note: A list is displayed with the matrices that are currently open in the window. The
    sequence the matrices are listed in corresponds to the sequence of the columns in
    the Matrix editor window and the histogram.
    3. Make the desired settings.
    Element
    Create

    Open

    Delete
    Up

    Down

    Description
    Use this button to open a separate window. In the navigator, you can
    then choose further Visum matrices that are shown in the same window.
    Note
    These matrices must have the same dimension and key values.
    Click this button to open further external matrices in the same window.
    Note
    These matrices must have the same dimension and key values.
    Click this button to delete the matrices selected from the list and from
    the window.
    Use this button to move the matrix selected up in the list. The
    sequence in the list defines the sequence the data is shown in the
    Matrix editor window or histogram. Matrix data that is at the top of the
    list is shown further left.
    Use this button to move the matrix selected down in the list. The
    sequence in the list defines the sequence the data is shown in the
    Matrix editor window or histogram. Matrix data that is at the top of the
    list is shown further left.

    4. Confirm with OK.


    The matrices are displayed according to the settings you made.

    16.3.4

    Generating new matrix


    You can generate a new matrix:

    PTVGROUP

    1725

    16.3.4.1 Generating matrix with zero values


    A Visum matrix or an external matrix with the value 0 for all relations
    A Visum matrix that is automatically generated from the values of other Visum matrices or
    attribute values and is continuously updated.
    16.3.4.1

    Generating matrix with zero values


    1. In the Matrices window, on the toolbar, click the

    Create matrix icon.

    The Create matrix window opens.


    Tip: Alternatively, In the Matrices tab, right-click next to the navigator. From the shortcut menu, choose Create matrix. The symbol and the context menu entry are both
    provided in the Matrices list (see "Opening a list" on page 2299).

    2. Make the desired changes.

    1726

    Element

    Description

    Number of
    matrices to
    be created

    Number of matrices you would like to create


    Note
    When creating more than one matrix, the matrix numbers will be continuously ascending. All created matrices have the same properties.

    Number

    User-defined matrix number (only for Visum matrices)

    Code

    Short name of the matrix

    PTVGROUP

    16.3.4.2 Create matrix calculated from formula


    Element

    Description

    Name

    Long name of the matrix

    Visum
    matrix

    Here you specify the matrix type (demand or skim matrix) and reference
    (zone or main zone) for Visum matrices.
    Define without formula
    Select this option to insert a matrix that contains the value 0 for all relations.
    Define with formula
    Select this option to insert a matrix that is automatically calculated from
    other matrices or attributes. Click the Edit formula button to specify the
    calculation (see "Create matrix calculated from formula" on page 1727).

    External
    matrix

    Dimension of external matrix


    External matrix of zone dimension
    Select this option to generate an external matrix according to the zone
    dimension specified in the version.
    Transfer zone numbers and names
    Select this option to use zone numbers and names of the version for the
    new matrix.
    External matrix of main zone dimension
    Select this option to generate an external matrix according to the main
    zone dimension specified in the version.
    Transfer the main zone numbers and names
    Select this option to use the main zone numbers and names of the version for the new matrix.
    External matrix of arbitrary dimension
    Select this option to generate a matrix with the dimension of your
    choice. In the entry boxes, enter the number of rows and columns.

    Edit new
    matrices
    after creating

    Select this option to open the created matrices in the Matrix editor and
    edit them.

    3. Confirm with OK.


    The new matrix is created and opened in a Matrix editor window. In the Matrices window, a
    new matrix entry is displayed.
    16.3.4.2

    Create matrix calculated from formula


    You can create a Visum matrix that is calculated from other Visum matrices or (main) zone attributes. This formula matrix is automatically recalculated if one of its operands changes.

    PTVGROUP

    1727

    16.3.4.2 Create matrix calculated from formula


    You are supported by Visum in formal generation of the formula. The syntax is checked on
    entry and errors are highlighted in color.
    Notes: You cannot change the values in formula matrices.
    If you delete matrices or attributes that are used to calculate a formula matrix, the formula
    matrix is also deleted.
    1. In the Matrices window, on the toolbar, click the

    Create matrix icon.

    The Create matrix window opens.


    2. Make the desired changes.
    Element

    Description

    Number

    User-defined matrix number (only for Visum matrices)

    Code

    Short name of the matrix

    Name

    Long name of the matrix

    Visum
    matrix

    Using the four options at the top of the window, specify the matrix type
    (demand or skim matrix) and object type reference (zones or main
    zones).

    3. In the Visum matrix section, select the Define with formula option.
    4. Click the Edit formula button.
    The Edit formula for matrix <number> window opens.
    5. Into the text box, enter the desired formula for calculation, or click the buttons next to the text
    box to create a formula.
    Note: You can copy and paste the formula from another formula matrix to use it.

    1728

    PTVGROUP

    16.3.4.2 Create matrix calculated from formula


    Element

    Description
    Select the operands for the formula matrix.
    Select matrix
    If the option is selected you can select a matrix in the Navigator.
    Network attribute
    If this option is selected, you can use the
    icon to select a network
    attribute for the formula.
    Zone attribute
    If this option is selected, you can use the button to apply a zone attribute
    for the formula.
    Origin
    If the entry is selected, the attribute values of origin zone are used.
    Destination
    If the entry is selected, the attribute values of destination zone are
    used.
    Load matrix from file
    You can use this button to load a matrix file.
    Constant
    If this option is selected, you can enter a constant numeric value as an
    operand.
    Click this button to select a binary operator for the formula. The available selection depends on the type of operand whose values are used in
    the formula.
    Click the button to select a function for the formula (see "Using matrix
    values for calculations" on page 1776).
    Abs(x) absolute value of x
    Floor(x) rounds x to the next smaller integer, Floor() is inserted at
    the cursor position.
    Exp(x) generates the exponential function of x
    Reciprocal(x) generates the reciprocal value of x, that is, 1/x; Reciprocal() is inserted at the cursor position
    Ln(x) generates the natural logarithm of x
    Max(x,y) forms the maximum of x and y.
    Min(x,y) forms the minimum of x and y
    OnlyActiveODPairs(x,y) applies a value of x to the active OD pairs
    and a value of y to inactive OD pairs; OnlyActiveRelations(,)
    is inserted at the cursor position
    MirrorTopTriangle(x) mirrors the upper triangle of the matrix x, Mirror_Upper() is inserted at the cursor position
    Power(x,y) corresponds to xy, Pow(,) is inserted at the cursor position

    PTVGROUP

    1729

    16.3.5 Editing formula matrices


    Element

    Description
    Percent(x,y) is equivalent to 100*x/y, Percent(,) is inserted at the
    cursor position
    Round(x,p) rounds x to p decimal places, the text Round(,) is inserted at the cursor position
    Make symmetrical(x) computes the mean value of the value
    above and below the matrix diagonal in a matrix x; Symmetrize()
    is inserted at the cursor position
    Transpose(x) swaps the row and column values in a square matrix;
    Transpose() is inserted at the cursor position
    MirrorBottomTriangle(x) mirrors the lower triangle of the matrix x,
    Mirror_Lower() is inserted at the cursor position
    Click this button to insert a bracket term without content into the formula.

    6. Confirm with OK.


    7. Confirm again with OK.
    The new formula matrix is created and calculated. It is displayed in the Matrices window,
    under Formula matrices.
    Note: If you save a formula matrix as a file, only the current values are saved, not the formula.

    16.3.5

    Editing formula matrices


    You cannot edit the values of a formula matrix directly. However, you can edit the formula.
    Editing the formula of a formula matrix
    1. In the Matrices window, right-click the formula matrix.
    The shortcut menu opens.
    2. From the menu, choose Edit formula.
    The Edit formula for matrix <number> window opens.
    3. Make the desired settings (see "Create matrix calculated from formula" on page 1727).
    4. Confirm with OK.
    The formula is changes and the matrix values are recalculated.
    Converting a formula matrix into a data matrix
    1. In the Matrices window, right-click the formula matrix.
    The shortcut menu opens.
    2. From the menu, choose Convert into data matrix.
    The formula matrix is converted into a data matrix. The formulas are converted into values.

    1730

    PTVGROUP

    16.3.6 Reading an external matrix into a network model

    16.3.6

    Reading an external matrix into a network model


    You can read a matrix which is available as a file into the Visum network model. In this case,
    only those matrix values are read in whose OD pairs exist in the network.
    1. In the Matrices window, right-click next to the navigator.
    The shortcut menu opens.
    2. From the menu, choose Add external matrix to network model.
    The Add external matrix to network model window opens.
    3. Make the desired changes.
    Element

    Description

    Number

    User-defined matrix number

    Code

    Short name of the matrix

    Name

    Long name of the matrix

    Demand matrix
    for zones

    Select this option to read in a demand matrix for zones.

    Skim matrix for


    zones

    Select this option to read in a skim matrix for zones.

    Demand matrix
    for main zones

    Select this option to read in a demand matrix for main zones.

    Skim matrix for


    main zones

    Select this option to read in a skim matrix for main zones.

    File

    symbol to select the matrix file.


    Click the
    Note
    Alternatively, into the field, enter the file name and the path.

    4. Confirm with OK.


    If the matrix file contains OD pairs that do not exist in the network, a corresponding message is displayed.
    5. If required, again confirm with OK.
    The matrix data is read into a new Visum matrix. OD pairs that do not exist in the read in matrix
    file are assigned the value 0. The matrix is opened.

    16.3.7

    Showing and editing matrix attribute values


    In the Quick view window or list, you can edit matrix attribute values.
    Editing attribute values in the Quick view window
    1. Open the Quick view window (see "Quick view window" on page 810).

    PTVGROUP

    1731

    16.3.7 Showing and editing matrix attribute values


    2. In the Quick view window, select the attributes of your choice (see "Selecting attributes for
    the Quick view display" on page 811).
    3. In the Matrices window, click the matrix of your choice.
    4. In the Quick view window, edit the attribute values.
    Note: Attribute values of external matrices are only displayed for opened matrices.
    Element

    Description

    Number

    User-defined matrix number

    Code

    Short name of the matrix

    Name

    Long name of the matrix

    Matrix type

    Demand matrix or skim matrix

    Object type
    reference

    Relations in matrices may be zone pairs or pairs of main zones.

    Number of
    rows

    Number of rows in the matrix (cannot be edited)

    Number of
    columns

    Number of columns in the matrix (cannot be edited)

    Total

    Total of all matrix values (cannot be edited)

    Diagonal
    sum

    Total of matrix diagonals (cannot be edited)


    Note
    The diagonal of a matrix runs from top left to bottom right (FromZoneNo
    = ToZoneNo). In demand matrices, the diagonal describes zone-internal travel demand.

    Demand seg- For skim matrices you can select the demand segment the matrix refers
    ment code
    to from the selection list.
    Demand seg- The codes of the demand segments associated with the matrix are disment set
    played for demand matrices (see "Connecting demand matrices and
    demand segments" on page 1607).

    1732

    DStratum

    Number of demand strata with trip distribution results that are saved to
    the matrix (see "Properties and options of demand strata" on page
    1635).

    File name

    For external matrices, name of the matrix file


    For Visum matrices, name of the file the matrix values were last imported from or exported to.

    Random
    rounding

    Rounding last used when saving values

    Decimal pla-

    Number of decimal places saved for matrix values to a file

    PTVGROUP

    16.3.8 Saving matrices


    Element

    Description

    ces
    Data source
    type

    In the list box, choose whether you want to use data from a file or have
    it calculated with a formula.
    Note
    You can switch from the formula entry to the data file entry, but not vice
    versa.

    Formula

    Shows the formula used

    The attribute values are immediately changed.


    Editing attribute values in the list
    1. Open the Matrices list (see "Opening a list" on page 2299).
    2. Show the attributes of your choice (see "Viewing/Hiding attributes" on page 2309).
    3. Edit the desired attributes (see "Editing attribute values in a list" on page 2321).
    The attribute values are immediately changed.

    16.3.8

    Saving matrices
    Changes you make to Visum matrices remain in effect when you close the Matrix editor window. However, to save your changes permanently, you need to save them to the version file. If
    required, you can save Visum matrices to a file.
    To keep changes made to external matrices, you must save them to a file when you close the
    Matrix editor window.
    You can save matrices either in a binary format or in one of four text formats (see "Visum-specific matrix file formats" on page 2678).
    For demand matrices, you can save the volumes of routes found by OD pair as partial matrices
    which just contain either the active trips or the remaining trips.
    Tips: Alternatively you can save skim matrices to file automatically with the calculation
    (see "Calculating:PrT skims" on page 1984 and "Calculating PuT skims" on page 2073).
    A further option: You can also save demand matrices together with the demand description (see "Saving demand data" on page 1842).
    EVA weighting matrices can also be saved (see "Managing weighting matrices" on page
    1677).

    16.3.8.1

    Saving a Visum matrix to a file


    Note: If you save a formula matrix as a file, only the current values are saved, not the formula.
    1. In the Matrices window, right-click the matrix of your choice.

    PTVGROUP

    1733

    16.3.8.1 Saving a Visum matrix to a file


    The shortcut menu opens.
    2. Click Save to file.
    The Save matrix window opens.
    Tips: Alternatively, open the matrix and in the Matrix editor window, on the toolbar,
    symbol Save to file, or from the Matrix editor menu, choose> Save to
    click the
    file. The Matrices list context menu contains an entry for this (see "Opening a list" on
    page 2299).
    3. Enter the file name and the path, if required.
    4. Select a file type, if required.
    Notes: You can specify and manage the file types available under menu File> Project directories> Edit project directories (see "Editing the storage location of files"
    on page 837).
    When you choose the file type Matrix (*.*), you must add an extension to matrix file
    name.
    5. Click the Save button.
    The Write matrix <Matrix name> window opens.
    6. Make the desired settings.

    1734

    Element

    Description

    Format

    From the selection list, you can select the output data format for the
    matrix file.
    For more information on data formats please refer to the appendix
    (see "Matrix formats" on page 2678).

    Matrix

    If you choose to save a skim matrix, in the list box, your only option is
    Skim matrix.
    If you choose to save a demand matrix, in the list box, select either
    Total matrix or Partial matrix (see "Example: Demand matrix with flow
    bundle matrix and remaining matrix" on page 1741).
    Demand matrix
    Total demand by demand segment. If applicable, you may reduce
    the total demand to a partial matrix via OD pair filter.
    Flow bundle matrix (partial matrix)
    Filtered trips
    Note
    This entry is only available after you select the Flow bundle option
    (see "Displaying flow bundles" on page 2265).

    PTVGROUP

    16.3.8.1 Saving a Visum matrix to a file


    Element

    Description
    Assignment matrix (partial matrix)
    Assigned trips ( total demand) by demand segment
    Note
    This entry is only available after you calculate an assignment.
    Tip
    Alternatively, you can save partial matrices during the procedure
    sequence run, if an assignment was calculated beforehand (see
    "Saving partial matrices during the execution of the procedure
    sequence" on page 1739).

    Consider OD
    pair filter

    If this option has been checked, only those OD pairs are saved to
    matrix file which are in the active state (see "Exception: Filter for OD
    pairs" on page 1026).
    If this option has not been checked, all relations are saved to
    matrix file.
    Notes
    For flow bundle matrices, the OD pair filter is always regarded. Therefore it does not need to be checked in this case.
    For other matrix types this option is only provided if the OD pair filter
    has been set.

    PTVGROUP

    1735

    16.3.8.2 Saving external matrices


    Element

    Description

    Random round Use this option to set the rounding when you want to save matrix attributes that have more decimal places than the number of decimal places specified for matrix attributes (see "Showing and editing matrix
    attribute values" on page 1731).
    If this option has been checked, values are randomly rounded up
    or down according to the particular share to be rounded. Random
    rounding causes the total of the values in the matrix to remain approximately constant.
    Example
    0.3 is rounded up to 1 with 30% probability and down to 0 with 70%
    probability.
    If this option has not been checked, the values are rounded arithmetically, i.e. decimal values up to 4 are rounded down and decimal
    values 5-9 are rounded up. This applies to negative numbers, too.
    Example
    1.2 is rounded down to 1; 4.5 is rounded up to 5 and 5.5 to 6.
    Remaining
    matrix

    If this option has been checked, the values of the remaining


    demand are saved to file which is not regarded for the currently
    selected partial matrix.
    If this option has not been checked, the demand values are saved
    for the currently selected partial matrix.
    Notes
    This option is provided only if a partial matrix has been selected in
    the Matrix selection list.
    After a LUCE equilibrium assignment, the value of the remaining
    matrix is null.

    7. Confirm with OK.


    The matrix values are saved to the matrix file specified. In the Matrix editor window, the Visum
    matrix remains open.
    16.3.8.2

    Saving external matrices


    You can save an external matrix that you have opened.
    1. Open the desired matrix (see "Opening matrices" on page 1721).
    2. In the Matrix editor window, on the toolbar, click the

    symbol Save as.

    The Save matrix window opens.


    Tip: Alternatively, in the Matrices tab, in the navigator, right-click an external matrix.
    Then from the shortcut menu, choose Save as.

    1736

    PTVGROUP

    16.3.8.2 Saving external matrices


    3. Enter the file name and the path, if required.
    Note: A file name for the external matrix is suggested.
    4. Select a file type, if required.
    Notes: You can specify and manage the file types available under menu File> Project directories>Edit project directories (see "Editing the storage location of files"
    on page 837).
    When you choose the file type Matrix (*.*), you must add an extension to matrix file
    name.
    5. Click the Save button.
    The Write matrix <Matrix name> window opens.
    Element

    Description

    Format

    From the selection list, you can select the output data format for the
    matrix file.
    For more information on data formats please refer to the appendix
    (see "Matrix formats" on page 2678).

    Matrix

    If you choose to save an external matrix, the list box only contains
    the option External matrix.

    Random round Use this option to set the rounding when you want to save matrix attributes that have more decimal places than the number of decimal places specified for matrix attributes (see "Showing and editing matrix
    attribute values" on page 1731).
    If this option has been checked, values are randomly rounded up
    or down according to the particular share to be rounded. Random
    rounding causes the total of the values in the matrix to remain approximately constant.
    Example
    0.3 is rounded up to 1 with 30% probability and down to 0 with 70%
    probability.
    If this option has not been checked, the values are rounded arithmetically, i.e. decimal values up to 4 are rounded down and decimal
    values 5-9 are rounded up. This applies to negative numbers, too.
    Example
    1.2 is rounded down to 1; 4.5 is rounded up to 5 and 5.5 to 6.
    6. Confirm with OK.
    The matrix is saved to the specified matrix file. The new matrix file is opened in the Matrix editor window.

    PTVGROUP

    1737

    16.3.8.3 Saving partial matrices


    16.3.8.3

    Saving partial matrices


    You can filter or dynamically aggregate a matrix and then only save the values that are displayed.
    1. Filter or aggregate the matrix.
    Filter (see "Filtering matrix data" on page 1742)
    Dynamically aggregate (see "Showing matrix values in an aggregated form" on page
    1744)
    2. In the Matrix editor window, on the toolbar, click the

    symbol Save as.

    A message is displayed. Decide whether you want to save the entire matrix or only part of it,
    namely the values currently displayed.
    3. Click the View button.
    The Save matrix window opens.
    4. Continue as if you were to save the whole matrix.
    The partial matrix is saved. For aggregated matrices, the name and value of the aggregation
    attribute are also output.
    16.3.8.4

    Saving matrices during procedure sequence execution


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Save matrix procedure
    of the Matrices category (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix you want to save.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Select matrix format window opens.
    7. In the list box, click the matrix format of your choice (see "Visum-specific matrix file formats"
    on page 2678).
    8. Confirm with OK.
    9. In the row of the added procedure, click in the Variant/file column.
    The icon

    1738

    is displayed.

    PTVGROUP

    16.3.8.5 Saving partial matrices during the execution of the procedure sequence

    10. Click the

    icon.

    The Save matrix window opens.


    11. Enter the file name and the path, if required.
    12. Click the Save button.
    The file name appears in the Variant/file column.
    13. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The matrix is saved.
    16.3.8.5

    Saving partial matrices during the execution of the procedure sequence


    Note: This functionality is only provided for demand matrices.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Save demand matrix
    from route volumes procedure of the Matrices category (see "Setting up and starting the
    procedure sequence" on page 1847).
    3. In the row of the newly inserted procedure, in the Reference object(s) column, click the button.
    The Select demand segment window opens.
    4. In the selection list, click the demand segment you would like to save a partial matrix for.
    5. Confirm with OK.
    The demand segment selected is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters for matrices from route volumes window opens.
    7. Make the desired changes.

    PTVGROUP

    1739

    16.3.8.5 Saving partial matrices during the execution of the procedure sequence
    Element

    Description

    Route choice Via this selection list you may decide for which of the routes the trips
    (volume) are to be saved.
    All
    If this option has been checked, all of the assigned trips will be saved
    after assignment.
    Filter for OD pairs
    If this option has been checked and the OD pair filter is active, only trips
    of active relations will be saved as traffic type matrix (see "Exception:
    Filter for OD pairs" on page 1026).
    Flow bundle
    If this option has been checked and a flow bundle is active, only the filtered trips will be saved as flow bundle matrix (see "Displaying flow
    bundles" on page 2265).
    Remaining
    matrix

    If this option has been checked, instead of the route choice trips only
    the corresponding remaining trips are saved to file which do not belong
    to the currently selected partial matrix.
    If you do not select this option, the attribute data is not saved.
    Note
    For each relation, the sum of the vehicle journeys of a route choice
    matrix and the respective remaining matrix add up to the number of
    vehicle journeys of the read-in demand matrix.

    Format

    Via the list box you can decide which data format is to be used for
    saving the partial matrix to file (see "Visum-specific matrix file formats"
    on page 2678)
    Note
    Volumes calculated with a high degree of precision should be saved to
    a matrix in binary data format (see "Round demand and volume data"
    on page 1995).

    Random
    round

    Via this option you can decide on rounding of values during saving in
    case the current number of decimal places exceeds the preset number
    of decimal places.
    If this option has been checked, values are randomly rounded up or
    down according to the particular share to be rounded. Random rounding causes the total of the values in the matrix to remain approximately constant.
    Example
    0.3 is rounded up to 1 with 30% probability and down to 0 with 70% probability.
    If this option has not been checked, the values are rounded arithmetically, i.e. decimal values up to 4 are rounded down and decimal

    1740

    PTVGROUP

    16.3.8.5 Saving partial matrices during the execution of the procedure sequence
    Element

    Description
    values 5-9 are rounded up. This applies to negative numbers, too.
    Example
    1.2 is rounded down to 1; 4.5 is rounded up to 5 and 5.5 to 6.

    Number of
    decimal places

    Number of decimal places for storage of non-integer volumes


    Note
    This option is only provided for the matrix data formats V, O, E and S.

    8. Confirm with OK.


    9. In the row of the added procedure, click in the Variant/file column.
    The icon
    10. Click the

    is displayed.
    icon.

    The Save matrix window opens.


    11. Select the desired file.
    12. Click the Save button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell in the Variant/file column and manually enter the path and file name.
    13. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The partial matrix is saved.
    Example: Demand matrix with flow bundle matrix and remaining matrix
    To the demand matrix below, a flow bundle matrix corresponds and a remaining matrix, too.
    Demand matrix
    Zone

    2000

    100

    200

    2000

    Sum

    2000

    100

    2000

    2000

    200

    Flow bundle matrix (partial matrix)

    PTVGROUP

    1741

    16.3.9 Filtering and aggregating matrix data, changing the view


    Zone

    362

    100

    200

    362

    Sum

    362

    100

    362

    362

    200

    Remaining matrix

    16.3.9

    Zone

    1638

    100

    200

    1638

    Sum

    1638

    100

    1638

    1638

    200

    Filtering and aggregating matrix data, changing the view


    In the Matrix editor window, you can specify how to show the matrix data. For instance, you
    can hide certain values or display them aggregated.
    Notes: You can also make basic settings for the display of matrix data (see "Basic settings for matrices" on page 1758).
    You can save and load the settings you make for matrix data display (see "Saving and
    loading the layout of a Matrix editor or Histogram window" on page 1747).

    16.3.9.1

    Filtering matrix data


    According to certain filter criteria, you can show or hide matrix data of Visum matrices.
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).

    Tip: You can apply pre-defined filter settings via icon


    Filter the matrix data view
    or via menu Matrix editor> Filter the matrix data view.
    2. In the Matrix editor window, on the toolbar, click the

    button Options.

    The Options window opens.


    Tip: Alternatively, from the Matrix editor menu, choose Options.
    3. In the Mode section, choose the view whose settings you want to change.

    1742

    Section

    Description

    Matrix view

    Select this option to make the settings effective in the Matrix view.

    List view

    Select this option to make the settings effective in the List view (see
    "Opening matrices in the List view" on page 1722).

    PTVGROUP

    16.3.9.1 Filtering matrix data


    4. In the Filtering section, make the desired changes.
    Section

    Description

    Filtering by
    active zones

    Select this option to show the matrix data of active zones only (see
    "Using filters to set network objects active or passive" on page 1008).
    Note
    If a main zone matrix has been opened, the labels are adjusted accordingly.

    Filtering by
    active zone
    pairs

    Select this option to show the matrix data of active OD pairs only (see
    "Exception: Filter for OD pairs" on page 1026).
    Note
    If a main zone matrix has been opened, the labels are adjusted accordingly.

    Filtering by
    matrix values

    If this option has been selected, only those matrix values are displayed which satisfy the defined filter criterion.
    From
    Smallest interval value
    To
    Greatest interval value
    Complement (Invert filter logic)
    Select this option to show all matrix intervals outside this interval.
    If you do not select this option, only matrix values inside the interval are displayed.

    Note: You can combine these filter criteria. Use the AND operator to combine filters.
    Only matrix data that meets both criteria is then shown.
    5. Confirm with OK.
    The settings are adopted for the Matrix editor window. The icon
    view appears as if pressed.

    Filter the matrix data

    Notes: Only entire rows and columns are hidden. If a matrix cell meets the filter criteria, its
    entire row and column are displayed. In the Matrix view, an entire row or column are only
    hidden if all cells of at least one matrix do not meet the filter criteria. In the List view, an
    OD pair (row) is only displayed, if all matrix cells meet the filter criteria.
    To switch off the filter, click icon
    editor> Filter the matrix data view.

    Filter the matrix data view or call menu Matrix

    For the matrix filtered, you can save the rows currently displayed (see "Saving partial
    matrices" on page 1738).

    PTVGROUP

    1743

    16.3.9.2 Showing matrix values in an aggregated form


    16.3.9.2

    Showing matrix values in an aggregated form


    You can show the matrix values of Visum matrices in an aggregated form. Here, rows and/or
    columns are summed up according to certain criteria. Thereby the data is displayed differently,
    but it is not changed.
    Notes: You can aggregate external matrices permanently (see "Aggregating or deleting
    matrix columns and rows" on page 1811).
    If you aggregate a filtered matrix, only the filtered values are aggregated.
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor window, on the toolbar, click the

    button Options.

    The Options window opens.

    Tip: Alternatively, from the Matrix editor menu, choose Options.


    3. In the Mode section, choose the view whose settings you want to change.

    1744

    Section

    Description

    Matrix view

    Select this option to make the settings effective in the Matrix view.

    List view

    Select this option to make the settings effective in the List view (see
    "Opening matrices in the List view" on page 1722).
    PTVGROUP

    16.3.9.2 Showing matrix values in an aggregated form


    4. In the Dynamic aggregation section, make the settings of your choice.
    Section

    Description

    Do not aggre- The matrix is not shown in an aggregated from.


    gate
    Aggregate
    rows and
    columns identically

    The (main) zones of the matrix are aggregated. Thereby the (main)
    zones are aggregated that have the same attribute values for the attribute selected.
    Attribute
    (Main) zone attribute by which the zones are aggregated
    Note
    In the List view, for this aggregation with an active OD or matrix value
    filter, a view might be created that is not defined by any matrix.

    Aggregate
    rows and
    columns nonidentically

    Rows and/or columns of the matrix are aggregated. Thereby the rows
    and/or columns are aggregated whose (main) zones have the same
    attribute values for the attribute selected.
    Rows
    (Main) zone attribute by which the rows are aggregated
    Columns
    (Main) zone attribute by which the columns are aggregated
    Notes
    For instance, if you only want to aggregate rows, use the (main) zone
    number as attribute for the columns.
    If you aggregate the data by an indirect attribute, you need to refresh
    Recalculate
    the matrix data after changing it. To do so, click the
    dynamically aggregated view icon, or from the Matrix editormenu,
    choose > Recalculate dynamically aggregated view.

    PTVGROUP

    1745

    16.3.9.3 Changing the matrix data view


    Section

    Description

    Function

    Computation function for aggregating matrix values


    Minimum
    The displayed value is the lowest of the aggregated matrix values.
    Maximum
    The displayed value is the highest of the aggregated matrix values.
    Average
    The displayed value is the average of the aggregated matrix values.
    Total
    The displayed value is the total of the aggregated matrix values.
    Weighted mean
    The displayed value is a mean value of the aggregated matrix values,
    with the matrix values weighted by an OD pair attribute.

    Weighting
    attribute

    This button is only enabled if the option Weighted mean has been
    selected in the Function section. Select the (main) OD pair attribute for
    weighting the values to be regarded for the calculation.

    5. Confirm with OK.


    Note: If you filter the matrix data, then the hidden data is not aggregated.
    The aggregated matrix values are shown in the Matrix editor window. An additional row and
    column show the attribute used for aggregation and the corresponding attribute values.
    Notes: You can not edit matrix values in the aggregated view.
    For dynamically aggregated matrices, you can save the rows and values currently displayed (see "Saving partial matrices" on page 1738).
    16.3.9.3

    Changing the matrix data view


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor window, on the toolbar, click the

    button Options.

    The Options window opens.


    Tip: Alternatively, from the Matrix editor menu, choose Options.
    3. In the Mode section, choose the view whose settings you want to change.

    1746

    PTVGROUP

    16.3.10 Saving and loading the layout of a Matrix editor or Histogram window
    Section

    Description

    Matrix view

    Select this option to make the settings effective in the Matrix view.

    List view

    Select this option to make the settings effective in the List view (see
    "Opening matrices in the List view" on page 1722).

    4. In the Display section, make the desired settings.


    Section

    Description

    Alignment of
    numbers

    Use the list box to set the alignment of the matrix values in the column.

    Decimal places

    Number of decimal places for matrix display on screen


    Note
    If a value smaller than the real number of decimal places is entered,
    the matrix values will be rounded arithmetically for display on screen.

    Show names
    of rows and
    columns

    Select this option to show captions at the beginning of rows and


    columns. For Visum matrices, these are the names of zones and main
    zones (see "Zones: General attributes" on page 1137 and "Main
    zones: General attributes" on page 1196).
    Tips
    Alternatively, use the shortcut menu > Show row and column labels,
    or from the Matrix editormenu, choose > Show row and column
    labels to show and hide row and column names.

    Show row and Select this option to show sums as figures at the beginning of columns
    column sums and rows.
    Tips
    Alternatively, use the shortcut menu > Show row and column totals, or
    call the menu Matrix editor> Show row and column totals to show or
    hide row and column totals.
    Note
    The option is not available in the List view.

    Note: Use the Edit > User Preferences menu to change the basic settings for opening matrices (see "Setting options for display in the Matrix window" on page 1758).
    5. Confirm with OK.
    The settings are adopted for the Matrix editor window.

    16.3.10 Saving and loading the layout of a Matrix editor or Histogram window
    You can save the following settings of a Matrix editor or Histogram window to a *.mly file and
    load the file in another window:

    PTVGROUP

    1747

    16.3.10.1 Saving the layout of a Matrix editor or Histogram window


    List of matrices
    All view options of the Matrix editor window and the column widths are set (see "Filtering
    and aggregating matrix data, changing the view" on page 1742)
    Intervals and extended parameters of the histogram window
    Note: The graphic parameters of the window are saved separately (see "Reading and
    saving the graphic parameters of the matrix window" on page 1752).
    16.3.10.1 Saving the layout of a Matrix editor or Histogram window
    1. Open a Matrix editor window or Histogram window with the matrices of your choice (see
    "Opening matrices" on page 1721 and "Showing matrices in a histogram" on page 1752).
    2. From the Matrix editor or Matrix histogram window, choose Save layout.
    The Matrix editor - Save layout window opens.
    3. Select the desired file.
    Note: Alternatively, you may enter path and file name.
    4. Click the Save button.
    5. Confirm with OK.
    The layout of the Matrix editor window is saved.
    16.3.10.2 Loading the layout of a Matrix editor or Histogram window
    1. Open a Matrix editor window or Histogram window with the matrices of your choice (see
    "Opening matrices" on page 1721 and "Showing matrices in a histogram" on page 1752).
    2. From the Matrix editor or Matrix histogram window, choose Open layout.
    The Matrix editor - Open layout window opens.
    3. Open the desired file.
    Notes: In a Matrix editor window, you can only load layout files that have been saved
    in a Matrix editor window. In a Histogram window, you can only load layout files that
    have been saved in a Histogram window.
    Alternatively, you may enter path and file name.
    4. Click the Open button.
    The Visum window appears.
    5. Make the desired changes.

    1748

    PTVGROUP

    16.3.11 Setting graphic parameters for the Matrix editor window


    Element

    Description

    Yes

    Besides the layout, information on the matrices shown are also loaded
    from the layout file.

    No

    Only the layout is loaded from the layout file. When you load the layout,
    this does not change the matrices shown.

    6. Confirm with OK.


    The layout is loaded.

    16.3.11 Setting graphic parameters for the Matrix editor window


    Similar to the network display, you can set graphic parameters for each Matrix editor window
    to arrange it according to your preferences. For instance, you can choose a classified display
    for cells or highlight the diagonals.
    In the Matrix editor window, you can specify the following settings:
    Define font color of matrix values
    Define cell background color
    You further have the following options:
    You can choose a classified display for OD pairs. To classify Visum matrices, you can use
    all (main) OD pair attributes. To classify external matrices, you can only use the matrix
    value.
    Tip: You can simply use the clipboard to copy the intervals for classification to the
    intervals in a Histogram window.
    For Visum matrices, you can show OD pairs in a different color.
    You can also show the diagonals in a different color.
    Note: You can save the graphic parameters to a *.gpm file to use them again later (see
    "Reading and saving the graphic parameters of the matrix window" on page 1752).
    16.3.11.1 Setting the graphic parameters for active OD pairs
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    3. In the navigator, select the Active OD pairs > Display entry.
    4. Make the desired changes.

    PTVGROUP

    1749

    16.3.11.1 Setting the graphic parameters for active OD pairs


    Element

    Description

    Uniform display

    If the option has been selected, all active relations are drawn consistently. In the Display section, select the appropriate colors for
    background and text display.

    Classified display If the option has been selected, the active relations can be classified and displayed by an attribute (see "Displaying classified
    objects based on attribute values" on page 2411).
    Tip
    Via the buttons in the Active OD pairs tab you can read previously defined classes for classified graphical display from file
    (see "Reading classes from file for value classification" on page
    1750).

    Note: Click the Preview button to immediately show your changes without closing the
    Edit graphic parameters window.
    5. Confirm with OK.
    The particular matrix values are displayed in the specified colors.
    Reading classes from file for value classification
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    3. In the navigator, select the Active OD pairs entry.
    4. Click the desired button.
    Element

    Description

    Read clasVia this button you can read classes which were previously
    sification from clip- copied to the clipboard from the histogram settings, for example
    board
    (see "Showing matrices in a histogram" on page 1752).
    Read clasVia this button you can read previously defined classes which
    sification from file were stored as attribute file (see "Saving intervals to an attribute
    file" on page 1756).
    The classes are imported.
    5. In the navigator, select the Active OD pairs > Display entry.
    6. Make the required changes.

    1750

    PTVGROUP

    16.3.11.2 Setting the graphic parameters for passive OD pairs


    16.3.11.2 Setting the graphic parameters for passive OD pairs
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    3. In the navigator, select the Passive OD pairs entry.
    4. Make the desired changes.
    Element

    Description

    Background color Background color of cells with passive OD pairs


    Font color

    Font color of cells with passive OD pairs

    Note: Click the Preview button to immediately show your changes without closing the
    Edit graphic parameters window.
    5. Confirm with OK.
    The particular matrix values are displayed in the specified colors.
    16.3.11.3 Setting the graphic parameters for the matrix diagonal
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    3. In the navigator, select the Diagonal elements entry.
    4. Make the desired changes.
    Element

    Description

    Separate display

    If this option has been selected, the display of the cells in the diagonal differs from the display of the cells in the upper and lower triangles.

    Background color Background color of the matrix diagonal rows


    Font color

    Font color of matrix diagonal rows

    Note: Click the Preview button, to immediately show your changes without closing the
    Edit graphic parameters window.
    5. Confirm with OK.

    PTVGROUP

    1751

    16.3.11.4 Resetting the matrix window graphic parameters


    In the selected matrix window, the particular matrix values are displayed with the selected
    colors.
    16.3.11.4 Resetting the matrix window graphic parameters
    The graphic parameters set up for a matrix window can be reset to the default settings.
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor menu, select the Reset graphic parameters entry.
    The graphic parameters are initialized.

    16.3.12 Reading and saving the graphic parameters of the matrix window
    Notes: The graphic parameters of the matrix window are saved to a *.gpm file.
    Other display options can be saved with the layout (see "Saving and loading the layout of
    a Matrix editor or Histogram window" on page 1747).
    16.3.12.1 Saving the matrix window graphic parameters
    1. Edit the graphic parameters as desired (see "Setting graphic parameters for the Matrix editor window" on page 1749).
    2. In the Matrix editor menu, select the Save graphic parameters entry.
    The Save: Matrix editor graphics parameters window opens.
    3. Enter the desired file name and path, if required.
    4. Click the Save button.
    The graphic parameters of the matrix window are saved.
    16.3.12.2 Reading the matrix window graphic parameters
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix editor menu, select the Open graphic parameters entry.
    The Open: Matrix editor graphics parameters window opens.
    3. Open the desired file.
    4. Confirm with Open.
    The graphic parameters of the matrix window are saved.

    16.3.13 Showing matrices in a histogram


    You can show the matrix values of one or several matrices with the same OD pairs in a histogram. From the histogram you can see the distribution of the matrix values to certain classes.
    The classes can be defined for the currently displayed matrix or on the basis of another matrix.

    1752

    PTVGROUP

    16.3.13.1 Create histogram


    16.3.13.1 Create histogram
    1. In the Matrices window, in the navigator, select the matrices of your choice.
    2. Right-click one of the matrices you selected.
    The shortcut menu opens.
    3. Choose Create histogram.

    Tip: Alternatively, on the tab toolbar, click the


    Create histogram icon. You will
    also find both options in the Matrices list (see "Opening a list" on page 2299).
    The Matrix histogram (Matrix <Matrix name> window opens.
    Note: If you select several matrices, instead of the matrix name, the number of the
    matrices selected is displayed.
    4. Click the

    Insert new intervals icon.

    Tip: Alternatively, from the Matrix histogram menu, choose Insert new intervals.
    The Add intervals window opens.
    5. Make the desired changes.
    Element

    Description

    Lower limit

    Lowest interval value


    Note
    The lower limit is not included in the interval.

    Upper limit

    Highest interval value


    Note
    The upper limit is part of the interval.

    Number of intervals

    The number of intervals

    Note: By default, the OD pairs in the matrices selected are classified according to their
    matrix values. However, you can also perform classification using the matrix values of
    another matrix. To do so, click the button
    Options, or from the Matrix histogram
    menu, choose > Options (see "Classifying a histogram on the basis of another matrix"
    on page 1755).
    6. Confirm with OK.
    The intervals are added to the bottom section of the window.
    PTVGROUP

    1753

    16.3.13.1 Create histogram

    Tips: Alternatively, click the button


    Open intervals to import the intervals from an
    attribute file *.att (see "Importing and exporting list contents" on page 2325).
    A further option: Copy the intervals from another Histogram window. To do so, in the
    other Histogram window, click the
    the

    Copy intervals to clipboard icon. Then click

    Paste intervals from clipboard icon to paste the intervals.

    7. You can then edit the intervals, if required.


    Notes: To edit the interval limits, double-click them. The lower limit is not included in
    the interval, the upper limit is part of the interval (a<xb).
    To delete highlighted intervals, on the Histogram window toolbar, click the
    marked intervals button.

    Delete

    As long as the classification has not been recalculated, edited intervals are labeled in
    brown.
    8. Click the

    Recalculate classification icon.

    Tip: Alternatively, from the Matrix histogram menu, choose Recalculate classification.
    The histogram is then shown in the top section of the window. The values calculated are displayed in the list. The LastShare column contains values of the last calculation.

    1754

    PTVGROUP

    16.3.13.2 Classifying a histogram on the basis of another matrix

    Notes: Use the


    Select matrices icon to edit the displayed matrices in this window
    (see "Managing matrices in the Matrix window or Histogram window" on page 1724).
    The histogram settings can be saved as a layout file (see "Saving and loading the layout
    of a Matrix editor or Histogram window" on page 1747). You can save the intervals to a
    *.att file (see "Saving intervals to an attribute file" on page 1756).
    If you change matrix values in the selected matrices, the histogram view is automatically
    refreshed.
    If you change intervals after calculating the histogram, the view is not automatically refreshed. The columns are displayed in grey, the values calculated are shown in brown. To
    refresh the view of the histogram, click the

    Recalculate classification icon.

    16.3.13.2 Classifying a histogram on the basis of another matrix


    You can classify the classes in a histogram according to the values of another matrix. For
    instance, you can display in this way, how the trips of a demand matrix spread across the journey distances. For that purpose, display the demand matrix data in the histogram in a classified view according to a skim matrix which represents the journey distances.
    1. Make sure that the histogram is open (see "Create histogram" on page 1753).
    2. Click the

    Edit optionsicon.

    The Options matrix histogram window opens.


    3. Select the Use classification matrix option.
    4. In the navigator, select the matrix you would like to classify.
    5. Confirm with OK.
    6. Set the desired intervals.
    7. Click the

    Recalculate classification icon.

    Tip: Alternatively, from the Matrix histogram menu, choose Recalculate classification.
    The histogram is then shown in the top section of the window.
    16.3.13.3 Changing the number of decimal places in intervals
    1. Make sure that the histogram is open (see "Create histogram" on page 1753).
    2. Click the

    Edit options icon.

    The Options matrix histogram window opens.


    3. In the Decimal places for intervals field, enter the value of your choice.
    4. Confirm with OK.

    PTVGROUP

    1755

    16.3.13.4 Saving intervals to an attribute file


    The change is stored.
    16.3.13.4 Saving intervals to an attribute file
    1. Make sure that you have defined intervals in the histogram (see "Create histogram" on
    page 1753).
    2. Click the

    Save intervals button.

    The Save intervals window opens.


    Tip: Alternatively, click menu Matrix histogram > Save intervals.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The Select matrix window opens.
    5. From the list, select the matrices whose calculated attribute values you would like to save to
    file.
    The Save attributes (distribution intervals) window opens.
    6. In the Separator list, click the entry of your choice.
    Note: To load the attribute file, you need to select the semicolon or tabulator as separator.
    7. Confirm with OK.
    The attribute file is saved.

    16.3.14 Comparing two matrices in a scatter plot


    In a scatter plot, you can compare the matrix values of two matrices that have the same OD
    pairs.
    1. Press the CTRL key and keep it pressed.
    2. In the Matrices window, in the navigator, select the matrices of your choice.
    3. Right-click one of the matrices you selected.
    The context menu opens.
    4. Click Comparison in pairs.
    The Matrix comparison window opens. The matrix values of both matrices are displayed in a
    scatter diagram. The matrix that was selected first is displayed along the X-axis, whereas the
    other one is displayed along the Y-axis. A blue line indicates the diagonal, a red line depicts
    the best straight line. Statistical values are displayed in the lower section to the right: the
    regression line equation in the form of a x + b, the coefficient of determination r2 and the number of matrix values n.

    1756

    PTVGROUP

    16.3.15 Deleting Visum matrices

    Notes: If the matrices are extremely large, the points are no longer displayed separately,
    but in a grid view. An additional legend indicates what the different levels of grey represent.
    In the Matrix comparison window, you can make the view either bigger or smaller, you
    can shift the image and recall the initial view. These functions correspond to those in the
    Network editor . To access them, in the View menu, on the toolbar, click the corresponding buttons or use the wheel button (see "Network editor window" on page 818).
    You can also export a matrix comparison as a graphic file. To do so, from the Matrix comparison menu, choose one of the following commands:
    JPG export (Screenshot) (see "Exporting screenshots" on page 2663),
    SVG export (see "SVG export" on page 2656),
    DXF export (see "DXF export" on page 2654).

    16.3.15 Deleting Visum matrices


    You can delete Visum matrices
    1. In the Matrices window, in the navigator, select the matrices of your choice.
    2. Right-click one of the matrices you selected.
    The shortcut menu opens.
    3. Select the Delete entry.

    PTVGROUP

    1757

    16.3.16 Basic settings for matrices


    Tip: Alternatively, in the window, select the matrices. Then on the toolbar, click the
    Delete button
    . You will also find both options in the Matrices list (see "Opening a
    list" on page 2299).
    A query opens.
    Note: If you delete a Visum matrix that contains a reference to another demand object,
    Visum deletes the reference as well.
    4. Confirm the query with Yes.
    The matrices are deleted.

    16.3.16 Basic settings for matrices


    You can make some basic settings for matrices.
    16.3.16.1 Setting options for display in the Matrix window
    You can specify the font of matrix values and whether you want to show the sum or the name
    per row and column.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, click GUI> Matrix editor.
    3. Make the desired settings.
    Element

    Description

    Font for matrix Select font


    editor and
    Use this button to select a font, font size and style for all Matrix winhistogram
    dows.
    Notes
    Your settings are applied to all Matrix and Histogram windows opened.
    You can reset the font to the Visum standard setting (see "Resetting
    fonts" on page 828).
    Defaults for
    display in the
    matrix editor

    1758

    Number of decimal places


    Number of decimal places used to show matrix values when a matrix
    is opened.
    Note
    If a value smaller than the real number of decimal places is entered,
    the matrix values will be rounded arithmetically for display on screen.
    Show row and column labels

    PTVGROUP

    16.3.16.2 Specifying treatment of division by zero


    Element

    Description
    Select this option to show captions at the beginning of rows and
    columns. For Visum matrices, these are the names of zones and main
    zones (see "Zones: General attributes" on page 1137 and "Main
    zones: General attributes" on page 1196).
    Show row and column sums
    Select this option to show sums as figures at the beginning of
    columns and rows.
    Note
    The setting is only applied to matrix windows that are subsequently
    opened.

    4. Confirm with OK.


    The settings are applied.
    16.3.16.2 Specifying treatment of division by zero
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, click GUI> Matrix editor.
    3. In the Behavior of arithmetic operations section, make the desired changes.
    Element

    Description

    0/0

    Default result to be used if a matrix value 0 is divided by 0.

    Pos / 0

    Default result to be used if a matrix value > 0 is divided by 0.

    Neg / 0

    Default result to be used if a matrix value < 0 is divided by 0.

    4. Confirm with OK.


    The settings are applied.
    16.3.16.3 Specifying a default value for new relations
    You can specify a default value that is used for new relations in matrices (see "Extending external matrices during an arithmetic operation" on page 1810).
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, click GUI > Matrix editor.
    3. In the Default for new OD pairs field, enter the desired value.
    4. Confirm with OK.
    The settings are applied.

    PTVGROUP

    1759

    16.3.16.4 Specifying settings for treatment of matrices

    Note: When you expand matrices with different formats, we recommend that you set the
    default value 0, as otherwise the column and row sums are changed through the new OD
    pairs.
    16.3.16.4 Specifying settings for treatment of matrices
    Skim matrices and demand matrices are loaded to the RAM when you access them. To prevent the RAM from matrix data overflow, define a maximum data volume for matrices in the
    RAM. If the matrices loaded exceed this volume, the matrix least used is saved to a swap file.
    Tip: You can also specify whether matrices are automatically loaded into the RAM when
    you open a version file, or only when they are needed (see "How to handle matrix data
    when opening or saving a version file" on page 843).
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Files & Protocols> Matrices.
    Element

    Description

    Activate swap file If this option has been checked, loaded matrices will be saved to
    a swap file as soon as the maximum size defined for working
    RAM will be exceeded.
    Via the
    icon you select the directory for the swap file.
    Notes
    We recommend that you select this option.
    If the maximum RAM volume reserved is not large enough, this
    might slow Visum down a little.
    Maximum size of Maximum share of the working storage to be used by loaded
    matrix data stored matrices.
    in RAM
    Notes
    By default, 25% of the working memory is selected.
    In case of giant networks you should reduce this value. Thus you
    provide more RAM for other files.
    Set to default
    values

    Via this button you set the RAM share to be used by loaded matrices to 25% of the working storage.

    3. Confirm with OK.


    The settings are applied.

    1760

    PTVGROUP

    16.3.16.5 Settings for Reading matrix from file in $O format


    16.3.16.5 Settings for Reading matrix from file in $O format
    In matrices in the $O-Format (see "Format $O" on page 2682), (main) OD pairs might occur
    multiple times. Thus, there are several matrix values for these (main) OD pairs. You can specify how you want to treat the matrix values when they are imported.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Files & Protocols> Matrices.
    3. Specify how you want to treat multiply occurring (main) OD pairs in matrices with an $O format.
    Element

    Description

    Sum up all values Select this option to add all values of the same (main) OD pair up
    of a (main) OD pair to a single matrix value.
    Use last value per Select this option to use the last (main) OD pair imported as the
    (main) OD pair
    matrix value.
    4. Confirm with OK.
    The settings are applied.

    16.4

    Editing matrix values


    Visum provides several basic functions for editing matrix values.
    Notes: For arithmetic operations you may not mix zone matrices and main zone matrices,
    since they have different dimensions.
    You cannot edit matrix values in formula matrices. However, you can edit the formula
    (see "Editing formula matrices" on page 1730).
    Marking matrix data
    Editing matrix values interactively
    Replacing matrix values
    Copying and pasting matrix values
    Copying and pasting matrix diagonal values
    Importing matrix values during execution of the procedure sequence
    Reflecting the upper triangle of a matrix
    Reflecting the lower triangle of a matrix
    Transposing the matrix values
    Editing matrix values using a log file during the procedure sequence run

    16.4.1

    Marking matrix data


    You can use some of the matrix editing functions to edit the selected matrix data. To do so,
    highlight the rows with the matrix values you want to change.

    PTVGROUP

    1761

    16.4.1.1 Finding cells


    16.4.1.1

    Finding cells
    In the open matrix, you can find individual values; search for a pair of zones or main zones.
    1. On the toolbar of the open matrix, click the

    Find a matrix cell icon.

    The Find matrix cell window opens.


    2. Select the search criterion in the upper selection list of the window.
    3. In the two selection lists below, select the OD pair or the pair of main zones whose matrix
    cell you would like to find.
    4. Click the Close button.
    The cell is highlighted.
    16.4.1.2

    Selecting cells using the mouse


    Selecting a single cell
    Left-click the desired cell.
    The cell is highlighted.

    Selecting several cells in any order desired


    To select several cells in any order desired, press the C TRL key and left-click the desired
    cells one after the other.
    The cells are highlighted.
    Selecting several cells in consecutive order
    To select several cells in consecutive order, left-click the first cell of your choice. Then keep
    the mouse-button held down and move the mouse pointer over the other cells you want to
    highlight.
    Tip: Alternatively, press the SHIFT key to highlight consecutive cell sections. With the
    mouse button, click in the first cell that you want to mark, press the SHIFT key and click
    in the last cell that you want to mark.
    The cells are highlighted.
    Highlighting single rows or columns
    Click the header of the row or column that you want to mark.
    The section is marked.
    Marking several rows or columns in any desired order
    Press the CTRL key and left-click the headers of the desired rows or columns one by one.
    The rows or columns are marked.

    1762

    PTVGROUP

    16.4.1.3 Selecting cells using the keyboard


    Marking several consecutive rows or columns
    1. Click the header of the first row or column that you want to mark.
    2. Hold down the SHIFT key.
    3. Click the last row or column that you want to mark.
    The section between the first and the last of the clicked rows or columns is marked.
    Selecting all cells
    In the Matrix window, click the top left cell.
    The cells are highlighted.
    16.4.1.3

    Selecting cells using the keyboard


    Alternatively, you can use the keyboard to highlight several consecutive cells, rows or
    columns.
    In the matrix, select one or more cells, rows, or columns.

    16.4.2

    Hotkeys

    Description

    SHIFT + arrow keys

    Press the SHIFT key and the appropriate arrow key simultaneously
    to extend the currently selected section towards the particular
    direction, or reduce it, as applicable.

    SHIFT + POS 1

    Press SHIFT + POS1 to select all cells to the left of the selected
    cells.

    SHIFT + END

    Press SHIFT + END to select all cells to the right of the selected
    cells.

    SHIFT + PUP

    Press SHIFT + PUP to select all cells above the selected cells.

    SHIFT + PDN

    Press SHIFT + PDOWN to select all cells below the selected cells.

    CTRL + A

    Press CTRL + A to select all cells.

    Editing matrix values interactively


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Highlight one or several matrix values of your choice (see "Marking matrix data" on page
    1761).
    3. Enter the new matrix value.
    4. Press the ENTER key.
    The highlighted matrix values are changed.
    Tip: Alternatively, use the context menu to change matrix values (see "Replacing selected matrix values" on page 1765).

    PTVGROUP

    1763

    16.4.3 Replacing matrix values

    16.4.3

    Replacing matrix values


    You can replace either the selected or all matrix values of one matrix or several matrices in
    three ways: either by a constant value or by a value taken from either another matrix or a zone
    attribute.

    16.4.3.1

    Replacing all matrix values


    1. Open a Matrix editor window with the matrices of your choice (see "Opening matrices" on
    page 1721).
    2. Click the

    Set value(s) icon.

    The Select the operand for 'Set value(s)... on the total matrix window opens.
    3. Make the desired changes.
    Element

    Description

    Select matrix

    Select this option to replace the matrix values by the values of a matrix
    listed in the navigator.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to replace the matrix values by the values of a zone
    attribute.
    Origin
    Select this entry to replace the matrix value of each OD pair ij by the
    attribute value of the origin zone i.
    Destination
    Select this entry to replace the matrix value of each OD pair ij by the
    attribute value of the destination zone j.
    Note
    This function is provided for Visum matrices only.
    Load matrix
    from file

    Select this option to replace the matrix values with the values of an

    Constant

    Select this option to replace your matrix data by a constant. Enter the
    constant into the input field (see "Replacing all matrix values" on page
    1764).

    external matrix. Click the


    choice.

    button to select the matrix file of your

    4. Confirm with OK.


    The matrix values are replaced.

    1764

    PTVGROUP

    16.4.3.2 Replacing selected matrix values

    Note: To set all matrix values to null, on the Matrix window toolbar, click the
    Initialize
    matrix button. Alternatively, select Matrix editor> Initialize matrix.
    If you select one or several matrices as operands, the number of zones and the zone
    numbers do not have to be identical with those of the matrices in the Matrix window. Arithmetic operations, however, are only performed on matrix values with identical OD pairs. If
    the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix as operand that does not have an OD pair, the matrix value
    null is used.
    OD pairs that are not shown in the Matrix window will not be taken into account.
    16.4.3.2

    Replacing selected matrix values


    1. Open a Matrix editor window with the matrices of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click the Matrix window.
    A shortcut menu opens.
    4. Select Arithmetic operations on marked section> Allocate value(s).
    The Select the operand for 'Set value(s)... in the selected section window opens.
    5. Make the desired settings (see "Replacing all matrix values" on page 1764).
    6. Confirm with OK.
    The selected matrix values are changed.
    Tip: Alternatively, enter matrix values manually (see "Editing matrix values interactively"
    on page 1763).

    16.4.3.3

    Replacing the matrix diagonal


    You can replace the current values in the matrix diagonal. The diagonal includes all cells
    whose row number and column number correspond with each other. You can either replace
    the values by a constant or by the values of another matrix or zone attribute. The matrix values
    of all other rows remain unchanged (see Fundamentals: Chpt. 4.3.5 , page 201).
    Note: Use the keys ALT + PGUP / PGDOWN to scroll along the diagonal in the matrix
    values.
    1. Open the desired matrix (see "Opening matrices" on page 1721).
    2. On the Matrix window toolbar, click the

    Set diagonal button.

    The Select the operand for 'Set diagonal... on the total matrix window opens.

    PTVGROUP

    1765

    16.4.3.4 Replacing selected values in the matrix diagonal


    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations> Set
    diagonal.
    3. Make the desired changes.
    Element

    Description

    Select matrix

    Select this option to replace the matrix values in the diagonal by the
    values of a matrix listed in the navigator.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to replace the matrix values by zone attribute values.
    Note
    This function is provided for Visum matrices only.
    Load matrix
    from file

    Select this option to replace the matrix values by the values of an exter-

    Constant

    If this option is selected, you can replace the matrix values by a constant value. Enter the constant into the entry field.
    Note
    If you enter 0 as a constant value for the diagonal, the output matrix
    corresponds to the input matrix, however, without the zone-internal
    demand.

    nal matrix. Click the

    button to select the matrix file of your choice.

    4. Confirm with OK.


    In the matrix diagonal, the values are replaced.
    16.4.3.4

    Replacing selected values in the matrix diagonal


    Note: Use the keys ALT + PGUP / PGDOWN to scroll along the diagonal in the matrix
    values.
    1. Open the desired matrix (see "Opening matrices" on page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click the Matrix window.
    A shortcut menu opens.
    4. Select Arithmetic operations on marked section> Set diagonal.
    The Select the operand for 'Set diagonal... on the marked section window opens.
    5. Make the desired settings (see "Replacing the matrix diagonal" on page 1765).
    6. Confirm with OK.
    In the diagonal, the selected matrix values are replaced.

    1766

    PTVGROUP

    16.4.3.5 Setting new matrix values based on a condition


    16.4.3.5

    Setting new matrix values based on a condition


    You can use a filter to divide the matrix values into two groups. Then you can replace their
    values with different values.
    1. Make sure that you have opened the desired matrices (see "Opening matrices" on page
    1721).
    2. On the Matrix window toolbar, click the

    Set values conditionally button.

    Tip: Alternatively, you can select menu Matrix editor > Arithmetic operations> Set
    values conditionally.
    The Set values conditionally window opens.
    3. Enter the desired data.
    Element

    Description

    From

    Lower filter threshold


    Values < threshold do not belong to the interval. Whether the threshold
    belongs to the interval or not depends on activation of the Interval
    limits included option.
    Note
    Negative values are permitted, empty entries are not permitted.

    To

    Upper threshold of the filter


    Values > threshold do not belong to the interval. Whether the threshold
    belongs to the interval or not depends on activation of the Interval
    limits included option.
    Note
    Negative values are permitted, empty entries are not permitted.

    Interval limits Select this option to include the threshold values in the interval.
    included
    Within interval

    New value for all matrix values that lie within the interval
    Note
    If you do not make an entry, the matrix values within the interval are not
    overwritten.

    Outside of
    interval

    New value for all matrix values that lie outside the interval
    Note
    If you do not make an entry, the matrix values outside the interval are
    not overwritten.

    4. Confirm with OK.


    The matrix values are modified according to the settings.

    PTVGROUP

    1767

    16.4.3.6 Setting matrix values of several matrices to null


    16.4.3.6

    Setting matrix values of several matrices to null


    1. In the Matrices window, in the navigator, select the matrices of your choice.
    2. Right-click one of the matrices you selected.
    The shortcut menu opens.
    3. Click Initialize.
    Tip: On the Matrix window toolbar, click the
    the Matrix window to null.

    Initialize button to set all matrix values in

    The matrix values of the matrices selected are set to null.


    16.4.3.7

    Importing matrix values into Visum matrices


    1. In the Matrices window, in the navigator, right-click the Visum matrix of your choice.
    The shortcut menu opens.
    2. Click Open from file.
    The Open matrix window opens.
    Note: A file name is suggested if the matrix has previously been assigned a name.
    3. Select the desired file.
    4. Click the Open button.
    The matrix values are overwritten. The name of the file selected is saved with the matrix.
    Tips: Alternatively, you can read values from file into a Visum matrix as follows: Open the
    Visum matrix and in the tool bar of the matrix window and click the
    Read matrix content from file button or select menu Matrix editor> Open from file. The Matrices list context menu contains an entry for this (see "Opening a list" on page 2299).
    Note: The number of zones and the zone numbers in the imported matrix do not have to
    be identical with those in the Visum matrix you selected. Arithmetic operations, however,
    are only performed on matrix values with identical OD pairs. If the matrices do not have
    identical OD pairs, the following applies:
    If the matrix file does not contain an OD pair, the matrix value null is used.
    Any OD pairs that are not in the Visum file, will not be taken into account.

    16.4.4

    Copying and pasting matrix values


    You can copy matrix values and paste them into another matrix or another position in the
    same matrix. Thereby, OD pairs are not accounted for.

    1768

    PTVGROUP

    16.4.4.1 Copying and pasting a matrix


    16.4.4.1

    Copying and pasting a matrix


    1. Open the desired matrix (see "Opening matrices" on page 1721).
    2. Click the

    Export of the current view to the clipboard icon.

    Tip: Alternatively, from the Matrix editor menu, choose Export of the current view to
    the Clipboard.
    The matrix is copied to the Clipboard.
    3. Open the matrix that you want to paste the copied values into (see "Opening matrices" on
    page 1721).
    4. Right-click the top left corner of the desired section.
    Note: The matrix section on the right, under the selected cell, must have at least the
    same size as the copied matrix.
    The shortcut menu opens.
    5. Select Paste cells.
    The values copied are pasted into the cells, independent of their OD relation.
    16.4.4.2

    Exchanging matrix values between opened matrices


    You can copy individual values, matrix sections, columns or rows to the Clipboard and paste
    them into another matrix or another position in the same matrix.
    1. Open a Matrix editor window with the matrices of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    Note: The highlighted cells must be adjacent to each other.
    3. Press CTRL + C.
    Tip: Alternatively, from the shortcut menu, choose Copy cells.
    The highlighted values are copied to the Clipboard.
    4. Open the matrix to which you want to paste the copied values, if applicable (see "Opening
    matrices" on page 1721).
    5. In the matrix, highlight the desired Paste position.
    Note: The relative position of the copied values in rows and columns is adopted. So
    when copying several cells, simply copy the top left cell of the Paste section.

    PTVGROUP

    1769

    16.4.5 Copying and pasting matrix diagonal values


    6. Press CTRL + V.
    Tip: Alternatively, from the shortcut menu, choose Paste cells.
    The values copied are pasted into the cells, independent of their OD relation.

    16.4.5

    Copying and pasting matrix diagonal values


    The values in the diagonal can be exchanged between Visum matrices.
    Note: Use the keys ALT + PGUP / PGDOWN to scroll along the diagonal in the matrix
    values.
    1. Open a matrix window with the desired matrices (see "Opening matrices" on page 1721).
    2. Mark the columns and rows with the appropriate values.
    3. Right-click the marked section.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Copy the diagonal to the clipboard.
    The diagonal values are copied to the clipboard.
    5. Open the matrix that you want to paste the copied values into.
    6. Mark the columns and rows whose diagonal values you want to overwrite.
    7. Right-click in the matrix.
    The shortcut menu opens.
    8. Select Arithmetic operations on marked section> Paste the diagonal from the clipboard.
    The copied data is stored in the appropriate cells of the diagonal. Visum replaces each value
    by the value derived from the same OD pair.

    16.4.6

    Importing matrix values during execution of the procedure sequence


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Open matrix procedure
    of the Matrices category (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Click the Visum matrix for which you want to import values.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    1770

    PTVGROUP

    16.4.7 Exporting matrix values to a database


    6. In the row of the added procedure, click in the Variant/file column.
    The icon
    7. Click the

    is displayed.
    icon.

    The Open matrix window opens.


    8. Select the desired file.
    Note: You can also select matrices with an external data format, for example EMME/2
    or TModel (see "EMME/2 import" on page 2587 and "TModel import" on page 2592).
    9. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell in the Variant/file column and manually enter the path and file name.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    To the matrix, values of the selected matrix file are assigned.
    Note: The number of zones and the zone numbers in the imported matrix do not have to
    be identical with those in the Visum matrix you selected. Arithmetic operations, however,
    are only performed on matrix values with identical OD pairs. If the matrices do not have
    identical OD pairs, the following applies:
    If the matrix file does not contain an OD pair, the matrix value null is used.
    Any OD pairs that are not in the Visum file, will not be taken into account.

    16.4.7

    Exporting matrix values to a database


    You can save a matrix in a database.
    1. On the toolbar, click the

    Export current view to database icon.

    A query opens.
    2. Select the desired database format.
    3. Confirm with OK.
    Another window opens. Further proceedings depend on the format which you have chosen.
    16.4.7.1

    Exporting matrix to an access database


    1. Select the option MS Access 2003 or earlier or MS Access 2007 or up.
    The Save Access 2007 database window opens.

    PTVGROUP

    1771

    16.4.7.2 Exporting matrix values to an SQL database


    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The matrix values for the current matrix view are stored in the database where you can edit
    them.
    16.4.7.2

    Exporting matrix values to an SQL database


    1. Select the MS SQL server option.
    The Data link properties window opens.
    2. Make sure that the Provider tab is selected.
    3. In the list, select a suitable provider, for example Microsoft OLE DB Provider for SQL Server.
    4. Click Next.
    The Connection tab is displayed.
    5. Enter a Server name or select a name in the list.
    6. Under User name, enter a name for the access to the SQL server.
    7. Under User name, enter a password for the access to the SQL server.
    8. Select the Allow saving of password option.
    9. Under topic 3, select a database from the list.
    10. If required, check the connection to the server by clicking the Check connection button.
    11. Confirm with OK.
    The matrix values for the current matrix view are stored in the database where you can edit
    them.

    16.4.8

    Reflecting the upper triangle of a matrix


    You can reflect the values in the matrix section above the diagonal to the section below the diagonal (see Fundamentals: Chpt. 4.3.4 , page 201). There are two options to do so:
    Reflecting the upper triangle in the matrix window
    Reflecting the upper triangle in the procedure sequence

    16.4.8.1

    Reflecting the upper triangle in the matrix window


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Reflect upper triangle icon.

    Tip: Alternatively, select menu Matrix editor > Arithmetic operations> Reflect
    upper triangle.

    1772

    PTVGROUP

    16.4.8.2 Reflecting the upper triangle in the procedure sequence


    The matrix values of the section above the diagonal are copied to the lower triangle of the
    matrix.
    16.4.8.2

    Reflecting the upper triangle in the procedure sequence


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix whose upper triangle you would like to reflect.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    7. Select option Reflect upper triangle.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The matrix values of the section above the diagonal are copied to the lower triangle of the
    matrix.

    16.4.9

    Reflecting the lower triangle of a matrix


    You can reflect the values in the matrix section below the diagonal to the section above the diagonal (see Fundamentals: Chpt. 4.3.4 , page 201). There are two options to do so:
    Reflecting the lower triangle in the Matrix window
    Reflecting the lower triangle during the procedure sequence run

    16.4.9.1

    Reflecting the lower triangle in the Matrix window


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Reflect lower triangle icon.

    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Reflect lower triangle.

    PTVGROUP

    1773

    16.4.9.2 Reflecting the lower triangle during the procedure sequence run
    The matrix values of the section below the diagonal are copied to the upper triangle of the
    matrix.
    16.4.9.2

    Reflecting the lower triangle during the procedure sequence run


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix whose lower triangle you would like to reflect.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    7. Select option Reflect lower triangle.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The matrix values of the section below the diagonal are copied to the upper triangle of the
    matrix.

    16.4.10 Transposing the matrix values


    In a square matrix, you can exchange rows for columns and vice versa. This is called transposing. This way, you may, for example, generate a matrix for the out-going demand from a
    matrix describing the in-coming demand (see Fundamentals: Chpt. 4.3.4 , page 201).
    There are two ways of transposing matrix values:
    Transposing matrix values in a Matrix window
    Transposing matrix values during the procedure sequence
    16.4.10.1 Transposing matrix values in a Matrix window
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    1774

    Transpose button.

    PTVGROUP

    16.4.10.2 Transposing matrix values during the procedure sequence


    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Transpose.
    The matrix values are transposed.
    Tip: A further option: You can also transpose matrix values during the procedure
    sequence run (see "Transposing matrix values during the procedure sequence" on page
    1775).
    16.4.10.2 Transposing matrix values during the procedure sequence
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix whose values you would like to transpose.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    7. Check option Transpose.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    During the procedure sequence, the matrix values are transposed according to the specified
    order of procedures.

    16.4.11 Editing matrix values using a log file during the procedure sequence run
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Edit matrix procedure
    of the Matrices category (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.

    PTVGROUP

    1775

    16.5 Using matrix values for calculations


    The Select matrix window opens.
    4. Select the desired matrix.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. In the row of the added procedure, click in the Variant/file column.
    The icon
    7. Click the

    is displayed.
    icon.

    The Open MUULI Log file window opens.


    8. Select the desired file.
    9. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell in the Variant/file column and manually enter the path and file name.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The matrix values are changed.

    16.5

    Using matrix values for calculations


    You can use matrix values in several arithmetic operations.
    Rounding matrix values
    Adding up matrix values
    Subtracting matrix values
    Multiplying matrix values
    Dividing matrix values
    Forming the reciprocal of matrix values
    Raise to power
    Take logarithm
    Exponential function
    Replacing matrix data by a maximum value
    Replacing matrix data by a minimum value
    Symmetrizing a matrix
    Combining matrices and attribute vectors
    Projecting matrix values
    Projecting matrix values by territory
    Calculating a main zone matrix from a zone matrix
    Calculating a zone matrix from a main zone matrix

    1776

    PTVGROUP

    16.5.1 Rounding matrix values


    Notes: For arithmetic operations you may not mix zone matrices and main zone matrices,
    since they have different dimensions.
    You cannot edit matrix values in formula matrices. However, you can edit the formula
    (see "Editing formula matrices" on page 1730).

    16.5.1

    Rounding matrix values


    You can use mercantile rounding for the matrix values. The matrix values are then rounded up
    or down to 2 digits after the decimal point, so that the new value is a multiple of the value rounded.
    Original matrix value

    Value that was roun- Rounding result


    ded

    123.27

    0.1

    123.30

    123.27

    123.00

    123.27

    10

    120.00

    123.27

    0.25

    123.25

    1. Open a Matrix editor window with the matrices of your choice (see "Opening matrices" on
    page 1721).
    2. Click the

    Round icon.

    The window Select the operand for Round... on total matrix opens.
    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Round.
    3. Enter the value you want to round to.
    4. Confirm with OK.
    The matrix values are rounded.

    16.5.2

    Adding up matrix values


    You can add a constant or values of other matrices or zone attribute values to some or all of
    your matrix values.

    16.5.2.1

    Add values to whole matrix


    Note: Click the Combination of matrices and vectors function to start the calculation
    during the procedure sequence run (see "Combining matrices and attribute vectors
    during the procedure sequence run" on page 1799).
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).

    PTVGROUP

    1777

    16.5.2.1 Add values to whole matrix

    2. On the Matrix window toolbar, click the

    symbol Add.

    The Select the operand for 'Add... on the total matrix window opens.

    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations> Add.
    3. Make the desired changes.
    Element

    Description

    Select matrices

    Select this option to add the values of one or several matrices (in the
    navigator) to your matrix values.
    Tips
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to add zone attribute values to your matrix data.
    Origin
    Select this option to add the matrix value of each OD pair ij to the attribute value of the origin zone i.
    Destination
    Select this option to add the matrix value of each OD pair ij to the attribute value of the destination zone i.
    Note
    This function is provided for Visum matrices only.

    1778

    Load matrix
    from file

    Select this option to add the values of an external matrix to your matrix

    Constant

    Select this option to add a constant to the matrix values. Enter the constant into the entry field.

    data. Click the

    button to select the matrix file of your choice.

    PTVGROUP

    16.5.2.2 Adding values to selected matrix data


    4. Confirm with OK.
    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).
    The matrix values are added up.
    16.5.2.2

    Adding values to selected matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The context menu opens.
    4. Select Arithmetic operations on marked section> Add.
    The Select the operand for 'Add... on marked section window opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: When you add matrix values, only those with the same OD pair are actually
    added up.
    6. Confirm with OK.
    The matrix values are added up.
    Tip: To add a constant, in the Quick view and lists, you can directly enter the arithmetic
    operation of your choice. To add the value 2 e.g., select the matrix values of your choice
    and enter the expression =+2.

    PTVGROUP

    1779

    16.5.2.3 Adding up matrix values during the procedure sequence run


    16.5.2.3

    Adding up matrix values during the procedure sequence run


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Open matrix procedure
    of the Matrices category (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the Visum matrix to which you want to add the values.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. In the row of the added procedure, click in the Variant/file column.
    The icon
    7. Click the

    is displayed.
    icon.

    The Open matrix window opens.


    8. Select the desired file.
    Note: You can also select matrices with an external data format, for example EMME/2
    or TModel (see "EMME/2 import" on page 2587 and "TModel import" on page 2592).
    9. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell in the Variant/file column and manually enter the path and file name.
    10. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The Read additively window opens.
    11. Select the Read additively option.
    12. Confirm with OK.
    13. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    To the matrix, values of the selected matrix file are assigned.

    1780

    PTVGROUP

    16.5.3 Subtracting matrix values


    Note: The number of zones and the zone numbers in the imported matrix do not have to
    be identical with those in the Visum matrix you selected. Arithmetic operations, however,
    are only performed on matrix values with identical OD pairs. If the matrices do not have
    identical OD pairs, the following applies:
    If the matrix file does not contain an OD pair, the matrix value null is used.
    Any OD pairs that are not in the Visum file, will not be taken into account.

    16.5.3

    Subtracting matrix values


    From all or from the selected matrix values you can subtract either a constant value or the
    values from either other matrices or of a zone attribute.

    16.5.3.1

    Subtracting values from all matrix data


    Note: Click the Combination of matrices and vectors function to start the calculation
    during the procedure sequence run (see "Combining matrices and attribute vectors
    during the procedure sequence run" on page 1799).
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the symbol

    Subtract.

    The window Select the operand for Subtraction... on entire matrix opens.
    Tip: Alternatively you can select menu Matrix editor> Arithmetic operations> Subtract.
    3. Make the desired changes.
    Element

    Description

    Select matrices

    Select this option to subtract the values of one or several matrices (in
    the navigator) from your matrix data.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to subtract the values of a zone attributes from your
    matrix data.
    Origin
    Select this option to subtract the matrix value of each OD pair ij from
    the attribute value of the origin zone i.
    Destination
    Select this option to subtract the matrix value of each OD pair ij from
    the attribute value of the destination zone i.

    PTVGROUP

    1781

    16.5.3.2 Subtracting values from selected matrix data


    Element

    Description
    Note
    This function is provided for Visum matrices only.

    Load matrix
    from file

    Select this option to subtract the values of an external matrix from your

    Constant

    Select this option to subtract a constant from your matrix values. Enter
    the constant into the entry field.

    matrix data. Click the

    button to select the matrix file of your choice.

    4. Confirm with OK.


    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).
    The matrix values are subtracted.
    16.5.3.2

    Subtracting values from selected matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The context menu opens.
    4. Select Arithmetic operations on marked section> Subtract.
    The window Select the operand for Subtraction... on marked section opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: To be able to subtract a value from matrix data, they must have the same OD
    pair.

    1782

    PTVGROUP

    16.5.4 Multiplying matrix values


    6. Confirm with OK.
    The matrix values are subtracted.
    Tip: To subtract a constant, in the Quick view and lists, you can directly enter the arithmetic operation of your choice. To subtract the value 2, for example, select the matrix
    values of your choice and enter the expression =-2.

    16.5.4

    Multiplying matrix values


    You can multiply either the selected or all matrix values in three ways: either by a constant
    value or by a value taken from either another matrix or a zone attribute.

    16.5.4.1

    Multiplying values by all matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the symbol

    Multiply.

    The window Select the operand for Multiplication... on entire matrix opens.
    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations> Multiply.
    3. Make the desired changes.
    Element

    Description

    Select matrices

    Use this option to multiply your matrix values by the data of one or
    several matrices shown in the navigator.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to multiply the matrix values by the values of a zone
    attribute.
    Origin
    Select this entry to multiply the matrix value of each OD pair ij by the
    attribute value of the origin zone i.
    Destination
    Select this entry to multiply the matrix value of each OD pair ij by the
    attribute value of the destination zone i.
    Note
    This function is provided for Visum matrices only.

    PTVGROUP

    1783

    16.5.4.2 Multiplying the matrix data by selected values


    Element

    Description

    Load matrix
    from file

    Select this option to multiply your matrix values by the data of an exter-

    Constant

    Select this option to multiply your matrix values by a constant. Enter


    the constant into the entry field.

    nal matrix. Click the

    button to select the matrix file of your choice.

    4. Confirm with OK.


    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).
    The matrix values are multiplied.
    16.5.4.2

    Multiplying the matrix data by selected values


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The context menu opens.
    4. Select Arithmetic operations on marked section> Multiply.
    The window Select the operand for Multiplication... on marked section opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: When you multiply matrix data, only those values with the same OD pair are multiplied.
    6. Confirm with OK.
    The matrix values are multiplied.

    1784

    PTVGROUP

    16.5.5 Dividing matrix values


    Tip: To multiply the values by a constant, you can enter the arithmetic operation of your
    choice directly, just as into the Quick view or lists. To multiply the matrix values e.g. by 2,
    select the values and then enter the expression =*2.

    16.5.5

    Dividing matrix values


    You can divide either the selected or all matrix values in three ways: either by a constant value
    or by a value taken from either another matrix or a zone attribute.

    16.5.5.1

    Dividing all matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. If required, check the settings for division by null (see "Specifying treatment of division by
    zero" on page 1759).
    3. On the Matrix window toolbar, click the

    Divide icon.

    The window Select the operand for Division... on entire matrix opens.
    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Divide.
    4. Make the desired changes.
    Element

    Description

    Select matrices

    Use this option to divide your matrix values by the values of one or
    several matrices shown in the navigator.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to divide all matrix values by the values of a zone
    attribute.
    Origin
    Select this entry to divide the matrix value of each OD pair ij by the attribute value of the origin zone i.
    Destination
    Select this entry to divide the matrix value of each OD pair ij by the attribute value of the destination zone j.
    Note
    This function is provided for Visum matrices only.

    PTVGROUP

    1785

    16.5.5.2 Dividing selected matrix data


    Element

    Description

    Load matrix
    from file

    Select this option to divide your matrix data by external matrix data.

    Constant

    Select this option to divide your matrix data by a constant. Enter the
    constant into the entry field.

    Click the

    button to select the matrix file of your choice.

    5. Confirm with OK.


    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).
    The matrix values are divided. For division by null, the value specified is used.
    16.5.5.2

    Dividing selected matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Divide.
    The window Select the operand for Division... on marked section opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: When you divide matrix data, the data is only divided by values with the same
    OD pair.
    6. Confirm with OK.
    The matrix values are divided.

    1786

    PTVGROUP

    16.5.6 Forming the reciprocal of matrix values


    Tip: To divide the values by a constant, you can enter the arithmetic operation of your
    choice directly, just as into the Quick view or lists. To divide matrix values by 2, for example, select the values of your choice and enter the expression =/2.

    16.5.6

    Forming the reciprocal of matrix values


    You can form the reciprocal of matrix values (see Fundamentals: Chpt. 4.3.7 , page 202):
    Forming the reciprocal for all matrix data
    Forming the reciprocal for selected matrix data
    Forming the reciprocal during the procedure sequence run

    16.5.6.1

    Forming the reciprocal for all matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. If required, check the settings for division by null (see "Specifying treatment of division by
    zero" on page 1759).
    3. In the Matrix window, on the toolbar, click the button

    Form reciprocal.

    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Form reciprocal.
    For each OD pair, the reciprocal of the matrix value is formed and saved to the matrix. For division by null, the value specified is used.
    16.5.6.2

    Forming the reciprocal for selected matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. If required, check the settings for division by null (see "Specifying treatment of division by
    zero" on page 1759).
    3. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    4. Right-click a highlighted value.
    The shortcut menu opens.
    5. Choose Arithmetic operations on marked section> Form reciprocal.
    For each selected OD pair, the reciprocal of the matrix value is calculated and stored in the
    matrix. For division by null, the value specified is used.
    Tip: To calculate the reciprocal value, you can enter the arithmetic operation of your
    choice directly, just as into the Quick view or lists. To do so, select the desired matrix
    values and enter the expression =1/.

    PTVGROUP

    1787

    16.5.6.3 Forming the reciprocal during the procedure sequence run


    16.5.6.3

    Forming the reciprocal during the procedure sequence run


    1. If required, check the settings for division by null (see "Specifying treatment of division by
    zero" on page 1759).
    2. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    3. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    4. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    5. Select the matrix with the values you want to form the reciprocal for.
    6. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    8. Select the Reciprocal (by element) option.
    9. Confirm with OK.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The reciprocal value of the matrix values is calculated. For division by null, the value specified
    is used.

    16.5.7

    Raise to power
    You can specify an exponent for all or only selected matrix value and then transfer the results
    as new matrix values (see Fundamentals: Chpt. 4.3.7 , page 202). As an exponent, you can
    use a constant value or the values taken from either another matrix or a zone attribute.

    16.5.7.1

    Applying raise to power function to all matrix data


    Note: Click the Combination of matrices and vectors function to start the calculation
    during the procedure sequence run (see "Combining matrices and attribute vectors
    during the procedure sequence run" on page 1799).
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Raise to power icon.

    The window Select the operand for Raise to power... on entire matrix opens.

    1788

    PTVGROUP

    16.5.7.1 Applying raise to power function to all matrix data


    Tips: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Raise to power.
    3. Make the desired changes.
    Element

    Description

    Select matrices

    Select this option to use the values of one or several matrices (in the
    navigator) as exponents.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to use zone attributes as exponents.


    Origin
    Select this option to use the attribute value of the origin zone i as an
    exponent for the matrix value of each OD pair ij.
    Destination
    Select this option to use the attribute value of the destination zone j as
    an exponent for the matrix value of each OD pair ij.
    Note
    This function is provided for Visum matrices only.
    Load matrix
    from file

    Select this option to use external matrix values as exponents. Click the
    button to select the matrix file of your choice.

    Constant

    Select this option to use a constant as an exponent. Enter the constant


    into the entry field.

    4. Confirm with OK.


    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).

    PTVGROUP

    1789

    16.5.7.2 Using raise to power function for selected matrices


    An exponent is calculated for each matrix value and is then saved to the matrix.
    16.5.7.2

    Using raise to power function for selected matrices


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Raise to power.
    The window Select the operand for Raise to power... on marked section opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: When you apply the raise to power function, it will only be applied to values with
    the same OD pair.
    6. Confirm with OK.
    The raise to power function is applied to the matrix data.
    Tip: To raise the matrix values to the power of a constant, you can enter the arithmetic
    operation of your choice directly, just as into the Quick view or lists. To raise the values
    e.g. to the power of 2, select the desired matrix values and enter the expression =^2.

    16.5.8

    Take logarithm
    You can calculate the natural logarithm of matrix values (see Fundamentals: Chpt. 4.3.7 , page
    202):
    Taking the logarithm of all matrix data
    Taking the logarithm of selected matrix values
    Taking the logarithm during procedure sequence run

    16.5.8.1

    Taking the logarithm of all matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Natural logarithm icon.

    Note: If the matrix data selected contain any negative values or null, the function is
    cancelled.
    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Apply natural logarithm.

    1790

    PTVGROUP

    16.5.8.2 Taking the logarithm of selected matrix values


    For each OD pair, the natural logarithm of the matrix value is taken to the base e (Eulerian
    number, e 2.71828183) and stored in the matrix.
    16.5.8.2

    Taking the logarithm of selected matrix values


    1. Opens a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Natural logarithm.
    Note: If the Matrix window contains any negative values or null, the function is cancelled.
    For each OD pair selected, the natural logarithm is taken to the base e (Eulerian number, e
    2.71828183) of the original matrix value and will be saved with the matrix.
    Tip: To logarithmize the values, you can enter the arithmetic operation of your choice
    directly, just as into the Quick view or lists. To do so, select the matrix values of your
    choice and enter the expression =log.

    16.5.8.3

    Taking the logarithm during procedure sequence run


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix you would like to apply the take the logarithms function to.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    7. Select the Logarithm (by element) option.
    8. Confirm with OK.

    PTVGROUP

    1791

    16.5.9 Exponential function


    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Note: If the matrix contains any negative values or null, the function is cancelled.
    The natural logarithm of the matrix values is calculated.

    16.5.9

    Exponential function
    You can apply the exponential function to matrix data (see Fundamentals: Chpt. 4.3.7 , page
    202):
    Applying the exponential function to all matrix data
    Applying the exponential function to selected matrix data
    Applying the exponential function during the procedure sequence run

    16.5.9.1

    Applying the exponential function to all matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Apply the exponential function icon.

    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Exponential.
    For each OD pair, the value of the exponential function taken to the base e (Eulerian number,
    e 2.71828183) is calculated and will be saved with the matrix.
    16.5.9.2

    Applying the exponential function to selected matrix data


    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Apply the exponential function.
    For each OD pair selected, the value of the exponential function taken to the base e (Eulerian
    number, e 2.71828183) is calculated and saved to the matrix.
    Tip: To apply the exponential function, you can enter the arithmetic operation of your
    choice directly, just as into the Quick view or lists. To do so, select the desired matrix
    values and then enter the expression =exp.

    1792

    PTVGROUP

    16.5.9.3 Applying the exponential function during the procedure sequence run
    16.5.9.3

    Applying the exponential function during the procedure sequence run


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the matrix with the data you want to apply the exponential function to.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    7. Select the Exponential function (by element) option.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The exponential function value is calculated for the matrix values.

    16.5.10 Replacing matrix data by a maximum value


    You can compare all or selected matrix data per element with a constant value or a zone attribute value or with the same OD pairs of other matrices. You can then decide to adopt the highest value in each case.
    16.5.10.1 Replacing all matrix data with a maximum value
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Form the maximum icon.

    The window Select the operand for Form the maximum... on entire matrix opens.
    Tips: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Form the maximum.
    3. Make the desired settings.

    PTVGROUP

    1793

    16.5.10.1 Replacing all matrix data with a maximum value


    Element

    Description

    Select matrices

    Use this option to compare your matrix values with the data of one or
    several matrices shown in the navigator.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to compare your matrix data with zone attribute data.
    Origin
    Select this entry to compare the matrix value of each OD pair ij with
    the attribute value of the origin zone i.
    Destination
    Select this entry to compare the matrix value of each OD pair ij with
    the attribute value of the destination zone j.
    Note
    This function is provided for Visum matrices only.
    Load matrix
    from file

    Select this option to compare your matrix data with external matrix

    Constant

    Select this option to compare your matrix data with a constant. Enter
    the constant into the entry field.

    data. Click the

    button to select the matrix file of your choice.

    4. Confirm with OK.


    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).
    The maximum value of the matrix data compared is adopted.

    1794

    PTVGROUP

    16.5.10.2 Replacing selected matrix data with a maximum value


    16.5.10.2 Replacing selected matrix data with a maximum value
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Form the maximum.
    The window Select the operand for Form the maximum... on marked section opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: When you select matrix values, only those of the same OD pair are compared.
    6. Confirm with OK.
    The maximum value of the matrix data compared is adopted.
    Tip: For an elementwise comparison of the matrix values with the constant and an adoption of the maximum value, enter the arithmetic operation of your choice directly, just as
    into the Quick view or lists. The maximum is specified by a comparison of the values and
    a constant, e.g. 2. To specify the maximum, mark the relevant matrix values and then
    enter the expression =max2.

    16.5.11 Replacing matrix data by a minimum value


    You can compare all or selected matrix data per element with a constant value or a zone attribute value or with the same OD pairs of other matrices. You can then decide to adopt the
    lowest value in each case.
    16.5.11.1 Replacing all matrix data by a minimum value
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Form the minimum icon.

    The window Select the operand for Form the minimum... on entire matrix opens.
    Tips: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Form the minimum.
    3. Make the desired settings.

    PTVGROUP

    1795

    16.5.11.1 Replacing all matrix data by a minimum value


    Element

    Description

    Select matrices

    Use this option to compare your matrix values with the data of one or
    several matrices shown in the navigator.
    Tip
    The navigator lists the same matrices as the Matrices window (see
    "Showing matrices in the Matrices window" on page 1716).

    Zone attribute Select this option to compare your matrix data with zone attribute data.
    Origin
    Select this entry to compare the matrix value of each OD pair ij with
    the attribute value of the origin zone i.
    Destination
    Select this entry to compare the matrix value of each OD pair ij with
    the attribute value of the destination zone j.
    Note
    This function is provided for Visum matrices only.
    Load matrix
    from file

    Select this option to compare your matrix data with external matrix

    Constant

    Select this option to compare your matrix data with a constant. Enter
    the constant into the entry field.

    data. Click the

    button to select the matrix file of your choice.

    4. Confirm with OK.


    Note: If you select one or several matrices for arithmetic operations, the number of
    zones and the zone numbers do not have to be identical with those of the matrices in
    the Matrix window. Arithmetic operations, however, are only performed on matrix
    values with identical OD pairs. If the matrices do not have identical OD pairs, the following applies:
    If you choose a matrix that does not have an OD pair for an arithmetic operation,
    the matrix value null will be used.
    If in the Matrix window at least one Visum matrix is opened, OD pairs not shown
    in the Matrix window will not be taken into account.
    If in the Matrix window only external matrices are opened - and you select matrices with OD pairs for an arithmetic operation that are not shown in the window - a
    query is prompted. You can then specify if you want to add the additional OD
    pairs to the original matrices. This extension of the matrix means that new
    columns and/or rows are added accordingly (see "Extending external matrices
    during an arithmetic operation" on page 1810).
    The minimum value of the matrix data compared is adopted.

    1796

    PTVGROUP

    16.5.11.2 Replacing selected matrix data with a minimum value


    16.5.11.2 Replacing selected matrix data with a minimum value
    1. Opens a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. Mark the desired matrix values (see "Marking matrix data" on page 1761).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select Arithmetic operations on marked section> Minimum.
    The window Select the operand for Form the minimum... on marked section opens.
    5. Make the desired settings (see "Add values to whole matrix" on page 1777).
    Note: When you select matrix values, only those of the same OD pair are compared.
    6. Confirm with OK.
    The minimum value of the matrix data compared is adopted.
    Tip: For an elementwise comparison of the matrix values with the constant and an adoption of the minimum value, enter the arithmetic operation of your choice directly, just as
    into the Quick view or lists. The minimum is specified with the minimum of the values and
    a constant, e.g. 2. To specify the minimum, select the relevant matrix values and then
    enter the expression =min2.

    16.5.12 Symmetrizing a matrix


    You can calculate the average of two mirror-inverted matrix values above and below the
    matrix diagonal to then replace them with the average value.
    16.5.12.1 Symmetrizing a matrix in the Matrix window
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Make symmetrical icon.

    Tip: Alternatively, from the Matrix editor menu, choose Arithmetic operations>
    Make symmetrical.
    The matrix values are averaged.
    16.5.12.2 Symmetrizing a matrix during the procedure sequence run
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.

    PTVGROUP

    1797

    16.5.13 Combining matrices and attribute vectors


    2. To the procedure sequence, at the position of your choice, add the Matrix operation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. In the list of matrices select the matrix which you would like to calculate the mean values of
    the upper and the lower triangles for.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix operations window opens.
    7. Select the Make symmetrical option.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The mean matrix values are calculated and saved to the matrix.
    Note: You can also select the calculation of average values as a transformation function
    when combining matrices and vectors (see "Combining matrices and attribute vectors in
    the Matrix window" on page 1799).

    16.5.13 Combining matrices and attribute vectors


    Note: Please note that the user interface had not been fully completed, when the Visum
    13 user manual was finalized. Therefore, the following descriptions of settings may partially differ from the current program interface. Settings of previous Visum versions cannot
    be used any more.
    To a Visum matrix, you can assign values that are calculated from other matrices or from zone
    attribute values. When doing so, the values of individual input matrices and attributes are converted elementwise, multiplied by a factor and then added together.
    This function allows you to add exponential or Box-Cox transformed complex terms.
    Note: You can create a new Visum matrix whose values are calculated with a formula.
    The values of a formula matrix are continuously updated automatically (see "Create
    matrix calculated from formula" on page 1727).

    1798

    PTVGROUP

    16.5.13.1 Combining matrices and attribute vectors in the Matrix window


    16.5.13.1 Combining matrices and attribute vectors in the Matrix window
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the matrix window, on the toolbar, click the symbol
    vectors

    Combination of matrices and

    Tip: Alternatively, in the Matrices window, from the shortcut menu, choose Combination of matrices and vectors.
    The Edit graphic parameters window opens.
    3. Make the desired settings (see "Create matrix calculated from formula" on page 1727).
    4. Confirm with OK.
    The combination is calculated and the result is saved to the result matrix of your choice.
    16.5.13.2 Combining matrices and attribute vectors during the procedure sequence run
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the procedure sequence, at the position of your choice, add the Combination of matrices and vectors procedure of the Matrices category (see "Setting up and starting the procedure sequence" on page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. From the list of matrices, select the matrix you want to edit by combination.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Edit formula for matrix <no.> window appears.
    7. Make the desired settings (see "Combining matrices and attribute vectors in the Matrix window" on page 1799).
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The combination is calculated. The result is saved to the result matrix selected.

    PTVGROUP

    1799

    16.5.14 Projecting matrix values

    16.5.14 Projecting matrix values


    You can project the maximum values of a square matrix. The function is primarily used if you
    want to multiply origin or destination total values of a zone by a particular value or if you want
    to reach a particular target value, which e.g. might be necessary after conducting origin-destination study interviews. Matrices collected are often just random samples and must be projected to census values (see Fundamentals: Chpt. 4.3.12 , page 203).
    The following options are available to project matrix values:
    All matrix values evenly
    per row (singly constrained projection regarding attraction)
    per column (singly constrained projection regarding attraction)
    per row and column (doubly constrained projection)
    16.5.14.1 Projecting all matrix values evenly
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Projection icon.

    Tip: Alternatively, from the Matrix editor menu, choose Special matrix operations>
    Projection.
    The Projection window opens.
    Note: If you have saved the settings for projection to a file (*.xml, *.cod), click the Open
    button to load them.
    3. In the Projection is executed list, select For the entire matrix.
    4. Make the desired changes.
    Element

    Description

    General parameters

    Multiply with factor


    Select this option to multiply each matrix value by a factor.
    Project to target value(s)
    Select this option to project each matrix value so that their total
    equals the target value specified.

    Parameters for The content of this field depends on the option selected in the Genereference type ral parameters section.
    "entire matrix" Factor
    Factor by which the matrix values are multiplied.
    Target value
    Target value to which the matrix total is projected.

    1800

    PTVGROUP

    16.5.14.2 Singly constrained projection of matrices


    5. Confirm with OK.
    The matrix values are projected.
    16.5.14.2 Singly constrained projection of matrices
    You can use singly constrained projection to project matrices. Then each row or column of the
    matrices is multiplied by a factor.
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Projection icon.

    The Projection window opens.


    Note: If you have saved the settings for projection to a file (*.xml, *.cod), click the Open
    button to load them.
    3. In the Projection is executed list, click one of the Singly constrained ... entries.
    Element

    Description

    Singly constrained The matrix values are projected per row.


    production
    Singly constrained The matrix values are projected per column.
    attraction
    4. In the General parameters section, make the settings of your choice.
    Element

    Description

    Multiply with factor

    Select this option to multiply each row or column by a factor.

    Project to target
    value(s)

    Select this option if you want to project the matrix data of a row or
    column to the target values specified.

    5. In the Use factors or Apply target values section, make the desired settings.

    PTVGROUP

    1801

    16.5.14.2 Singly constrained projection of matrices


    Element

    Description

    From zone attributes

    Note
    This option is only available for Visum matrices.
    Select this option to use factors or target values for projection that
    are listed in a zone attribute.
    Factor for rows from attribute or Factor for columns from attribute
    Target value for rows from attribute or Target value for
    columns from attribute
    Click the respective button to select the zone attribute with factors
    or target values for projection.
    Note
    Only those options are enabled that correspond with the settings
    in the General parameters section.
    Identification of a zone as "external" from attribute
    If you are using target values for projection, you can use this zone
    attribute to exclude specific OD pairs from projection. Then the
    matrix values of all OD pairs between two zones marked as "external" are set to 0. The target values are distributed among the
    remaining matrix values.

    From parameters

    Select this option to use the factors or target values specified in


    the table for projection.
    ProductionValue and/or AttractionValue: Enter the desired
    factors or target values per row or column.
    Note
    If you require the same factor for multiple rows or columns, it
    can make sense to use the Projection by territory function
    (see "Projection by territory singly constrained" on page
    1805).
    External: If you are using target values for projection, you
    can use this qualification to exclude specific OD pairs from
    projection. Then the matrix values of all OD pairs between
    two zones marked as "external" are set to 0. The target
    values are distributed among the remaining matrix values.
    Tip
    Alternatively, click the Open button to read in the values of the
    table from the corresponding parameter file.

    6. Confirm with OK.


    The matrix values are projected.

    1802

    PTVGROUP

    16.5.14.3 Doubly constrained projection of matrices


    16.5.14.3 Doubly constrained projection of matrices
    You can use doubly constrained projection to project matrices. To do so, you use an iterative
    procedure, also called multi-procedure. During this iterative procedure, a solution to how the
    target values are best reached is generated stepwise.
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Projection icon.

    The Projection window opens.


    Note: If you have saved the settings for projection to a file (*.xml, *.cod), click the Open
    button to load them.
    3. In the Projection is executed list, click Doubly constrained (multi-procedure).
    4. Make the desired changes.
    Element

    Description

    General parameters

    Multiply with factor


    Select this option to project the matrix values per row and column,
    using a factor.
    Project to target value(s)
    Select this option to project the matrix values so that their row and
    column totals approximately correspond to the target values specified.

    Parameters for
    reference type
    doubly constrained (multi-procedure)

    Select this option to specify the matrix total used to calculate the
    multi-procedure, if the total of all row sums and the total of all
    column sums differ due to the factors or target values applied.
    Sum of productions
    The total of all row sums is used as matrix total.
    Sum of attractions
    The total of all column sums is used as matrix total.
    Mean of both sums
    The mean value of row sums and column sums is used as matrix
    total.
    Minimum of both sums
    The lower of the two values (total of all row sums and total of all
    column sums) is used as matrix total.
    Maximum of both sums
    The higher of the two values (total of all row sums and total of all
    column sums) is used as matrix total.

    PTVGROUP

    1803

    16.5.14.3 Doubly constrained projection of matrices


    Element

    Description
    Max. number of iterations
    The calculation procedure is canceled as soon as the specified
    number of iterations is reached.
    Quality factor
    The calculation procedure is canceled as soon as a value falls
    below a specific limit. The quality factor is included in limit calculation (see Fundamentals: Chpt. 4.3.12 , page 203).
    Note
    The higher the quality factor is, the longer the computing time and
    the higher the precision of the calculations.

    5. In the Use factors or Apply target values section, make the desired settings.

    1804

    Element

    Description

    From zone attributes

    Note
    This option is only available for Visum matrices.
    Select this option to use factors or target values for projection that
    are listed in two zone attributes.
    Factor for rows from attribute and Factor for columns from
    attribute
    Target value for rows from attribute and Target value for
    columns from attribute
    Click the corresponding button to select zone attributes with factors or target values for projection.
    Note
    Only those options are enabled that correspond with the settings
    in the General parameters section.
    Identification of a zone as "external" from attribute
    If you are using target values for projection, you can use this zone
    attribute to exclude specific OD pairs from projection. Then the
    matrix values of all OD pairs between two zones marked as "external" are set to 0. The target values are distributed among the
    remaining matrix values.

    From parameters

    Select this option to use the factors or target values specified in


    the table for projection.
    ProductionValue and AttractionValue: Here you enter the
    desired factors or target values per row or column.
    External: If you are using target values for projection, you
    can use this qualification to exclude specific OD pairs from
    projection. Then the matrix values of all OD pairs between

    PTVGROUP

    16.5.15 Projecting matrix values by territory


    Element

    Description
    two zones marked as "external" are set to 0. The target
    values are distributed among the remaining matrix values.
    Tip
    Alternatively, click the Open button to read in the values of the
    table from the corresponding parameter file.

    6. Confirm with OK.


    The matrix values are projected.

    16.5.15 Projecting matrix values by territory


    This function allows you to convert square matrices. The zones or main zones, i.e. the rows
    and columns of a matrix, are then divided into groups. Then you define a projection factor per
    group or per group relation (see Fundamentals: Chpt. 4.3.13 , page 205). The matrix values
    are multiplied by the projection factors.
    Note: The projection by territory does not regard network objects of the Territory type.
    16.5.15.1 Projection by territory singly constrained
    Singly constrained projection by territory corresponds to singly constrained projection with a
    factor (see "Projecting matrix values" on page 1800). The only difference is that for projection
    by territory the rows and columns of the matrix are divided into groups ("territories") and you
    specify a projection factor per group.
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix window, on the toolbar, click the

    button Projection by territory.

    Tip: Alternatively, in the Matrix editor menu, click Special matrix operations> Projection by territory.
    The Projection by territory window opens.
    3. In the Projection section, make the desired settings.
    Element

    Description

    Singly constrained Select this option to project the matrix values by row.
    production
    Singly constrained Select this option to project the matrix values by column.
    attraction
    4. In the Territory definition area, define the groups (see "Dividing rows or cells into groups"
    on page 1806).

    PTVGROUP

    1805

    16.5.15.2 Projection by territory - element-wise


    5. In the Factor column, then specify a projection factor per group.
    6. Confirm with OK.
    The matrix is projected by territory.
    16.5.15.2 Projection by territory - element-wise
    1. Open a Matrix editor window with the matrix of your choice (see "Opening matrices" on
    page 1721).
    2. In the Matrix window, on the toolbar, click the

    button Projection by territory.

    Tip: Alternatively, in the Matrix editor menu, click Special matrix operations> Projection by territory.
    The Projection by territory window opens.
    3. In the Projection section, select By element.
    4. In the Territory definition area, define the groups (see "Dividing rows or cells into groups"
    on page 1806).
    In the Element-based projection section, a matrix is displayed, listing the defined groups
    (=territories) as rows and columns.
    5. In the Element-based projection section, make the settings of your choice.
    Element

    Description

    Matrix values

    In the matrix, you can enter a factor per relation between two territories.

    Open matrix

    Click this button to read in the projection factors from a matrix file.
    Note
    The territory numbers in the matrix file must correspond with
    those used for territory definition. If required, you can change the
    territory numbers in the Territory definition section.

    Save matrix

    Click this button to save the projection factors defined in the


    matrix.

    6. Confirm with OK.


    The matrix is projected by territory.
    16.5.15.3 Dividing rows or cells into groups
    There are different ways to divide zones into groups:
    Read in territory assignment from a parameter file generated during aggregation (see
    "Selecting rows and columns for aggregation" on page 1813)
    Allocate zones to groups to reflect attribute values of an attribute

    1806

    PTVGROUP

    16.5.15.3 Dividing rows or cells into groups


    This function is only available for Visum matrices.
    Specifying groups manually
    Reading in territory assignment from a file
    If you have saved territory assignment as a file (*.xml or *.cod ), e.g. during aggregation, you
    can read in the file (see "Selecting rows and columns for aggregation" on page 1813).
    1. Open the Projection by territory window.
    2. Click the Open parameter file button.
    The Open: Parameters for matrix operations window opens.
    3. Select the desired file.
    4. Confirm with Open.
    The territory allocations are displayed.
    Generating territory allocation using an attribute
    For Visum matrices, you can divide the zones into territories according to the values of a specific attribute. For instance, you can use the attribute Main zone number to divide the zones
    into groups according to the main zones they belong to.
    Note: If you use an attribute to generate territory assignment, all other entries in the list
    are deleted.
    1. Open the Projection by territory window.
    2. Click the Create from attribute button.
    The Attributes window opens.
    3. Select the desired attribute.
    4. Confirm with OK.
    The territory allocations are generated. Zones with the same attribute value are assigned to
    the same group.
    Defining territories manually
    1. Open the Projection by territory window.
    2. Click the Create button.
    The Selection of zones window opens.
    3. In the list, click the objects you want to assign to the same group.
    Tip: Click the Check all and Uncheck all buttons to select or deselect all objects.
    Click the Invert button to invert your current selection.
    4. Confirm with OK.

    PTVGROUP

    1807

    16.5.16 Calculating a main zone matrix from a zone matrix


    A new row is added to the list for territory assignment.
    Changing the territory allocation
    Click the Edit button to edit the territory allocation for the currently selected territory.
    Click the Delete button to delete the currently selected territory allocations.

    16.5.16 Calculating a main zone matrix from a zone matrix


    You can use a zone matrix to calculate a main zone matrix. The matrix values of zones belonging to the same main zone are added up and the results are stored in a main zone matrix
    (see Fundamentals: Chpt. 4.3.14 , page 205).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Matrix aggregation procedure of the Matrices category (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. In the list box, click the main zone matrix you want to save the aggregated values to.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Select matrix window opens.
    7. In the list box, click the zone matrix with the data you want to aggregate.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The values of the zone matrix are added together and the result is saved to the main zone
    matrix selected.

    16.5.17 Calculating a zone matrix from a main zone matrix


    To create a zone matrix from a main zone matrix, distribute the data of each main zone to its
    zones, and save this data to an existing zone matrix. You can distribute the data evenly or use
    weighting factors (see Fundamentals: Chpt. 4.3.14 , page 205).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.

    1808

    PTVGROUP

    16.5.17 Calculating a zone matrix from a main zone matrix


    2. To the procedure sequence, at the position of your choice, add the Matrix disaggregation
    procedure of the Matrices category (see "Setting up and starting the procedure sequence"
    on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select matrix window opens.
    4. In the list box, click the zone matrix you want to save the disaggregated values to.
    5. Confirm with OK.
    The selected matrix is listed in the Reference object(s) column.
    6. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Disaggregate matrix window opens.

    7. Make the desired changes.


    Element

    Description

    Select matrix

    Click this button to select the main zone matrix you want to disaggregate.

    Disaggregation
    weights

    Two origin-destination properties that are used as weighting factors for disaggregation. You can for instance choose a matrix or
    an origin or destination attribute.
    Notes
    Enter 1.0 for both weighting factors to obtain an even distribution
    of the data among the zones.
    If the denominator in the formula becomes null, the data is also
    evenly distributed.

    8. Confirm with OK.


    PTVGROUP

    1809

    16.6 Changing the structure of matrices


    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The values of the main zone matrix are broken down and the result is saved to the zone matrix
    selected.

    16.6

    Changing the structure of matrices


    You can change the structure of external matrices, i.e. you can add or delete columns and
    rows.
    Note: This is recommended for external matrices only, since Visum matrices need a reference to (main) zones of the version file.
    Extending external matrices during an arithmetic operation
    Aggregating or deleting matrix columns and rows
    Splitting columns and rows

    16.6.1

    Extending external matrices during an arithmetic operation


    You can extend external matrices during an arithmetic operation, i.e. you can add columns
    and rows (see Fundamentals: Chpt. 4.3.15 , page 206). To do so, choose an arithmetic operation that allows you to combine external matrices with matrices that have different OD pairs.
    Before the arithmetic operation is performed, Visum queries whether you want to extend the
    matrices.
    1. Open a Matrix window with the external matrices of your choice (see "Opening matrices" on
    page 1721).
    2. Perform the arithmetic operation of your choice.
    Notes: You can use any arithmetic operation that requires a second operand, e.g. the
    basic ones or forming the maximum or minimum (see "Using matrix values for calculations" on page 1776).
    As operand for the arithmetic operation, choose one or several matrices with OD pairs
    that are not shown in the matrices of the Matrix window.
    A query opens.

    3. Click Yes to confirm.


    The arithmetic operation is performed and the matrix is extended.

    1810

    PTVGROUP

    16.6.2 Aggregating or deleting matrix columns and rows


    Notes: The matrix data is calculated as follows:
    The arithmetic operation is performed for the OD pairs that occur in both matrices.
    If an OD pair is only listed in one matrix, a null is entered for it before the arithmetic
    operation is performed. Then the arithmetic operation is performed.
    For OD pairs that are not listed in any of the matrices, a default value is set in the
    results matrix (see "Specifying a default value for new relations" on page 1759).
    If the rows and column objects have names, they are combined. If the names are different, the name of the matrix is used from which the arithmetic operation was started.

    16.6.2

    Aggregating or deleting matrix columns and rows


    You can bundle several columns and rows in an external matrix. When doing so, you can
    change the column or row numbers or delete any columns or rows (see Fundamentals: Chpt.
    4.3.16 , page 207).

    16.6.2.1

    Basic settings for aggregation


    1. Open a Matrix window with the external matrices of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Aggregate icon.

    Tip: Alternatively, from the Matrix editor menu, choose Special matrix operations>
    Aggregate.
    The Aggregation window opens.
    3. Make the desired settings.

    PTVGROUP

    1811

    16.6.2.1 Basic settings for aggregation


    Element

    Description

    Functionality Here you specify how to determine a new, aggregated matrix value.
    Minimum
    The new matrix value is the smallest value of the aggregated matrix
    values.
    Maximum
    The new matrix value is the largest value of the aggregated matrix
    values.
    Arithmetic mean
    The new matrix value is the mean value of the aggregated matrix
    values.
    Total
    The new matrix value is the sum of the aggregated matrix values.
    Weighted mean
    The new matrix value is the weighted mean of the aggregated matrix
    values. Before the mean value is calculated, the original matrix values
    are weighted with the values of the matrix selected.
    Matrix
    Click this button to select the matrix you want to use for weighting. The
    matrix must have the same number of rows and columns as the nonaggregated matrix.
    Apply to

    Rows and columns


    All rows and columns of the matrix are aggregated, deleted or renumbered.
    Only rows
    Only the rows of the matrix are aggregated, deleted or renumbered.
    The number and numbering of the columns remain unchanged.
    Only columns
    Only the columns of the matrix are aggregated, deleted or renumbered.
    The number and numbering of the rows remain unchanged.

    Cut off input Select this option to limit the values of the original matrix to a threshold.
    matrix values For calculation of the new, aggregated value, the threshold is used instead of the higher or lower original value.
    Minimum
    Lower threshold for original matrix values
    Maximum
    Highest threshold for original matrix values
    4. In the list, specify the rows and columns you want to aggregate, renumber or delete (see
    "Selecting rows and columns for aggregation" on page 1813).

    1812

    PTVGROUP

    16.6.2.2 Selecting rows and columns for aggregation


    Note: Click the Open button to read in the list from a corresponding parameter file
    (*.xml, *.cod).
    5. Confirm with OK.
    The rows and/or columns of your choice are aggregated.
    16.6.2.2

    Selecting rows and columns for aggregation


    For the aggregation function, select the rows or columns you want to aggregate, renumber or
    delete.
    Selecting rows or columns for aggregation
    1. Open the Aggregation window.
    2. Click the Create button.
    The Selection of aggregated zones window opens.
    3. Select the numbers of the rows or columns that you want to aggregate to one, single row or
    column.
    Tip: Use the following buttons to select the entries:
    Check all: Select all entries
    Uncheck all: Undo the selection
    Invert: Select all entries currently not selected
    4. Confirm with OK.
    A new entry is added to the list. It contains a column with the new row or column number
    and a column with the previous row and column numbers.
    5. If required, in the NewZoneNo column, change the number of the new row or column.
    6. In the same way, you can add further entries to the list.
    Selecting row or column for renumbering
    1. Open the Aggregation window.
    2. Click the Create button.
    The Selection of aggregated zones window opens.
    3. Select the number of the row or column you want to renumber.
    4. Confirm with OK.
    A new entry is added to the list.
    5. Into the NewZoneNo column, enter the new number.
    6. In the same way, you can add further entries to the list.

    PTVGROUP

    1813

    16.6.3 Splitting columns and rows


    Selecting rows or columns for deletion
    1. Open the Aggregation window.
    2. Click the Create button.
    The Selection of aggregated zones window opens.
    3. Select the numbers of the rows or columns you want to delete.
    4. Confirm with OK.
    A new entry is added to the list.
    5. In the Operation column, select Delete.
    6. In the same way, you can add further entries to the list.
    Notes: To edit an individual row of the list, select it and click the Edit button.
    To delete rows from the list, select them and click the Delete button.
    You can save the list to a parameter file (*.xml) (see "Saving settings for special matrix
    operations" on page 1815).

    16.6.3

    Splitting columns and rows


    You can split the columns and rows of an external, square matrix. This way you can, for example, adjust demand matrices of a roughly meshed network to a finer zone definition in the network model (see Fundamentals: Chpt. 4.3.17 , page 208).
    Note: During splitting, both the row and column of the object are split.
    1. Open a Matrix window with the external matrices of your choice (see "Opening matrices" on
    page 1721).
    2. On the Matrix window toolbar, click the

    Split icon

    Tip: Alternatively, in the Matrix editor menu, click Special matrix operations> Split.
    The Split window opens.
    3. Click the Create button.
    The Selection of the zone to be split window opens.
    4. Select the number of the row or column you want to split into several rows or columns.
    5. Confirm with OK.
    A new entry is added to the list. It contains a column with the old row or column number and
    another column with the new row or column number.
    6. Make your changes to the new entry.

    1814

    PTVGROUP

    16.6.4 Saving settings for special matrix operations


    Column

    Description

    NewZoneNo

    Number of the new row or column

    Origin factor

    Factor by which the origin traffic of the selected zone is multiplied


    in order to calculate the values of the new zone.

    Destination factor Factor by which the destination traffic of the selected zone is multiplied in order to calculate the values of the new zone.

    Note: You can specify any factor.

    7. In the same way, you can add further entries to the list.
    Notes: To edit an individual row of the list, select it and click the Edit button.
    To delete rows from the list, select them and click the Delete button.
    You can save the list to a parameter file (*.xml) (see "Saving settings for special matrix
    operations" on page 1815).
    8. Make the desired changes.
    Column

    Description

    Set any arising


    Select this option to set all newly created cells of the main diaintrazonal demand gonal (row number=column number) to zero.
    to zero
    If this option is not selected, the values are calculated for the
    newly created cells in the main diagonal. The original values are
    multiplied by the origin factor and by the destination factor.
    9. Confirm with OK.
    The rows or columns selected are split according to your specifications. The rows and
    columns with the original values are deleted.

    16.6.4

    Saving settings for special matrix operations


    For the following matrix operations, you can save your current settings as a parameter file
    (*.xml):

    PTVGROUP

    1815

    16.7 Correcting matrices


    Projection (see "Projecting matrix values" on page 1800)
    Aggregation (see "Aggregating or deleting matrix columns and rows" on page 1811)
    Splitting (see "Splitting columns and rows" on page 1814)
    When doing so, you can decide to save the changes made in the list to a separate text file *.att.
    You can then read in the parameter files for other operations.
    1. Open the parameter window of the operation of your choice.
    2. Make the desired changes.
    3. Click the Save button.
    The Save the parameters for matrix operation window opens.
    4. Make the desired changes.
    Element

    Description

    Save the paraSelect this option to save the changes made to assignments in
    meters for zones the list to a separate text file (*.att). In this case, the *.xml file conto a separate attri- tains a reference to the *.att file.
    bute file
    If this option is not selected, all settings are saved to the *.xml
    file.
    File name

    Select this option to choose the *.att you want to save the settings
    to.

    5. Click the Next button.


    The Save the parameters for matrix operations window opens.
    6. Select the desired file.
    Note: Alternatively, you may enter path and file name.
    7. Click the Save button.
    If the Save the parameters for zones to a separate attribute file option is selected, the
    Save attributes window opens.
    8. In the Separator list, click the entry of your choice.
    Note: To read in the attribute files again, select either the semicolon or the tabulator
    as separator.
    9. Confirm with OK.
    The settings are stored.

    16.7

    Correcting matrices
    You have different possibilities of correcting the demand matrix values with count data.

    1816

    PTVGROUP

    16.7.1 Matrix update using TFlowFuzzy


    Matrix update using TFlowFuzzy
    Projecting PrT path volumes
    Calibrating a PrT matrix

    16.7.1

    Matrix update using TFlowFuzzy


    Note: This function will only be available if the TFlowFuzzy add-on module has been activated (see "Enabling or disabling installed add-ons" on page 886).
    The TFlowFuzzy procedure can be used to adjust demand matrix values to current count data
    (for example link volumes or origin and destination demand from and to zones) (see Fundamentals: Chpt. 4.4.1 , page 210).

    16.7.1.1

    Preparing data for the matrix update


    Prior to the matrix value update by TFlowFuzzy you need to perform the following steps for
    data preparation:
    1. Open a version file or a network with the supply valid at the time of acquiring the count data
    (see "Opening and saving files" on page 831).
    2. Import the demand matrices that you would like to update with TFlowFuzzy into Visum(see
    "Importing matrix values into Visum matrices" on page 1768).
    3. Make sure that the input is provided as numerical (possibly user-defined) attributes of links,
    zones, screenlines, turns or main turns (if a main node has been defined), lines or stop
    areas (see "Managing attributes" on page 958 and "Editing attribute values of network
    objects" on page 983).
    4. Allocate the empirically determined values s (from several counts of the same volume of
    links, zones, screenlines, turns or main turns, lines or stop areas or from several counts in
    the same zone) to a numerical (possibly user-defined) attribute of links, zones, screenlines,
    turns or main turns, lines or stop areas (see "Editing attribute values of network objects" on
    page 983 and "Reading an attribute file" on page 2646).
    Note: The value s indicates the difference of counted value z at which the fuzzy membership function decreases to the value 0 (see Fundamentals: Chpt. 4.4.1.1 , page
    212).
    5. Assign the out-dated demand matrices to the current supply (see "Setting and calculating
    the parameters for PrT assignment" on page 1931 and "Setting and calculating PuT assignment parameters" on page 2006).
    The volumes of the links, screenlines, turns or main turns or lines and/or passengers boarding
    or alighting at stop areas as well as the origin and destination demand of zones are calculated
    and are the basis for the flow matrix calculated with TFlowFuzzy (see Fundamentals: Chpt.
    4.4.1.1 , page 212).

    PTVGROUP

    1817

    16.7.1.2 Matrix correction using TFlowFuzzy


    16.7.1.2

    Matrix correction using TFlowFuzzy


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Demand matrix correction (TFlowFuzzy) procedure of the Matrices category (see "Setting up and starting the
    procedure sequence" on page 1847).
    3. In the row of the added procedure, click the button in the Reference object(s) column.
    The Select Demand segments window opens.
    4. In the Select mode selection list, select the mode of the demand segments whose matrices
    you would like to correct.
    5. In the Demand segments selection list, select the demand segments whose matrices you
    would like to correct.
    Tip: To mark multiple demand segments, press the C TRL key and keep it pressed
    while clicking the desired entries one by one.
    Note: Since demand matrices in Visum are separate objects that can be assigned to
    several demand segments, the changes to a matrix affect all demand segments that
    are linked to the matrix after demand segment selection (see "Connecting demand
    matrices and demand segments" on page 1607).
    6. Confirm with OK.
    The demand segments selected are adopted in the Reference object(s) column.
    7. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The TFlowFuzzy window opens.
    8. Set the desired parameters (see "TFlowFuzzy parameters" on page 1819).
    Tip: Alternatively, you may read matrix correction settings from file for TFlowFuzzy
    (see "Reading old TFlowFuzzy settings from file" on page 1833).
    9. Confirm with OK.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Matrix correction is executed.
    Note: If the matrix correction is canceled due to invalid count data, Visum writes the invalid count data to the log file.

    1818

    PTVGROUP

    16.7.1.3 TFlowFuzzy parameters


    16.7.1.3

    TFlowFuzzy parameters
    TFlowFuzzy: Input
    Element

    Description

    Use only network objects


    with volume >0
    and counted
    value >0

    If you select this option, only network objects with a volume and count
    value above 0 will be used.

    Counted volumes only refer


    to active line
    route items

    If you select this option, the PuT count values will refer to active line
    route items only. The volumes or boarding/alighting passengers will be
    included on the basis of the following rules:
    Link volume: the line route item at "From node" of the link must be
    active.
    Turn volume: the line route items at "From node" and "Via node" of
    the turn must be active.
    Screenline volume: the line route item at the "From node" of the link
    crossing the screenline must be active.
    Line volume (PTrips): the first line route item of the path leg must be
    active.
    Passengers alighting at a stop area: the last line route item of the
    path leg must be active. This is the line route item before the line
    route item of the alighting stop.
    Passengers boarding at a stop area: the first line route item of the
    path leg must be active.
    Note
    This option does not appear, unless you have selected a demand segment of the PuT mode.

    PTVGROUP

    1819

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description

    Zones

    Take the totals of matrix rows and columns as basis


    If you select this option, the values of the numerical (possibly user-defined) zone attributes will be used as count data.
    Note
    When determining the origin/destination demand, PuT boarding/alighting volumes may be used only if these values do not include
    transfers.
    Only active zones
    If count data is not provided for all of the zones, you may use this option
    to regard only the data of active zones (see "Using filters to set network
    objects active or passive" on page 1008 and "Setting network objects
    active/passive via the spatial selection" on page 1033).
    Row totals
    Via this button, you may - in a separate window - select the numerical
    zone attribute that codes the origin demand counts.
    Column totals
    Via this button, you may - in a separate window - select the numerical
    zone attribute that codes the destination demand counts.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).

    Links

    1820

    Based on counted link volumes


    If you select this option, the values of the numerical (possibly user-defined) zone attributes will be used as count data.
    Only active links
    If count data is not provided for all of the links you may use this option to
    consider only the data of active links (see "Using filters to set network
    objects active or passive" on page 1008 and "Setting network objects
    active/passive via the spatial selection" on page 1033)
    Volume
    Via this button, you may - in a separate window - select the link attribute
    that codes the volume counts of the link.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).

    PTVGROUP

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description

    Turns and main Based on counted turn and main turn volumes
    turns
    If you select this option, the values of the numerical (possibly user-defined) turn or main turn attributes will be used as count data.
    Note
    To use a user-defined attribute for main turns, you also have to create
    this attribute for regular turns.
    Only active turns and main turns
    If count data is not provided for all of the turns or main turns respectively, you may use this option to regard only the data of active turns or
    main turns (if a main node has been defined) (see "Using filters to set
    network objects active or passive" on page 1008 and "Setting network
    objects active/passive via the spatial selection" on page 1033).
    Volume
    Via this button, you may - in a separate window - select the turn attribute that codes the volume counts values of turns or main turns.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).
    Screenlines

    PTVGROUP

    Based on volumes counted in the direction of the screenline


    If this option has been checked, the values of numerical (possibly userdefined) screenline attributes are used as count data. Thereby, only
    volume data for the direction of the screenline is considered.
    Only active screenlines
    If count data is not provided for all of the screenlines you may use this
    option to regard only the data of active screenlines (see "Using filters to
    set network objects active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page 1033).
    Volume
    Via this button, you may - in a separate window - select the screenline
    attribute that codes the volume counts of the screenline.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).

    1821

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description

    Total traffic

    Take the counted total traffic (all demand segments) as basis


    If this option has been selected, the counted total traffic will be used.
    Note
    The counted total traffic is summed up over all demand segments.
    Total traffic
    In the entry field, enter the initial counted total traffic value.
    +/In the entry field, enter the bandwidth.

    TFlowFuzzy: Count data PrT


    Note: The Count data PrT tab does not appear unless you select a demand segment of
    the PrT mode.
    Element

    Description

    Lane groups

    Based on counted lane group volumes


    Select this option to use numerical values of lanes as count data.
    Here several lanes are divided into lane groups, if there are mixed
    lanes that allow for turns in several directions (see Fundamentals:
    Chpt. 6.5.3.2 , page 246).
    Note
    If a lane belonging to a group contains the value zero, a warning message is displayed.
    Only lane groups of active nodes
    If count data is not available for all nodes, select this option to consider the lane values of active nodes only (see "Using filters to set network objects active or passive" on page 1008 and "Setting network
    objects active/passive via the spatial selection" on page 1033).
    Volume
    Click this button to select the lane attribute that contains the volume
    counts of the lane group in a separate window.
    +/Via this button, you may - in a separate window - select the attribute
    that codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page
    212).

    TFlowFuzzy: Count data PuT


    Notes: The Count data PuT tab does not appear unless you select a demand segment of
    the PuT mode.
    Count data can only be used, if there are PuT paths for the selected demand segments.
    1822

    PTVGROUP

    16.7.1.3 TFlowFuzzy parameters

    Element

    Description

    PuT lines

    Based on counted PTripsUnlinked


    If you select this option, the values of the numerical (possibly user-defined)
    line attributes will be used as count data.
    Only active lines
    If count data is not provided for all PuT lines, you may use this option to
    include only the data of active lines (see "Using filters to set network objects
    active or passive" on page 1008 and "Setting network objects active/passive
    via the spatial selection" on page 1033).
    Volume
    Via this button, you may - in a separate window - select the line attribute that
    codes the volume counts of the line.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).
    Based on counted person kilometers
    If you select this option, the values of the numerical (possibly user-defined)
    line attributes will be used as count data.
    Only active lines
    If count data is not provided for all PuT lines, you may use this option to
    include only the data of active lines (see "Using filters to set network objects
    active or passive" on page 1008 and "Setting network objects active/passive
    via the spatial selection" on page 1033).
    Person kilometers
    Via this button, you call a separate window: select the line attribute that
    codes the counted person kilometers of the line.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).

    Stop areas Based on counted boarding/alighting passengers at stop areas


    If you select this option, the values of numerical (possibly user-defined) stop
    area attributes will be used as count data.
    Only active stop areas
    If count data is not provided for all stop areas, you may use this option to
    include only the data of active stop areas (see "Using filters to set network
    objects active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page 1033).
    Boardings
    Via this button, you may - in a separate window - select the stop area attribute that codes the count data of boarding passengers.

    PTVGROUP

    1823

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description
    Alightings
    Via this button, you may - in a separate window - select the stop area attribute that codes the count data of alighting passengers.
    +/Via this button, you may - in a separate window - select the attribute that
    codes the bandwidths (see Fundamentals: Chpt. 4.4.1.1 , page 212).
    Transfers count as boarding/alighting passengers
    Use the drop-down list to specify whether transfers are counted as boarding
    and alighting passengers.
    Always: Transfers are counted as boarding and alighting passengers
    Never: Transfers are not counted as boarding and alighting passengers
    If attribute > 0: Select the desired attribute by clicking the button below.
    Transfers are counted as boarding and alighting passengers at all stop
    areas whose attribute value is greater than 0.

    TFlowFuzzy: Distribution <Demand segment code>


    Note: A tab is displayed for each selected demand segment. You can adjust several settings for each demand segment.
    Element

    Description

    Based on skim If you select this option, the demand segment output will be adjusted to
    data disa given distribution.
    tribution
    Regard only
    If this option is selected, only the active OD pairs will be regarded when
    active OD pairs the result matrix is adjusted to a given distribution. This applies to both
    class limit determination and OD pair determination in the output matrix.
    Note
    The values in the columns Number of trips and Number of trips - tolerance depend on this setting.
    Skim matrix for Via this button, you call a separate window for the selection of a skim
    classification
    matrix for the classification of OD pairs. You may select either an external matrix file or a matrix which is included in the version file.
    Classes and
    shares

    1824

    Preset class limits and derive shares from current matrix


    If this option is selected, the class limits will be defined according to the
    following option settings:
    Shares due to the current demand matrix
    The shares of the specified classes are based on the current demand
    matrix.

    PTVGROUP

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description
    Shares due to the matrix
    Via this button, you call a separate window for the selection of the
    demand matrix, from which the share by specified class will be derived.
    You may select either an external matrix file or a matrix which is included in the version file.

    Preset class
    limits and shares

    By selecting this option you specify the class limits in the list Class
    limits and shares below.

    Class limits
    and shares

    List of specified classes. You can add the classes manually or import
    them from an interval file for further editing.
    From / To
    Class limits for the desired distribution
    Note
    Classes must not overlap.
    Share
    Percentage of the class (100% = 1)
    Note
    These fields cannot be edited, if you import the shares from an existing
    demand matrix.
    Cum. share
    Accumulated share
    Number of trips
    Number of trips resulting from the class limits and the entered share of
    the current demand matrix.
    Number of trips - tolerance
    Value obtained from the Number of trips and the Class share tolerance values.
    Create
    Use this button to add a new class.
    Delete
    Use this button to delete the selected class.
    Read from file
    Use this button to delete all existing classes and import new classes
    and shares from an interval file (*.cod or *.att) into the list.

    Interval type

    Use this option to specify the class for each threshold.

    From interval
    file

    Select this option to use an interval file with classes and shares. Click

    PTVGROUP

    button to choose a file.


    the
    Notes

    1825

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description
    This option allows you to use data that is not calculated until during the
    procedure sequence run.
    Interval files have the extensions *.cod or *.att.

    Class share
    tolerance

    Permitted deviation regarding the number of trips in the classes


    Tip
    In the Number of trips - tolerance column the resulting absolute values
    appear.

    TFlowFuzzy: Parameters
    Note: We recommend not to change the default settings in the Parameters tab.

    1826

    PTVGROUP

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description

    Analysis

    Protocol
    If this option is selected, a matrix update protocol will be traced to the
    log file (see "Using protocol files" on page 876).
    Diagnosis
    If the option has been selected, the diagnosis functionality is active.
    Visum will use various criteria for the diagnosis. The output lists will be
    recorded in the log file.
    Progress statistics
    If the option is selected, a progress statistics will be generated. Click the
    icon and define where the statistics are to be stored.
    Note
    The statistics file is saved in the *.txt format. Thus you can easily convert
    the file into a graphics display.

    Procedure para- Max. correction factor


    meters
    The correction factor limits any change to a relation from the "old"
    matrix to the new one to the factor e.
    Note
    This applies to the default setting only in the event that the procedure
    can find no solution within the specified counted values and becomes
    numerically unstable.
    Cancel if change <
    The calculation is cancelled if - from one iteration to the next - the OD
    matrices have not changed in any OD pair by more than the specified
    number of trips.
    Number of iterations
    After the user-defined number of iterations the iteration process is cancelled though convergence has not been reached yet.
    Estimated number of trips
    If you estimate the number of trips in the corrected matrix as close as
    possible, you can reduce the number of required iterations.
    Enter the desired value.
    Alpha level
    Factor for scaling the bandwidths (see Fundamentals: Chpt. 4.4.1.1 ,
    page 212).

    PTVGROUP

    1827

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description

    Adjust OD pairs If link volumes are used and none of the routes of an OD pair uses any
    with data only
    of the counted links, data for matrix updating is missing for this OD pair.
    If this option has been checked, the given OD data is stored in the
    new output matrix.
    If this option has not been checked, the given OD data is projected
    according to the mean changes to all of the other OD relations, the
    result is stored in the new output matrix.
    Tips
    If for example only a link corridor has been counted in an extensive network and you would like to update just the corridor-using OD pairs, we
    recommend to set only the links of the corridor to the active state and to
    check this option.
    If only some individual OD pairs of lower priority do not use any of the
    counted links, we recommend to uncheck this option, since these links
    should be updated according to the general data changes.
    Adjust only
    If this option has been checked, only OD pairs that have a value difactive OD pairs ferent from 0 in the filter matrix are active (see "Creating a filter matrix"
    on page 1833). Any other OD pair is fixed and stored in the new output
    matrix without changes. The active OD pairs are adjusted in such a way
    that, as a result, the differences between old and new assignment volumes are already equalized.
    Via this button, you call a separate window for the selection of the filter
    matrix. You may select either an external matrix file or a matrix which is
    included in the version file.
    Flow matrix

    You can specify how the demand segment path information of the previous assignment shall be used for matrix correction by demand segment (see Fundamentals: Chpt. 4.4.1.1 , page 212).

    DSeg

    Demand segments selected for matrix correction


    Note
    A demand matrix refers to each demand segment (see "Connecting
    demand matrices and demand segments" on page 1607).

    1828

    PTVGROUP

    16.7.1.3 TFlowFuzzy parameters


    Element

    Description

    Load/Save

    Recalculate
    If this option is checked, the flow matrix is recalculated for this particular
    demand segment.
    Load from file
    If this option is checked, the values of a calculated flow matrix are read
    from file for this particular demand segment.
    Tip
    If you want to perform several calculation runs for a demand segment,
    using the same demand matrix, but different count data (unchanged set
    of turns, links, main turns, zones) and/or procedure parameters, we
    recommend that during the first run you calculate and save the flow
    matrix. For all subsequent runs, you can then read in the flow matrix
    again.
    Note
    Using an 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. Make sure that the following applies.
    The original matrix is identical to the matrix you used during the
    flow matrix calculation run, or it at least has the same OD pairs with
    the number of trips > 0.
    The links, zones, turns or main turns used are identical.

    File name

    Use the respective button to open a window. Depending on your Load/Save setting, you can enter or select a path and file name for the flow
    matrix you want to load (Load from file) or save (Recalculate).

    TFlowFuzzy: Output
    Element

    Description

    DSeg

    Demand segments selected for matrix correction


    Note
    Each demand segment refers to a demand matrix (see "Connecting
    demand matrices and demand segments" on page 1607).

    Save result

    To demand matrix of DSeg


    Select this option to replace the demand segment data of the existing
    demand matrix in Visum by the calculated results.
    To matrix
    If this option has been selected, the demand segment's corrected demand
    matrix is saved.

    PTVGROUP

    1829

    16.7.1.4 Performing analyses of TFlowFuzzy solution procedures

    16.7.1.4

    Element

    Description

    Output

    If option To matrix has been selected, click the button and select the
    matrix in which the result is to be stored. You may select either an external
    matrix file or a matrix which is included in the version file.

    Dec.

    Number of decimal places for the storage of matrix values

    Performing analyses of TFlowFuzzy solution procedures


    In the TFlowFuzzy procedure parameters, you can activate various analysis functions. The diagnosis returns lists which describe the conflict potential between the count locations. These
    lists are stored in the log file. Additionally, a statistics file can be output. In *.txt data format, it
    provides a statistics for each iteration which describes the current deviation between counted
    values and current demand matrix data (see "Using protocol files" on page 876 and
    "TFlowFuzzy: Parameters" on page 1826).
    The diagnosis list includes the following analyses:
    Element

    Description

    1st order analysis

    Each count location is analyzed separately. Only the proportional


    deviation of the counted value from the current assignment value is
    regarded.

    1.5 order analysis

    The counted value is compared to a fictitious assignment value. This


    assignment value is computed from the flow matrix and a demand
    matrix estimation.

    2nd order analysis The conflict potential is determined for pairs of count locations. It
    depends on both the similarity of the count locations and the difference between the counted values which are to be reached.
    Impact index

    Impact of each count object on the total result. The impact simply
    sums up from the similarities of the particular count object compared
    to the other count objects. Actually, an object whose structure is similar to many other objects can greatly impact the result.

    Example diagnosis list (incomplete)


    Diagnosis for demand segment c
    Analysis of the termination of the operation:
    Procedure termination at count object link 1000101(12394->1000057) .
    Counted value and tolerance of this count object might be problematic.
    1st order analysis
    Relative deviations between count data and assignment results taking the global trend
    into account.
    12% (GEH=0.7) for count object link 1000099(1000056->93027)
    12% (GEH=0.9) for count object link 4378(51037->12377)
    11% (GEH=1.1) for count object link 7377(93043->93046)
    11% (GEH=1.0) for count object link 7312(93025->93026)
    11% (GEH=1.1) for count object link 1000080(51044->1000046)
    11% (GEH=1.2) for count object link 1000042(12337->1000027)
    1.5 order analysis

    1830

    PTVGROUP

    16.7.1.4 Performing analyses of TFlowFuzzy solution procedures


    Relative deviations between count data and assignment results based on a simple
    matrix estimation.
    30% (GEH=7.0) for count object link 1000115(1000064->51046)
    23% (GEH=3.8) for count object link 1000050(1000031->93020)
    18% (GEH=2.1) for count object link 1000045(93023->1000029)
    16% (GEH=1.5) for count object link 4293(12342->51029)
    15% (GEH=2.3) for count object link 7298(51036->93021)
    14% (GEH=3.8) for count object link 1000101(1000057->12394)
    2nd order analysis
    Pairs of objects, which might have a conflict and thus prevent a TFlowFuzzy solution.
    21% conflict potential between count object link 7347(16362->93040) and count object
    link 7361(93040->93041)
    21% conflict potential between count object link 6376(51027->16362) and count object
    link 7361(93040->93041)
    20% conflict potential between count object link 7347(16362->93040) and count object
    link 1000053(93041->1000033)
    20% conflict potential between count object link 6376(51027->16362) and count object
    link 1000053(93041->1000033)
    19% conflict potential between count object link 4397(12384->27163) and count object
    link 1000074(12374->1000043)
    19% conflict potential between count object link 7347(16362->93040) and count object
    link 1000054(1000033->93042)
    Impact index
    Impact of count objects on the TFlowFuzzy solution.
    The greater the impact, the more global are the effects of the specified count
    values.
    Accordingly, especially the count data of objects with higher impact should be
    checked for correctness.
    42.8 for count object link 7372(93015->51032)
    42.5 for count object link 7180(51032->12336)
    42.4 for count object link 4269(12333->51026)
    42.1 for count object link 1000038(1000025->12338)
    41.7 for count object link 4277(12336->27154)
    41.3 for count object link 6764(27154->12333)

    Example statistics list (incomplete)


    TFlowFuzzy progress statistics
    number of relevant OD pairs;3193
    ;matrix statistics;;;;;;;"assignment" statistics;;;;;;;;;;;;
    ;matrix sum;max. modification;quantiles of weighted relative deviation;;;;;assignment
    values exceed tolerance range;;GEH quantiles;;;;
    iteration;;;5%;25%;50%;75%;95%;count;trips;5%;25%;50%;75%;95%
    1;27817.00;1053.43;0.07;0.07;0.07;0.07;0.07;108;31622.00;0.07;1.52;3.69;6.73;13.91
    2;30591.41;484.32;0.02;0.14;0.35;0.80;2.39;114;68294.00;0.11;1.74;3.57;6.32;11.14
    3;29497.89;171.84;0.02;0.16;0.37;0.77;1.86;59;38383.00;0.06;1.09;1.95;3.28;6.18
    4;28492.88;67.82;0.03;0.15;0.34;0.74;1.61;9;6197.00;0.03;0.46;1.19;2.40;4.58
    5;27907.55;26.24;0.03;0.14;0.34;0.72;1.49;7;6262.00;0.02;0.41;1.14;2.64;5.02
    6;27610.25;19.21;0.03;0.13;0.33;0.72;1.49;9;8147.00;0.01;0.46;1.18;2.70;5.18
    7;27458.60;15.23;0.04;0.13;0.33;0.72;1.51;7;6262.00;0.01;0.43;1.13;2.62;5.15
    8;27379.17;10.49;0.03;0.13;0.33;0.72;1.50;6;4525.00;0.04;0.39;1.13;2.62;5.12
    9;27337.42;6.75;0.03;0.13;0.34;0.73;1.50;5;2835.00;0.01;0.39;1.09;2.58;5.09
    Progress of "assignment values"

    PTVGROUP

    1831

    16.7.1.4 Performing analyses of TFlowFuzzy solution procedures


    count object number;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;39;40;41;42;43;44;45;46;47;48;49;50;51;52;53;54;55;56;57;58;59;60;61;62;63;64;65;66;67;68;69;70;71;72;73;74;75;76;77;78;79;80;81;82;83;84;85;86;87;88;89;90;91;92;93;94;95;96;97;98;99;100;101;102;103;104;105;106;107;108;109;110;111;112;113;114;115;116;117;118;119;120;121;122;123;124;125;126;127;128;129;130;131;132;133;134;135;136;137;138;139;140;141;142;143;144;145;146;147;148;149;150;151;152;153;154;155;156;157;158;159;160;161;162;163;164;165;166;167;168;169;170;171;172;173;174;175;176;177;178;179;180;181;182;183;184;185;186;187;188;189;190;191;192;193;194;195;196;197;198;199;200;201;202;203;204;205;206;207;208;209;210;211;212;213;214;215;216;217;218;219;220;221;222;223;224;225;226;227;228;229;230;231;232;233;234;235;236;237;238;239;240;241;242;243;244;245;246;247;248;249;250;251;252;253;254;255;256;257;258;259;260;261;262;263;264;265;266;267;268;269;270;271;272;273;274;275;276;277;278;279
    count object;link 2322(10202->51048) ;link 2322(51048->10202) ;link 2327(10203>51048) ;link 2327(51048->10203) ;link 4258(12329->51080) ;link 4258(51080->12329)
    ;link 4260(12330->51080) ;link 4260(51080->12330) ;link 4261(12330->51081) ;link 4261
    (51081->12330) ;link 4268(12333->51025) ;link 4268(51025->12333) ;link 4269(12333>51026) ;link 4270(12333->51028) ;link 4270(51028->12333) ;link 4271(12334->27155)
    ;link 4272(12334->51023) ;link 4273(51025->12334) ;link 4274(12335->51020) ;link 4275
    (51021->12335) ;link 4276(12335->51024) ;link 4277(12336->27154) ;link 4278(12336>51030) ;link 4278(51030->12336) ;count value+tolerance;521.0;521.0;552.0;510.0;740.0;363.0;610.0;576.0;633.0;612.0;189.0;0.0;2143.0;0.0;366.0;2266.0;136.0;201.0;142.0;73.0;1680.0;1736.0;125.0;189.0;193.0;145.0;152.0;163.0;186.0;276.0;1443.0;204.0;2674.0;235.0;126.0;70.0;60.0;162.0;118.0;2380.0;216.0;0.0;139.0;175.0;224.0;226.0;660.0;915.0;360.0;144.0;195.0;305.0;367.0;41.0;0.0;0.0;1095.0;1276.0;469.0;297.0;385.0;
    count
    value;473.0;501.0;501.0;473.0;674.0;339.0;501.0;556.0;569.0;463.0;169.0;0.0;1899.0;0.0;271.0;2031.0;49.0;151.0;122.0;45.0;1660.0;1682.0;77.0;157.0;151.0;125.0;60.0;58.0;104.0;191.0;1358.0;125.0;1944.0;71.0;54.0;49.0;40.0;123.0;88.0;2023.0;142.0;0.0;116.0;154.0;150.0;169.0;508.0;761.0;340.0;124.0;160.0;257.0;215.0;8.0;0.0;0.0;933.0;1051.0;397.0;187.0;222.0;154.0;338.0;217.0;598.0;441.0;713.0;253.0;270.0;590.0;219.0;467.0;263.0;503.0;306.0;142.0;482.0;740.0;
    count value-tolerance;425.0;481.0;450.0;436.0;608.0;315.0;392.0;536.0;505.0;314.0;149.0;0.0;1655.0;0.0;176.0;1796.0;-38.0;101.0;102.0;17.0;1640.0;1628.0;29.0;125.0;109.0;105.0;-32.0;47.0;22.0;106.0;1273.0;46.0;1214.0;-93.0;18.0;28.0;20.0;84.0;58.0;1666.0;68.0;0.0;93.0;133.0;76.0;112.0;356.0;607.0;320.0;104.0;125.0;209.0;63.0;
    iteration
    1;454.60;526.61;480.57;466.64;650.52;388.66;419.18;615.78;539.98;335.76;175.91;0.00;1771.31;0.00;187.60;1921.77;145.57;216.12;137.66;78.67;1787.86;1741.51;30.09;203.26;206.59;115.00;163.67;174.90;23.21;295.71;1362.01;218.37;1298.81;251.89;135.82;74.93;40.87;173.85;61.16;1782.93;231.63;0.00;98.85;141.68;81.02;118.84;380.78;649.23;361.41;143.51;208.72;223.22;393.06;44.84;0.00;0.00;825.19;883.24;501.99;82.15;412.60;86.00;302.51;350.76;305.78;420.44;321.05;

    1832

    PTVGROUP

    16.7.1.5 Creating a filter matrix


    The statistics show the progress of both assignment values and demand matrix during the iteration. The (fictitious) assignment values indicate the deviation from counted values and return
    the number of count locations, which are not in the required interval yet.
    Cancelled due to
    The TFlowFuzzy procedure often terminates when calculating the rows of a flow matrix. In this
    case, the termination is caused by a count object. This count object will be traced to the diagnosis list.
    16.7.1.5

    Creating a filter matrix


    If you want to update certain OD pairs in the demand matrix, create a filter matrix with the same
    dimensions as the demand matrix and with the value 0 for all OD pairs that are to be saved
    unchanged to the results matrix.
    1. Open the demand matrix you want to update (see "Opening a Visum matrix" on page 1721).
    2. Overwrite the value of all OD pairs which should remain unchanged with 0.
    3. Save the filter matrix in $V or $O format (see "Saving matrices" on page 1733).

    16.7.1.6

    Reading old TFlowFuzzy settings from file


    As for any other procedure, you may save the procedure parameter settings to a procedure
    parameter file and read the settings from an existing procedure parameter file (see "Saving
    procedure parameters to a file and loading them from a file" on page 1867).
    Additionally, you may read TFlowFuzzy settings of previous Visum versions from an a
    TFlowFuzzy file *.vsf.
    1. Make sure that the TFlowFuzzy window is open (see "Matrix correction using TFlowFuzzy"
    on page 1818).
    2. Click the Open old settings button.
    The Open window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings are read from file.

    16.7.2

    Projecting PrT path volumes


    With the help of this function you can adjust the demand matrix of a PrT demand segment to
    the count data gained from several links (see Fundamentals: Chpt. 4.4.2 , page 218).
    1. Make sure that the counted volumes are provided as AddValue data of links (see "Links:
    Basis tab" on page 1108).
    2. Make sure, that the network contains a PrT assignment result (routes via this link) and counted link data or a random sampling factor.
    3. In the Demand menu, select the Projection of Routes entry.
    The Graphics tools (Paths projection) window opens.

    PTVGROUP

    1833

    16.7.3 Calibrating a PrT matrix


    4. Make the desired changes.
    Element

    Description

    Demand segment Via the selection list you may pick the PrT demand segment,
    PrT
    whose route volumes you would like to project.
    Count data from

    Via the selection list you may pick the Link-AddValue that is
    coding the census data.

    5. Mark the desired link (see "Selecting links" on page 1112).


    In the Paths Projection window, the Number, the number of the FromNode, the Volume
    and the Counted value of the marked link are displayed and the Factor (= Counted value
    divided by PrT link volume) which is automatically calculated.
    Note: The factor is calculated each time a new link is marked.
    6. If necessary, edit the projection factor.
    7. If necessary, mark the reverse direction of the link: Click the Direction: Down button.
    8. Click the Execute button.
    All OD pairs of the demand matrix that use the marked link are recalculated with the projection factor calculated for this link. The route volumes are adjusted.
    Note: Rounding errors might cause deviations of the rounded result (for example 2
    1.3 trips = 2.6 trips is rounded to 3 trips).
    9. Mark further links, if necessary, and project the OD pairs using these links.
    Tip: You can display all OD pairs which use the selected or the projected link as flow
    bundle via the menu Graphics> Flow bundle (see "Inserting a flow bundle" on page
    2265).

    16.7.3

    Calibrating a PrT matrix


    You can use the demand matrix calibration to project a PrT demand matrix with the help of
    count data (see Fundamentals: Chpt. 4.4.3 , page 218).
    Note: You cannot combine the procedure demand matrix calibration with LUCE equilibrium assignment or Tribut equilibrium assignment.
    1. Make sure that the counted volumes are provided as AddValue data of links (see "Links:
    Basis tab" on page 1108).
    2. Make sure, that the network contains a PrT assignment result (routes via this link).

    1834

    PTVGROUP

    16.7.3 Calibrating a PrT matrix


    3. Make sure, that the existing demand matrix is an optimally generated matrix which may
    have resulted from previous counts or calculations and whose inner structure must correctly
    represent the impedance situation in the network.
    Note: Representative cross-sections can be used to compensate for significant changes (for example closing of a company with a large work force or the construction of a
    new residential area).
    4. Make sure that the network has been calibrated at the best for route choice.
    5. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    6. To the procedure sequence, at the position of your choice, add the Demand matrix calibration procedure of the Matrices category (see "Setting up and starting the procedure
    sequence" on page 1847).
    7. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select demand segment window opens.
    8. In the selection list, click the PrT demand segment whose demand matrix you would like to
    calibrate.
    9. Confirm with OK.
    The demand segment selected is listed in the Reference object(s) column.
    10. Make sure the added procedure is highlighted. Then, in the Operations section, click the
    Edit button.
    The Parameters: Matrix calibration (Lohse) window opens.
    11. Make the desired changes.
    Element

    Description

    Count data from

    Via the selection list you may pick the Link-AddValue that is
    coding the census data.

    Max. number of ite- After the user-defined number of iterations the iteration process is
    rations
    canceled though convergence has not been reached yet.
    Threshold of precision

    Criterion for termination of the multi-procedure (see Fundamentals: Chpt. 4.3.12 , page 203)
    Note
    The higher the value, the longer the computing time and the higher the precision of the calculations.

    12. Confirm with OK.

    PTVGROUP

    1835

    16.8 Reading and saving demand data


    13. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The demand matrix of the PrT demand segment selected is calibrated.
    Tip: You can verify the calibration by graphical or tabular display of the computation
    results.
    Difference between assigned link volume and count data via menu Graphics> Edit
    graphic parameters > Entry Links> Bars> Display> bar type Difference bars
    (see "Configuring a difference bar display" on page 2379).
    Statistical deviations via menu Calculate> Assignment analysis > List or Chart
    (see "Analyzing the assignment quality" on page 1879).

    16.8

    Reading and saving demand data


    The demand description includes all data coding travel demand and is stored as OD demand
    data file *.dmd.

    16.8.1

    Reading demand data from file


    There are two ways to read OD demand data
    Reading the entire OD demand data file
    Reading OD demand data additively

    16.8.1.1

    Reading the entire OD demand data file


    1. Click the

    Open icon.

    The Select file type window opens.


    Tip: Alternatively, in the File menu, point at Open and click Demand data.
    2. Select the Demand data entry.
    3. Confirm with OK.
    The Open OD demand data window opens.
    4. Select the desired file.
    5. Click the Open button.
    The Read demand data window opens.
    6. Specify whether you want to have warnings displayed when reading in data.

    1836

    PTVGROUP

    16.8.1.2 Reading OD demand data additively


    Element

    Description

    Show warnings on
    screen

    Select this option to show warnings when you load files.


    If this option is not selected, no warnings are shown when you
    load files. This will speed up the reading process.
    Note
    If in the warning settings, you selected Save warnings and
    details to the message file and in the log files, you selected Message file: Create new file, warnings are saved to a message file
    (see "Specifying settings for protocol files" on page 876).

    Display error messages on screen

    Select this option to show error messages when loading files.


    If this option is not selected, no error messages are shown
    when you load files. This will speed up the reading process.

    7. Make sure the option Read demand data file additionally is not selected.
    8. Confirm with OK.
    All existing demand objects are deleted and the new demand data is imported.
    Tip: You may also open a demand data file by clicking the selected file in the list of
    recently opened files in the File menu.
    16.8.1.2

    Reading OD demand data additively


    You can choose data from an OD demand data file and add it to the current demand description.
    1. Make sure that a version file or a network file has been opened.
    2. Click the

    Open icon.

    The Select file type window opens.


    Tip: Alternatively, in the File menu, point at Open and click Demand data.
    3. Select the Demand data entry.
    4. Confirm with OK.
    The Open OD demand data window opens.
    5. Select the desired file.
    6. Click the Open button.
    The Read demand data window opens.
    7. Decide whether warnings are to be displayed on screen during reading demand data from
    file.

    PTVGROUP

    1837

    16.8.1.2 Reading OD demand data additively


    Element

    Description

    Show warnings on
    If this option has been checked, warnings are displayed during
    reading.
    screen
    If this option has not been checked, no warnings are displayed
    during reading. This will speed up the reading process.
    Note
    If in the warning settings, you selected Save warnings and
    details to the message file and in the log files, you selected Message file: Create new file, warnings are saved to a message file
    (see "Specifying settings for protocol files" on page 876).
    Display error mesIf this option has been checked, error messages are displayed
    sages on screen during reading.
    If this option has not been checked, no error messages are displayed during reading. This will speed up the reading process.
    8. Select the option Read demand data file additionally.
    More options will be available.
    9. Make the desired changes.
    Element

    Description

    First off, determine tables in file

    If this option has been checked, the demand file tables are
    screened. Only available data tables will be listed for selection
    then.
    If this option has not been checked, all theoretically possible
    demand data tables will be provided for selection.

    Create warnings
    for conflicts in
    mode "Ignore"

    If this option has been selected, warning messages indicating


    existing network objects will be displayed on the screen during
    the reading process in the selected "Ignore" mode (see next window).
    If this option has not been selected, warnings about existing
    network objects will not be displayed on the screen during the reading process in the selected "Ignore" mode. This will speed up
    the reading process.
    Note
    To save warnings to a message file, in the warning settings,
    select Save warnings and details to the message file and in the
    log file settings, select Create new file (see "Specifying settings
    for protocol files" on page 876).

    Permit the removal of objects

    1838

    If this option has been selected, demand objects stored in


    tables with the flag $-<Name of the object type> are removed
    from the existing demand model (see "Creating a model transfer

    PTVGROUP

    16.8.1.2 Reading OD demand data additively


    Element

    Description
    file" on page 908).
    If this option has not been selected, tables that are labeled
    $<Object type name> will be ignored.

    Show statistics of Select this option to have Visum create a model transfer file while
    modifications
    reading in a new file. The model transfer file contains all changes
    that are made according to the new file.
    The file is saved to the project directory specified for model transfer files, under the name <Current version name> - ReadNetwork.tra. It opens
    automatically after it is read in.
    10. Confirm with OK.
    The Read demand data additively window opens.
    Note: Visum files cannot be written in all languages the Visum program interface is
    available in. (You can currently write the files in English, French, German, Italian, and
    Polish.) The language you show the program interface in is displayed in the Display
    language section. Here you can specify whether the text entries in the column
    Demand objects (Table) are to be displayed in the language you have chosen or in
    the language of the demand file which is to be read.
    11. Select the data tables you want to read additionally to your current network.
    Element

    Description

    Column to the left

    If this option is checked the particular table will be read additionally to the given demand data.
    If this option is not checked the particular table will be ignored.

    Demand objects
    (Table)

    List of data tables required for demand description. Due to current


    option First off, determine tables in file setting, this list contains
    either any possible table or only those stored with the demand
    data file to be read from file additionally.

    Check all

    Via this button, you may check all tables.

    Uncheck all

    Via this button, you may uncheck all tables.

    12. Decide for each data table, how demand objects are to be read if the current network does
    already contain a demand object with identical object key.
    Note: Key attributes are attributes which serve for unique identification of demand
    objects (see "Save list to attribute file" on page 2325).

    PTVGROUP

    1839

    16.8.1.2 Reading OD demand data additively


    Element

    Description

    Conflict avoidance

    If this option has been checked, you can - in the Conflict handling column - modify the value of the key attribute in a way that
    makes the value unique.
    If this option has not been checked or if it is not provided, you
    can - in the Conflict handling column - choose how to handle
    demand objects with identical keys.

    Conflict handling
    (if Conflict avoidance is checked)

    According to the data type of the key attribute, enter an alphanumerical prefix value or a numerical offset value.
    Prefix
    To an alphanumerical key attribute, you can add an alphanumerical prefix in the first position.
    Offset
    To the value of a numerical key attribute you can add a constant
    value.

    Conflict handling
    (if Conflict avoidance is not
    checked or not provided)

    From the selection list, select the appropriate option for handling
    of demand objects with identical key.
    Ignore
    Demand objects of the demand data file with identical keys will
    be ignored as the existing demand objects. The existing network
    objects and their attribute values remain unchanged.
    Overwrite object
    Existing demand objects for which the OD demand data file contains demand objects with identical keys, are replaced by the
    objects read from file. Attribute values of attributes which are not
    contained in the OD demand data file are set to a standard value.
    Note
    When importing data tables of the demand objects Matrices, Standard time series and Demand time series the existing data will be
    deleted before reading the new data records:
    All matrix values are set to 0.
    Time series elements are deleted
    Zone type-based time series are deleted
    Overwrite attributes
    Existing demand objects for which the OD demand data file contains demand objects with identical keys are kept but their attribute values are replaced. Attribute values of attributes which are
    not contained in the OD demand data file are kept.
    Notes
    The same applies to the import of data tables of the demand
    objects Matrices, Standard time series and Demand time series.

    1840

    PTVGROUP

    16.8.1.2 Reading OD demand data additively


    Element

    Description
    The existing matrix values, time series elements or zone typebased time series are kept before reading the data.
    Attributes values can only be added to the current time series elements, if the origin interval index and the destination interval
    index have not been changed.
    Cancel
    Reading is cancelled.

    Tips: Alternatively you may specify the settings for multiple data tables at the same
    time by marking the tables and clicking the Edit button (see "Setting options for multiple data tables" on page 1841).
    Alternatively you may read the settings from a parameter file for additive demand data
    reading (*.adrp) (see "Opening settings for Read demand data additively" on page
    1842).
    You may save these settings (see "Saving settings for Read demand data additively"
    on page 1842)
    Notes: The demand objects Matrices, Standard time series and Demand time series
    (see "Managing demand objects" on page 1606) are described in two tables. The first
    table includes the so-called header data and the second table the actual OD demand
    data.
    Matrices: Header data table matrix and data table matrix entries
    Standard time series: Header data table time series and data table time series
    item
    Demand time series: Header data table demand time series and data table zone
    type-based time series
    Header data tables and data tables can be read separately. For example, if you read
    only the header data table of the matrices, the matrix values will not be read. If you
    only read the data table of the matrices, the values will be read according to the key of
    the current matrices without changing the header data.
    13. Confirm with OK.
    Demand data is read from file.
    Tip: You may also open a demand data file by clicking the selected file in the list of
    recently opened files in the File menu.
    Setting options for multiple data tables
    1. Make sure that the Read demand data additively window is open (see "Reading OD
    demand data additively" on page 1837).

    PTVGROUP

    1841

    16.8.2 Saving demand data


    2. Press the CTRL key and keep it pressed.
    3. In the list of tables, mark the entries you would like to edit.
    4. Click the Edit button.
    A window opens.
    5. Make the desired settings (see "Reading OD demand data additively" on page 1837).
    6. Confirm with OK.
    The settings are used for the selected tables.
    Saving settings for Read demand data additively
    1. Make sure that the Read demand data additively window is open (see "Reading OD
    demand data additively" on page 1837).
    2. Make sure the desired options are set (see "Reading OD demand data additively" on page
    1837).
    3. Click the Save button.
    The Save parameters for additive demand reading window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The settings are saved to an *.adrp file.
    Opening settings for Read demand data additively
    1. Make sure that the Read demand data additively window is open (see "Reading OD
    demand data additively" on page 1837).
    2. Click the Open button.
    The Open parameters for additive demand reading window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings are read from file.

    16.8.2

    Saving demand data


    Note: When you save demand data, attribute values are saved with a specific number of
    decimal places (see "Settings for decimal places and aggregate functions" on page 960).
    1. Click the

    Save as icon.

    The Select file type window opens.


    Tip: Alternatively, from the File menu, choose Save as. Then click Demand data.

    1842

    PTVGROUP

    16.8.2 Saving demand data


    2. Select the Demand data entry.
    3. Confirm with OK.
    The Save demand data window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The Save demand (user-defined) window opens.
    6. If necessary, reduce the amount of data to be saved to file.
    Element

    Description

    Hiding calculated
    attributes

    If this option has been selected, the calculated attributes are


    hidden and are not saved.
    If this option has not been selected, calculated attributes are
    equally saved.
    Tip
    Saving calculated attributes can be useful for further evaluation
    purposes, such as an analysis in a database.
    Note
    Calculated attributes are ignored during the reading process.

    Hide attribute with


    If this option has been checked, only selected attributes are
    default values
    saved with their values.
    Tip
    Use this option to reduce file size.
    If this option has not been checked, all of the selected attributes are saved with their values not regarding whether attribute
    value and default value are identical or not.
    Note
    You can find the default attribute values in the Attribute.xls file,
    under ...\Program files\PTV Vision\PTV Visum 13\Doc.
    Hiding empty
    tables

    If this option has been selected, only tables with entries will be
    saved.

    7. Select the data tables you want to save to file.


    Element

    Description
    The table has been selected and will be saved to file.
    The table has not been selected and will not be saved to file.

    All tables ON

    PTVGROUP

    Via this button, you may check all tables.


    Note

    1843

    16.8.2 Saving demand data


    Element

    Description
    The status of the attributes in the tables remains unchanged.

    All tables OFF

    Via this button, you may uncheck all tables except $VERSION.
    Note
    The status of the attributes in the tables remains unchanged.

    8. Click a table name.


    The table attributes are displayed.
    Tip: Click the CTRL key and keep it pressed while clicking multiple tables one by one
    to show the attributes of these tables simultaneously.
    Note: Due to current option settings in the upper section of the window possibly not all
    of the attributes might be displayed by table.
    9. Select the attributes you want to save to file.
    Element

    Description
    The attribute has been selected and is saved to file.
    The attribute has not been selected and is not saved to file.
    The attribute is a key attribute and cannot be switched off.
    Key attributes are attributes which serve for unique identification of
    demand objects.
    The attribute is a mandatory attribute and cannot be excluded.

    Attribute
    groups

    Via this button you can either select or switch off predefined groups of
    attributes in a separate window (see "Selecting or deselecting groups
    of attributes for saving data" on page 1845).

    Standard

    Select all readable attributes

    Tip: Alternatively, you may read selected tables and attributes from a demand data file
    *.dmd (see "Reading layout from demand data file" on page 1846)
    10. Confirm with OK.
    The Store matrices to window opens.
    Note: The window only opens if you have selected the data table Matrix entries.
    11. Specify for each matrix whether the matrix is saved to the demand data file or as separate
    matrix file.

    1844

    PTVGROUP

    16.8.2 Saving demand data


    Element

    Description

    Format

    (in DMD)
    If this option has been checked, the particular matrix is saved to the
    demand data file.
    Binary, Format V, Format O, Format E, Format S
    If one of these options has been selected, the selected matrix will be
    saved as separate matrix file in the selected format (see "Visum-specific
    matrix file formats" on page 2678). In the demand data file, only a reference to this matrix is saved.

    File name

    File name and - if applicable - the directory for the matrix which is to be
    saved as a separate matrix file
    button you call the Save matrix file window.
    Via the
    Notes
    If you have chosen another format than (in DMD) for a matrix, you will
    have to enter a file name.
    The path needs only to be entered if the matrix is not to be saved to the
    directory specified for this file type (see "Editing the storage location of
    files" on page 837).
    Tip
    For file name handling, Copy & Paste can be used.

    12. Confirm with OK.


    Demand data is saved according to the current settings.
    Selecting or deselecting groups of attributes for saving data
    1. Make sure that the Save demand data file (user-defined) window is open (see "Saving
    demand data" on page 1842).
    2. Click the Attribute groups button.
    The Save selected groups of attributes window opens.
    3. In the selection list, mark the predefined attribute group you would like to save to file or to
    exclude from saving.
    4. Click the desired button.
    Element

    Description

    Activate

    All attributes of the selected groups are enabled.

    Switch off

    Except key attributes and mandatory attributes, all attributes of the


    selected group are excluded from saving data to file

    Activate exclusively

    All attributes of the selected group are activated for saving data to
    file and all attributes of other groups - except key attributes and
    mandatory attributes - are excluded from saving data to file.

    PTVGROUP

    1845

    16.8.2 Saving demand data


    5. Click the Close button.
    According to the current settings, the attributes are either selected or deselected.
    Saving selected demand data as layout
    You can save the selected tables and attributes x as demand file data *.dmd without content
    and read it later as default.
    1. Make sure that the Save demand data file (user-defined) window is open (see "Saving
    demand data" on page 1842).
    2. Click the Save layout button.
    The Save demand data window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    Selected tables and attributes are saved as data block templates without data.
    Reading layout from demand data file
    You can read a selection of tables and attributes from a demand data file or from a demand
    data file without content which is saved as layout.
    1. Make sure that the Save demand data file (user-defined) window is open (see "Saving
    demand data" on page 1842).
    2. Click the Open layout button.
    The Open OD demand data window opens.
    3. Select the desired file.
    4. Click the Open button.
    The tables and attributes contained in the demand data file are adopted.

    1846

    PTVGROUP

    17 Setting the procedure sequence

    17

    Setting the procedure sequence


    Using a procedure sequence in Visum makes it possible to execute several work steps successively. In the framework of a procedure sequence, you can perform extensive calculations
    overnight or throughout several days, if applicable.
    Examples for procedures in the procedure sequence: Opening files, calculating results, saving
    results, checking results, 'Go To' to a previous position in the procedure sequence or saving
    results.
    A procedure sequence includes several pre-defined procedures with specific user-defined procedure settings. Additionally you can adjust the general procedure settings which apply to all
    procedures.
    Some of the procedures provided in Visum can be applied to both PrT and PuT tasks, whereas
    others are either PrT-specific or PuT-specific (see "Setting and calculating the parameters for
    PrT assignment" on page 1931 and "Setting and calculating PuT assignment parameters" on
    page 2006).
    Finally you can call the calculation state which provides the list of the calculated procedures.
    Subjects
    Setting up and starting the procedure sequence
    Adjusting the general procedure settings
    Saving procedure parameters to a file and loading them from a file
    Calculating general procedures (PrT and PuT)
    Displaying the calculation status

    17.1

    Setting up and starting the procedure sequence


    According to the steps outlined below, select the procedures for the procedure sequence, edit
    the procedures and execute them:
    Opening the procedure sequence
    Adding procedures to the procedure sequence
    Forming and naming groups
    Duplicating procedures or groups
    Rearranging the order of procedures and groups in the list
    Setting procedures or groups to the active or inactive state
    Editing procedures
    Entering a comment or code for a procedure
    Deleting a listed procedure or column
    Executing procedures in the procedure sequence

    17.1.1

    Opening the procedure sequence


    On the toolbar, click the
    button Open 'Procedure sequence' window. Alternatively,
    from the Calculate menu, choose > Procedure sequence.
    The 'Procedure sequence' window opens.

    PTVGROUP

    1847

    17.1.2 Adding procedures to the procedure sequence

    (1) Procedure sequence toolbar


    Using the buttons in the toolbar, you can save a procedure sequence to file or load it from file,
    execute either selected procedures or the entire procedure sequence, and reset the current
    procedure or adjust the general procedure settings.
    (2) List of procedures in the procedure sequence
    This list includes all procedures selected by the user. They are arranged in the order in which
    they are executed by default, as far as they are active. You can define whether just a single
    procedure is to be executed or all procedures, or the marked procedures, or all procedures
    until a marked procedure alternatively.
    (3) Operations of the procedure sequence
    In this section you can find the operations which are provided for the procedure sequence.
    Use the buttons to add procedures or to edit or delete them, among others. You can also move
    them up and down in the list or define groups.
    (4) View options for groups
    Via this icon, you specify the view options for groups.

    17.1.2

    Adding procedures to the procedure sequence


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. If procedures are already available, click the row in the list in the procedure sequence window below which you would like to add another procedure.
    3. In the Operations section, select Create.
    The Procedure window opens.
    1848

    PTVGROUP

    17.1.2 Adding procedures to the procedure sequence


    4. Select the desired procedure from the appropriate folder. The following procedures are provided:
    Notes: For each procedure, the settings are described in the appropriate chapter. The
    table below lists the appropriate references.
    Some procedures are only displayed if you have activated the respective add-on
    module (see "Enabling or disabling installed add-ons" on page 886).
    For some procedures you need to select a file for data reading or saving, respectively
    (see "Opening and saving a project directories file" on page 838).
    Folder Assignments
    Procedure

    Description

    Init assignment

    Deletes the assignment results (see "Deleting PrT/PuT assignment results" on page 1879)

    PrT assignment

    Calculates PrT assignments (see "Setting and calculating


    the parameters for PrT assignment" on page 1931)

    PuT assignment

    Calculates PuT assignments (see "Setting and calculating


    PuT assignment parameters" on page 2006)

    Connection import

    Reads PuT connections from file (see "Connections:importing" on page 2560)

    Route import

    Reads PrT routes for a demand segment from file (see


    "Importing routes" on page 2561)

    Extended route import

    Reads externally calculated assignment results from file (see


    "Extended route import" on page 2562)

    Set signal programs

    Resetting the signal programs of all external controls to the


    active signal program for the given time, and input of the
    daily signal program list to be used (see "Editing a signal
    control in Vissig" on page 2528 and "Editing a signal control
    of the RBC type" on page 1470).

    Update impedances at Re-calculates impedances of nodes and main nodes (see


    node
    "Updating the impedances at all nodes and main nodes" on
    page 1073)
    Signal cycle and green Calculation of the optimum cycle time for signal control at the
    time optimization
    node and at the same time an optimal green time split for this
    cycle time (see "Optimizing signal cycle and split times for
    active nodes" on page 1921)
    Optimization of the
    signal control offset

    Calculation of the signal offset optimization for signal controls (see "Signal timing optimization and coordination" on
    page 1921)

    SC offset analysis

    Analyses signal timing optimization (see "SC offset analysis"

    PTVGROUP

    1849

    17.1.2 Adding procedures to the procedure sequence


    Folder Assignments
    Procedure

    Description
    on page 1925)

    Assignment analysis

    Analyses the quality of an assignment (see "Calculating


    general procedures (PrT and PuT)" on page 1878)

    Folder Demand model


    Procedure

    Description

    Trip generation

    Calculates stage 1 (Trip generation) of the Standard 4-Step


    model (see "Starting the iterative repetition" on page 1697)

    Trip distribution

    Calculates stage 2 (Trip distribution) of the Standard 4-Step


    model (see "Calculating trip distribution" on page 1643)

    Mode choice

    Calculates stage 3 (Mode choice) of the Standard 4-Step


    model (see "Calculate mode choice" on page 1649)

    Nested mode choice

    Calculates the nested mode choice model (see "Calculating


    nested mode choice" on page 1653)

    Time-of-day choice

    Distributes the demand to time intervals (see "Calculating


    Time-of-day choice" on page 1658)

    EVA trip generation

    Calculates the trip generation of the EVA-P model (see "Calculating EVA trip generation" on page 1666)

    EVA weighting

    Calculates evaluation of the EVA-P model (see "Calculating


    EVA weighting" on page 1671)

    EVA distribution/mode
    choice

    Calculates distribution and mode choice of the EVA-P model


    (see "Calculating EVA trip distribution and mode choice" on
    page 1680)

    Tour-based model - trip Calculates the trip generation of the Tour-based Model
    generation
    (VISEM) (see "Calculating Tour-based model - Trip generation" on page 1684)
    Tour-based Model Calculates trip distribution and mode choice of the Tourcombined trip disbased Model (VISEM) (see "Calculating tour-based model tribution / mode choice combined trip distribution and mode choice" on page 1689)
    Estimate gravitation
    parameters (KALIBRI)

    1850

    Estimates parameters of the utility function of the gravity


    model (see "Estimate gravitation parameters (KALIBRI)" on
    page 1703)

    PTVGROUP

    17.1.2 Adding procedures to the procedure sequence


    Folder PuT Analyses
    Procedure

    Description

    Init PuT operating indicators

    Deletes calculated PuT operating indicator data (see


    "Discarding calculated PuT operating indicators" on page
    2166)

    PuT operating Indicators

    Calculates PuT operating indicator data (see "Revenue calculation using a fixed revenue per PTripUnlinked" on page
    2167)

    Init line blocking

    Deletes calculated PuT line block versions (see "Initializing


    PuT line blocking" on page 2118)

    Line blocking

    Calculates PuT line blocking (see "Executing the line


    blocking procedure" on page 2104)

    PuT interlining matrix

    Generates skim matrices for interlining trip relations between


    stop points (see "Performing the PuT interlining matrix procedure" on page 2148)

    Calculate service trip


    patterns

    Calculates groups of regular services (see "Calculate service trip patterns" on page 2086)

    Folder PuT Passenger Surveys


    Procedure

    Description

    Read survey data

    Reads survey data by PuT demand segment from file


    (see "Read survey data" on page 2055)

    Plausibilization of survey data

    Checks and completes survey data (see "Plausibilization of


    survey data" on page 2059)

    Direct assignment

    Assigns plausible paths by PuT demand segment to the network (see "Assignment of survey data" on page 2071)

    Folder Matrices
    Procedure

    Description

    Save demand matrix


    from route volumes

    Saves partial matrices (see "Saving partial matrices during


    the execution of the procedure sequence" on page 1739)

    Demand matrix calibration

    Projects a PrT demand matrix with the help of census data


    (see "Calibrating a PrT matrix" on page 1834)

    Demand matrix correction (TFlowFuzzy)

    Adjusts demand matrix data to current count data (see


    "Matrix correction using TFlowFuzzy" on page 1818)

    Calculate PrT skim


    matrix

    Calculates PrT skim matrices (see "Calculating:PrT skims"


    on page 1984)

    Calculate PuT skim

    Calculates PuT skim matrices (see "Calculating PuT skims"

    PTVGROUP

    1851

    17.1.2 Adding procedures to the procedure sequence


    Folder Matrices
    Procedure

    Description

    matrix

    on page 2073)

    Open matrix

    Reads matrix data from file (see "Importing matrix values


    during execution of the procedure sequence" on page 1770
    and "Adding up matrix values during the procedure
    sequence run" on page 1780)

    Save matrix

    Saves matrix data to file (see "Saving matrices during procedure sequence execution" on page 1738)

    Edit matrix

    Modifies matrix data according to stored matrix processing


    steps (see "Editing matrix values using a log file during the
    procedure sequence run" on page 1775)

    Combination of matrices and vectors

    Combines matrices and attribute vectors (see "Combining


    matrices and attribute vectors during the procedure
    sequence run" on page 1799)

    Method of successive
    averages over matrices

    Calculates the mean value from two matrices (see "Calculating the weighted mean of matrices" on page 1700)

    Matrix processing

    Allows for multiple matrix operations (see "Editing matrix


    values" on page 1761 and "Using matrix values for calculations" on page 1776)

    Matrix aggregation

    Generates main zone matrix based on aggregated values of


    a zone matrix (see "Calculating a main zone matrix from a
    zone matrix" on page 1808)

    Matrix disaggregation

    Disaggregates main zone matrix data and stores values in


    zone matrix (see "Calculating a zone matrix from a main
    zone matrix" on page 1808)

    Distribution of demand Distributes matrix values as volumes to paths (see "Dismatrix to paths
    tribution of demand matrix to paths" on page 1886)

    Note: The AddIn folder contains scripts provided together with Visum(see "Embedding add-ins automatically via a project directory" on page 2667).
    Folder Miscellaneous

    1852

    Procedure

    Description

    Edit attribute

    Allows for editing the attribute data of all or all active network
    objects of the selected network object type (see "Editing attribute values during a procedure sequence" on page 990)

    Method of successive

    Calculates the mean value from the attribute values of all or

    PTVGROUP

    17.1.2 Adding procedures to the procedure sequence


    Folder Miscellaneous
    Procedure

    Description

    averages (MSA) for


    attributes

    all active network objects of the selected network object type


    (see "Calculating the weighted mean of attributes" on page
    1701)

    Set run and dwell times Re-calculates the run and dwell times of all or all active time
    profiles (see "Setting time profile times during a procedure
    sequence" on page 1326)
    Set link run times from Replaces the link run time data by line run time data (see
    line run times
    "Generating link run times from line run times in a procedure
    sequence" on page 1133)
    Read filter

    Reads filter settings from file (see "Reading filters during a


    procedure sequence" on page 1026)

    Initialize all filters

    Resets all active filters (see "Initializing all filters during a procedure sequence" on page 1024)

    Go to the procedure

    Checks the convergence of current results and starts the iterative repetition of procedures, if applicable (see "Go to a procedure in the procedure sequence (GoTo procedure)" on
    page 1697)

    Run script

    Runs a Visual Basic script (see "Integrating script files or


    script code into the procedure sequence" on page 2668)

    NCHRP 255

    Performs post-processing of PrT assignment results (see


    "NCHRP 255 (Post-processor for PrT assignments)" on page
    1983)

    HBEFA-based emission calculation

    Emission data calculation according to HBEFA (see "Settings for emission calculation according to HBEFA" on page
    2191)

    Init HBEFA-based emis- Deletes HBEFA-based emission results (see "Resetting


    sion calculation
    emission calculation" on page 2203)
    Save version

    Saves version data file (see "Saving a version file" on page


    841)

    Group

    Forms a group of procedures in the procedure sequence


    (see "Forming and naming groups" on page 1854)

    Intersect

    Calculates target attribute values by intersecting the source


    attribute (see "Intersecting objects" on page 2217)

    Convert paths

    Converts paths (see "Converting the paths of a path set or


    demand segment" on page 1233)

    Territory indicators

    Calculates basic territory indicators (see "Calculating basic


    territory indicators" on page 1885)

    PTVGROUP

    1853

    17.1.3 Forming and naming groups


    5. Adjust the settings required by the procedure, e.g. reference objects, variants or files.
    6. For changes to the parameter settings of the selected procedure, mark the procedure and,
    in the Operations section, click Edit.
    Thus, the procedure has been defined. In the columns Reference object(s) and Variant/file,
    the specified settings are displayed.
    Note: The procedure sequence is stored if you close the window with OK. An error message appears if the parameters for one or several procedures have not been specified
    correctly. In this case, the procedure sequence is not stored.

    17.1.3

    Forming and naming groups


    Several consecutive procedures can be bundled in a group. You can show or hide the procedures of a group.
    Notes: Grouping of procedures does not take effect on the procedure sequence.
    For the Go to procedure, a group name can be used as target (see "Go to a procedure in
    the procedure sequence (GoTo procedure)" on page 1697).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the list, mark the row under which the group shall be created.
    3. In the Operations section, select Create group.
    For the group, another row is added to the list of procedures. All subsequent procedures in the
    list until the start of the next group are added to the group.
    Note: In the group's Reference object(s) column, the numbers of the rows belonging to
    the group are displayed.
    Naming a group
    Once a group has been created, the name Group unnamed group appears in the Procedure
    column, and Unnamed group appears in the Comment column. You can edit these names.
    1. In the group's row, click in the Comment column.
    2. Enter the desired name.
    3. Press the ENTER key.
    In the Procedure column, the entered name appears behind Group.

    17.1.4

    Showing or hiding the procedures of a group


    To arrange the list more clearly, you can fade out the procedures of a group. Furthermore, you
    can shift and delete groups
    1. In the list, double-click in the group's row outside of the Procedure column.

    1854

    PTVGROUP

    17.1.5 Duplicating procedures or groups


    The procedures forming the group are hidden. Three dots are added to the group name.
    2. In the list, double-click in the group's row outside of the Procedure column.
    The procedures forming the group are shown.
    Tip: Alternatively, you can click the buttons in the View section.

    17.1.5

    Duplicating procedures or groups


    You can duplicate one procedure or several consecutive procedures or a group of procedures.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the list, mark the row(s) you would like to duplicate.
    Note: Groups have to duplicated one by one.
    3. In the Operations section, click the Duplicate button.
    Below the selected rows, the copies of the selected rows are added to the list of procedures.

    17.1.6

    Rearranging the order of procedures and groups in the list


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the list, mark the row(s) you would like to shift to another position.
    Note: Groups have to be shifted one by one.
    3. In the Operations section, click either button Up or button Down.
    Each marked procedure is accordingly shifted by one row. A group is shifted to the position on
    top or below the next group, as applicable.

    17.1.7

    Setting procedures or groups to the active or inactive state


    You may set procedures or groups in the procedure sequence to the active state or to the inactive state. Active procedures and groups are directly executed. Due to the kind of execution,
    inactive procedures are not executed or a warning message has to be confirmed prior to the
    execution. By default, procedures and groups are active.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the row of the procedure or group, click the checkbox in the Active column.
    The state of the particular procedure or group toggles from inactive to active or vice versa.
    PTVGROUP

    1855

    17.1.8 Editing procedures


    Notes: When changing the state of a group, the state of each procedure belonging to the
    group automatically changes accordingly.
    If a group consists of both active and inactive procedures, the checkbox in the group's
    row appears grey.
    In the Operations section you can click the buttons Set all active or Set all inactive, as
    applicable, to set all procedures and group to the desired state at the same time.

    17.1.8

    Editing procedures
    You can replace a selected procedure by another procedure and edit the procedure parameters.
    Replacing one procedure by another
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the row of the procedure or group you want to replace, click in the Procedure column.
    The Procedure window opens.
    3. Select the desired procedure from the appropriate category.
    4. Click the OK button.
    The procedure is replaced.
    5. If applicable, adjust the required procedure settings.
    The procedure is edited.
    Editing the procedure parameters
    1. In the list, mark the procedure for which you would like to adjust the parameter settings.
    2. In the Operations section, click the Edit button.
    The Parameters: <Procedure> window opens.
    3. Edit the parameter settings.
    Notes: The Edit button is only provided for procedures whose parameters are subject to
    changes.
    The parameters are described with the particular procedure (see "Adding procedures to
    the procedure sequence" on page 1848).
    Editing reference object(s) or variant/file entries
    1. In the row of the procedure for which you would like to edit the entries, click in the Reference object(s) column or in the Variant/file column.
    2. Adjust the desired settings.

    1856

    PTVGROUP

    17.1.9 Deleting a listed procedure or column


    Entering a comment or code for a procedure
    1. In the row of the procedure for which you would like to enter a comment or code, click in the
    Comment column or in the Code column.
    2. Enter the desired comment or code.
    Comment and/or code appear in the list.

    17.1.9

    Deleting a listed procedure or column


    You can delete one or several procedures or a group in the procedure sequence.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the list, mark the procedures or the groups you would like to delete.
    Note: Groups have to deleted one by one.
    3. Click the Delete button.
    The selected procedures or the selected group are deleted in the list of procedures.
    Note: With a group, also the corresponding procedures are deleted.

    17.1.10 Unlocking a group of procedures


    You can unlock a group of procedures.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Right-click the group that you want to unlock.
    The shortcut menu opens.
    3. Click the Marked group> Unlock entry.
    The group is unlocked. The group row is deleted. The procedure rows are retained.

    17.1.11 Executing procedures in the procedure sequence


    You have the following possibilities to execute procedures in the procedure sequence:
    Executing a single procedure
    Executing all active procedures
    Executing marked procedures
    Executing all procedures until a certain procedure
    A prerequisite for executing procedures is that you have inserted at least one procedure (see
    "Adding procedures to the procedure sequence" on page 1848).

    PTVGROUP

    1857

    17.1.11.1 Executing a single procedure


    Prior to the execution Visum verifies, whether the parameters have been set correctly for the
    procedures. An error message appears if an error has been detected. In this case, the procedure sequence is not executed.
    Status information on execution of the procedure is displayed in the Procedure sequence window, in the following columns:
    Success: The entry x indicates that the recent execution was successful.
    StartTime: Indicates the start time of the last procedure carried out. The data is overwritten when you rerun the procedure.
    EndTime: Indicates the end time of the last procedure carried out. The data is overwritten
    when you rerun the procedure.
    Messages: Warnings and error messages that were returned during the execution of the
    procedure. These are listed even if the output of warnings is suppressed (see "Specifying
    settings for protocol files" on page 876).
    ResultMessage: Final message including additional information about the executed procedure.
    The execution of the procedure sequence can be recorded to the log file (see "Using protocol
    files" on page 876). If an error occurs during the execution, an error message will appear and
    the procedure sequence will be terminated at this point. For corresponding information please
    refer to the message file.
    17.1.11.1 Executing a single procedure
    1. In the Execution column, use the mouse key to drag the blue arrow head to the row of the
    (active or inactive) procedure which you want to execute.
    2. On the toolbar, click the

    button Single step.

    The procedure is executed. As long as the procedure is being executed, the blue arrow head
    appears filled in the Execution column. Once the procedure is executed, the arrow head is placed in the row of the next active procedure in the list.
    Note: You can set the blue arrow head to a procedure of either state. Prior to the execution of an inactive procedure, a warning appears. Confirm this warning, otherwise you
    cannot execute an inactive procedure.
    17.1.11.2 Executing all active procedures
    1. In the procedure sequence list, set all procedures and/or groups to the active state, which
    you want to execute.
    2. In the execution column, drag the blue arrow head to the row of the first active procedure in
    the list.
    3. On the toolbar, click the

    Start icon.

    As long as the procedure is being executed, the blue arrow head appears filled in the Execution column. Once the calculation finished, the arrow head is placed in the row of the next
    active procedure in the list.

    1858

    PTVGROUP

    17.1.11.3 Executing marked procedures


    Tip: You can also run all active procedures when the Procedure sequence window is
    closed. On the Functions toolbar, click
    button Start - Execute all active procedures
    (see "Tool bars" on page 823). The Procedure sequence window opens and you can
    view the progress of the procedure.
    17.1.11.3 Executing marked procedures
    1. In the list of procedures, mark the procedures which are to be executed. The position of the
    blue arrow head in the Execution column is irrelevant.
    2. Right-click at any position in the list.
    The shortcut menu opens.
    3. Click Execute marked procedures.
    The marked procedures are executed. Once the calculation finished, the arrow head is placed
    in the row of the next active procedure underneath the marking.
    17.1.11.4 Executing all procedures until a certain procedure
    1. Use the mouse key to drag the blue arrow to the row of the first one of the procedures which
    are to be executed. The state of the procedure is not regarded.
    2. Further down in the list, mark the procedure until which all procedures are to be calculated.
    3. Right-click at any position in the list.
    The shortcut menu opens.
    4. Click Execute until the marked procedure.
    From the blue arrow head until the marked procedure, all procedures are highlighted. If the
    selection includes inactive procedures, the execution of these procedures will be queried.
    5. Click Execute all, if procedures of either state are to be executed. Click Execute only
    active ones, if only the active procedures are to be executed.
    17.1.11.5 Resetting status information of the procedures run
    In the columns Success, StartTime, EndTime , Duration, Messages, and Result Message ,
    you can reset the status information of all procedures carried out.
    Resetting status information of individual procedures
    1. In the procedure sequence, select the procedures of your choice.
    2. Right-click a selected row.
    The shortcut menu opens.
    3. Click Marked procedures > Reset status information.
    The status information for the selected procedures is reset.

    PTVGROUP

    1859

    17.2 Adjusting the general procedure settings


    Resetting status information of all procedures run
    1. Right-click a procedure in the procedure sequence.
    The shortcut menu opens.
    2. Click Reset status information.
    The status information for all procedures run is reset.

    17.2

    Adjusting the general procedure settings


    For the calculations performed during the execution of procedures, you can adjust various
    general settings:
    Defining the analysis period to which the calculations refer (see "Defining the analysis
    period" on page 1860)
    Defining the analysis time intervals to which you can distribute the calculated results (see
    "Defining analysis time intervals" on page 1861 and "Saving assignment results by analysis time interval" on page 1863)
    Note: For analysis period and analysis time intervals, the temporal context is of significant importance in Visum(see Fundamentals: Chpt. 3.2.4 , page 101).
    Setting parameters for skim matrices (see "Setting metadata for skim matrices" on page
    1865)
    Further PrT-specific settings and PuT-specific settings are provided for the calculations.
    Specific settings for Private Transport (PrT) (see "Settings for the PrT user model" on page
    1888)
    Specific settings for Public Transport (PuT) (see "Settings for the PuT user model" on page
    1995)

    17.2.1

    Defining the analysis period


    The analysis period represents the space of time to which all evaluations refer. The analysis
    period can only be edited if a calendar is used (see "Selecting a calendar " on page 1511). If
    you have not selected a calendar, the analysis period automatically covers a single day.
    Note: The analysis period settings are saved with the procedure parameters (see
    "Saving procedure parameters to a file and loading them from a file" on page 1867).
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. In the Analysis period section, make the settings of your choice.

    1860

    PTVGROUP

    17.2.2 Defining analysis time intervals


    Element

    Description

    From

    Start of the analysis period

    To

    End of the analysis period

    Note: The analysis period lasts at least one day and may cover the entire calendar
    period at most, i.e. a week in case of a weekly calendar or the entire calendar period
    in case of an annual calendar (see "Selecting a calendar " on page 1511). The analysis period must lie completely within the calendar period.
    4. Confirm with OK.
    The analysis period is stored.

    17.2.2

    Defining analysis time intervals


    Within the analysis period, you may define analysis time intervals. For the dynamic PrT assignments DUE and the dynamic-stochastic assignment as well as for the timetable-based PuT
    assignment you can calculate the results by analysis time interval (see Fundamentals: Chpt.
    3.2.4.1 , page 102).
    Each analysis time interval needs to lie completely within a calendar day of the analysis
    period.
    Notes: If you want to calculate and store assignment results for each analysis time interval, you need to check the appropriate option PrT or PuT in the section Use for calculated results. If this option has not been checked, the results are summed up for the
    entire assignment time interval.
    The distribution of the results to the individual analysis time intervals increases both the
    computation time and the required storage space.
    The analysis time intervals are saved with the procedure parameter settings (see "Saving
    procedure parameters to a file and loading them from a file" on page 1867).

    17.2.2.1

    Creating a single analysis time interval


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. Click the Create button.
    A new row is added to the list of analysis time intervals.
    4. Make the desired changes.
    Note: To edit the data, double-click in the cells.

    PTVGROUP

    1861

    17.2.2.2 Creating multiple successive analysis time intervals


    Column

    Description

    Code

    Short name for the analysis time interval


    Notes
    The code needs to be unique.
    Automatically, the first four digits of the From time entry are used for
    a new interval (displayed as hhmm). Prior to the time, either the weekday or the date appears, if a calendar is used.

    From time

    Start of the interval (input format: hh, hh:mm or hh:mm:ss)

    To time

    End of the interval (input format: hh, hh:mm or hh:mm:ss)

    Day

    Via the selection list you select the day if a calendar is used.
    Weekly calendar: Weekday on which the interval occurs.
    Annual calendar: Date of day on which interval occurs.

    Name

    Name of the analysis time interval (optional)


    Note
    For a new interval, the name is automatically formed from From time
    and To time. If you are using a calendar, the weekday or date are
    shown before the time period.

    Tip: You may arrange the analysis time intervals in chronological order (see "Sorting
    analysis time intervals chronologically" on page 1863).
    5. Confirm with OK.
    The analysis time intervals are stored.
    17.2.2.2

    Creating multiple successive analysis time intervals


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. Click the Multiple button.
    The Create multiple analysis time intervals window opens.
    4. Enter the desired data.
    Element

    Description

    Number

    Number of time intervals you would like to create

    Interval length Duration of the individual analysis time intervals in minutes


    Note
    You may add the unit to the duration (h, min, s).

    1862

    PTVGROUP

    17.2.2.3 Sorting analysis time intervals chronologically


    Element

    Description

    First from-time Start of the first analysis time interval


    Note
    Prior to the time, either the weekday or the date appears, if a calendar is used.
    5. Click the Create button.
    The analysis time intervals are created.
    Note: Code and Name are automatically set for each analysis time interval. Depending on the calendar set, the entry in the Code and Name boxes are different. To
    change the automatically set entries, click the respective box.
    6. Confirm with OK.
    The analysis time intervals are stored.
    17.2.2.3

    Sorting analysis time intervals chronologically


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. Click the Sort button.
    The analysis time intervals are sorted according to date and time.
    4. Confirm with OK.
    The order is stored.

    17.2.2.4

    Deleting a single analysis time interval


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. In the list of analysis time intervals, click the row you would like to delete.
    4. Click the Delete button.
    The analysis time interval is deleted.
    5. Confirm with OK.
    The settings are stored.

    17.2.3

    Saving assignment results by analysis time interval


    You can decide that the assignment results are to be saved by analysis time interval.
    1. From the Calculate menu, choose General procedure settings.

    PTVGROUP

    1863

    17.2.4 Aggregating results of analysis time intervals


    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. Define the desired time intervals (see "Defining analysis time intervals" on page 1861).
    4. Next to Use for calculated results, check the desired option.
    Element

    Description

    PrT

    The PrT assignment results are saved by analysis time interval.

    PuT

    The PuT assignment results are saved by analysis time interval.

    5. Confirm with OK.


    The changes are applied. When an assignment is calculated, the results are stored by analysis time interval.

    17.2.4

    Aggregating results of analysis time intervals


    You can show aggregated data across multiple analysis time intervals. To do so, you can
    create additional analysis time intervals, assign them existing time intervals, and specify an
    aggregation function. Using these time intervals, you can output data for more than a day.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Analysis time slots entry.
    3. In the Analysis time intervals list, add new rows for the aggregations desired (see "Creating
    a single analysis time interval" on page 1861 and "Creating multiple successive analysis
    time intervals" on page 1862).
    4. In the Aggregated column, select the option.
    5. In the Derived from column, click the

    button.

    The window Specify composition of the aggregated analysis time interval opens. On the
    left, the analysis time intervals used for aggregation are displayed. On the right, the analysis time intervals not used are displayed.
    6. In the section on the right, select the analysis time intervals you want to use for aggregation.
    Then click the

    button to move them to the section on the left.

    Note: To simultaneously select multiple analysis time intervals, hold down the C TRL
    key.
    7. Confirm with OK.
    8. In the Aggregation column, click the aggregation function of your choice.

    1864

    PTVGROUP

    17.2.5 Setting metadata for skim matrices


    Element

    Description

    Avg

    Mean value of all attribute values

    Sum

    Sum of all attribute values

    Maximum

    Maximum of all attribute values

    Minimum

    Minimum of all attribute values

    9. Confirm with OK.


    The aggregated results can be viewed in lists and the Network editor.
    Note: On the Analysis time intervals toolbar, in the list box, you can select aggregated
    analysis time intervals (see "View by analysis time interval" on page 821). In the animated view and when you use the toolbar buttons, the aggregated analysis time intervals
    are skipped.

    17.2.5

    Setting metadata for skim matrices


    You can configure certain settings for the calculation of PrT (see Fundamentals: Chpt. 6.6 ,
    page 311) and PuT (see Fundamentals: Chpt. 7.4 , page 456) skim matrices.
    Note: Skim matrices can be generated with the procedures Calculate PrT skim matrix
    (see "Calculating:PrT skims" on page 1984) and Calculate PuT skim matrix (see "Calculating PuT skims" on page 2073). For PuT, you may additionally calculate and save
    skim matrices simultaneously with an assignment (see "Calculating skim matrices during
    an assignment" on page 2078).
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the desired entry.
    Entry

    Description

    PrT settings>
    Skims

    On this page, you set metadata for PrT skim matrices. Each row
    contains the settings for a specific PrT skim matrix type.

    PuT settings >


    Skims

    On this page, you set metadata for PuT skim matrices. Each row
    contains the settings for a specific PuT skim matrix type.

    3. For the desired matrix type, edit the desired entry in the particular column.
    Element

    Description

    Skim

    Name of the skim


    The entries are not subject to changes.

    File extension

    Standard file extension of the output file

    PTVGROUP

    1865

    17.2.5 Setting metadata for skim matrices


    Element

    Description
    Note
    Please note that renaming a file extension may cause identification problems, since the manual and PTV Vision Support
    refer to standard file extensions.

    Diagonal

    Via this button, you set the value for the main diagonal by matrix
    type. The button labels indicate the current settings (see "Specifying main diagonal values of a matrix type" on page 1866).

    Ignored OD pairs

    Standard entry for OD pairs which according to the filter settings


    are not taken into account for skim matrix calculation

    OD pairs without
    paths

    Standard entry for OD pairs for which no path could be found

    Minimum

    Minimum permitted value. This value will be used instead of smaller calculated values.

    Maximum

    Maximum permitted value. This value will be used instead of greater calculated values.

    Decimal places

    Number of decimal places (09)

    4. Confirm with OK.


    The changes are applied.
    Specifying main diagonal values of a matrix type
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the desired entry.
    Entry

    Description

    PrT settings>
    Skims

    On this page, you set metadata for PrT skim matrices. Each row
    contains the settings for a specific skim matrix type.

    PuT settings >


    Skims

    On this page, you set metadata for PuT skim matrices. Each row
    contains the settings for a specific skim matrix type.

    3. In the desired row, click the button in the Diagonal column.


    The Set main diagonal for skim <matrix type> window opens.
    4. Make the desired changes.

    1866

    PTVGROUP

    17.3 Saving procedure parameters to a file and loading them from a file
    Element

    Description

    With constant
    value

    If this option has been checked, the constant value entered here
    is applied to the cells of the main diagonal.

    From attribute

    If this option has been checked, the numerical zone attribute


    which is to be selected via the button is applied to the cells of the
    main diagonal.

    Row/column mini- If this option has been checked, the minimum value to be found in
    mum
    the corresponding row and column is applied to each cell of the
    main diagonal.
    Mean value of n
    row/column
    minima

    If this option has been checked, the mean value calculated from
    other values of the zone is applied to each cell of the main diagonal. For a zone X, the value is calculated as follows: In a first
    step, the mean values are calculated from the two values each
    between zone X and any other zone J (vxj and vjx). Then, the
    mean value calculated from the n smallest values of those mean
    values is used as value in the main diagonal.

    Number of values for mean value calculation


    Note
    The number needs to be 1 and may not reach the number of
    zones.

    Factor

    Multiplication factor for all values in the main diagonal

    5. Confirm with OK.


    The settings for the main diagonal of this matrix type are changed.

    17.3

    Saving procedure parameters to a file and loading them from a file


    You can save the procedure sequence and procedure parameters to load them again later.
    Therefore, two data file formats are provided, *.par and *.xml.
    The file format *.par is a binary format, which stores the general settings (Calculate menu>
    General procedure settings) and the procedure sequence with the corresponding settings
    (Calculate menu> Procedure sequence).
    The file format *.xml is a text format, its structure is similar to the COM model. However, this format has not yet been implemented for all procedures. Thus, if a procedure sequence is saved
    in *.xml format, the file will contain the complete sequence but no further information for those
    procedures which have not been fully implemented yet (see "Data format of the procedure
    parameter file *.xml" on page 1871).
    Note: Procedure parameter files in the *.xml format can be accessed via COM (read and
    write access).

    PTVGROUP

    1867

    17.3.1 Saving procedure parameter settings to file

    17.3.1

    Saving procedure parameter settings to file


    Procedure parameter files can be stored in either window: General procedure settings and
    Procedure sequence.
    1. Open either the Procedure sequence or the General procedure settings window.
    2. Adjust the desired settings, if applicable.
    3. In the procedure sequence, click the Save procedure parameters to file button. In the
    General procedure settings window, click the Save button.
    The Save: Procedure parameters window opens.
    4. Select the desired file or enter path and file name.
    5. In the File type drop-down list, select the desired entry.
    Note: Procedure parameter settings you may save to file either in *.par or in *.xml data
    format. Format *.xml does not yet include all of the provided procedures (see "Overview of the XML elements and XML attributes" on page 1873).
    6. Click the Save button.
    Note: If the *.xml format has been selected and the procedure sequence includes procedures that have not yet been fully implemented in this format, a warning appears.
    You may confirm this message by clicking the No warnings button. In this case, the
    file is saved without further warnings. Alternatively, you may confirm this message via
    the OK button. Before the file is saved, a warning appears for each procedure which
    has not yet been implemented.
    The procedure sequence and the procedure parameter settings are saved to the selected
    parameter file.
    Tip: You may save the procedure parameter settings also via menu File> Save as> file
    type Procedure parameters.

    17.3.2

    Reading procedure parameter settings from file


    You can read procedure parameter settings from a file in *.par format or from a file in *.xml format.
    Reading procedure parameter settings from *.par file
    Reading procedure parameter settings from *.xml file
    Data format of the procedure parameter file *.xml

    17.3.2.1

    Reading procedure parameter settings from *.par file


    You may open a procedure parameters file provided in *.par format. Decide whether to read
    only the procedure sequence or just the general settings or both items. Procedure parameter
    files can be opened in either window: General procedure settings and Procedure sequence.
    1. Open either the Procedure sequence or the General procedure settings window.

    1868

    PTVGROUP

    17.3.2.2 Reading procedure parameter settings from *.xml file

    2. In the procedure sequence, on the toolbar, click the


    button Load procedure parameters from file.... In the General procedure settings window, click the Open button.
    The Open: Procedure parameters window opens.
    3. Select the file you want to open.
    4. Click the Open button.
    The Read procedure parameters window opens.

    5. Select the desired options.


    Element

    Description

    Procedure
    sequence

    The procedure sequence is read from file. The current procedure


    sequence is replaced.

    General procedure
    settings

    The general procedure settings are read from file. The current
    procedure settings are replaced.

    6. Confirm with OK.


    According to your settings, the procedure parameters are read from file.
    17.3.2.2

    Reading procedure parameter settings from *.xml file


    You can open procedure parameters in the *.xml format. You then specify whether you want to
    overwrite your current settings, read the file additively, or read in the procedure parameters at
    a specific point of the procedure sequence. Procedure parameter files can be opened in either
    window: General procedure settings and Procedure sequence.
    1. Open either the Procedure sequence or the General procedure settings window.
    2. In the procedure sequence, on the toolbar, click the
    button Load procedure parameters from file.... In the General procedure settings window, click the Open button.
    The Open: Procedure parameters window opens.
    3. Select the desired file.
    4. Click the Open button.
    The Read procedure parameters window opens.
    5. Select the desired option.

    PTVGROUP

    1869

    17.3.2.2 Reading procedure parameter settings from *.xml file


    Element

    Description

    Procedure
    sequence

    Select this option to additively load the procedures from the procedure parameters file into the current procedure sequence.
    Replace the procedure sequence
    Select this option to delete all procedures currently in the procedure sequence and add the procedures of the procedure parameters file.
    Note
    This option is only available if you selected Procedure
    sequence.
    Replace existing procedures in the same position, add others
    Select this option to add the procedures of the procedure parameters file to the current procedures. In the procedure sequence
    rows with identical number are replaced.
    Notes
    Restrictions apply to the analysis time intervals in the procedure
    parameter settings file. An analysis time interval is not read from
    file, if its code is identical with a code of an existing time interval
    or if it overlaps with an existing time interval.
    This option is only available if you selected Procedure
    sequence.
    Insert as new procedures after position
    Select this option to add the procedures at the beginning of a
    procedure sequence, before all existing procedures, or behind a
    specific procedure within the procedure sequence. In the dropdown list, select the desired entry.
    Notes
    Group structures of the procedure sequence are not considered.
    If you add one or several procedures to a procedure that is part
    of group, the group is extended by the procedures added. GoTo
    procedures within the procedure sequence are adapted.
    This option is only available if you selected Procedure
    sequence.

    General procedure
    settings

    Select this option to adopt the general procedure settings from


    the procedure parameters file.
    Note
    Do not select this option to merely add procedures to an existing
    procedure sequence, without wanting to change the general procedure settings of the version.

    6. Confirm with OK.


    The settings are read from the procedure parameter file.
    1870

    PTVGROUP

    17.3.2.3 Data format of the procedure parameter file *.xml


    Note: You may automatically open a procedure parameter settings file when the program
    session is started (see "Editing user preferences" on page 867).
    17.3.2.3

    Data format of the procedure parameter file *.xml


    Note: Files in *.xml format you can open with a text editor or in a browser. Use a text-processing editor for changes to those files.
    Example: Procedure parameter file (incomplete)
    <?xml version = "1.0" encoding = "UTF-8"?>
    <PROCEDURES VERSION="5">
    <OPERATIONS>
    <OPERATION
    NO = "1"
    OPERATIONTYPE = "InitAssignment"
    ACTIVE = "1"
    COMMENT = "">
    <ASSIGNMENTINITPARA
    INITPUT = "1"
    </OPERATION>
    <OPERATION
    NO = "2"
    OPERATIONTYPE = "PrTAssignment"
    ACTIVE = "1"
    COMMENT = "">
    ...
    </OPERATION>
    <OPERATION
    NO = "3"
    ...
    ...
    </OPERATIONS>
    <FUNCTIONS>
    <PUTSKIMMATRIXSETTINGS
    USELONGLENGTH = "0"
    USESECONDS = "0"
    USESECONDSIMP = "0"
    PATHLEGATTRIBUTE = "LINEROUTE\ADDVAL1"
    PATHLEGAGGREGATETYPE = "MAX"
    DISCOMFORTPARAA = "7.500"
    DISCOMFORTPARAB="4,500">
    <SINGLESKIMMATRIXSETTINGS
    NAME = "JOURNEYTIME"
    ...
    />
    ...
    </PUTSKIMMATRIXSETTINGS>
    <PRTSKIMMATRIXSETTINGS
    USELONGLENGTH="0"
    <USERDEFSKIM>
    ...
    </USERDEFSKIM>
    ...
    </PRTSKIMMATRIXSETTINGS>

    PTVGROUP

    INITPRT = "1"

    />

    USESECONDS="0">

    1871

    17.3.2.3 Data format of the procedure parameter file *.xml


    ...
    </FUNCTIONS>
    </PROCEDURES>

    Brief introduction to the *.xml data format


    An *.xml file contains XML elements, whose names are in brackets. Normally, an XML element
    starts with the start tag <NAME> and ends with the end tag </NAME>. For example, the procedure parameters file contains the comprehensive XML element <PROCEDURES>.
    An XML element may contain further XML elements between the two tags. Thus, the XML elements are structured hierarchically. In the procedure parameter file, the XML element
    <PROCEDURES> includes the two secondary XML elements <OPERATIONS> and
    <FUNCTIONS>.
    The start tag of an XML element may contain XML attributes coding information on the XML
    element. They have the structure NAME="Value" and follow the name of the XML element,
    separated by a blank each. For example, the XML element <PROCEDURES> contains the
    XML attribute VERSION="3".
    Notes: For a better overview, subordinate XML elements are indented compared to their
    superior XML element. Some of the browsers allow for hiding and showing subordinate
    elements of an XML element, use the sign next to the start tag for toggling.
    An element without subordinate elements does not necessarily need an end tag. The
    spelling is <NAME/>.
    Structure of the procedure parameters file *.xml
    The procedure parameters file contains the comprehensive XML element <PROCEDURES>.
    This contains the two subordinate XML elements <OPERATIONS> and <FUNCTIONS>. The
    XML element <OPERATIONS> describes the settings in the Procedure sequence window,
    whereas the XML element <FUNCTIONS> describes the settings in the General procedure
    settings window.
    The XML element <OPERATIONS> contains the subordinate elements with the name
    <OPERATION>. These code a row of the procedure sequence each, and thus either a procedure or a group header. Each of the XML elements <OPERATION> has the following XML
    attributes: NO (consecutive number), OPERATIONTYPE (Name of the procedure or "Group")
    and COMMENT (Comment).
    If the XML element <OPERATION> codes a procedure, it has the attribute ACTIVE additionally, which indicates whether the procedure is active or not. If the XML element
    <OPERATION> codes a group, it has the attribute ISEXPANDED, which indicates whether the
    procedures of the group are faded in or out. Some XML elements contain further XML attributes, e.g. those coding the specific selected procedure variant.
    XML elements <OPERATION> coding procedures with further settings have subordinate elements with specific XML attributes.
    The end of the settings description for the Procedure sequence window is indicated by the
    end tag </OPERATIONS>.

    1872

    PTVGROUP

    17.3.2.3 Data format of the procedure parameter file *.xml


    The XML element <FUNCTIONS> codes the settings in the General procedure settings window. For each navigator entry, a subordinate element is stored.
    Note: All of the XML elements and also the XML attributes of the procedure parameters
    are named in English (see "Overview of the XML elements and XML attributes" on page
    1873).
    Overview of the XML elements and XML attributes
    The tables below list the allocation of the procedures in the procedure sequence (see "Adding
    procedures to the procedure sequence" on page 1848) to the names of the XML elements and
    XML attributes.
    Folder Assignments
    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Init assignment

    InitAssignment

    <ASSIGNMENTINITPARA>

    PrT assignment

    PrTAssignment

    Equilibrium
    assignment

    PRTASSIGNMENTVARIAN- <EQUILIBRIUMPARA>
    T=
    "Equilibrium"

    Equilibrium
    assignment
    LUCE

    PRTASSIGNMENTVARIAN- <LUCEPARA>
    T=
    "LUCE"

    Assignment
    with ICA

    PRTASSIGNMENTVARIAN- <ASSIGNMENTICAPARA>
    T=
    "ICA"

    Equilibrium_
    Lohse

    PRTASSIGNMENTVARIAN- <EQUILIBRIUMLOHSEPARA>
    T=
    "Equilibrium_Lohse"

    Stochastic
    assignment

    PRTASSIGNMENTVARIAN- <STOCHASTICPARA>
    T=
    "Stochastic"

    TRIBUT - Equi- PRTASSIGNMENTVARIAN- (not available yet)


    librium assiT="Tribut"
    gnment
    TRIBUT - Equi- PRTASSIGNMENTVARIAN- (not available yet)
    librium_
    T=
    Lohse
    "TributEquilibrium_Lohse"
    Dynamic
    User Equilibrium (DUE)

    PTVGROUP

    PRTASSIGNMENTVARIAN- <DUEPARAMETERS>
    T=
    "Dynamic User Equilibrium"

    1873

    17.3.2.3 Data format of the procedure parameter file *.xml


    Folder Assignments
    Procedure
    Dynamic stochastic assignment
    PuT assignment

    1874

    XML attribute
    OPERATIONTYPE

    Subordinate element

    PRTASSIGNMENTVARIAN- <DYNSTOCHASTICPARA>
    T=
    "DynStochastic"
    PuTAssignment

    TSys-based

    PUTASSIGNMENTVARIAN- (not available yet)


    T=
    "TSys-based"

    HWay-based

    PUTASSIGNMENTVARIAN- <HEADWAYBASEDASSIGNMENTPART=
    AMETERS>
    "Headway-based"

    Timetablebased

    PUTASSIGNMENTVARIAN- <TTBASEDASSIGNMENTPARAMETET=
    RS>
    "Timetable-based"

    Connection
    import

    ConnectionImport

    No subordinate element

    Route import

    RouteImport

    (not available yet)

    Extended route
    import

    Extended RouteImport

    <PRTEXTROUTEIMPORTPARA>

    Set signal programs

    Set Signal Programs

    <SETSIGNALPROGRAMSPARA>

    Update impedances at node

    UpdateImpedancesAtNode

    No subordinate element

    Signal cycle and


    green time optimization

    Signal timing optimization

    No subordinate element

    Optimization of
    Signal coordination optithe signal control mization
    offset

    No subordinate element

    SC offset analysis

    Analyzing signal coordination

    No subordinate element

    Assignment analysis

    AssignmentAnalysis

    (not available yet)

    PTVGROUP

    17.3.2.3 Data format of the procedure parameter file *.xml


    Folder Demand model
    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Trip generation

    TripGeneration

    <TRIPGENERATIONPARA>

    Trip distribution

    TripDistribution

    <TRIPDISTRIBUTIONPARA>

    Mode choice

    ModeChoice

    (not available yet)

    Nested mode
    choice

    NestedModeChoice

    (not available yet)

    Time-of-day choice

    TimeOfDayChoice

    (not available yet)

    EVA trip generation EVA TripGeneration

    <EVAGENERATIONPARA>

    EVA weighting

    EVA Weighting

    <EVAWEIGHTINGPARA>

    EVA distribution/mode
    choice

    EVA Distribution/Mode
    Choice

    <EVAMODECHOICEPARA>

    Tour-based model - VISEM TripGeneration


    trip generation

    <VISEMGENERATIONPARA>

    Tour-based Model combined trip distribution / mode


    choice

    <VISEMCOMBINEDPARA>

    VISEM Combined

    Estimate gravitation Estimate gravitation para- ESTIMATEGRAVITATIONPARAMETERparameters


    meters (KALIBRI)
    SPARA
    (KALIBRI)

    Folder PuT Analyses


    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Init PuT operating indicators

    InitPuTOperatingIndicators

    <INITPUTOPINDPARA>

    PuT operating Indicators

    PuTOperatingIndicators

    <PUTOPINDPARAMETERS>

    Init line blocking

    InitLineBlockCalc

    <INITLINEBLOCKINGPARA>

    Line blocking

    LineBlockCalc

    <LINEBLOCKINGCALCPARA>

    PuT interlining matrix

    PuTInterliningMatrix

    (not available yet)

    Calculate service trip


    patterns

    CalculateServiceTripPatterns

    (not available yet)

    PTVGROUP

    1875

    17.3.2.3 Data format of the procedure parameter file *.xml


    Folder PuT Passenger Surveys
    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Read survey data

    ReadSingleRowSurveyData

    <READSINGLEROWSURVEYDATAPARA>

    Plausibilization of
    survey data

    Survey Data Plausibility

    <PLAUSIPARA>

    Direct assignment

    Direct Assignment

    <DIRECTASSIGNMENTPARA>

    Folder Matrices

    1876

    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Save demand
    matrix from route
    volumes

    SaveMatrixFromRouteVolumes

    (not available yet)

    Demand matrix cali- MatrixCalibration


    bration

    (not available yet)

    Demand matrix cor- TFlowFuzzy


    rection (TFlowFuzzy)

    <TFLOWFUZZYPARA>

    Calculate PrT skim


    matrix

    PrTSkimMatrixCalculation

    <PRTSKIMMATRIXPARA>

    Calculate PuT skim


    matrix

    PuTSkimMatrixCalculation

    <PUTASSIGNMENTPARABASE>

    Open matrix

    OpenMatrix

    <MATRIXREADPARA>

    Save matrix

    SaveMatrix

    <SAVEMATRIXTOFILEPARA>

    Edit matrix

    EditMatrix

    <MATRIXCHANGEPARA>

    Combination of
    matrices and vectors

    CombinationOfMatrices

    <LINCOMBPARA>

    Method of successive averages


    (MSA) of matrices

    AverageCalculationOverMatrices

    <MSAPARA>

    Matrix processing

    MatrixOperation

    <MATRIXOPPARA>

    Matrix aggregation

    MatrixAggregation

    <MATRIXAGGREGATEPARA>

    Matrix disaggregation

    MatrixDisaggregation

    <MATRIXDISAGGREGATEPARA>

    Distribution of
    demand matrix to
    paths

    DistributeMatrixToPaths

    <DISTRIBUTEMATRIXTOPATHSPARA>

    PTVGROUP

    17.3.2.3 Data format of the procedure parameter file *.xml

    Folder Add-Ins
    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    <all procedures>

    AddIn

    <ADDINPARA>

    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Edit attribute

    EditAttribute

    <EDITATTRIBUTEPARA>

    Method of successive averages(MSA) of


    attributes

    AverageCalculationOverAttributes

    <MSAPARA>

    Set run and


    dwell times

    UpdateTravelTimes

    (not available yet)

    Set link run


    times from line
    run times

    UpdateLinkTravelTimesWithLineTravelTimes

    <UPDATELINKTRAVELTIMESFROMLINESPARA>

    Read filter

    ReadFilter

    <READFILTERPARA>

    Initialize all filters

    InitAllFilters

    No subordinate element

    Go to the procedure

    Goto

    <JUMPBACKPARA>

    Run script

    Script

    <EXECUTESCRIPTPARA>

    NCHRP 255

    NCHRP255

    (not available yet)

    HBEFA-based
    emission calculation

    Calculate HBEFA Emissions

    (not available yet)

    Folder Miscellaneous

    Init HBEFAInit HBEFA emissions


    based emission
    calculation

    (not available yet)

    Save version

    <SAVEVERSIONPARA>

    SaveVersion

    Incremental pro- IncrementalPropagation


    pagation

    <INCREMENTALPROPAGATIONPARA>

    Group

    Group

    <GROUPPARA>

    Intersect

    Intersect Attribute

    <INTERSECTATTRIBUTEPARA>

    PTVGROUP

    1877

    17.4 Calculating general procedures (PrT and PuT)


    Folder Miscellaneous
    Procedure

    XML attribute
    OPERATIONTYPE

    Subordinate element

    Convert paths

    Convert Paths

    <CONVERTPATHSPARA>

    Territory indicators

    TerritoryIndicators

    No subordinate element

    The table below shows the allocation of sub-items of the XML element <FUNCTIONS> (in
    alphabetical order) to navigator entries in the General procedure settings window.

    17.4

    XML element

    Navigator entry in the General procedure settings


    window

    <ANALYSISTIMES>

    Analysis time slots

    <BLOCKINGBACKPARA>

    PrT settings > Blocking back model

    <IMPEDANCEFUNCTIONS>

    PrT settings > Impedance

    <NODEIMPEDANCEPARA>

    PrT settings > Node impedances

    <PRTGENERALPARA>

    PrT settings

    <PRTSKIMMATRIXSETTINGS>

    PrT settings> Skims

    <PRTVOLUMESPARA>

    PrT settings > Assignment

    <PUTREVENUESPARA>

    PuT settings > Revenues

    <PUTSKIMMATRIXSETTINGS>

    PuT settings > Skims

    <PUTVOLUMESPARA>

    PuT settings > Assignment

    <SIGNALCOORDINATIONPARA>

    PrT settings > Signal offset optimization

    <SIGNALOPTIMIZATIONPARA>

    PrT settings > Signal cycle and split optimization

    <VDFUNCTIONSPARAMETERS>

    PrT settings > Volume-delay functions

    <VOLUMESPARA>

    Volumes

    Calculating general procedures (PrT and PuT)


    Some of the procedures that can be selected for the procedure sequence apply to both private
    transport and public transport:
    Deleting PrT/PuT assignment results
    Analyzing the assignment quality
    Calculating basic territory indicators
    Distribution of demand matrix to paths

    1878

    PTVGROUP

    17.4.1 Deleting PrT/PuT assignment results


    Note: Specific PrT procedures and specific PuT procedures are described separately.
    Procedures of the PrT user model (see "Settings for the PrT user model" on page
    1888)
    Procedures of the PuT user model (see "Settings for the PuT user model" on page
    1995)
    Procedures of the PuT operator model (see "Settings for the PuT operator model" on
    page 2091)

    17.4.1

    Deleting PrT/PuT assignment results


    During a procedure run the PrT assignment and PuT assignment results can be deleted either
    separately or at the same time.
    Note: Alternatively, you may delete all assignment results (PrT and PuT) via menu Calculate> Initialize assignment.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the procedure Init assignment from the Assignments category to the given order of
    procedures in the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. In the row of the added procedure, click in the Variant/file column and select the desired
    entry in the selection list.
    Element

    Description

    PrT

    Existing PrT assignment results are deleted.

    PuT

    Existing PuT assignment results are deleted.

    All

    All existing assignment results are deleted

    None

    None of the assignment results are deleted.

    Note: If PrT assignment results are deleted also those attribute values might be reset
    which were modified during an assignment with ICA calculation, for example.
    4. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment results are deleted according to the order in the procedure sequence.

    17.4.2

    Analyzing the assignment quality


    Assignment analysis means a comparison of two numerical attributes. Usually, calculated assignment results are compared to observed values, e.g. count data. The assignment analysis
    can be applied to PrT (see "Assignment analysis PrT" on page 446) and PuT (see "Assignment analysis PuT" on page 528) assignment results.

    PTVGROUP

    1879

    17.4.2.1 Calculating assignment analysis


    As a result, a statistical evaluation is returned as a chart or in tabular form.
    17.4.2.1

    Calculating assignment analysis


    Assignment analysis means a comparison of two numerical attributes of one of the following
    network object types: Links, nodes, turns, main nodes, main turns, PuT lines, line routes,
    screenlines, time profiles, paths.
    Notes: At least three observed values > 0 are required.
    The observed values need to be different from the volume that has been calculated. The
    same observed value may not occur twice.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. To the procedure sequence, at the position of your choice, add the Assignment analysis
    procedure of the Assignments category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Make sure that the added procedure has been marked and click the Edit button.
    The Parameters: Assignment analysis window opens.
    4. In the Network object selection list, select the desired network object type.
    5. Make sure, that the Basis tab has been selected.

    6. Make the desired changes.

    1880

    Element

    Description

    Model attribute

    Via this button, you select the numerical attribute of the network
    object type that stores the calculated data, e.g. Volume PrT [Veh]
    or vCur-PrTSys.

    Observed value

    Via this button, you select the numerical attribute of the network
    object type, that stores the observed data, e.g. counted volumes

    PTVGROUP

    17.4.2.1 Calculating assignment analysis


    Element

    Description
    or measured speeds.

    Only objects with


    observed value >
    0

    If this option has been checked, only network objects with


    observed value data> 0 are regarded for calculation.

    Only active network objects

    If this option has been checked, only active network objects


    are regarded for calculation.

    If this option has not been checked, all objects are included in
    the calculation. In the calculation, network objects without observed value are included with value0.

    If this option has not been checked, all objects are included in
    the calculation.
    Classification by:

    If this option has been checked, the assignment analysis is performed by class. The classes are created according to the values
    of an attribute of the selected network object type, which is to be
    selected via the button, e.g. Type or TSysSet. For each value of
    the selected classification attribute that occurs in the considered
    objects (active/observed/all objects of the selected network object
    type), a class is generated automatically.
    Note
    All attributes of the Integer, String, or SingleEnum data type can
    be selected as classification attributes.
    If this option has not been checked, the analysis is performed
    for all network objects to be considered in just a single class.

    7. Select the Tolerances tab.

    8. Make the desired changes.

    PTVGROUP

    1881

    17.4.2.1 Calculating assignment analysis


    Element

    Description

    Use tolerances

    If this option has been checked, the calculated values and the
    observed values are compared with the help of the user-defined
    permitted tolerance per user-defined value class.
    A calculated value that is in the tolerance range of the value class
    of the observed value is accepted. The share of acceptable relative errors can be displayed in the output list. The tolerances are
    displayed in the output chart.
    If this option has not been checked, tolerances are not regarded.

    Max GEH

    Based on the user-defined value, the share of network objects


    with acceptable GEH value is determined.

    withM: calculated value


    C: observed value (Counted)
    Observed value

    In this column, you define the upper limit of the value range, for
    which the tolerances are to be defined in the neighboring column.
    Notes
    Double-click in the selected cell to edit the value.
    Take care, that the user-defined classes comply with the value
    range of the selected attribute.
    After closing the window and opening it again, the rows will be
    sorted according to this column.

    Tolerance

    In this column, define the tolerance range as percentage for each


    value range.
    Note
    Double-click in the selected cell to edit the value.

    Standard

    Use this button to reset the tolerances to standard values for


    volume / permitted deviation (according to Report 255 National
    Cooperative Highway Research Program).
    NCHRP 255 ADT
    Standard values per day
    NCHRP 255 Hourly
    Standard values per hour
    Note
    The tolerance ranges are identical for both options.

    1882

    Create

    Via this button, you can add a class.

    Delete

    Via this button, you can delete the currently selected class.

    PTVGROUP

    17.4.2.2 Viewing assignment analysis results in a list


    9. Confirm with OK.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment analysis is executed.
    Note: The calculation results are saved merely in a temporary data structure. They are
    dismissed immediately when repeating the procedure sequence or initializing an assignment result which was used as a basis.
    17.4.2.2

    Viewing assignment analysis results in a list


    You can display the assignment analysis results as a list. If the analysis was performed in the
    classified way, each data row contains the values of a class.
    1. In the Calculate menu, select the Assignment Analysis> List command.
    The List (Assignment analyses) window opens.

    Note: You may design the layout of the list and start the data output (see "Working with
    lists" on page 2299).
    17.4.2.3

    Viewing assignment analysis results in a scatter diagram


    1. In the Calculate menu, click the Assignment Analysis> Chart entry.
    The Assignment Analysis Chart window opens.

    2. Click the Settings button.


    PTVGROUP

    1883

    17.4.2.4 Exporting the assignment analysis chart


    The Chart settings window opens.

    3. Make the desired changes.


    Element

    Description

    X-axis

    Min observed value


    Minimum value displayed along the x-axis
    Max observed value
    Maximum value displayed along the x-axis
    Note
    If no value has been entered, Visum automatically scales the x-axis
    according to the current data range.

    Y-axis

    Y = calculated value
    Along the y-axis, the calculated attribute values are displayed.
    Y = absolute error
    Along the y-axis, the absolute difference between calculated value
    and observed value is displayed.
    Y = relative error
    Along the y-axis, the relative difference between calculated value and
    observed value is displayed as percentage.

    Show legend

    If this option has been checked, the legend is displayed.

    Show grid

    If this option has been checked, the grid is displayed.

    Preview

    Via this button, you can view the scatter diagram according to the current settings without closing the window.

    4. Confirm with OK.


    The changes are applied.
    17.4.2.4

    Exporting the assignment analysis chart


    1. In the Calculate menu, click the Assignment Analysis> Chart entry.
    The Assignment Analysis Chart window opens.

    1884

    PTVGROUP

    17.4.3 Calculating basic territory indicators


    2. Click the Export button.
    The Export diagram window opens.
    3. Make the desired changes.
    Element

    Description

    Copy chart to clip- Uncompressed bitmap


    board
    If this option has been checked, the chart is exported as uncompressed bitmap.
    Vector graphics
    If this option has been checked, the chart is exported as vector
    graphics.
    Copy
    Click this button to copy the selected chart to the clipboard.
    Tip
    Subsequently, you may import this chart in another application.
    Export chart as
    file

    Save
    Click this button to export the chart as image file.
    Note
    In the Save image file window, you may chose one of the following formats: *.emf, *.jpg or *.bmp.

    4. Click the Close button.

    17.4.3

    Calculating basic territory indicators


    For user-defined territories you may calculate basic indicators. These indicators include Link
    length and Number of served stops, for example.
    The calculation regards the boundaries of territories precisely in the case of links for example, just the portion of the link that lies within a territory is counted (see Fundamentals: Chpt.
    3.1.9 , page 63).
    Notes: The indicators available are provided in the files IndicatorSource.xls and IndicatorAvailability.xls, under ...\Program files\PTV Vision\PTV Visum 13\Doc\Eng.
    For public transport in particular, further indicators can be calculated (see "Carrying out
    the procedure PuT operating indicators" on page 2156).
    1. From the Calculate menu, choose Procedure sequence.
    The Procedure sequence window opens.
    2. Add the procedure Territory indicators from the Miscellaneous category to the given order
    of procedures in the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).

    PTVGROUP

    1885

    17.4.4 Distribution of demand matrix to paths


    3. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The territory indicators are calculated. You will find the results in the Territories - basis list in
    the list of territories (see "Opening a list" on page 2299).
    Note: The territory indicators VehKmTravPrT (Vehicle kilometers traveled PrT) and
    VehHourTravPrT (Vehicle hours traveled PrT tCur and t0) are computed with links and
    turning times, but do not contain the connectors.

    17.4.4

    Distribution of demand matrix to paths


    The values of a matrix you can distribute to existing PrT paths. The matrix value for the OD pair
    from zone A to zone B will be used as volume of the path from zone A to zone B. If there are
    several paths from zone A to zone B, the particular matrix value is distributed to the paths of all
    (or all active) path sets according to the path attribute ShareOfPathTarget.
    1. From the Calculate menu, choose Procedure sequence.
    The Procedure sequence window opens.
    2. Add the Distribution of demand matrix to paths procedure from the Matrices category to
    the given order of procedures in the procedure sequence (see "Setting up and starting the
    procedure sequence" on page 1847).
    3. Click in the Reference object(s) column.
    The Select matrix window opens.
    4. Select the desired matrix.
    5. Confirm with OK.
    6. Click the Edit button.
    The Distribute matrix to paths window opens.
    7. Select the desired options.

    1886

    Element

    Description

    Only active path


    sets

    If this option has been checked, each matrix value is distributed to


    paths of active path sets only. Volumes of other paths are retained.

    Consider OD pair
    filter

    If this option has been checked, only active OD pairs are regarded (see "Exception: Filter for OD pairs" on page 1026).

    PTVGROUP

    17.5 Displaying the calculation status


    Note: If you exclude path sets from distribution via options, path attribute ShareOfPathTarget of the path sets excluded is not accounted for during the distribution
    of matrix values.
    Example: There are the paths d, e, and f from zone A to zone B. Path d has a ShareOfPathTarget of 3, paths e and f of 1. The matrix value to be distributed is 100. Via
    path filters, path f is set to inactive. Via the option Only active path sets, it is excluded
    from distribution. The matrix value is then distributed across paths d and e.
    Path d is assigned 100 : 4 x 3 = 75.
    Path e is assigned 100 : 4 x 1 = 25.
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    During the procedure sequence, the matrix values are distributed to the paths according to the
    specified order of procedures.

    17.5

    Displaying the calculation status


    You can call the list of procedures which have already been executed and for which the calculated results are available in the current version.
    1. In the Calculate menu, select the Calculation status command.
    The Calculation status window opens.

    Note: In the Assignments section, the assignment procedures are listed by demand
    segment, and other procedures are listed in the Other procedures section.
    2. Click the Close button.
    PTVGROUP

    1887

    18 Settings for the PrT user model

    18

    Settings for the PrT user model


    Visum provides several assignment procedures for the PrT. There are static assignment procedures without explicit time modeling as well as procedures which use a time dynamic traffic
    flow model.
    For the numerous procedures, certain parameters have to be set.
    Additionally to assignment results you can also calculate PrT skim matrices.
    Subjects
    Setting parameters for PrT assignments
    Definition and application of volume-delay functions
    Calculating node impedances
    Signal timing optimization and coordination
    Blocking back model settings and calculation
    Setting and calculating the parameters for PrT assignment
    Evaluating the goodness of the PrT assignment
    Calculating:PrT skims

    18.1

    Setting parameters for PrT assignments


    Set the basic parameters for private transport assignment calculations.

    18.1.1

    Distributing the demand to PrT connectors


    You can distribute the demand among a zone's PrT connectors absolutely (freely) or proportionally (by shares).
    For zones with proportional demand distribution to connectors, you may select volume-dependent consideration or multi-point assignment (MPA) calculation (see Fundamentals: Chpt. 6.7 ,
    page 312).
    Note: In the network, the zone connectors do not need to be regarded in the same way,
    and also for the origin and destination demand of a zone, different distribution settings
    are permitted.

    18.1.1.1

    Absolute (free) distribution of demand


    Make sure that for zones with which you want to use free distribution during assignment,
    the attributes SharePrTOrig and/or SharePrTDest have been set to 0(no) (see "Zones:
    Connections tab" on page 1138).
    Note: In contrast to using connector shares for zone demand the free distribution
    does not require further procedure parameter settings.

    18.1.1.2

    Proportional distribution of demand


    1. Make sure, that - for zones to be regarded with proportional demand distribution during assignment - the attribute SharePrTOrig and/or SharePrTDest has been set to 1(yes).

    1888

    PTVGROUP

    18.1.1.2 Proportional distribution of demand


    Note: For the origin and/or destination connectors of these zones, you need to specify
    shares (see "Connectors: Basis tab" on page 1162).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. In the navigator, select PrT settings> Volume-delay functions.
    4. In the Connectors by percentage section, select an appropriate volume-delay function as
    default method for zones with proportional demand distribution to connectors (see "Allocating a VDF to proportional connectors without MPA" on page 1894).
    This VDF is used only for zone connectors with proportional distribution of the total origin/destination demand.
    5. In the navigator, select PrT settings.
    6. In the Connector weights apply to selection list, click the desired entry.
    Element

    Description

    Total trips (MPA


    off)

    If this option has been checked, MPA is not calculated.


    All origin and destination traffic of the zone is distributed onto all
    connectors as percentages of the zone proportionally to their
    respective current connector weights. The distribution regards the
    zone's total demand.
    Note
    Connector impedances depend on the connector volumes.

    Each single OD
    pair

    If this option has been checked, MPA is calculated.


    For each OD pair, the demand is split between available connectors proportionally to their weights.
    Note
    Connector impedances do not depend on the connector volumes.

    Notes: Multi-point assignment (MPA) has been implemented with the TModel interface and can be used with every PrT assignment procedure besides the procedure
    Dynamic User Equilibrium (DUE). MPA always works symmetrically, thus only OD
    pairs with proportional demand distribution to the origin zone connectors and to the
    destination zone connectors are concerned. Thus, the user has a choice for every
    zone and direction whether to apply MPA or not.
    For an assignment with MPA and simultaneous blocking back modeling, all assigned
    PrT demand segments of the network have to be selected. Otherwise, the blocking
    back model cannot be calculated with an assignment with MPA (see "Executing an
    assignment with the blocking back model" on page 1926).
    The default method has been selected.

    PTVGROUP

    1889

    18.1.2 Settings for saving PrT assignment results


    7. Confirm with OK.
    The settings are applied.
    8. Make sure, that the attribute MethodConnShares has been set to 0(Default) for all proportionally connected zones, to which the selected method is to be applied during assignment.
    For these zones, the default method is used.
    9. If applicable, change the method for individual zones: Set the attribute MethodConnShares
    to 1(Each single OD pair) or 2(Total trips (MPA off)).
    For those zones, the default method is replaced by the method selected for this particular
    zone.
    For all zones with demand distribution by shares, the next PrT assignment will use the
    method allocated to the zone by direction of the connector.

    18.1.2

    Settings for saving PrT assignment results


    For all PrT assignment procedures, you cannot only save the volumes, but also the paths
    found during calculation.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, click PrT settings> Assignment.
    3. In the Save assignment results section, select the desired entry in the Save paths selection list.

    1890

    Element

    Description

    Save
    paths

    Do not save
    The assignment result stores only the resulting volumes of network
    objects, the calculated paths are not stored. This option saves memory.
    As routes
    Calculated paths are stored as routes, i.e. only the spatial component is
    stored.
    As connections
    Calculated paths are stored as connections, i.e. both the temporal and the
    spatial component are stored.
    Notes
    This option is only relevant for dynamic PrT assignment procedures. If it
    has been selected for static assignment procedures, the paths are saved
    as routes.
    The larger the network the more computation time is required if paths are
    to be stored as connections. We recommend to use this option only if the
    path list is required for subsequent analyses.

    PTVGROUP

    18.1.3 Taking basic volume into account


    The changes are applied. The results of the next PrT assignment will be stored according to
    your settings.

    18.1.3

    Taking basic volume into account


    During assignment, you may take an existing basic volume into account which is read from
    available attribute data and will be dealt with like a PrT volume q. You may select either simple
    or detailed computation of the initial volume.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, click PrT settings> Assignment.

    3. In the Basic volume section, adjust the desired settings.


    Element

    Description

    Fix

    If this option has been checked, you can read existing basic
    volume data from network object attributes and regard the basic
    volume during assignment.

    Simple calculation If this option has been checked, you should select a unique
    AddValue that stores the basic volume of all of the traversed network object types (e.g. AddValue2 regards the AddValue2 data of
    links, main turns, turns and connectors). You can multiply the attribute values of the selected AddValue by a common factor.

    PTVGROUP

    1891

    18.1.4 Limiting the number of non-converged network objects logged to the log file
    Element

    Description

    Detailed calculation

    If this option has been checked, you can select a specific attribute
    by network object type that stores the basic volume of all traversed network objects of this type. For each network object type,
    the attribute values can be multiplied by a specific factor.

    The changes are applied. The next PrT assignment will use the new settings.

    18.1.4

    Limiting the number of non-converged network objects logged to the log file
    You can define the level of detail for the output of PrT assignment results to the log file. This
    applies to the following assignment procedures: Stochastic assignment, Dynamic stochastic
    assignment, Equilibrium_ Lohse and TRIBUT-Equilibrium_ Lohse. In the log file, Visum can
    trace the list of network objects or routes that have not yet converged. You define the maximum number of network objects for this detailed list output. If this number is exceeded, the network objects will be summarized.
    Note: For this list output, select the log file output option (see "Specifying settings for protocol files" on page 876).
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings.
    3. In the Protocol of non-converged objects, enter the desired number in the Maximum number of non-converged objects to be recorded in detail to log file input field.
    The change is stored. The next PrT assignment will use the new setting.

    18.2

    Definition and application of volume-delay functions


    Impedances of network objects are mostly calculated according to selected volume-delay functions (VD functions) (see "Allocating VDFs to network object types" on page 1892).
    For impedances of transport systems, user-defined impedance functions are also accounted
    for (see "Defining impedance functions for transport systems" on page 1908).

    18.2.1

    Allocating VDFs to network object types


    For certain network object types, you can select volume delay functions. The VDF parameters
    are subject to changes:
    For connectors by percentage without MPA you can select a VDF, thus tcur t0 applies.
    For each type of links, turns and nodes you can select a specific VDF.
    Visum provides several frequently used volume-delay functions. Furthermore, user-defined
    VDFs can be applied.

    1892

    PTVGROUP

    18.2.1.1 Selecting VDFs for link types


    18.2.1.1

    Selecting VDFs for link types


    You can compile a list of VD functions with user-defined parameters and subsequently allocate these VDFs to link types.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings > Volume-delay functions.

    3. In the Volume-delay functions section, select the desired VDFs (see "Selecting a VDF and
    setting the parameters " on page 1896).
    4. In the Link types section, select the desired link types.
    Notes: The table shows the allocation of VD functions to the link types00-99. The row
    number represents the decade of the link type number and the column number indicates the unit position. Example: The cell in the second row in the third column refers
    to link type12. Each cell stores the number of the currently allocated VDF.
    You may select multiple cells.
    To select multiple cells individually, press C TRL and keep it pressed while
    clicking each single desired cell one by one.
    Alternatively you may select a section of neighboring cells: Press the left-hand
    mouse-button while dragging the pointer over the desired section. Subsequently,
    you may refine this selection. Press C TRL and click any cell to toggle, you may
    add this cell to the selection or remove it from the selection.

    PTVGROUP

    1893

    18.2.1.2 Allocating a VDF to proportional connectors without MPA


    5. Next to VDF for selected cells, enter the number of the desired volume-delay function.
    The number is allocated to the selected cells.
    6. In the link type section, check the option Consider vMin, if applicable.
    Note: Select this option to limit the minimum speed of a link to the minimum speed of
    the link type (congestion) (see "Specifying link types" on page 1099).
    7. Confirm with OK.
    The changes are applied.
    18.2.1.2

    Allocating a VDF to proportional connectors without MPA


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Volume-delay functions.
    3. In the Connectors by percentages section, click the button.
    The Volume-delay function parameters window opens.
    Notes: Via this button, you select a VDF for connectors defined by shares. This VDF
    applies to proportional connectors without multi-point assignment only.
    Absolute connectors are regarded as being volume-independent. tCur=t0 applies.
    4. In the Type selection list, select the desired VDF.
    5. Edit the preset parameters, if required (see "Selecting a VDF and setting the parameters "
    on page 1896).
    6. Confirm with OK.
    This VDF has been selected for proportional connectors without multi-point assignment only.
    The selected VDF appears as button label with the name of the VDF and the user-defined
    parameters.

    18.2.1.3

    Selecting VDFs for node types


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Node impedances.
    3. In the Standard method selection list, select option Nodes VDF.

    1894

    PTVGROUP

    18.2.1.3 Selecting VDFs for node types

    4. In the navigator, select PrT settings> Node impedances> Nodes VDF.


    5. In the Volume-delay functions section, select the desired VDFs (see "Selecting a VDF and
    setting the parameters " on page 1896).
    6. In the Node types section, select the desired node types.
    Notes: The table shows the allocation of CR functions to the node types00-99. The
    row number represents the decade of the node type number and the column number
    indicates the unit position. Example: The cell in the second row in the third column
    refers to node type12. Each cell stores the number of the currently allocated VDF.
    You may select multiple cells.
    To select multiple cells individually, press C TRL and keep it pressed while
    clicking each single desired cell one by one.
    Alternatively you may select a section of neighboring cells: Press the left-hand
    mouse-button while dragging the pointer over the desired section.
    Subsequently, you may refine this selection.
    Press CTRL and click any cell to toggle, you may add this cell to the selection or
    remove it from the selection.
    7. Next to VDF for selected cells, enter the number of the desired volume-delay function.
    The number is allocated to the selected cells.
    Note: Additionally, the settings chosen for the method Turns VDF take effect.

    PTVGROUP

    1895

    18.2.1.4 Selecting VDFs for turn types


    18.2.1.4

    Selecting VDFs for turn types


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Node impedances.
    3. In the Standard method selection list, select option Turns VDF.
    4. In the navigator, select PrT settings> Node impedances> Turns VDF.
    5. In the Volume-delay functions section, select the desired VDFs (see "Selecting a VDF and
    setting the parameters " on page 1896).
    6. In the Turn types section, select the desired turn types (see "Selecting a VDF and setting
    the parameters " on page 1896).
    Notes: The table shows the allocation of VDFs to the turn types0-9. The row number
    represents the decade of the turn type number and the column number indicates the
    unit position. Example: The cell in the third column refers to turn type02. Each cell stores the number of the currently allocated VDF.
    You may select multiple cells.
    To select multiple cells individually, press C TRL and keep it pressed while
    clicking each single desired cell one by one.
    Alternatively you may select a section of neighboring cells: Press the left-hand
    mouse-button while dragging the pointer over the desired section.
    Subsequently, you may refine this selection.
    Press CTRL and click any cell to toggle, you may add this cell to the selection or
    remove it from the selection.
    7. Next to VDF for selected cells, enter the number of the desired volume-delay function.
    The number is allocated to the selected cells.

    18.2.1.5

    Selecting a VDF and setting the parameters


    1. For the particular network object type, open the VDF selection window:
    Link types (see "Selecting VDFs for link types" on page 1893)
    Node types (see "Selecting VDFs for node types" on page 1894)
    Turn types (see "Selecting VDFs for turn types" on page 1896)
    2. In the Volume-delay functions section, click the Create button.
    The Volume-delay function parameters window opens.

    1896

    PTVGROUP

    18.2.1.5 Selecting a VDF and setting the parameters

    3. Make the desired changes.


    Element

    Description

    Number of
    the VDF

    Arbitrary unique number (1..99)


    Note
    Use this number to allocate the VDF to particular link types, node types, or
    turn types.

    Type

    In the list, click a VD function type (see Fundamentals: Chpt. 6.4.2 , page
    233).
    Note
    In addition to the predefined VDFs listed, you may also use your own VDF
    (see "Applying user-defined volume-delay functions" on page 1899).
    AKCELIK
    Wait times at nodes
    AKCELIK2
    Speed reduction on links
    BPR
    Bureau of Public Roads function
    BPR2
    Modified BPR function with a different parameter b for the saturated and the
    unsaturated state
    BPR3
    Modified BPR function, for which an additional supplement d per vehicle can
    be specified in the saturated state.
    CONICAL

    PTVGROUP

    1897

    18.2.1.5 Selecting a VDF and setting the parameters


    Element

    Description
    (Spiess)
    CONICAL_MARGINAL
    A marginal-cost version of the CONICAL function, proposed by Spiess to calculate a system optimum instead of a user optimum in the Equilibrium assignment.
    EXPONENTIAL
    Models queuing at entry legs whose inflow is restricted by signal control
    (Ramp Metering)
    ICA-Turn
    VDF for precise calculation of impedances and capacities of turns by lane
    via Intersection Capacity Analysis (see Fundamentals: Chpt. 6.15 , page
    374)
    INRETS
    The INRETS function of the French Institut National de Recherche sur les
    Transports et leur Scurit
    Constant
    A constant function where the capacity has no impact on the travel time
    (tcur= t0)
    LOGISTIC,
    QUADRATIC,
    SIGMOIDAL_MMF_NODES (Morgan-Mercer-Flodin),
    SIGMOIDAL_MMF_LINKS
    Functions for modeling turn impedances
    TMODEL_LINKS,
    TMODEL_NODES
    Specific TModel functions, (see Fundamentals: Chpt. 6.5.2 , page 243)
    Lohse
    Modified BPR function with a linear rise in the congested section, according
    to the queuing theories
    Linear bottle-neck
    Linear bottle-neck modeling

    1898

    Function

    In this section, the functional form of the selected VDF is displayed.

    Parameters

    Enter the VDF parameters in the input fields.


    Note
    Next to VDF number and name in the list, the user-defined parameters will
    be displayed in alphabetical order in parentheses.
    Closed
    If this option has been checked, the particular network object will only be

    PTVGROUP

    18.2.1.6 Applying user-defined volume-delay functions


    Element

    Description
    included in path search if no alternative path can be found (e.g. for residential traffic). In this case, Visum assigns a high virtual time penalty, which,
    for example, has to be considered in the travel time skim matrix, when evaluating path times.
    Hard closure
    If this option has been checked, the particular network object will be excluded from path search.
    Notes
    The option Hard closure is only visible, if option Closed has been checked.
    If network objects are blocked by a VDF please make sure, that the network
    remains consistent for OD pairs with demand>0.
    If option Closed or even Hard closure has been checked for a VDF, the particular entry Weak closure or Hard closure will be displayed next to the VDF
    number in the list.

    4. Edit the preset parameters, if applicable.


    5. Confirm with OK.
    The volume-delay function has been selected and is - with the VDF name and the user-defined parameters - added to the list of Volume-delay functions.
    Notes: You may edit the list of selected VDFs.
    To modify the selected VDF, click the Edit button.
    To remove the selected VDF from the list, click the Delete button. As long as a VDF is still
    allocated to a link type, you may not remove it from the list.
    18.2.1.6

    Applying user-defined volume-delay functions


    The file storing a user-defined VDF must include a specific interface in order to be recognized
    by Visum. Most importantly, each file *.dll must export the functions listed below, so that Visum
    can call the *.dll file correctly during assignment.
    Preparing a *.dll file for a user-defined VDF
    Visum comes with a header file UserDefinedVDF.h which can be used directly for implementing the required functions in C++. The header file and a full example project for Microsoft
    Visual Studio can be found in the directory ...\Program files\PTV Vision\PTV Visum 13\Data\UserDefVDF. Generally any programming language can be used, as long as it can produce
    a Windows *.dll file which exposes an interface equivalent to the C++ function declarations.
    Note: The volume-delay function needs to be continuous and monotonously rising with
    respect to volumes. This applies to all possible values of the parameters.

    PTVGROUP

    1899

    18.2.1.6 Applying user-defined volume-delay functions


    Mandatory functions in the *.dll

    1900

    Declaration

    char Init ();

    Description

    This function is called by Visum once immediately after start-up and


    before the first use of any of the other functions.
    Note
    Use this function to initialize your data structures or perform any other preparatory functions, if necessary.

    Parameters

    None

    Return value

    true initialization successful


    false initialization failed, the *.dll file should not be called.

    Declaration

    void Destroy ();

    Description

    This function is called by Visum once immediately before shut-down and


    after the last use of any of the other functions.
    Note
    Use this function to perform any clean-up, if necessary. For example, free
    up dynamically allocated memory.

    Parameters

    None

    Return value

    None

    Declaration

    char IsThreadSafe();

    Description

    This function is called by Visum once immediately after start-up and


    before the first call of any of the other functions. The returned value indicates whether the Calc... functions listed below have been implemented
    for simultaneous use. If so, the function can be called once more before
    the previous call has been finished.
    Note
    This parallelism can be used in case of multithread implementation of assignment procedures in Visum.

    Parameters

    None

    Return value

    true reentrant
    false not re-entrant

    PTVGROUP

    18.2.1.6 Applying user-defined volume-delay functions


    Declaration

    char DependsOnTSys ();

    Description

    This function is called by Visum once immediately after start-up and


    before the first call of any of the other functions. Use this function to indicate whether your function makes use of separate volumes per transport
    system. If this is not the case, Visum can avoid extracting and passing
    these volumes to the Calc functions, which saves calculation time.

    Parameters

    None

    Return value

    true needs volumes per transport system


    false uses only total volumes in PCU

    Declaration

    const wchar_t * GetName (const char * langid);

    Description

    Returns a readable name for the functional form which is used as the list
    entry in the VDF selection list.

    Parameters

    langid is a language code which can be used to optionally translate the


    name to other languages.
    Currently, the following options are provided.
    ENG English
    DEU German
    FRA French
    ITA Italian
    POL Polish
    ESP Spanish
    CHI Chinese
    JAP - Japanese
    Notes
    If not required, you may ignore this functionality. If you use the language
    code, always include the case of an unknown code, because languages
    may be added in the future without explicit notice.

    Return value

    The readable name of the functional form as a 16-bit UTF-8 character


    string. The value must be returned as UTF-8 to accommodate special characters in some languages, notably the Asiatic ones. Visum expects a pointer to a string stored in the *.dll file.
    Note
    Be sure not to allocate the string on the stack, so that the address is still
    valid after the function call.

    PTVGROUP

    1901

    18.2.1.6 Applying user-defined volume-delay functions

    1902

    Declaration

    const char * GetID ();

    Description

    Should return a string to be used as a unique ID for the functional form.


    This ID is stored internally in the version file to record the user allocation
    to connectors and types of links, nodes or turns, and it serves as the ID of
    the functional form in the *.xml format for procedure parameters.

    Parameters

    None

    Return value

    The ID string as an ASCII string. The string must contain only the characters 0..9, a..z, A..Z. Visum expects a pointer to a string stored in the *.dll
    file.
    Note
    Be sure not to allocate the string on the stack, so that the address is still
    valid after the function call.

    Declaration

    int GetInterfaceVersion();

    Description

    The interface definition is versioned for files of the *.dll type, so that function declarations can be changed or extended in the future. Return the version number of the header file for which you program your functions.
    Visum compares the returned number to the version numbers it knows
    about, calls the dll functions accordingly or returns an error message, if
    the interface version is not supported.

    Parameters

    None

    Return value

    the version number

    Declaration

    void SetTsysInfo (int numtsys, const wchar_t * tsysids[])

    Description

    Visum calls this function each time the set of private transport systems
    changes. As parameters, it passes the number of transport systems and
    an array of the transport system codes. For efficiency reasons, Visum passes the transport system as a number to the Calc functions, i.e. as the 0based index into the tsysids array.
    Note
    To avoid string comparisons in these frequently called functions, you
    should - in SetTsysInfo - evaluate the numerical TSys index of transport
    systems that require special treatment in volume-delay functions and store
    this data.

    Parameters

    numtsys the number of transport systems (= length of array tsysids)


    tsysids array of 16-bit UTF-8 character strings, each of which is the value
    of the attribute Code for one transport system used in the assignment.

    Return value

    No

    PTVGROUP

    18.2.1.6 Applying user-defined volume-delay functions


    Declaration

    double Calc (int tsysind, bool tsysisopen, int typ, int numlanes, double
    length, double cap, double v0, double t0, double gradient, double pcuvol,
    double vehvolsys[], int uval1, int uval2, int uval3, int uvaltsys, double para_
    a, double para_b, double para_c, double para_d, double para_f, double
    para_a2, double para_b2, double para_d2, double para_f2, double satcrit)

    Description

    The implementation of the volume-delay function itself. Visum calls this


    function in order to calculate the current travel time tCur by link / turn /
    connector / node and transport system.
    Note
    Care should be taken to code the function in a computationally efficient
    form, because it will be called very frequently.

    Parameters

    For the network objects, various parameters are passed.


    Note
    For details, please refer to the table below.

    Return value

    tCur in [s]

    Depending on the network object type, Visum passes the following parameters to the Calc
    function.
    Link

    Connector

    Turn

    Node

    int tsysind

    Zero-based index of the transport system (refers to the array tsysids


    passed in SetTsysInfo) for which tCur should be computed

    bool tsysisopen

    Is the network object open for the transport system

    int typ

    0..99

    0..9

    0..99

    int numlanes

    Number of lanes 1 (arbitrary)

    1 (arbitrary)

    1 (arbitrary)

    double length

    Length
    [short length]

    Length
    [short length]

    0 (arbitrary)

    0 (arbitrary)

    double cap

    CapPrT [pcu]

    10E10 or
    CapPrT [pcu]
    CapPrT[pcu] if
    connectors have
    specified shares
    for the total origin/destination
    demand.

    CapPrT [pcu]

    double v0

    v0 [m/s]

    Length/t0 (or 0 if 0
    t0=0)

    double t0

    Length/v0 [s] or
    10E10 if v0=0

    t0 [s]

    double gradient Slope


    double pcuvol

    PTVGROUP

    0..9

    0 (arbitrary)

    0 (arbitrary)

    0 (arbitrary)

    VolPCU[pcu] as a linear combination of all TSys volumes in [veh],


    multiplied by the TSys-specific value of the attribute PCU.

    1903

    18.2.1.6 Applying user-defined volume-delay functions


    Link

    Connector

    Turn

    Node

    Note
    Recommended for most of the applications.
    double vehvolsys[]

    Alternatively, for non-standard PCU calculations, an array of all TSys


    volumes in [veh]. The order of entries complies with the order of entries in the tsysids array which is passed to SetTsysInfo.

    double uval1/2/3 Values of the attributes AddValue1, AddValue2 and AddValue3


    double uvaltsys

    Value of the
    0
    TSys-specific
    attribute AddValue-TSys

    double para_
    a..f2

    From the Volume-delay function parameters window

    double satcrit

    From the Volume-delay function parameters window (see "Selecting a VDF and setting the parameters " on page 1896)

    Optional functions in the *.dll

    1904

    Declaration

    double CalcDerivative (int tsysind, bool tsysisopen, int typ, int numlanes,
    double length, double cap, double v0, double t0, double gradient, double
    pcuvol, double vehvolsys[], int uval1, int uval2, int uval3, int uvaltsys, double para_a, double para_b, double para_c, double para_d, double para_f,
    double para_a2, double para_b2, double para_d2, double para_f2, double
    satcrit)

    Description

    The program calls this function in order to calculate the derivative of the
    current travel time tCur with respect to saturation by link / turn / connector /
    node and TSys. This function is only called within the bicriterial toll assignment methods TRIBUT - Equilibrium assignment and TRIBUT - Equilibrium_Lohse.
    Notes
    Care should be taken to code the function in a computationally efficient
    form, because it will be called very frequently.
    If the function has not been implemented in the *.dll, Visum will compute
    the derivative numerically. However, this requires more time than supplying the CalcDerivative() in the *.dll.

    Parameters

    Same as for Calc()

    Return value

    Derivative of tCur in [s]

    PTVGROUP

    18.2.1.6 Applying user-defined volume-delay functions


    Declaration

    double CalcIntegral (int tsysind, bool tsysisopen, int typ, int numlanes, double length, double cap, double v0, double t0, double gradient, double pcuvol, double vehvolsys[], int uval1, int uval2, int uval3, int uvaltsys, double
    para_a, double para_b, double para_c, double para_d, double para_f, double para_a2, double para_b2, double para_d2, double para_f2, double satcrit)

    Description

    The program calls this function in order to calculate the integral of the current travel time tCur with respect to saturation by link / turn / connector /
    node and TSys.
    Note
    This function is no longer required. Thus it does not have to be implemented.
    If the function is not implemented in the *.dll, Visum will compute the integral numerically. However, this will require more time than supplying CalcIntegral() in the *.dll.

    Parameters

    Same as for Calc()

    Return value

    Integral from 0 to saturation of the volume-delay function in [s].

    Example for a user-defined VDF


    Assume that two transport systems CAR and HGV are used in the assignment.
    For CAR the volume-delay function is a linear form with one breakpoint at satcrit.

    For HGV two breakpoints d and e are used.

    The following applies.

    The derivations are:

    Source code of the *.dll file


    #include "UserDefinedVDF.h"

    PTVGROUP

    1905

    18.2.1.6 Applying user-defined volume-delay functions


    #include "tchar.h"
    int indHGV; // index of the HGV tsys
    wchar_t VDFName[] = _T("ManualExample"); // UTF-8 !!
    char VDFID[] = "MANEX";
    int INTERFACE_VERSION = 1;
    bool Init()
    {
    indHGV = -1;
    return true;
    }
    void Destroy()
    {
    }
    const wchar_t* GetName(const char *langid)
    {
    return VDFName;
    }
    const char* GetID(const char *langid)
    {
    return VDFID;
    }
    int GetInterfaceVersion()
    {
    return INTERFACE_VERSION;
    }
    void SetTsysInfo (int numtsys, const wchar_t * tsysids[])
    {
    for (int i = 0; i < numtsys; i++)
    {
    if (_tcscmp(tsysids[i], _T(HGV)) == 0) indHGV = i;
    }
    }
    double Calc (int tsysind, bool tsysisopen, int typ, int numlanes, double length, double cap, double v0, double t0, double gradient, double pcuvol, double vehvolsys[],
    int uval1, int uval2, int uval3, int uvaltsys, double para_a, double para_b, double
    para_c, double para_d, double para_f, double para_a2, double para_b2, double para_d2,
    double para_f2, double satcrit)
    {
    double sat = pcuvol / cap;
    if (tsysind != indHGV) {
    if (sat < satcrit)
    return t0 * (1 + para_a * sat);
    else
    return t0 * (1 + para_a * satcrit + para_b * (sat-satcrit));
    }
    else {
    if (sat < d)
    return t0 * (1 + para_a2 * sat);
    else {
    if (d <= sat && sat < e)
    return t0 * (1 + para_a2 * d + para_b2 * (sat-d));
    else
    return t0 * (1 + para_a2 * d + para_b2*(e-d) + para_c*(sat-e));
    }

    1906

    PTVGROUP

    18.2.1.6 Applying user-defined volume-delay functions


    }
    }
    double CalcDerivative (int tsysind, bool tsysisopen, int typ, int numlanes, double
    length, double cap, double v0, double t0, double gradient, double pcuvol, double vehvolsys[], int uval1, int uval2, int uval3, int uvaltsys, double para_a, double para_
    b, double para_c, double para_d, double para_f, double para_a2, double para_b2, double para_d2, double para_f2, double satcrit)
    {
    double sat = pcuvol / cap;
    if (tsysind != indHGV) {
    if (sat < satcrit)
    return para_a;
    else
    return para_b;
    }
    else {
    if (sat < d)
    return para_a2;
    else {
    if (d <= sat && sat < e)
    return para_b2;
    else
    return para_c;
    }
    }
    }

    Importing user-defined VDFs


    1. Compile and link the *.dll with the development environment of your choice.
    2. Name the library file according to the following pattern: VisumVDF***.dll.
    Notes: Here, *** can be replaced by any string that matches the Windows file name
    conventions.
    Note that the IDs returned by GetID() must be unique. If two *.dll files use the same ID,
    only the first one will be loaded into Visum. All others will be ignored.
    3. Save the file to ...\Program files\PTV Vision\PTV Visum 13\Data\UserDefVDF.
    Notes: During the installation process, this folder is created by default. It is evaluated,
    whenever a program session starts.
    Alternatively, you may select a different folder as standard folder for your *.dll files. In
    this case, the different path must be saved to the standard path file std.pfd (see
    "Editing the storage location of files" on page 837). The modification takes effect once
    you restart the program.
    During the program start, Visum detects the *.dll files and loads the contents. Only those files
    are opened, whose Windows edition (32 or 64 Bit) complies with the current Visum edition.
    Then, the user-defined VDFs are listed jointly with the predefined VDFs in the Volume-delay
    function parameters window.

    PTVGROUP

    1907

    18.2.2 Defining impedance functions for transport systems


    Notes: After start-up Visum no longer scans for new *.dll files. If you add another user-defined VDF, you have to start Visum again.
    If you store a *.bmp file and the *.dll file with identical filenames in the same folder, the
    graph of the selected VDF will be displayed in the Function column.

    18.2.2

    Defining impedance functions for transport systems


    For each private transport system you can either define a simple, uniform impedance function
    that is taken into account for links, connectors, turns and main turns, or you can define a detailed impedance function for each of the aforementioned network object types.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Impedance.
    The list of transport systems appears.

    3. Check the option in the detailed column, if you would like to set up a specific impedance
    function for each of the four network object types for the particular transport system.
    Uncheck the option in the detailed column, if you would like to set up just a single unique
    impedance function for the four network object types for the particular transport system.
    For each transport system, the Function button appears either in the All column or by network object type.
    4. Click each Function button.
    The Parameters 'Edit attribute' window opens.

    1908

    PTVGROUP

    18.2.2 Defining impedance functions for transport systems

    5. Make the desired changes.


    Element

    Description

    Network
    object type

    Display of the network object types to which the impedance formula applies

    Target attr.

    Impedance by transport system(s)


    Notes
    With the help of the formula, you can calculate the target attribute value
    from the values of other attributes.
    The formula consists of rows where each row defines an mathematical
    operation.
    If an operational sign has been selected, two terms per row can be defined.
    In case of multirow formulas, the rows are linked by +. A linear combination (see "Editing attribute values during a procedure sequence" on
    page 990) of various mathematical operations is calculated.

    Create

    Via this button, you add a new line to the formula.


    Note
    A variable number of terms may be used.

    Delete

    Via this button, you remove the bottom row.

    Coefficient

    Factor, the value of the selected attribute is multiplied by


    Note
    The term in the section to the right is only provided, if an operation sign
    has been selected.

    Attribute

    Source attribute, whose value enters the formula.

    PTVGROUP

    1909

    18.2.2 Defining impedance functions for transport systems


    Element

    Description
    Via the button you may select an attribute (and sub-attribute, if applicable). The selection is done in a separate window (see "The window
    used for the selection of one attribute" on page 963).
    If option detailed has been checked, all of the particular target network
    object type's direct and indirect (also user-defined) attributes are provided for selection for each of the four network objects types.
    If option detailed has not been checked, the following attributes are provided, which apply to all of the four target network object types simultaneously.
    Toll PrTSys
    Length
    If the Toll or Length attributes of links are used in the uniform impedance function, a different formula might have been specified internally for connectors, turns, and main turns.
    t0_PrTSys
    tCur-PrTSys
    When defining the impedance function for a TSys, you can use the
    impedance function of a different TSys as a data source. Please
    note that impedances of two different TSys may not depend on each
    other. Otherwise, Visum might get caught in an infinite loop. It is the
    users own responsibility to use correct terms.
    AddValue1, AddValue2, AddValue3
    If the unique impedance function includes AddValues that are taken
    into account for costs or basic volumes, the same AddValue needs
    to include the same data for each of the four network object types,
    e.g. AddValue2.
    Notes
    The term in the section to the right is only provided, if an operation sign
    has been selected.
    If no source attribute has been selected, the value 1.0 is used instead.
    The set attribute IDs have to be valid. Otherwise, the impedance function
    will be reset to the default of 1 tCur, as soon as values have to be retrieved from the function.
    However, the calculations are not necessarily correct for all of the impedance functions set.
    If you select an attribute which directly depends on tCur (e.g. vCur,
    impedance or delay time), the set function cannot be integrated or
    derived with regard to tCur by default. In that case derivations and
    integrals will be determined incorrectly.
    If tCur has been set for both attributes of a term, it will be calculated
    incorrectly if the operational sign is .
    In case the operational sign is /, the calculation will only be correct if

    1910

    PTVGROUP

    18.3 Calculating node impedances


    Element

    Description
    only the first attribute of a term is tCur.

    Op.

    Operational sign of a mathematical operation that includes two terms


    (for example AddVal2 + AddVal3).
    From the selection list, you may select the operational sign (+, -, *, /, %)

    Units for
    The displayed units for impedance attributes (times/lengths) are pre-defiimpedances ned. The length unit used (metric or imperial) depends on the settings
    made under Network> Network parameters> Units tab. You may use
    the coefficient to convert the impedance into any unit.
    Note
    Since the impedance is an integer value in PrT procedures, a small unit
    should be preferred for assignments. We recommend 1/100 seconds
    (equals 100 tCur).
    6. Confirm with OK.
    The TSys-specific impedance function settings are stored either for the network object type listed on top of the window or for all network object types.

    18.3

    Calculating node impedances


    For node impedance calculations, you need to define the method according to which they
    shall be calculated (see Fundamentals: Chpt. 6.5 , page 241).
    During the assignment, node impedances are calculated for all nodes from the relevant input
    attributes by default. However, the node impedances can also be calculated without assignment.

    18.3.1

    Selecting the method for node impedance calculation


    Select the standard method which applies to all nodes by default For selected nodes, you can
    set a different method.
    Setting the standard method for node impedance calculation
    For the node impedance calculation, you can select a method as standard method. This
    method is applied to all nodes, for which the attribute Use preset method for impedance at
    node is false (not true).
    1. For the desired nodes, set the value of the Use preset method for impedance at node attribute to 'true'.
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. In the navigator, select PrT settings> Node impedances.
    4. In the Standard method selection list, click the desired entry (see Fundamentals: Chpt. 6.5 ,
    page 241).

    PTVGROUP

    1911

    18.3.2 Setting the design hourly volume for node impedance calculations
    5. Adjust the settings for the selected method.
    Element

    Description

    Turns VDF

    (see "Calculating node impedances via Turns VDF" on page


    1913)

    From previous
    assignment with
    ICA

    (see "Using VD functions of assignment with ICA for other assignments" on page 1920)

    Nodes VDF

    (see "Calculating node impedances using Nodes VDF" on page


    1914)

    Intersection Capa- (see "Calculating node impedances using Node impedance calcity Analysis (ICA) culation (ICA)" on page 1914)
    6. Confirm with OK.
    The standard method has been set.
    Setting the method for node impedance calculation for selected nodes
    For selected nodes, you can set a node impedance calculation method which differs from the
    standard method.
    1. For the desired nodes, set the value of the Use preset method for impedance at node attribute to 'true'.
    2. For the selected nodes, select the desired method as value of the Method for impedance
    at node attribute.
    3. Adjust the settings for the selected method.
    Element

    Description

    Turns VDF

    (see "Calculating node impedances via Turns VDF" on page


    1913)

    From previous
    assignment with
    ICA

    (see "Using VD functions of assignment with ICA for other assignments" on page 1920)

    Nodes VDF

    (see "Calculating node impedances using Nodes VDF" on page


    1914)

    Intersection Capa- (see "Calculating node impedances using Node impedance calcity Analysis (ICA) culation (ICA)" on page 1914)
    For the selected nodes, the desired node impedance calculation method has been set.

    18.3.2

    Setting the design hourly volume for node impedance calculations


    For all nodes, select the design hourly volume for the node impedance calculation.
    1. From the Calculate menu, choose General procedure settings.

    1912

    PTVGROUP

    18.3.3 Calculating node impedances via Turns VDF


    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Node impedances.
    3. In the Design hourly volume [PCU / h] drop-down list, select the desired entry.
    Element

    Description

    Volume PrT
    [PCU]

    The design hourly volume is derived from the turn attribute Volume
    PrT [PCU/h].

    Volume PrT
    with base
    [PCU]

    The design hourly volume is summed up from the turn attribute


    Volume PrT [PCU/h] and the base volume which is defined via PrT
    settings> Assignment.

    AddValues 1 to The design hourly volume is calculated from the selected attribute.
    3
    Vistro - hourly
    volume

    This option is only available, if you have activated the Vistro add-on
    module.
    The design hourly volume is then calculated with Vistro attributes
    depending on the analysis time slot.
    If in the Time interval for ICA box you enter 1h (see "Parameters for Assignment with ICA" on page 1948), the peak hour
    factor (PHF) is not considered. The design hourly volume is calculated: rounded (Vistro Total Hourly Volume * Vistro Other
    Adjustment Factor).
    If in the Time interval for ICA box you enter another value than
    1h (see "Parameters for Assignment with ICA" on page 1948),
    the peak hour factor (PHF) is considered. The design hourly
    volume is calculated: rounded (Vistro Total Hourly Volume *
    Vistro Other Adjustment Factor / PHF).

    Note: The option Vistro - hourly volume is only relevant for PTV Vistro. It is only
    available, if you have activated the Vistro add-on module.
    4. In the entry field, enter the desired factor.
    5. Confirm with OK.
    The design hourly volume is set.

    18.3.3

    Calculating node impedances via Turns VDF


    tCur, the time required by a turning vehicle, is calculated from the free-flow turn time t0 in an
    unloaded network and the saturation of the turn, using a volume-delay function (see Fundamentals: Chpt. 6.5.1 , page 243).
    1. For the nodes selected, choose the Turns VDF function for node impedance calculation
    (see "Selecting the method for node impedance calculation" on page 1911).

    PTVGROUP

    1913

    18.3.4 Calculating node impedances using Nodes VDF


    2. Make sure that at the desired nodes, the input attribute values Capacity PrT, t0 PrT and
    TypeNo are correct for the turns (see "Managing turns" on page 1090).
    3. For each turn type used in the network, select the appropriate VDF (see "Selecting VDFs for
    turn types" on page 1896).
    4. Calculate the node impedances with an appropriate method (see "Methods for node impedance calculation" on page 1921).

    18.3.4

    Calculating node impedances using Nodes VDF


    The tCur of a turn is calculated usng a node VDF and a turn VDF (see Fundamentals: Chpt.
    6.5.2 , page 243).
    1. For the nodes desired, specify the Nodes VDF method for node impedance calculation
    (see "Selecting the method for node impedance calculation" on page 1911).
    2. Make sure that the values of the following input attributes are correct at the selected nodes:
    Capacity PrT, t0 PrT and Type Number for turns (see "Managing turns" on page
    1090)
    Capacity PrT and t0 PrT for nodes (see "Managing nodes" on page 1063)
    TModelSpecial (TModel receives penalty by node) = 1 for minor links towards the
    node (see "Managing links" on page 1099)
    3. For each turn type used in the network, select the appropriate VDF (see "Selecting VDFs for
    turn types" on page 1896).
    4. For each node type used in the network, select the appropriate VDF (see "Selecting VDFs
    for node types" on page 1894).
    5. Calculate the node impedances with an appropriate method (see "Methods for node impedance calculation" on page 1921).

    18.3.5

    Calculating node impedances using Node impedance calculation (ICA)


    tCur of a turn is calculated with the exception of uncontrolled nodes according to the HCM
    and depends on the node's control type (see Fundamentals: Chpt. 6.5.3 , page 244).
    1. For the nodes desired, specify the Node impedance calculation (ICA) method (see "Selecting the method for node impedance calculation" on page 1911).
    2. Make sure that at the nodes desired, the input attributes values are correct (see Fundamentals: Chpt. 6.5.3 , page 244).
    3. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    4. In the navigator, select PrT settings> Node impedances> Node impedance calculation
    (ICA).
    5. Make the desired changes.

    1914

    PTVGROUP

    18.3.5 Calculating node impedances using Node impedance calculation (ICA)


    Element

    Description

    tCur update

    User-defined time for tCur re-calculation.


    Manually
    If this option has been checked, tCur is not calculated automatically.
    Node impedances can - at a time of your choice - be calculated by
    means of one of the following options:
    Operation Update impedances at node in the procedure
    sequence
    Special function Update impedances at node (Multi-edit nodes)
    in the network editor
    Via the COM interface
    For a single node via editing t0 or via the ICA calculation icon in
    the junction editor.
    After assignment
    If this option has been selected, tCur is calculated after assignment.
    Note
    We recommend to use this option.
    Before and during assignment
    If this option has been selected, an initial tCur is calculated prior to
    the assignment and additionally tCur is calculated during the assignment.
    During assignment
    If this option has been selected, tCur is calculated during the assignment.

    Active nodes
    only

    If this option has been checked, the impedance is calculated for


    active nodes only.

    Treatment of U- Treat U-turns as left-most left-turn


    turns
    If this option has been checked, the calculation is not based on the
    HCM. Taking the node geometry into account, also turn times are calculated for U-turns.
    Ignore U-turns
    If this option has been checked, the calculation is based on the HCM.

    PTVGROUP

    1915

    18.3.5 Calculating node impedances using Node impedance calculation (ICA)


    Element

    Description

    Time interval

    User-defined duration of the volume peak

    Create Excel
    report

    If this option has been checked, the ICA output is saved as a formatted Excel report *.xls.
    Notes
    The file is stored in the folder, that has been set for ICA files via project directories. The file name of the Excel report is generated automatically.
    ICA<Network file name>.xls for multiple nodes or
    ICA<Network file name>_<Node number>.xls for a single node.
    The output file includes an overview sheet and a special sheet for
    each node that stores the node's number and data.
    Another sheet stores error messages and warnings.

    6. For the nodes with various control types, adjust the settings via the navigator entry PrT
    settings> Impedances at node> Node impedance calculation (ICA):
    Signalized (see "Signalized nodes (LOS)" on page 1917)
    Two-way stop (see "Two-way stop nodes (LOS)" on page 1918)
    Roundabout (see "Roundabout" on page 1918)
    All-way stop (see "All-way stop (LOS)" on page 1919)
    Uncontrolled (see "Uncontrolled nodes (TModel)" on page 1919)
    7. Confirm with OK.

    1916

    PTVGROUP

    18.3.5.1 Signalized nodes (LOS)


    8. Calculate the node impedances with an appropriate method (see "Methods for node impedance calculation" on page 1921).
    18.3.5.1

    Signalized nodes (LOS)


    The method includes six steps of calculation (see Fundamentals: Chpt. 6.5.3.2 , page 246).
    1. Make sure the input attributes values at nodes of the control type Signalized are correct
    (see Fundamentals: Chpt. 6.5.3.2 , page 246).
    2. Check and adjust the parameters on the Signalized tab.
    Element

    Description

    Calculation accor- From the drop-down list, select the desired option.
    ding to
    Circular 212 Operations and Circular 212 Planning
    These methods adopt the saturation flow rate from row E of the
    Planning or Operations table or from a common table (see Fundamentals: Chpt. 6.5.3.2 , page 246).
    Note
    For the Circular options, the ideal saturation flow rate is not subject to changes.
    HCM 2000
    Node impedances are calculated according to the HCM 2000.
    HCM 2010
    Node impedances are calculated according to HCM 2010.
    ICU 1
    ICU1 (V/S)= (volume / saturation flow rate) + (ICA loss time / SC
    cycle time)
    ICU 2
    ICU2 (V/S)= (volume / saturation flow rate) * [1 + (1 / [SC cycle
    time / ICA loss time) 1] ) ]
    Notes
    For ICU options, the user-defined number of vehicles per pocket
    lane is regarded, if option Use number of vehicles has been
    selected for this lane. If this option has not been checked, the
    number of vehicles is determined from the length of the pocket
    lane and the attribute Space per PCU.
    Maximum tCur

    If this option has been checked, enter a value which is used as


    user-defined maximum turn penalty at the node.

    Queue length per- In the list, select the percentile (70, 85, 90, 95 or 98) which is to
    centile [%]
    be saved in turn attribute ICA average back of queue for signalized junctions.
    Ideal flow rate

    PTVGROUP

    User-defined value for HCM calculation method. Maximum num-

    1917

    18.3.5.2 Two-way stop nodes (LOS)

    18.3.5.2

    Element

    Description

    HCM [veh/lane/h]

    ber of vehicles that can drive in an ideal scenario.


    Note
    We recommend a value between 1,600 and 2,000 vehicles per
    lane/h.

    Ideal flow rate


    ICU1 [veh/lane/h]

    User-defined value for ICU1 calculation method. Maximum number of vehicles that can drive in an ideal scenario.
    Note
    We recommend a value between 1,600 and 2,000 vehicles per
    lane/h

    Ideal flow rate


    ICU2 [veh/lane/h]

    User-defined value for ICU2 calculation method, maximum number of vehicles that can drive in an ideal scenario.
    Note
    We recommend a value between 1,600 and 2,000 vehicles per
    lane/h

    Use the pocket


    length for the calculation

    If the option has been selected, the OD pair filter is taken into
    account.
    If the option has not been selected, the length of the pocket is not
    regarded.

    Two-way stop nodes (LOS)


    The method includes six steps of calculation (see Fundamentals: Chpt. 6.5.3.3 , page 268).
    1. Make sure the input attributes values at the nodes of the control type Two-way stop are correct (see Fundamentals: Chpt. 6.5.3.3 , page 268).
    2. Check and adjust the parameters on the Two-way stop tab.
    Element

    Description

    Calculation accor- HCM 2000


    ding to
    Node impedances are calculated according to HCM 2000.
    HCM 2010
    Node impedances are calculated according to HCM 2010.
    Maximum tCur

    18.3.5.3

    If this option has been checked, enter a value which is used as


    user-defined maximum turn penalty at the node.

    Roundabout
    The calculation is performed according to either HCM 2010 (see Fundamentals: Chpt. 6.5.3.5 ,
    page 287) or TRL/Kimber (see Fundamentals: Chpt. 6.5.3.6 , page 293).
    1. Make sure that the values of the input attributes are correct at the nodes with control type
    Roundabout.

    1918

    PTVGROUP

    18.3.5.4 All-way stop (LOS)


    Input attributes for calculation based on HCM (see Fundamentals: Chpt. 6.5.3.5 , page
    287)
    Input attributes for calculation based on TRL/Kimber (see Fundamentals: Chpt. 6.5.3.6
    , page 293)
    2. Check and adjust the impedance model on the Roundabout tab.

    18.3.5.4

    Element

    Description

    HCM

    Select this option for an impedance calculation based on the


    HCM 2010 (see Fundamentals: Chpt. 6.5.3.5 , page 287).

    TRL/Kimber

    Select this option for an impedance calculation according to the


    TRL/Kimber method (see Fundamentals: Chpt. 6.5.3.6 , page
    293).

    All-way stop (LOS)


    The method includes five steps of calculation (see Fundamentals: Chpt. 6.5.3.4 , page 279).
    1. Make sure that the input attribute values at nodes with control type All-way stop are correct
    (see Fundamentals: Chpt. 6.5.3.4 , page 279).
    2. Check and adjust the parameters on the All-way stop tab.
    Element

    Description

    Calculation accor- HCM 2000


    ding to
    Node impedances are calculated according to the HCM 2000.
    HCM 2010
    Node impedances are calculated according to HCM 2010.
    Maximum tCur

    18.3.5.5

    If this option has been checked, enter a value which is used as


    user-defined maximum turn penalty at the node.

    Uncontrolled nodes (TModel)


    Note: For nodes of the control type uncontrolled and the Method for impedance at node
    Node impedance calculation (ICA), the Node VDF calculation method is used (see Fundamentals: Chpt. 6.5.3.1 , page 245).
    1. Make sure the node input attributes Capacity PrT and t0 PrT (identical for all turns via the
    node) are set correctly for nodes of the control type uncontrolled.
    2. Check and adjust the parameters on the Uncontrolled tab.
    Element

    Description

    Volume delay All VD functions are available for selection (see "Selecting VDFs for
    function
    node types" on page 1894).
    Maximum

    PTVGROUP

    If this option has been selected, enter two values. The user-defined

    1919

    18.3.6 Using VD functions of assignment with ICA for other assignments


    Element

    Description

    tCur

    maximum turn penalty results from the formula.


    Note
    Since any VDF can be selected and a maximum turn penalty tCur can
    be defined, resulting turn penalties shall become more realistic. Using
    the BPR function with the default parameters a=2, b=4 and c=1
    may lead to very high turn penalties for the minor flows in the case of
    saturation. During route search these turns can then behave almost
    like blocked turns. This can lead to heavy oscillations during the assignment process. Therefore it is recommendable to select parameters
    which ensure a lesser slope after saturation. This may be achieved
    with a parameter of b < 4 or better with the BPR2 function and b= 1 if
    saturation exceeded 100%. Additionally it can be useful to set a maximum penalty. This is possible in the following form:
    tCur = MIN (tCur from node control VDF; t0 x Factor; Max tCur)
    Example with BPR function
    t0 = 20 s
    Saturation = 250 %
    a = 2, b = 4
    tCur = 1583 s = 26.4 min
    Example with BPR2 function
    t0 = 20 s
    Saturation = 250 %
    a = 2, b = 4, b = 0.8
    tCur = 103 s = 1.7 min
    A saturation of 250 % is not realistic in real life, but it may easily occur
    during assignment when the total volume is assigned to one shortest
    path. If you use the option Computing of tCur after assignment, please
    note that the shortest path algorithm will apply - to all turns - the tCur
    values available at the beginning of the assignment. These values are
    not initialized, i.e they are not reset to t0.
    Make sure, that t0 PrT > 0 applies to all relevant turns.

    18.3.6

    Using VD functions of assignment with ICA for other assignments


    The Assignment with ICA calculates the VDF parameters for turn-specific volume-delay functions. Subsequently you can use these parameters for another assignment.
    1. Execute an assignment with ICA (see "Assignment with ICA" on page 1946).
    2. For the selected node, select the node impedance calculation method From previous assignment with ICA (see "Selecting the method for node impedance calculation" on page
    1911).
    3. Execute the desired assignment, the Equilibrium assignment, for example.

    1920

    PTVGROUP

    18.3.7 Methods for node impedance calculation

    18.3.7

    Methods for node impedance calculation


    You can have node impedances calculated automatically prior to, during, or after the assignment (see Fundamentals: Chpt. 18.1 , page 1888).
    Note: For nodes with Node VDF or Turn VDF being selected for Method for impedances
    at node the impedances will immediately be updated as soon as you edit a relevant input
    attribute.
    Independently of assignments, you may manually calculate node impedances. Set selected
    nodes to the active state, if applicable, and chose the appropriate method.
    Operation Update impedances at node in the procedure sequence (see "Updating the
    impedances at all nodes and main nodes" on page 1073)
    Special function Update impedances at node (Multi-edit nodes) in the network editor
    (see "Updating impedances at nodes" on page 1072)
    Script (via COM interface) (see "Integrating script files or script code into the procedure
    sequence" on page 2668)
    For multiple nodes by editing t0 via Edit nodes or Multi-edit nodes in the Formula tab
    For a single node
    by editing t0 in the node list or in the junction editor or
    via the
    Perform ICA calculation icon in the junction editor (see "Calculating and
    exporting ICA" on page 1499)

    18.4

    Signal timing optimization and coordination


    The methods for signal timing optimization optimize the signal control for a single node or for
    several neighboring nodes. You can apply either one or both of the methods below:
    Signal cycle and split optimization for optimization of a single signal control (see "Optimizing signal cycle and split times for active nodes" on page 1921)
    Signal offset optimization for optimization of multiple signal controls (see "Signal offset
    optimization" on page 1923)
    In the context of signal offset optimization, the analysis of SC offsets might also be of interest
    (see "SC offset analysis" on page 1925).

    18.4.1

    Optimizing signal cycle and split times for active nodes


    You can optimize the cycle times and green times of selected signal controls or all signal controls (see Fundamentals: Chpt. 6.5.4.3 , page 302).
    This method affects all active signalized (main) nodes with the node impedance calculation
    method Node impedance calculation (ICA), to which a signal control has been allocated that
    has not been switched off. All signal controls which have been allocated to these nodes are
    optimized according to their current setting of the Optimization method attribute. Automatically, the optimization is executed for all (main) nodes of a signal control.
    Notes: Prior to optimization, you can check the network's viability for ICA (see "Checking
    the network and fixing errors" on page 1504).

    PTVGROUP

    1921

    18.4.1 Optimizing signal cycle and split times for active nodes
    1. Make sure the required input attributes for this procedure are correct (see Fundamentals:
    Chpt. 6.5.4.1 , page 298).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. In the navigator, select PrT settings> Signal cycle and split optimization.
    4. Make the desired changes.
    Element

    Description

    Use cycle times of If this option has been selected, only cycle times of their particular
    coordination
    cycle time family are permissive for signal controls belonging to a
    groups
    coordination group.
    If this option has not been selected, any cycle time (integer in [s])
    in the interval between the node attributes ICAMinCycletimeOpt
    and ICAMaxCycletimeOpt is permissive.
    Precision of computation

    No decimal places
    The times are rounded to seconds as whole numbers
    One decimal place
    The times are rounded to tenths of a second

    Retain intergreens

    If this option has been selected, the current intergreens are


    retained.
    If this option has not been selected, the intergreen data from
    the intergreen matrix are used. If this matrix is empty, the value of
    the SC attribute Standard intergreen will be used.
    This setting is not regarded for signal controls of external control
    strategies, since their intergreen data is managed externally.

    5. Confirm with OK.


    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Select the desired position and add the procedure Signal cycle and split optimization from
    the Assignments category to the given sequence of procedures (see "Setting up and starting the procedure sequence" on page 1847).
    8. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The signal cycle and split optimization is executed.

    1922

    PTVGROUP

    18.4.2 Signal offset optimization


    Note: Alternatively, you can also execute the signal cycle and split optimization for a single node or several selected nodes (see "Optimizing signal cycles and split of a single
    signal control" on page 1501 and "Updating impedances at nodes" on page 1072).

    18.4.2

    Signal offset optimization


    Signal offset optimization is used to optimize the offset of signal timing at adjacent nodes, so
    that vehicles can pass several consecutive signal controls at green. The general aim is to minimize the total wait time at signal controls for all vehicles (see Fundamentals: Chpt. 6.5.4.4 ,
    page 302)..
    Note: Nodes with switched off signal control are not included.
    1. Make sure that the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.5.4.4 , page 302).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. In the navigator, select PrT settings> Signal offset optimization.

    4. Make the desired changes.

    PTVGROUP

    1923

    18.4.2 Signal offset optimization


    Element

    Description

    Execute analysis Select this option to automatically update output link attributes
    after coordination after signal coordination (see Fundamentals: Chpt. 6.5.4.4 , page
    optimization
    302).
    Note
    This analysis can also be included as a procedure in the procedure sequence (see "SC offset analysis" on page 1925).
    Use coordination
    group filter

    If this option has been checked, the coordination is executed only


    for the signal controls of the selected SC coordination groups.

    Use demand segment filter

    If this option has been checked, the path legs are determined
    from the assignment paths of the selected demand segments
    only. Click the button to select the desired demand segments.
    Note
    This setting is also used for the signal time-space diagram (see
    "Adjusting the signal time-space diagram" on page 2483).

    Max. computation User-defined restriction to the computation time spent for solving
    time for optithe optimization problem. The best solution found up to the spemization
    cified time limitation, is assigned.
    Max. permitted
    vol/cap ratio for
    platooning [%]

    If this saturation is exceeded on a path leg link, the path leg is


    ignored for coordination, because no platoon is retained with too
    high saturation.

    Minimum platoon
    index

    If the platoon index is below this threshold at the end of the path
    leg, the path leg is ignored for coordination, because the platoon
    is not distinct enough.

    Platoon progression formula


    according to
    Robertson

    Enter appropriate values for alpha and beta required by the platoon progression formula.

    Travel times

    For each of the three network object types, select a numerical attribute for path leg travel time calculation and enter a factor, if applicable.
    Note
    This setting is also used for the signal time-space diagram (see
    "Adjusting the signal time-space diagram" on page 2483).

    5. Add the Signal offset optimization procedure of the Assignments category to the position
    of your choice in the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).
    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The signal offset optimization is executed.

    1924

    PTVGROUP

    18.4.3 SC offset analysis

    18.4.3

    SC offset analysis
    Use this function to update the signal coordination output attributes of links such as maximum
    queue length, wait time or platoon index (see Fundamentals: Chpt. 6.5.4.4 , page 302).
    Tips: The names of the corresponding link attributes start with SC coord.
    Alternatively, you can update these values during signal offset optimization (see "Signal
    offset optimization" on page 1923).
    1. Make sure that the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.5.4.1 , page 298).
    2. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    3. Add the procedure Signal offset analysis from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    4. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The attribute values are updated.

    18.5

    Blocking back model settings and calculation


    The blocking back model (pseudo-dynamic assignment, pa) fills the gap between merely static
    procedures, which do not have any temporal reference and cannot determine congestion-related wait times, and dynamic procedures that require long computation times. The blocking
    back model is not an independent assignment procedure, but it modifies the results of a
    currently running or a previously run assignment (see Fundamentals: Chpt. 6.8 , page 314).
    The blocking back model can be applied together with the following static PrT assignment procedures:
    Incremental assignment
    Equilibrium assignment
    Equilibrium_Lohse
    TRIBUT - Equilibrium assignment
    TRIBUT - Equilibrium_Lohse
    Stochastic assignment

    PTVGROUP

    1925

    18.5.1 Executing an assignment with the blocking back model


    Notes: Please make sure, that the demand remains a realistic value when computing
    various scenarios with demand being increased step-by-step. Therefore, you should
    raise the demand by factors like 1.1 or 1.2 gradually.
    Changes to network data which is relevant to the blocking back model, e.g. capacity, will
    not automatically adjust the results of a previously calculated blocking back model (corrected volumes, wait times or absolute and relative queue length) accordingly. In this
    case, you need to re-calculate the blocking back model.
    An assignment with blocking back model determines the paths with their volumes first.
    Then, the spill-back impact is calculated which changes the link volumes. For this reason, the volumes of the OD pairs and of the paths resulting from assignment do not comply with the link volumes. Thus, the flow bundle volumes may differ from the link volumes.
    Even when you select Filter network volumes, the OD pair filter only considers the volumes of the assignment, not the volume after calculation of the blocking back model.

    18.5.1

    Executing an assignment with the blocking back model


    You can configure that the blocking back model is calculated with a PrT assignment procedure.
    1. Specify a procedure sequence, including the PrT assignment procedure of your choice
    (see "Setting and calculating the parameters for PrT assignment" on page 1931).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. In the navigator, select PrT settings> Blocking back model.
    4. Check the option Blocking back calculation is active.
    You can now change the other settings in this window.
    5. Make the desired changes.
    Element

    Description

    Blocking back calIf this option has been checked, blocking back modeling is perculation also
    formed in the external iteration of the PrT assignment procedure.
    during assignment Thus, the results are regarded for link impedances and thus for
    route choice, too.
    Note
    This modus operandi is not recommended, since it significantly
    downgrades the convergence of the respective assignment procedure (see Fundamentals: Chpt. 6.8.1 , page 315).
    If this option has not been checked, the blocking back model is
    calculated as a post-processing step following an assignment,
    and therefore does not influence the route choice.
    6. Otherwise make the desired changes to the blocking back model settings (see "Executing
    the blocking back model after assignment" on page 1927).
    1926

    PTVGROUP

    18.5.2 Executing the blocking back model after assignment


    7. Start the procedure sequence.
    The selected assignment procedure is calculated in combination with the blocking back
    model. If already an assignment of at least one demand segment exists which does not have
    to be re-calculated, then the blocking back model is calculated for any of the assigned
    demand segments prior to assignment execution.
    Note: If you want to assign all assigned PrT demand segments of your network model,
    the blocking back model can be calculated with an assignment with MPA (see "Proportional distribution of demand" on page 1888).

    18.5.2

    Executing the blocking back model after assignment


    1. Make sure that your network model contains the results of a static PrT assignment (see "Setting and calculating the parameters for PrT assignment" on page 1931).
    Note: The blocking back model can be applied together with the following static PrT
    assignment procedures:
    Incremental assignment
    Equilibrium assignment
    Equilibrium_Lohse
    TRIBUT - Equilibrium assignment
    TRIBUT - Equilibrium_Lohse
    Stochastic assignment
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Blocking back model.
    3. Check the option Blocking back calculation is active.
    Now, further options can be set in this window.

    PTVGROUP

    1927

    18.5.2 Executing the blocking back model after assignment

    4. Make the desired changes.


    Notes: These parameters are effective in connection with the respective calculated
    static PrT assignment and the parameters set for it. Assignment with ICA does not
    regard the settings for the blocking back model.

    1928

    PTVGROUP

    18.5.2 Executing the blocking back model after assignment


    Element

    Description

    Limiting capacity

    For the exit flow, the capacity properties of various network object
    types can be regarded.
    Use the link capacity for the blocking back model
    If this option has been selected, the link capacities are used for
    limiting the exit flow. The Link capacity model selection list provides two options:
    Capacity PrT
    The link attribute Capacity PrT limits the exit flow.
    Sum of turn capacities
    The sum of the capacities of all out-going turns (Capacity PrT)
    limits the exit flow.
    Note
    This option is only provided for compliance with out-dated versions. It is no longer recommended. Preferably, the option Use
    the turn capacity for the blocking back model should be used.
    Use the node capacity for the blocking back model
    If this option has been selected, the capacities of nodes and main
    nodes (Capacity PrT) are used for limiting the exit flow. These
    capacities are only regarded for traffic flows on secondary links
    (tmodelspecial = true) towards the node. Traffic flows on major
    legs therefore also have an effect on crossing routes via secondary links.
    Use the turn capacity for the blocking back model
    If this option has been selected, the capacities of turns and main
    turns (Capacity PrT) are used for limiting the exit flow..
    Note
    Instead of the global settings in this window, you can select specific parameters for each node and main node. For that purpose,
    the attribute Use preset blocking back capacity settings has to
    be true for those nodes. In this case, the node attributes Use turn
    capacity in blocking back, Use node capacity in blocking back
    and Use link capacity in blocking back determine the out-flow
    limiting parameter for this node.

    Scaling factor for


    capacities

    Factor for adjustment of the limiting capacity to an assignment


    time interval that differs from one hour.
    Note
    By default, this factor is 1. This means usage of the capacities
    without any changes. In this case, the values refer to a single
    hour, such as the design hourly volume and parameter c of the
    selected VDF (see "Allocating VDFs to network object types" on

    PTVGROUP

    1929

    18.5.2 Executing the blocking back model after assignment


    Element

    Description
    page 1892).

    Average space
    required per car
    unit

    Space, a passenger car unit requires at an average


    Note
    Due to gaps that occur between vehicles, this value is greater
    than the average length of a vehicle.

    Phase 1

    Duration of phase 1
    Duration of simulation phase 1 in which the queues build up, e.g.
    30min or 1h.
    Number of shares for flow distribution in phase 1
    Number of portions resulting from the distribution of demand in
    the simulation interval which are gradually loaded onto the network in phase 1 (=N).
    Notes
    In this phase, the number of iterations is approximately (1 - 1/)
    N, i.e. the excess congestion factor flows into the equation (see
    Fundamentals: Chpt. 6.8.2 , page 317).
    The higher N, the more evenly the distribution of the demand to
    the network. We recommend a ratio of approximately 2M = N.

    1930

    PTVGROUP

    18.6 Setting and calculating the parameters for PrT assignment


    Element

    Description

    Perform Phase 2
    (Wait time calculation)

    If this option has been checked, not only the buildup of the
    queues is modeled, but also the clearing of the congestion.

    Phase 2

    Number of shares for flow distribution in phase 2


    Number of portions, in which the capacity is propagated gradually
    in phase 2 (=M).
    Notes
    For this parameter, values between 2 and 10 are recommended,
    since the demand in Phase 2 is lower than the demand in Phase
    1.
    The number of performed iterations depends on the retained
    queue lengths and thus on occurring capacity losses. If no capacity losses occur (all P = 100%), the traffic demand passes in
    times the simulation interval through the network. Due to the fact,
    that one step of the second phase corresponds to the M-the time
    proportion of the simulation period, (-1)M iteration steps can
    thus be expected.
    Maximum number of iterations in Phase 2
    Phase 2 terminates as soon as the number of iterations is reached.
    Note
    With an appropriate value, a sufficiently accurate wait time can be
    calculated though the queue has not dispersed yet completely.

    5. Confirm with OK.


    The desired attribute values are recalculated (see Fundamentals: Chpt. 6.8 , page 314).
    Note: You can reset the attribute values to their original values: Uncheck option Blocking
    back calculation active and confirm OK.

    18.6

    Setting and calculating the parameters for PrT assignment


    Visum provides several assignment procedures for the PrT. There are static assignment procedures without explicit time modeling as well as procedures which use a time dynamic traffic
    flow model (see Fundamentals: Chpt. 6 , page 226).
    Any desired assignment procedure you may integrate in the user- defined procedure
    sequence. For each procedure, specific parameters have to be set. Additionally, general settings are regarded by various procedures.
    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).

    PTVGROUP

    1931

    18.6.1 Incremental assignment (static)


    Subjects
    Incremental assignment (static)
    Equilibrium assignment (static)
    Equilibrium assignment LUCE
    Equilibrium_Lohse assignment (static)
    Assignment with ICA
    Stochastic assignment (static)
    TRIBUT - Equilibrium assignment
    TRIBUT - Equilibrium_Lohse (static)
    Dynamic User Equilibrium (DUE)
    Dynamic stochastic assignment

    18.6.1

    Incremental assignment (static)


    Incremental assignment divides the demand matrix on a percentage basis into several partial
    matrices. These partial matrices are then successively assigned to the network. The route
    search accounts for impedance resulting from the traffic volume of the previous step (see Fundamentals: Chpt. 6.11 , page 336).

    18.6.1.1

    Selecting and executing incremental assignment


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.11.3 , page 339).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.

    1932

    PTVGROUP

    18.6.1.2 Parameters of incremental assignment


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the drop-down list, select the Incremental assignment entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: Incremental assignment procedure window opens.
    15. Set the desired parameters (see "Parameters of incremental assignment" on page 1933).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    18.6.1.2

    Parameters of incremental assignment

    PTVGROUP

    1933

    18.6.2 Equilibrium assignment (static)


    Element Description
    1 - 12

    18.6.2

    Per iteration step, the user-defined percentage of demand will be assigned.


    Notes
    Maximum twelve iteration steps can be performed.
    The sum of the percentages must amount to 100%. If 0% is entered for a step,
    further proportions will be ignored.
    Tip
    To assign less than 100% of a matrix, first generate a partial matrix using matrix
    multiplication with a factor <1 (see "Multiplying matrix values" on page 1783).

    Equilibrium assignment (static)


    The Equilibrium assignment distributes the demand according to Wardrop's first principle (see
    Fundamentals: Chpt. 6.12 , page 342).

    18.6.2.1

    Selecting and executing the Equilibrium assignment


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.12.3 , page 345).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    6. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    7. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.

    1934

    PTVGROUP

    18.6.2.2 Parameters of Equilibrium assignment


    8. In the Select mode selection list, click the desired entry.
    9. In the Demand segments section, select the desired entries.
    Tips: To select several individual entries hold down the C TRL key while clicking each
    single entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    10. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    11. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    12. In the selection list, select the Equilibrium assignment entry.
    The selected entry is displayed in the column.
    13. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: Equilibrium assignment window opens.
    14. Set the desired parameters (see "Parameters of Equilibrium assignment" on page 1935).
    15. Confirm with OK.
    16. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    18.6.2.2

    Parameters of Equilibrium assignment

    PTVGROUP

    1935

    18.6.2.2 Parameters of Equilibrium assignment


    Element

    Description

    Use current
    assignment
    result as initial
    solution

    If this option is checked, the assignment will use existing paths and
    volumes of the previous assignment as initial solution.
    Notes
    This option is recommended in the case of modified demand (e.g. due to
    'Read matrix additionally' or matrix editing in the matrix editor). First, the
    former assignment result is scaled according to the new demand and
    then the assignment continues to calculate the new result. Usually, this
    requires less iterations than a complete recalculation. In this way, a lot of
    computation time can be saved in models with feedback from the assignment calculation to the demand calculation.
    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 satisfy
    Wardrop's first principle of the equilibrium procedure.
    If this option is not selected, the initial solution is calculated using
    incremental assignment (see "Incremental assignment (static)" on page
    1932). For this initial solution calculation, the demand portion defined in
    the section Calculate initial solution: Incremental assignment is used
    for each iteration step.
    Note
    These settings are also regarded if an existing assignment result is to be
    used as initial solution, but no assignment result can be found.

    Initial solution
    calculation by
    incremental
    assignment

    1936

    OD demand share per iteration step


    Incremental assignment assigns the user-defined percentage of
    demand per iteration step (see "Parameters of incremental assignment"
    on page 1933).
    Notes
    This setting applies in two cases:
    The option Use current assignment result as initial solution has
    not been selected.
    The option Use current assignment result as initial solution has
    been selected, but an assignment result could not be found.

    PTVGROUP

    18.6.2.2 Parameters of Equilibrium assignment


    Element

    Description

    Termination
    condition

    Visum cancels the iteration process for calculating the equilibrium, if one
    of the following conditions is fulfilled (see Fundamentals: Chpt. 6.12 ,
    page 342).
    Permitted deviation of impedances of alternative routes
    Absolute deviation
    Absolute difference of impedances between coupled equalization of
    routes. The procedure terminates as soon as the value falls below.
    Relative deviation
    Proportional difference of impedances between coupled equalization of routes. The procedure terminates as soon as the value
    falls below.
    Max. number of iterations
    The procedure terminates after the specified number of external iterations.
    Notes
    For example this option is relevant in heavily overloaded networks,
    since it is possible that no state of balance can be reached with the
    given permitted deviations.
    For an existing assignment, you can enter value 0 to adjust only the path
    volumes.
    Max. gap
    Measure of the difference between the current loaded state and the
    balanced state (see Fundamentals: Chpt. 6.9 , page 329). The procedure terminates as soon as the value falls below.
    Blocking back calculation during assignment
    Max. relative deviation
    The procedure is canceled if the congestion volumes and wait times
    of two external iterations deviate by a maximum of the entered
    value.
    Note
    This constraint is only regarded for assignment with simultaneous
    blocking back model calculation. In this case, you must select the
    Blocking back calculation also during assignment option (see "Executing the blocking back model after assignment" on page 1927).

    Network balan- Max. number of iterations


    cing
    Via this button, you can set the number of internal balancing iterations.
    The number may vary due to the fact, which of the external iterations is
    currently being calculated. This is why you can assign the steps of external iterations to classes (see "Setting the number of balancing iterations"
    on page 1938).

    PTVGROUP

    1937

    18.6.2.2 Parameters of Equilibrium assignment


    Element

    Description
    Notes
    It might make sense to calculate a lower number of internal balancing iterations in the first external iterations.
    The button label shows the current settings in brief.
    By default, no classes have been defined, thus, the number of balancing
    iterations is the same for all external iterations.
    When reading older versions or procedure parameter files, a class with
    a constant number of internal balancing iterations is defined.

    Setting the number of balancing iterations


    1. Make sure the Parameters: Equilibrium assignment window is open (see "Parameters of
    Equilibrium assignment" on page 1935).
    2. Click the button next to Max. number of iterations.
    The window Max. number of balancing iterations opens. When being opened for the first
    time, the list contains a single entry.

    1938

    Element

    Description

    External iteration

    Arrangement of the iteration steps of the external iteration in classes


    Note
    Double-click in the selected cell to edit the value.
    The maximum class limit is no subject to changes.
    Note
    For an existing assignment, you can enter value 0 to adjust only
    the path volumes.

    Number of balancing iterations

    Number of internal iterations for balancing of route volumes.


    Note
    Double-click in the selected cell to edit the value.

    Create

    Via this button you can create additional classes.


    Notes
    A new class is automatically added after the currently selected
    class. For the new class, the class limit is automatically set to the
    middle between the two neighboring class limits. If the new class
    is added to the topmost limit, the maximum value is raised automatically.
    Double-click in the selected cell to edit the value.
    The maximum class limit is no subject to changes.

    Delete

    Via this button, you remove the currently selected row.

    PTVGROUP

    18.6.3 Equilibrium assignment LUCE


    3. Confirm with OK.
    The number of balancing iterations has been set for the defined classes of external iterations.

    18.6.3

    Equilibrium assignment LUCE


    The basic idea of the procedure is the following: for any node, a user equilibrium shall be reached on all forward edges for the local route choice of drivers heading to a destination zone
    (see Fundamentals: Chpt. 6.13 , page 351).

    18.6.3.1

    Selecting and executing the Equilibrium assignment LUCE


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.13.5 , page 363).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.

    PTVGROUP

    1939

    18.6.3.1 Selecting and executing the Equilibrium assignment LUCE


    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the Equilibrium assignment LUCE entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: Equilibrium assignment LUCE window opens.
    15. Set the desired parameters (see "Parameters of Equilibrium assignment LUCE" on page
    1941).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    Note: For more details on the calculated results please refer to the log file. It contains - for
    each iteration - the number of network objects having a too great deviation when the procedure terminated. If the number by transport system goes below a certain value, the network objects are listed in detail. These network objects you may analyze for input data
    errors or other problems.
    You can define the number up to which non-converging network objects shall be listed
    individually (see "Limiting the number of non-converged network objects logged to the
    log file" on page 1892).

    1940

    PTVGROUP

    18.6.3.2 Parameters of Equilibrium assignment LUCE


    18.6.3.2

    Parameters of Equilibrium assignment LUCE

    Element

    Description

    Use current
    assignment
    result as initial
    solution

    If this option is checked, the assignment will use existing paths and
    volumes of the previous assignment as initial solution.
    Notes
    This option is recommended in case of modified demand (e.g. due to
    Open matrix or Edit matrix data in the matrix editor). First, the former assignment result is scaled according to the new demand and then the assignment continues to calculate the new result. Usually, this requires less
    iterations than a complete recalculation. In this way, a lot of computation
    time can be saved in models with feedback from the assignment calculation to the demand calculation.
    Multiple network modifications and repeated use of this option result in a
    different routes compared to the result of a new assignment without this
    option, since in the Equilibrium assignment there are numerous possible routes which satisfy Wardrop's principle.
    If this option has not been selected, the assignment is calculated completely.

    Termination
    condition

    PTVGROUP

    Visum cancels the iteration process for calculating the equilibrium, if one
    of the following conditions is fulfilled (see Fundamentals: Chpt. 6.12 ,
    page 342).
    Max. number of iterations
    The procedure terminates after the specified number of external iterations. At least three iterations are required, since the first two iterations
    do not return relevant results.

    1941

    18.6.4 Equilibrium_Lohse assignment (static)


    Element

    Description
    Note
    For example this option is relevant in heavily overloaded networks,
    since it is possible that no state of balance can be reached with the
    given permitted deviations.
    Max. gap
    Measure for the level of convergence in the network (see Fundamentals:
    Chpt. 6.9 , page 329). The procedure terminates as soon as the value is
    exceeded.
    Note
    Existing results can be reproduced, since the default value is 0.

    18.6.4

    Multithreading

    Number of zones to be balanced in parallel


    Enter the number of zones to be calculated simultaneously. This number
    depends on your computer's number of real processor cores. This setting applies independently of the settings made via Edit> User Preferences> Working environment (see "Specifying the number of
    processor cores to be used" on page 873).
    Tip
    The maximum computation speed can be reached with 3 or 4 zones,
    even if your computer had more processor cores built in. With a greater
    number, conflicts might occur during the balancing step calculations,
    which would slow down the computation.
    Note
    To reproduce the results, the same number of zones has to be set here.
    To minimize the deviation in the case of a different number of processore cores, enter a value less than 10 -6 for Max. gap.

    Optimization of
    the proportionality of
    route volumes
    along meshes

    No optimization
    Path volumes are not harmonized
    Separate balancing for each transport system
    Path volumes are harmonized separately per transport system (see Fundamentals: Chpt. 6.13.8 , page 364).
    Joint balancing for equi-impedance meshes for all transport systems, if possible
    Path volumes are harmonized jointly for all transport systems, if possible
    (see Fundamentals: Chpt. 6.13.8 , page 364).

    Equilibrium_Lohse assignment (static)


    The Equilibrium_ Lohse assignment models the "learning process" of road-users in the network. Starting with an "all or nothing assignment", drivers consecutively include information
    gained during their last journey for the next route search (see Fundamentals: Chpt. 6.15 , page
    374).

    1942

    PTVGROUP

    18.6.4.1 Selecting and executing Equilibrium_Lohse


    18.6.4.1

    Selecting and executing Equilibrium_Lohse


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.14.2 , page 371).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    PTVGROUP

    1943

    18.6.4.2 Parameters of the Equilibrium_Lohse assignment


    A selection list appears.
    13. In the selection list, select the Equilibrium_Lohse entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: Equilibrium_Lohse window opens.
    15. Set the desired parameters (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    Note: For more details on the calculated results please refer to the log file. It contains - for
    each iteration - the number of network objects having a too great deviation when the procedure terminated. If the number by transport system goes below a certain value, the network objects are listed in detail. These network objects you may analyze for input data
    errors or other problems.
    You can define the number up to which non-converging network objects shall be listed
    individually (see "Limiting the number of non-converged network objects logged to the
    log file" on page 1892).
    18.6.4.2

    1944

    Parameters of the Equilibrium_Lohse assignment

    PTVGROUP

    18.6.4.2 Parameters of the Equilibrium_Lohse assignment

    Element

    Description

    N = Maximum
    number of iterations

    The procedure terminates after the specified number of external iterations.

    Route volumes

    Route volumes are calculated according to the method of successive


    averages (MSA). Therefore, you need to define the exponent (value
    range 04).
    Notes
    For smoothing the route volumes, we recommend an exponent between 1 and 1.5.
    With exponent = 1 the formula complies with the formula used by the
    method of successive averages (MSA). This ensures a safe but slow
    convergence. A greater value normally reduces the number of iteration steps, but does not necessarily lead to convergence.

    PTVGROUP

    1945

    18.6.5 Assignment with ICA

    18.6.5

    Element

    Description

    Estimated impedances

    In the selection list, select the method for smoothing the estimated
    impedance. The methods provide different input options for the Delta
    value computation.
    Notes
    We recommend to test the three smoothing methods prior to the
    actual calculation.
    Heuristic rule
    Lotka-Volterra rule
    Note
    In most cases, the Lotka Volterra method is faster than the heuristic
    method; however, the quality of the calculation results depends on
    the used network.
    Method of Successive Averages
    For this option you need to define the exponent (value range 01).
    Notes
    For the exponent, we recommend a value close to 0.15.
    With parameter value = 1 the formula complies with the formula used
    by the method of successive averages. This ensures a safe but slow
    convergence.
    Do not smooth impedances
    This option is used to obtain convergence faster, if exponential smoothing of impedance values impairs the convergence of a procedure
    instead of improving it.
    If this option has been selected, the currently estimated impedance
    equals the current impedance.

    Termination condition

    The procedure terminates as soon as the deviation between two subsequent iteration steps goes below a certain threshold. You may
    adjust the formula for the threshold.

    Assignment with ICA


    Compared to other procedures, volume-delay functions by lane that are continuously re-calibrated by means of ICA lead to a significantly improved convergence behavior, since the lane
    geometry and interdependencies between the individual turns via a node are accounted for in
    detail (see Fundamentals: Chpt. 6.15 , page 374).

    18.6.5.1

    Selecting and executing Assignment with ICA


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).

    1946

    PTVGROUP

    18.6.5.1 Selecting and executing Assignment with ICA


    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.15.3 , page 377).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments. To select several individual entries hold down the C TRL key while clicking each single entry. To select
    several consecutive entries hold down the SHIFT key while clicking the first and the
    last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the Assignment with ICA entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters for assignment with ICA window opens.
    PTVGROUP

    1947

    18.6.5.2 Parameters for Assignment with ICA


    15. Set the desired parameters (see "Parameters for Assignment with ICA" on page 1948).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    Note: For more details on the calculated results please refer to the log file. It contains - for
    each iteration - the number of network objects having a too great deviation when the procedure terminated. If the number by transport system goes below a certain value, the network objects are listed in detail. These network objects you may analyze for input data
    errors or other problems. You can define the number up to which non-converging network objects shall be listed individually (see "Limiting the number of non-converged network objects logged to the log file" on page 1892).
    You have several options for output of the results calculated (see Fundamentals: Chpt.
    6.15.3 , page 377).
    18.6.5.2

    Parameters for Assignment with ICA


    Assignment with ICA:Input tab
    In this tab, enter the basic parameters for the procedure.
    Element

    Description

    Use current assignment result as


    initial solution

    If this option is checked, the assignment will use existing paths


    and volumes of the previous assignment as initial solution.
    Note
    This option is recommended in the case of modified demand (e.g.
    due to 'Read matrix additionally' or matrix editing in the matrix editor).
    First, the former assignment result is scaled according to the new
    demand and then the assignment continues to calculate the new
    result. Usually, this requires less iterations than a complete recalculation. In this way, a lot of computation time can be saved in
    models with feedback from the assignment calculation to the demand
    calculation.
    If this option has not been checked, the calculation starts from the
    unloaded network.

    Initial setting section

    1948

    Saturation flow
    rate of turns

    Saturation flow rate of turns, which is multiplied by the number of


    lanes.

    Number of lanes
    at shared lane

    Total capacity for each turn


    Select this option to assign each turn the total capacity.
    Share of capacity for each turn
    Select this option to assign each turn a share of capacity.

    PTVGROUP

    18.6.5.2 Parameters for Assignment with ICA


    Element

    Description

    Minimum capacity Select a direct or indirect numerical attribute of turns and enter the
    of turns
    factor for the computation of the minimum turn capacity which is to be
    considered.
    Blocking back model section
    Use the link capacity for the
    blocking back
    model

    If this option has been selected, the link capacities are used for limiting the exit flow.
    Capacity PrT
    If this option is selected, the link attribute Capacity PrT restricts the
    outflow.
    Sum of turn capacities
    If this option is selected, the total of the capacities of all outgoing
    turns (Capacity PrT) restricts the outflow.

    Number of shares Enter the number of shares for Phase 1 (see "Executing the blocking
    for the volume dis- back model after assignment" on page 1927).
    tribution
    Average space
    required per car
    unit

    Space, a passenger car unit requires at an average


    Note
    Due to gaps that occur between vehicles, this value is greater than
    the average length of a vehicle.

    Notes: The assignment time interval for ICA and the blocking back model is one hour.
    After the assignment, all global parameters for blocking back (Calculate menu> General
    procedure settings > PrT settings> Blocking back model) and all blocking back parameters of ICA nodes are set to the values you set for the blocking back model. In this way
    you can make sure that the settings match the calculated results.
    Assignment with ICA:Procedure sequence tab
    In this tab, you select the subordinate assignment procedure and set up the parameters for it.
    Furthermore, the weight of the new solution for exponential smoothing of turn volumes and
    turn capacities and the termination conditions have to be defined.

    PTVGROUP

    1949

    18.6.5.2 Parameters for Assignment with ICA


    Element

    Description

    Subordinate assi- In the list, you can click Equilibrium_Lohse (see "Parameters of the
    gnment procedure Equilibrium_Lohse assignment" on page 1944), Equilibrium assignment (see "Parameters of Equilibrium assignment" on page 1935)
    or Equilibrium assignment LUCE (see "Equilibrium assignment
    LUCE" on page 1939).
    Click the Parameters button to enter the assignment parameters for
    the selected procedure.
    Weight of the new Use the slider to determine a value between 0=no weight and
    solution for expo- 1=100% and enter the appropriate factor.
    nential smoothing
    of turn volumes
    and turn capacities
    Termination conditions

    Maximum number of outer iterations


    Enter the maximum number of outer iterations.
    GEH between turning flows in previous assignment and current
    assignment is
    Under Condition, enter a numerical value and define the share in the
    Share of turning vehicles which satisfy the condition section.
    GEH between turning flows in current assignment and smoothed
    ICA turning volumes is
    Under Condition, enter a numerical value and define the share in the
    Share of turning vehicles which satisfy the condition section.
    Relative gap between ICA wait time and VDF wait time is
    Under Condition, enter a numerical value and define the share in the
    Share of turning vehicles which satisfy the condition section.

    Assignment with ICA:Output tab


    In this tab, you determine the data which is to be stored.
    Element

    Description

    During the proIf this option has been selected, the attribute files are saved to the
    cedure, save con- project folder Attributes: <Path>.
    vergence attributes
    If this option is not selected, the attribute files will not be saved.
    of turns and main
    turns as *.csv files
    Save the conIf this option is selected, the attribute data will be saved as uservergence attributes defined attributes.
    of turns and main
    If this option is not selected, the attribute data will not be saved.
    turns as UDAs at

    1950

    PTVGROUP

    18.6.6 Stochastic assignment (static)


    Element

    Description

    the end of the procedure


    Save the Excel
    If this option has been selected, the report is saved to the project
    report at the end of folder ICA: <Path>.
    the procedure
    If this option is not selected, the report will not be saved.

    Notes: Except for the following ones, all parameters of subordinate assignment procedures are subject to changes: For the Equilibrium assignment, blocking back parameters are not accessible. Furthermore, the parameter Use existing assignment as
    initial solution is set to TRUE for the Equilibrium assignment, but this setting cannot be
    changed.
    While the procedure is being executed, convergence data is written to the list Goodness
    of PrT assignment with ICA (see "Opening a list" on page 2299). It contains only calculated values and is therefore not editable. The list Goodness of PrT assignment is cleared prior to the Assignment with ICA and will not be re-filled as long as the procedure is
    running.

    18.6.6

    Stochastic assignment (static)


    In stochastic assignment, a quantity of alternative routes is initially calculated and the demand
    is distributed across the alternatives based on a distribution model (see Fundamentals: Chpt.
    6.16 , page 385).

    18.6.6.1

    Selecting and executing the Stochastic assignment


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.16.2 , page 386).
    2. From the Calculate menu, choose General procedure settings.
    The General procedures settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)

    PTVGROUP

    1951

    18.6.6.1 Selecting and executing the Stochastic assignment


    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the Stochastic assignment entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: Stochastic assignment window opens.
    15. Set the desired parameters (see "Parameters of Stochastic assignment" on page 1953).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.

    1952

    PTVGROUP

    18.6.6.2 Parameters of Stochastic assignment


    Note: For more details on the calculated results please refer to the log file. It contains - for
    each iteration - the number of network objects having a too great deviation when the procedure terminated. If the number by transport system goes below a certain value, the network objects are listed in detail. These network objects you may analyze for input data
    errors or other problems.
    You can define the number up to which non-converging network objects shall be listed
    individually (see "Limiting the number of non-converged network objects logged to the
    log file" on page 1892).
    18.6.6.2

    Parameters of Stochastic assignment


    Stochastic assignment:Basis tab

    PTVGROUP

    1953

    18.6.6.2 Parameters of Stochastic assignment


    Element

    Description

    Use current assignment result as


    initial solution

    If this option is checked, the assignment will use existing paths


    and volumes of the previous assignment as initial solution.
    Note
    This option is recommended in the case of modified demand (e.g.
    due to 'Read matrix additionally' or matrix editing in the matrix editor).
    First, the former assignment result is scaled according to the new
    demand and then the assignment continues to calculate the new
    result. Usually, this requires less iterations than a complete recalculation. In this way, a lot of computation time can be saved in
    models with feedback from the assignment calculation to the demand
    calculation.
    If this option has not been checked, the calculation starts from the
    unloaded network.

    Termination conditions General

    Maximum number of iterations


    The procedure terminates after the specified number of external iterations.

    Termination conditions Balancing

    Maximum number of iterations


    Via this button, you can set the number of balancing iterations. The
    number may vary due to the fact, which of the external iterations is
    currently being calculated. This is why you can assign the steps of
    external iterations to classes (see "Setting the number of balancing
    iterations" on page 1938).
    Notes
    In the first external iterations, in order to save computation time it
    might be useful to calculate a lower number of internal balancing iterations prior to searching for new paths.
    The button label shows the current settings in brief.
    By default, no classes have been defined, thus, the number of balancing iterations is the same for all external iterations.
    When reading older versions or procedure parameter files, a class
    with a constant number of internal balancing iterations is defined.
    Parameters in formulae
    The procedure terminates as soon as the deviation of impedances
    and route volumes calculated in two subsequent iteration steps goes
    below a certain threshold. You may adjust the formula for the threshold.

    1954

    PTVGROUP

    18.6.6.2 Parameters of Stochastic assignment


    Stochastic assignment:Smoothing tab

    The parameters correspond to the parameters of the Equilibrium_ Lohse assignment (see
    "Parameters of the Equilibrium_Lohse assignment" on page 1944).
    Notes: In contrast to the Equilibrium_Lohse assignment the value range of the exponent
    is 02 in the Route volumes section.
    For smoothing the route volumes, we recommend an exponent between 1 and 1.5.
    Stochastic assignment:Search tab
    In this tab, you define how to determine PrT routes.

    PTVGROUP

    1955

    18.6.6.2 Parameters of Stochastic assignment

    1956

    PTVGROUP

    18.6.6.2 Parameters of Stochastic assignment


    Element

    Description

    Randomized
    search

    Perform
    If this option has been checked, the best-path search is performed several
    times, each time using different conditions: link impedances are randomly
    increased or reduced In this way, also less attractive routes are found.
    This option models the differences in the road users ratings.
    Number of extra search iterations
    Via this button, you can set the number of extra search iterations for finding more routes. The number may vary due to the fact, which of the external iterations is currently being calculated. This is why you can assign the
    steps of external iterations to classes (see "Setting the number of search
    iterations" on page 1957).
    Notes
    For saving computation time it might make sense to calculate a different
    number of extra search iterations in the first internal balancing iterations.
    The button label shows the current settings in brief.
    By default, no classes have been defined, thus, the number of search iterations is the same for all external iterations.
    Sigma
    Standard deviation of the normal distribution (with mean R) from which
    the randomly varied impedance is drawn.
    Note
    The power of the impedance Rgoes into the calculation. An exponent of
    >0.5 leads to increased scattering and thus to more alternative routes.

    Detour test

    Perform
    Select this option to discard routes that match existing routes, except for
    one segment that is considerably longer than in the existing routes (see
    Fundamentals: Chpt. 6.16.3 , page 388).
    A route is deleted, if the following condition applies to a mesh
    Via this formula you define, how much longer the travel time of a route
    segment may be at the most before the longer route is discarded. Here,
    the travel time t0 in the unloaded network is used.

    Setting the number of search iterations


    1. Make sure that in the Parameters: Stochastic assignment window, the Search tab is
    open (see "Stochastic assignment (static)" on page 1951).
    2. Click the button next to Number of extra search iterations.
    The Number of extra search iterations window opens.

    PTVGROUP

    1957

    18.6.6.2 Parameters of Stochastic assignment


    Element

    Description

    External iteration

    Arrangement of the iteration steps of the external iteration in classes


    Note
    Double-click in the selected cell to edit the value.
    The maximum class limit is no subject to changes.

    Number of extra
    search iterations

    Number of search iterations for determination of further routes


    Note
    Double-click in the selected cell to edit the value.

    Create

    Via this button you can create additional classes.


    Notes
    A new class is automatically added after the currently selected
    class. For the new class, the class limit is automatically set to the
    middle between the two neighboring class limits. If the new class
    is added to the topmost limit, the maximum value is raised automatically.
    Double-click in the selected cell to edit the value.
    The maximum class limit is no subject to changes.

    Delete

    Via this button, you remove the currently selected row.

    3. Confirm with OK.


    The number of search iterations has been set for the defined classes of external iterations.
    Stochastic assignment:Preselection tab
    In this tab, you define how to select the found routes.

    1958

    PTVGROUP

    18.6.6.2 Parameters of Stochastic assignment

    Element

    Description

    A route is deleted, Use this formula to define to which extent the current estimated impeif
    dance and the travel time t0 of a route may exceed the values of the
    best route found. If both conditions are satisfied, the longer route will
    be discarded. Here, the travel time t0 in the unloaded network is
    used.
    Note
    The estimated impedance sums up from the impedances of all network objects traversed by the route.
    Check only once
    when route is
    found for the first
    time

    If this option has been checked, only when finding the route for the
    first time, Visum checks whether it meets the criterion and should be
    dismissed. Afterwards, the route remains valid in all further iterations.
    This option is enabled by default.

    Stochastic assignment:Choice tab


    In this tab, you define how to distribute the demand to the found routes.

    PTVGROUP

    1959

    18.6.6.2 Parameters of Stochastic assignment

    1960

    Element

    Description

    Choice model

    From the drop down list, select the appropriate choice model. The
    model controls the distribution of the demand to the individual routes
    according to the route impedances. For each choice model, you can
    set certain parameters (see Fundamentals: Chpt. 6.10 , page 329).

    Independence

    Via these options you decide how to calculate the independence of


    the routes. You select the attribute and calculation method to be used
    (see Fundamentals: Chpt. 6.16.4 , page 391).
    Define by t0
    If this option has been checked, the similarity of two routes is calculated from the free-flow travel time. Here, the total routes are regarded.
    Define by length
    If this option has been checked, the similarity of two routes is calculated from the length. Here, the common section of the routes is
    regarded.
    Precise calculation according to Cascetta
    If this option has been selected, the commonality factor for the calculation of the independence of routes is calculated by means of the
    C Logit approach according to Cascetta.
    Instant approximate calculation according to Ben Akiva
    If this option has been checked, the Commonality factor, which enters
    the calculation of the independence, is calculated with a simpler

    PTVGROUP

    18.6.7 TRIBUT - Equilibrium assignment


    Element

    Description
    approach according to Ben Akiva.
    Notes
    The calculation according to Cascetta requires a lot of calculation
    time due to the comparison of the routes in pairs; it is yet very precise.
    Ben Akiva saves calculation time yet impairs the accuracy of the calculation results.

    18.6.7

    TRIBUT - Equilibrium assignment


    TRIBUT - Equilibrium assignment is particularly suited for modeling road toll (see Fundamentals: Chpt. 6.17 , page 397).

    18.6.7.1

    Selecting and executing the TRIBUT - Equilibrium assignment


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.17.1 , page 397).
    Note: Especially, the toll has to be defined. For the TRIBUT - Equilibrium assignment,
    enter the appropriate link attribute value for Toll-PrTSys (see "Links: PrT TSys tab" on
    page 1109).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)
    Note: For impedance calculation, the link attribute Toll-PrTSys should not be used,
    since it is automatically accounted for by the procedure in addition to impedance
    (tCur, length) (see "Definition and application of volume-delay functions" on page
    1892).

    PTVGROUP

    1961

    18.6.7.1 Selecting and executing the TRIBUT - Equilibrium assignment


    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the TRIBUT - Equilibrium assignment entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: TRIBUT - Equilibrium assignment window opens.
    15. Set the desired parameters (see "Parameters of TRIBUT - Equilibrium assignment" on
    page 1963).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.

    1962

    PTVGROUP

    18.6.7.2 Parameters of TRIBUT - Equilibrium assignment


    18.6.7.2

    Parameters of TRIBUT - Equilibrium assignment

    PTVGROUP

    1963

    18.6.7.2 Parameters of TRIBUT - Equilibrium assignment


    Element

    Description

    Value of Time dis- In the table, you specify parameters for the Value of Time calculation
    tribution function for reach demand segment (see Fundamentals: Chpt. 6.17.3 , page
    405)
    OD pair-dependent
    If this option has been selected, you define the parameters for the
    Value of Time calculation by OD pair. Click this button in the Median,
    Dispersion parameters and Std. dev. of the LogN distr. columns to
    open the Sampling points for Value of Time window and make further settings (see "Defining OD pair-dependent parameters for Value
    of Time calculation" on page 1965).
    If this option has not been selected, you define identical parameters for all OD pairs for the Value of Time calculation. Enter the
    parameters in the columns Median and Dispersion parameter.
    Median
    Median of the Value of Time for the LogN distribution of the random
    variable (VT).
    Dispersion parameter
    Standard deviation of the associated standard LogN distribution
    Using this value, Visum automatically calculates the standard deviation of the LogN distribution of the random variable Value of Time
    (VT) (Std. dev. of the LogN distr.).
    Note
    This calculated value you have to use as standard deviation for the
    graphical display of this function in a spreadsheet program, for example.
    Use factor for zone type
    If the option has been selected, you can enter a zone type-specific
    weighting factor for the Value of Time via the button in the Factors
    column.
    Factors
    Click this button to open a window for setting the weighting factors
    (see "Specifying weighting factors per zone type" on page 1966)

    1964

    PTVGROUP

    18.6.7.2 Parameters of TRIBUT - Equilibrium assignment


    Element

    Description

    Termination conditions General

    Maximum number of iterations


    The procedure terminates after the specified number of external iterations.
    Maximum relative deviation of impedance and road toll
    The procedure terminates as soon as the relative deviation of the
    total impedance and the total road toll calculated in two subsequent
    iteration steps goes below the threshold.
    Blocking back calculation during assignment
    Max. relative deviation
    The procedure is canceled if the congestion volumes and wait
    times of two external iterations deviate by a maximum of the entered value.
    Note
    This constraint is only regarded for assignment with simultaneous
    blocking back model calculation. In this case, you must select the
    Blocking back calculation also during assignment option (see "Executing the blocking back model after assignment" on page 1927).

    Termination conditions for balancing between


    different road toll
    levels

    Maximum deviation in Car Units


    Balancing of volumes between two road toll levels terminates as
    soon as the deviation of the distribution function goes below this
    value.

    Termination conditions for balancing alternative


    routes with identical road toll

    Permitted deviation of impedances of alternative routes


    Absolute
    Balancing between two alternative routes of the same road toll level
    terminates as soon as the difference of the impedances goes below
    the specified value.
    Relative
    Balancing between two alternative routes of the same road toll level
    terminates as soon as the relative deviation of the impedances goes
    below the specified value.

    Defining OD pair-dependent parameters for Value of Time calculation


    In the Sampling points for Value of Time window you set the OD pair-specific parameters for
    the Value of Time computation. For specific attribute values of a selected OD pair attribute you
    specify the parameters. Based on these sampling points, linear interpolation is performed.
    Thus, the parameters for the attribute values between the sampling points are automatically
    returned.

    PTVGROUP

    1965

    18.6.8 TRIBUT - Equilibrium_Lohse (static)


    Element

    Description

    OD pair attribute

    Click the button and select the attribute whose values shall be used
    as sampling points.
    Note
    Usually, the attribute Matrix value is used. These values can be derived from infrastructure data of zones, for example.

    Create

    Click this button to add another row for another sampling point to the
    grid.

    Delete

    Via this button, you remove the currently selected row.

    Attribute value

    Here, enter the attribute value to which the user-defined parameters


    apply.

    Median

    Median of the Value of Time for the LogN distribution of the random
    variable (VT).

    Dispersion parameter

    Standard deviation of the associated standard LogN distribution


    Using this value, Visum automatically calculates the standard deviation of the LogN distribution of the random variable Value of Time
    (VT) (Std. dev. of the LogN distr.).
    Note
    This calculated value you have to use as standard deviation for the
    graphical display of this function in a spreadsheet program, for example.

    Analyze

    Via this button a window opens. By OD pair, you can here call the display of the value of the selected OD pair attribute and the values
    resulting for the parameters Median und Dispersion parameter.

    Specifying weighting factors per zone type

    18.6.8

    Element

    Description

    Weighting factor
    of the origin zone

    Value of Time weighting factor for a zone's origin demand. Accordingly, the destination factor is derived as follows: 1 - origin factor. By
    default, origin factor = destination factor = 0.5 applies.

    Weighting factors
    by zone type

    Via the input fields, you may set a weighting factor for the value of
    time by zone type. Normally, the factors are close to 1. For example,
    a factor > 1 means a higher value of time for the zone's origin (or destination) demand.

    TRIBUT - Equilibrium_Lohse (static)


    TRIBUT Equilibrium_Lohse is a modified version of the conventional French procedure, where
    procedural steps of the Equilibrium_ Lohse method are used (see Fundamentals: Chpt. 6.17 ,
    page 397).

    18.6.8.1

    1966

    Selecting and executing TRIBUT - Equilibrium_Lohse

    PTVGROUP

    18.6.8.1 Selecting and executing TRIBUT - Equilibrium_Lohse


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.17.1 , page 397).
    Note: Especially, the toll has to be defined. For your model, you can use various toll
    types. However, each link is regarded for only one toll type.
    Toll type 'link toll': For links that are not located within a toll system, enter the link
    toll into the Toll-PrTSys link attribute (see "Links: PrT TSys tab" on page 1109).
    Toll type 'area toll' or 'matrix toll': Define one or several toll systems and allocate
    the desired links to the toll systems (see "Creating a toll system" on page 1417). If
    required, define the matrix toll for matrix toll systems (see "Specifying the matrix
    toll of a toll system" on page 1422). The link attribute Toll-PrTSys of links which
    have been allocated to a toll system will be ignored.
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    PrT settings > Blocking back model (see "Blocking back model settings and calculation" on page 1925)
    Note: For impedance calculation, the link attribute Toll-PrTSys should not be used,
    since it is automatically accounted for by the procedure in addition to impedance
    (tCur, length) (see "Definition and application of volume-delay functions" on page
    1892).
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    5. Confirm with OK.
    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    PTVGROUP

    1967

    18.6.8.1 Selecting and executing TRIBUT - Equilibrium_Lohse


    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To do so, hold down the C TRL key and click each entry. To select several consecutive
    entries hold down the SHIFT key while clicking the first and the last entry of the desired
    portion in the list.
    11. Confirm with OK.
    The selected demand segments are listed in the Reference object(s) column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the TRIBUT - Equilibrium_Lohse entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: TRIBUT - Equilibrium_Lohse window opens.
    15. Set the desired parameters (see "Parameters of the TRIBUT - Equilibrium_Lohse assignment" on page 1969).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    Note: For more details on the calculated TRIBUT - Equilibrium_Lohse results please
    refer to the log file. It contains - for each iteration - the number of network objects having
    a too great deviation when the procedure terminated. If the number by transport system
    goes below a certain value, the network objects are listed in detail. These network
    objects you may analyze for input data errors or other problems.
    You can define the number up to which non-converging network objects shall be listed
    individually (see "Limiting the number of non-converged network objects logged to the
    log file" on page 1892).

    1968

    PTVGROUP

    18.6.8.2 Parameters of the TRIBUT - Equilibrium_Lohse assignment


    18.6.8.2

    18.6.9

    Parameters of the TRIBUT - Equilibrium_Lohse assignment

    Element

    Description

    N = Maximum
    number of iterations

    This setting corresponds to the setting for Equilibrium_Lohse assignment (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944)

    Route volumes

    This setting corresponds to the setting for Equilibrium_Lohse assignment (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944)

    Estimated impedances

    This setting corresponds to the setting for Equilibrium_Lohse assignment (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944)

    Termination condition

    This setting corresponds to the setting for Equilibrium_Lohse assignment (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944)

    Parameters for
    Value of Time

    The settings correspond with those you made for TRIBUT - Equilibrium assignment procedure, in the table Matrix-specific distribution function of the Value of Time (see "Parameters of TRIBUT Equilibrium assignment" on page 1963).

    Dynamic User Equilibrium (DUE)


    The DUE procedure contains a blocking back model. Additionally, it can regard time-varying
    capacities as well as road tolls and it includes a departure time choice model (see

    PTVGROUP

    1969

    18.6.9.1 Selecting and executing the Dynamic User Equilibrium


    Fundamentals: Chpt. 6.18 , page 410).
    18.6.9.1

    Selecting and executing the Dynamic User Equilibrium


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.18.8 , page 433).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    Note: To the Dynamic User Equilibrium merely the following parameters are relevant.
    Settings directly under PrT settings (see "Distributing the demand to PrT connectors" on page 1888)
    Settings via PrT settings> Assignment> in section Save assignment results
    (see "Settings for saving PrT assignment results" on page 1890)
    4. Under Analysis time slots, make the desired settings (see "Adjusting the general procedure settings" on page 1860).
    Note: Alternatively, you may define time intervals in the assignment parameters instead (see "Dynamic User Equilibrium DUE:Assignment time interval tab" on page
    1974).
    5. Confirm with OK.
    The window closes.
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    1970

    PTVGROUP

    18.6.9.2 Parameters of Dynamic User Equilibrium (DUE)


    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the Dynamic User Equilibrium DUE entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters: Dynamic User Equilibrium (DUE) window opens.
    15. Set the desired parameters (see "Parameters of Dynamic User Equilibrium (DUE)" on
    page 1971).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    18.6.9.2

    Parameters of Dynamic User Equilibrium (DUE)


    Dynamic User Equilibrium DUE:Basis tab

    PTVGROUP

    1971

    18.6.9.2 Parameters of Dynamic User Equilibrium (DUE)

    1972

    Element

    Description

    Min. capacity factor for gridlock


    conditions

    The dynamic assignment can lead to a gridlock, if several highly congested links form a closed cycle in the network. The simplest case is
    a roundabout which has been broken down into multiple nodes. A
    gridlock can reflect oversaturation in reality, but sometimes it is an
    artifact which just occurs as a transient condition during the iterations. To get past these artificial gridlocks it is possible to specify
    that a (small) fraction of the link capacity is always available, even in
    highly congested conditions.
    Note
    Gridlock is highly affected by merging priorities, especially in correspondence of roundabouts where, as in reality, priority should be
    given to the flows already on the roundabout. Within DUE however,
    merging priorities in presence of spillback on the downstream arc are
    determined on the basis of turn capacities (see Fundamentals: Chpt.
    6.16 , page 385). Then, it is possible to set turn capacities as to properly simulate turn priorities, as in the example below, where links
    have the duty of simulating road capacities (they act as capacity constraints with respect to flows), while turns with very high (infinite) capacity simulate approaches with the right of priority. Dummy links may
    be used also for the same purpose.

    Shortest path
    search

    Maximum anticipated costs


    Maximum generalized costs for any connection in the network.
    Note
    In the current state of implementation DUE uses a shortest path
    search which benefits from an estimate of maximum cost. Generalized cost is expressed in monetary terms, and the default value of
    time (10 currency units / h) and the default max. cost of 100 correspond to a maximum travel time of 10 h for any OD pair. Change
    values, if this is exceeded in the current network.
    Discretization of the costs
    Smallest difference of generalized costs, that is considered as being
    different from zero.
    Note
    The smaller the discretization of the cost, the slower the simulation.

    PTVGROUP

    18.6.9.2 Parameters of Dynamic User Equilibrium (DUE)


    Element

    Description

    Termination condition

    Maximum computation time


    The procedure terminates after the specified computation time.
    Maximum number of iterations
    The procedure terminates after the specified number of external iterations.
    Maximum relative deviation
    The procedure terminates when the relative deviation of the impedance has reached the convergence criterion (see Fundamentals:
    Chpt. 6.9 , page 329).

    Spill-back

    Calculate blocking back


    If this option has been checked, horizontal queuing in the model is
    regarded. If a horizontal queue exceeds the length of the link, it will
    spill back to upstream links.
    Notes
    Spill-back is an equilibrium sub problem of its own and is solved by a
    nested inner iteration.
    Horizontal queues result in more realistic congestion effects. However, more computation time is required.
    The link attribute Space per PCU is critical for horizontal queue propagation. If queues propagate backward too fast with respect to
    observed or expected data, you should decrease Space per PCU.
    If this option has not been checked, vertical queuing is modeled.
    Vertical queues still record where links are oversaturated, but do not
    propagate to other links.
    Notes
    If vertical queues are adopted (that is blocking back calculation is not
    active), the link attributes SpacePerPCU and DUEvWave are not
    required.
    We recommend - in a new network - to calculate the procedure
    without spill-back first. This will ease the identification of problems or
    faulty input data such as incorrect link or turn capacities.
    Maximum number of iterations
    Maximum number of iteration steps for blocking back calculation.
    Maximum relative deviation
    The spill-back calculation terminates if - for all links - the relative
    deviation of the exit capacities between the current and the recent
    spill-back iteration goes below the given value.

    PTVGROUP

    1973

    18.6.9.2 Parameters of Dynamic User Equilibrium (DUE)


    Dynamic User Equilibrium DUE:Assignment time interval tab
    In this tab, you define the assignment time interval and sub-divide it into smaller time slices for
    calculation. The time slices can be of different size, for example it is possible to use longer
    time slices during night time and shorter ones during peak hours. For that purpose, sub-divide
    the assignment time interval into several larger time periods and then define the duration of
    the time slices - which means the number of time slices - by period.
    Note: The calculation time is roughly linear with the total number of time intervals defined.

    1974

    Element

    Description

    From

    Start of the assignment time interval


    Note
    The assignment time interval may exceed 24 hours; thus, an appropriate
    extension can also be defined for a 24h assignment.

    To

    End of the assignment time interval


    Note
    This value is not subject to changes. Visum calculates it on the basis of
    the time intervals defined in the table.

    To time

    End of the defined time slices

    Number of
    time intervals

    Number of time intervals in the given time slice.


    Note
    From the ToTime and the Number of time intervals, Visum calculates
    the Length of a time interval.

    PTVGROUP

    18.6.9.2 Parameters of Dynamic User Equilibrium (DUE)


    Element

    Description

    Extension
    interval

    If this option has been selected, the weights of an existing time series are
    set to 0 for the demand arising in this time slot. Use this option if the assignment period ends before the end of the time series and you do not
    want to adjust the time series.

    Create

    Via this button, you add a new row.

    Delete

    Via this button, you remove the currently selected row.

    Use time interIf this option has been checked, the time intervals defined here are
    also used as analysis time intervals.
    vals as analysis time
    Note
    intervals
    Analysis time intervals which have been defined in the general procedure settings will be ignored.
    If this option has not been checked, the time intervals defined here will
    not be used as analysis time intervals. Instead, the analysis time intervals
    defined in the general procedure settings are used to calculate the
    results (e.g. volumes) (see "Defining analysis time intervals" on page
    1861).
    Note
    If you do not want to use the time intervals defined here as analysis time
    intervals, you should make sure, that the various intervals match. For
    example, multiple time intervals can be summed up to form longer analysis time intervals.
    Dynamic User Equilibrium DUE:Choice tab

    PTVGROUP

    1975

    18.6.10 Dynamic stochastic assignment


    Element

    Description

    Number of deterministic iterations


    before Probit iterations

    Number of the first N iterations that use all-or-nothing assignment to


    the least-cost path per OD pair, until for each OD pair the best path
    has been found. This is followed by the Probit iterations, i.e. network
    volumes will be perturbed to generate alternative paths for the choice
    set.
    Note
    To disable Probit, in the Termination condition section, set the value
    to the Maximum number of iterations (see "Dynamic User Equilibrium DUE:Basis tab" on page 1971).

    Multiplier for road toll

    Multiplier for travel time, i.e. value of time

    Multiplier for an early departure, i.e. for the difference between desired departure time and actual departure time (if the actual departure
    time is before the desired departure time)

    Multiplier for a late departure, i.e. for the difference between actual
    departure time and desired departure time (if the actual departure
    time is after the desired departure time)

    Max. DeltaT(early) Maximum delay of the departure to a time which is before the desired
    time of departure.
    Note
    Enter 0 to deactivate the choice of the departure time.
    Max. DeltaT(late)

    Maximum delay of the departure to a time which is later than the desired time of departure.
    Note
    Enter 0 to deactivate the choice of the departure time.

    Variance

    For Probit iterations the variances of the standard normal distribution


    from which the perturbed network impedances are drawn.

    18.6.10 Dynamic stochastic assignment


    The Dynamic stochastic assignment differs from all the previously named procedures as a
    result of the explicit modeling of the time axis. The assignment period is divided into individual
    time slices. Volume and impedance are determined separately per time slice (see Fundamentals: Chpt. 6.19 , page 439).
    18.6.10.1 Selecting and executing the Dynamic stochastic assignment
    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).

    1976

    PTVGROUP

    18.6.10.1 Selecting and executing the Dynamic stochastic assignment


    1. Make sure the input attributes required by this procedure have been set (see Fundamentals: Chpt. 6.19.2 , page 441).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Adjust the settings via PrT settings.
    PrT settings (see "Setting parameters for PrT assignments" on page 1888)
    PrT settings> Impedance and PrT settings> Volume-delay functions (see "Definition and application of volume-delay functions" on page 1892)
    PrT settings > Node impedances (see "Calculating node impedances" on page
    1911)
    4. Make the desired changes under Analysis time slots and Volumes (see "Adjusting the
    general procedure settings" on page 1860).
    5. Confirm with OK.
    The window closes
    6. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    7. Add the procedure PrT assignment from the Assignments category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    8. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segment window opens.
    9. In the Select mode selection list, click the All PrT Modes entry.
    10. In the Demand segments section, select the desired entry.
    Tip: Alternatively, you can select multiple demand segments.
    To select several individual entries hold down the C TRL key while clicking each single
    entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    11. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    12. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    13. In the selection list, select the Dynamic stochastic assignment entry.
    The selected entry is displayed in the column.
    14. Select the operation added. Then in the Operations section, click the Edit button.
    PTVGROUP

    1977

    18.6.10.2 Parameters of Dynamic stochastic assignment


    The Parameters: Dynamic stochastic assignment window opens.
    15. Set the desired parameters (see "Parameters of Dynamic stochastic assignment" on page
    1978).
    16. Confirm with OK.
    17. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    Note: For more details on the calculated results please refer to the log file. It contains - for
    each iteration - the number of network objects having a too great deviation when the procedure terminated. If the number by transport system goes below a certain value, the network objects are listed in detail. These network objects you may analyze for input data
    errors or other problems.
    You can define the number up to which non-converging network objects shall be listed
    individually (see "Limiting the number of non-converged network objects logged to the
    log file" on page 1892).
    18.6.10.2 Parameters of Dynamic stochastic assignment
    Dynamic stochastic assignment:Basis tab

    1978

    PTVGROUP

    18.6.10.2 Parameters of Dynamic stochastic assignment


    Element

    Description

    From

    Start of the assignment time interval


    Note
    If a calendar is used, you need to select a weekday or a date (see
    "Specifying a calendar and valid days" on page 1511).

    To

    End of the assignment time interval


    Note
    If a calendar is used, you need to select a weekday or a date (see
    "Specifying a calendar and valid days" on page 1511).

    Interval length

    Length of time sub-intervals of the assignment interval in [minutes]


    (see Fundamentals: Chpt. 6.19 , page 439)

    Termination conditions

    The termination conditions comply with those of stochastic assignment, but refer to connections instead of routes (see "Stochastic
    assignment:Basis tab" on page 1953)

    Ignore turns

    If this option is checked, t0 of the turn is used for impedance without


    applying a volume-delay function. Volumes are not calculated.
    Note
    This option may save memory and computing time, but it also reduces the precision of the calculated results because delay times on
    turns do not depend on the vol/cap ratio.

    Dynamic stochastic assignment:Smoothing tab

    PTVGROUP

    1979

    18.6.10.2 Parameters of Dynamic stochastic assignment


    Element

    Description

    Route loading

    This setting corresponds to the setting for Equilibrium_Lohse assignment (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944)

    Estimated impedances

    This setting corresponds to the setting for Equilibrium_Lohse assignment (see "Parameters of the Equilibrium_Lohse assignment" on
    page 1944)

    Impedances of
    connections

    The impedance of a connection sums up from three components. For


    each of the three components, you may enter a factor.
    * estimated impedances of network objects
    Factor, by which the sum of the impedances of all network objects traversed by a connection is multiplied
    * DeltaT (early)
    Factor, by which the delay of the departure to an earlier time is multiplied
    * DeltaT (late)
    Factor, by which the delay of the departure to a later time is multiplied
    Max. permitted
    Maximum delay of the departure time compared to the desired time
    of departure earlier (DeltaT (early)) and later (DeltaT (late)).
    Note
    The default value of the maximum permitted delay = 0. In this case,
    Time-of-Day Choice is disabled. We recommend a value between 0
    and 30 minutes.

    Dynamic stochastic assignment:Search tab


    In this tab, you define how to determine PrT routes.

    1980

    PTVGROUP

    18.6.10.2 Parameters of Dynamic stochastic assignment

    Element

    Description

    Randomized
    search

    These parameters correspond to the parameters of stochastic assignment (see "Stochastic assignment:Search tab" on page 1955)

    Detour test

    These parameters correspond to the parameters of stochastic assignment (see "Stochastic assignment:Search tab" on page 1955)

    Points in time for


    path search

    Click this button to define the times you want to use for route search
    (see Fundamentals: Chpt. 6.19 , page 439).
    Note
    If none of the specified points in time is within the current assignment
    time interval, Visum will use the current start time from (see "Dynamic stochastic assignment:Basis tab" on page 1978)

    PTVGROUP

    1981

    18.7 Evaluating the goodness of the PrT assignment


    Element

    Description

    Day

    Weekday or date
    Note
    The entries depend on the calendar selected (see "Specifying a
    calendar and valid days" on page 1511).

    Time

    Points in time for path search

    Create

    Via this button, you add a new row.

    Delete

    Via this button, you remove the currently selected row.

    Note: After closing the window and calling it again, the entries will automatically be sorted in chronological order.
    Dynamic stochastic assignment:Preselection tab
    In this tab, you define how to select the routes found (see "Stochastic assignment:Preselection
    tab" on page 1958).
    Dynamic stochastic assignment:Choice tab
    In this tab, you specify how to distribute the demand to the connections found (see "Stochastic
    assignment:Choice tab" on page 1959).

    18.7

    Evaluating the goodness of the PrT assignment


    During and after an assignment, you can view information on the procedure's current state of
    convergence.
    After the calculation you can compare the assigned volumes to count data and correct them
    accordingly.

    18.7.1

    Viewing convergence criteria and convergence speed


    To assess the convergence speed, Visum traces the convergence criteria for each iteration in
    all static assignment methods (see Fundamentals: Chpt. 6.9 , page 329).
    This data indicating the assignment quality you may already display in tabular form while the
    calculation is still running.
    1. Open the Goodness of PrT assignment list (see "Opening a list" on page 2299).
    Note: For the Assignment with ICA, the Goodness of PrT assignment with ICA list is
    provided.
    The Goodness of PrT assignment list opens.
    2. Perform one of the aforementioned PrT assignment calculations (see "Setting and calculating the parameters for PrT assignment" on page 1931).
    During the calculation process, for each iteration the convergence criteria are listed.

    1982

    PTVGROUP

    18.7.2 NCHRP 255 (Post-processor for PrT assignments)

    18.7.2

    NCHRP 255 (Post-processor for PrT assignments)


    Note: This functionality is only available if the NCHRP 255 add-on is active (see "Enabling or disabling installed add-ons" on page 886).
    This add-on uses a correction factor to correct turn volumes of links and turns in a forecast scenario (see Fundamentals: Chpt. 6.20 , page 445). The correction factor results from the differences between traffic counts and an assignment which describe the same time slice. This
    calculation is performed according to Report 255 (National Cooperative Highway Research
    Program).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the NCHRP 255 procedure of the Miscellaneous category to the given procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    3. Select the operation added. Then in the Operations section, click the Edit button.
    The NCHRP 255 Post Processor window opens.
    4. Make the desired changes.
    Element

    Description

    Active nodes
    only

    If this option has been checked, flows passing passive nodes will not
    be adjusted

    Adjustment
    procedure

    Method for volume correction


    Difference
    Adjusted link volume = Future link assigned volume + (Link base
    count Base link assigned volume)
    Average
    Link Adjusted Volume = Future Link Assigned Volume (Difference +
    Ratio)/2
    Ratio
    Link Adjusted Volume = Future Link Assigned Volume (Link Base
    Count / Base Link Assigned Volume)
    Combination
    Due to the ratio between the counted turn volume and the assigned
    base volume, one of the methods mentioned above is used for calculation. Therefore, define - via Boundaries - the lower limit (01) and
    the upper limit (14).
    For values < lower limit, the Ratio method is used
    For values > lower limit and < upper limit, the Average method is
    used
    For values > upper limit, the Difference method is used

    PTVGROUP

    1983

    18.8 Calculating:PrT skims


    Element

    Description

    Boundaries

    If method Combination has been selected for adjustment, you need to


    define the limits for the three methods.

    Input data

    Counted turn volume


    Via this button, select the numerical turn attribute that stores the counted turn data.
    Base Assigned Volume
    Via this button, select the numerical link attribute that stores basic assignment volume data.
    Future Assigned Volume
    Via this button, select the numerical link attribute that stores future assignment volume data.

    Output data

    Log file
    If this option has been checked, detailed information on the procedure
    run are logged to trace file.
    Adjusted link volume
    Link attribute, to which the corrected link volume is to be saved.
    Adjusted turn volume
    Turn attribute, to which the corrected turn volume is to be saved.

    5. Confirm with OK.


    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The procedure is executed.

    18.8

    Calculating:PrT skims
    For skim data calculation, you need to predefine certain settings. Then you can start skim
    matrix calculation as a separate operation in the procedure sequence (see Fundamentals:
    Chpt. 6.6 , page 311).

    18.8.1

    Setting parameters for PrT skim matrices


    Additionally to the settings described here, you need to specify basic settings for PrT skim
    matrices (see "Setting metadata for skim matrices" on page 1865).

    1984

    PTVGROUP

    18.8.1.1 Defining units for PrT skims

    Note: In the skim table, further settings can be adjusted (see "Setting metadata for
    skim matrices" on page 1865).
    18.8.1.1

    Defining units for PrT skims


    For skim matrix output regarding private transport you may select a unit for length data and a
    unit for time data.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Skims.
    The table of skims appears.
    3. In the Units for skim matrices section, select the desired options.

    PTVGROUP

    1985

    18.8.1.2 User-defined PrT skims


    Element

    Description

    Lengths

    Unit for storing all skims of the Length data type, it is also used for skims of
    the Speed data type.
    Select either Kilometers/Miles (long length) or Meters/Feet (short length).
    Note
    Whether metric or imperial units are provided depends on the current settings made under Network> Network parameters> Units tab (see
    "Undoing and redoing actions" on page 870).

    Time

    Unit for storing all skims of the Time/Duration data type, it is also used for
    skims of the Speed data type.
    Select either Minutes or Seconds.

    Note: Visum does not store the data type of the selected unit but just saves whether a
    short length (Meters or Feet) or a long length unit (Kilometers or Miles) has been set.
    When you load data, the unit set under Network> Network settings> Units tab is
    used. The values are re-calculated, if applicable.
    4. Confirm with OK.
    The changes are applied.
    18.8.1.2

    User-defined PrT skims


    You can determine a user-defined PrT skim which concatenates the attributes of traversed network objects. By means of the user-defined skim, you can count the traversed POIs (gas stations, for example) or 'count locations' by OD pair. You may also link a unique attribute
    (AddValue1, for example) of various traversed network objects. For this, the direct and indirect
    numerical attributes of links, connectors, turns and main turns are provided for selection. Attributes of nodes and main nodes can be included in the skim calculation as follows:
    As ViaNodes of turns (without FromNodes or ToNodes)
    As FromNodes of links (without ToNodes)
    As ToNodes of links (without FromNodes)
    As ViaNodes of turns plus connector nodes (all nodes included)
    As connector nodes
    Real values can be calculated. You may also use user-defined numerical attributes.
    Setting parameters for the user-defined PrT skim
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PrT settings> Skims.
    The table of skims appears.
    3. In the Settings for specific skims section, click the Parameters button.

    1986

    PTVGROUP

    18.8.1.2 User-defined PrT skims


    The window User-defined skim PrT opens.

    4. Click the button of the desired network object type.


    The Parameters 'Edit attribute' window opens.

    5. Make the desired changes.


    Element

    Description

    Network object
    type

    Selected network object type, whose selected attribute data is


    regarded for the calculation of the user-defined skim.

    Target attribute

    User-defined skim

    Coefficient

    Factor, the source attribute is multiplied by.


    Note
    To make the coefficient on the right available, select an operational sign.

    Attribute

    Source attribute, whose value enters the formula.


    Use the button to select an attribute (and a subattribute, if available). Direct and indirect attributes of the source network object
    type are provided. The selection is done in a separate window

    PTVGROUP

    1987

    18.8.2 Calculating PrT skim matrices


    Element

    Description
    (see "The window used for the selection of one attribute" on page
    963).
    Notes
    The source attribute on the right is only available, if you have
    selected an operational sign.
    If you do not select a source attribute, the value 1.0 is used instead.

    Op.

    Operational sign of a mathematical operation, that includes two


    terms (e.g. AddVal2 + AddVal3).
    Use the drop-down list to select an operational sign.

    Create

    Via this button, you add a new line to the formula.

    Delete

    Via this button, you remove the bottom row.

    6. Confirm with OK.


    The window Parameters: Edit attribute closes, the settings for the selected network object
    type are stored.
    7. If applicable, click the button for any other network object type in the window User-defined
    skim PrT to take the particular attribute data into consideration for the user-defined skim calculation, and repeat step 6) and step 7).
    The settings for further network object types are stored.
    8. Confirm with OK in the window User-defined skim PrT.
    The parameters for the calculation of the user-defined skim have been set.
    Note: Take the given units for impedances into consideration for the choice of the coefficients: Length in Meters and Time in Seconds.

    18.8.2

    Calculating PrT skim matrices


    1. Make sure your settings for the individual skim matrices are correct (see "Setting metadata
    for skim matrices" on page 1865).
    2. Make sure your settings for the PrT skim matrices are correct (see "Setting parameters for
    PrT skim matrices" on page 1984).
    3. On the toolbar, click the

    button Open 'Procedure sequence' window.

    The Procedure sequence window opens.


    4. Add the operation Calculate PrT skim matrix from the Matrices category to the procedure
    sequence (see "Setting up and starting the procedure sequence" on page 1847).
    5. In the row of the added procedure, click on the button in the Reference object(s) column.
    The Select demand segments window opens.
    1988

    PTVGROUP

    18.8.3 Setting parameters for the calculation of PrT skim matrices


    6. Select the desired entry.
    7. Confirm with OK.
    In the Reference object(s) column, the selected demand segment is listed.
    8. Select the operation added. Then in theOperations section, click the Edit button.
    The Parameters PrT skim matrices window opens.
    9. Make the desired settings (see "Setting parameters for the calculation of PrT skim matrices"
    on page 1989).
    10. Confirm with OK.
    11. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The skim matrices are calculated.
    Note: You can then open and edit the skim matrices (see "Editing matrix values" on page
    1761).

    18.8.3

    Setting parameters for the calculation of PrT skim matrices

    PTVGROUP

    1989

    18.8.3 Setting parameters for the calculation of PrT skim matrices


    Analyzed OD pairs
    Element

    Description

    Calculate only OD If this option has been checked, only OD pairs with demand > 0 are
    pairs with demand regarded.
    >0
    Note
    For OD pairs with demand = 0, skim value 0 is used.
    Filter selection list

    With this selection list, the analyzed OD pairs that comply with the current setting of option Calculate only OD pairs with demand >0 can
    be reduced further.
    Note
    For OD pairs that are not evaluated according to the current option
    settings, the skim matrix contains the value set for Ignored OD pairs
    under Calculate menu > General procedure settings> PrT
    settings> Skims (see "Setting metadata for skim matrices" on page
    1865).
    All
    If this option has been selected, all OD pairs are regarded.
    Only active OD pairs
    If this option has been checked, only active OD pairs are regarded.
    Only active origin zones
    If this option has been checked, only OD pairs with an active origin
    zone are regarded.
    Only pairs of active zones
    If this option has been checked, only OD pairs connecting active
    zones are regarded.
    Notes
    The setting of the analyzed OD pairs specified for the calculation of
    skim matrices can differ from the setting for the assignment.
    If a restricting zone interval has been set for assignment, this will
    reduce the number of analyzed OD pairs even more.
    When reading parameters from an elder Visum version file the original selection for this option will be interpreted as either All or Only
    pairs of active zones.

    1990

    PTVGROUP

    18.8.3 Setting parameters for the calculation of PrT skim matrices


    Path choice, Sum up paths from
    Element

    Description

    Path search cri- Criterion for selection of one or several paths per OD pair from which the
    terion
    relation's skim value is gained.
    t0
    Path with shortest travel time in unloaded network
    tCur
    Path with shortest travel time in loaded network
    Impedance
    Depends on the current selection for option Use paths from assignment.
    If this option has not been checked, the path with the lowest impedance for the private transport system according to the current impedance function is used
    If this option has been checked, the aggregate value resulting from
    all paths is used
    Distance
    Path with shortest length
    AddValue1, AddValue2, AddValue3
    Path with minimum AddValue
    Use paths from f this option has been checked, the skim value is gained from all paths
    assignment
    per OD pair according to the current option Weighting of paths setting.
    If this option has not been checked, the path with the lowest impedance
    for the private transport system according to the current impedance function is used
    Note
    This option is only provided, if Impedance has been selected as path
    search criterion.

    PTVGROUP

    1991

    18.8.3 Setting parameters for the calculation of PrT skim matrices

    1992

    Element

    Description

    Weighting of
    paths

    Method for skim value determination from the skims of all paths resulting
    from assignment
    Minimum per skim
    Value of the path with the smallest value
    Maximum per skim
    Value of the path with the highest value
    Mean over paths
    Mean value calculated from all paths
    Mean over path volume
    Mean value calculated from all paths and weighted by the particular path
    volumes
    Notes
    This option is only provided, if the option Use paths from assignment
    has been selected.
    The path with the lowest impedance is determined for OD pairs for which
    no paths were calculated during assignment.

    Sum up paths
    from

    The skim value results from the data of the network objects of selected
    network object types over the selected paths.
    Links
    Turns (main turns included)
    Origin connectors
    Destination connectors

    PTVGROUP

    18.8.3 Setting parameters for the calculation of PrT skim matrices


    List of PrT skims
    Element

    Description

    List of skims

    Calculate
    If this option has been checked, the particular skim is calculated.
    Save to file
    If this option has been checked, the particular skim is saved as skim
    matrix file. For further output settings, please refer to the Output file section (see "Output file of a PrT skim matrix" on page 1993). For each skim
    that is to be saved to file, Visum creates a file with a skim-specific file
    extension which has been derived from the English abbreviation.
    Notes
    Skim matrix files created with previous Visum versions have file extensions that differ by language. These may even have been replaced by
    user-defined file extensions.
    This option is grayed out as long as option Calculate is not selected.
    Open
    If this option has been checked, the particular skim matrix is opened in
    the matrix editor on screen right after the calculation.
    Note
    This option is grayed out as long as option Calculate is not selected.
    Tip
    Each of the columns mentioned above can be checked or unchecked
    completely as follows: In the column header, right click to call the context
    menu and click either Activate column or Deactivate column.
    Skim
    List of available skims (see Fundamentals: Chpt. 6.6 , page 311)

    Output file of a PrT skim matrix


    Note: This section is only provided if you would like to save at least one skim matrix to
    file.

    PTVGROUP

    1993

    18.8.3 Setting parameters for the calculation of PrT skim matrices


    Element

    Description

    File name
    button, you can enter or
    Name of the output skim matrix files. Via the
    select the file name (and path, if applicable) for the skim matrix file(s) without
    file extension(s).
    Notes
    If the file name is entered without path, then the file is stored in the pre-set
    project directory for matrices.
    Visum adds the file extension according to the Format selected and the settings made under Calculate> General procedure settings> PrT settings>
    Skims (see "Setting metadata for skim matrices" on page 1865).
    Format

    Via the selection list, you can choose the format in which you want to save
    the matrices (see "Data structures of matrices in Visum-specific text formats"
    on page 2679).
    Binary

    Format V (Text format)


    Format O (Text format)
    Format E (Text format)
    Format S (Text format)
    CSV format (Text format)
    Separator

    Via the selection list you can select the separator to be used for saving the
    matrices in text format.
    Notes
    This selection list is only provided for output in CSV format.
    For all other formats, spaces are used as separators, so that the matrix can
    be edited in the matrix editor.
    Double-click to open a comma-separated matrix in *.csv format as an Excel
    sheet. Matrices in *.csv format, with a different decimal separator, need to be
    opened with the Excel Assistant.

    Means of
    transport
    No.
    (VISEM)

    Number of the means of transport (for VISEM)


    1 = walk link
    2 = car passenger
    3 = PuT
    4 = car driver (including HGV) etc.

    Confirm
    If this option has been checked, a warning is displayed if matrices with
    overwriting identical names already exist. You may either confirm this message or cancel the data file output.
    If this option has not been checked, existing matrix files with identical
    names are overwritten without a warning.

    1994

    PTVGROUP

    19 Settings for the PuT user model

    19

    Settings for the PuT user model


    The user model PuT models the travel behavior of public transport passengers. Based on
    demand data and the network model, you can calculate volume data by assignment or passenger-related skims such as journey time or transfer frequency.
    By means of the Passenger onboard survey add-on, you may perform the plausibilization of
    the survey sample data read from file and assign the data to the network.
    Subjects
    Setting parameters for PuT assignments
    Setting and calculating PuT assignment parameters
    Importing, checking and assigning passenger onboard surveys
    Calculating PuT skims
    Calculate service trip patterns

    19.1

    Setting parameters for PuT assignments


    You must make some basic settings for the calculation of public transport assignments.

    19.1.1

    Settings for calculating and saving results


    Set basic parameters for public transport assignment calculations and storage of results.

    19.1.1.1

    Round demand and volume data


    You may specify that demand data and volumes have to be rounded.
    Notes: This setting is regarded by any procedure using demand data and has to be set
    prior to reading the demand matrix from file.
    This setting neither affects skim matrix calculations nor zone lists or overall statistics. For
    these output values, the exact non-rounded demand and path volumes are always used.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PuT settings> Assignment.
    3. In the Precision of computation section, make the desired settings.

    PTVGROUP

    1995

    19.1.1.2 Settings for saving PuT assignment results


    Element

    Description

    Round
    demand and
    volume data

    If this option has been checked, the demand values will be rounded to the specified Number of decimal places. The volumes of all
    paths will be of the same precision.
    If this option has not been checked, the original values are used for
    the calculation.
    Notes
    Due to the precise calculation more paths are stored, i.e. the memory
    requirements for the assignment result rise with the calculation accuracy. In case of large networks, we recommend to make use of the
    rounding option. If reasonable in terms of memory requirements, the
    exact real-valued volume should always be used in order to obtain
    the most precise calculation results.
    In the case of demand matrices with sparsely filled OD pair data it is
    recommended to activate the rounding option since the program
    might discard more paths than desired if the rounding is too coarse.
    When reading older version files or PuT connection files, the option is
    always checked.

    Number of
    decimal places

    Number of decimal places for rounding (between 0 and 6). This option
    is only provided if option Round demand and volume data has been
    checked.

    4. Confirm with OK.


    The changes are applied. The next PuT assignment will use the new settings.
    19.1.1.2

    Settings for saving PuT assignment results


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PuT settings> Assignment.
    3. Make the desired changes in the Save assignment results section.

    1996

    PTVGROUP

    19.1.1.2 Settings for saving PuT assignment results


    Element

    Description

    Save paths Do not save


    The assignment result stores only the resulting volumes of network
    objects, the calculated paths are not stored. This option saves memory.
    As routes
    Calculated paths are stored as routes, i.e. only the spatial component is
    stored.
    As connections
    Calculated paths are stored as connections, i.e. both the temporal and
    the spatial component are stored.
    Note
    The larger the network the more computation time is required if paths are
    to be stored as connections. We recommend to only use this option, if the
    path list is required for subsequent analyses or PuT flow bundle calculation (see Fundamentals: Chpt. 7.3 , page 453).
    Save volumes

    Only for time profiles


    Network volumes are saved by line, by line route and by time profile.
    Additionally for vehicle journeys
    Additionally, the network volume is saved separately by vehicle journey.
    Note
    The memory required also increases when storing volumes at the vehicle
    journey level. We recommend to use this option only if you would like to
    analyze the volumes by vehicle journey.

    Store trans- Note


    fers
    This option applies only to the timetable-based assignment.
    Between time profiles
    As before, transfers are stored for pairs of time profiles. Both time profile
    numbers (FromTP and ToTP) are returned.
    Between vehicle journeys
    Transfers are saved for pairs of vehicle journeys. Both vehicle journey
    numbers (FromVehJourney and ToVehJourney) are returned.
    Save PJT

    PTVGROUP

    Note
    This option applies only to the headway-based and the timetable-based
    assignment.
    Do not save
    The calculated perceived journey time is not saved with the assignment.
    Save
    The perceived journey time is saved with the assignment and issued in
    the PuT path list, column PJT.

    1997

    19.1.1.2 Settings for saving PuT assignment results


    Element

    Description
    Note
    If several demand segments are calculated simultaneously in an assignment, Visum only saves the PJT of the demand segment which is used
    for the skim matrix as well.

    Save impor- Do not save


    ted fare
    Fares read in from a connection file are not saved with the assignment.
    data
    They still take effect within the scope of the impedance calculation.
    On path level
    The fare per connection is saved beyond the assignment (PuT path attribute Fare).
    On path leg level
    The connection fare prorated for each path leg of the connection is saved
    beyond the assignment (PuT path leg attribute Fare)
    Notes
    During assignment, the fare per path or path leg is calculated by default
    by the Visum internal fare model. Optionally, they may be replaced by
    user-defined fares. These may be permanently stores and used for later
    line costing calculations.
    Fares are not stored per demand segment but only once per assignment.
    If several demand segments are calculated simultaneously in an assignment, Visum calculates the fares for the demand segment which is
    used for the skim matrix as well. This predefinition is necessary since different DSegs may refer to different ticket types and thus different fares,
    too. Saving fares without regard to demand segment reduces memory
    requirements for storage capacity and also for connection files *.con.
    In line costing calculations, the distribution of revenues of paths for which
    imported fares have been saved is not calculated with the fare model. Instead, it is extracted directly from the entered values.
    Regardless of this setting, you may calculate and export path-based or
    path leg-based fares during connection export (see "Timetable-based
    assignment:Connection export tab" on page 2047).

    1998

    PTVGROUP

    19.1.1.3 Limiting the path leg time


    Element

    Description

    Save the
    volume
    matrix between stop
    points on
    the path
    level

    If this option is selected, Visum generates a stop point matrix on path


    level during timetable-based or headway-based assignment (Lists
    menu> Volume matrix between stop points> On path level) (see "Opening a list" on page 2299)). For each pair of stop points (A, B), it stores
    the summed up volume of all paths that start from stop point A and end at
    stop point B.

    Save the
    volume
    matrix between stop
    points on
    the path leg
    level

    If this option is selected, Visum generates a stop point matrix on path leg
    level during timetable-based or headway-based assignment (Lists
    menu> Volume matrix between stop points> On path leg level) (see
    "Opening a list" on page 2299)). For each pair of stop points (A, B), it stores the summed up volume of all paths legs that start from stop point A
    and end at stop point B.

    The changes are applied. The results of the next PuT assignment will be calculated and stored
    according to your settings.
    19.1.1.3

    Limiting the path leg time


    The duration of PuT-Aux path legs and PuT-Walk path legs you may reduce to a maximum
    value. This is mandatory if large parts of the network are open to such transport systems and if,
    without a limitation, the number of possible path legs is so high that the memory capacity is
    insufficient. Moreover, such a limitation can reduce the run time of the procedure.
    Reasons concerning the content can frequently lead to such a limitation, too: Walking or going
    by taxi may be possible anywhere in the network, however, no passenger accepts walk transfers of more than 15 minutes between two lines or uses a taxi in town for more than two hours.
    The following applies to the limitation of PuT Aux or walk times
    It affects the precalculation of path legs already.
    It reduces the number of utilized path legs to those with a walk time or PuT-Aux time that
    does not exceed the preset value.
    It is relevant to timetable-based AND headway-based assignments.
    In the case of the walk time it only applies to walk times that arise from links open to walkTSys and transitions between stop areas of a stop, not to connector times.
    It is to be interpreted per path leg, thus per transition between two PuT sections of a
    connection. If, for example, 30min is entered for walk time it can arise twice for a PuT
    connection with a walk transition time of 20min, thus 40min in total. However, a single
    transition cannot take longer than 30min.

    PTVGROUP

    1999

    19.1.1.4 Restricting the walk link search


    Notes: Please note, that using such time limitations can also lead to unintended effects.
    Example: For an OD pair, the ideal connection is a direct 3h trip by Taxi (PuT-Aux). Since
    the maximum duration is limited to 2 h, this path is not permitted. Within the three hours of
    transfer, the passenger might have the option to do a "loop", either walking or using a
    PuT-TSys. The passenger thus gets out of the taxi after e.g. one hour and a half, takes a
    walk in the park, and then takes another taxi to continue his journey. Even though such a
    loop would not make any sense, it would lead to the fact that condition "PuT-Aux path leg
    may not take more than two hours" would be complied with by interrupting the total
    path somewhere in the middle of it.
    Users can avoid such constellations for one thing by limiting the time in such a way that it
    encompasses all desired path legs which are thus shorter than the time specified for the
    limit, and for another thing, by making sure that the whole network is not open to all TSys
    but that TSys subnetworks are modeled in detail.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PuT settings> Assignment.
    3. In the PuT-Aux path legs section, make the desired settings.
    Element

    Description

    Maximum PuT-Aux
    time

    Maximum time permitted for a PuT-Aux path leg in [minutes]

    4. In the Walk links section, make the desired settings.


    Element

    Description

    Maximum walk time

    Maximum time permitted for a walk in [minutes]

    Note: In problematic networks, a value of approximately 30min is recommended as


    walk time however, because connections with longer walk link transitions are not realistic.
    The changes are applied. The next PuT assignment will use the new settings.
    19.1.1.4

    Restricting the walk link search


    When predetermining PuT Walk path legs for the headway-based or the timetable-based assignment, the shortest path search can be restricted to specific PuT Walk path legs. You may
    edit the settings for the transitions between stop areas and for the PuT Walk path legs between
    zones.
    Note: By default a transfer consists of a PuT Walk path leg between two stop areas.
    Sometimes, a transfer event may include several path legs, e.g. PuT Walk PuT Aux
    (escalator) PuT Walk. Therefore the term transition is used in Visum for the transfers in
    general.

    2000

    PTVGROUP

    19.1.1.4 Restricting the walk link search


    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PuT settings> Assignment.
    3. In the Walk links section, select the desired entry in the Walk links within a stop selection
    list.
    Element

    Description

    Search without Shortest path search accounts for all PuT Walk path legs of a netrestrictions
    work. Based on the stop matrix, Visum automatically determines all
    possible (even indirect) transitions and the most favorable transition
    for each pair of stop areas. In the process, it uses the combined time
    of an indirect transition instead of the direct transition, if it is less than
    the direct time. For stop areas which are connected to the same
    access node, the transition time is 0 since each stop area without a
    time penalty is connected to its access node.
    Example
    According to the stop matrix, the transition from stop area A to stop
    area C takes 5 minutes. The transition from stop area A to stop area B
    takes 1 minute and the transition from stop area B to stop area C
    takes 2 minutes. In this case, Visum identifies a transition of 3 minutes for changing from stop area A to stop area C.
    Note
    The use of this option might lead to a multitude of possible (direct or
    indirect) paths in case of a large number of stop areas, which may
    cause an extensive shortest path search.
    Do not permit
    search via
    access node

    The shortest path search is restricted to PuT Walk path legs of the
    stop matrix. The transition times are taken into account like for the
    Search without restrictions; the access node, however, is ignored, so
    that the transition time from the matrix is used for transitions between
    stop areas which have the same access node (direct or indirect).
    This does not cause changes to PuT Walk path legs between other
    network objects.

    No search, use The PuT Walk path legs are generated exactly according to the entethe matrix as
    red transition times. Visum does not determine indirect transitions.
    specified
    Any transitions for which no transition times have been entered are
    prohibited.
    This setting possibly also has an effect on PuT Walk path legs between other network objects.
    If, for example, two nodes are connected by a PuT Walk path leg,
    which contains a stop transition including a change between
    stop areas, the given transition time is also used for this change.

    PTVGROUP

    2001

    19.1.1.4 Restricting the walk link search


    Element

    Description
    The existence of blocked transitions within the stop matrix might
    lead to the blocking of further paths.
    Example
    According to the stop matrix, the transition from stop area A to stop
    area C takes 5 minutes. The transition from stop area A to stop area B
    takes 1 minute and the transition from stop area B to stop area C
    takes 2 minutes. Nevertheless, Visum would use 5 minutes for the
    transition from stop area A to stop area C. This makes sense, if, for
    example, streets have to be crossed for the indirect transition or if the
    'intermediate' stop area is not used, since it is located underground.
    Notes
    This option we recommend to experienced users only, since the user
    has to ensure that the matrix contains meaningful and matching entries.
    If the direct transition time between two stop areas is much higher
    than the combined time, which would be needed for indirect transitions, Visum might find useless connections.

    4. In the Walk links section, select the desired entry in the Walk links from/to connectors
    selection list.
    Element

    Description

    Permit all walk


    links

    Path search between two zones may detect pure walk paths. Thus,
    also paths using a PuT Walk TSys for origin connector and destination connector and any further path leg are permitted.

    Walk links between zones not


    permitted

    Paths between two zones, which exist of just two connectors or of


    two connectors and a PuT Walk path leg, are ignored during the
    shortest path search. Only paths which use at least one PuT line
    are permitted.

    Force boarding/alighting at
    connected node

    An origin connector may only be followed by a PuT Walk path leg


    leading to a connected node or to a stop area which is connected
    with this node (and not beyond it). A destination connector may just
    be reached by a directly connected node or by a stop area which is
    connected with this node.

    Notes: If either option Walk links between zones not permitted or option Force boarding/alighting at connected node is selected, no connections without PuT will be
    found between the zones. In this case, the corresponding setting for the timetablebased assignment is irrelevant (see "Timetable-based assignment:Preselection tab"
    on page 2030).
    The options Walk links between zones not permitted and Force boarding/alighting
    at connected node are recommended to experienced users only.
    2002

    PTVGROUP

    19.1.2 Saving volumes by demand segment or additively


    The changes are applied. The next PuT assignment will use the new settings.

    19.1.2

    Saving volumes by demand segment or additively


    If multiple PuT demand segments are assigned simultaneously, by default the results are
    saved separately for each demand segment. Alternatively, you may save the results additively.
    For this purpose, you need to define prior to assignment, to which demand segment the results
    are to be saved in each case. For example, you can save the results of the demand segments
    A, B and C additively to demand segment A, whereas the result for demand segment D is
    saved to D further on.
    Notes: In case of large networks you may save memory capacity by storing results additively.
    The results cannot be differentiated subsequently by the individual demand segments.
    This functionality is provided for PuT demand segments only.
    Tip: You may also calculate the assignment in a way, that finally the results are stored by
    demand segment and as total value as well. For that purpose, create another (dummy)
    demand segment. Define, that the results of the assigned demand segments are to be
    stored additively with the new demand segment and start the assignment for all demand
    segments. The volume total is now stored with the new demand segment. Then reset the
    settings to the default: Each result is to be stored with the respective demand segment.
    Calculate another assignment, but do not include the new demand segment this time.
    Now, the volumes are stored by demand segment whereas the volume total has not changed.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select the Volumes tab.
    3. In the particular row, select the desired entry from the drop-down list provided in the Save
    for demand segment column.
    Note: If assignment results already exist you will delete the results of those demand
    segments whose results you would like to save to a different demand segment by this
    adjustment.
    4. Confirm with OK.
    The changes are applied. When an assignment is calculated, the results are stored by the
    selected demand segment.
    Note: To save assignment results additively, you need to assign also the demand segments to which the results are to be saved additively.
    Tip: Via the Initialize button you may reset the settings to default.

    PTVGROUP

    2003

    19.1.3 Coordination groups for headway-based assignment

    19.1.3

    Coordination groups for headway-based assignment


    Using coordination groups, you can model headway-based assignment, with specific line routes running at equal time intervals, for the benefit of the passengers (see Fundamentals: Chpt.
    7.9.8 , page 495).
    You define the line routes being part of coordination groups and the particular line route sections From Stop - To Stop. For the assignment you then select the Search option Due to coordination groups (see "Headway-based assignment:Search tab" on page 2014).

    19.1.3.1

    Creating a coordination group


    1. From the Network menu, choose PuT Coordination groups.
    The PuT coordination groups window opens.
    2. Click the

    Create button.

    The Create PuT coordination group window opens.


    3. Enter the desired Number.
    4. Enter the desired Name.
    5. Next to From stop, click the Edit button.
    The Find stop window opens. It displays the list of all stops.
    Tip: Via the selection list you may chose the stop attribute for list display.
    6. Click the desired stop.
    7. Click the Close button.
    The window closes. The button label now shows the selected stop.
    8. Next to To stop, click the Edit button.
    The Find stop window opens.
    9. Click the desired stop.
    10. Click the Close button.
    The window closes. The button label now shows the number and name of the selected
    stop. In the Not allocated list, the time profiles are listed which exist between the selected
    stops.
    11. Click the desired time profile.
    12. Click the

    icon.

    The time profile is allocated to the coordination group and shifted to the Allocated list.
    13. Add further time profiles.
    14. Confirm with OK.

    2004

    PTVGROUP

    19.1.3.2 Editing a coordination group


    The Create PuT coordination group window closes. The coordination group is displayed
    in the list.
    15. Confirm with OK.
    The coordination group is created.
    19.1.3.2

    Editing a coordination group


    1. From the Network menu, choose PuT Coordination groups.
    The PuT coordination groups window opens.
    2. In the list, click the coordination group of your choice.
    3. Click the

    Edit button.

    The Edit PuT coordination group window opens.


    4. Edit the stops via the buttons, if applicable.
    5. In the not allocated section, click a desired time profile.
    6. Click the

    icon.

    The time profile is allocated to the coordination group and shifted to the Allocated list.
    7. In the Allocated list, click a desired time profile.
    8. Click the

    icon.

    The time profile is removed from the coordination group and shifted to the Not allocated
    list.
    9. Confirm with OK.
    The Edit PuT coordination group window closes.
    10. Confirm with OK.
    The changes are applied.
    19.1.3.3

    Deleting a coordination group


    1. From the Network menu, choose PuT Coordination groups.
    The PuT coordination groups window opens.
    2. In the list, click the coordination group of your choice.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the

    Delete button.

    4. Confirm with OK.

    PTVGROUP

    2005

    19.2 Setting and calculating PuT assignment parameters


    The coordination group is deleted.

    19.2

    Setting and calculating PuT assignment parameters


    For modeling PuT trips, Visum provides three types of PuT assignment procedures which differ
    in the required input data, in the accuracy of results, and computing time (see Fundamentals:
    Chpt. 7.1 , page 449).
    The procedure selection process is the same for all three procedures (see "Selecting and executing a PuT assignment procedure" on page 2006).
    For the selected procedure, specific parameters have to be set.
    Transport system-based assignment (see Fundamentals: Chpt. 7.8 , page 471)
    Headway-based assignment (see Fundamentals: Chpt. 7.9 , page 473)
    Timetable-based assignment (see Fundamentals: Chpt. 7.10 , page 498)

    19.2.1

    Selecting and executing a PuT assignment procedure


    Note: If your network contains assignment results, you may delete them either directly or
    within the procedure sequence, e.g. as the procedure which is directly followed by the
    new assignment calculation (see "Deleting PrT/PuT assignment results" on page 1879).
    1. Make sure the input attributes required for this procedure are available (see Fundamentals:
    Chpt. 19 , page 1995).
    2. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    3. Under PuT settings> Assignment, make the settings of your choice (see "Setting parameters for PuT assignments" on page 1995).
    4. If required, edit the settings under PuT settings> Skims (see "Setting metadata for skim
    matrices" on page 1865 and "Setting parameters for PuT skim matrices" on page 2074).
    Note: These settings are only regarded for simultaneous skim matrix calculation.
    5. Under Analysis time intervals, make the settings of your choice (see "Adjusting the general procedure settings" on page 1860).
    6. Under Volumes, make the settings of your choice (see "Saving volumes by demand segment or additively" on page 2003).
    7. Confirm with OK.
    8. From the Calculate menu, choose Procedure sequence.
    The Procedure sequence window opens.
    9. Add the PuT assignment procedure of the Assignments category to the position of your
    choice within the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).

    2006

    PTVGROUP

    19.2.2 Parameters of the TSys-based assignment


    10. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select Demand segments window opens.
    11. In the Select mode selection list, click the desired entry.
    12. In the Demand segments section, select the desired entries.
    Tips: To select several individual entries hold down the C TRL key while clicking each
    single entry.
    To select several consecutive entries hold down the SHIFT key while clicking the first
    and the last entry of the desired portion in the list.
    13. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    14. In the column Variant/file in the selection list, select the desired entry.
    The selected entry is displayed in the column.
    15. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters for assignment procedure:... window opens.
    16. Make the desired changes.
    Note: The three procedures have different parameters.
    TSys-based assignment (see "Parameters of the TSys-based assignment" on
    page 2007)
    Headway-based assignment (see "Parameters of headway-based assignment"
    on page 2010)
    Timetable-based assignment (see "Parameters of timetable-based assignment"
    on page 2021)
    17. Confirm with OK.
    18. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The assignment procedure is executed.
    Note: You can show the results in a table or diagram, or use them for further evaluations
    (see "Displaying data graphically and in lists" on page 2299 and "Settings for interactive
    analyses" on page 2265).

    19.2.2

    Parameters of the TSys-based assignment


    You make the settings for TSys-based assignment in several tabs.

    19.2.2.1

    Transport system-based assignment:Basis tab

    PTVGROUP

    2007

    19.2.2.2 Transport system-based assignment:Search tab


    Element

    Description

    Origin zones

    Via these two entries you may restrict the calculation to the demand of origin zones with selected numbers. Thus only the selected rows of the
    demand matrix will be assigned.
    Note
    If both entry fields are empty, Visum will assign the entire demand matrix.
    If only a single zone number is entered, Visum will use this value as the
    upper or lower limit respectively (half-open interval).

    Calculate assiIf this option has been checked, new PuT routes are determined and
    loaded on the basis of transport systems.
    gnment
    If this option has not been checked, the assignment is not performed.
    Note
    You may, for example, just calculate skim matrices.
    Calculate skim If this option is selected, the skim matrices selected in the Skim matrices
    matrices
    tab are calculated (see "Calculating PuT skims" on page 2073).
    19.2.2.2

    2008

    Transport system-based assignment:Search tab

    PTVGROUP

    19.2.2.2 Transport system-based assignment:Search tab


    Element

    Description

    Transfers

    Max. number
    Maximum permitted number of transfers for a route from origin zone
    to destination zone.
    Penalty per transfer
    Each transfer event increases the impedance of the route by this
    fixed time penalty.
    Permissibility at node
    Via this selection list you decide how to gain the 'transfers permitted
    at node' information.
    From node type table
    The information is coded in the list in the lower section of the window.
    From allocated stop points
    At a node, transfers are permitted between PuT systems that are allowed at the stop points allocated to the node (see "Stop points: Transport systems tab" on page 1271).

    Consider prohibited turns

    If this option has been checked, existing prohibited turns in the network are regarded (and excluded from the path search).

    Network for path


    search

    Via this selection list you decide which of the links, turns and main
    turns in the network are to be used for route search by transport system.
    All links
    All links, turns and main turns permitted for the transport system are
    regarded.
    Links used by line routes
    Only the network objects that are traversed by line routes are regarded.
    Links used by active line routes
    Only network objects that are traversed by active line routes are
    regarded.

    List

    By node type this list defines, whether transfers between transport


    systems are permitted and also the time penalty for a transfer between transport systems.
    Edit
    Click this button to edit the properties of the node type(s) selected in
    the list (see "Editing transfer data by node type" on page 2010).
    Note
    Left click in the row to select a node type. To select several individual
    entries hold down the C TRL key while clicking each single entry. To
    select several consecutive entries hold down the SHIFT key while
    clicking the first and the last entry of the desired portion in the list.

    PTVGROUP

    2009

    19.2.2.3 Transport system-based assignment: Skim matrices tab


    Editing transfer data by node type
    Changes refer to the selected node type(s).

    Element

    Description

    Transfers permitted

    Via this drop-down list you decide whether transfers are permitted.

    Transfer time pen- Time to be added for a transfer event, in [minutes].


    alty
    19.2.2.3

    Transport system-based assignment: Skim matrices tab


    You only have to set parameters for skim matrix calculation, if you want to calculate an assignment and skim matrices simultaneously (see "Settings for PuT skim matrix calculation" on
    page 2078).
    Note: To have skim matrices calculated, in the Basis tab, select Calculate skim matrices.

    19.2.3

    Parameters of headway-based assignment


    You make the settings for headway-based assignment in several tabs.

    2010

    PTVGROUP

    19.2.3.1 Headway-based assignment:Basis tab


    19.2.3.1

    Headway-based assignment:Basis tab

    Element

    Description

    Calculate assignment

    If this option has been checked, the assignment is performed.


    If this option has not been checked, the assignment is not performed.
    Note
    You may, for example, just calculate skim matrices.

    Calculate SF for If this option has been checked, the service frequency is calculated by
    PuT OD pair list OD pair. The service frequency by OD pair can be displayed in the Service frequency column of the Paths> OD pairs PuT list.
    Calculate skim
    matrices

    If this option is selected, the skim matrices selected in the Skim matrices tab are calculated (see "Calculating PuT skims" on page 2073).

    Use connector
    shares

    If this option is selected, the assignment is calculated with a proportional distribution of the transport demand across the connectors
    (see Fundamentals: Chpt. 7.6 , page 469).
    Notes
    If you want zones to be accounted for with proportional distribution
    during the assignment, set the SharePuT attribute to 1(yes). For the origin and/or destination connectors of these zones, you need to specify
    shares (see "Connectors: Basis tab" on page 1162).

    PTVGROUP

    2011

    19.2.3.1 Headway-based assignment:Basis tab


    Element

    Description
    If this option has been checked, certain path attributes in lists are no
    longer defined clearly, e.g. access time.

    2012

    Destination
    zones

    Via these two entries you may restrict the calculation to the demand for
    the destination zones with the selected numbers. Thus only the selected columns of the demand matrix will be assigned.
    Notes
    If both entry fields are empty, Visum will assign the entire demand
    matrix.
    If only a single zone number is entered, Visum will use this value as the
    upper or lower limit respectively (half-open interval).
    These limiting entries apply to the assignment and skim matrix calculation. In addition, the restrictions selected via the Analyzed OD
    pairs apply.

    Analyzed OD
    pairs

    In the list box, you can specify the data you want to use for the assignment procedure: All, Only active OD pairs, Only active destination
    zones, Only pairs of active zones.
    Note
    The setting specified for the OD pairs analyzed might differ from the setting for skim matrix calculation.
    If a restricting zone interval has been set for assignment, this will
    reduce the number of analyzed OD pairs even more.

    Assignment
    time interval

    Only those portions of the timetable and travel demand are considered
    for assignment which lie within the assignment time interval.
    Note
    If a calendar is used, you need to select a weekday or a date (see
    "Selecting a calendar " on page 1511).

    Headway calculation

    The headway-based procedure calculates the headway by line or


    gains the headway from a time profile attribute. Using this headway
    data, a path search including choice is performed. Additionally, you
    may subdivide the analysis time interval into time slices, with different
    parameter settings per time slice (see Fundamentals: Chpt. 7.9.2 ,
    page 475).

    PTVGROUP

    19.2.3.1 Headway-based assignment:Basis tab


    Element

    Description

    Calculation
    mode

    Per time interval from the mean wait time according to timetable
    The headway results from the time expected until the next departure of
    the succeeding line according to its timetable.
    Per time interval from the mean headway according to timetable
    The headway results from the temporal length of a time slot divided by
    the number of vehicle journeys in this slot.
    Constant from time profile attribute
    If the timetable information is not essential due to dense headways or if
    there is no timetable data available, the headway per time interval can
    be read from any attribute.

    List of time intervals

    The defined time intervals are displayed in tabular form. Number and
    labels of columns depend on the selected Calculation mode and whether a calendar is used.
    Date or Weekday
    Via the selection list you select the day when the time interval starts.
    Note
    This column is only shown if you use a calendar (see "Selecting a
    calendar " on page 1511).
    Time
    Start time of the time interval
    Double-click in the selected cell to edit the value.
    Headway input attribute
    Click the button to open an attribute selection window (see "The window used for the selection of one attribute" on page 963). Select - by
    time interval - the time profile attribute for headway calculation.
    Notes
    This column is only provided, if - for Calculation mode - the option Constant from time profile attribute has been selected.
    Here, only numerical attributes are provided.
    We recommend to use a user-defined attribute.
    Headway output attribute
    Click the button to open an attribute selection window (see "The window used for the selection of one attribute" on page 963). Define - by
    time interval - to which time profile attribute the calculated cycles are to
    be saved.
    Notes
    This column is only provided, if one of the Per time interval from... options has been selected for Calculation mode.
    Here, only editable numerical attributes are provided.

    PTVGROUP

    2013

    19.2.3.2 Headway-based assignment:Search tab


    Element

    Description
    We recommend to use a user-defined attribute.

    19.2.3.2

    2014

    Create

    Via this button, you add a new time interval.


    Notes
    The new interval is automatically added after the currently selected
    interval. For the new interval, the start time limit is automatically set to
    the middle between the two neighboring intervals.
    Via double-click in the selected cell you may edit the time.
    The time intervals are automatically adjusted to the current settings in
    the Assignment time interval section.
    By default, the first time interval starts at 0.00 a.m. If the start of the
    assignment time interval is edited, this moment in time is adjusted
    automatically.
    User-defined time intervals that lie completely outside of the current assignment time interval are highlighted in red.

    Delete

    Via this button, you remove the selected time interval.

    Headway-based assignment:Search tab


    In this tab you configure the parameters for the PuT path search.

    PTVGROUP

    19.2.3.2 Headway-based assignment:Search tab


    PuT Supply

    Element

    Description

    Regard only
    active time profiles

    If this option has been checked, only active time profiles are regarded
    for path search.

    Coordination

    Due to coordination groups


    Coordination groups for time profiles on shared sections are taken into
    account for the calculation of transfer wait time and start wait time for
    these time profiles (see "Coordination" on page 495).
    Note
    You need to create the coordination groups in advance (see "Coordination groups for headway-based assignment" on page 2004).
    Coordination everywhere
    At each stop, all time profiles that depart from this stop (boarding permitted) and that serve the same next stop (alighting permitted) are
    regarded as being coordinated.
    Uncheck coordination
    Neither new coordinations are generated nor existing coordination
    groups are regarded.

    Interchanges

    Use interchanges
    The transfer wait time calculation will take pre-defined transfer wait
    times between transport systems or time profiles at stops into account
    for those time profiles (see Fundamentals: Chpt. 7.9.8.2 , page 496).
    Note
    The transfer wait times need to be specified in advance (see "Stops:
    Wait times tab" on page 1241).
    Ignore interchanges
    The transfer time between two lines at a stop results from the transfer
    walk time listed in the transfer walk time matrix (see "Stops: Walk times
    / stop areas tab" on page 1240) and the random wait time for a vehicle
    journey of the successor line.

    Assume coorIf this option has been checked, the time profiles in the coordinated
    dinated time pro- time profile bundle are not distinguishable. Headway and impedance
    are irrelevant. Instead, the headway is calculated based on the service
    files to be
    undisfrequency (see Fundamentals: Chpt. 7.9.8.4 , page 497).
    tinguishable
    If this option has not been checked, the passengers are able to distinguish between individual time profiles in a coordinated bundle. In
    this case, their choice depends on the attributes of the respective time
    profile.

    PTVGROUP

    2015

    19.2.3.2 Headway-based assignment:Search tab


    Choice model

    Element

    Description

    Passenger
    information

    Additional information a passenger has available, besides headways


    and PuT line times (see Fundamentals: Chpt. 7.9.4 , page 480)
    None (Optimal Strategies)
    The passenger has no further information. The headways are distributed
    exponentially.
    None (constant headways)
    The passenger has no further information. The headways are constant.
    Elapsed wait time
    The passenger uses information on the elapsed wait time. The headways are constant.
    Departures from stop area
    At the stop, the passenger has detailed information on the departure
    times of the PuT lines, e.g. from dynamic passenger information systems. The headways are constant.
    Note
    If this option has been checked, two more options concerning Stop area
    info... are provided.
    Complete information
    Already in the origin zone, the passenger knows the departure times in
    detail. The headways are constant.

    Discrete
    choice model
    (Logit) among
    distinct boarding stop areas

    If this option has been checked, a discrete choice model is used to


    model the stop choice behavior of passengers prior to boarding or transfer events. If this option is checked, into the field, enter the Logit parameter Beta (see "Modeling the choice on the basis of estimates" on page
    487).
    If this option has not been checked, all passengers chose the best
    alternative according to expectancy.
    Note
    This option is grayed-out, if option Complete information has been
    selected for Passenger information.

    2016

    PTVGROUP

    19.2.3.2 Headway-based assignment:Search tab


    Choice model

    Element

    Description

    Discrete
    choice model
    (Logit) between
    stay on board
    and alight

    If this option has been checked, a discrete choice model is used to


    model the behavior of passengers when deciding whether to stay on
    board or to alight. If this option is checked, into the field, enter the Logit
    parameter Beta (see "Modeling the choice on the basis of estimates" on
    page 487).
    If this option has not been checked, all passengers chose the best
    alternative according to expectancy.
    Note
    This option is grayed-out, if option Complete information has been
    selected for Passenger information.

    Stop area info


    includes departures from different stop
    areas

    If this option is checked, information on lines serving stops nearby is


    also provided at the stop (see "Extended applicability of the departure
    time model" on page 486).
    Note
    This option is only relevant, if option Departures from stop area has
    been selected for Passenger information.

    Stop area info


    is already
    available in the
    vehicle

    If this option is checked, information on departure times from the next


    stop is provided in the vehicle for passengers who intend to alight at the
    next stop (see "Extended applicability of the departure time model" on
    page 486).
    Note
    This option is only relevant, if option Departures from stop area has
    been selected for Passenger information.

    Search

    Element

    Description

    Ignore path, if
    Paths are ignored if two conditions are satisfied.
    share <
    During the choice, the path's share in demand would be smaller
    and <=
    - by the entered factor between 0 and 1 - than the maximum
    share.
    * maximum share
    During the choice, the path's share in demand would go below a
    certain absolute value.
    The first condition guarantees that the run time of the procedure does
    not increase due to the evaluation of paths that are very unlikely to
    have a minimum impedance.
    The second condition avoids the deletion of all paths of an OD pair.
    Delete dominated If this option has been checked, all dominated paths are deleted prior
    routes
    to the route choice and will not be loaded. A path is dominated by

    PTVGROUP

    2017

    19.2.3.3 Headway-based assignment:Demand segments tab


    Search

    Element

    Description
    another path, if the following applies.
    Both paths are located on the same OD pair.
    Both paths use the same sequence of time profiles (in the same
    order).
    Both paths contain the same start stop and end stop.
    The dominated path has a longer total journey time, e.g. for less
    convenient transfer stops.

    Approximate shares calculation

    Element

    Description

    Number of simulations per step

    The number of simulations per step regulates the accuracy of the


    approximate share calculation. The more simulations calculated, the
    more accurate the result.
    Note
    An approximate calculation is inevitable whenever there are too
    many suitable options at a decision point (e.g. a boarding stop) so
    that an accurate calculation is no longer arithmetically reliable. This
    is the case from 50 options on. The polynomial to be integrated then
    has level 50 and very high coefficients as a rule.

    19.2.3.3

    Headway-based assignment:Demand segments tab


    Note: This tab is only visible if several PuT demand segments have been selected.

    2018

    Element

    Description

    Same impedance
    parameters for
    each demand segment

    If this option has been checked, the same search parameters are
    used for all demand segments during path search.
    Note
    Option not yet provided.

    Demand segments for skim


    matrices

    Use this button to open the selection list and select the demand segments, whose demand dscriptions shall be used for the skim matrix
    calculation.
    If multiple demand segments have been selected, the settings for the
    selected skims refer to each of the selected demand segments comparably. For example, this includes preset meta data as well as data
    file format or weighting settings.
    Notes
    For all these demand segments, the unitary impedance parameters

    PTVGROUP

    19.2.3.4 Headway-based assignment:Impedance tab


    Element

    Description
    are used.
    The particular DSeg allocation of an output matrix is retained in the
    storage and in the file name. To the user-defined file name, the DSeg
    code is added in all cases.

    19.2.3.4

    Headway-based assignment:Impedance tab


    In this tab you configure the parameters for the distribution of the demand to the found paths.
    Decide whether the calculation shall be based on perceived journey time and fare points or on
    perceived journey time and fare (see Fundamentals: Chpt. 7.9.3 , page 476).

    PTVGROUP

    2019

    19.2.3.4 Headway-based assignment:Impedance tab


    Element

    Description

    Impedance

    The impedance of a path results from the total calculated either from perceived journey time (PCJ) and number of fare points or from perceived journey time and fare. You may enter a weighting factor for each of the
    addends.
    Below you define how the PJT is to be calculated. The number of fare
    points is calculated based on the input data of the corresponding network
    objects (see "Inserting fare points at network objects" on page 2168). The
    fare is based on the PuT fares defined (see "Defining PuT fares" on page
    2171).
    Note
    If the impedance calculation accounts for the fare, Visum will automatically
    select the option Each path leg separately for the fare system's 'Fare applies to' option (see "Defining fare systems" on page 2172).

    Perceived
    The perceived journey time is the sum of different times and supplements
    journey time (see Fundamentals: Chpt. 7.9.3 , page 476).
    PJT
    PJT =
    Factor In-vehicle time (in)direct numerical time profile item attribute
    + Factor PuT-Aux ride time
    + Factor Access time
    + Factor Egress time
    + Factor Walk time
    + Factor Origin wait time, where the OWT is calculated according to a formula
    + Factor Transfer wait time (in)direct numerical stop area attribute
    + Factor Number of transfers
    + Boarding penalty PuT (numerical time profile item attribute)
    + Boarding penalty PuT-Aux (numerical transport system attribute)
    + Mean delay (numerical time profile item attribute)
    Notes
    You may specify a weighting factor for each of the time components
    (see Fundamentals: Chpt. 7.9.3 , page 476).
    Using the factors (for in-vehicle time and transfer wait time) that you
    can select via buttons, you chose the numerical attribute (see "The window used for the selection of one attribute" on page 963). Each button
    label indicates the selected attribute. By default, no attribute is selected
    but the value 1.0 appears for factors and the value 0.0 appears for
    addends. As an additional factor for the In-vehicle time you may use
    the AddValue, for example, to consider line-specific features (e.g. preference to tram over bus).
    The origin wait time is calculated according to a formula which can be

    2020

    PTVGROUP

    19.2.3.5 Headway-based assignment: Skim matrices tab


    Element

    Description
    defined via the button. The formula can include attributes of the stop
    area and attributes of the time profile.
    The boarding penalty PuT is a time profile attribute and will be added
    to the perceived journey time for the boarding and for each transfer.
    The boarding penalty is used to model that certain lines are preferred
    to other lines in general.
    The Boarding penalty PuT-Aux is a transport system attribute. It only
    has an effect on transport systems of the type PuTAux.
    The mean delay will be added to the impedance for the boarding and
    for each transfer event. The mean delay is used to model the fact that
    certain lines (actually: time profiles) are often behind schedule at specific stops and that those lines are used less often by passengers than
    the theoretical data (run time, headway) would suggest.

    19.2.3.5

    Headway-based assignment: Skim matrices tab


    You only have to set parameters for skim matrix calculation, if you want to calculate an assignment and skim matrices simultaneously (see "Settings for PuT skim matrix calculation" on
    page 2078).
    Note: To have skim matrices calculated, in the Basis tab, select Calculate skim matrices.

    19.2.4

    Parameters of timetable-based assignment


    You make the settings for timetable-based assignment in several tabs.

    PTVGROUP

    2021

    19.2.4.1 Timetable-based assignment:Basis tab


    19.2.4.1

    2022

    Timetable-based assignment:Basis tab

    Element

    Description

    Calculate assignment

    If this option has been checked, the assignment is performed.


    If this option has not been checked, the assignment is not performed.
    Note
    You may, for example, calculate only skim matrices or perform connection export.

    Calculate skim
    matrices

    Select this option to calculate the skim matrices selected in the Skim
    matrices tab (see "Timetable-based assignment:Skim matrices tab" on
    page 2046).

    Connection
    export

    Select this option to export the connections found (see Fundamentals:


    Chpt. 7.10.7 , page 513). You can make additional settings in the
    Connection export tab (see "Timetable-based assignment:Connection
    export tab" on page 2047).

    Use capacity
    restriction

    If the option is selected, the calculation will take capacity restrictions


    into account. You can make additional settings in the Capacity restriction tab (see "Timetable-based assignment:Capacity restriction tab" on
    page 2042).

    PTVGROUP

    19.2.4.1 Timetable-based assignment:Basis tab


    Element

    Description

    Use connector
    shares

    If this option is selected, the assignment is calculated with a proportional distribution of the transport demand across the connectors
    (see Fundamentals: Chpt. 7.6 , page 469).
    Notes
    If you want zones to be accounted for with proportional distribution
    during the assignment, set the SharePuT attribute to 1(yes). The shares of the connectors of these zones must be specified (see "Connectors: Basis tab" on page 1162).
    If this option has been checked, certain path attributes in lists are no
    longer defined clearly, e.g. access time.

    Save detailed
    log files

    If this option is checked, the assignment results will be saved to log


    files on the connection level.

    Origin zones

    Via these entries you may restrict the calculation to the demand of the
    selected origin zones. Thus only the selected rows of the demand
    matrix will be assigned.
    Notes
    If both entry fields are empty, Visum will assign the entire demand
    matrix.
    If only a single zone number is entered, Visum will use this value as the
    upper or lower limit respectively (half-open interval).
    These limiting entries apply to all iteration steps of the procedure: assignment, skim matrix calculation, and connection export, if required. In
    addition, the restrictions selected via the Analyzed OD pairs apply.

    Analyzed OD
    pairs

    PTVGROUP

    In the list box, you can specify the data you want to use for the assignment procedure: All, Only active OD pairs, Only active origin
    zones, Only pairs of active zones.
    Note
    The setting specified for the OD pairs analyzed might differ from the setting for skim matrix calculation.
    If a restricting zone interval has been set for assignment, this will
    reduce the number of analyzed OD pairs even more.

    2023

    19.2.4.1 Timetable-based assignment:Basis tab


    Element

    Description

    Assignment
    time interval

    From To
    Only those portions of the timetable and travel demand are considered
    for assignment which lie within the assignment time interval.
    Note
    If a calendar is used, you need to select a weekday or a date (see
    "Selecting a calendar " on page 1511).
    Extension
    Period after the assignment period within which connections must
    reach the travel destination.

    Calculate paths
    from

    Connection search
    If this option has been checked, Visum determines the connections.
    Stored connections for DSeg
    If this option has been checked, Visum does not perform connection
    search, but will use connections precalculated in a previous assignment instead.
    In the list, click the demand segments with the connections you want to
    read in (see Fundamentals: Chpt. 7.10.7 , page 513).
    Notes
    Irrespectively of the specified assignment time interval, the assignment
    will regard all connections read from file.
    When calculating a skim matrix, no skim values are calculated for OD
    pairs with no demand, i.e. with no paths.
    File
    If this option is selected, connections are read in from a file (see Funbutton, select the desidamentals: Chpt. 7.10.7 , page 513). Via the
    red file in *.con format.
    Notes
    Irrespectively of the specified assignment time interval, the assignment
    will regard all connections read from file.
    You can also save connections to several files (see "Timetable-based
    assignment:Connection export tab" on page 2047).
    Import fares
    If this option has been checked, fares stored by path or path leg are
    read from the file specified for File, if available. Visum calculates the
    impedances, skim values and choice on the basis of the fares read
    from the connection file.
    If this option has not been checked, Visum reads only the connections from the specified file. Impedance, skim values, and choice are
    calculated with the fare model (see "Revenue calculation using the fare

    2024

    PTVGROUP

    19.2.4.2 Timetable-based assignment:Search tab


    Element

    Description
    model" on page 2169).
    Notes
    This option is only provided if option File has been checked.
    In the connection file, fares are not stored per demand segment, i.e. for
    all demand segments the same fare per connection is read in from the
    file.
    If the connection file stores the fares on path leg level, the fare of the
    connection results from the total of the fares of the path legs. If the
    connection file stores the fares on path level, the fare of the connection
    is used without changes.
    Tip
    Fares are saved on path leg level or separately per path leg, if under
    Calculate > General procedure settings> PuT settings> Assignment, in the Save imported fare data list, you click On path leg
    level (see "Settings for saving PuT assignment results" on page 1996).

    Time-varying
    impedance calculation

    19.2.4.2

    Refine time series intervals


    If this option has been checked, you may set the maximum length for
    the time intervals, for which demand portions and adaptation times are
    determined.
    Maximum interval length
    Maximum length of intervals

    Timetable-based assignment:Search tab


    In this tab you configure the parameters for the PuT connection search.

    PTVGROUP

    2025

    19.2.4.2 Timetable-based assignment:Search tab

    Element

    Description

    Regard only
    If this option has been checked, only active vehicle journey sections
    active vehicle jour- are regarded for path search.
    ney sections

    2026

    Max. number of
    transfers

    Maximum permitted number of transfers for a connection from origin


    zone to destination zone.

    Branch & bound


    search

    If this option is selected, all suitable connections in the entire analysis time interval are determined, even multiple connections with different impedances starting at the same time (see "Branch & bound
    search" on page 2027).
    Note
    Branch & bound search is suitable for the analysis of a time period.

    Shortest path
    search

    If this option is selected, one connection per departure time is determined (see "Shortest path search" on page 2029).
    Note
    Shortest path search is suitable for the analysis of a particular
    moment in time.

    PTVGROUP

    19.2.4.2 Timetable-based assignment:Search tab


    Branch & bound search
    Element

    Description

    SearchImp

    The search uses an impedance value which is calculated from journey time (JT), number of transfers (NT), TSys-specific supplements
    (TSys-Imp; Fare) and vehicle journey-specific supplements (VehJImp; boarding penalty and discomfort term).
    Note
    If in the Basis tab the option Use capacity restriction is selected,
    then to the SearchImp a Vol/cap ratio-dependent impedance as for
    demand segment will be added additionally. In the selection list,
    select the demand segment.
    You may enter a weighting factor for each of the addends.
    Click the TSys-Imp button to specify how transport system specific
    supplements shall be calculated (see "Specifying TSys-specific impedances" on page 2028).
    Click VehJ-Imp to specify how vehicle journey specific supplements
    shall be calculated (see "Specifying vehicle journey-specific impedances" on page 2028). This vehicle journey impedance is determined for each PuT path leg and added to the search impedance.
    Note
    The search impedance defined here differs from the impedance used
    in the connection choice procedure.

    A connection is
    deleted, if:

    Connections which fulfill one of the following conditions during


    search tree construction are deleted. You may adjust the conditions
    with the help of factors and addends.
    SearchImp > Factor Min. search impedance + Addend
    Connections are deleted, if their search impedance is very high compared to the minimum search impedance of the OD pair.
    Journey time > Factor Min. journey time + Addend
    Connections are deleted, if their journey time is very high compared
    to the minimum journey time of the OD pair.
    Number of transfers > Min. number of transfers + Addend
    Connections are deleted, if their number of transfers is very high compared to the minimum number of transfers of the OD pair.

    Dominance

    Via the button, the Dominance of connections window opens.


    These are the required conditions for the dominance of a connection
    when two connections are compared. In this case, the dominated
    connection is deleted.
    You may adjust the formula for comparison of search impedances.
    Note
    With a factor > 1 and/or an addend > 0 you may achieve that connections with a higher search impedance are still regarded.

    PTVGROUP

    2027

    19.2.4.2 Timetable-based assignment:Search tab


    Specifying TSys-specific impedances
    In this window, you define - by transport system - the supplement to be added to the impedance.

    Element

    Description

    Imp/km

    The TSys-specific fare/km is multiplied by the total number of km


    covered in the TSys.

    Imp/FarePoint

    The TSys-specific fare/FP is multiplied by the total number of fare


    points on links traversed in the TSys.

    Imp/TSys-AddVal

    The TSys-specific value is multiplied by the total TSys-AddVal of the


    links traversed in the TSys.

    Const. supplem.

    The constant supplement is regarded once for the entire connection.

    Const. supplem.
    per path leg

    The constant supplement is regarded for each path leg covered in


    the transport system.

    Specifying vehicle journey-specific impedances


    In this window, you define - by vehicle journey - the supplement to be added to the impedance.

    2028

    PTVGROUP

    19.2.4.2 Timetable-based assignment:Search tab


    Element

    Description

    Boarding supplement

    Select a direct or indirect numerical vehicle journey attribute of the


    vehicle journey course which is to be used as boarding supplement.
    The boarding supplement is charged on each PuT path leg for the
    first vehicle journey item of this path leg.
    Note
    Attribute values < 0 are regarded as if = 0.

    Discomfort supplement

    Select a direct or indirect numerical vehicle journey attribute of the


    vehicle journey course which is to be used as boarding supplement.
    The discomfort supplement is charged for all items between the first
    vehicle journey item (included) of the path leg and the last vehicle
    journey item of the path leg (excluded) and will be aggregated according to the user's choice. The last item does not count, since in this
    context the link viewon the vehicle journey is applied, which means
    the transport from one stop to the next. Transport is not continued
    after passing the last item.
    Note
    Attribute values < 0 are regarded as if = 0.

    Aggregate function

    In the selection list, select the appropriate aggregate function:


    Sum
    Minimum
    Mean
    Maximum
    Weighted mean
    This function aggregates the values per vehicle journey item to determine the value by path leg.
    Note
    If the weighted mean is used for aggregation, another vehicle journey item attribute can be selected for weighting.

    Shortest path search


    Element

    Description

    Find connection
    If this option has been checked, the connection with the minimum
    with minimum
    impedance according to the current formula settings is determined
    search impedance for each start time. You may adjust the weighting factors for journey
    time and number of transfers in the formula.
    Bi-criterion
    method: For each
    feasible NT find a
    connection with
    minimal JT

    PTVGROUP

    If this option has been selected, the connection with the minimum
    journey time is calculated for each start time and any permitted number of transfers (all integers 0 and Max. number of transfers). If
    the calculation returns identical journey times for different numbers of
    transfers, the program only stores the connection with the lowest num-

    2029

    19.2.4.3 Timetable-based assignment:Preselection tab


    Element

    Description
    ber of transfers (dominance).

    19.2.4.3

    Times of departure for search

    For a zone, the connections are determined by a best path search


    performed for various start times. The start times result from the departures (max. 1/min, thus max. 1440/day) of the PuT lines from the
    connected stops.
    Use all available ones
    If this option has been checked, a best path search is run for each
    departure time.
    Limit the number
    If this option has been checked, you can set the maximum number of
    departure times. If there are more departure times than defined as
    upper limit, the specified number of departure times is chosen randomly from all available departure times.
    Notes
    In case of a 24 hour assignment time interval, the maximum number
    is 1440 = 60 minutes x 24 hours.
    Limiting the number reduces computation time, since not all of the
    connections have to be determined. The result will differ from the
    result of a full search, and the quality of the results depends on the
    transport supply side. The limitation takes less effect in case of regular, fixed-rhythm headway service compared to networks with few,
    irregular services.
    The correct calculation of the service frequency is only possible if all
    times of departure are considered.
    For limited search, option Correction (reverse) is recommended.

    Correction
    (reverse)

    If this option has been checked, a reverse search based on the arrival time at the destination stop in the destination zone is conducted
    to find a later departure either of the same line or of a different line for
    every part of the found connection. This reduces journey and transfer
    times. In this way, a better connection with identical stop points (origin, all transfer stop points, destination) for the calculated arrival time
    may be found which has a later departure time. Instead of the initially
    found connection, the connection detected by reverse correction will
    be used.

    Timetable-based assignment:Preselection tab


    In this tab, you set the parameters for the selection of found connections.
    Note: Some of the parameters in this tab are not provided, if option Shortest path search
    has been checked in the Search tab.

    2030

    PTVGROUP

    19.2.4.3 Timetable-based assignment:Preselection tab

    PTVGROUP

    2031

    19.2.4.3 Timetable-based assignment:Preselection tab

    2032

    Element

    Description

    For OD pairs for


    which connections
    using PuT (...) and
    also without PuT
    (...) were found

    Delete all connections using PuT lines


    All connections for an OD pair either found by the path search procedure or imported from connection file, that include at least one
    boarding of a PuTSys are deleted.
    Delete all connections without PuT
    All connections for an OD pair either found by the path search procedure or imported from connection file, that do not include PuTSys
    boardings (e.g. using only WalkLinks) are deleted.
    Note
    This option is not relevant, if under Calculate> General procedure
    settings> PuT settings> Assignment> Walk links from/to connectors, you have selected Walk links between zones not permitted or
    Force boarding/alighting at connected node. In this case, no
    connections without PuT are found (see "Restricting the walk link
    search" on page 2000).
    Do not delete any connection
    None of the connections for an OD pair either found by the path
    search procedure or read in during the connection import is deleted.

    Delete connections with departure time later


    than end of the
    assignment time
    interval

    If this option has been checked, all connections are deleted that
    depart past the end of the assignment time interval.
    Notes
    Those connections might be found - and loaded - because of the temporal extension in the timetable-based assignment. They may also
    be read from file.
    Those connections do not affect most of the skims as they are usually
    charged with fewer passengers and thus have less weight. However,
    when calculating the service frequency, each connection is counted.
    This option can be used to determine the precise number of connections that depart within the assignment period.

    PTVGROUP

    19.2.4.3 Timetable-based assignment:Preselection tab


    Element

    Description

    Numbered conditions

    For each OD pair, all connections - either found by the connection


    search or imported from a connection file - that were not deleted for
    other reasons yet, are evaluated prior to connection choice. The following criteria are verified. If applicable, connections are deleted.
    You may adjust the conditions with the help of factors and addends.
    Note
    The criteria are checked in exactly that order.
    1. SearchImp > Factor min. search impedance + Addend
    Connections are deleted, if their search impedances are very high
    compared to the minimum search impedance of the OD pair.
    Notes
    This option is only provided, if either - in the Search tab - option
    Branch & bound has been checked or after connection import.
    The impedance used here complies with the SearchImp defined in
    the Search tab.
    2. Journey time > Factor Min. journey time + Addend and number
    of transfers > minimum number of transfers
    or
    Number of transfers > Min. number of transfers + Addend and journey time > minimum journey time
    To all remaining connections applies:
    Connections are deleted if two conditions are satisfied: Compared to
    the minimum journey time per OD pair their journey times are extremely long and their numbers of transfers exceed the minimum number of transfers.
    Connections are also deleted if these two conditions are satisfied:
    Their numbers of transfers exceed the minimum number of transfers
    per OD pair by a certain number of transfers and their journey times
    exceed the minimum journey time.
    Perceived journey time PJT > Factor Mean PJT + Addend
    To all remaining connections applies:
    If this option has been checked connections are deleted if their perceived journey time exceeds the mean PJT by OD pair significantly.
    If this option is checked and multiple demand segments are assigned, then select the Demand segment for the calculation of the perceived journey time from the selection list.
    Notes
    The selection list is invisible as long as only a single demand segment is to ne assigned.
    The selection list is grayed out as long as the third condition has not
    been checked, if multiple demand segments are assigned.

    PTVGROUP

    2033

    19.2.4.4 Timetable-based assignment:Demand segments tab


    19.2.4.4

    Timetable-based assignment:Demand segments tab


    Note: This tab is only visible if several PuT demand segments have been selected.
    Element

    Description

    The same impeIf this option has been checked, the connection search uses the
    dance parameters same search parameters for all demand segments.
    for all demand segments
    The same choice If this option has been checked, the connection choice uses the
    parameters for all same choice parameters for all demand segments.
    demand segments
    The same vol/cap If this option has been checked, the connection choice uses the
    ratio-dependent
    same vol/cap ratio-dependent impedance parameters for all demand
    parameters for all segments.
    demand segments
    Demand segments for skim
    matrices

    19.2.4.5

    2034

    Via the button a window is opened. In the selection list, select the
    demand segments, whose choice parameters are to be used for the
    skim calculation. If multiple demand segments have been selected,
    the settings for the selected skims refer to each of the selected
    demand segments comparably. For example, this includes preset
    meta data as well as data file format or weighting settings.
    Note
    The particular DSeg allocation of an output matrix is retained in the
    storage and in the file name. To the user-defined file name, the DSeg
    code is added in all cases.

    Timetable-based assignment:Impedance tab


    In this tab, you set the parameters for the distribution of the demand to the found connections.
    The demand for an OD pair is distributed across connections based on the perceived journey
    time, the fare, and the time difference between desired departure time and actual departure
    time (see Fundamentals: Chpt. 7.10.5 , page 505).

    PTVGROUP

    19.2.4.5 Timetable-based assignment:Impedance tab

    PTVGROUP

    2035

    19.2.4.5 Timetable-based assignment:Impedance tab


    Element

    Description

    Perceived
    journey time
    PJT =

    The table represents the formula for the calculation of the perceived journey time by connection. The perceived journey time sums up from several
    addends which are listed in rows. Each addend is multiplied by a constant
    coefficient. Additionally, two of the addends can be multiplied by an attribute value. Some of the addends are calculated according to given formulas.
    For the perceived journey time, the following formula is used:
    Coefficient In-vehicle time (in)direct numerical attribute of vehicle journey items
    + Coefficient PuT-Aux ride time (in)direct numerical attribute of the
    transport system
    + Coefficient Access time
    + Coefficient Egress time
    + Coefficient Walk time
    + Coefficient Origin wait time
    + Coefficient Transfer wait time
    + Coefficient Number of transfers Formula
    + Coefficient Number of operator changes
    + Coefficient Extended impedance Formula
    Notes
    Double-click a coefficient to edit the value.
    A coefficient may have a negative value.
    Click the In-vehicle time or PuT-Aux ride time buttons to open an attribute selection window (see "The window used for the selection of one attribute" on page 963). Each button label indicates the selected attribute. By
    default, no attribute has been selected. The label shows factor 1.0 instead.
    Via the Parameters buttons, you can open the appropriate window and
    define there how the respective time is to be calculated:
    Origin wait time (see "Parameters for origin wait time calculation" on
    page 2038)
    Transfer wait time (see "Parameters for transfer wait time calculation" on page 2038)
    Number of operator changes: Select the attribute that defines whether two operators are identical. By default, the operator number is
    regarded. Instead, you may select an appropriate attribute to regard
    regional operator associations, for example.
    Via the Formula buttons, you can open the appropriate window and
    define there how the respective value is to be calculated:
    Number of transfers (see "Journey time-based factor for the number

    2036

    PTVGROUP

    19.2.4.5 Timetable-based assignment:Impedance tab


    Element

    Description
    of transfers" on page 2039)
    Extended impedance (see "Formula for the extended impedance calculation" on page 2039).
    BoxCox and Lambda
    If the option BoxCox is selected, the respective addend is transformed
    (Box-Cox) to the Lambda parameter entered (see Fundamentals: Chpt.
    7.10.5.1 , page 505).
    Notes
    If option BoxCox has been checked, double-click to edit the corresponding Lambda value.

    Consider
    connections
    with DeltaT >
    0, if connection with DeltaT = 0 exists.

    DeltaT is the difference between desired departure time interval and


    actual departure time.

    Impedance =

    The table represents the formula for connection impedance calculation.


    The impedance sums up from perceived journey time, fare and deviations
    of the departure from the desired time interval.
    Note
    On the Basis tab, click Use capacity restriction to additionally add a
    Vol/Cap ratio-dependent impedance.
    The addends are listed by row and each of them is multiplied by a constant coefficient.
    If the option BoxCox is selected, the respective addend is transformed
    (Box-Cox) to the Lambda parameter entered (see Fundamentals: Chpt.
    7.10.5.1 , page 505).
    Notes

    If this option has been checked, all found connections are available to
    passengers within a certain time interval of the time series.
    If this option has not been checked, only connections which depart
    within this time interval are available to passengers within a certain time
    interval of the time series. If there are no connections within this time interval, also this option provides all connections.

    Double-click a coefficient to edit the value.


    A coefficient may have a negative value.
    If option BoxCox has been checked, double-click to edit the corresponding Lambda value.

    PTVGROUP

    2037

    19.2.4.5 Timetable-based assignment:Impedance tab


    Parameters for origin wait time calculation
    Element

    Description

    Origin wait
    time =

    Formula for origin wait time computation.


    Origin wait time = A (Assignment time interval / Service frequency) E

    with service frequency being the service frequency of all connections.


    You may edit factor A and the exponent E.
    Notes
    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 the case of low service frequency.
    The origin wait time is the same for all connections of an OD pair. Including it in the PJT is therefore just like a constant supplement. The output
    of OWT in a skim matrix can be important for the network analysis.
    Max.

    Maximum value of the origin wait time

    Parameters for transfer wait time calculation

    Element

    Description

    Transfer wait time Maximum value of the transfer wait time or of the extended transfer
    =
    wait time respectively, if option Use extended TWT has been selected.
    Extended transfer Use extended TWT
    wait time
    If the option has been checked, instead of the regular transfer wait
    time the extended transfer wait time is used for PJT computation. Furthermore, the extended transfer wait time is used for skim calculation,
    if this is to be computed.

    2038

    PTVGROUP

    19.2.4.5 Timetable-based assignment:Impedance tab


    Element

    Description
    The extended transfer wait time is calculated with a formula whose
    parameters you can set (see Fundamentals: Chpt. 7.10.4.1 , page
    502).
    n
    Exponent of the function that is used for extended transfer wait time
    calculation.
    t0
    The transfer wait time considered ideal, it might depend on the transfer walk time.
    Note
    By default, n=2 and t0=5 is set.

    Use constant
    If this option has been checked, the extended transfer wait time is
    value for transfers automatically set to the entered value as soon as a PuT-Aux transwith TSys of PuT- port system is involved. Transfers between PuT lines are not affected.
    Aux type
    Journey time-based factor for the number of transfers

    Here, define a term to be multiplied by the number of transfers. The term depends on the journey time of the path if the entered journey time factor differs from null.
    Formula for the extended impedance calculation

    PTVGROUP

    2039

    19.2.4.5 Timetable-based assignment:Impedance tab


    Note: The extended impedance includes up to five components which are summed up.
    Tip: The formula for perceived journey time calculation already contains addends for
    access time, egress time, walk time, and in-vehicle time (see "Timetable-based assignment:Impedance tab" on page 2034). You have the choice: The calculation settings of
    these times defined here you may use either additively or instead of the addends defined
    there. To use them instead of the settings defined there, you need to set the particular
    coefficients to 0 in the formula for perceived journey time calculation.
    Element

    Description

    Access + egress + If this option has been checked, the walk times are calculated accorwalk times
    ding to the given formula and will be added to the extended impedance. Both the factors you may adjust.
    Note
    This non-linear evaluation of walk times is used for the Standardized Assessment (Modal Split) procedure, for example.
    In-vehicle time

    If this option has been checked, the in-vehicle time is calculated


    according to the given formula and will be added to the extended
    impedance. You may adjust the two factors and click the buttons to
    select a direct or indirect attribute of the vehicle journey items (see
    "The window used for the selection of one attribute" on page 963).
    Note
    Via this non-linear evaluation of run times you can consider advantages of transport means with regard to comfort and image, for
    example. For Standardized assessment various criteria are recommended to include the quality of the transport means and also the
    use of road or rail track.

    Transfer penalty
    depending on path
    leg run time

    If this option has been checked, the transfer time penalty is calculated according to the given formula and will be added to the
    extended impedance.
    Note
    The formula meets the requirements for Standardized assessment.

    Penalty for boardings, transfers,


    alightings

    2040

    If this option has been checked, for each boarding or alighting or


    transfer event the time penalty is calculated according to the given
    formula and will be added to the extended impedance. You may
    adjust the factors and click the buttons to select an attribute of the
    vehicle journey items (see "The window used for the selection of
    one attribute" on page 963).
    Note
    This way you can model to which degree the quality of a transfer
    event depends on the properties of the arriving and/or departing

    PTVGROUP

    19.2.4.6 Timetable-based assignment:Choice tab


    Element

    Description
    vehicle journey.

    Penalty per intermediate stop


    19.2.4.6

    If this option has been checked, the constant time penalty is added
    to the extended impedance for each intermediate stop.

    Timetable-based assignment:Choice tab


    In this tab, you define how to distribute the demand to the found connections.

    Element

    Description

    Choice model

    From the drop down list, select the appropriate choice model. The
    model controls the distribution of the demand to the individual
    connections according to the connection impedances. You can edit
    specific parameters for each choice model (see Fundamentals: Chpt.
    7.10.5.2 , page 506).

    Independence

    Use independence
    If this option is selected, the discreteness of the connections in the
    choice model selected is taken into account (see Fundamentals:
    Chpt. 7.10.5.2 , page 506).
    Note

    PTVGROUP

    2041

    19.2.4.7 Timetable-based assignment:Capacity restriction tab


    Element

    Description
    The independence of a connection codes the information whether
    there are interesting contemporary connections which could alternatively be used by passengers. When determining the value,
    always arrival AND departure times of connections are regarded.
    Optionally, also the qualitative skims perceived journey time and fare
    can be included.
    Maximum time slot
    Over this maximum period of time, connections may have an influence on each other. The value must be greater than null.
    Impact of perceived journey time and fare
    Value indicating the impact of PJT and fare for the independence calculation (0: no impact, 1: maximum impact). This value complies with
    variable c.
    Impact on connections of high quality
    Value for the impact of worse connections on a better one.
    Impact on connections of low quality
    Value for the impact of better connections on a worse one.
    Note
    The value entered for Impact on connections of high quality may not
    exceed the value entered for Impact on connections of low quality.

    19.2.4.7

    Timetable-based assignment:Capacity restriction tab


    In this tab, you specify the capacity restriction settings for assignment (see Fundamentals:
    Chpt. 7.10.8 , page 521). Capacity restrictions model the passengers' discomfort which cannot
    be taken into account if just the standard settings are used for the timetable- based assignment.
    Note: To include the capacity restrictions into the computation, you need to check the
    option Use capacity restriction in the Basis tab.

    2042

    PTVGROUP

    19.2.4.7 Timetable-based assignment:Capacity restriction tab

    Element

    Description

    Capacity per
    vehicle journey
    item

    Click this button to select the attribute, which defines the capacity of a
    vehicle journey item. By default, Sum:Vehicle journey sections/Vehicle combination/Seat capacity is set.
    Notes
    Alternatively, select a user-defined attribute or a formula attribute,
    which is calculated from the number of seats multiplied by the desired target saturation.
    Different capacity values by calendar day cannot be pre-defined.

    Search

    In the loaded network, search a second time


    If this option is selected, the connection search is repeated in the loaded network (see Fundamentals: Chpt. 7.10.8.1 , page 522).
    Note
    Use the second connection search to prevent alternative connections
    from being dominated.
    This option is only relevant, if in the Search tab the option Branch &
    bound search is selected.
    Merge the results of 1st search and 2nd search
    Select this option to combine the connection results of both searches that are then available for further processing.

    PTVGROUP

    2043

    19.2.4.8 Timetable-based assignment:Vol/Cap ratio-dependent impedance tab


    Element

    Description
    If this option is not selected, the connection results of the second
    search only are available for further processing.
    Note
    The option is grayed out, if the option In the loaded network, search
    a second time is not selected (see Fundamentals: Chpt. 7.10.8.1 ,
    page 522).

    Termination conditions

    Maximum number of iterations


    Number of iterations as a termination criterion, if the procedure cannot reach convergence with the selected iteration algorithm.
    To all volumes of vehicle journey items in time step i applies:
    Formula for the computation of the termination condition. You can
    adjust the factors.

    Convergence pro- Log convergence


    tocol
    If this option has been checked, a protocol file is generated. Click the
    button to select a path and file name.
    Smoothing
    method

    19.2.4.8

    Applied smoothing method


    In the selection list, select the smoothing method for the calculation.
    You can either smooth the vol/cap ratio (see Fundamentals: Chpt.
    7.10.8.3 , page 524) or the impedance (see Fundamentals: Chpt.
    7.10.8.4 , page 525).
    Vol/Cap ratios interpolated
    Select this option to smoothen the vol/cap ratios of the connections.
    In the formula used to calculate the smoothened vol/cap ratio, you
    can adjust this factor.
    Impedance exponential
    If the option is selected, the smoothed impedances of the connections will be calculated from the impedances of the previous iteration.
    In the formula used to calculate the smoothened impedance, you can
    adjust this factor.
    Impedance MSA
    If the option is selected, the convergence of the impedances and consequently the convergence of the volumes will be forced in the procedure. Then the procedure will use the smoothed impedances
    instead of the real impedances.

    Timetable-based assignment:Vol/Cap ratio-dependent impedance tab


    In this tab you define the impedance function and set the parameters for the computation of the
    vol/cap ratio-dependent impedance.
    Note: During the 'Choice', the vol/cap ratio-dependent impedance will be added to the
    actual impedance.

    2044

    PTVGROUP

    19.2.4.8 Timetable-based assignment:Vol/Cap ratio-dependent impedance tab

    PTVGROUP

    2045

    19.2.4.9 Timetable-based assignment:Skim matrices tab


    Element

    Description

    Applied volumedelay function

    DB
    If the option is selected, the calculation of the vol/cap ratio-dependent
    impedance is based on the volume-delay function of the Deutsche
    Bahn (German rail). In this case, the so-called expected standing
    minutes (E) are taken into account (see Fundamentals: Chpt.
    7.10.8.2 , page 523).
    Note
    The expected standing minutes (E) are the mean value of the minutes a passenger has no seat during his journey, if the seats are randomly provided to passengers on each stop-stop relation.
    In the formula used to calculate the smoothened impedance, you can
    adjust these factors.
    SBB
    If the option is selected, the calculation of the vol/cap ratio-dependent
    impedance will use a penalty function on the basis of the volumedelay function of the SBB (Swiss rail).
    In the formula used to calculate smoothened impedance, you can
    adjust these factors (see Fundamentals: Chpt. 7.10.8.2 , page 523).
    Linear
    If the option is selected, the vol/cap ratio-dependent impedance will
    use a penalty function for the linear calculation.
    In the formula used to calculate smoothened impedance, you can
    adjust these factors (see Fundamentals: Chpt. 7.10.8.2 , page 523).

    Choice

    19.2.4.9

    2046

    Shift volumes among adjacent connections


    If the option is selected, the volume is shifted between adjacent
    connections instead of applying the choice model to all connections
    with each iteration (see Fundamentals: Chpt. 7.10.8.5 , page 526).
    Factor for alternating standby
    Value for the computation of the deterrence of volumes between
    connections and their corresponding alternatives.
    Factor for expected minutes without seat
    Value for the expected standing minutes which is included in the
    choice calculation.
    Note
    The Choice section is only available if you have selected the DB
    impedance function.

    Timetable-based assignment:Skim matrices tab


    You only have to set parameters for skim matrix calculation, if you want to calculate assignment and skim matrices simultaneously (see "Settings for PuT skim matrix calculation" on
    page 2078).
    PTVGROUP

    19.2.4.10 Timetable-based assignment:Connection export tab


    Note: To have skim matrices calculated, in the Basis tab, select Calculate skim matrices.
    19.2.4.10 Timetable-based assignment:Connection export tab
    In this tab, you define how to export the found connections.
    Note: For export of connections, you need to check the option Connection export in the
    Basis tab.

    PTVGROUP

    2047

    19.2.4.10 Timetable-based assignment:Connection export tab


    Element

    Description

    Export file(s)

    The connections are stored in several files. You need to specify the
    name for the first file, the so-called master file. Visum then automatically creates other files having the same name and an index
    number attached.
    File name
    button, you can enter or select file name (and path, if appVia the
    licable) for the master file. Notes
    The file has the binary *.con format.
    In the master file, Visum stores important information on the other
    files. This is required for the import of connections (see "Timetablebased assignment:Basis tab" on page 2022 and "Connections:importing" on page 2560).
    Maximum size of a single file is about
    Maximum size of the files.
    Notes
    The size of the files may differ significantly.

    Export of paths

    With volumes
    If this option has been checked, the connections are exported including their volumes.
    Note
    When you export volumes, only DSegs with volumes that are not
    saved to other DSegs are taken into account (see "Saving volumes
    by demand segment or additively" on page 2003).
    With fare points
    If this option has been checked, the connections are exported including their fare points. The fare points are allocated by path leg.
    Regard all relations
    If this option has been checked, connections are determined for
    each OD pair.
    If this option has not been checked, connections are determined
    only for OD pairs with demand > 0.
    With user-defined attributes
    Select this option to additionally export user-defined attributes of PuT
    paths.

    2048

    PTVGROUP

    19.2.4.10 Timetable-based assignment:Connection export tab


    Element

    Description

    Export of fares

    Do not export
    If this option has been selected, the fares are not exported.
    On path level
    If this option has been selected, the fare by connection is exported.
    If multiple demand segments are assigned while this option is
    checked, then the demand segment for the fare calculation per path
    has also to be selected in the list. Click All demand segments to
    export the fares separately per demand segment.
    On path leg level
    If this option has been selected, the fare by path leg is exported.
    If multiple demand segments are assigned while this option is
    checked, then the demand segment for the fare calculation per path
    leg has also to be selected in the list. Click All demand segments to
    export the fares separately per demand segment.
    Notes
    The selection list is invisible as long as only a single demand segment is to ne assigned.
    The selection list is grayed out as long as the option Do not export is
    selected for assignment of multiple demand segments.

    Adjusting the Visum registry to speed up timetable-based assignment calculation


    You can speed up the calculation of timetable-based assignment on computers with more
    than 12 kernels by changing the registry of your Visum installation.
    There is no universally optimal setting, as it depends on the hardware of each user. The following section describes the registry keys whose configuration can help improve computation
    speed. We recommend that you test different settings. The following description is for Windows
    7.
    1. In the Windows task bar, click the Start button.
    2. In the search box, enter Regedit.
    3. Press ENTER.
    The Registration editor opens.
    4. Navigate to HKEY_CURRENT_USER\Software\PTV AG\Vision\Visum\130\Common\Misc.
    5. Enter the ProcessorInfo key.
    6. In the ProcessorInfo key, enter the keys AvoidMemoryDonationsToOtherProcessors, CoreEnumerationOrder, and NumberOfProcessors of the type REG-DWORD.

    PTVGROUP

    2049

    19.2.4.10 Timetable-based assignment:Connection export tab

    2050

    Registry key

    Description

    NumberOfProcessors

    Enter the number of physical processors your computer has. The number of kernels is not relevant.
    Note
    If you enter a higher number of processors than
    your computer has, you will need more main
    memory during computation.

    CoreEnumeration order

    Specifies the distribution of real and virtual kernels across the processors.
    The value 0 means that the real and virtual
    kernels are numbered alternately.
    Example: A computer has 2 processors and
    16 kernels:
    Kernels 1 to 8 belong to processor 1. Thereby
    kernels 1, 3, 5, 7 are real, and kernels 2, 4, 6,
    8 are virtual kernels. Kernels 9 to 16 belong
    to processor 2. Thereby kernels 9, 11, 13, 15
    are real, and kernels 10, 12, 14, 16 are virtual
    kernels.
    The value 1 means that real and virtual kernels are numbered in two halves. The first
    half consists of real kernels. The second half
    consists of virtual kernels.
    Example: A computer has 2 processors and
    16 kernels:
    Kernels 1, 2, 3, 4, 9, 10, 11, 12 belong to processor 1. Thereby, kernels 1, 2, 3, 4 are real
    kernels and kernels 9, 10, 11, 12 are virtual
    kernels. Accordingly, kernels 5, 6, 7, 8, 13, 14,
    15, 16 belong to processor 2. Thereby, kernels 5, 6, 7, 8 are real kernels, and kernels
    13, 14, 15, 16 are virtual kernels.
    Notes
    If you do not know your computer's architecture,
    you will have to try which value leads to the faster
    computational results.
    The free software CoreInfo, which belongs to
    Microsoft's SysInternals Suite, can provide information on the processors and kernels of your computer. The analyses results obtained with
    CoreInfo can help you determine the right settings
    for your computer.

    AvoidMemoryDonations-

    Specifies the memory exchange between pro-

    PTVGROUP

    19.3 Importing, checking and assigning passenger onboard surveys


    Registry key

    Description

    ToOtherProcessors

    cessors.
    The value 0 means that during computation
    free memory is exchanged between the processors. For some computers this can slow
    down the computation process.
    The value 1 means that the exchange of
    memory is prevented.

    7. In the ProcessorInfo folder, right-click the key of your choice and from the shortcut menu,
    choose Edit.
    8. In the Value box, enter the settings of your choice.
    9. Confirm with OK.
    The value of the key is changed.

    19.3

    Importing, checking and assigning passenger onboard surveys


    Passenger sample surveys - interviews and counts - are essential for public transport supply
    planning. You have to read the survey data in Visum, then the data needs to be checked and
    completed, if applicable. Subsequently, the data can be directly assigned and evaluated (see
    Fundamentals: Chpt. 7.12 , page 531).
    Notes: This function is only available with the Passenger onboard survey add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    The same functionality can be applied to data extracted from e-ticketing applications, if
    the data contain at least check-in information per path leg with line route, stop point, and
    departure time. In this case, a path leg needs to be marked as surveyed path leg.

    19.3.1

    Preparing survey sample data


    The data need to be available as text file in either single-row format or multi-row format which
    can be read in Visum.
    Single-row survey data files contain one data record per row (see "Format of a single-row
    survey file" on page 2052).
    Multi-row survey data files contain the paths in path leg data format. Each row includes a
    path leg (see "Format of a multi-row survey file" on page 2053).
    Notes: When reading survey data, data records with a departure time past midnight
    (24:00 to 48:00) are permitted. Such data records are converted to format 0-24 for output
    after plausibilization, departure times >24:00 then fall on the next valid day.
    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.
    If one of these stops is deleted after reading survey data from file, all paths from/to these
    stops will get lost.

    PTVGROUP

    2051

    19.3.1.1 Format of a single-row survey file


    19.3.1.1

    Format of a single-row survey file


    The example below shows a single-row record file.
    $VISION
    * VisumInst
    * 24.07.08
    *
    *
    * Table: Version block
    $VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
    4.00;SingleRowSurveyData;ENG;KM
    * Table: Single-row survey data
    $SingleRowSurveyData:No;Type;
    SurveyLineName;SurveyLineDirCode;SurveyLineRouteName;SurveyTimeProfileName;
    PreTSysCode;PreLineName;PreLineDirCode;PreLineRouteName;PreTimeProfileName;SucTSysCo
    de;SucLineName;SucLineDirCode;SucLineRouteName;SucTimeProfileName;InputStopNo;InputS
    topDepDay;InputStopDepTime;OrigZoneNo;OrigStopNo;PreStopNo;BoardStopNo;AlightStopNo;
    SucStopNo;DestStopNo;DestZoneNo;NumPass;ExtProjFac
    1;0;Train;H;1;;B;BUS1;H;1;1;;;;;;;;5;1;6:26:00;;30;10;20;40;;40;;17;
    2;0;Train;R;1;1;;;;;;;;;;;;;5;1;6:25:00;100;;10;20;40;;40;;29;
    3;99;Train;H;1;1;B;;;;;;;;;;5;1;6:25:00;;;;10;10;20;40;;40;;33;
    4;0;BUS1;H;1;1;B;BUS1;H;1;1;;;;;;5;1;6:15:00;;;;10;20;30;40;;40;;18;
    5;0;BUS1;H;1;1;;;;;;Z;Train;R;1;1;5;1;6:05:00;1;6:10:00;;10;;10;20;;40;;15;3

    The table below describes the mandatory and optional attributes of a single-row survey data
    file. Mandatory attributes are indicated by P, optional attributes have the O flag.
    Attribute

    Description

    No.

    Number of the data record

    Type

    Data record type, serves for filtering during plausibilization (Default: 0)

    SurveyLineName

    Key of the survey


    line, consisting of 4
    SurveyLineDirCode
    compounds. These
    SurveyLineRouteName attributes need to
    Surmatch.
    veyTimeProfileName

    Direction code of survey line

    Name of the surveyed line route

    Name of the surveyed time profile

    PreTSysCode

    Code of the preceding lines TSys

    PreLineName

    PreTimeProfileName

    Four-part key of the Name of the preceding line


    prec. leg These
    Direction code of the preceding line
    attributes need to
    Name of the preceding line route
    match.
    Name of the preceding time profile

    SucTSysCode

    Code of the succeeding lines TSys

    PreLineDirCode
    PreLineRouteName

    2052

    Name of the survey line

    O
    O
    O
    O

    PTVGROUP

    19.3.1.2 Format of a multi-row survey file


    Attribute

    Description

    SucLineName

    Four-part key of the


    succ. leg These
    attributes need to
    be consistent with
    each other.

    SucLineDirCode
    SucLineRouteName
    SucTimeProfileName

    19.3.1.2

    Name of the succeeding line

    Direction code of succeeding line

    Name of the succeeding line route

    Name of the succeeding time profile O

    InputStopDepTime

    Time of departure time of the survey line from the stop


    specified as InputStopNo.

    InputStopDepDay

    Day of departure of the survey line from the stop specified P


    as InputStopNo.

    InputStopNo

    Number of the stop in the survey line, to which the values P


    InputStopDepTime and InputStopDepDay refer.

    OrigZoneNo

    Number of the passengers origin zone. If the


    O
    OrigStopNo is also defined, both numbers have to match:
    At least one stop area of the stop needs to be allocated to
    a node which is connected to the zone.

    OrigStopNo

    Number of the start stop of the passenger trip.


    O
    If the OrigStopNo is missing, PreStopNo = OrigStopNo is
    assumed.

    PreStopNo

    Number of a preceding stop (transfer stop) of the passenger trip.

    BoardStopNo

    Number of the stop where the passenger boarded the sur- P


    vey line.

    AlightStopNo

    Number of the stop where the passenger will alight the


    survey line.

    SucStopNo

    Number of a succeeding stop (transfer stop) of the passenger trip.

    DestStopNo

    Number of the passengers destination stop.


    O
    If the DestStopNo is missing, SucStopNo = DestStopNo
    is assumed.

    DestZoneNo

    Number of the passengers destination zone. If the


    O
    DestStopNo is also defined, both numbers have to match:
    At least one stop area of the stop needs to be allocated to
    a node which is connected to the zone.

    NumPassengers

    Number of boarding persons per ticket


    (= a data record, default value: 1)

    ExtProjFactor

    Via the external projection factor, external passenger


    weights can be taken into account.

    Format of a multi-row survey file


    The example below shows a multi-row record file.

    PTVGROUP

    2053

    19.3.1.2 Format of a multi-row survey file


    Notes: Multi-row survey data files are usually created by Visum. Thus, you may read the
    data from file and store them again multiple times consecutively which means an iterative
    plausibilization process. Visum creates multi-row survey data record files this way:
    Output of attribute files from PuT path leg lists (using the option Only PuT path legs)
    (see "Save list to attribute file" on page 2325).
    Output of result files during plausibilization
    To be able to reload survey data of PuT path leg lists that consist of multiple rows, select
    the format suitable for databases (without header) when you save the attribute file.
    $VISION
    * VisumInst
    * 06.03.07, 18.27.29
    *
    *
    * Table: Version block
    $VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
    4.00;Att;ENG;KM
    *
    *
    * Table: PuT path legs
    $PuTPathLeg:OrigZoneNo;DestZoneNo;PathLegIndex;ODTrips;DataSetNo;DataSetType;FromSto
    pNo;ToStopNo;TSysCode;LineName;DirectionCode;LineRouteName;TimeProfileName;StartTime
    ProfileItemIndex;EndTimeProfileItemIndex;TypeString;InputStopDepDay;InputStopDepTime
    ;FromStopPointNo;ToStopPointNo;DepDay;DepTime;ArrDay;ArrTime;Time;WaitTime;Path\ExtP
    rojFactor;Path\PathStatus;Path\SurveyLineStatus;Path\PreStatus;Path\SucStatus
    30;200;2;17.000;1;0;30;20;B;BUS1;R;1;1;2;3;V1;;;;;;30;20;1;07:58:00;1;08:18:00;20min;0s;1.000;1;1;4;0
    30;200;4;17.000;1;0;20;40;Z;Train;H;1;1;1;2;E;;;;1;06:26:00;20;40;1;06:25:00;1;06:41:00;16min;0s;1.000;1;1;4;0
    100;200;2;29.000;2;0;10;20;B;BUS1;H;1;1;1;2;V1;;;;;;10;20;1;06:10:00;1;06:22:00;12min;0s;1.000;1;2;1;0
    100;200;4;29.000;2;0;20;40;Z;Train;H;1;1;1;2;E;;;;1;06:25:00;20;40;1;06:25:00;1;06:41:00;16min;0s;1.000;1;2;1;0
    100;200;2;33.000;3;99;10;20;B;BUS1;H;1;1;1;2;V1;;;;;;10;20;1;06:10:00;1;06:22:00;12min;0s;1.000;1;1;1;0
    100;200;4;33.000;3;99;20;40;Z;Train;H;1;1;1;2;E;1;06:25:00;25;;;20;40;1;06:25:00;1;06:41:00;16min;0s;1.000;1;1;1;0
    100;200;2;18.000;4;0;10;30;B;BUS1;H;1;1;1;3;V1;;;;;;10;30;1;06:10:00;1;06:42:00;32min;0s;1.000;1;1;4;0
    100;200;4;18.000;4;0;30;40;B;BUS1;H;1;1;3;4;E;1;06:15:00;24;;;30;40;1;06:42:00;1;06:55:00;13min;0s;1.000;1;1;4;0
    100;200;2;45.000;5;0;10;20;B;BUS1;H;1;1;1;2;E;1;06:05:00;23;1;06:10:00;10;20;1;06:10:00;1;06:22:00;12min;0s;3.000;1;1;0;2
    100;200;4;45.000;5;0;20;40;Z;Train;H;1;1;1;2;N1;;;;;;20;40;1;06:25:00;1;06:41:00;16min;0s;3.000;1;1;0;2

    The following table describes the input attributes of a multi-row survey data record file. Mandatory attributes are indicated by P, optional attributes have the O flag. I marks attributes that
    are ignored.

    2054

    PTVGROUP

    19.3.2 Read survey data

    19.3.2

    Attribute

    Description

    DataSetNo

    Number of the data record

    DataSetType

    Type of the data record {1..32000}, serves as filter criterion for plausibilization (default value: 0)

    InputStopDepDay

    Day of departure of the survey line from the stop specified P


    as InputStopNo.

    InputStopDepTime

    Time of departure of the survey line from the stop specified as InputStopNo.

    InputStopNo

    Number of the stop to which InputStopDep and


    InputStopDepTime and InputStopDepDay refer.

    TimeProfileName

    Name of the time profile

    LineName

    Line name
    *(mandatory for survey path leg, else optional)

    P*

    LineRouteName

    Name of the line route

    ToStopNo

    Number of the ToStop

    ODTrips

    Path volume in [person trips]

    OrigZoneNo

    Number of the origin zone

    DirectionCode

    Direction code

    TypeString

    Type of the path leg, serves for path leg identification


    E = Survey path leg
    V = Preceding path leg
    N = Succeeding path leg
    T = any other path leg (Standard value which is set
    when reading invalid data from file)

    PathLegIndex

    Path leg index

    FromStopNo

    Number of the FromStop

    TSysCode

    Transport system code

    PathInd

    Path index

    DestZoneNo

    Number of the destination zone

    Path\ExtProjFactor

    The external projection factor is a path attribute and must O


    be specified in each row of a data record. If there are different entries, the last value read is adopted.

    Read survey data


    1. Make sure the survey data is saved in one of the formats required (see "Preparing survey
    sample data" on page 2051).
    2. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    PTVGROUP

    2055

    19.3.2 Read survey data


    3. Add the procedure Read survey data of the PuT Passenger surveys category to the position of your choice in the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).
    4. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select demand segment window opens.
    5. Select the desired demand segment.
    6. Confirm with OK.
    The window closes. In the Reference object(s) column, the selected demand segment is
    listed.
    7. Select the operation added. Then in the Operations section, click the Edit button.
    The Read survey data window opens.
    8. Make the desired settings (see "Settings for reading survey data from file" on page 2057).
    9. Confirm with OK.
    10. In the row of the added procedure, click in the Variant/file column.
    The icon
    11. Click the

    is displayed.
    icon.

    The Open survey data window opens.


    12. Select the desired file.
    13. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell in the Variant/file column and manually enter the path and file name.
    14. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Note: If there are incorrect data records, an error message appears for each faulty
    data set. Incorrect data records are not read from file.
    The survey data record file is read. This data is stored as PuT paths on connection level, missing zones and connectors are created according to your parameter settings.

    2056

    PTVGROUP

    19.3.2.1 Settings for reading survey data from file


    Notes: You can show the imported data in the lists PuT paths and PuT path legs (see
    "Opening a list" on page 2299).
    Data records recently read from file have plausibility status 0 first, which indicates that
    plausibilization has not yet been performed. In the next step, you need to perform data
    plausibilization. Subsequently, you can assign the data.
    If you have specified that you want to save volumes of the selected demand segment with
    another target demand segment (see "Saving volumes by demand segment or additively"
    on page 2003), your setting is automatically reset during data import (target demand segment = selected demand segment).
    19.3.2.1

    Settings for reading survey data from file


    Element

    Description

    Read additionally

    If this option has been checked, survey data are read additionally to loaded
    data (either after or prior to plausibilization) which were read from file for the
    selected demand segment before.

    Conflict
    handling

    Via this option you define how to handle data records to be read from file
    whose data record number already exists.
    Ignore new data record
    If this option has been checked, the data record is not read from file.
    Override old data record
    If this option has been checked, the new data record is read from file this
    way replacing the existing data record.
    Cancel reading completely
    If this option has been checked, reading is cancelled.

    PTVGROUP

    2057

    19.3.2.1 Settings for reading survey data from file


    Element

    Description

    Protocol

    No protocol
    If this option has been checked, no protocol file is generated. The messages, however, are displayed on the screen and are saved to the Message
    file, if you have set the options accordingly (see "Using protocol files" on
    page 876).
    In file
    butIf this option has been checked, a protocol file is generated. Click the
    ton to select a path and file name. The protocol file stores messages and
    details on data not read from file.

    Zones

    Each path starts in a zone and ends in another zone. In case of incomplete
    path information from survey data or if zones are missing or demanded
    stops are not connected to a zone, Visum automatically creates missing
    zones and connectors. If, for a stop, a connector (PrT or PuT) already exists
    for a TSys different from the PuTAux-TSys of the survey data record, then
    this connector is opened for the PuTAux-TSys of the survey data record and
    no zone is generated.
    Delete existing zones first
    If this option has been checked, all zones existing in the network are deleted and new zones will be generated to connect origin and destination
    stops.
    If this option has not been checked, zones existing in the network are not
    deleted. Existing allocations of zones and stops are handled according to
    option Create zone even if stop has already been connected.
    Create zone even if stop has already been connected
    If this option has been checked, all of the existing allocations between
    zones and stops are ignored. Instead, new zones are created to connect the
    stops.
    If this option has not been checked, all of the existing allocations between zones and stops remain unchanged. Only for stops that have not yet
    been connected new zones are created.
    Note
    This option is only provided if option Delete existing zones first has not
    been checked.
    Type of generated zones
    Zone type of the generated zones (see "Zones: General attributes" on page
    1137)
    Type of generated PuT Walk connectors
    Connector type of the generated connectors (09) (see "Connectors: General attributes" on page 1161)
    Connector length

    2058

    PTVGROUP

    19.3.3 Plausibilization of survey data


    Element

    Description
    Distance between the zone's centroid and the access node of the stop area
    (see "Generating zones" on page 1152).
    Connector time for all permitted TSys:
    Connector time (see "Generating zones" on page 1152)

    19.3.3

    Plausibilization of survey data


    In general, the survey data you import is incomplete. You need to check and complete the data
    records, if required, by adding plausible data for missing information (see Fundamentals:
    Chpt. 7.12.4 , page 535).
    Plausibilization includes the following steps.
    Validity check of the survey path leg
    Validity check of the preceding path leg and the succeeding path leg
    If plausibilization of a survey path leg is not successful, both the preceding and the succeeding
    path leg will be ignored.
    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.
    Note: After plausibilization, a plausibility status is allocated to the survey path leg (E1
    E9), to the preceding path leg (V1V9) and to the succeeding path leg (N1N9) of
    each data record. Furthermore, each data record stores an overall status. With 100%
    plausible path legs, this overall status is plausible (G1), otherwise it is not plausible (G9)
    (see Fundamentals: Chpt. 7.12.4 , page 535).
    1. Import the desired survey data (see "Read survey data" on page 2055).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the procedure Plausibilization of survey data of the PuT Passenger surveys category to the position of your choice in the procedure sequence (see "Setting up and starting
    the procedure sequence" on page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select demand segment window opens.
    4. Select the desired demand segment.
    5. Confirm with OK.
    The window closes. In the Reference object(s) column, the selected demand segment is
    listed.
    6. Select the operation added. Then in the Operations section, click the Edit button.
    The Plausibilization of survey data window opens.

    PTVGROUP

    2059

    19.3.3.1 Settings for plausibilization of survey data records


    7. Make the desired settings (see "Settings for plausibilization of survey data records" on page
    2060).
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The survey data records are verified and the plausibilization is performed. You can show the
    results in lists or in files (see "Viewing results of plausibilization" on page 2070). After plausibilization, you may use the data for direct assignment (see "Assignment of survey data" on
    page 2071).
    19.3.3.1

    Settings for plausibilization of survey data records


    Plausibilization of survey data:General parameters tab

    2060

    PTVGROUP

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description

    General extent of
    plausibilization

    All
    If this option has been checked, all data records even those previously checked are subjected to a plausibility check with the selected parameters.
    Note
    Since this procedure costs much computation time, this option should
    be applied carefully. For example, you may finally perform plausibilization for all survey data records all at once by means of identical parameters after separate irrespective plausibilization of certain
    data records with the help of different parameters.
    Only untreated ones
    If this option has been checked, only untreated data records - having
    plausibility status G0 are subject to plausibilization.
    Only untreated or implausible ones
    If this option has been checked, only data records having either plausibility status G0 (untreated records) or plausibility status G9 (unsuccessful plausibilization result = implausible) are subject to
    plausibilization.

    Extent of plauAll
    sibilization by data If this option has been checked, all data records are subjected to a
    set type
    plausibility check with the selected parameters.
    Only types from / to
    If this option has been checked, only data records of the given type(s)
    are subjected to a plausibility check.

    PTVGROUP

    2061

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description

    Result file

    No output file
    If this option has been checked, no result file is generated.
    In file
    If this option has been checked, a result file is generated. Via the
    button, you can enter or select file name and path, if applicable, for
    the file. The result file contains the results of plausibilization and includes information on plausibilization quality in a multi-row format. Its
    file extension is *.att (see "Format of a multi-row survey file" on page
    2053).
    Notes
    The result file contains only those data records that have just been
    subjected to plausibilization. Thus it may contain less data records
    compared to the PuT path leg list.
    You can read in the result file similarly to a survey data record file to
    perform another plausibilization run, with criteria that are easier to
    meet (see "Read survey data" on page 2055).

    Protocol

    No protocol
    If this option has been checked, no protocol file is generated.
    In file
    If this option has been checked, a protocol file is generated. Via the
    button, you can enter or select file name and path, if applicable,
    for the file. In the log file, you can check the results of plausibilization
    (see "Example of a log file" on page 2071).

    Plausibilization of survey data:Survey path leg tab


    In this tab you configure the parameters for plausibilization of survey path legs.

    2062

    PTVGROUP

    19.3.3.1 Settings for plausibilization of survey data records

    PTVGROUP

    2063

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description

    Survey line Different line route permitted


    If this option has been checked, Visum searches also in time profiles (or line
    routes, respectively) different from the one specified for the survey line in the
    survey data record. The survey path leg of a data record is plausible and
    receives status E2, if - in the network - another time profile (or line route) of
    the survey line is found to which the following applies
    Matching SurveyLineName and SurveyDirectionCode.
    The departure time lies within the permitted tolerances (please refer to
    Departure time).
    The departure time is the closest moment in time compared to other
    time profiles of the survey line.
    Different line and line route permitted
    If this option has been checked, Visum searches also in the time profiles (or
    line routes, respectively) of other lines. The survey path leg of a data record
    is plausible and assigned the status E3, if - in the network - another time profile (or line route) of another line is found for which the following applies
    The departure time lies within the permitted tolerances (please refer to
    Departure time).
    The departure time is the closest moment in time compared to other
    time profiles in the network.
    No different line or line route permitted
    Select this option if you want Visum to first search the time profile (or line
    route) data that, in the survey data record, has been specified for the survey
    line. In this case, the survey path leg of a data record is plausible and receives status E1, if - in the network - a time profile (or line route) is found to
    which the following applies
    Matching SurveyLineName and SurveyDirectionCode and SurveyLineRouteName and SurveyTimeProfName.
    The departure time lies within the permitted tolerances (please refer to
    Departure time).
    Only after an unsuccessful search is the survey line specified ignored and
    other lines and line routes are included in the search.
    Departure
    time

    2064

    Max. permitted deviation from the specified time of departure (+/-)


    Time slice defining the tolerances when searching for an appropriate
    vehicle journey or connection either before or post the given departure time
    from the boarding stop.

    PTVGROUP

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description

    Connection Connection search from boarding to alighting stop, if no line route could
    search
    be found
    If this option has been checked, a shortest path search is performed for
    all data records for whose survey line no vehicle journey could be found
    according to the current settings in the Survey line section. This determines
    a direct or indirect connection with a departure time from the boarding stop,
    that lies within the permitted deviation (cf. departure time).
    Notes
    The connection search regards the current settings in the Search options
    section.
    Data records that satisfy these criteria, receive plausibility status E5 for the
    survey line.
    If this option has not been checked, the shortest path search is not performed.. All data records which could - according to the Survey line criteria not successfully be subjected to plausibilization, remain 'not plausible' (E7,
    E8).
    Search opti- Parameters for timetable-based connection search (Shortest path search).
    ons
    Regard only active vehicle journey sections
    If this option has been checked, only active vehicle journey sections are
    regarded for connection search.
    Note
    This option is also regarded for time profile search according to the settings
    in the Survey line section.
    Max. number of transfers
    If the value exceeds0, also indirect connections will be found.
    Note
    For working storage reasons this value should be as small as possible (2
    should do in most of the cases).
    SearchImp
    The connection with the minimum journey time is determined for each permitted number of transfers. Then the connection with the lowest search impedance (by definition) is selected (see "Shortest path search" on page 2029).
    Correction (reverse)
    (see "Shortest path search" on page 2029)
    Plausibilization of survey data:Pre-/Succeeding tab
    In this tab you configure the parameters for plausibilization of preceding and succeeding path
    legs.

    PTVGROUP

    2065

    19.3.3.1 Settings for plausibilization of survey data records

    Notes: If the a preceding or succeeding path leg includes several path sub-legs these
    path sub-legs will be subjected to plausibilization consecutively. For each path sub-leg
    from inside to outside (from the survey line to the origin or to the destination respectively)
    the plausibilization steps are performed one by one until plausibility is reached for this
    path leg. This might result in different status values for the path legs. To the entire preceding or succeeding path leg respectively, the worst status found for one of its path sublegs is allocated.
    If one of the path sub-legs is not plausible, the procedure described above is cancelled
    for the particular preceding or succeeding path leg respectively. In this case, plausibilization might still be reached by free connection choice for the entire preceding or
    succeeding path leg respectively.
    Via another option you may define, that finally all of the plausible preceding and succeeding path legs are to be compared to a possible direct connection and should be
    replaced by it, if applicable. This again could modify the plausibility status.

    2066

    PTVGROUP

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description

    Preced./succeed.
    line

    Different line route permitted


    If this option has been checked, Visum searches also in time profiles (or
    line routes, respectively) different from the one specified for the preceding/succeeding line in the survey data record. The preceding (or succeeding) path leg of a data record is plausible and receives status V2
    (or N2), if - in the network - another time profile (or line route) of the preceding (or succeeding) line is found to which the following applies
    Pre-/SucceedLineName and Pre-/SucceedDirectionCode match.
    The criteria listed in the Dep. times section are fulfilled.
    The departure is the closest moment in time compared to other time
    profiles of the preceding/succeeding line.
    Permit other line
    If this option has been checked, Visum searches also in the time profiles
    (or line routes, respectively) of other lines. The preceding (or succeeding) path leg of a data record is plausible and receives status V3
    (or N3), if - in the network - any other time profile (or line route) of another line is found to which the following applies
    The criteria listed in the Dep. times section are fulfilled.
    The time of arrival or departure is the closest moment in time compared to other time profiles in the network.
    No different line or line route permitted
    Select this option if you want Visum to first search the time profile (or line
    route) data that, in the survey data record, has been specified for the
    Prec./Succeed.line. The preceding (or succeeding) path leg of a data
    record is plausible and receives status V1 (or N1), if - in the network - a
    time profile (or line route) is found to which the following applies
    Matching Pre-/SucceedLineName and Pre-/SucceedDirectionCode
    and Pre-/SucceedLineRouteName and Pre-/SucceedTimeProfName.
    The criteria listed in the Dep. times section are fulfilled.
    Only after an unsuccessful search is the Prec./Succeed.line specified
    ignored and other lines and line routes are included in the search.

    Departure
    times

    Ignore the possibly specified time of departure


    If this option has been checked, the path leg's time of departure possibly specified in the data record will be ignored during the search for an
    appropriate vehicle journey or connection. The search is based on the
    arrival (succeed.) or departure (preced.) of the particular internal path
    leg. Enter the desired wait time under maximum permitted transfer
    wait time.
    If this option has not been checked, the path leg's time of departure
    specified in the data record will be regarded during the connection

    PTVGROUP

    2067

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description
    search. Via Max. permitted deviation from specified time of departure
    (+/-) you can enter the desired tolerance range.
    Max. permitted deviation from the specified time of departure (+/-)
    Time slice defining the tolerances when searching for an appropriate
    vehicle journey or connection either before or post the given departure
    time.
    Notes
    This option is provided only if option Ignore the possibly specified time
    of departure has not been checked.
    This option applies to multi-row survey data records only, since singlerow data records do not contain departure time data of path legs.
    Use the max. permitted transfer wait time
    If this option has been selected, the maximum permitted wait time is
    taken into account between the regarded path leg and the next internal
    path leg. This way connections can be avoided which include an overnight wait time, for example.
    If this option has not been selected, wait times are not regarded
    during the search for an appropriate connection.

    2068

    PTVGROUP

    19.3.3.1 Settings for plausibilization of survey data records


    Element

    Description

    Connection
    search

    Find connection for a single path leg, if no line route could be found
    If this option has been checked, a shortest path search for a connection in the network is performed for that path sub-leg of the preceding or
    succeeding path leg for which no time profile or line route had been
    found.
    Notes
    The connection search regards the current settings in the Search options section.
    If - for the path leg - a connection (including walk links) between preceding and boarding stop or between alighting and succeeding stop is
    found which has a departure time that lies within the defined time slice
    for departures, plausibility status V5 or N5 will be allocated to the path
    leg.
    Here, ignore selected TSys, if applicable.
    If this option has been checked, the connection search will not regard
    the transport system recorded in the data record.
    Find connection for remaining preceding/succeeding path legs if plausibilization failed for a single sub-leg
    If this option has been checked, a connection search is performed in the
    network for data records with multi-leg preceding or succeeding path
    legs having an implausible sub-leg.
    Notes
    The connection search regards the current settings in the Search options section.
    If - for the remaining path sub-leg of the preceding or succeeding path
    leg - a connection (incl. walk links) is found, plausibility status V6 or N6
    respectively is allocated to the particular path leg.
    Compare plausible multi-leg preceding/succeeding parts to direct
    connection
    If this option has been checked, all data records with plausible multi-leg
    preceding/succeeding path legs are verified again. The journey time of
    the preceding/succeeding path leg is compared to the direct connection
    (no transfer events) from origin stop to boarding stop (and from alighting
    stop to destination stop respectively). If the journey time of the preceding
    (succeeding) section exceeds the result of factor journey time of direct
    connection + constant value, then the journey time of the direct connection will replace the preceding (succeeding) section.
    Notes
    Here, current search option settings do not take effect.
    Plausibility status V4 (or N4 respectively) is allocated to the preceding

    PTVGROUP

    2069

    19.3.3.2 Viewing results of plausibilization


    Element

    Description
    (or succeeding) section.

    Search options Parameters for timetable-based connection search (Shortest path


    search).
    Regard only active vehicle journey sections

    If this option has been checked, only active vehicle journey sections are
    regarded for connection search.
    Note
    This option is also regarded if time profiles are searched for.
    Max. number of transfers

    If the value exceeds0, also indirect connections will be found.


    Note
    For working storage reasons this value should be as small as possible
    (2 should do in most of the cases).
    SearchImp

    For each permitted number of transfers, the connection with the minimum journey time is determined. Then connection with the lowest
    search impedance (by definition) is selected (see "Shortest path search"
    on page 2029).
    Correction (reverse)

    (see "Shortest path search" on page 2029)


    19.3.3.2

    Viewing results of plausibilization


    You can save the results of plausibilization to an attribute file *.att. The output file is in the format of the multi-row survey data record and includes certain preset columns (see "Format of a
    multi-row survey file" on page 2053).
    You can also show the results in the lists PuT paths and PuT path legs (see "Opening a list"
    on page 2299). In the aforementioned lists, you can further show the plausiblization status of
    the data records. The PuT paths list contains the total path status. The PuT path leg list contains the status of of the partial legs.
    Path attribute

    Description

    Overall path sta- Plausibility status of the entire path


    tus

    2070

    Survey leg status

    Plausibility status of the survey path leg

    Pre-survey leg
    status

    Plausibility status of the preceding section

    Post-survey leg
    status

    Plausibility status of the succeeding section

    PTVGROUP

    19.3.4 Assignment of survey data


    Via the button next to Filter for path status you can reduce the content of the PuT path list and
    the PuT path leg list to a selected plausibility status of the total path.
    Note: When saving a list layout to file, the setting of the PathStatus filter is saved as well.
    You can save the PuT path legs list as an attribute file (see "Limiting list display to a selection"
    on page 2315 and "Save list to attribute file" on page 2325), e.g. in order to read it in again
    later (see "Preparing survey sample data" on page 2051).
    Example of a log file
    $VISION
    * VisumInst
    * 06.03.08, 18.27.29
    *
    *
    * Plausibilization of survey data:
    * Origin zone 1(3): Data record 1 processed.
    * Origin zone 2(3): Data record 2 processed.
    * Origin zone 2(3): Data record 3 processed.
    * Origin zone 2(3): Data record 4 processed.
    * Origin zone 2(3): Data record 5 processed.

    19.3.4

    Overall
    Overall
    Overall
    Overall
    Overall

    path
    path
    path
    path
    path

    status:
    status:
    status:
    status:
    status:

    1
    1
    1
    1
    1

    Assignment of survey data


    Direct assignment means assignment of a demand segments plausible paths to the network
    (see Fundamentals: Chpt. 7.12.5 , page 540).
    1. Import the desired survey data (see "Read survey data" on page 2055).
    2. Start plausibilization of the survey data (see "Plausibilization of survey data" on page 2059)
    3. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    4. In the PuT settings section, adjust the desired settings.
    5. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    6. Add the procedure Direct assignment, of the PuT Passenger surveys category, to the
    desired position in the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).
    7. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select demand segment window opens.
    8. Select the desired demand segment.
    9. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    10. Select the operation added. Then in the Operations section, click the Edit button.
    PTVGROUP

    2071

    19.3.4.1 Parameters of direct assignment


    The Parameters: Direct assignment window opens.
    11. Make the desired settings (see "Parameters of direct assignment" on page 2072).
    12. Confirm with OK.
    13. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The survey data is directly assigned according to the specified order of procedures
    Note: You can show the results in a table or diagram, or use them for further evaluations
    (see "Displaying data graphically and in lists" on page 2299 and "Settings for interactive
    analyses" on page 2265).
    19.3.4.1

    Parameters of direct assignment


    Direct assignment:Basis tab
    Element

    Description

    Recalculate
    demand
    matrix

    If this option has been checked, the demand matrix of the selected
    demand segment is recalculated. If the demand segment is not connected to a demand matrix (see "Connecting demand matrices and demand
    segments" on page 1607), a new demand matrix is automatically created.
    Note
    The demand matrix data result from the path volumes read from file with
    the survey data records (Num Pass). In the survey data file, a projection
    factor (ExtProjFactor) can be entered by data record. The values are multiplied when being read from file. In this way, passenger weighting performed outside of Visum can be regarded for the direct assignment.

    Calculate
    If this option is selected, the skim matrices selected in the Skim matrices
    skim matrices tab are calculated (see "Settings for PuT skim matrix calculation" on page
    2078).
    Note
    You cannot calculate the following skims because the direct assignment
    does not store the required parameters for calculation.
    perceived journey time, impedance und utility
    extended transfer waiting time
    adaptation time and extended adaptation time
    equivalent journey time
    service frequency
    number of operator changes

    2072

    PTVGROUP

    19.4 Calculating PuT skims


    Element

    Description

    Zone selection Origin zones


    Via these entries you may restrict the calculation to the demand of the
    selected origin zones. Thus only the selected rows of the demand matrix
    will be assigned.
    Note
    If both entry fields are empty, Visum will assign the entire demand matrix.
    If only a single zone number is entered, Visum will use this value as the
    upper or lower limit respectively (half-open interval).
    Analyzed OD pairs
    Use this list box to restrict the amount of analyzed OD pairs to active OD
    pairs, active origin zones, or pairs of active zones only.
    Note
    The options Origin zones and Analyzed OD pairs can be combined.
    Assignment
    time interval

    Via the entry fields you specify the assignment time interval.
    Notes
    The direct assignment regards only paths with departure time within the
    assignment time interval. The departure time of a path indicates that
    moment in time when the passenger starts walking from his origin to the
    public transport stop.
    If a calendar is used, you need to select a weekday or a date (see "Selecting a calendar " on page 1511).

    Direct assignment: Skim matrices tab


    You only have to set parameters for skim matrix calculation, if you want to calculate an assignment and skim matrices simultaneously (see "Settings for PuT skim matrix calculation" on
    page 2078).
    Note: To have skim matrices calculated, in the Basis tab, select Calculate skim matrices.

    19.4

    Calculating PuT skims


    For skim data calculation, you need to make specific settings. You can then start skim matrix
    calculation either during an assignment or as a separate procedure step (see Fundamentals:
    Chpt. 7.4 , page 456).
    Specific skims are provided by assignment procedure. Select the desired skims from the list of
    available skims.
    After the calculation, the skims are provided as skim matrices in the Matrices window.
    Note: Depending on the size of the network the computing time for skim calculation increases and the files may become very large.

    PTVGROUP

    2073

    19.4.1 Setting parameters for PuT skim matrices

    19.4.1

    Setting parameters for PuT skim matrices


    Note: Here, only the PuT-specific settings for skim matrices are described. You must also
    set global parameters for skim matrices (see "Setting metadata for skim matrices" on
    page 1865).
    For skim data output regarding public transport you may select a unit for length data, a unit for
    time data and a unit for impedance data.
    With the headway-based assignment or the timetable-based assignment you can return any
    direct or indirect time profile attribute as skim Path leg attribute. Specify the time profile attributes you would like to aggregate and the aggregate method. This way, a path attribute is
    determined from the attribute values of all path legs used by a time profile. If a path does not
    use any PuT lines, the result of this path is = zero, so that the path does not enter the weighting
    of all path values for a relation-based skim value.
    Note: The skim Path leg attribute is not issued in PuT path lists.
    The skim Discomfort due to capacity overload measures the time the passenger spends
    standing in the vehicle. The skim is calculated based on a formula that you can change (see
    Fundamentals: Chpt. 7.4.1.6 , page 460). Due to capacity overload the skim is only calculated
    with a timetable-based assignment. The following prerequisites need to be fulfilled:
    The paths are saved as connections.
    The volumes of the demand segments for which discomfort is to be calculated are not
    saved to another demand segment.
    To all OD pairs, demand > 0 applies.
    1. From the Calculate menu, choose General procedure settings.
    The General procedure settings window opens.
    2. In the navigator, select PuT settings> Skims.

    2074

    PTVGROUP

    19.4.1 Setting parameters for PuT skim matrices

    Note: In the skim table, you can make additional settings (see "Setting metadata for
    skim matrices" on page 1865).
    3. In the Units for skim matrices section, select the desired options.
    Element

    Description

    Lengths

    Unit for storing all skims of the Length data type, it is also used for skims of
    the Speed data type.
    Select either Kilometers/Miles (long length) or Meters/Feet (short
    length).
    Note
    Whether metric or imperial units are provided depends on the current settings made under Network> Network parameters> Units tab (see
    "Undoing and redoing actions" on page 870).

    Time

    Unit for storing all skims of the Time/Duration data type, it is also used for
    skims of the Speed data type.
    Select either Minutes or Seconds.

    Impedance

    Select Minutes or Seconds as unit for the skim impedance

    PTVGROUP

    2075

    19.4.2 Calculating PuT skim matrices


    Note: Visum does not store the data type of the selected unit but just saves whether a
    short length (Meters or Feet) or a long length unit (Kilometers or Miles) has been set.
    When you load data, the unit set under Network> Network settings> Units tab is
    used. The values are re-calculated, if applicable.
    4. Next to Path leg attribute, click the Parameters button.
    The Skim 'Path leg attribute' window opens.
    5. Click the <Attribute> button.
    Note: The button is labeled with the currently selected attribute.
    The Attributes (Time profiles) window opens.
    6. Select the desired attribute (see "The window used for the selection of one attribute" on
    page 963).
    7. Confirm with OK.
    8. In the Aggregate function selection list, select the desired entry.
    Element

    Description

    Avg

    Mean value of all attribute values

    AvgActive

    Mean value of all attribute values of active time profiles

    Max

    Maximum of all attribute values

    MaxActive

    Maximum of all attribute values of active time profiles

    Min

    Minimum of all attribute values

    MinActive

    Minimum of all attribute values of active time profiles

    Sum

    Sum of all attribute values

    SumActive

    Sum of all attribute values of active time profiles

    9. Confirm with OK.


    10. Next to Discomfort, click the Parameters button.
    The Skim Discomfort window opens.
    11. Enter the required parameter values.
    Note: The values need to be 0.
    12. Confirm with OK.
    The parameters for the PuT skim calculation have been set.

    19.4.2

    Calculating PuT skim matrices


    Note: For PuT skim matrix calculation, demand data is not required.

    2076

    PTVGROUP

    19.4.2 Calculating PuT skim matrices


    1. For each skim matrix, specify the desired settings (see "Setting metadata for skim matrices"
    on page 1865).
    2. Make sure your settings for the PuT skim matrices are correct (see "Setting parameters for
    PuT skim matrices" on page 2074).
    3. From the Calculate menu, choose Procedure sequence.
    The Procedure sequence window opens.
    4. Add the Calculate PuT skim matrix procedure of the Matrices category to the position of
    your choice within the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).
    5. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select Demand segments window opens.
    6. Select the desired entries.
    7. Confirm with OK.
    The window closes. The selected demand segments are listed in the Reference object(s)
    column.
    8. In the row of the added procedure, click in the Variant/file column.
    A selection list appears.
    9. In the drop-down list, select the desired entry.
    The selected entry is displayed in the column.
    10. Select the operation added. Then in the Operations section, click the Edit button.
    The Parameters for assignment procedure... window opens.
    11. If applicable, edit the desired settings in the Basis tab.
    Note: The settings in the Basis tab, in the Zone selection and Assignment time interval sections are relevant for skim matrix calculation (see "Timetable-based assignment:Basis tab" on page 2022).
    12. After selecting multiple demand segments, make sure that in the Demand segments tab,
    the assignment parameters set are correct (see "Timetable-based assignment:Demand segments tab" on page 2034).
    13. In the Skim matrices tab, make the desired settings (see "Settings for PuT skim matrix calculation" on page 2078).
    14. Click the OK button.
    The Parameters for assignment procedure window closes.
    15. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The skim matrices are calculated.
    PTVGROUP

    2077

    19.4.3 Calculating skim matrices during an assignment


    Note: You can then open and edit the skim matrices (see "Editing matrix values" on page
    1761).

    19.4.3

    Calculating skim matrices during an assignment


    1. Make sure your settings for the individual skim matrices are correct (see "Setting metadata
    for skim matrices" on page 1865).
    2. Make sure your settings for the PuT skim matrices are correct (see "Setting parameters for
    PuT skim matrices" on page 2074).
    3. Specify a procedure sequence including a PuT assignment (see "Selecting and executing
    a PuT assignment procedure" on page 2006).
    4. Make sure that option Calculate skim matrices has been checked in the Basis tab of the
    assignment parameters.
    Note: The settings in the Basis tab, in the Zone selection and Assignment time interval sections are relevant for skim matrix calculation (see "Timetable-based assignment:Basis tab" on page 2022).
    5. After selecting multiple demand segments, make sure that in the Demand segments tab,
    the assignment parameters set are correct (see "Timetable-based assignment:Demand segments tab" on page 2034).
    6. In the Skim matrices tab, make the desired settings (see "Settings for PuT skim matrix calculation" on page 2078).
    7. Click the Execute button.
    During the procedure sequence, the skim matrices are calculated according to the specified
    order simultaneously with the assignment.
    Note: You can then open and edit the skim matrices (see "Editing matrix values" on page
    1761).

    19.4.4

    Settings for PuT skim matrix calculation


    You may calculate skim matrices during an assignment (see "Setting and calculating PuT assignment parameters" on page 2006). The required parameters are provided in a separate tab.

    2078

    PTVGROUP

    19.4.4.1 PuT skim matrices:Aggregation section

    PuT skim matrices:Aggregation section


    PuT skim matrices:Analyzed OD pairs section
    PuT skim matrices:List of PuT skims
    PuT skim matrices:Settings for journey time equivalent
    PuT skim matrices:Output file section
    19.4.4.1

    PuT skim matrices:Aggregation section


    Note: This section is only provided if either the headway-based procedure has been
    selected or the timetable-based assignment.
    Here you select the function for skim calculation per OD pair of routes or connections (see Fundamentals: Chpt. 7.4.1.9 , page 465).

    PTVGROUP

    2079

    19.4.4.1 PuT skim matrices:Aggregation section

    2080

    Function

    Description

    Min. IMP route


    (headway-based)
    Min. PJT connection (timetablebased)

    If this function has been selected Visum will not return compiled data.
    In this case, Visum derives the skim values from the particular best
    route or connection respectively from the connection with the minimum PJT after timetable-based assignment or from the route with the
    minimum impedance after headway-based assignment respectively.
    Note
    The skim Discomfort due to capacity overload is only calculated with
    the aggregate function min. PJT connection, if the perceived journey
    time is saved (see "Settings for saving PuT assignment results" on
    page 1996).

    Avg value

    Mean value from the values of all routes or connections.


    Weighted by volumes
    If this option has been selected, the number of passengers is used for
    the weighting of connections when the mean value is calculated. We
    recommend to use this option.
    Notes
    Average values as statistical skims are more susceptible to outliers.
    The timetable-based assignment assumes a service frequency of 1 for
    each connection.
    If the Mean value function is used in combination with the proportional
    distribution of demand to the connectors option which can be selected
    via Basis tab > Use connector shares, then the option Weighted by
    volumes has to be checked. Otherwise an error will be returned.

    PTVGROUP

    19.4.4.1 PuT skim matrices:Aggregation section


    Function

    Description

    Mean value of
    routes with a low
    IMP (headwaybased)
    Mean value conn.
    with a low IMP
    (timetable-based)

    Mean value calculation over a lowest impedance share of the found


    routes or connections.
    IMP quantile
    Enter the percentage as value z. The connections are sorted by impedance, and the z% with the lowest impedance are used for the mean
    value computation.
    Weighted by volumes
    If this option has been checked, the sorted series of skim values does
    not contain a value per connection, but a value per passenger instead.
    We recommend to use this option.
    Notes
    Mean values of routes/connections with a low IMP also have the
    advantage that the leaps known from the skim quantiles do not occur.
    If value 0 is entered, for each skim the value of the connection with the
    lowest impedance is returned.
    When determining the quantile, no connection is excluded from the
    evaluation that has the same impedance as others which are also
    included.
    The skim Discomfort due to capacity overload is only calculated with
    the aggregate function Mean value conn. with a low IMP, if the perceived journey time is saved and the fares are saved by path (see "Settings for saving PuT assignment results" on page 1996).
    This function cannot be used in combination with the proportional distribution of demand to the connectors option which can be selected via
    Basis tab > Use connector shares.

    Quantile

    PTVGROUP

    With the help of quantiles you can visualize the distribution of skim
    values.
    Quantile
    Enter the percentage as value z. The quantile z is defined as the smallest number y, to which the following applies: y divides the classified
    series into two groups - one with a percentage of (at least) z% with
    values y, and the remainder with values > y. The 50% quantile is
    also called the Median.
    Examples: Quantiles of the values (1,2,2,3,5)
    The 50% quantile (i.e. the Median) equals 2, since 2 is the
    smallest number to which applies, that at least 50% of all
    values are smaller or equal.
    The 20% quantile equals 1, the 21% quantile yet 2 already.
    The latter is due to the fact that - to all numbers smaller than 2 applies that only 20% of all values are smaller or equal. Since,
    however, 21% are required, 2 is the first sought quantile.

    2081

    19.4.4.2 PuT skim matrices:Analyzed OD pairs section


    Function

    Description
    The 0% quantile equals 1, since there is no smaller value.
    Weighted by volumes
    If this option has been checked, the sorted series of skim values does
    not contain a value per connection, but a value per passenger instead.
    We recommend to use this option.
    Notes
    The parameter settings are regarded for all skims being calculated
    simultaneously. It is, in particular, not possible, to calculate different
    quantiles for different skims in one step. For a more detailed view of
    the distribution of skim values you can repeat the skim calculation
    several times with varying quantile settings.
    This aggregation function requires more calculation time and storage
    capacities.
    This function cannot be used in combination with the proportional distribution of demand to the connectors option which can be selected via
    Basis tab > Use connector shares.

    19.4.4.2

    PuT skim matrices:Analyzed OD pairs section


    Note: This section is only provided if either the headway-based procedure has been
    selected or the timetable-based assignment.
    With this selection list, the analyzed OD pairs can be reduced further.
    Element

    Description

    All

    If this option has been selected, all OD pairs are regarded.

    Only active
    OD pairs

    If this option has been checked, only active OD pairs are regarded.

    Only active
    origin zones

    If this option has been checked, only OD pairs with an active origin zone
    are regarded.

    Only pairs of
    active zones

    If this option has been checked, only OD pairs connecting active zones
    are regarded.

    Notes: For OD pairs that are not evaluated due to the current option setting, the skim
    matrix contains the value set for Ignored OD pairs (under Calculate menu> General procedure settings> PuT settings> Skims) (see "Setting metadata for skim matrices" on
    page 1865).
    The setting of the analyzed relations specified for the calculation of skim matrices can differ from the one set for the assignment.
    If a restricting zone interval has been set for assignment, this will reduce the number of
    analyzed OD pairs even more.

    2082

    PTVGROUP

    19.4.4.3 PuT skim matrices:List of PuT skims


    19.4.4.3

    PuT skim matrices:List of PuT skims


    Element

    Description

    List of skims

    Calculate
    If this option has been checked, the particular skim is calculated.
    Save to file
    If this option has been checked, the particular skim is saved as skim
    matrix file. Additional settings can be made in the Output file section (see
    "PuT skim matrices:Output file section" on page 2084).
    Notes
    Skim matrix files created with previous Visum versions have file extensions that differ by language. These may even have been replaced by
    user-defined file extensions.
    This option is grayed out as long as option Calculate is not selected.
    Open
    If this option has been checked, the particular skim matrix is opened in
    the matrix editor on screen right after the calculation.
    Note
    This option is grayed out as long as option Calculate is not selected.
    Tip
    Each of the columns mentioned above can be checked or unchecked
    completely as follows: In the column header, right click to call the context
    menu and click either Activate column or Deactivate column.
    Skim
    List of available skims (see Fundamentals: Chpt. 7.4.1.8 , page 464)

    Settings for
    journey time
    equivalent
    19.4.4.4

    If you selected the skim Equivalent journey time, you can click this button
    to edit the calculation formula (see "PuT skim matrices:Settings for journey time equivalent" on page 2083).

    PuT skim matrices:Settings for journey time equivalent

    PTVGROUP

    2083

    19.4.4.5 PuT skim matrices:Output file section

    Element

    Description

    Operator

    Addition or subtraction of the term

    Skim

    From the drop-down list, select a skim.

    Exp.

    Exponent of the skim value (also negative values permitted)

    Factor

    Factor the new value resulting from the skim value exponent is multiplied by.

    Min. value

    If the resulting term goes below the min. value, Visum will use the min. value
    instead.

    Max. value If the resulting term goes above the max. value, Visum will use the max.
    value instead.
    Example of the journey time equivalent calculation
    You would like to define the equivalent journey time as the sum of the journey time and of the
    origin wait time that depends on the service frequency.
    The assignment time interval (ATI) is 120 min.
    The origin wait time shall not exceed 10 min.
    The origin wait time results from the service frequency (SF) according to the formula
    =
    =
    (see "Parameters for origin wait time calculation" on page 2038)
    Thus, the origin wait times below result from various service frequencies (SF).
    SF= 1: Formula result = 16.4 min; Origin wait time = 10 min (due to maximum)
    SF= 3: Origin wait time = 9.5 min
    SF= 12: Origin wait time = 4.7 min
    19.4.4.5

    PuT skim matrices:Output file section


    Note: This section is only provided if you would like to save at least one skim matrix to
    file.

    2084

    PTVGROUP

    19.4.4.5 PuT skim matrices:Output file section


    Element

    Description

    File name
    button, you can enter or
    Name of the output skim matrix files. Via the
    select the file name (and path, if applicable) for the skim matrix file(s) without
    file extension(s).
    Notes
    If the file name is entered without path, then the file is stored in the pre-set
    project directory for matrices.
    Visum adds the file extension(s) according to the Format set for the matrix
    file(s) and the settings made under Calculate menu> General procedure
    settings > PuT settings> Skims (see "Setting metadata for skim matrices"
    on page 1865). For each skim that is to be saved to file, Visum creates a file
    with a skim-specific file extension which has been derived from the English
    abbreviation. If skim matrices are calculated for multiple demand segments
    during an assignment of multiple demand segments, the DSeg allocation is
    kept when being stored and also in the file names. To the user-defined file
    name, the DSeg code is added in all cases.
    Note
    Underneath the file name entry field, the corresponding extension is viewed
    as Example.
    Format

    In the list, click the format you want to save the matrices in (see "Data structures of matrices in Visum-specific text formats" on page 2679).
    Binary
    Format O (Text format)
    Format V (Text format)
    Part-V Format (Text format)
    CSV format (Text format)

    Separator

    Via the selection list you can select the separator to be used for saving the
    matrices in text format.
    Notes
    This selection list is only provided for output in CSV format.
    For all other formats, spaces are used as separators, so that the matrix can
    be edited in the matrix editor.
    Double-click a comma-separated matrix in *.csv format to open it as an Excel
    file. Matrices in *.csv format with a different decimal separator must be opened with the Excel Wizard.

    PTVGROUP

    2085

    19.5 Calculate service trip patterns


    Element

    Description

    Means of
    transport
    No.
    (VISEM)

    Number of the means of transport (for VISEM)


    1 = walk link
    2 = car passenger
    3 = PuT
    4 = car driver (including HGV) etc.

    Confirm
    If this option has been checked, a warning is displayed if matrices with
    overwriting identical names already exist. You may either confirm this message or cancel the data file output.
    If this option has not been checked, existing matrix files with identical
    names are overwritten without a warning.

    19.5

    Calculate service trip patterns


    You can calculate service trip patterns while the procedure sequence is carried out (see "Algorithm for service trip pattern calculation" on page 2088).
    A service trip pattern has to satisfy the following criteria:
    A service trip pattern can only be created based on a time profile (except for in the schematic line diagram).
    A service trip pattern consists of at least four vehicle journeys.
    The (possibly virtual) departures of vehicle journeys from the start stop point of the time
    profile have a recurring pattern that is less than four hours.
    Any other vehicle journey attributes are not relevant. Particularly, the following attributes are
    not considered when forming patterns:
    Vehicle journey sections of the vehicle journeys, i.e. the number of sections, their valid
    days, their vehicle combinations etc.
    Operators
    At no point the consistency of the attribute will be checked, i.e. the vehicle journeys of different
    time profiles may have the same service trip pattern number. Later in the timetable editor view,
    only vehicle journeys within one time profile will be grouped to patterns.
    Note: You may also calculate service trips groups in the timetable editor (see "Editing
    regular services" on page 1546), though this method is much more restrictive. For example, shorter vehicle journeys at the beginning or at the end of a day are not included in
    the timetable editor method.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the Calculate service trip patterns procedure of the PuT Analyses category to the
    position of your choice in the procedure sequence (see "Setting up and starting the procedure sequence" on page 1847).

    2086

    PTVGROUP

    19.5 Calculate service trip patterns


    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Parameters: Calculate service trip patterns window opens.
    4. Select the desired options.
    Element

    Description

    Calculate for
    active time profiles only

    If this option has been checked, only active time profiles are regarded for service trip pattern calculation.

    Calculate for
    If this option has been checked, only active vehicle journeys are
    active vehicle jour- regarded for service trip pattern calculation.
    neys only
    Take the spatial
    extent of vehicle
    journeys into
    account

    If the option has been selected, only vehicle journeys with identical start and end stops are put together in one regular service
    pattern.

    Maximize number
    of vehicle journeys in headway
    pattern

    If the option has been selected, the regular services with the maximum number of vehicle journeys are displayed as a headway patterns.

    Maximize temporal dimensions


    of headway patterns

    If this option has been selected, the regular services which span
    the longest period of time are displayed as headway patterns.

    PTVGROUP

    Notes
    Besides constant temporal distances of vehicle journeys changing headway patterns are also permitted. Each time difference
    may occur multiple times (for example, the headway pattern
    6/7/7).

    2087

    19.5 Calculate service trip patterns


    Element

    Description

    Identifying service
    trip patterns with
    any service interval

    Select this option to group vehicle journeys with the same differences into service trip patterns. The time differences may differ
    between trip patterns.
    Note
    This option is available, if the option Set coordinates of existing
    centroids is selected.

    Only fractured
    multiples of the
    base headway are
    permitted as service intervals for a
    service trip pattern

    Select this option to specify a base headway that limits the service trip patterns possible. The time difference between vehicle
    journeys of a service trip pattern must be a multiple of the base
    headway or a multiple of half, a third, or a quarter of the base
    headway. You can use this option to exclude specific unwanted
    headways.
    Example
    If you enter a base headway of 30 min, the following service trip
    patterns are possible:
    90 min is a multiple of 30/1
    45 min is a multiple of 30/2
    20 min is a multiple of 30/3
    22.5 min is a multiple of 30/4
    Note
    This option is available, if the option Set coordinates of existing
    centroids is selected.

    5. Confirm with OK.


    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The service trip patterns are computed. The results are saved to the vehicle journey attribute
    Service trip pattern number.
    Note: You can view the results in a list or in the timetable editor (see "Editing regular services" on page 1546). Subsequent processing and modification of service trip patterns is
    also possible (see "Editing regular services" on page 1546).
    Algorithm for service trip pattern calculation
    The algorithm considers the active vehicle journeys of each time profile separately since
    vehicle journeys of different time profiles cannot be combined.
    At the start the ServTripPatNo attribute of all vehicle journeys is reset to 0. Then the ServTripPatNo 1, 2, ... will be allocated successively to identified service trip patterns until all time
    profiles have been processed.
    The algorithm includes the following steps:

    2088

    PTVGROUP

    19.5 Calculate service trip patterns


    Note: If in the window Parameters: Calculate service trip patterns, you select Number
    of veh. journ., the algorithm is performed differently. The following section describes the
    difference.
    1. For all N vehicle journeys of a time profile the (possibly virtual) departures at the start of the
    time profile are determined.
    2. The vehicle journeys are sorted according to this departure time.
    3. The (maximum) m = N (N - 1) / 2 differences occurring between these departure times are
    determined. Generally m is much lower because the vehicle journeys already run in regular
    intervals. The set of M, resulting from the various differences, is sorted in ascending order.
    4. For each difference d in M it is checked which maximum service trip pattern G(d) can be formed from the available vehicle journeys with headway d. Maximum here means: covering
    the longest period, i.e. featuring the longest interval between first and last vehicle journey
    included.
    5. After determination - for each difference d - of the maximum service trip pattern G(d), the pattern g is selected from all patterns which covers the longest interval. In case several groups
    cover the same period of time, the group with the greatest number of vehicle journeys is
    selected.
    The second rule for example ensures that with perfectly regular vehicle journeys, running at
    a 1h interval between 6 a.m. and 10 p.m., a 1-hour frequency with 17 vehicle journeys (and
    not a 4-hour frequency with 5 vehicle journeys), is found.
    Should more than one headway be found covering the same (longest) period (1st) and
    same number of vehicle journeys (2nd) within a time profile, first the pattern with the earliest
    vehicle journey is formed.
    6. The vehicle journeys of the selected group receive the next free number as service trip pattern number. The vehicle journeys are then removed from the set of all vehicle journeys considered.
    7. This algorithm is applied repeatedly to the remaining vehicle journeys of a time profile until
    no further service trip pattern can be formed.
    If in the window Parameters: Calculate service trip patterns, you select Number of veh.
    journ., the algorithm is performed differently.
    1. For all N vehicle journeys of a time profile the (possibly virtual) departures at the start of the
    time profile are determined.
    2. The vehicle journeys are sorted according to this departure time.
    3. The (maximum) m = N (N - 1) / 2 differences occurring between these departure times are
    determined. Generally m is much lower because the vehicle journeys already run in regular
    intervals. The set of M, resulting from the various differences, is sorted in ascending order.
    4. For each difference d, starting with the smallest, it is checked whether there are groups with
    an overlapping time period, so that the differences of the first departures are added to the
    difference d. These are the combinations that are looked for.

    PTVGROUP

    2089

    19.5 Calculate service trip patterns


    5. From such possible group combinations, the one combination is chosen that represents the
    combined group with the most trips. These groups are combined.
    6. With the combination, redundant trips are again grouped into service trip patterns.
    7. These steps are repeated until no more groups can be combined.
    8. The vehicle journeys of the selected group receive the next free number as service trip pattern number. The vehicle journeys are then removed from the set of all vehicle journeys considered.
    9. This algorithm is applied repeatedly to the remaining vehicle journeys of a time profile until
    no further service trip pattern can be formed.

    2090

    PTVGROUP

    20 Settings for the PuT operator model

    20

    Settings for the PuT operator model


    The operator model is meant for evaluation of an existing public transport network.
    To minimize costs through efficient vehicle deployment, you can calculate line blocks and, if
    required, create a matrix of interlining trips based on a timetable (see Fundamentals: Chpt. 8.4
    , page 553). You can store various line block versions and may select - among these versions
    - the active line block version for further calculations.
    Using the PuT Operational indicators procedure, you can calculate multiple indicators of line
    performance, including revenues and vehicle costs for the overall network as well as for territories (see Fundamentals: Chpt. 8.6 , page 629).
    With the Line costing calculation add-on, you can also compute infrastructure costs and cost
    coverage.
    Subjects
    Calculating PuT line blocks
    Creating a cost model
    Calculating PuT operating indicators
    Revenue calculation using a fixed revenue per PTripUnlinked
    Revenue calculation using revenue per fare point
    Revenue calculation using the fare model

    20.1

    Calculating PuT line blocks


    Using different restrictions, you can determine the number of vehicles required to service a
    specific timetable (see Fundamentals: Chpt. 8.4 , page 553).
    Subjects
    Managing line block versions
    Managing line block item types
    Executing the PuT line blocking procedure
    Tabular output of line block results
    Displaying line blocks in the block view
    Editing block versions and line blocks
    Setting forced chainings
    Calculating skim matrices for interlining trips

    20.1.1

    Managing line block versions


    In Visum you can manage multiple line blocking results with the aid of line block versions (see
    Fundamentals: Chpt. 8.4.3 , page 568).

    20.1.1.1

    Creating a line block version


    1. In the Network menu, click the PuT block versions entry.
    The Line block versions window opens.

    PTVGROUP

    2091

    20.1.1.1 Creating a line block version

    Note: The list contains all existing line block versions with their general attributes.
    From the list, you cannot see whether line blocking has already been calculated for a
    line block version.
    2. Click the

    Create button.

    The Create block version window opens.


    3. Enter the desired data (see "Attributes of line block versions" on page 2093).
    4. Confirm with OK.
    Tip: Alternatively, you can create a new block version by copying an existing one (see
    "Copying line blocks or block versions" on page 2130).
    The block version is created and can be calculated (see "Executing the line blocking procedure" on page 2104).

    2092

    PTVGROUP

    20.1.1.2 Attributes of line block versions


    20.1.1.2

    Attributes of line block versions

    Note: During line blocking calculation for this line block version, these settings are
    accounted for in addition to the line blocking procedure parameter settings.
    Element

    Description

    Block version

    Number of the block version. The next free number is allocated automatically.

    Code

    Code of the block version

    Name

    Name of the block version

    PTVGROUP

    2093

    20.1.1.2 Attributes of line block versions


    Element

    Description

    Line blocking time In the selection list, you may select the time span for which line
    interval
    blocking is to be calculated. Line blocking regards all vehicle journey
    sections whose vehicle journey has at least one valid day within the
    line blocking time interval.
    Notes
    The default entry depends on the currently set calendar period.
    If the annual calendar has been selected, you can select the time
    span between the two dates (both dates included) forming the
    line blocking time interval.
    If the weekly calendar has been selected, you can select the time
    span between the two weekdays (both days included) forming
    the line blocking time interval.
    If no calendar is used, line blocking is performed for 24 hours.
    This block version
    If this option has been selected, the selected block version becobecomes the
    mes the active block version.
    active block verIf this option has not been selected, line blocking can be calsion
    culated, but the block version is not set active.
    Tip
    In the Line block versions window, you can also set a version active:
    Select the line block version and click the Active button.
    Block version:Interlining tab
    Element

    Description

    Interlining permissible

    If this option has been selected, also empty trips for vehicle combination transport between two vehicle journeys can occur in the line
    block.
    If this option is not selected, interlining is subject to a layover at
    the depot (see Fundamentals: Chpt. 8.4.1 , page 553).
    Tip
    For interlining trips between stop points, you can create interlining
    matrices (see "Creating a cost model" on page 2153).

    System routes

    2094

    Note
    This option is only relevant if option Interlining permissible has
    been selected.
    Do not use
    Routes traversing links and turns which are already open for the particular transport system are determined for interlining.
    Apply
    If this option has been selected, existing system routes are used for

    PTVGROUP

    20.1.1.2 Attributes of line block versions


    Element

    Description
    the generation of empty trips.
    Use exclusively
    If this option has been selected, existing system routes are used
    exclusively for the generation of empty trips.
    Create, if required
    If this option has been selected, existing system routes are used for
    the generation of empty trips. A shortest path search will be calculated if there is no matching system route. After successful shortest
    path calculation, a system route will be created from the calculated
    data.
    Note
    The name of this system route is derived from attributes of the block
    version. To choose them, go to Naming for generated system routes.
    Use only active system routes
    If the option has been selected, only active system routes will be
    used when using system routes for the generation of empty trips.
    If the option has not been selected, active and passive system routes are used.
    Note
    This option is only relevant, if one of these three options has been
    selected: Use system routes or Use system routes exclusively or
    Create, if required.

    Distance criterion In the drop-down list, you can select the link attribute which is to be
    (link attribute)
    regarded as best path search criterion, when interlining routes are
    calculated for empty trips between the last end stop point and the
    next start stop point.
    Select one of the following attributes:
    Length, t-PuTSys, AddValue1, AddValue2, AddValue3 and
    AddVal_TSys.
    Note
    This option is only relevant if option Interlining permissible has
    been selected.
    Naming of geneThe following components of names of the system routes to be generated system rou- rated can be selected and edited:
    tes
    Prefix
    Enter an arbitrary text
    Transport system
    Select a transport system attribute

    PTVGROUP

    2095

    20.1.1.2 Attributes of line block versions


    Element

    Description
    Start stop point
    Select a stop point attribute
    End stop point
    Select a stop point attribute
    Notes
    The following naming rules are effective if there is no system route
    within the network yet with an identical transport system and course:
    A generated system route could, for example, result in the following name, if all four elements are selected: Sys_T_20_40.
    In order to avoid that identical names are assigned to different
    system routes that are generated at the same time, a number is
    attached to the end of the name in case a combination already
    exists. The numbering begins with 1, for example Sys_B_20_
    40_1.
    Existing system routes can be overridden or updated when given a
    new name:
    A system route with an identical transport system and course will
    be overridden, if its name is identical to the components listed
    above. If the system route data of a network is supposed to be
    updated only, the same parameters as for the existing system
    routes thus need to be entered in the window.
    If you want to prevent that existing system routes are overwritten,
    you need to specify a new combination of name components. No
    existing system routes will then be found in the network. All
    objects are then created in addition to the existing system routes.

    Block version:Layover times tab

    2096

    Element

    Description

    Regard Pre and


    Post preparation
    times

    If this option has been selected, the pre and post preparation times
    by vehicle journey section are regarded for line blocking.
    Tip
    If for vehicle journey sections, you want to take user-defined time
    span values into account, instead of pre- and post-preparation times,
    also select Short turning permitted (see "Managing vehicle journeys
    and vehicle journey sections" on page 1531).

    Always permit the


    transition between
    the sections of a
    vehicle journey

    If this option has been checked, the transition between the sections
    of a vehicle journey is always permitted. Neither pre nor post preparation times are regarded in this case.
    Notes
    This option is only relevant if option Regard Pre and Post pre-

    PTVGROUP

    20.1.1.3 Editing a block version


    Element

    Description
    paration times has been selected.

    Short turning permitted

    If this option has been selected, short turnings are also permitted for
    line blocking. In this case, the layover time may differ from the vehicle
    journey sections pre and post preparation times.
    Notes
    This option is only relevant if option Regard Pre and Post preparation times has been selected.
    The short turning data are stored as values of the attributes that have
    been selected for the maximum dwell time and the reduced pre and
    post preparation times.
    If the selected attributes are not of the data type duration, values will
    be read as seconds.

    Reduced pre-preparation time

    Via the button you can select the numerical vehicle journey section
    attribute that stores the reduced preparation time to be regarded for
    line blocking.

    Reduced post-pre- Via the button you can select the numerical vehicle journey section
    paration time
    attribute that stores the reduced postpreparation time to be regarded
    for line blocking.
    Maximum dwell
    time

    Via the button you can select the numerical stop point attribute that
    stores the maximum dwell time between arrival and departure of two
    consecutive vehicle journeys to be regarded for line blocking.

    Note: If you have created user-defined attributes for block versions, these are shown in
    the User-defined attr. tab (see User Manual: Chpt. 15.2.6 , page 973).
    20.1.1.3

    Editing a block version


    1. In the Network menu, click the PuT block versions entry.
    The Line block versions window opens.
    2. In the list, click the block version of your choice.
    The line block version is highlighted.
    3. Click the

    Edit button.

    The Edit block version window opens.


    Tip: Alternatively, you can right-click a block version in the navigator of the block view
    and select the Edit block version entry.
    4. Make the desired changes (see "Attributes of line block versions" on page 2093).
    5. Confirm with OK.
    PTVGROUP

    2097

    20.1.1.4 Checking the coverage


    The new attribute values are stored.
    Note: If you have already carried out line blocking for this block version, the results are
    not adjusted automatically by this change. You have to rerun the line blocking procedure,
    if required (see "Executing the line blocking procedure" on page 2104).
    20.1.1.4

    Checking the coverage


    After line blocking is completed, you can verify whether all vehicle journey sections of the
    selected block version are covered by block items of this block version (see Fundamentals:
    Chpt. 8.4.3.10 , page 585).
    1. In the Network menu, click the PuT block versions entry.
    The Line block versions window opens.
    2. In the list, click the block version of your choice.
    The line block version is highlighted.
    3. In the Coverage column, click the Check button.
    The Coverage check window opens.

    4. Make the desired changes.


    Element

    Description

    Block version

    Number and code of the selected block version

    Check only active


    If the option has been selected, the coverage is only checked
    vehicle journey
    for active vehicle journey sections.
    sections
    If the option has not been selected, the coverage is checked
    for all vehicle journey sections.
    Check time slice

    2098

    You can select a time period for which the coverage shall be
    checked.
    Analysis period
    If the option has been selected, the coverage is checked for the
    set analysis period.
    Line blocking time interval

    PTVGROUP

    20.1.1.5 Performing the line block check


    Element

    Description
    If the option is selected, coverage is checked for the line blocking
    time interval of the block version (see "Attributes of line block versions" on page 2093).
    Different time slice
    If the option has been selected, you can specify the coverage
    check for a time period within the calendar period.
    Note
    The option is only relevant, if you use a calendar.

    5. Click the Check button.


    The coverage is checked. A message appears on the screen.
    Note: The message files is saved as a Messages.txt file (see "Using protocol files" on
    page 876).
    20.1.1.5

    Performing the line block check


    Once line blocking is completed, you can perform a line block check for the line block version
    (see Fundamentals: Chpt. 8.4.3.9 , page 582). Here, two methods are provided. Alternatively
    to the usual line block check, you can also select the forced block check.
    1. In the Network menu, click the PuT block versions entry.
    The Line block versions window opens.
    2. In the list, click the block version of your choice.
    The line block version is highlighted.
    3. In the Line blocks column, click the Check button.
    Tip: Alternatively, you can right-click a block version in the navigator of the block view
    or in the block view and select the Check line block or Check line blocks entry.
    The Block check window opens.

    4. Make the desired changes.


    Note: The settings displayed here are the same as those of the block version. As a
    rule, you should not change them.
    PTVGROUP

    2099

    20.1.1.5 Performing the line block check

    Element

    Description

    Forced block
    check

    If this option has been selected, the forced block check is performed. It becomes necessary when, through additional network
    changes, inconsistencies arise between the network basis and
    line blocks that cannot be found through a normal line block
    check (see Fundamentals: Chpt. 8.4.3.9 , page 582).

    Create empty
    trips

    If this option is selected, the block version may also include interlining trips between stop points (see Fundamentals: Chpt. 8.4.3.6
    , page 578).

    System routes

    Note
    This option is only relevant if option Create empty trips has been
    selected.
    Do not use
    Routes traversing links and turns which are already open for the
    particular transport system are determined for interlining.
    Apply
    If this option has been selected, existing system routes are used
    for the generation of empty trips.
    Use exclusively
    If this option has been selected, existing system routes are used
    exclusively for the generation of empty trips.
    Create, if required
    If this option has been selected, existing system routes are used
    for the generation of empty trips. A shortest path search will be calculated if there is no matching system route. After successful shortest path calculation, a system route will be created from the
    calculated data.
    Tip
    If you use system routes, you can refine them further with the
    option Use only active system routes.

    2100

    PTVGROUP

    20.1.1.6 Selecting the active line block version


    Element

    Description

    Use only active


    system routes

    If the option has been selected, only active system routes will
    be used when using system routes for the generation of empty
    trips.
    If the option has not been selected, active and passive system
    routes are used.
    Note
    This option is only relevant if in the System routes list, you selected Use, Use exclusively or Create if required.

    Distance criterion In the drop-down list, you can select the link attribute which is to
    (link attribute)
    be regarded as best path search criterion, when interlining routes
    are calculated for empty trips between the last end stop point and
    the next start stop point.
    Note
    This option is only relevant if option Create empty trips has been
    selected.
    5. Click the Check button.
    The line block check is performed. A message appears on the screen. Line blocks with faults
    are indicated through the fault flags (see Fundamentals: Chpt. 8.4.3.9 , page 582).
    20.1.1.6

    Selecting the active line block version


    You can set a block version active. The active block version is used to calculate the PuT operating indicators (see "Calculating PuT operating indicators" on page 2156).
    1. In the Network menu, click the PuT block versions entry.
    The Line block versions window opens.
    2. In the list, click the block version of your choice.
    The line block version is highlighted.
    3. Click the Set active button.
    The selected block version turns into the active block version. In the Active column, it is marked with an x.

    20.1.1.7

    Deleting a line block version


    1. In the Network menu, click the PuT block versions entry.
    The Line block versions window opens.
    2. In the list, click the block version of your choice.
    The line block version is highlighted.

    PTVGROUP

    2101

    20.1.2 Managing line block item types


    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the

    Delete button.

    Tip: Alternatively, you can right-click a block version in the navigator of the block view
    and select the Delete block version entry.
    The selected line block version is deleted.

    20.1.2

    Managing line block item types


    Besides the system types Vehicle journey, Empty trip, Layover time, and Depot, you can use
    additional block item types. During line blocking, the block item type is determined for each
    line block item (see Fundamentals: Chpt. 8.4.3.3 , page 573).

    20.1.2.1

    Creating a block item type


    1. In the Network menu, select the PuT block item types entry.
    The Block item types window opens.

    Note: The list contains all block item types. By default, the system-inherent types
    Vehicle journey, Empty trip, Layover and Layover time are stored. They are determined as system-inherent characteristics of the block item types and can be issued in
    the line blocks list. You may neither edit nor delete system-inherent types.
    2. Click the

    Create button.

    The new block item type is added to the list. The attribute values are preset with 0.
    Note: You can edit the properties of a user-defined block item type directly in the list
    (see "Editing a block item type" on page 2103).

    2102

    PTVGROUP

    20.1.2.2 Attributes of block item types


    20.1.2.2

    Attributes of block item types


    Element

    Description

    ID

    Number of the block item type The next free number is allocated automatically.
    Note
    By default, the numbers 1, 2, 3 and 4 are preset by the system.

    Name

    Name of the line block item type

    Default duration

    Period of time: default value for the time required by an item of this
    type

    Default length

    Long length: default value for the distance covered by an item of this
    type

    Time limit

    Period of time: limit for the time between two items of this block item
    type in minutes
    Note
    Value 0 = unlimited

    Length limit

    Long length: limit for the distance between two items of this block
    item type in km
    Note
    Value 0 = unlimited

    20.1.2.3

    Editing a block item type


    1. In the Network menu, select the PuT block item types entry.
    The Block item types window opens.
    2. In the list, select the particular cell in the row of the block item type you would like to edit.
    The attribute value is highlighted.
    Note: You cannot edit the attributes of a system type (ID 1 to 4).
    3. Overwrite the selected entry.
    The new attribute value is applied.

    20.1.2.4

    Deleting a block item type


    1. In the Network menu, select the PuT block item types entry.
    The Block item types window opens.
    2. In the list, click the block type item of your choice.
    The block item type is highlighted.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.

    PTVGROUP

    2103

    20.1.3 Executing the PuT line blocking procedure

    Note: You cannot delete a system type (ID 1 to 4).


    3. Click the

    Delete button.

    4. Confirm with OK.


    The selected block item type is deleted.

    20.1.3

    Executing the PuT line blocking procedure


    The objective of the line blocking is to determine the number of required vehicles for a given
    timetable and simultaneously minimize the resulting costs. You can perform line blocking with
    or without vehicle interchange:
    Line blocking without vehicle interchange always uses the vehicle combination specified
    (see Fundamentals: Chpt. 8.4.4 , page 585)..
    Line blocking with vehicle interchange is only available, if the Detailed line blocking addon is activated (see "Enabling or disabling installed add-ons" on page 886). This procedure allows for the following: For each vehicle journey section, you can choose the
    most suitable vehicle combination from the combinations saved to the attribute Vehicle
    combination set (see Fundamentals: Chpt. 8.4.5 , page 595).
    You can edit the attribute Vehicle combination set like any other input attribute of vehicle
    journey sections:
    in the tabular timetable (see "Editing a vehicle journey section" on page 1551 and
    "Editing the attribute values of all or all active vehicle journey sections" on page 1554)
    in the vehicle journey sections list
    via Multi-edit> Vehicle journey sections.
    For example, you can transfer the Vehicle combination set attribute data of the
    vehicle combinations to the respective attribute of the vehicle journey sections (see
    "Specifying a vehicle combination set" on page 1289).

    20.1.3.1

    Executing the line blocking procedure


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the Line blocking procedure of the PuT analyses category to the desired position in
    the procedure sequence (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select block version window opens.
    4. Select the desired block version.
    5. Confirm with OK.
    6. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.

    2104

    PTVGROUP

    20.1.3.2 Parameters of the line blocking procedure


    The Line blocking parameters window opens.
    7. Make the desired settings (see "Parameters of the line blocking procedure" on page 2105).
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The line block calculation is performed. Similar to assignments, the start time and end time of
    the procedure are logged to the log file. You can display and edit the results (see "Displaying
    line blocks in the block view" on page 2119 and "Editing block versions and line blocks" on
    page 2129). If required, you can perform a coverage or line block check (see "Checking the
    coverage" on page 2098 and "Performing the line block check" on page 2099).
    20.1.3.2

    Parameters of the line blocking procedure


    All parameters required for line blocking without vehicle interchange are also taken into
    account for line blocking with vehicle interchange. For line blocking with vehicle interchange,
    additional settings are required (see "Additional parameters for line blocking with vehicle interchange" on page 2114).
    Line blocking:Selecting a block version

    Element

    Description

    Block version

    In the drop-down list, you can select one of the line block versions of
    the network for line blocking calculation. The attributes Number and
    Code of the selected line block version are displayed (see "Attributes
    of line block versions" on page 2093).

    Line blocking time The attribute Line blocking time interval is displayed for the block

    PTVGROUP

    2105

    20.1.3.2 Parameters of the line blocking procedure


    Element

    Description

    interval

    version selected (see "Attributes of line block versions" on page


    2093).
    Note
    If the line blocking time interval differs from the analysis period, a warning will be displayed concerning potential subsequent PuT operational indicator calculations.

    Line blocking with If the option has not been selected, line blocking is calculated without
    vehicle intera vehicle interchange.
    change
    Notes
    This option is only available if the Detailed line blocking add-on is
    activated (see "Additional parameters for line blocking with vehicle
    interchange" on page 2114).
    If the option is selected, three more tabs are displayed that are only
    relevant for line blocking with vehicle interchange (see "Additional
    parameters for line blocking with vehicle interchange" on page
    2114).
    Note: Other properties of the selected block version are displayed in the tabs.
    Line blocking:Basis tab
    Element

    Description

    This block version If this option has been selected, the selected block version becomes
    becomes the
    the active block version.
    active block version
    Regard only
    If this option has been selected, only active vehicle journey sections
    active vehicle jour- are regarded for line blocking.
    ney sections
    Note
    Additionally, you can reduce the amount of vehicle journey sections
    to be regarded to just the unbound vehicle journey sections.

    2106

    PTVGROUP

    20.1.3.2 Parameters of the line blocking procedure


    Element

    Description

    Regard only
    unbound vehicle
    journey sections

    If this option has been selected, only unbound vehicle journey sections are regarded for line blocking.
    Note
    Additionally, you can reduce the amount of vehicle journey sections
    to be regarded to just the active vehicle journey sections.

    Take forced chai- Note


    nings into account This function is only available, if the Detailed line blocking add-on
    module is activated (see "Enabling or disabling installed add-ons" on
    page 886).
    If this option has not been selected, any existing forced chaining is
    ignored during line blocking. Vehicle journey sections which are linked by forced chainings are not regarded together but like separate
    activities.
    If this option has been selected, any existing forced chaining is
    ignored during line blocking. Vehicle journey sections linked by forced chainings are treated and planned as a single activity (see Fundamentals: Chpt. 8.4.3.8 , page 581).
    Line blocking:Properties of line blocks tab
    Note: Some of these settings are only provided, if the Detailed line blocking add-on is
    activated (see "Enabling or disabling installed add-ons" on page 886).

    PTVGROUP

    2107

    20.1.3.2 Parameters of the line blocking procedure


    Element

    Description

    Build closed
    blocks

    If this option has been, closed blocks are calculated.


    Note
    This option is only provided, if no annual calendar has been selected.

    Start and end only If this option has been selected, blocks start at a depot and end at a
    permitted in
    depot. Start depot and end depot do not need to be identical.
    depots
    Note
    This option is only provided, if option Build closed blocks has not
    been selected.
    To the block start, If this option is selected, you can choose a user-defined block item
    add element of
    type from the drop-down list (see "Creating a block item type" on
    type
    page 2102). As the first block item, an item of the select type is added
    to each open PuT line block.
    Note
    The option is only provided, if the Build closed blocks option has not
    been selected, and if at least one user-defined block item type has
    been defined.

    2108

    To the block end,


    add element of
    type

    If this option is selected, you can choose a user-defined block item


    type from the drop-down list (see "Creating a block item type" on
    page 2102). As the last block item, an item of the select type is added
    to each open PuT line block.
    Note
    The option is only provided, if the Build closed blocks option has not
    been selected, and if at least one user-defined block item type has
    been defined.

    Regard running
    direction

    If this option is selected, the orientation of the line blocks with the property Regard running direction will be checked at the end of the line
    blocking procedure:
    For closed line blocks, the check verifies whether the first vehicle
    journey block item always starts with the same orientation.
    For a line blocking time interval of more than one day the check
    additionally verifies whether the orientation is the same for each
    occurrence of the vehicle journey section.
    If one of these criteria is not satisfied, the status direction fault will be
    assigned to the line block.
    For line blocks generated by the line blocking procedure, the attribute
    Regard running direction is set = true.

    Secondary optimization criterion

    Via the options, you can influence the structure of transfers between
    vehicle journey sections in the line block (see Fundamentals: Chpt.
    8.4.4.4 , page 592).

    PTVGROUP

    20.1.3.2 Parameters of the line blocking procedure


    Element

    Description
    Differentiated duration of standstills
    The distribution of the standstill times is as irregular as possible, in
    other words, there are more short and long standstills than average
    standstill times. The aim of this is to obtain long standstills which can
    be used as maintenance time slots.
    Even duration of standstills
    The distribution of the standstill times is as even as possible. Such
    blocks are exceptionally resistant to disturbances.
    Line purity
    It is attempted to only run vehicle journeys of the same line in a block
    or to at least avoid line changes within a block as often as possible.
    No specific requirements
    In this dimension, no requirements are set concerning the result.
    Even line blocks
    Select this option, if you want Visum to try to calculate line blocks that
    are as similar as possible for each calendar day of the block time
    period. This makes it easier to perform line blocking in real operation.
    In addition, line block readability is improved.
    Note
    This option is only available, if your line blocking time interval is longer than a day.

    Duration of blocks If closed blocks are generated, you can use the options to influence
    (intended number the duration of the blocks (see Fundamentals: Chpt. 8.4.4.4 , page
    of block days)
    592).
    Note
    These options are not available, if in the Secondary optimization criterion section, Even line blocks is selected.
    Preferably, build long blocks
    Blocks have as many block days as possible. This means that the single vehicles traverse multiple line paths. In the most extreme case, all
    vehicle journeys of a partition are covered by a single line block.
    Preferably, build short blocks
    Line blocks have as few blocking days as possible.
    No specific requirements
    In this dimension, no requirements are set concerning the result.

    PTVGROUP

    2109

    20.1.3.2 Parameters of the line blocking procedure


    Line blocking:Interlining tab

    Note: In this tab, various settings of the block version are displayed (see "Attributes of line
    block versions" on page 2093).
    Line blocking:Layover times

    In the top section of the tab, various settings of the block version are displayed (see "Attributes
    of line block versions" on page 2093).

    2110

    PTVGROUP

    20.1.3.2 Parameters of the line blocking procedure


    In the Interpretation of pre and post preparation times section, you can make settings for the
    layover time. This allows you to save vehicle costs or change the timetable.
    Element

    Description

    Use pre and post


    If this option is selected, the layover time is used as specified for the
    preparation time as block version (see "Attributes of line block versions" on page 2093).
    specified
    Soft interpretation Select this option to make settings for the interpretation of the layover
    of pre and post pre- time.
    paration time
    Note
    This option is only available, if in the Layover times tab, you selected Regard Pre and Post preparation times (see "Attributes of line
    block versions" on page 2093).
    Allow negative
    layover time (timetable changes)

    Select this option to make settings for the interpretation of negative


    layover time.
    Note
    The entry of a negative layover time might lead to time faults during
    the block check (see Fundamentals: Chpt. 8.4.3.9 , page 582). You
    can avoid this problem by adapting the timetable or creating additional vehicle combinations.

    Minimum fixed layo- Only one of these options is available.


    ver time/Minimum Fixed part of minimum layover time in minutes that must not be fallen
    negative layover
    short of.
    time
    Note
    This option is only available, if in the Layover times tab, under attributes of the block version, Regard Pre and Post preparation times
    (see "Attributes of line block versions" on page 2093) and Soft interpretation of pre- and post-preparation times are selected.
    The share of the negative layover time that leads to a timetable
    change is indicated in minutes. The value is automatically given a
    minus sign.

    PTVGROUP

    2111

    20.1.3.2 Parameters of the line blocking procedure


    Element

    Description

    Variable portion in
    layover time

    Value indicates the variable part of the minimum layover time, by


    which the layover time can be shortened, if costs can be saved.
    Together, the fixed and variable parts form the minimum layover time.

    Save one vehicle


    combination if
    underrunning the
    minimum layover
    time by less than

    Indicates the shortening of the layover time with which one vehicle
    combination is no longer required.
    Example:
    The value 10 means it is more cost-efficient to accept a layover time
    fallen short of less than 10 minutes than to deploy an additional
    vehicle combination.
    A shortfall of exactly 10 minutes means the costs for the shortfall and
    the costs for an additional vehicle combination are the same.
    A shortfall of more than 10 minutes is only cost-efficient if more than
    one vehicle combination is no longer needed.
    Note
    A shortfall of layover time is penalized. The penalty costs can only be
    offset by vehicle cost savings. This is why there is only a shortfall of
    layover time, if the penalty costs can be offset by vehicle saving
    costs.

    Line blocking:Transport systems tab

    2112

    PTVGROUP

    20.1.3.2 Parameters of the line blocking procedure


    Element

    Description

    Same operator for


    next vehicle journey

    If this option has been selected, the succeeding trip can only be a
    vehicle journey which is run by the same operator.

    Same TSys for next If this option has been selected, the succeeding trip can only be a
    vehicle journey
    vehicle journey using the same transport system.
    Same line for next
    vehicle journey

    If this option has been selected, the succeeding trip can only be a
    vehicle journey of the same line.

    List

    The list contains all vehicle combinations of all possible combinations of the items operator, transport system, and line, depending on the options selected above.
    Empty trip TSys
    Use the drop-down list to select the empty trip transport system for
    the respective combination.
    Tip
    In the Use values from marked row for (identical) section, click the
    buttons to copy the setting of one row to another row.

    Use values from


    marked row for
    (identical)

    Use the buttons to copy the empty trip transport system selected in
    the Empty trip-TSys column of a marked row to other rows.
    All
    Use the button to copy the empty trip transport system to all rows.
    VehComb
    Use the button to copy the empty trip transport system to all rows
    with the same vehicle combination.
    Operator
    Use the button to copy the empty trip transport system to all rows
    with the same operator.
    TSys
    Use the button to copy the empty trip transport system to all rows
    with the same transport system.
    Line
    Use the button to copy the empty trip transport system to all rows
    with the same line.
    Note
    The buttons Line, TSys and Operator are only provided, if the particular option has been selected for the next vehicle journey.

    PTVGROUP

    2113

    20.1.3.3 Additional parameters for line blocking with vehicle interchange


    Line blocking:Cost tab

    20.1.3.3

    Element

    Description

    Costs of an
    activity

    In this list, you can enter the weight by cost component which shall be
    regarded during the cost calculation.

    Coefficient

    Weighting factor by cost component

    Attribute

    List of line block attributes, whose attribute value is regarded if the coefficient for the attribute is greater than 0.

    Cost rate

    Attribute values; each of them is multiplied with the particular coefficient


    and the line block attribute value.

    Value if no
    VehComb

    This user-defined value by cost component is used for vehicles for


    which no vehicle combination has been defined.

    Additional parameters for line blocking with vehicle interchange


    Note: You can only edit these three tabs, if the Detailed line blocking add-on is activated
    (see "Displaying details on program and license" on page 886).
    If the Line blocking with vehicle interchange option is selected (see "Line blocking:Selecting
    a block version" on page 2105), three more tabs are available in the Line blocking parameters window. The tabs contain parameters that are additionally taken into account:
    Line blocking with vehicle interchange:Parameters tab
    In this tab, you can specify a reference solution to be used and set further procedure parameters.

    2114

    PTVGROUP

    20.1.3.3 Additional parameters for line blocking with vehicle interchange

    Element

    Description

    Use reference soluIf the option has not been selected, a reference solution is used for
    tion
    the line blocking.
    If the option has been selected, you can select and use a block version of the network in the list as reference solution. The attributes
    Number and Code of the selected line block version are displayed
    (see "Attributes of line block versions" on page 2093).
    Note
    A block check is run for the reference version. If it does not contain a
    complete coverage of valid blocks, a warning is displayed and the
    procedure is terminated (see Fundamentals: Chpt. 8.4.5.3 , page
    599).
    Maximum number
    of iterations

    Line blocking terminates after the entered number of iterations.

    Number of iterations without


    improvement

    As convergence criterion, enter the number of iterations, after which


    the solution must be improved to iterate further.

    Number of solutions per iteration

    The higher the number of solutions which are determined per iteration, the higher the quality of the result to be expected.
    Note
    Both the time required for the calculation and the required memory
    capacity will increase in this case, however.

    Random seed

    In the case of otherwise unchanged settings, you determine a different result with a new starting value. With the same starting value
    and unchanged settings you can reproduce an existing result.

    PTVGROUP

    2115

    20.1.3.3 Additional parameters for line blocking with vehicle interchange

    Line blocking with vehicle interchange:Objective function tab


    In this tab, you determine the weight of each single component of the objective function (see
    Fundamentals: Chpt. 8.4.5.2 , page 597).

    Element

    Description

    Component

    In each row, this column contains a cost component of the objective


    function.

    Factor

    In this column, you can enter a factor for each component after double-clicking the respective row. This way, you specify the weight with
    which the component enters the objective function.

    Weight (%)

    This column outputs the automatically determined share of the total


    weight 100% for each user-defined factor.

    Line blocking with vehicle interchange:Settings for objective function components tab
    In this tab, you can specify the use of attributes.

    2116

    PTVGROUP

    20.1.3.3 Additional parameters for line blocking with vehicle interchange

    Element

    Description

    Attribute for numUse the button to select the vehicle units attribute which determines
    ber of vehicle units the number of vehicle units.
    Evaluate block day
    If this option has been selected, the regularity is evaluated based
    for the assessment on the block day.
    of the regularity
    If this option has not been selected, the regularity is evaluated
    based on the line block.
    Attribute for volume Use the button to select the vehicle journey items attribute which
    determines the volume.
    For dimensioning Select the desired option in case the volume of a vehicle journey secof the vehicle com- tion is higher than the capacity of the scheduled vehicle. This option
    bination use
    refers to the objective function component Consideration of volumes.
    Average volume
    If this option has been selected, the average capacity overload over
    all vehicle journey items of the section will be evaluated.
    Peak volume
    If this option has been selected, the peak capacity overload over all
    vehicle journey items of the section will be evaluated.

    PTVGROUP

    2117

    20.1.3.4 Initializing PuT line blocking

    20.1.3.4

    Element

    Description

    Vehicle capacity
    determination

    You specify how the vehicle capacity is included in the calculation.


    You can also specify not to account for the vol/cap ratio.
    Use total capacity
    Select this option for consistent use of the total capacity as capacity.
    Use the seat capacity
    Select this option for consistent use of the total seating capacity as
    capacity.
    Capacity switchover due to the attribute value
    Select this option to choose an attribute of vehicle journey items
    whose value indicates the criterion used to determine the capacity.
    For values greater than null, the total capacity is used.
    For values smaller than null, the seating capacity is used.
    With null, the capacity is not included.

    Attribute for destination vol/cap


    ratio factor

    Use the button to select the vehicle journeys attribute which determines the desired vol/cap ratio.

    Initializing PuT line blocking


    You can initialize a single block version or all block versions. This will discard the line blocking
    result calculated for the selected line block version.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the Init line blocking procedure of the PuT analyses category to the desired position in
    the procedure sequence (see "Setting up and starting the procedure sequence" on page
    1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Initializing line blocking window opens.
    4. Make the desired changes.
    Element

    Description

    Initialize all line


    block versions

    If this option has been selected, all line block versions are reset to
    the uncalculated state for which line blocking had been calculated.

    Block version

    From the selection list, select the block version for which the line
    blocking result is to be dismissed.

    5. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The line blocking results of the selected block versions are discarded.
    2118

    PTVGROUP

    20.1.4 Tabular output of line block results

    Note: Initializing a block version does not automatically delete this block version. You
    can recalculate an initialized block version, using modified properties or line blocking
    parameters, if applicable.

    20.1.4

    Tabular output of line block results


    You can display the line blocking results in lists in three different levels of detail (see "Opening
    a list" on page 2299):
    In the Block versions list, each row describes a block version.
    In the Line blocks list, each row describes a line block sorted by block version. Via a button in the toolbar, you can filter the list according to line block version.
    In the Block items list, each row describes a line block item of the line blocks calculated,
    differentiated by line block number and index number.
    Tips: You can synchronize the lists of line blocks and line block items with the Network
    editor window (see "Setting list options" on page 2306). Then network objects highlighted in the lists are also automatically highlighted in the Network editor window.
    You can change the layout of lists according to your needs and then output the data (see
    "Working with lists" on page 2299).

    20.1.5

    Displaying line blocks in the block view


    Line blocks can be displayed graphically in the block view. You can also edit the line blocks in
    this view (see "Editing block versions and line blocks" on page 2129).

    PTVGROUP

    2119

    20.1.5.1 Opening the block view


    Subjects
    Opening the block view
    Filtering displayed block items by a valid day
    Editing the time of the day change
    Displaying free actions in the block view
    Printing or exporting free actions
    Finding a block item in the block view
    Influencing program behavior when inserting block items
    Setting graphic parameters for the block view
    Printing or exporting the Block view
    20.1.5.1

    Opening the block view


    Line blocks can be displayed in a block view.
    1. In the Windows toolbar, click the

    Open timetable editor icon.

    Tip: Alternatively, from the Edit menu, choose Timetable editor.


    The Timetable editor window opens.
    2. Select the Block view PuT line blocks tab.
    3. If necessary, select a different valid day Basic filter in the drop-down list of the tool bar of
    the timetable editor.
    4. In the navigator, select the Line blocks tab.
    The navigator lists all block versions with their blocks.
    Note: Here, you can display the subordinated objects of an entry by clicking the
    respective plus icon.
    5. In the navigator, select the block version, vehicle combination and block, which you want to
    display in the timetable editor.
    Note: Alternatively, in the navigator, in the Lines tab, select lines (see "Selecting line
    (s) to be displayed in the Timetable editor" on page 1527). To adopt your selection
    into the Line blocks tab, from the shortcut menu, choose Transfer all objects to line
    block selection or Transfer visible objects to line block selection.
    The selected blocks are displayed in the Block view PuT line blocks tab.
    Tips: In the Block view, you can change the display similar as to in the Network editor
    window (see "Network editor window" on page 818). You can enlarge, reduce, or shift
    the window section via symbols in the toolbar, for example.
    You can hide or show the margins of the block view by selecting the Upper margin visible, Lower margin visible, Left margin visible , Right margin visible entries in the context menu.
    2120

    PTVGROUP

    20.1.5.2 Filtering displayed block items by a valid day


    20.1.5.2

    Filtering displayed block items by a valid day


    You can specify that only the block items of a specific valid day shall be displayed.
    In drop-down list of the tool bar in the Block view PuT line blocks tab, select the desired
    entry.
    The block view only displays the block items of the selected valid day.

    20.1.5.3

    Editing the time of the day change


    You can change the time for the day change of the block view.
    1. Right-click the Block view PuT line blocks tab.
    The shortcut menu opens.
    2. Click Parameters.
    Tip: Alternatively, from the Timetable editor menu, choose Parameters.
    The Parameters window opens.
    3. Select the Line block view tab.
    4. Make the desired changes.
    Element

    Description

    Time for day


    change

    This setting determines the time of the line break in the block
    view. If you set a time > 0:00, the blocks are shifted in the display.
    The operating days can be displayed in a position that differs from
    the calendar day.

    5. Confirm with OK.


    The changes are applied.
    20.1.5.4

    Displaying free actions in the block view


    1. Right-click the Block view PuT line blocks tab.
    The shortcut menu opens.
    2. Click Parameters.
    Tip: Alternatively, from the Timetable editor menu, choose Parameters.
    The Parameters window opens.
    3. Select the Line block view tab.
    4. Make the desired changes in the Free actions section.

    PTVGROUP

    2121

    20.1.5.4 Displaying free actions in the block view

    Element

    Description

    Show free actions If the option has been selected, free actions are displayed in the
    upper section of the Block view PuT line blocks tab.
    Notes
    A block is displayed whose validity is the section of the basic filter
    and the valid day of the vehicle journey section (after the shifting),
    i.e. exactly the shares which can be bound to one block item with
    start day in the basic filter. The date limit has the same effect as
    for bound actions.
    Use additional options to restrict the set of displayed vehicle journey sections further.
    Regard line filter

    If the option has been selected, only active vehicle journey sections will be displayed.

    Regard line selec- If the option has been selected, only vehicle journey sections of
    tion
    lines from the line selection are displayed.
    Predecessor / Suc- Show only predecessors / Show only successors
    cessor
    If one of the options (or both) have been selected and exactly one
    block has been marked, only those blocks are displayed from the
    set of blocks to be displayed according to the basic filter, line filter
    and option bound/unbound, whose departure occurs after the arrival of the marked block and whose start stop point (or start stop
    according to option Check stop (instead of stop point)) corresponds to the end stop point or end stop of the marked block or
    vice versa. The valid day of both blocks is not regarded for the
    selection. If a different block is marked in a line block, the display

    2122

    PTVGROUP

    20.1.5.5 Printing or exporting free actions


    Element

    Description
    is refreshed.

    Show only
    unbound actions

    If the option has been selected, only vehicle journey sections are
    displayed which are not included yet in a specific block version.
    Refers to line block
    Use the drop-down list to select the desired block version.

    Max. no. of displayed actions

    Specify the maximum number of free actions to be displayed.

    5. Confirm with OK.


    The free actions are displayed according to your settings.
    20.1.5.5

    Printing or exporting free actions


    Analogous to the Timetable editor, you can print or export free actions as a *.svg graphic file.
    You can scale the printout, only print the current display section, or print the entire display on
    multiple pages.
    1. To do so, make sure the free actions are displayed in the Block view (see "Displaying free
    actions in the block view" on page 2121).
    2. From the Timetable editor menu, choose Print free actions... or Export free actions....
    The Print: Timetable editor or the Save SVG file window opens.
    3. Make the further changes.
    SVG export (see "SVG export" on page 2656)
    Print (see "Starting print output" on page 2508)
    The display is saved to an *.svg file or printed.
    Note: Alternatively, right-click in the Block view PuT line blocks section. From the shortcut menu, choose the desired entry to print or export free actions.

    20.1.5.6

    Finding a block item in the block view


    The following section describes how to find all types of network objects (see "Finding network
    objects in the network" on page 999).

    20.1.5.7

    Influencing program behavior when inserting block items


    1. Right-click the Block view PuT line blocks tab.
    The context menu opens.
    2. Click Parameters.
    Tip: Alternatively, from the Timetable editor menu, choose Parameters.

    PTVGROUP

    2123

    20.1.5.8 Setting graphic parameters for the block view


    The Parameters window opens.
    3. Select the Line block view tab.
    4. Make the desired changes in the Line block items section.
    Element

    Description

    During creation,
    delete conflicting
    layover elements

    If the option has been selected, layover elements are deleted,


    if they are in a temporal conflict with elements that are newly inserted.
    If the option has not been selected, line blocks can be generated with multiple block items at the same time, because layover
    items outside of depots are not displayed.

    5. Confirm with OK.


    The settings are applied.
    20.1.5.8

    Setting graphic parameters for the block view


    Similar as for the network display, you can set the desired graphic parameters for the block
    view display of line blocks. The options largely correspond to the graphic parameters of the
    Tabular timetable and the Graphical timetable in the Timetable editor (see "Setting the
    graphic parameters of the graphical timetable" on page 1577).
    1. In the Timetable editor menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.

    2. In the navigator, select the respective entry under Line block view.
    2124

    PTVGROUP

    20.1.5.8 Setting graphic parameters for the block view


    The selected page opens.
    Tip: Alternatively, in the Block view, right-click a line block item. Then from the shortcut
    menu, choose Edit graphic parameters. The window then opens with the line block
    item's page.
    3. Make the desired changes.
    Tip: Click the Preview button to immediately show your changes without closing the
    Edit graphic parameters window.
    Font page
    Element

    Description

    Size

    Text size in mm

    Font

    You can specify the font and the style of the block labels in a separate window by clicking in the field.

    Color

    In a separate window, you can specify a color for the block labels by
    clicking in the field.

    Header data page


    Element

    Description

    Show header
    data

    If the option has been selected, the block header data are displayed in the block view with the selected attributes.
    If the option has not been selected, only the ID and the selected
    attribute of the block version as well as the ID and the selected attribute of the block are displayed in the display area of the block day of
    each valid day level.

    Display attributes

    For the output in the left column of the block header data, you can
    select a separate attribute for the block version, block, vehicle combination and the depot, which differs from the preset Standard
    labels.
    Note
    The other output values of the two block header data columns are
    determined automatically.

    Header data >


    Background
    page

    Here you can specify a uniform or a classified display for the background color of the block header data. These settings are the same
    as for the table background in the tabular timetable (see "Specifying
    the background of the table" on page 1574).
    Note
    A distinction between "Active/Passive/Marked" does not exist for header data.

    PTVGROUP

    2125

    20.1.5.8 Setting graphic parameters for the block view

    Vehicle journey page


    Element

    Description

    Labels of
    blocks

    For each labeling position at blocks that represent a vehicle journey,


    you can select an attribute that differs from the preset Standard
    labels. You may alternatively select No label.

    Classification
    as for route
    courses

    Generate
    Click this button to automatically classify the colors for active block
    items as for line route (see "Displaying route courses in the network
    window" on page 2387).
    Note
    You can view and edit the classification on page Vehicle journey>
    Block> Active.

    Vehicle journey Via the tabs Active (direction 'Up') and Active (direction 'Down')
    > Block page
    you specify the display of active vehicle journeys in either direction.
    You can select either uniform or classified display. If the Classified
    display option is selected, you can classify and display active vehicle
    journeys by an attribute (see "Displaying classified objects based on
    attribute values" on page 2411).
    In the Marked tab, you specify the display of marked vehicle journeys
    and in the Conflict tab, you specify the display of conflicting vehicle
    journeys. In each tab, you can select a specific Color for Filling and
    Margin. Here, classification is not provided.

    Empty trip page

    2126

    Element

    Description

    Labels of
    blocks

    For each label position at blocks that represent an empty trip, you
    can select an attribute that differs from the preset Standard labels.
    You may alternatively select No label.

    Empty trip >


    Block page

    Via the tabs Active (direction 'Up') and Active (direction 'Down')
    you specify the display of active empty trips in either direction. You
    can select either uniform or classified display. If the Classified display option is selected, you can classify and display active empty
    trips by an attribute (see "Displaying classified objects based on attribute values" on page 2411).
    In the Marked tab, you specify the display of marked empty trips. You
    can select a specific Color for Filling and Margin. Here, classification
    is not provided.

    PTVGROUP

    20.1.5.8 Setting graphic parameters for the block view


    Standstill in depot page
    Element

    Description

    Labels of
    blocks

    For each labeling position at blocks that represent a layover in depot,


    you can select an attribute that differs from the preset Standard
    labels. You may alternatively select No label.

    Layover in
    depot > Block
    page

    Via the tabs Active (direction 'Up') and Active (direction 'Down')
    you specify the display of active depot layovers in either direction.
    You can select either uniform or classified display. If the Classified
    display option is selected, you can classify and display active downtimes at depots by an attribute (see "Displaying classified objects
    based on attribute values" on page 2411).
    In the Marked tab, you specify the display of marked standstills in
    depots. You can select a specific Color for Filling and Margin. Here,
    classification is not provided.

    Pre-/Post-preparation time page


    Element

    Description

    Labels of
    blocks

    For each labeling position at blocks that represent the pre- and postpreparation time, you can select an attribute that differs from the preset Standard labels. You may alternatively select No label.

    Pre-/Post-pre- Via the tabs Active (direction 'Up') and Active (direction 'Down')
    paration time > you specify the display of active pre- and post-preparation time in eitBlock page
    her direction. You can select either uniform or classified display. If the
    Classified display option is selected, you can classify and display
    active pre-/post-preparation times by an attribute (see "Displaying
    classified objects based on attribute values" on page 2411).
    In the Marked tab, you specify the display of marked pre-/post-preparation times, and in the Conflict tab, you specify the display of conflicting pre-/post-preparation times. In each tab, you can select a
    specific Color for Filling and Margin. Here, classification is not provided.

    User-defined page
    Element

    Description

    Labels of
    blocks

    For each label position at blocks that represent a user-defined block


    item type, you can select an attribute that differs from the preset Standard labels. You may alternatively select No label.

    User-defined >
    Block page

    Via the tabs Active (direction 'Up') and Active (direction 'Down')
    you specify the display of active user-defined block item types in either direction. You can select either uniform or classified display. If the

    PTVGROUP

    2127

    20.1.5.8 Setting graphic parameters for the block view


    User-defined page
    Element

    Description
    Classified display option is selected, you can classify and display
    active user-defined block item types by an attribute (see "Displaying
    classified objects based on attribute values" on page 2411).
    In the Marked tab, you configure the display of marked user-defined
    block item types. You can select a specific Color for Filling and Margin. Here, classification is not provided.

    Free action page


    Element

    Description

    Labels of
    blocks

    For each label position at blocks that represent a free action, you can
    select an attribute that differs from the preset Standard labels. You
    may alternatively select No label.

    Classification
    as for route
    courses

    Generate
    Click this button to automatically classify the colors for active block
    items as for line route (see "Displaying route courses in the network
    window" on page 2387).

    Free action >


    Block page

    Via the tabs Active (direction 'Up') and Active (direction 'Down')
    you specify the display of active free actions in either direction. You
    can select either uniform or classified display. If the Classified display option is selected, you can classify and display the active free
    actions by an attribute (see "Displaying classified objects based on
    attribute values" on page 2411).
    In the Marked tab and in the Passive tab, you configure the display
    of marked or passive free actions. In each tab, you can select a specific Color for Filling and Margin. Here, classification is not provided.

    Free action >


    Pre-/Post-preparation time
    page

    Draw
    If the option has been selected, the pre-/post-preparation times of
    free actions are displayed. For the pre-/post-preparation times of free
    actions you can specify the Color for Filling and Margin.
    Show time labels of pre- and post-preparation times in minutes
    If the option has been selected, the time is output in min.
    If the option has not been selected, the format hh:mm:ss is used.

    2128

    PTVGROUP

    20.1.5.9 Printing or exporting the Block view


    Forced chainings page
    Element

    Description

    Invalid forced
    chainings

    Use the drop-down list to select the desired color for the display of
    invalid forced chainings.

    Valid forced chai- Use the drop-down list to select the desired color for the display of
    nings
    valid forced chainings.
    Implemented for- Use the drop-down list to select the desired color for the display of
    ced chainings
    implemented forced chainings.
    4. Confirm with OK.
    The settings are applied. The display in the Block view PuT line blocks is refreshed accordingly.
    Note: From the Timetable editor menu, choose > Reset graphic parameters to dismiss
    the current timetable graphic parameter settings and restore the default settings.
    You can save your graphic parameters for the timetable and read them in again later
    (see "Saving the graphic parameters of the timetable" on page 1599 and "Reading
    graphic parameters for the timetable" on page 1600).
    20.1.5.9

    Printing or exporting the Block view


    Analogous to the Timetable editor, you can print or export the Block view PuT line blocks as a
    *.svg graphic file. You can scale the printout, only print the current display section, or print the
    entire display on multiple pages.
    1. From the Timetable editor menu, choose Print line blocks... or Export line blocks....
    The Print: Timetable editor or the Save SVG file window opens.
    2. Make the further changes.
    SVG export (see "SVG export" on page 2656)
    Print (see "Starting print output" on page 2508)
    The display is saved to an *.svg file or printed.
    Note: Alternatively, right-click in the Block view PuT line blocks section. From the shortcut menu, select the entry of your choice.

    20.1.6

    Editing block versions and line blocks


    You can edit block versions and line blocks. From the block view, you can edit vehicle journeys and vehicle journey sections.

    20.1.6.1

    Marking items in the block view


    You can edit items in the block view, if you mark them beforehand.

    PTVGROUP

    2129

    20.1.6.2 Copying line blocks or block versions


    Selecting a single block
    If you want to select a single block, click the desired block with the left mouse button.
    The block is selected.

    Marking several blocks in any desired order


    Press the CTRL key and click the desired blocks with the left mouse button.
    The blocks are selected.
    Marking several consecutive blocks
    Select multiple adjacent blocks by clicking the desired block with the left mouse button,
    pressing the SHIFT key, and clicking the last block.
    The blocks are selected.
    Cancelling the selection of a block
    You can cancel the selection of a block by pressing the C TRL key and left-clicking the selected block.
    Cancelling the entire selection
    You can cancel the entire selection if you click next to the blocks anywhere in the display.
    Notes: Line blocks and block days are not marked directly but implicitly via the blocks
    contained therein.
    Actions that are applied to the marked blocks always refer to the calendar days / block
    items past this block.
    Block items on days which are not contained in the basic filter, can thus only be edited once the basic filter has been changed adequately.
    Basically, actions only apply to the respective first part of the day; this particularly prevents contradictions which would arise by dragging multiple parts of the day of the
    same block item to a target level. In particular, you cannot shift any part past midnight with the mouse. Its position is only determined by the first part of the day.
    20.1.6.2

    Copying line blocks or block versions


    You can copy line blocks to a different or a new block version. You can also copy an entire
    block version.
    Note: When copying line blocks, all block items are also copied.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the navigator, right-click a block version or a vehicle combination whose line blocks you
    want to copy entirely or in parts.

    2130

    PTVGROUP

    20.1.6.2 Copying line blocks or block versions


    Tip: You can also copy single line blocks, if you right-click a block in the Block view
    PuT blocks tab.
    The shortcut menu opens.
    3. In the context menu, select the Copy line block entry or the Copy line blocks entry.
    The Copy line blocks window opens.

    4. Make the desired changes.


    Element

    Description

    From version
    (source)

    Number and name of the block version of the selected line blocks

    Line blocking time Line blocking time interval of the block version of the selected line
    interval
    blocks
    Copy blocks

    List of all line blocks of the selected block version


    Here, you select all line blocks that you want to copy.

    In version (target) Use the drop-down list to select the block version in which you
    want to insert the selected line blocks.
    Note
    Select the New block version to create a new block version with
    the copied blocks. A new block version will be generated with the
    same data (apart from the ID) as the copied blocks. The new
    block version contains the copies of the line blocks with consecutively numbered IDs and the status information.
    If you copy line blocks to an existing block version, first, all block

    PTVGROUP

    2131

    20.1.6.3 Creating a line block


    Element

    Description
    items are deleted from the copy of the line blocks which fall on a
    calendar day which is not contained in the line blocking time interval of the target block version. Furthermore, all block items are
    deleted whose vehicle journey section for the calendar day is
    already bound to a different line block of the target version. The
    new line block gets the status unaudited.

    Line blocking time Line blocking time interval of the block version in which the line
    interval
    blocks shall be inserted
    Repeat the block
    items throughout
    the entire target
    line blocking time
    interval

    If this option is not selected, just the block items whose the
    calendar day lies within the line blocking time interval of the target block version will be copied. Thus, the copy serves the occurrences of vehicle journey sections which are in the target line
    blocking time interval and are served by the original line block.
    If this option is selected, copying means the following: Similar
    line block items (identical vehicle journey section, identical line
    block day) will additionally be generated for each calendar day,
    which satisfies either criterion: It differs from the original line block
    day by the length of the line blocking time interval of the original
    block version and the vehicle journey section is carried out on
    this day. Thus, the pattern of the original line block is propagated
    to the entire target line blocking time interval. Example: For an original block version with a line blocking time interval of one week
    this option will repeatedly copy the block items by week to the
    entire line blocking time interval of the target block version if the
    vehicle journey sections are carried out on these days.

    Double vehicle
    journey line block
    items

    Via the selection list you define how to handle two vehicle journey block items in the same time slot which might occur in a line
    block version as a result of copying.
    Delete out-dated line block item
    The block item in the new line block will be used, the one in the
    copied line block will be deleted.
    Do not paste new block item
    The block item in the copied line block is retained. This line block
    item is not copied.

    5. Confirm with OK.


    The selected line blocks are copied.
    20.1.6.3

    Creating a line block


    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).

    2132

    PTVGROUP

    20.1.6.4 Properties and options of line blocks


    2. In the navigator of the block view, right-click the block version or the vehicle combination for
    which you want to use the line block.
    The shortcut menu opens.
    3. Select the New line block entry.
    The Create line block window opens.
    4. Make the desired settings (see "Properties and options of line blocks " on page 2133).
    5. Confirm with OK.
    The new line block is inserted.
    20.1.6.4

    Properties and options of line blocks

    Element

    Description

    Block version

    Block version of the block

    Line blocking
    time interval

    Validity from - to of the displayed block version (date in case of an


    annual calendar, name of the respective weekday in case of a weekly
    calendar, "-" if no calendar is used)

    Number

    ID of the line block


    Determines the ID; may not collide with IDs of other line blocks of the
    same version.

    Code, Name

    Code and name of the line block

    PTVGROUP

    2133

    20.1.6.4 Properties and options of line blocks

    Basis tab
    Element

    Description

    Number of block
    days

    Number of block days

    Vehicle combination

    Select a vehicle combination from the list.

    Empty trip TSys

    Select an empty trip TSys from the list.

    Depot

    Select a depot via the ? button.

    Closed

    If this option has been selected, the line block is closed. In this case,
    after the last day of the line blocking time interval the first day will follow once again.

    Regard running
    direction

    If this option has been checked, the line block check will also
    include the line block's orientation:
    For closed line blocks, the check verifies whether the first
    vehicle journey block item always starts with the same orientation.
    For a line blocking time interval of more than one day the check
    additionally verifies whether the orientation is the same for each
    occurrence of the vehicle journey section.
    If this is not the case, the status direction fault will be assigned to the
    line block.

    Has vehicle interchange

    If this option has been selected, a vehicle interchange is permissible for this line block. In this case, the line block check will
    verify the vehicle combination of the line block and also for graphical
    display in the line block view it will be compared to the vehicle journey section attribute Vehicle combination set.
    If this option has been selected, the vehicle combination of the
    line block is compared to the vehicle journey section attribute
    Vehicle combination.
    Note
    This option is not checked if the line blocks has been created
    without vehicle interchange. This option is checked if the line blocks
    has been created with vehicle interchange.

    2134

    Status

    Output of the result of the status check, analogous to the display of


    the header data in the block view
    Click the Reset to unaudited button, to reset a checked block to the
    unchecked state.

    Operating-km

    Output of the covered operating kilometers

    Operating-km per
    day

    Output of the covered operating kilometers per day

    PTVGROUP

    20.1.6.5 Fixing a line block


    Basis tab

    20.1.6.5

    Element

    Description

    Service-km

    Output of the covered service kilometers

    Service-km per
    day

    Output of the covered service kilometers per day

    Service time

    Output of the covered service time

    Fixing a line block


    To fix a block item, you can automatically create a forced chaining from the block item to the
    successor within the line block.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view or in the navigator of the block view, right-click the desired line block or
    line blocks.
    The shortcut menu opens.
    3. Select the Fix line block command.
    A query opens.
    4. Confirm the query.
    The forced chainings are created and the line block is fixed.

    20.1.6.6

    Editing a line block


    You can display and edit header data and user-defined attributes of existing line blocks. The
    block version cannot be edited.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view or in the navigator, right-click the desired line block.
    The shortcut menu opens.
    3. In the context menu, select the Edit line block entry.
    The Edit line block window opens.
    4. Make the desired settings (see "Properties and options of line blocks " on page 2133).
    5. Confirm with OK.
    The changes are applied.
    Note: A change of the vehicle combination leads to a vehicle error if the status is not
    Unaudited. If you edit the number of block days, Unaudited will be output. If you decrease the number of block days and block items (apart from stand items) fall on the block
    days deleted in the process, the change is only made after confirming a prompt. The
    affected block items are deleted.

    PTVGROUP

    2135

    20.1.6.7 Resolving line blocks


    20.1.6.7

    Resolving line blocks


    You can solve one or multiple line blocks or all line blocks of a block version. The block items
    will be deleted but the line block itself will survive.
    Note: If you want to solve several line blocks at the same time, mark the desired line
    blocks beforehand.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view or in the navigator of the block view, right-click the desired line block or
    line blocks.
    The shortcut menu opens.
    3. In the context menu, select the Solve line block entry or the Solve line blocks entry.
    A query opens.
    4. Confirm the query with Yes.
    The line blocks are solved.

    20.1.6.8

    Deleting line blocks


    You can delete one or multiple line blocks or all line blocks of a block version.
    Note: If you want to delete several line blocks at the same time, mark the desired line
    blocks beforehand.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view or in the navigator of the block view, right-click the desired line block or
    line blocks.
    The shortcut menu opens.
    3. In the context menu, select the Delete line block entry or the Delete line blocks entry.
    A query opens.
    4. Confirm the query with Yes.
    The line blocks are deleted.

    20.1.6.9

    Creating a block day


    Note: If you want to create a block day for several line blocks at the same time, mark
    the desired line blocks beforehand.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).

    2136

    PTVGROUP

    20.1.6.10 Deleting a block day


    2. In the block view or in the navigator of the block view, right-click a line block or a block version.
    The shortcut menu opens.
    3. In the context menu, select the Create block day entry.
    The block day is created at the end of the line block.
    Inserting a block day in a specific position
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, click a block day.
    The shortcut menu opens.
    3. In the context menu, select the Create block day here entry.
    The block day is inserted behind the selected block day.
    20.1.6.10 Deleting a block day
    Note: If you want to delete several block days at the same time, mark the desired
    block days beforehand.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click a block day.
    The shortcut menu opens.
    3. In the context menu, select the Delete block day entry.
    The block day is deleted.
    20.1.6.11 Creating a user-defined block item
    You can create a block item with a user-defined block item type.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. Ensure that you have inserted a block item type (see "Creating a block item type" on page
    2102).
    3. In the line block view, right click the desired time on the desired blocking day.
    The shortcut menu opens.
    4. In the context menu, select the Create user-defined line block item entry.
    The Insert block item window opens.
    5. Make the desired settings (see "Editing a block item" on page 2138).
    6. Confirm with OK.
    PTVGROUP

    2137

    20.1.6.12 Editing a block item


    The block item is inserted.
    20.1.6.12 Editing a block item
    The window is used both to create new user-defined block items and to display and edit the
    header data of user-defined attributes of existing user-defined block items or system block
    items.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click the desired block item.
    The shortcut menu opens.
    3. In the context menu, select the Edit line block item entry.
    The Edit line block item window opens.

    4. Make the desired changes.


    General
    Element

    Description

    Block

    Output of ID and Code of the line block to which the item belongs

    Block day

    Number of the block day

    Block item type Output of the type

    2138

    PTVGROUP

    20.1.6.13 Shifting block items to different line block or block day


    General
    Element

    Description

    Line

    Output of the name of the line to which the item belongs

    Vehicle journey Output of the vehicle journey


    Section

    Output of the section

    Valid day

    Output of the valid day

    Basis tab
    Element

    Description

    Start at

    Time of the start of the block item

    In

    Start stop of the block item

    Duration

    Duration of the block item

    End at

    Time of the end of the block item

    In

    End stop of the block item

    Length

    Distance covered by the block item

    Is change of
    running direction

    If this option has been checked, the running direction is changed


    within this block item. This option is important for line blocking regarding changes to the running direction.

    Notes: In the Basis tab, the settings can only be edited for user-defined block items
    and empty trips.
    5. Confirm with OK.
    Your settings are saved.
    20.1.6.13 Shifting block items to different line block or block day
    You can shift bound actions to a different line block or block day. You can also shift free actions to a line block or block day. The time settings for start and end of the block item are retained.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. Make sure you have selected the desired option for shifting of block items (see "Influencing
    program behavior when inserting block items" on page 2123).
    3. In the block view, mark the desired line blocks.
    Note: To select free actions, you have to show them (see "Editing the time of the day
    change" on page 2121).
    4. Click one of the marked blocks and hold down the mouse button.

    PTVGROUP

    2139

    20.1.6.14 Inserting free actions into a line block


    5. With the mouse, drag the marked items to the desired block day.
    6. Release the mouse button.
    Note: Depending on the selected items, alerts and prompts may open.
    The block items are shifted.
    20.1.6.14 Inserting free actions into a line block
    You can insert free actions into a line block. To do this, you have to display the free actions. It
    is also useful to adjust the display settings to your requirements (see "Displaying free actions
    in the block view" on page 2121).
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. Make sure you have selected the desired option for shifting of block items (see "Influencing
    program behavior when inserting block items" on page 2123).
    3. In the block view, show the section with the free actions (see "Displaying free actions in the
    block view" on page 2121).
    4. In the block view, click an item of the block day in which you wan to insert the free actions.
    Tip: If in the section of the free actions, you only show predecessors and/or successors, when you select an item, the matching free actions are displayed (see "Displaying free actions in the block view" on page 2121).
    5. Mark the desired free actions.
    6. Right-click one of the marked free actions.
    The shortcut menu opens.
    7. Select the Include entry.
    Note: Depending on the selected items, alerts and prompts may open.
    The free actions are added to the line block. They are marked automatically.
    20.1.6.15 Shifting empty trips and user-defined block items to another time
    Within a line block day or valid day, you can shift empty trips and user-defined block items
    along the time axis.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. Make sure you have selected the desired option for shifting of block items (see "Influencing
    program behavior when inserting block items" on page 2123).
    3. In the block view, mark the desired line blocks.
    4. Click one of the marked blocks and hold down the mouse button.

    2140

    PTVGROUP

    20.1.6.16 Deleting block items


    5. With the mouse, drag the marked items to the desired time.
    Notes: Visum adds the items. The accuracy is 5 minutes. The time of the new position
    is displayed in the Quickinfo. For a more precise placing of the items, press the SHIFT
    key simultaneously.
    Drag the item to an existing block to place it subsequent to the existing block.
    6. Release the mouse button.
    The block items are shifted to the desired time. All other attribute values remain unchanged.
    20.1.6.16 Deleting block items
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, mark the desired block items.
    3. Press the DEL key.
    The block items are deleted.
    20.1.6.17 Editing vehicle journeys and vehicle journey sections
    Using the block view, you can edit vehicle journeys and vehicle journey sections of a block
    item.
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, mark the desired block item.
    3. Right-click the marked block item.
    The shortcut menu opens.
    4. Select either Edit vehicle journey or Edit vehicle journey section.
    The Edit vehicle journey or Edit vehicle journey section window opens.
    5. Make the desired changes.
    Edit vehicle journey (see "Editing vehicle journeys" on page 1541)
    Edit vehicle journey section (see "Editing a vehicle journey section" on page 1551)
    6. Confirm with OK.
    The vehicle journeys or vehicle journey sections are edited.
    20.1.6.18 Converting an empty trip into a vehicle journey
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click a block that represents an empty trip.
    The shortcut menu opens.

    PTVGROUP

    2141

    20.1.6.18 Converting an empty trip into a vehicle journey


    3. In the context menu, select the Convert into veh. journey entry.
    The Create veh. journey from empty trip window opens.

    4. Make the desired changes.


    Element

    Description

    EmptyTrip-TSys of Output of the name and code of the empty trip-TSys of the line
    line block
    block
    Vehicle comOutput of the vehicle combination of the line block
    bination of the line
    block
    Only show lines
    If the option has been selected, only lines are displayed that use
    with this Emptythe TSys of the empty trip.
    Trip transport system
    Line

    In the drop-down list, select a suitable line.

    Line route name

    Enter the name of the new line route.

    Direction

    In the drop-down list, select one of the two options.

    Time profile name Enter the time profile name for the new time profile.
    Vehicle journey
    number

    The vehicle journey number is suggested by the system and can


    be overwritten.

    Vehicle journey
    name

    Enter the name for the new vehicle journey.

    5. Confirm with OK.


    Note: If you use a weekly calendar or an annual calendar, another window opens in
    which you have to select the relevant valid days.
    Your settings are saved. The selected empty trip is converted into a new vehicle journey.

    2142

    PTVGROUP

    20.1.6.19 Shifting a standstill from/to depot


    20.1.6.19 Shifting a standstill from/to depot
    Shifting a standstill out of the depot
    You can shift block items of the type stand from inside a depot to outside a depot (see Fundamentals: Chpt. 8.4.3.5 , page 577).
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click a block item of type stand.
    The shortcut menu opens.
    3. Select the Shift standstill to outside of depot entry.
    Note: If the block item is interrupted by a day change, you can use the Shift an individual layover item to 'outside of depot' entry in the context menu to shift only one of
    the parts.
    The block item is hidden. The In depot property is deactivated.
    Note: If a stop point is no longer a depot due to changes to its property is depot, the property in depot will be disabled for the line block items of the type 'Layover' in there.
    Shifting a standstill into a depot
    You can shift block items of the type stand into a depot (see Fundamentals: Chpt. 8.4.3.5 ,
    page 577).
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click a hidden block item of type stand.
    The shortcut menu opens.
    3. Select the Shift standstill to inside of depot entry.
    Note: If the block item is interrupted by a day change, you can use the Shift an individual layover item to 'inside of depot' entry in the context menu to shift only one of
    the parts.
    The block item is shown. The In depot property is activated.
    Note: If a former depot is a regular stop point now, the line block items of the 'Layover'
    type in that depot lose their in depot property.

    PTVGROUP

    2143

    20.1.7 Setting forced chainings

    20.1.7

    Setting forced chainings


    Note: For the definition of forced chainings for line blocking, the Detailed line
    blocking add-on needs to be activated. The forced chainings can then be used in
    both line blocking procedures (see Fundamentals: Chpt. 8.4.3.8 , page 581).

    20.1.7.1

    Creating a forced chaining


    You can insert forced chainings between vehicle journey sections (see Fundamentals: Chpt.
    8.4.3.8 , page 581).
    Tip: In addition, you can insert forced chainings between all adjacent block items by
    fixing line blocks (see "Fixing a line block" on page 2135).
    Setting forced chainings between adjacent vehicle journey sections
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, mark adjacent vehicle journey sections.
    3. Right-click one of the marked vehicle journey sections.
    The shortcut menu opens.
    4. Select the Create forced chainings entry.
    The forced chaining is inserted. In the block view, the forced chaining is displayed as a double
    line between the vehicle journey sections.
    Setting forced chainings between any vehicle journey sections
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click the desired vehicle journey section.
    Tip: You can highlight the vehicle journey section in the lower section of the display,
    or in the upper section, which shows the free actions (see "Editing the time of the day
    change" on page 2121).
    The shortcut menu opens.
    3. Select the Edit forced chainings entry.
    The Edit forced chainings for vehicle journey section <...> window opens.
    Tips: Alternatively, you can open the window by right-clicking the desired vehicle journey and selecting the Edit forced chainings entry in the context menu.
    Via the icon
    Attribute selection, you can select the columns for display in the list.
    Columns returning calculated departure and arrival times and also the valid day
    column are always listed.
    4. Click the Define forced chaining button.

    2144

    PTVGROUP

    20.1.7.1 Creating a forced chaining


    The Edit forced chainings for vehicle journey section <...>: Set filter criteria window
    opens.
    Note: If a calendar is used (weekly/yearly), the Edit forced chainings for vehicle journey section <...>: Define the set of calendar days window appears: Specify the
    valid calendar days for the forced chainings (see "Weekly calendar" on page 1514
    and "Annual calendar" on page 1515).

    5. Make the desired changes.


    Element

    Description

    Show only useful


    destination
    vehicle journey
    sections

    If the option has been selected, only destination vehicle journey


    sections are displayed whose valid day and vehicle match.

    Show only free


    destination
    vehicle journey
    sections

    If the option has been selected, only destination vehicle journey


    sections are displayed which have no forced chaining yet.

    Regard line filter

    If the option has been selected, only vehicle journey sections of


    active lines are displayed.

    Regard line selec- If the option has been selected, only vehicle journey sections of
    tion
    lines of the current line selection are displayed in the timetable
    editor.
    Show only vehicle If the option has been selected, only vehicle journey sections are
    journey sections displayed that start at the end stop point of the selected vehicle

    PTVGROUP

    2145

    20.1.7.1 Creating a forced chaining


    Element

    Description

    that start at the


    end stop point

    journey section.

    Show only vehicle If the option has been selected, only vehicle journey sections are
    journey sections displayed that start at the end stop of the selected vehicle journey
    that start at the
    section.
    end stop
    6. Click the Next button.
    Your settings are saved. The Edit forced chainings for vehicle journey section <...>:
    Select destination vehicle journey section window opens.
    7. Select a suitable destination vehicle journey section.
    Tips: You can sort the list in ascending or in descending order by clicking the small triangle in the column header.
    Via the icon
    Attribute selection, you can select the columns for display in the list.
    Columns returning calculated departure and arrival times and also the valid day
    column are always listed.

    8. Click the Finish button.


    The forced chaining is inserted. The Edit forced chainings for vehicle journey section <...>
    window opens. It contains a new entry for the inserted forced chaining.

    2146

    PTVGROUP

    20.1.7.2 Editing forced chainings

    9. Confirm with OK.


    In the block view, the forced chaining is displayed as a double line between the vehicle journey sections.
    Adding the destination of a forced chaining
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right click the forced chaining you would like to add the destination for.
    A context menu opens.
    3. Click the Add destination of forced chaining entry.
    For each calendar day of the display level, a new line block item is created for the destination
    vehicle journey of the forced chaining on this day.
    20.1.7.2

    Editing forced chainings


    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click the desired vehicle journey section with forced chaining.
    The shortcut menu opens.
    3. Select the Edit forced chainings entry.
    The Edit forced chainings for vehicle journey section <...> window opens.
    Tips: Alternatively, you can open the window as follows: In the tabular timetable or in
    the graphical timetable, or in the list of vehicle journey sections, right-click the desired
    vehicle journey section and select the Edit forced chainings entry.
    Via the
    Attribute selection icon, you can select the columns for display in the list
    of forced chainings.
    4. In the list, select the desired forced chaining.
    5. Click the Define forced chaining button.

    PTVGROUP

    2147

    20.1.7.3 Deleting forced chainings


    6. Make the desired settings (see "Creating a forced chaining " on page 2144).
    The changes are applied.
    20.1.7.3

    Deleting forced chainings


    Deleting selected forced chainings
    1. Open the timetable editor and select the Block view PuT line blocks tab (see "Opening the
    block view" on page 2120).
    2. In the block view, right-click the desired block item with forced chaining.
    The shortcut menu opens.
    3. Select the Edit forced chainings entry.
    The Edit forced chainings for vehicle journey section <...> window opens.
    4. In the list, select the desired forced chainings.
    5. Click the Delete forced chaining button.
    6. Confirm with OK.
    The forced chainings are deleted.
    Deleting all or all invalid forced chainings
    1. In the Network window, right-click the Lines button.
    The Lines context menu opens.
    2. Select the Multi-edit> Vehicle journey sections entry.
    The Multi-edit vehicle journey sections window opens.
    Tip: If the network object type Lines has been selected, you can also call the Multiedit vehicle journey sections window via menu Edit> Multi-edit.
    3. Select the Special functions tab.
    4. In the drop-down list, select the entry Forced chainings.
    5. If applicable, check the option Delete only invalid forced chainings.
    6. Click the Delete forced chainings button.
    The forced chainings are deleted.

    20.1.8

    Calculating skim matrices for interlining trips


    You can generate skim matrices for interlining trips between all relevant stop points for a selected transport system (see Fundamentals: Chpt. 8.4.8 , page 604).

    20.1.8.1

    Performing the PuT interlining matrix procedure


    1. On the toolbar, click the

    2148

    Open 'Procedure sequence' window button.

    PTVGROUP

    20.1.8.2 Setting parameters for PuT interlining matrices


    The Procedure sequence window opens.
    2. Add the PuT interlining matrix procedure of the PuT analyses category to the desired position in the procedure sequence (see "Setting up and starting the procedure sequence" on
    page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Transport System selection window opens.
    4. Select the transport system you would like to create the interlining trip matrix for.
    5. Confirm with OK.
    The transport system appears in the column.
    6. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The PuT interlining matrix window opens.
    7. Make the desired settings (see "Setting parameters for PuT interlining matrices" on page
    2149).
    8. Confirm with OK.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The desired skim matrices for interlining trips of the selected transport system are created.
    20.1.8.2

    Setting parameters for PuT interlining matrices

    PTVGROUP

    2149

    20.1.8.2 Setting parameters for PuT interlining matrices


    General settings section
    Element

    Description

    Return only active


    stop points

    If this option has been selected, the dimensions of the output matrices are reduced to only active stop points.

    Return only terIf this option has been selected, the dimensions of the output matriminal stop points of ces are reduced to only those stop points that are either the start or
    the TSys
    the end of a vehicle journey section of the transport system.
    Use system routes If this option has been selected, the route choice will only find system routes.

    Route choice section


    Element

    Description

    Route search criterion

    In the drop-down list, you can select the route search criterion.
    The following criteria are provided.
    Time
    Path with shortest TSys travel time in network
    Distance
    Path with shortest TSys length in network
    AddValue 1, 2, 3
    Path with minimum AddValue total calculated from the traversed
    links
    AddVal_TSys
    Path with minimum TSys-AddValue total calculated from the traversed links

    Links/Turns have to If this option has been selected, the shortest paths found do not trabe permitted for
    verse links or turns or main turns that are not open to this transport
    TSys
    system.
    Note
    This option is only relevant, if option Use system routes has not
    been selected.

    2150

    PTVGROUP

    20.1.8.2 Setting parameters for PuT interlining matrices


    Skims section
    Element

    Description

    Calculate and save


    to file

    If the option has been selected, the respective skim matrix is calculated and, with the specific file extension, saved in the selected
    directory.
    Tip
    You can check or uncheck all rows in this column at once: In the
    column header, right click to call the context menu and click either
    Activate column or Deactivate column.

    Skim

    List of skims provided for interlining trips by transport system. Each


    output matrix stores the skim value of the best path per relation between selected stop points.
    t-PuTSys
    Total link run time of the transport system in [s]
    v-PuTSys
    Speed of the transport system in the network
    Distance
    Total length of the traversed links (in-vehicle distance)
    Direct distance
    Direct distance between the two stop points
    AddValue 1, 2, 3
    Total of the particular AddValue of the traversed links
    AddValue_TSys
    Total of the TSys-AddValue of the traversed links

    Ext.

    The skim-specific file extension is added automatically to the uniform matrix file name. It is used for the identification of the skim
    whose values are stored in the output matrix.
    Note
    Please note that renaming a file extension may cause identification
    problems, since the manual and PTV Vision Support refer to standard file extensions.

    Default

    Standard entry if no path can be found for a relation between stop


    points.

    Min. value

    Standard entry, if the calculated skim value goes below the Min.
    value for a relation between stop points

    Max. value

    Standard entry, if the calculated skim value exceeds the Max. value
    for a relation between stop points.

    Dec.

    Number of decimal places in the matrix

    Value for diagonal

    Standard value for the diagonal

    PTVGROUP

    2151

    20.1.8.3 Examples for PuT interlining matrices


    Output file section
    Element

    Description

    File name

    Via the
    button, you can enter or select the file name (and path, if
    applicable) for the matrices of interlining trips.
    Note
    The specific file extension is added automatically.

    Format

    In the list, click a format for output files (see "Matrix formats" on page
    2678).

    Confirm overwriting If this option has been selected, a query will appear if files with identical path and name shall be overwritten.
    20.1.8.3

    Examples for PuT interlining matrices


    Skim: Direct distance
    $VN
    *
    * PuT interlining matrix
    * Transport system B Bus
    * Direct distance
    * Only active stop points
    * VisumInst
    * 28.08.08
    * Number of stop points
    4
    *
    10
    20
    *
    * SP10
    0
    7071
    * SP20
    7071
    0
    * SP30
    14142
    7071
    * SP40
    15811
    10000

    30

    40

    14142

    15811

    7071

    10000

    7071

    7071

    30

    40

    Skim: Time-PuTSys
    $VN
    *
    * PuT interlining matrix
    * Transport system B Bus
    * t Time-PuTSys(s)
    * Only active stop points
    * VisumInst
    * 28.08.08
    * Number of stop points
    4
    *
    10
    20

    2152

    PTVGROUP

    20.2 Creating a cost model


    *
    * SP10
    0

    720

    1680

    1260

    720
    * SP30
    1920
    * SP40
    1260

    1200

    1980

    1200

    780

    1980

    780

    * SP20

    20.2

    Creating a cost model


    The reference time periods of the costs and revenues to be calculated must to be identical in
    order to obtain reasonable cost coverage results (see Fundamentals: Chpt. 8.6.5 , page 648).
    Costs are calculated based on the analysis period (see Fundamentals: Chpt. 8.6.6 , page
    649). The program distinguishes between vehicle-bound costs and infrastructure costs, which
    are calculated with the help of the PuT operating indicators procedure (see "Carrying out the
    procedure PuT operating indicators" on page 2156).
    The revenues are calculated based on the assignment time interval (see Fundamentals: Chpt.
    8.6.7 , page 659).
    The attribute OD trips total indicates the number of passenger trips in the assignment time interval; it thus varies according to the particular assignment time interval. This way, the revenues
    also vary according to the temporal position and length of the assignment time interval.
    Since the assignment time interval mostly covers just the peak hour, it is required to project
    this result to the entire analysis period.
    Following the projection, you can compute the cost coverage in your network model or, for
    example, combine indicator values calculated during assignment and indicators calculated by
    means of the PuT operating indicators procedure.

    20.2.1

    Infrastructure costs
    For each of the network object types Links , Operators and Stop points, three cost rates are
    saved that may flow into the infrastructure cost calculation (see "PuT operating indicators:Infrastructure cost tab" on page 2162).

    20.2.2

    Vehicle-bound costs
    For objects of the PuT line hierarchy, the vehicle costs consist of the sum of the cost rates per
    vehicle unit and the optional cost rate of the vehicle combination.
    We distinguish between cost per hour, cost per kilometer, cost per vehicle and cost per stopover (layover or depot).
    Vehicle costs (hourly cost, kilometer cost and fixed cost) depend on the vehicle type (for example standard or articulated bus or tram in single or multiple traction) and/or the operator (for
    example public or private bus operator).

    20.2.2.1

    Defining cost rates by vehicle unit


    Cost rates may be edited like any other attribute of the vehicle units.

    PTVGROUP

    2153

    20.2.2.2 Defining cost rates by vehicle combination


    From the Network menu, choose PuT vehicles > Vehicle units tab, for a selected
    vehicle unit in the Cost rates tab (see "Vehicle units: Cost rates tab" on page 1285).
    In the Vehicle units list for selected vehicle units (see "Opening a list" on page 2299 and
    "Editing the properties of objects in lists" on page 2321).

    20.2.2.2

    Element

    Description

    per hour

    Operating time-based cost for drivers and other personnel (for example train attendants), separately for service trips and empty trips

    per km

    Kilometer-based driving cost (fuel) or repair cost, separately for service trips and empty trips

    Per vehicle

    Fixed vehicle costs such as acquisition costs, subsidies, depreciation


    costs, and other costs (for example, insurance costs) per analysis
    period or analysis horizon

    Defining cost rates by vehicle combination


    Cost rates can be edited like any other attribute of vehicle combinations.
    From the Networkmenu, choose PuT vehicles > Vehicle combinations tab, for a selected vehicle combination in the Cost rates tab (see "Vehicle units: Cost rates tab" on page
    1285).
    In the navigator, via the Line blocking shortcut menu (see "Displaying line blocks in the
    block view" on page 2119 and "Vehicle units: Cost rates tab" on page 1285).
    In the Vehicle combinations list for selected vehicle combinations (see "Opening a list"
    on page 2299 and "Editing the properties of objects in lists" on page 2321).

    2154

    PTVGROUP

    20.2.2.3 Calculating vehicle-bound costs

    20.2.2.3

    Element

    Description

    Total costs per


    hour

    The total time-varying cost of a vehicle combination is the sum of all


    vehicle units plus hourly costs of the vehicle combination. The latter
    are specifically for service trips and empty trips and layover times.

    Total costs per km

    Similarly, the total distance-varying cost of a vehicle combination is


    the sum of all vehicle units plus kilometer costs of the vehicle combination. The latter are specifically for service trips and empty trips.

    Calculating vehicle-bound costs


    Vehicle costs are part of the operating costs (general) and are calculated with the help of the
    PuT operating indicators procedure (see "Carrying out the procedure PuT operating indicators" on page 2156). To take empty times and empty km into consideration, line blocking
    needs to be calculated.
    Once the cost rates have been entered, Visum automatically calculates the costs for vehicle
    use.
    Hourly costs = cost rate per hour operating time
    The operating time is calculated as follows.
    Service time (load time) for passenger transport. It can be taken from the timetable.
    Layover times for delay buffers, driver breaks or interlining. To determine the layover
    times, a line blocking calculation is required that considers the minimum layover times
    for driver breaks and interlining times as well as stand times at the end of a vehicle
    journey.
    Kilometer costs = cost rate per kilometer vehicle kilometers
    Vehicle kilometers are determined on the basis of vehicle journeys, interlining trips,
    pull-out and pull-in trips of a line.

    PTVGROUP

    2155

    20.3 Calculating PuT operating indicators


    Vehicle kilometers for passenger transport are calculated directly from the vehicle journeys in the timetable.
    The calculation of interlining kilometers requires a line blocking calculation.
    Vehicle costs = fixed costs number of vehicles
    Fixed costs increase with every additional vehicle required.
    The number of vehicles results from the number of required vehicle blocks.

    20.3

    Calculating PuT operating indicators


    PuT operating indicators can be calculated by territory or for other levels of detail (see Fundamentals: Chpt. 8.6 , page 629).
    The results of the procedure are listed under menu Lists > Territories > PuT detail.
    Notes: The PuT operating indicators are calculated for the block version currently active
    (see "Selecting the active line block version" on page 2101).
    In the directory ...\Program files\PTV Vision\PTV Visum 13\Doc\Eng of your Visum installation, you can find further information on indicators:
    The IndicatorSource.xls file specifies which indicators can be determined by which
    procedure.
    The IndicatorAvailability.xls indicates which indicators are output in which list type.

    20.3.1

    Carrying out the procedure PuT operating indicators


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the PuT operating indicators procedure of the PuT analyses category to the desired
    position in the procedure sequence (see "Setting up and starting the procedure sequence"
    on page 1847).
    3. Select the operation added. Then in the Operations section, click the Edit button.
    The PuT Operating Indicators: Parameters window opens.
    4. Check the settings and make the desired changes (see "Parameters for PuT operating indicators calculation" on page 2156).
    5. Click the OK button.
    The PuT Operating Indicators: Parameters window closes. The settings are applied.
    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    During the procedure sequence, the PuT operating indicators are calculated according to the
    specified order of procedures.

    20.3.2

    Parameters for PuT operating indicators calculation


    The procedure parameters are arranged by topic in various tabs.

    2156

    PTVGROUP

    20.3.2.1 PuT operating indicators:General tab


    Note: As soon as a key option has been selected in one of the tabs, the tab name is highlighted in red.
    20.3.2.1

    PuT operating indicators:General tab

    Element

    Description

    Calculate indicators for

    Select the desired level of detail for the indicators to be calculated. In


    addition to the data output by territory, various levels of the line hierarchy can be combined for the desired data output.
    Note
    If option x vehicle combination has been selected for assessment,
    revenues (and cost coverage) are calculated only if paths were
    saved as connections. If paths are saved as routes, revenues are distributed without taking the vehicle combinations into account.

    Store indicators
    also for vehicle
    journey items

    If this option has been selected, the indicators are additionally determined for the vehicle journey items and stored with the vehicle journey items.

    For indicators of
    If option Consider only active veh. journ. sections has been selectransport supply
    ted, the indicators are calculated without taking passive vehicle jourand infrastructure ney sections into consideration.
    cost
    20.3.2.2

    PuT operating indicators: Transport supply tab


    Transport supply indicators are always calculated for the network objects of the line and stop
    hierarchy. Additionally, you can calculate them for territories (see Fundamentals: Chpt. 8.6.3 ,
    page 639).
    As line costing is based on vehicle journeys, empty times and empty kilometers of a line block
    have to be allocated to the vehicle journeys served by the block. Based on this, costs can be

    PTVGROUP

    2157

    20.3.2.2 PuT operating indicators: Transport supply tab


    calculated by the PuT operating indicators procedure. Therefore, a line blocking result is required.
    Element

    Description

    Calculate also for


    territories

    If this option has been selected, the indicators are additionally calculated by territory.

    also calculate indi- If this option is selected, the indicators are also calculated by turns
    cators for turns
    and main turns.
    and main turns
    Calculate also indi- If this option is selected, the indicators of the Territory indicators procators of the 'Ter- cedure are also calculated (see "Calculating basic territory indiritory indicators'
    cators" on page 1885).
    procedure
    No empty time/no If this option has been selected, the properties of empty trips are ignoempty km
    red

    2158

    Empty time from


    pre- and post-preparation time of
    vehicle journey /
    no empty km

    If this option has been selected, the empty time is calculated as it


    used to be calculated in previous Visum versions.
    Empty time(vehicle journey) = pre preparation time + post preparation time

    From empty time/empty km of the


    line block weighted by vehicle journeys

    If this option has been selected, the empty times and empty kilometers of a line block are uniformly distributed to the vehicle journeys.
    Empty time(vehicle journey) = empty time(block) / num vehicle journeys(block)
    Empty km(vehicle journey) = empty km (block) / num vehicle journeys
    (block)

    From empty time/empty km of line


    block weighted by
    service time

    If this option has been selected, the empty times and empty km/mi of
    the line block are distributed to the vehicle journeys according to the
    service time.
    Empty time(vehicle journey) = empty time (block) service time
    (vehicle journey)/service time (block)
    Empty km(vehicle journey) = empty km(block) service km(vehicle
    journey)/service km(block)

    From empty time/empty km before


    + after vehicle
    journey

    Considering a user-defined share, the empty time of a vehicle journey results from the total empty time before and after the vehicle journey. The pull-out time is added to the first and the pull-in time is
    added to the last vehicle journey.
    Empty time(vehicle journey)= share empty time before vehicle journey + (1 - share) empty time after vehicle journey
    Empty km(vehicle journey)= share empty km before vehicle journey
    + (1 - share) empty km after vehicle journey

    Empty km(vehicle journey) = 0

    PTVGROUP

    20.3.2.3 PuT operating indicators:Network performance tab


    20.3.2.3

    PuT operating indicators:Network performance tab


    Network performance indicators are always calculated during assignment (see Fundamentals:
    Chpt. 8.6.4 , page 643). Additionally you can calculate them by territory.

    Element

    Description

    Calculate also for


    territories

    If this option has been checked, the indicators are additionally calculated by territory.

    Calculate indicators for

    The current selection is displayed. You can make changes in the


    Parameters: PuT operating indicators window (see "PuT operating
    indicators:General tab" on page 2157).

    Save volumes

    The current selection is displayed. To make changes, from the Calculate menu, choose General procedure settings> PuT settings>
    Assignment (see "Settings for saving PuT assignment results" on
    page 1996).

    Calculate for time The current selection is displayed. To make changes, from the
    intervals
    Calculatemenu, choose General procedure settings> PuT
    settings> Analysis time slots (see "Defining analysis time intervals" on page 1861).
    Save paths

    20.3.2.4

    The current selection is displayed. To make changes, from the Calculate menu, choose General procedure settings> PuT settings>
    Assignment (see "Settings for saving PuT assignment results" on
    page 1996).

    PuT operating indicators:Revenue tab


    The revenue indicators (see Fundamentals: Chpt. 8.6.5 , page 648) include the following indicators:
    Operating costs (see Fundamentals: Chpt. 8.6.6 , page 649) and
    revenues from fares and cost coverage (see Fundamentals: Chpt. 8.6.7 , page 659).

    PTVGROUP

    2159

    20.3.2.4 PuT operating indicators:Revenue tab


    Note: You can only calculate cost coverage if you have activated the Line costing calculation add-on (see "Enabling or disabling installed add-ons" on page 886).
    Cost coverage total = revenue total cost
    Cost coverage percent = (revenue total / cost) 100
    Cost coverage PTripUnlinked = cost coverage total PTripsUnlinked

    2160

    Element

    Description

    Calculate

    If this option has been selected, the indicators of the revenue calculation are computed.

    Calculate also for


    territories

    If this option has been selected, the indicators are additionally calculated by territory.

    Save only for


    active time profiles

    If this option has been selected, the revenue indicators are stored
    only for active time profiles.

    Revenue calculation method

    The current selection is displayed. To make changes, from the


    Calculatemenu, choose General procedure settings> PuT
    settings> Revenues, or from the Networkmenu, choose PuT
    fares (see "Selecting the revenue calculation method and the distribution method" on page 2161 and "PuT operating indicators:Infrastructure cost tab" on page 2162).

    Calculate indicators for

    The current selection is displayed. You can make changes in the


    Parameters: PuT operating indicators window (see "PuT operating
    indicators:General tab" on page 2157).

    Save paths

    The current selection is displayed. To make changes, from the Calculate menu, choose General procedure settings> PuT settings>
    Assignment (see "Settings for saving PuT assignment results" on
    page 1996).

    PTVGROUP

    20.3.2.4 PuT operating indicators:Revenue tab


    Selecting the revenue calculation method and the distribution method

    1. Make sure, that the input attributes required by this method have been set.
    2. Click menu Calculate> General procedure settings> PuT settings> Revenues and follow the steps outlined below:
    Select the appropriate revenue calculation method.
    Set the respective revenue calculation parameters (except for fare model).
    Change the settings accordingly for revenue distribution to path legs.
    Revenue calculation

    Revenue distribution (see Fundamentals: Chpt. 8.6.7.4


    , page 664)

    Revenue from fare model


    Additionally, the revenue distribution can be modified by
    (see "Revenue calculation using the following:
    the fare model" on page 2169)
    Fixed amount per path leg
    Weight by number of fare points
    Weight by number of path legs
    Distribute supplements to transport systems
    Fixed revenue per passenger
    Additionally, the revenue distribution can be modified by
    trip
    the following:
    (see "Revenue calculation using
    Fixed amount per path leg
    a fixed revenue per PTripUnWeight by number of fare points
    linked" on page 2167)
    Weight by number of path legs
    Revenue per fare point

    PTVGROUP

    Additionally, the revenue distribution can be modified by

    2161

    20.3.2.5 PuT operating indicators:Infrastructure cost tab


    Revenue calculation

    Revenue distribution (see Fundamentals: Chpt. 8.6.7.4


    , page 664)

    (see "Revenue calculation using the following:


    revenue per fare point" on page
    Fixed amount per path leg
    2167)
    Weight by number of fare points
    Weight by number of path legs
    20.3.2.5

    PuT operating indicators:Infrastructure cost tab


    Note: This tab is only displayed, if you have activated the Line costing calculation addon (see "Enabling or disabling installed add-ons" on page 886).

    2162

    Element

    Description

    Calculate

    If this option has been selected, selected cost values are calculated.

    Calculate also
    for territories

    If this option has been selected, the cost values are not only calculated
    on the level of detail selected in the General tab, but also by territory.

    Calculate
    Link cost
    Operator cost
    Stop point cost

    If this option has been selected for a network object type, these costs by
    network object type enter the infrastructure cost calculation.
    In the selection list, select this chosen network object type and set the
    parameters for the calculation of up to three cost values in the columns
    1, 2 and 3 for each of the chosen network object types.
    Note
    Stop point costs are defined by stop point and will be distributed evenly
    to the vehicle journeys, for which boarding or alighting is permissible at
    this stop point.

    Name

    User-defined cost name (optional)

    PTVGROUP

    20.3.2.5 PuT operating indicators:Infrastructure cost tab


    Element

    Description

    Cost type

    In the selection list, select a cost type.


    Depreciation cost
    Debt service for the annual cost of amortization and interest
    Running cost
    Maintenance and operating costs
    Utilization cost
    Fees for using the network object, for example track fees for links

    Depreciation
    period

    Depreciation time DT for depreciation costs


    Note
    This parameter is only provided for the cost type Depreciation cost.

    Interest rate

    Interest rate p for the depreciation cost


    Note
    This parameter is only provided for the cost type Depreciation cost.

    Time reference

    In the selection list, select the reference time period - either Analysis
    period or Analysis horizon - for running costs.
    Note
    This parameter is only provided for the cost type Running cost.

    Length reference

    PTVGROUP

    Only for links (see Fundamentals: Chpt. 8.6.6.2 , page 652)


    In the selection list, select the reference distance by cost type.
    Link length
    The link cost values refer to the total link length.
    Meter/Kilometers (or Feet/Miles respectively)
    The link cost values refer to 1 m/km (or ft/mi) of the total link length.
    In this case, the cost value of each cost type must be multiplied with the
    link length.

    2163

    20.3.2.5 PuT operating indicators:Infrastructure cost tab


    Element

    Description

    Regard:

    Only for stop points (see Fundamentals: Chpt. 8.6.6.3 , page 655)
    In the selection list, select the reference by cost type.
    all vehicle journeys
    The cost values are distributed to all vehicle journeys.
    Beginning+ending vehicle journeys
    The cost values are distributed to all vehicle journeys starting or terminating at the stop point.

    Weighting

    Only for operators (see Fundamentals: Chpt. 8.6.6.4 , page 656)


    For an operator, six indicators can be weighted by a factor prior to the
    distribution of the operator costs to the lines (or to other objects of the
    line hierarchy).
    Service kilometers
    Service time
    Seat kilometers
    Number of vehicle journeys
    Passenger kilometers
    Passenger trips unlinked
    For each indicator you can specify the distribution key in % to model the
    indicator's weight for the distribution of the operator costs.
    Note
    The total weighting must equal 100%.

    As a prerequisite, cost rates have to be defined for the network objects.


    Defining cost rates for stop points
    Cost rates can be edited like any other attribute of stop points:
    For a selected stop point in the Cost tab (see "Stop points: Cost tab" on page 1271)
    For multiple stop points in the Multi-edit stop points window
    In the Quick view window (see "Modifying attribute values in the Quick view" on page
    995)
    In the Stop points list (see "Editing the properties of objects in lists" on page 2321).
    Defining cost rates for links
    Cost rates by permitted public transport system can be edited like any other attribute of links:
    For a selected link in the PuT-Sys tab (see "Links: PuT TSys tab" on page 1109)
    For multiple links in the Multi-edit links window
    In the Quick view window (see "Modifying attribute values in the Quick view" on page
    995)
    In the Links list (see "Editing the properties of objects in lists" on page 2321).

    2164

    PTVGROUP

    20.3.2.6 PuT operating indicators: User-defined attributes tab


    Defining cost rates for operators
    Cost rates can be edited like any other attribute of operators:
    For a selected operator via menu Network> PuT operators in the Edit operator
    window> Basis tab (see "Editing the attribute values of operators" on page 1282)
    In the PuT operators list (see "Editing the properties of objects in lists" on page 2321).
    20.3.2.6

    PuT operating indicators: User-defined attributes tab


    You can project direct or indirect numerical attributes of vehicle journey sections - even userdefined attributes - to higher levels of the PuT line hierarchy.
    Element

    Description

    Calculate

    If this option has been selected, selected attributes of vehicle journey


    sections are projected to higher levels of the line hierarchy.

    Calculate also for


    territories

    If this option has been selected, additionally the indicators by territory


    are calculated for the level of detail selected in the General tab.

    Active

    If this option has been selected, the attribute value is projected with
    regard to the particular projection basis.

    Attribute

    Select a direct or indirect numerical vehicle journey section attribute,


    even user-defined attributes can be selected.

    Projection basis

    In the selection list, select the appropriate option for the particular
    attribute: it can be either a length-related attribute or a time-related
    attribute or it can refer to the entire vehicle journey section.

    Create

    Via this button you can add another row.

    Delete

    Via this button you can delete the selected row.

    Each vehicle journey section attribute selected for the projection of further attributes is calculated according to the following algorithm.
    For the network objects vehicle journey, time profile, line route, line, main line, TSys and territory PuT detail it is checked if there is a numeric, editable attribute featuring the same ID as
    the original attribute. If not, a user-defined attribute featuring that ID is generated automatically.
    Code and name, too, are adopted from the original attribute.
    For the network objects vehicle journey section, vehicle journey, time profile, line route, line,
    main line, TSys and territory PuT detail it is checked if there is a numeric, editable attribute featuring the same ID as the original attribute but suffixed by AH. If not, a user-defined attribute
    featuring that ID is generated automatically. Code and name will each be suffixed by AH.
    If the result attributes already exist, they will be set to zero.
    If the output attributes already exist but are neither numeric or nor editable, an error message
    is displayed and the calculation is not started. Unaffected hereof, the rest of the PuT operating
    indicators procedure will still be executed.

    PTVGROUP

    2165

    20.3.3 Discarding calculated PuT operating indicators


    For calculations on vehicle journey section level it is assumed that the original attribute contains a value related to AP.
    At the vehicle journey section the AH result attribute value is determined as follows:
    ValueAH = ValueAP ProjFactorTransportSupply
    Here, the projection factor specified for the valid day of the vehicle journey section is used for
    the transport supply.
    For calculations in the line hierarchy, the values of the original attribute are added up along
    the line hierarchy and allocated to the respective result attribute. The values of the AH output
    attribute of the vehicle journey section are equally added up and allocated to the AH output
    attribute at each level.
    To territory-based calculations the following applies:
    If the original attribute is a length-related attribute, the value of the vehicle journey section
    will be distributed first onto the traversed links in proportion to the line length. As usually,
    the link values are calculated for the territories, too. The value of a link is added to the
    share (link length in territory / link length) in the AP result attribute per object(s) of the line
    hierarchy x territory.
    If the original attribute is a time-related attribute, the value of the vehicle journey section is
    first distributed onto the traversed links in proportion to the run times of the time profile.
    Here, too, the link values are length-proportionally allocated to the territories (see above).
    If the original attribute is not length-related, its value will simply be added up for each traversed territory.
    The values calculated per vehicle journey section are each multiplied by the projection factor
    AH for the transport supply (see above) and then added up equally in the AH result attribute
    per object(s) of the line hierarchy x territory.
    If the Init PuT operating indicators procedure is executed, the user-defined attributes of the territory PuT detail network object, for example territory TSys vehicle combination, will be deleted. This is performed even if the line costing results are discarded for other reasons. The
    other output attributes are kept since they might have existed before. If necessary, they have to
    be deleted manually.

    20.3.3

    Discarding calculated PuT operating indicators


    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Add the Init PuT operating indicators procedure of the PuT analyses category to the desired position in the procedure sequence (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Init PuT operating indicators window opens.
    4. Make the desired changes.
    2166

    PTVGROUP

    20.4 Revenue calculation using a fixed revenue per PTripUnlinked

    Element

    Description

    Transport supply

    Use this option to discard the calculated transport supply indicators. Note
    If this option has been selected, you can also discard the transport supply indicators by territory.

    Infrastructure
    costs

    Use this option to discard the calculated infrastructure cost indicators.


    Note
    If this option has been selected, you can also discard the infrastructure cost indicators by territory.

    Revenue

    Use this option to dismiss the calculated revenue indicators.


    Note
    If this option has been selected, you can also discard the revenue
    indicators by territory.

    Network performance for territories

    Use this option to discard the network performance indicators calculated by territory.

    5. Confirm with OK.


    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The selected PuT operating indicators are deleted.

    20.4

    Revenue calculation using a fixed revenue per PTripUnlinked


    1. Click menu Calculate> General procedure settings> PuT settings> Revenues and follow the steps outlined below:
    Select the option Fix revenue per PTripUnlinked.
    Enter the revenue per unlinked passenger trip (see Fundamentals: Chpt. 8.6.7.1 ,
    page 660).
    Set the parameters for revenue distribution (see Fundamentals: Chpt. 8.6.7.4 , page
    664).
    2. Start the PuT operating indicators procedure (see "Calculating PuT operating indicators"
    on page 2156).

    20.5

    Revenue calculation using revenue per fare point


    Click menu Calculate> General procedure settings> PuT settings> Revenues and follow the steps outlined below:
    Select the option Revenue per fare point.
    Enter the revenue per fare point (see Fundamentals: Chpt. 8.6.7.2 , page 661).

    PTVGROUP

    2167

    20.5.1 Inserting fare points at network objects


    Set the parameters for revenue distribution (see Fundamentals: Chpt. 8.6.7.4 , page
    664).

    20.5.1

    Inserting fare points at network objects


    Fare points can be defined for two types of network objects:
    Input attributes Number of fare points, Number of fare points for boarding, Number of
    fare points for passing, Number of fare points for alighting for time profile items
    TSys-specific input attribute Number of fare points_TSys for links
    Notes: Additionally, the output attribute Number of link fare points is stored for time profile items. Its value complies with the total value of the link attribute Number of fare
    points_TSys for the transport system of the time profile's line summed up from the traversed sequence of links between this time profile item and the next one to be served by
    this time profile.
    If the time profile item is a stop point located on a link, only the traversed length portion of
    the link is regarded. Only the proportional value of the link attribute Number of fare
    points_TSys enters the value of the output attribute Number of link fare points.
    Based on a PuT assignment result, revenue calculation determines the number of traversed
    fare points by PuT path from the number of traversed link fare points by PuT path leg being
    summed by transport system and adds the number of fare points of traversed time profile
    items. The total number of traversed fare points of a passenger's journey is multiplied by the
    value of the parameter Revenue per fare point.

    20.5.1.1

    Defining fare points of links by transport system


    The attribute Number of fare points_TSys can be edited like any other attribute of links.
    Note: Fare points of links are taken into account by all PuT assignment procedures.
    For a selected link in the PuT-Sys tab (see "Links: PuT TSys tab" on page 1109)
    For multiple links in the Multi-edit links window
    In the Quick view window (see "Modifying attribute values in the Quick view" on page
    995)
    In the Links list (see "Editing the properties of objects in lists" on page 2321)

    20.5.1.2

    Defining fare points at time profile items


    You can edit the attributes Number of fare points, Number of fare points for boarding, Number of fare points for passing, Number of fare points for alighting like any other time profile
    item attribute:
    Note: The TSys-based assignment does not regard fare points of time profile items.
    For a selected time profile in the Edit line route window in the Items and time profiles tab
    (see "Line routes: Items and time profiles tab" on page 1313)
    For all or all active time profile items in the Multi-edit time profile items window.
    In the Time profile items list (see "Editing the properties of objects in lists" on page 2321)

    2168

    PTVGROUP

    20.6 Revenue calculation using the fare model

    20.6

    Revenue calculation using the fare model


    Similar to fare points, fare zones may serve for ticket type and fare definition.
    Notes: Fare points of traversed network objects are only relevant in the fare model, if - to
    at least one demand segment in the network - a distance-based ticket type has been allocated or if distance-based fare supplements shall be regarded for at least one transport
    system.
    In the fare model, fare zones are only relevant, if a ticket type with a zone-based fare or a
    From-To-zone-based fare is allocated to a demand segment.

    20.6.1

    Using fare points


    Fare points can be defined for two types of network objects (see "Inserting fare points at network objects" on page 2168):
    At time profile items
    At links by PuT-Sys
    In the fare model, fare points can be used to model distance-based fare components:
    For ticket types of the type distance-based fare
    Distance-based supplements for PuT-Sys

    20.6.2

    Using fare zones


    Fare zones are usually used to model zone-based fares (zone-based fare or a From-To-zonebased fare).

    20.6.2.1

    Defining fare zones


    1. In the Network menu, click the PuT fare zones entry.
    The Fare zones window opens.

    2. Click the

    Create button.

    The Create fare zone window opens.


    3. Make the desired settings (see "Properties and options of fare zones" on page 2170).

    PTVGROUP

    2169

    20.6.2.2 Properties and options of fare zones


    4. Confirm with OK.
    The fare zone is inserted.
    20.6.2.2

    Properties and options of fare zones

    The upper section of the Create fare zone or Edit fare zone window contains the general attributes of the fare zone. In the lower section, you can allocate stops or remove them from the
    allocation list.
    Element

    Description

    Number

    Number of the fare zone

    Type

    Fare zone type

    Code

    Code of the fare zone

    Name

    Name of the fare zone

    Stops

    In this section, you can allocate one or several stops to the fare zone.
    and
    buttons.
    Mark the desired stops and use the
    Tip
    To select multiple stops, press the C TRL key and keep it pressed
    while clicking the desired entries one by one.
    Note
    A stop can be allocated to more than one fare zone.

    2170

    All stops

    If this option has been selected, all stops are listed in the List of
    stops.
    Tip
    This way you can allocate a stop which is located directly on the
    boundaries of fare zones to several fare zones.

    Only free stops

    If this option has been selected, only those stops are listed in the List
    of stops that have not yet been allocated to a fare zone.

    PTVGROUP

    20.6.2.3 Editing attribute values of fare zones


    20.6.2.3

    Editing attribute values of fare zones


    1. In the Network menu, click the PuT fare zones entry.
    The Fare zones window opens.
    2. In the list, click the fare zone of your choice.
    3. Click the

    Edit button.

    The Edit fare zone window opens.


    4. Make the desired settings (see "Properties and options of fare zones" on page 2170).
    5. Confirm with OK.
    The fare zone is changed.
    20.6.2.4

    Deleting a fare zone


    1. In the Network menu, click the PuT fare zones entry.
    The Fare zones window opens.
    2. In the list, click the fare zone of your choice.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the

    Delete button.

    The fare zone is deleted.

    20.6.3

    Defining PuT fares


    For each fare system, you can specify ticket types and price arrangements and their allocation
    to the demand segments. Further general settings for the fare calculation are required.
    In the Network menu, click the PuT fares entry.
    The PuT fares window opens.

    PTVGROUP

    2171

    20.6.3.1 Defining fare systems


    The fare model is defined in the five tabs.
    20.6.3.1

    Defining fare systems


    1. In the Network menu, click the PuT fares entry.
    The PuT fares window opens.
    2. Select the Fare systems tab.
    The list of defined fare systems is displayed.
    3. Click the Create button.
    Another row is added to the list of fare systems.
    4. Make the desired changes.

    2172

    Element

    Description

    Number

    Number of the fare system

    Name

    Name of the fare system

    Rank

    Rank of the fare system. If multiple fare systems are available for
    a path, the fare is determined based on the fare system with the
    highest rank (see Fundamentals: Chpt. 8.5.3.1 , page 624).

    Fare weight for


    selection

    Fare system weight. If multiple fare systems of the same rank are
    available for a path, the path with the minimum fare will be used
    by default. This weight again can be applied to the fare. This way
    you can model that non-local incoming passengers usually go by
    train as long as possible, until they transfer to a local transport system, even if this is more expensive compared to the minimum fare
    (see Fundamentals: Chpt. 8.5.2.4 , page 623).

    Fare applies to

    Use the drop-down list to specify whether one or more ticket types
    must be purchased for a connection with multiple path legs (see
    Fundamentals: Chpt. 8.5.2.1 , page 620).
    Each group of contiguous path legs
    A ticket can be used for several successive path legs of a connection.
    All path legs together
    A ticket can be used for all path legs of a connection.
    Each path leg separately
    For each single path leg, a ticket must be purchased.
    Note
    Visum automatically uses this option, if in the procedure Headway-based PuT assignment, you use fares for impedance calculation (see ""Fare reference" of a fare system" on page 620 and
    "Headway-based assignment:Impedance tab" on page 2019)

    PTVGROUP

    20.6.3.2 Creating ticket types


    Element

    Description

    Initial fare

    Start fare for the ticket type (see Fundamentals: Chpt. 8.5.2.3 ,
    page 623)

    Lines

    Use the button to select for each fare system the lines which run
    within the fare system. For each line, the FareSystemSet column
    automatically refreshes the numbers of the fare systems to which
    they are allocated.

    Ticket types

    The column lists the numbers of ticket types that are valid for the
    fare system (see "Creating ticket types" on page 2173).

    5. Confirm with OK.


    The fare system is inserted.
    Editing a fare system
    1. Make sure that the Fare systems tab is open in the PuT fares window.
    2. In the list of the fare systems, click the cell that you want to edit.
    3. Make the desired changes.
    4. Confirm with OK.
    The changes are applied.
    Deleting fare systems
    1. Make sure that the Fare systems tab is open in the PuT fares window.
    2. In the list, click the fare system of your choice.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the Delete button.
    4. Confirm with OK.
    The fare system is deleted.
    20.6.3.2

    Creating ticket types


    1. In the Network menu, click the PuT fares entry.
    The PuT fares window opens.
    2. Select the Ticket types tab.
    The list of defined ticket types is displayed.
    3. Click the Create button.
    The Create ticket type window opens.

    PTVGROUP

    2173

    20.6.3.2 Creating ticket types

    4. Make the desired changes.


    Ticket type Basis tab

    2174

    Element

    Description

    Number

    Number of the ticket type

    Name

    Name of the ticket type

    Utility rate

    The utility rate of the ticket type indicates the average number of single trips of a season ticket within its validity period.

    Rank

    Rank of a ticket type in the hierarchy of the ticket types


    Note
    This setting is only relevant, if several ticket types are defined in the
    fare system. The lower the number, the higher the preference given
    to this ticket type per fare zone x demand segment (see Fundamentals: Chpt. 8.5.2.2 , page 622).

    Fare structure

    In the list with the four options of fare modeling, click the fare structure
    that is suitable for this ticket type (see Fundamentals: Chpt. 8.5.1.1 ,
    page 609):
    Zone-based fare
    Distance-based fare
    From-to-zone-based fare
    Short-distance fare

    Calculating
    distance-based
    supplements

    Use the list to specify how to calculate distance-based supplements


    of transport systems.
    Proportional
    The distance-based supplement of a transport system is determined
    on the basis of the sum of fare points for all TSys and then weighted
    with the share of the transport system on the path. The distancebased total supplement of the connection results from the sum of the
    supplements calculated by TSys.

    PTVGROUP

    20.6.3.2 Creating ticket types


    Element

    Description
    Supplement by TSys = number of fare points of TSys / total number of
    fare points for all TSys TSys supplement for total number of fare
    points
    Additionally
    The distance-based supplement of a transport system is determined
    on the basis of the number of fare points traversed with this TSys. The
    distance-based total supplement of the connection results from the
    sum of the supplements calculated by TSys.
    Supplement by TSys = TSys supplement for the number of fare points
    of TSys

    Fixed supplements

    Use the list to specify when to apply fixed supplements.


    Apply once per transport system
    For a connection, the fixed supplement for a transport system is applied once, even if the transport system is used on two separate path
    legs (default).
    Apply to the top-ranking transport system only
    For a connection, a fixed supplement is applied which is the supplement that has been set for the top-ranking transport system. The
    maximum of the supplements will be applied if there are equivalent
    ranks.
    Apply to path leg
    Instead of just once per connection, the fixed TSys supplement is applied for each path leg of the connection. The supplement is thus applied twice if two path legs use the same transport system which is
    subject to a supplement.

    Fare zone type

    Fare zone type for which the ticket type is valid with Fare structure =
    Zone-based fare or From-to zone-based fare.

    Used by fare sys- Numbers of the fare systems that currently use this ticket type (see
    tems
    "Defining fare systems" on page 2172)
    Ticket type Fares tab (depends on the fare structure)
    Fares tab for Distance-based fare
    Element

    Description

    Number of fare
    points

    For each fare level, enter the number of fare points that may be traversed.

    Interpolate

    Select the option, if the values shall be interpolated for the fare level.

    Fare

    User-defined fare per row. Edit the values directly in the list.

    PTVGROUP

    2175

    20.6.3.2 Creating ticket types


    Fares tab for Zone-based fare
    Element

    Description

    Number of fare
    zones

    For each fare level, enter the number of fare points that may be traversed. The cardinalities of the fare zones also enter the determination of traversed fare zones as well as the Fare zones being
    traversed multiple times are counted multiple times option.

    Fare

    User-defined fare per row. Edit the values directly in the list.

    Fares tab for From-to zone-based fare


    Element

    Description

    From fare zone/To Use the buttons to specify in a separate window between which fare
    fare zone
    zones the fare shall be valid.
    Notes
    If you do not specify a combination, no ticket will exist for it.
    Fare

    User-defined fare for the specified combination of fare zones


    Note
    The fare does not have to be symmetrical for the two directions of a
    relation.

    Creating the oppo- Mark a row and click this button to add another row with the fare
    site direction
    zones at the cross position, to which the same fare applies. If this row
    already exists, only the fare will be updated.

    Fares tab for Short distance fare

    2176

    Element

    Description

    Max. run time

    Max. run time in minutes to which the short-distance fare applies


    Notes
    If this option is not relevant, you need to enter a very high value.

    Max. distance

    Max. distance in km to which the short-distance fare applies


    Notes
    If this option is not relevant, you need to enter a very high value.

    Max. number of
    stops

    Max. number of stops to which the short-distance fare applies


    Note
    If this option is not relevant, you need to enter a very high value.

    Fare

    User-defined fare for the specified conditions

    PTVGROUP

    20.6.3.2 Creating ticket types


    Ticket type Count fare zones tab (Zone-based fare / From-to zone-based fare)

    Note: This tab is only provided, if the ticket type has either fare structure: Zone-based fare
    or From-to zone-based fare.
    Element

    Description

    Ignore stops
    without fare zone

    If the option has been selected, the calculation does not report an
    error, if a stop is located on the way which is not connected to a fare
    zone of specified type.
    Note
    By default, the option is not selected.

    Fare zones being If the option has been selected, a fare zone which is traversed more
    traversed multiple than once, is counted accordingly, depending on the number of fare
    times are counted zones. This will increase the fare.
    multiple times
    User-defined cardinalities

    PTVGROUP

    User-defined cardinalities
    If the option has been selected, fare zones can be weighted based
    on a numeric, integer attribute. Fare zones are counted according to
    their weighting, which results in increasing fares.
    Select the Attribute for cardinality in a separate window via the corresponding button.
    Ignore the cardinalities of first and last fare zones
    If the option has been selected, first and last fare zones are not weighted.
    Note
    Fare zones can be weighted and simultaneously be counted repeatedly.

    2177

    20.6.3.2 Creating ticket types


    Ticket type Supplements tab

    2178

    Element

    Description

    Code

    TSys code to which the supplement applies

    Name

    Name of the transport system to which the supplement applies.

    Fix

    Constant supplement in [currency units] for using the transport system

    Minimum

    Minimum fare for a passenger journey using this transport system. If the
    total fare resulting from the basic fare and the added supplement is still
    below this minimum fare value, then this minimum fare is charged.

    Rank

    In addition, you can define different ranks. Optionally only the TSys-specific supplement of the topmost rank (smallest rank no.) can enter the
    fare. If the ranks are equal, only the maximum supplement is charged.

    Dist.

    Specify whether a fare point based distance supplement shall be charged.


    Note
    This option is only provided, if you have specified a supplement via the
    Distance button.

    Distance

    Use the button to open a separate window in which you can specify how
    the supplement is calculated depending on the distance that is covered
    by the transport system.
    Note
    The distance is modeled in fare points.

    Use values

    Via this button you can apply the TSys-specific supplements defined for
    a different ticket type to the current ticket type. Select the different ticket
    type in the drop-down list.

    PTVGROUP

    20.6.3.3 Allocating transfer fares to fare systems

    1. Confirm with OK.


    The ticket type is defined.
    Edit ticket type
    1. In the PuT fare systems window, click the Ticket types tab.
    2. In the list of the ticket types, click the cell you want to edit.
    3. Make the desired changes.
    4. Confirm with OK.
    The changes are applied.
    Delete ticket types
    1. In the PuT fare systems window, click the Ticket types tab.
    2. In the list, click the ticket type of your choice.
    Tip: To select multiple entries, hold down the C TRL key while clicking the desired entries one by one.
    3. Click the Delete button.
    4. Confirm with OK.
    The ticket type is deleted.
    20.6.3.3

    Allocating transfer fares to fare systems


    The transfer fare is added to the ticket type's basic fare for the fare system. The transfer fare
    depends on the fare systems of the lines, where the transfer is made.
    1. In the Network menu, click the PuT fares entry.
    The PuT fares window opens.

    PTVGROUP

    2179

    20.6.3.4 Allocating ticket types to demand segments and fare systems

    2. Select the Transfer fares tab.


    A row is displayed for each possible transfer from fare system to fare system.
    3. Make the desired changes.
    Element

    Description

    Fare

    For each transfer between one fare system and another, a transfer fare
    can be charged. Edit the values directly in the cell. This value might be a
    negative one, though the total fare of a connection always is zero or
    greater than zero (see Fundamentals: Chpt. 8.5.2.3 , page 623)

    4. Confirm with OK.


    The transfer fares are allocated to the fare system.
    20.6.3.4

    Allocating ticket types to demand segments and fare systems


    Note: If demand matrices are not available by ticket type, you can define a virtual combined ticket type that contains mean fares for one-way tickets and season tickets, for
    example.
    1. In the Network menu, click the PuT fares entry.
    The PuT fares window opens.
    2. Select the Demand segments tab.
    For each combination of demand segment and fare system, a separate row is displayed.

    2180

    PTVGROUP

    20.6.3.5 Setting general options for PuT fares

    3. In the Ticket types column, click the desired button.


    The Selection Ticket types window opens.
    4. Select the desired ticket type.

    5. Confirm with OK.


    6. Confirm again with OK.
    The ticket types are allocated to the demand segments and fare systems.
    20.6.3.5

    Setting general options for PuT fares


    1. In the Network menu, click the PuT fares entry.
    The PuT fares window opens.
    2. Select the General settings tab.

    PTVGROUP

    2181

    20.6.3.5 Setting general options for PuT fares

    3. Make the desired changes.


    Element

    Description

    Fall-back fare

    Price that is charged for a path if no possible fare system selection can be found.

    PuT-aux fare sys- Use the button to select the fare systems which will be used for all
    tems
    paths legs with a TSys of type PuT Aux.
    4. Confirm with OK.
    The general settings for fares become effective.

    2182

    PTVGROUP

    21 Settings for the environmental impact model and emission calculation according to HBEFA

    21

    Settings for the environmental impact model and emission


    calculation according to HBEFA
    Using the add-on module Noise emissions RLS 90 , you can calculate the environmental
    impact - noise volumes and air pollution emissions caused by motorized private traffic. The
    results of noise volume and pollution emission calculations can be displayed in tables or
    graphically (see "Displaying noise volumes" on page 2187 and "Displaying air pollution emissions" on page 2190).
    In Visum, the HBEFA add-on allows you to calculate emission values by link, by territory, or
    network-wide (see "Settings for emission calculation according to HBEFA" on page 2191).
    Subjects
    Setting environmental impact parameters
    Editing environmental link attributes
    Resetting the calculation
    Calculating noise volumes
    Displaying noise volumes
    Saving noise volumes
    Calculating air pollution emissions
    Displaying air pollution emissions
    Saving air pollution emissions
    Settings for emission calculation according to HBEFA

    21.1

    Setting environmental impact parameters


    Note: You can read the environmental parameters available from the environmental parameters file (*.upa) (see "Opening a file" on page 833).
    1. In the Calculate menu, select Environmental parameters.
    The Environmental parameters window opens.

    2. Select the Basis tab.


    PTVGROUP

    2183

    21.1 Setting environmental impact parameters


    3. Make the desired changes.
    Element

    Description

    Calculation based
    upon

    The calculation of all environmental calculation procedures is


    based on transport volumes.
    Volume PrT [Veh]
    The volumes are adopted from the assignment results. That
    means vCur per link and TSys is calculated based on tCur, via
    link type specific VD functions (see "Definition and application of
    volume-delay functions" on page 1892).
    AddValue1 - AddValue3
    The volumes are adopted from the AddValues (count data), i.e.
    vCur is calculated via link type specific VD functions (see "Definition and application of volume-delay functions" on page 1892).

    Valid speed ranges If the calculation is based on tCur, you can specify the valid
    speed ranges for cars and HGV for all environmental calculation
    procedures.
    Note
    If the calculation is based on vCur, the following applies:
    vMin is considered if vCur < vMin.
    vMax is considered if vCur > vMax.
    Noise

    In the list, you can select the parameters for noise volume calculation (see "Calculating noise volumes" on page 2185).

    mADT

    For all environmental calculation procedures a factor can be specified for every global link type for converting the mean average
    daily traffic (mADT) to the relevant hourly values.

    4. Select the Pollutants tab.


    5. Make the desired changes.
    Element

    Description

    Pollutants

    In the list, you can select the parameter for calculating air pollutant
    emissions (see "Calculating air pollution emissions" on page 2188).

    6. Confirm with OK.


    The changes are applied.
    Note: You can save your settings to the environmental parameters file (*.upa) (see
    "Saving a file" on page 831).

    2184

    PTVGROUP

    21.2 Editing environmental link attributes

    21.2

    Editing environmental link attributes


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Links button.


    3. Double click the link.
    The Edit link window opens.

    4. Select the Environment tab.


    5. Make the desired changes (see "Links: Environment tab" on page 1110).
    6. Confirm with OK.
    The changes are applied.

    21.3

    Resetting the calculation


    From the Calculate menu, choose Initialize environment.
    The existing environmental calculation is reset.

    21.4

    Calculating noise volumes


    The following example describes the individual work steps for calculating the noise load produced by HGVs.
    Calculating HGV share
    If the HGV share p is not yet available as attribute value, it has to be specified first.
    1. Read the demand matrix for the car and HGV demand segments (see "Opening matrices"
    on page 1721).
    2. Perform an assignment for demand segments of cars and HGVs (see "Setting and calculating the parameters for PrT assignment" on page 1931).

    PTVGROUP

    2185

    21.4 Calculating noise volumes

    Note: The assignment can be performed with all assignment procedures.


    3. Calculate the HGV shares (see "Calculating attribute values from the values of other attributes" on page 989)

    Calculating noise volume


    1. In the Calculate menu, select Environmental impact parameters.
    The Environmental parameters window opens.
    2. Select the Basis tab.
    3. Make the desired changes.
    Element

    Description

    Calculation based
    upon

    The calculation of all environmental calculation procedures is


    based on transport volumes.
    Volume PrT [Veh]
    The volumes are adopted from the assignment results. That
    means vCur per link and TSys is calculated based on tCur, via
    link type specific VD functions (see "Definition and application of
    volume-delay functions" on page 1892).
    AddValue1 - AddValue3
    The volumes are adopted from the AddValues (count data), i.e.
    vCur is calculated via link type specific VD functions (see "Definition and application of volume-delay functions" on page 1892).

    Valid speed ranges You can specify the valid speed for cars and HGV for all environmental calculation procedures.
    Note
    If the calculation is based on vCur, the following applies:
    vMin is considered if vCur < vMin.
    vMax is considered if vCur > vMax.
    Noise

    2186

    You can specify specific parameters for the calculation of the


    noise volume.
    v0 free speed

    PTVGROUP

    21.5 Displaying noise volumes


    Element

    Description
    Noise calculation is carried out with permissible maximum speed
    v0 in accordance with RLS-90. Value range for minimum and
    maximum v0 for cars is 30-130 km/h and for HGV 30-80 km/h.
    vCur current speed
    Noise calculation is carried out with specific, volume-dependent
    speed vCur contrary to the standard model calculation values of
    RLS-90. In this case, the specified patterns and valid speeds
    apply.

    mADT

    Noise calculation in accordance with RLS-90 is based on the socalled relevant hourly traffic volume M 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 RLS-90 lists the conversion factors mADT. If suitable project-specific analysis results
    for determining the relevant hourly traffic volume M are available
    (no peak hour values), these can be used. If this is the case, the
    standard setting mADT = 1 must be specified.

    4. Confirm with OK.


    The changes are applied.
    5. In the Calculate menu, select Calculate environmental impact> Noise-Emis-Rls90 or
    Noise-Emis-Nordic.
    The noise volume is calculated based on the link according to the selected procedure.
    Note: Links with volumes < 10 veh/h are not regarded in noise calculation.

    21.5

    Displaying noise volumes


    The results of noise volume calculations can be displayed in tables or graphically.

    21.5.1

    Graphic display of noise volumes


    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Links> Bars.
    3. Make the basic settings (see "Displaying bars and adjusting basic settings" on page 2368).
    4. Insert the desired bar (see "Defining one or multiple bars" on page 2373).
    5. Make the desired settings for the bar (see "Setting the display properties of a standard bar"
    on page 2375).
    6. In the Scaling attribute section, select the Noise attribute via the button.

    PTVGROUP

    2187

    21.5.2 List output of noise volumes

    7. Confirm with OK.


    The bars are displayed according to your chosen settings.

    21.5.2

    List output of noise volumes


    1. Open the Links list (see "Opening a list" on page 2299).
    2. Click the Select attributes symbol
    to select the Noise attribute (see "The window used
    for the selection of multiple attributes" on page 968).
    3. Confirm with OK.
    The attribute is shown in the list in the set order.

    21.6

    Saving noise volumes


    You can save the calculated noise volumes a as version file *.ver, or as an attribute file *.att in
    the current List (links) window (see "Saving a version file" on page 841 and "Save list to attribute file" on page 2325).

    21.7

    Calculating air pollution emissions


    1. For the calculation of air pollution emissions, read the emission factors for a different reference year.
    Reference year 1990: EMI1990.DAT
    Reference year 1992: EMI1992.DAT
    Reference year 2000: EMI2000.DAT

    2188

    PTVGROUP

    21.7 Calculating air pollution emissions


    Note: During the installation, the files are generated in the directory ...Program
    files\PTV Vision\PTV Visum 13\exe\....
    2. Rename the read emiss.dat file, or enter a name and directory for the desired file in the standard configuration file VISUM.cfg, under option -E, instead of in the emiss.dat standard
    emission file (see "Changes to settings in the configuration file" on page 889).
    3. In the Calculate menu, select Environmental parameters.
    The Environmental parameters window opens.
    4. Select the Basis tab.
    5. Make the desired changes.
    Element

    Description

    Calculation based
    upon

    The calculation of all environmental calculation procedures is


    based on transport volumes.
    Volume PrT [Veh]
    The volumes are adopted from the assignment results. That
    means vCur per link and TSys is calculated based on tCur, via
    link type specific VD functions (see "Definition and application of
    volume-delay functions" on page 1892).
    AddValue1 - AddValue3
    The volumes are adopted from the AddValues (count data), i.e.
    vCur is calculated via link type specific VD functions (see "Definition and application of volume-delay functions" on page 1892).

    Valid speed ranges The procedure requires the following value ranges for speeds in
    order to carry out a correct calculation of the air pollution emissions:
    Pollution-Emis: 10-130 km/h (car); 10-100 km/h (HGV).
    In this case applies:
    vMin is considered if vCur < vMin.
    vMax is considered if vCur > vMax.
    Noise

    In the list, you can select the parameters for noise volume calculation (see "Calculating noise volumes" on page 2185).

    mADT

    For factor = 1.00 per GlobLinkType the pollutants for the time
    interval for which the traffic volumes are available are calculated.

    6. Select the Pollutants tab.


    7. Make the desired changes.

    PTVGROUP

    2189

    21.8 Displaying air pollution emissions


    Element

    Description

    v0 free speed

    Free flow speed v0 is used for calculation.

    vCur current
    speed

    Free flow speed v0 is used for calculation.

    vCur with time


    series

    The calculation is based on vCur and is carried out in several


    steps. Hereby, the total pollution volume is determined by adding
    the three calculated partial pollution volumes.
    The first partial pollution calculation is carried out for 50% traffic
    volume with resulting vCur.
    The second partial pollution calculation is carried out for further
    30% of vehicles with vCur at 80% of traffic volume.
    The third partial pollution calculation is carried out for the remaining 20% of vehicles with vCur at 100 % traffic volume.

    8. Confirm with OK.


    The changes are applied.
    9. In the Calculate menu, select Calculate environmental impact> Pollution-Emis.
    The air pollution emissions are calculated.

    21.8

    Displaying air pollution emissions


    The results of air pollution calculations can be displayed in tables or graphically.

    21.8.1

    Graphic display of air pollution emissions


    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Links> Bars.
    3. Make the basic settings (see "Displaying bars and adjusting basic settings" on page 2368).
    4. Insert the desired bars (see "Defining one or multiple bars" on page 2373).
    5. Specify the desired bar settings (see "Setting the display properties of a standard bar" on
    page 2375).
    6. In the Scaling attribute section, select one of the following attributes for each bar, via the
    button:
    EDat-CO (carbon monoxide in kg/km)
    EDat-HC (Hydrocarbons in g/km)
    EDat-NOx (Nitric oxides in g/km)
    EDat-SO2 (Sulphur dioxide in g/km)

    2190

    PTVGROUP

    21.8.2 List output of noise volumes

    7. Confirm with OK.


    The bars are displayed according to your chosen settings.

    21.8.2

    List output of noise volumes


    1. Open the Links list (see "Opening a list" on page 2299).
    2. Click the Select attributes symbol
    to select the attributes of your choice (see "The window used for the selection of multiple attributes" on page 968).
    3. Confirm with OK.
    The attributes are displayed in the list in the set order.

    21.9

    Saving air pollution emissions


    You can save the noise volumes as a version file *.ver or as an attribute file *.att in the current
    List (links) window (see "Saving a version file" on page 841 and "Save list to attribute file" on
    page 2325).

    21.10

    Settings for emission calculation according to HBEFA


    Prior to emission calculation according to HBEFA (see Fundamentals: Chpt. 9.3 , page 685),
    you need to specify the following settings.
    Notes: This functionality is only available with the HBEFA add-on.
    In addition, you require additional data files which provide the HBEFA emission factors.
    This PTV HBEFA Data Package is installed with your Visum installation.

    PTVGROUP

    2191

    21.10.1 Defining fleet compositions for the calculation

    21.10.1 Defining fleet compositions for the calculation


    Before you can start the HBEFA-based calculation of emissions, you need to define fleet compositions, which provide the basis for the calculation.
    In Visum six HBEFA fleet compositions are provided. On the basis of those fleet compositions,
    you create your Visum fleet compositions.
    21.10.1.1 Creating a fleet composition
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.

    Tips: Use the context menu to adjust the column width to the size of the window or to
    copy and paste cell contents.
    Double-click a row to open the Edit window of the respective fleet composition (see
    "Editing fleet compositions" on page 2193).
    2. Click the Create button.
    The Create fleet composition window opens.
    3. Enter the desired data (see "Attributes and options of fleet compositions" on page 2193).
    4. Confirm with OK.
    The fleet composition is inserted.

    2192

    PTVGROUP

    21.10.1.2 Attributes and options of fleet compositions


    21.10.1.2 Attributes and options of fleet compositions

    Element

    Description

    Number

    Unique number of the fleet composition


    Note
    The fleet compositions are numbered consecutively. You can
    overwrite the preset number with a number that does not yet exist
    in the network.

    Code

    Code of the fleet composition

    Name

    Name of the fleet composition

    Ref. year

    Indicates the year whose fuel quality is taken as a basis for the
    emission factors.

    Categories

    Categories selected from the six HBEFA fleet compositions which


    will be allocated to the fleet composition.
    Note
    At least one category must be selected, multiple selection is possible.

    21.10.1.3 Editing fleet compositions


    You can edit existing fleet compositions as follows.
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.
    2. Mark the row that you want to edit.
    Tip: You can also mark multiple rows and edit the fleet compositions jointly. Then only
    the Categories can be edited however.
    3. Click the Edit button.
    The Edit fleet compositions window opens.

    PTVGROUP

    2193

    21.10.1.4 Duplicating fleet compositions


    4. Make the desired changes (see "Attributes and options of fleet compositions" on page
    2193).
    5. Confirm with OK.
    The changes are applied.
    21.10.1.4 Duplicating fleet compositions
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.
    2. In the table of fleet compositions, mark the one you want to duplicate.
    3. Click the Duplicate button.
    The Edit fleet composition <number> window opens.
    4. Make the desired changes (see "Attributes and options of fleet compositions" on page
    2193).
    5. Confirm with OK.
    The fleet composition is duplicated.
    21.10.1.5 Combining existing fleet compositions
    In HBEFA, a fleet composition belongs to exactly one vehicle category (for example Car, Bus,
    Motorcycle). In Visum, exactly one fleet composition (per class, i.e. urban, rural and highway)
    is specified for a demand segment. Since the classification into demand segments is less fine,
    it might be necessary to combine existing fleet compositions.
    You can generate combinations of existing fleet compositions as follows:
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.
    2. In the table of fleet compositions, mark at least two fleet compositions you want to combine.
    3. Click the Form combinations button.
    A Wizard opens.

    4. In the Weight column, enter the desired weighting.


    2194

    PTVGROUP

    21.10.1.6 Adopting fleet compositions from HBEFA


    5. Click the Next button.
    The next page opens.
    6. Enter the desired data for the new fleet composition (see "Attributes and options of fleet
    compositions" on page 2193).
    7. Click the Next button.
    The next page opens. The page lists all categories which will be allocated to the fleet composition.
    Tip: Use the Back button, if you want to make changes on previous pages.
    8. Click the Finish button.
    The combination is inserted. It contains all categories of the combined fleet compositions that
    have a weighting > 0.
    21.10.1.6 Adopting fleet compositions from HBEFA
    You can transfer fleet compositions predefined in HBEFA to Visum.
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.
    2. Click the Transfer from HBEFA button.
    A wizard opens.
    3. Select the desired fleet compositions in the Active column.
    4. Select a Country, if desired.
    5. Select a Ref. year, if desired.
    6. Click the Next button.
    The Please select the desired fleet composition(s) page opens.
    Note: The page only contains the fleet compositions that match the selected country
    and the reference year. Use the Back button, if you want to make changes on previous pages.
    7. From the list, select one or more fleet compositions.
    Tip: Press and hold down the C TRL key if you want to select several rows.
    8. Click the Next button.
    The Creating the following fleet composition(s) page opens.
    9. To delete one or more fleet compositions in the list, mark the appropriate row(s) and click
    the Delete button.

    PTVGROUP

    2195

    21.10.1.7 Editing subsegment shares


    10. Click the Finish button.
    For each fleet composition transferred from HBEFA a fleet composition will be inserted in
    Visum. The shares of the subsegments are transferred from HBEFA.
    21.10.1.7 Editing subsegment shares
    You can edit the weight shares of the individual subsegments of one or multiple fleet compositions.
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.
    2. Mark the fleet composition(s) whose subsegments you want to edit.
    Tip: Press and hold down the C TRL key if you want to mark several rows.
    3. Click the Edit subsegment shares button.
    The Management of the weight proportions of the fleet compositions window opens.
    Note: The displayed set of subsegments depends on the categories of the marked
    fleet compositions. All subsegments are listed, whose category is contained in at least
    one of the selected fleet compositions. Each row relates to a subsegment with the relevant attributes.
    4. Edit the Weight column(s) as desired.
    Notes: If you edit the weighting, the values of the Share columns are recalculated.
    The Weight columns are the only ones that can be edited.
    5. If required, make further changes in the window.

    2196

    Element

    Description

    Normalize weight

    Here you can enter a factor for the scaling of the weights.
    Note
    A scaling makes sense, if the weight sums have changed during
    the modification and the weights can no longer be compared.
    After the scaling, the sum of the weights of each column equals
    the entered factor.

    Switch
    to the bar view

    Use this button to open the bar display of the fleet composition(s).
    Notes
    Each bar represents a fleet composition with the individual subsegments. The meaning of the colors is explained in the legend.
    You cannot edit the display.

    PTVGROUP

    21.10.1.8 Deleting a fleet composition

    Tip: If you move the mouse over the bars, a quick info displays the characteristics of
    the subsegments.
    6. Confirm with OK.
    The changes of the shares are applied.
    21.10.1.8 Deleting a fleet composition
    1. In the Network menu, select the Fleet compositions entry.
    The Fleet compositions window opens.
    2. Mark the fleet composition that you want to delete.
    Tip: Press and hold down the C TRL key if you want to delete several rows.
    3. Click the Create button.
    4. Confirm with OK.
    The fleet composition is deleted.

    21.10.2 Input attributes for calculation


    Prior to emission calculation, values must be entered for the following attributes:
    Network
    object

    Attribute

    Link type

    HBEFA_Roadtype Use this attribute to allocate an HBEFA road type to each


    Visum link type in the Link types list or in the Link types
    window.

    Link

    Urban

    PTVGROUP

    Description

    This attribute specifies whether a link is regarded as


    urban or rural during the calculation.

    2197

    21.10.3 Calculating emissions according to HBEFA


    Network
    object

    Attribute

    Description
    Notes
    Your allocations should be based on the HBEFA scheme
    (see Fundamentals: Chpt. 9.3.2.1 , page 686). You can
    set the attribute value In the Environment tab of the
    respective link window or in the Link list.
    The attribute is not directly related to the set fleet compositions Urban, Rural and Highway.

    Zone

    Specifying the
    Cold start share
    per zone

    Use this attribute to specify the share of cold start separately for each zone. In the Zones list and in the HBEFA
    tab of the Edit zone window, you can allocate values
    from 0 to 1 to the attribute.
    Tip
    If the zone is a cordon zone, for example, it makes sense
    to allocate value 0 to the zone, because vehicles are
    usually warm already as they pass a cordon zone.

    Zone

    Calculate Cold
    Start Excess
    Based on Routes

    Use this attribute to specify for each zone, whether the


    cold start excess emission shall be calculated on the
    basis of routes (yes/no) or polygonally. In the Zones list,
    you can allocate value 0 (no) or 1 (yes) to the attribute,
    see calculation of the paths (see Fundamentals: Chpt.
    9.3.2.2 , page 688).
    Alternatively, you can specify this setting in the HBEFA
    tab of the Edit zone window.

    21.10.3 Calculating emissions according to HBEFA


    Notes: The results of a PrT assignment should be provided.
    If you want to calculate emission values by territory, you can execute the Territory indicators operation after HBEFA-based emission calculation (see "Calculating basic territory indicators" on page 1885). The emission values can then be displayed in the list
    Territories > Basis.
    Before you start the calculation, you should specify all desired settings concerning the fleet
    compositions (see "Defining fleet compositions for the calculation" on page 2192) and enter
    values for each input attribute (see "Input attributes for calculation" on page 2197), as they
    serve as a basis for the calculation.
    21.10.3.1 Emission calculation according to HBEFA
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.

    2198

    PTVGROUP

    21.10.3.2 Parameters of the HBEFA procedure


    2. In the desired position of the procedure sequence, insert the HBEFA-based emission calculation procedure from the Miscellaneous category.
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    The Select Demand segments window opens.
    4. In the Demand segments section, select the desired entries.
    5. Confirm with OK.
    The demand segments selected are listed in the Reference object(s) column.
    6. Select the operation inserted Then in the Operations section, click the Edit button.
    The Parameters: HBEFA-based emission calculation window opens.
    7. Select the Basis tab.
    8. Set the desired parameters (see "Parameters of the HBEFA procedure" on page 2199).
    9. Confirm with OK.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    Emission calculation according to HBEFA is executed.
    21.10.3.2 Parameters of the HBEFA procedure

    Basis tab

    PTVGROUP

    2199

    21.10.3.2 Parameters of the HBEFA procedure


    Element

    Description

    Emission calIf the option has been selected, the emissions are calculated staculation for anatically, accordingly only for analysis period and analysis horizon.
    lysis period (AP)
    and analysis horizon (AH)
    Emission calculation for analysis period (AP),
    for analysis horizon (AH), and for
    each analysis
    time interval

    2200

    If the option has been selected, the emissions are calculated dynamically, accordingly for analysis period, analysis horizon, and for
    each existing analysis time interval.
    Tip
    In the Links and Territories lists, emission values can then be displayed for each analysis interval.
    Note
    If you use the attribute Volume Capacity Ratio PrT to determine the
    LOS, the LOS is calculated separately per analysis time interval. In
    this case, however, the value for AP and AH is not significant,
    because the Volume Capacity Ratio PrT(AP) is the quotient of the
    Volume (AP) and the Capacity. The capacity relates to one hour
    while AP usually takes more than an hour, so that the Volume Capacity Ratio PrT(AP) is strongly inflated and LOS 4 will almost always
    be set.

    PTVGROUP

    21.10.3.2 Parameters of the HBEFA procedure


    Element

    Description

    Calculate cold
    start emissions

    If this option has been selected, cold start excess emissions are calculated.
    Cold start parameters
    Use the list to select a parameter, which specifies the average temperature, the dwell time distribution and the travel time distribution for
    the cold start.

    Pollutants

    Select the pollutants whose values you want to calculate:


    HBEFA group 1: Established measurement programs
    CO (carbon monoxide)
    Fuel (fuel consumption)
    Gasoline (fuel consumption)
    Diesel (fuel consumption)
    PM (particle matters)
    HC (hydrocarbons)
    NOx (nitrogen oxide)
    CO2 reported (carbon dioxide)
    CO2 total (carbon dioxide)
    PN (particle matters)
    HBEFA group 2: Complementary measurement programs and
    literature
    Pb (lead)
    Benzene
    CH4 (methane)
    SO2 (sulfur dioxide)
    NO2 (nitrogen dioxide)
    NMHC (non-methane hydrocarbon)
    HBEFA group 3: Indicative literature references
    NH3 (ammoniac)
    N2O (nitrous oxide)
    Note
    The emission factors of the pollutants SO2, Pb and CO2 reported are
    country specific. So far, only values for Germany can be calculated in
    Visum.

    Traffic situations tab


    Element

    Description

    Link attribute for


    speed class

    Use the button to select a link attribute for the determination of the
    speed class. By default, the v0 PrT attribute is selected.

    Level of Service
    (LOS)

    In this section, specify how you want to determine the LOS.


    Link attribute for LOS determination

    PTVGROUP

    2201

    21.10.3.2 Parameters of the HBEFA procedure


    Element

    Description
    Use this button to select a link attribute that defines the Level of Service, for example Volume Capacity Ratio PrT (standard) or a userdefined link attribute.
    Apply values directly (expected values 1, 2, 3 or 4)
    If the option has been selected, the values 1, 2, 3 or 4 are expected.
    According to the values, classify by the given class limits
    If this option has been selected, you can set three values as class
    limits.

    Volume and fleet composition tab


    Element

    Description

    Use uniform fleet


    composition
    (recommended)

    If the option has been selected, only one fleet composition is used
    per demand segment.
    Note
    We recommend this option because otherwise, a shift from urban to
    rural areas (for example in case of a by-pass) would lead to changed
    emissions only due to a different fleet composition. Effects arising
    from a changed driving performance or traffic situation would hence
    be covered and falsified.

    Use differentiated If the option has been selected, a fleet composition Urban, Rural and
    fleet compositions Highway must be allocated to each demand segment.
    Volume attributes
    and fleet compositions by
    demand segment

    The following values enter the calculation:


    DSeg
    The column contains a row for each previously specified demand
    segment.
    Traffic volume: Links (Attribute)
    Specify a volume attribute by clicking the button with the attribute
    label.
    Origin traffic: Zones (Attribute)
    Specify a zone attribute which contains the origin traffic.

    2202

    PTVGROUP

    21.10.4 Resetting emission calculation


    Element

    Description

    only uniform fleet


    composition

    If you use a uniform fleet composition, you need to make the following selection in addition:
    Fleet composition
    Use the drop-down list to allocate a fleet composition to each
    demand segment.

    only differentiated
    fleet composition

    If you use a differentiated fleet composition, you need to make the following selection in addition:
    Urban
    From the drop-down list, select a fleet composition for each demand
    segment.
    Rural
    From the drop-down list, select a fleet composition for each demand
    segment.
    Highway
    From the drop-down list, select a fleet composition for each demand
    segment.

    Note: If you want to calculate emissions for PuT, create a PrT demand segment for the
    PuT, calculate the Number of service trips (AP) using operation PuT operating indicators and select the volume attribute Number of Service Trips (AP) in the Volume and
    fleet composition tab.

    21.10.4 Resetting emission calculation


    The procedure Init HBEFA-based emission calculation deletes all existing emission results.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. In the desired position of the procedure sequence, insert the INIT HBEFA-based emission
    calculation procedure from the Miscellaneous category.
    3. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The results of the emission calculation according to HBEFA are deleted.
    Note: In addition, the data structures for depositing the averaged emission factors at the
    fleet compositions are initialized in order to save memory.

    21.10.5 Displaying the emission calculation results


    You can view the results calculated in lists and graphically in the network, e.g. as link bars.

    PTVGROUP

    2203

    21.10.5.1 Displaying the results in lists


    21.10.5.1 Displaying the results in lists
    The following lists contain calculated emission values.
    The Emissions (HBEFA) list contains indicators that have been determined based on the
    entire network.
    In the Links list, you can display the calculated pollutants in grams. Per pollutant, one output attribute each is issued per demand segment for warm emissions, cold start and PrT
    total.
    In the Territories list, you can display the calculated pollutants by territory.
    1. Open the desired list (see "Opening a list" on page 2299)
    2. Click the Select attributes symbol
    to select the attributes of your choice (see "The window used for the selection of multiple attributes" on page 968).
    3. Confirm with OK.
    The emission values are displayed.
    21.10.5.2 Graphic display of HBEFA results
    Based on the link attributes calculated, you can e.g. show your emission results as link bars.
    Note: We recommend scaling the emission values for the display of link bars to achieve
    better results. To do this, use the Edit attribute operation and divide by the length and, if
    necessary, the volume, too.
    Alternatively, you can display absolute values in the form of column charts.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Links> Bars.
    3. Make the basic settings (see "Displaying bars and adjusting basic settings" on page 2368).
    4. Insert the desired bars (see "Defining one or multiple bars" on page 2373).
    5. Specify the desired bar settings (see "Setting the display properties of a standard bar" on
    page 2375).
    6. In the Scaling attribute row, for each bar, click the button to select the desired emission
    value.

    2204

    PTVGROUP

    21.10.6 Saving HBEFA results

    7. Confirm with OK.


    In the network, the selected emission values are displayed on link level.

    21.10.6 Saving HBEFA results


    You can save the results of your HBEFA calculation as follows:
    With the version in a *.ver file.
    To a network file *.net.

    PTVGROUP

    2205

    21.10.6 Saving HBEFA results


    To an attribute file *.att for the respective list.
    In shapefiles (for a potential transfer to immission modules).
    Note: Instructions on how to save files can be found at the beginning of the manual (see
    "Opening and saving files" on page 831).

    2206

    PTVGROUP

    22 Using GIS functionalities

    22

    Using GIS functionalities


    This chapter describes the handling of GIS objects, the intersection of objects and the shapefile interface. It also deals with the functionalities for network editing (GPS tracking) and the
    use of legends, backgrounds, texts and polygons facilitating network data processing for presentations.
    Subjects
    Editing the coordinate system and scale
    GIS objects
    Intersecting objects
    The Shapefiles interface
    Inserting additional information in the network display
    Using texts in the network display
    Using backgrounds in the network display
    Using polygons in the network display
    Creating legends
    GPS tracking
    Note: For all geometrically arranged network objects in Visum read and write access to
    attributes for the geometry information is provided. In Visum these are the WKT polyline,
    WKT location and WKT surface attributes.

    22.1

    Editing the coordinate system and scale


    You can switch the coordinate system of your network, change the scale, recalculate the
    lengths of some network objects and shift or rotate the network.
    Note: Visum stores information about coordinate systems in various data files. If you read
    data with coordinate information additionally to a network, Visum deals with that information differently depending on file type and settings.
    Examples
    Reading network files additionally (see "Reading network data additionally" on page
    851)
    Importing Shapefiles (see "Importing Shapefiles" on page 2221)

    22.1.1

    Selecting a coordinate system


    For the network currently loaded, you can select a different coordinate system. This is
    necessary, for example, if your current network uses the Visum coordinate system, and you
    want to import input data in a certain projection (see Fundamentals: Chpt. 10.4 , page 705).
    Notes: By default Visum uses its own Visum coordinate system.
    A set of coordinate systems is provided as files, with the extension *.prj, in the directory
    ...\Exe\Projections of your Visum installation (see "Editing the storage location of files" on
    page 837). The format of the files is *.wkt (well-known text format).

    PTVGROUP

    2207

    22.1.1 Selecting a coordinate system


    Depending on the coordinate systems between which you switch this may have different
    effects:
    When switching from the Visum coordinate system to another coordinate system, you
    decide that the previously used coordinates belong to the newly selected coordinate system. Neither the coordinates nor the display will change.
    If you switch between two pre-defined coordinate systems, Visum will transform the data.
    Both display and coordinates will change.
    If you switch back from a pre-defined coordinate system to the Visum system, neither the
    coordinates nor the display will change.
    1. From the Network menu, choose Network settings.
    The Network settings window opens.
    2. Select the Scale tab.
    Note: From the selected options Visum (no projection) and From file you can see
    which coordinate system is currently selected.
    3. In the Spatial reference system section, select the desired options.

    2208

    Element

    Description

    Visum (no projection)

    If this option has been selected, you will switch to the Visum coordinate system. Neither the coordinates nor the display will
    change.

    From file

    If this option has been selected, you will switch to a pre-defined


    coordinate system. Via the adjacent button, select the desired
    coordinate system in the Projections window.
    Notes
    Make sure that the selected coordinate system matches your
    data.
    If you want to switch between two pre-defined coordinate systems, first of all you have to switch to the world-wide applicable
    GCS WGS 84 coordinate system and then to the desired system.
    This is to ensure that the date (=the zero point of the coordinate
    system) is converted correctly.
    You will find the GCS WGS 84 coordinate system in the Projections window under Geographic Coordinate Systems>
    World> WGS 1984.prj.

    Transform coordinates in case of


    changes

    If this option has been selected, the coordinates are transformed automatically and the network display is refreshed.
    If this option has not been selected, the coordinate values
    remain unaltered when switching the system. This setting is helpful, for example, if the wrong coordinate system has previously
    been defined for the available coordinate values.

    PTVGROUP

    22.1.2 Editing the network scale


    Notes: Once you have changed the coordinate system, performed actions cannot be
    undone.
    If you change the coordinate system, the lengths of line objects (for example links,
    connectors and line route items) may alter, too. If required, they must be explicitly
    recalculated (see "Recalculating lengths" on page 2209).
    4. Confirm with OK.
    The coordinate system is changed.

    22.1.2

    Editing the network scale


    Visum uses the network scale to calculate the distance between two points in length units from
    the distance in coordinate units.
    Note: If you use metric units, the formula distance [m] = network scale distance [coordinate units] applies. If you use imperial units, the formula distance [miles/1000] = network scale distance [coordinate units] applies.
    1. In the Network menu, select the Network settings entry.
    The Network settings window opens.
    2. Select the Scale tab.
    3. Under Network scale, enter a factor the network scale is multiplied by.
    Note: If you change the network scale, the lengths of line objects (for example links,
    connectors and line route items) may alter, too. If required, they must be explicitly
    recalculated (see "Recalculating lengths" on page 2209).
    4. Confirm with OK.
    If you have not recalculated the lengths, a message will be displayed.
    5. Confirm with OK.
    The network scale is changed.

    22.1.3

    Recalculating lengths
    You can recalculate the lengths of line objects, for example of links, connectors and line routes, after making manual adjustments in the network or changes to the network scale.
    Notes: The lengths are only calculated correctly, if your network has a length-preserving
    (=metrical) coordinate system (see "Selecting a coordinate system" on page 2207).
    If you change the number of decimal places or the network scale, the link lengths and the
    connector lengths will change, too. Due to the changed length of links, the link impedance and thus the assignment result may also change.
    1. From the Network menu, choose Network settings.

    PTVGROUP

    2209

    22.1.4 Rotating and/or shifting the network


    The Network settings window opens.
    2. Select the Scale tab.
    3. Select the desired options.
    Element

    Description

    Recalculate lengths The lengths of links and connectors are recalculated on the
    of links and connec- basis of the coordinate system.
    tors
    Recalculate line
    route length data
    from link lengths

    If this option has been selected, in addition to links and connectors, the lengths of line routes are recalculated.

    Regard only active


    links, connectors,
    line routes

    If this option has been selected, only active links, connectors


    and line routes are considered.
    If this option has not been selected, all links, connectors and
    line routes are considered.

    Calculation method Length = Direct length x Network scale


    If this option has been selected, the link lengths are determined
    by multiplying the direct distance between two nodes with the
    network scale.
    Length = Polygon length x Network scale (intermediate points
    are regarded for links with edited shape)
    If this option has been selected, the link lengths are determined
    by multiplying the actual course of the link with the network
    scale.
    4. Click the Recalculate button.
    5. Confirm with OK.
    The lengths are recalculated.

    22.1.4

    Rotating and/or shifting the network


    You can rotate the entire network model by an arbitrary angle and additionally shift it vertically
    and/or horizontally by an arbitrary offset.
    Notes: If you rotate or shift a network with any other coordinate system than the Visum
    one, the reference to real coordinates is dropped. The active coordinate system is deleted and reset to the standard Visum coordinate system.
    Any backgrounds displayed with the aid of a reference point are shifted (see "Using backgrounds in the network display" on page 2237).
    1. From the Network menu, choose Network settings.
    The Network settings window opens.
    2. Select the Scale tab.

    2210

    PTVGROUP

    22.2 GIS objects


    3. Click the Shift network button.
    The Rotate / shift network window opens.
    4. Make the desired changes.
    Element

    Description

    Rotation angle
    (degree)

    Angle in degree by which the network is rotated


    Note
    For an angle between 0 and 360 the rotation is clockwise, for an
    angle between -360 and 0 the rotation is an anti-clockwise.

    Shift X

    Offset by which the network is shifted horizontally

    Shift Y

    Offset by which the network is shifted vertically

    5. Confirm with OK.


    6. Confirm the query with Yes.
    The network is rotated and/or shifted.

    22.2

    GIS objects
    You can display GIS objects in your network by connecting to a Personal Geodatabase (PGD)
    (see Fundamentals: Chpt. 10.1 , page 691).
    Note: The GIS objects are only displayed in your network while you are connected to the
    PGD. You cannot create or delete GIS objects interactively.
    Three types of GIS objects can be distinguished:
    Point
    Line
    Surface

    22.2.1

    Connecting Visum to a Personal Geodatabase


    1. From File menu, choose Import> Connect to Personal Geodatabase.
    The Select Feature class or Feature data set window opens.

    PTVGROUP

    2211

    22.2.2 Finding a GIS object

    2. Select the desired objects and confirm with Add.


    A query opens.
    Note: The information on the coordinate system of the PGD is disregarded.
    3. Click Yes to confirm.
    The selected GIS objects are imported.

    Notes: GIS objects can be normalized when read in (see Fundamentals: Chpt. 3.5 , page
    120). In the case of GIS objects with many faces the process with normalization may take
    very long.
    You can intersect GIS objects with other network objects and thus continue using the
    data when you are no longer connected to the PGD (see "Intersecting objects" on page
    2217).

    22.2.2

    Finding a GIS object


    1. In the Network window, click the

    2212

    Edit mode icon.


    PTVGROUP

    22.2.3 Selecting GIS objects


    2. Right-click the GIS objects button.
    The GIS objects context menu opens.
    3. Select the Find entry.
    A window opens.
    4. From the drop-down list, select the search criterion (Number or Name).
    5. If necessary, restrict the number of GIS objects which is searched.
    Element

    Description

    Only active ones

    If this option has been selected, only active GIS objects are
    considered.
    If this option has not been selected, all GIS objects will be considered.

    6. In the input field, enter the value or text you want to find.
    The first GIS object found is marked.
    Tip: Alternatively you can select the desired entry from the list of GIS objects.
    7. If necessary, zoom into the network display by clicking the Autozoom button or by pressing
    ENTER.
    The network section is enlarged and the marked GIS object is positioned in the middle of the
    section.

    22.2.3

    Selecting GIS objects


    There are various ways to select GIS objects in order to edit them in another step.
    Finding a GIS object
    Selecting GIS objects
    Marking several GIS objects
    Setting GIS objects active/passive

    22.2.3.1

    Marking a GIS object


    1. In the Network window, click the

    Edit mode icon.

    2. Click the GIS objects button.


    3. Click the GIS object in the network.
    The GIS object is marked.
    Tip: You can also mark a GIS object in the network by searching for it (see "Finding a GIS
    object" on page 2212) or by selecting the corresponding row in the list of GIS objects
    (see "Working with lists" on page 2299).

    PTVGROUP

    2213

    22.2.3.2 Marking several GIS objects


    22.2.3.2

    Marking several GIS objects


    1. In the Network window, click the

    Edit mode icon.

    2. Click the GIS objects button.


    3. In the network, click the first GIS object that you want to mark.
    The GIS object is marked.
    4. Press the CTRL key and keep it pressed.
    5. Click all GIS objects you want to mark one by one.
    The GIS objects are marked.
    Tip: You can also mark multiple GIS objects in the network by selecting the corresponding rows in the list of GIS objects (see "Working with lists" on page 2299).
    22.2.3.3

    22.2.4

    Setting GIS objects active/passive


    Network objects can be active or passive. They are only active, if they are included in the spatial selection (see "Setting network objects active/passive via the spatial selection" on page
    1033) and comply with the current filter settings (see "Using filters to set network objects active
    or passive" on page 1008).

    Editing attribute values of GIS objects


    You can change the attribute values of one or multiple GIS objects.

    22.2.4.1

    Editing the attribute values of a GIS object


    To edit the values of a single GIS object, proceed as if you wanted to edit multiple GIS objects
    (see "Editing the attribute values of marked GIS objects" on page 2214).

    22.2.4.2

    Editing the attribute values of marked GIS objects


    1. Mark the desired GIS objects whose attribute values you want to edit (see "Marking several
    GIS objects" on page 2214).
    The selected GIS objects are marked.
    2. Press the ENTER key.
    The Multi-edit GIS: <Number> objects window opens.
    3. Edit the values of the desired attributes (see "Editing attribute values of network objects" on
    page 983).
    The attribute values are edited.
    4. Click the Close button.

    22.2.4.3

    Editing the attribute values of all or all active GIS objects


    Note: If there are no passive GIS objects in the network, all GIS objects are edited. Markings of GIS objects are ignored.

    2214

    PTVGROUP

    22.2.5 Setting graphic parameters for GIS objects


    1. If required, set the GIS objects active whose attribute values you want to edit via
    the spatial selection (see "Setting network objects active/passive via the spatial selection" on page 1033) and/or
    filter criteria (see "Using filters to set network objects active or passive" on page 1008).
    The selected GIS objects are active.
    2. In the Network window, right-click the GIS objects button.
    The GIS objects context menu opens.
    3. Select Multi-edit > All GIS objects.
    Note: You can also edit only the GIS objects of a certain category by selecting Multiedit > Category <Name>.
    The Multi-edit GIS objects window opens.
    4. Select whether you want to edit the attribute values of all GIS objects or just the active ones.
    Element

    Description

    Only active ones

    If this option has been selected, only active GIS objects are
    considered.
    If this option has not been selected, all GIS objects are considered.

    5. Select the Formula tab.


    6. Edit the values of the desired attributes (see "Editing attribute values of network objects" on
    page 983).
    The attribute values are edited.
    7. Click the Close button.

    22.2.5

    Setting graphic parameters for GIS objects


    If you are connected to a Personal Geodatabase, you can specify the following graphic settings for the display and labeling of GIS objects in the network.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select GIS Objects.

    PTVGROUP

    2215

    22.2.5 Setting graphic parameters for GIS objects

    3. Make the desired changes.


    Element

    Description

    Layer GIS

    If this option has been selected, GIS objects are displayed in the network.
    GIS category
    Here all GIS categories in the network are listed.
    Tip
    With the aid of the
    and
    buttons, you can edit the order of the
    drawn layers by marking the desired layer in the list. The top layer is
    drawn first.
    Draw
    For each category, you can switch the display on or off by selecting the
    respective category in the list.

    4. Make the required changes on the individual pages of the desired GIS categories.
    Tip: The settings are identical to those of active point objects (see "Displaying point
    objects in the network window" on page 2341).
    5. Confirm with OK.
    The GIS objects are displayed according to the chosen settings.

    2216

    PTVGROUP

    22.2.6 Output of GIS objects in lists

    22.2.6

    Output of GIS objects in lists


    Open the GIS objects list (see "Opening a list" on page 2299).

    The list opens. The GIS objects are displayed.


    Notes: All columns which are not disabled can be edited. Modifications are immediately
    saved to the database.
    You can limit the display to GIS objects of one category by selecting a GIS category in the
    list on the toolbar (see "Displaying GIS objects or POIs of one category only" on page
    2315).

    22.2.7

    Disconnecting a Personal Geodatabase


    1. From the File menu, choose Import> Disconnect Personal Geodatabase.
    A query opens.
    2. Confirm with OK.
    The Personal Geodatabase disconnects and the GIS objects are removed.
    Note: In the Personal Geodatabase the objects are retained.

    22.3

    Intersecting objects
    In Visum, you can intersect any network objects of the type point, line, or polygon that overlap
    spatially.
    Tip: You can also intersect GIS objects with other network objects, for example in order to
    create Visum attributes (see Fundamentals: Chpt. 10.3 , page 696).
    In the following example, the total number of boarding passengers at the stops of a zone is calculated and saved in the AddVal1 attribute.
    1. In the Network window, click the

    Edit mode icon.

    2. Right-click the Zones button.


    The Zones context menu opens.
    3. Select the Multi-edit entry.
    The Multi-edit zones window opens.
    PTVGROUP

    2217

    22.3 Intersecting objects


    4. In the Formula tab, select the AddValue 1 attribute.
    5. Click the Intersect button.
    The Generate attribute value by intersection with source attribute window opens.

    6. Make the desired changes.

    2218

    PTVGROUP

    22.3 Intersecting objects


    Element

    Description

    Target attribute
    (AddValue1)

    From the drop-down list, select how the target attribute values are
    calculated from the source attribute values. The aggregate functions that are available (and their effects) depend on the data
    types of source attribute and target attribute.
    Sum
    Sum of attribute values
    Mean
    Average of attribute values
    Count
    Number of attribute values
    Minimum
    smallest attribute value
    Maximum
    largest attribute value
    Concatenate
    The values of intersected attributes are separated by separator
    Histogram
    The occurrence of intersected attributes, separated by separator
    Weight the source attribute value with the share of the overlapping area of source object and target object in the source
    object
    If this option has been selected, for overlapping source and target objects, the source object attribute values are only considered
    proportionally. The share is calculated according to the size of the
    overlap. This is how the length of all links in a zone can be calculated for example.
    If this option has not been selected, for overlapping source and
    target objects, the given source object attribute values are considered. The size of the overlap is irrelevant This is how the number of a zone, where a link lies can be calculated, for example.

    Parameters for
    target objects

    PTVGROUP

    Intersect only active objects


    If this option has been selected, only active target objects are intersected.
    Network object
    Selected target network object
    Attribute
    Selected target attribute
    Buffer size
    Buffer size in meters

    2219

    22.3 Intersecting objects


    Element

    Description
    Note
    You can allocate a buffer to the selected object to intersect it.
    Thus you can, for example, intersect two point objects to which an
    area is allocated due to the buffer.

    Parameters for
    source objects

    Intersect only active objects


    If this option has been selected, only active source objects are
    intersected.
    Network object
    Specification of the origin network object (here Stops)
    Attribute
    Specification of the source attribute (here Passengers boarding)
    Tip
    If you select the 1.0 attribute, the number of source objects per target object will be counted.
    Buffer size
    Buffer size in meters
    Note
    You can allocate a buffer to the selected object to intersect it.
    Thus you can, for example, intersect two point objects to which an
    area is allocated due to the buffer.

    Sum up values?

    If this option has been selected, the value is added to the current attribute value.
    If this option has not been selected, the current attribute value
    is replaced by the input value.

    Cut

    If this option has been selected, all decimal places of the calculated value are dropped.
    Note
    The option is only available for attributes of the type integer.

    Round

    If this option has been selected, the calculated value is rounded.


    Decimal places up to and including four are rounded off, from five
    they are rounded up. This applies to negative numbers, too.
    Note
    The option is only available for attributes of the type integer.

    7. Confirm with OK.


    The number of boarding passengers at the stops is calculated.

    2220

    PTVGROUP

    22.4 The Shapefiles interface


    Notes: The resulting values of the intersected attribute are issued in the list of the target
    object.
    You can also intersect objects during a sequence of operations. To do so, from the Calculate menu, choose Procedure sequence, Miscellaneous procedure> Intersect (see
    "Setting up and starting the procedure sequence" on page 1847).

    22.4

    The Shapefiles interface


    Shapefiles are convenient when exchanging data with geographical information systems
    (GIS). Using the Shapefiles interface, you can read Shapefiles directly into Visum and save
    them in Visum(see Fundamentals: Chpt. 10.2 , page 692).

    22.4.1

    Importing Shapefiles
    When you import Shapefiles, the information contained in the Shapefile is read into a Visum
    network object. It depends on the type of Shapefile (point, polyline or polygon) and the read
    mode (additional or non-additional) into which network object the data is imported (see Fundamentals: Chpt. 10.2.1 , page 692).
    Notes: If you want to additionally read a Shapefile with coordinate information, you
    should make sure that the current network version contains a predefined coordinate system (see "Selecting a coordinate system" on page 2207).
    You can also read Shapefiles as background images into Visum(see "Using backgrounds in the network display" on page 2237).
    1. In the File menu, select the Import> Shapefile entry.
    The Open ESRI shapefile window opens.
    2. Select the desired file.
    3. Click the Open button.
    The Read shapefile window opens.
    Note: The options shown in the Read shapefile window depend on the type of shapefile to be imported (point, polyline or polygon).
    4. Make the desired changes.
    Shapefiles of type point
    Element

    Description

    Number of objects Number of point objects to be read


    in shapefile
    Read additively

    PTVGROUP

    If the option has been selected, the point objects and their data
    are read additionally to the existing network.

    2221

    22.4.1 Importing Shapefiles


    Shapefiles of type point
    Element

    Description
    Note
    The unit system used is the system specified for the existing network (see "Undoing and redoing actions" on page 870). Which
    coordinate system is used depends on whether the Shapefile contains coordinate system data and whether this data is different
    from the network data (see "Editing the coordinate system and
    scale" on page 2207).
    If the option has not been selected, a new network with the
    newly inserted point objects only will be created.

    Set coordinates of If this option has been selected, the point objects are read in as
    existing centroids new centroids of existing zones, main zones, main nodes, or territories. The polygons remain unchanged.
    Note
    This option is provided only if the option Read additionally has
    been selected.

    2222

    Read as

    From the drop-down list select the Visum target network object
    type into which the data are to be imported.
    Notes
    You can only select the POI network object type, if the option
    Read additionally is selected, the option Set coordinates of existing centroids is not selected, and if at least one POI category is
    defined for the network (see "Creating a POI category" on page
    1384).

    POI category

    From the drop-down list, select the POI category in which the
    point objects read in as POI shall be included.
    Note
    This option is provided only if the option Read additionally has
    been selected and POI is the chosen Visum target network object
    type.

    Key column

    From the drop-down list select which column of the shapefile


    shall be the key column for the allocation of the point objects to
    zones, main zones, main nodes, and territories.
    Note
    This option is provided only if the option Set coordinates of existing centroids has been selected.

    PTVGROUP

    22.4.1 Importing Shapefiles


    Shapefiles of type point
    Element

    Description

    Offset

    Optional value which is added to the respective ID of the point


    objects

    Imperial units

    If this option has been selected, imperial units are used for the
    data to be read in.
    If this option has not been selected, metric units are used for
    the data to be read in.
    Note
    This option is provided only if the option Read additionally has
    not been selected.

    Shapefiles of type polyline


    Element

    Description

    Number of objects Number of line objects to be read in


    in shapefile
    Read additively

    If the option has been selected, the line objects and their data
    are read additionally to the existing network.
    Note
    The unit system used is the system specified for the existing network (see "Undoing and redoing actions" on page 870). Which
    coordinate system is used depends on whether the Shapefile contains coordinate system data and whether this data is different
    from the network data (see "Editing the coordinate system and
    scale" on page 2207).
    If the option has not been selected, a new network with the
    newly inserted line objects only will be created.

    Node is starting
    point

    If this option has been selected, the connectors start at nodes,


    not at zones.
    If the option has not been selected, the connectors start at
    zones.
    Note
    The option Node is starting point is provided only if the option
    Read additionally has been selected and Connectors is the chosen Visum target network object type.

    Read as

    PTVGROUP

    From the drop-down list select the Visum target network object
    type into which the data are to be imported.
    Notes
    The Connectors network object type is provided only if the option

    2223

    22.4.1 Importing Shapefiles


    Shapefiles of type polyline
    Element

    Description
    Read additionally has been selected.
    The POI type of network objects is only available, if the option
    Read additionally is selected, and at least one POI category is
    defined for the network (see "Creating a POI category" on page
    1384).

    POI category

    From the drop-down list, select the POI category in which the line
    objects read in as POI are to be included.
    Note
    This option is provided only if the option Read additionally has
    been selected and POI is the chosen Visum target network object
    type.

    Key column for


    zones/nodes

    From the drop-down list, you can select a column of the shapefile
    as key for the allocation of the line objects read as connectors to
    the zones and nodes.
    Notes
    The option Key column for zones/nodes is provided only if the
    option Read additionally has been selected and Connectors has
    been selected as Visum target network object type.
    You cannot select the same column for zones and nodes.
    If you select no column for neither zones nor nodes, the data are
    determined by the snap radius.

    Create directed
    links

    If this option has been selected, a directed link is generated


    from a line object.
    If the option has not been selected, two links (both directions)
    will be generated from a line object.
    Note
    This option is provided only if Links has been selected as Visum
    target network object type.

    2224

    Offset

    Optional value which is added to the respective key attribute of


    the line objects
    Note
    This option is not provided if you read data as connectors.

    Snap radius

    Maximum permitted distance between the coordinates of several


    nodes so that they are interpreted as a single node.
    Of all nodes within this radius one single node is created.
    Note
    This option is provided only if you read data as links or connectors.

    PTVGROUP

    22.4.1 Importing Shapefiles


    Shapefiles of type polyline
    Element

    Description
    The units applicable to the value are the units used for the coordinates of the shapefile.

    Imperial units

    If this option has been selected, imperial units are used for the
    data to be read in.
    If this option has not been selected, metric units are used for
    the data to be read in.
    Note
    This option is provided only if the option Read additionally has
    not been selected.

    Zone -> Node


    Node ->Zone

    Transport systems
    Via this button you can select the transport systems in a separate
    window for which the respective direction of the connectors shall
    be open.
    Note
    If you do not select a transport system, the respective direction of
    the connectors is closed for all transport systems.
    Type
    Type of the respective connectors direction (see "Connectors:
    General attributes" on page 1161)
    Time
    Connector time of the respective connectors direction (see
    "Connectors: Transport systems tab" on page 1163)
    Notes
    These options are provided only if the option Read additionally
    has been selected and Connectors is chosen as Visum destination network object type.
    Both directions of a connector are always generated.

    Shapefiles of type polygon


    Element

    Description

    Number of objects Number of polygon objects to be read in


    in shapefile
    Read additively

    PTVGROUP

    If this option has been selected, the polygon objects and their
    data are read additionally to the existing network.
    Note
    The unit system used is the system specified for the existing network (see "Undoing and redoing actions" on page 870). Which

    2225

    22.4.1 Importing Shapefiles


    Shapefiles of type polygon
    Element

    Description
    coordinate system is used depends on whether the Shapefile contains coordinate system data and whether this data is different
    from the network data (see "Editing the coordinate system and
    scale" on page 2207).
    If the option has not been selected, a new network including
    the newly inserted polygon objects only will be created.

    Replace boundaries

    If this option has been selected, existing boundaries are replaced


    by the newly read-in boundaries.
    Note
    This option is provided only if the option Read additionally has
    been selected.

    Read as

    From the drop-down list select the Visum target network object
    type into which the data are to be imported.
    Note
    The POI type of network objects is only available, if the option
    Read additionally is selected, and at least one POI category is
    defined for the network (see "Creating a POI category" on page
    1384).

    Key column

    Use the drop-down list to select a column of the shapefile as key


    for the allocation of the newly read-in polygons to the existing
    Visum network objects.
    Note
    This option is provided only if the option Replace boundaries has
    been selected.

    POI category

    From the drop-down list, select the POI category in which the
    objects read in as POIs are to be included.
    Note
    This option is only provided if the option Read additionally has
    been selected and POI is chosen as Visum target network object
    type.

    Offset

    Optional value which is added to the respective key attribute of


    the polygon objects

    Imperial units

    If this option has been selected, imperial units are used for the
    data to be read in.
    If this option has not been selected, metric units are used for
    the data to be read in.
    Note
    This option is provided only if the option Read additionally has

    2226

    PTVGROUP

    22.4.1 Importing Shapefiles


    Shapefiles of type polygon
    Element

    Description
    not been selected.

    Normalize created
    If this option has been selected, all newly read polygons and
    and modified poly- all polygons modified through reading in, are normalized.
    gons (Self-interIf this option has not been selected, polygons are not norsecting test)
    malized.
    Notes
    Polygons have to be normalized, if for example you require the
    area or want to intersect the polygons. You do not have to normalize polygons to e.g. only show them in the background (see
    Fundamentals: Chpt. 3.5.2 , page 124).
    You can also normalize polygons later on (see "Normalizing all
    surfaces" on page 1052).
    Merge points with
    If this option has been selected, polygon points with the same
    coordinates are merged
    the same coordinates
    If this option has not been selected, polygon points are not merged.
    Notes
    This option makes sense, if the borders of communities are concerned for example. If two polygon points are merged, both polygons will automatically be modified by the shifted point.
    You can also merge polygon points later on (see "Merging all
    polygon points with identical co-ordinates" on page 1053).
    Fuzzy surface alignment

    If this option is selected, the imported surfaces are aligned to


    reflect the surfaces that already exist in the network. This prevents
    overlap of gaps between surfaces (see Fundamentals: Chpt.
    3.5.4 , page 127).
    Tolerance for imported surfaces
    Enter the tolerance value for fuzzy alignment. The value states
    the radius within which the points in the imported surface can be
    shifted towards the reference surface.
    Reference surfaces
    Use this button to open the Fuzzy surface alignment window in
    which you can configure further settings.
    Note
    This option is provided only if the Read additively option has
    been selected.

    5. Confirm with OK.

    PTVGROUP

    2227

    22.4.1 Importing Shapefiles


    When reading a shapefile additionally, the program checks whether the data on the coordinate system of the shapefile are the same as those of the existing network. Depending on
    the constellation either a warning or a window opens or the data are read from file without
    any further query.
    Coordinates
    Coordinates
    Response when read in
    data in the sha- data in the netpefile
    work
    None

    Visum (no pro- The coordinates are read without transformation.


    jection)

    None

    From proThe Select spatial reference system window


    jection file *.prj opens. Select the coordinate system of the shapefile via the from file option. Visum converts the
    coordinates of the shape file into the coordinates of
    the network. If you select the option Visum
    (untransformed reading) instead, the coordinates
    will be read from file without transformation. Confirm with OK.

    From projection
    file *.prj

    Visum (no pro- A warning is issued. Confirm with OK. The coorjection)
    dinates are read without transformation.
    Note
    To match the data, it is generally recommended to
    first change the coordinate system of the network
    (see "Selecting a coordinate system" on page
    2207).

    From projection
    file *.prj

    From proThe data are read without further queries. In case of


    jection file *.prj different coordinate systems the coordinates of the
    shapefile will be transformed into coordinates of the
    network.

    The Read attributes window opens.


    6. Make the desired changes.
    Element

    Description

    Column

    Order in which the attribute columns are read

    SourceAttributeID

    Codes of the attributes which are read


    Note
    The codes correspond to the column identifiers of the attribute file.

    Source data type Data type of the source attribute


    N: numeric
    C: character

    2228

    PTVGROUP

    22.4.1 Importing Shapefiles


    Element

    Description

    Target attribute

    Click this button to in a separate window select a target attribute


    (and a subattribute, if available) for each source attribute. The
    source attribute values are then read into the target attribute (see
    "The window used for the selection of one attribute" on page 963).
    Tip
    Alternatively, you can create a user-defined attribute as target attribute.
    Notes
    If no target attribute is selected for a source attribute, the attribute
    values of the source attribute are not read.
    If the same target attribute is selected for multiple source attributes,
    only the attribute values of the source attribute last read (highest
    column number of the same target attribute) is taken, whose value
    range corresponds to the value range of the target attribute.

    Target data type Data type of the selected target attribute


    New
    Edit

    Via the New button you can create a user-defined attribute as a target attribute for a source attribute in a separate window. Click the
    Edit button to change the settings of the user-defined attribute allocated (see "Managing user-defined attributes" on page 973).
    Note
    The button label changes from New to Edit, as soon as you allocate
    a source attribute to a user-defined attribute manually or via the
    Create button.

    Create

    Via this button you can create simultaneously user-defined attributes for all source attributes to which no target attribute is allocated. Visum uses the SourceAttributeID as a name for the new
    attribute.

    Notes: If you do not select Number as target attribute for point and polygon objects,
    ascending numbers will be created, starting with maximum key + 1.
    If for line objects read in as links one of the three required target attributes Number,
    From node number and To node number has not been selected, the necessary routing information is calculated by means of the snap radius.
    7. If line objects are read in as undirected links, select for each attribute how its value is to be
    read in.

    PTVGROUP

    2229

    22.4.2 Exporting Shapefiles


    Element

    Description

    Outward

    Direction From node - To node

    Reverse

    Direction To node - From node

    Undir. value

    50% of the value for each direction

    Symmetrical

    Equal value for both directions

    Note: In Visum the following applies to links:


    From node number < To node number
    Outward = From node - To node
    Reverse = To node - From node
    8. Confirm with OK.
    The shapefile is imported into Visum.
    Notes: If you read in line objects, all required yet non-existing nodes are created.
    If an object cannot be read in, the reading process is not aborted. The object will be skipped.
    Tip: To generate stop points from point objects, read point objects as nodes and then
    aggregate the isolated nodes to create stop points (see "Aggregating isolated nodes" on
    page 1076).
    Notes: The import of background data (e.g. land development) is not supported. However, they can be read as POIs.
    In shapefiles, several faces can form a surface. When you import Shapefiles, Visum supports several faces per surface (see Fundamentals: Chpt. 3.5 , page 120). All faces are
    inserted according to the Visum data structure. This also applies to polylines with several
    segments.

    22.4.2

    Exporting Shapefiles
    Note: This function is only provided with the GIS Interface Shape add-on module (see
    "Enabling or disabling installed add-ons" on page 886).
    1. In the File menu, select the Export> Shapefile entry.
    The Save ESRI shapefile window opens.
    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The Save shapefile(s) window opens.

    2230

    PTVGROUP

    22.4.2 Exporting Shapefiles


    Note: Network object types for which no network objects are defined in the network
    are disabled.
    4. Make the desired changes for each network object type.
    Element

    Description
    If the option of the left column has been selected, all objects or all
    active objects of the network object type are exported.

    Only active ones

    If this option has been selected, only active objects of the network object type are exported.
    If the option has not been selected, all objects of the network
    object type are exported.

    Directed

    If the option has been selected, a separate object per direction


    is exported.
    If the option has not been selected, only one object for both
    directions of a link is exported. The attributes of the outward direction keep their names; attributes of the reverse direction all start
    with the prefix "R_".
    Note
    The option Directed is provided only for the network object type
    Link.

    Node is starting
    point

    If this option has been selected, the connectors start at nodes,


    not at zones.
    If the option has not been selected, the connectors start at
    zones.
    Notes
    The option Node is starting point is provided only for the network
    objects type of Connectors.
    For each single object the attributes of both directions are always
    stored. Attributes of the reverse direction all begin with the prefix
    "R_" (see Fundamentals: Chpt. 10.2.2 , page 694).

    Columns

    PTVGROUP

    Via the button you can select the attributes you want to export per
    network object type. The selection is done in a separate window
    (see "The window used for the selection of multiple attributes" on
    page 968).

    2231

    22.5 Inserting additional information in the network display


    Element

    Description

    Read layout

    Click this button to read in a selection of attributes, defined per


    network object, from a list layout file *.lla (see "Saving a list layout" on page 2313). The attribute selection is displayed in the
    Attribute selection window and can be edited there (see "The
    window used for the selection of multiple attributes" on page
    968).

    POIs

    You can restrict the POI export to one category, if you select the
    desired category in the list.

    5. Confirm with OK.


    For each selected network object type three shapefiles are saved (*.shp, *.shx and *.dbf) as
    well as a *.ctf file containing renamed attribute identifiers. For each selected network object
    type a projection file *.prj with the currently set projection is saved, if deviating from the standard setting (Visum = no projection).
    Note: To show the resutls, open the Shapefiles in ArcView or ArcInfo.

    22.5

    Inserting additional information in the network display


    The following graphic objects are provided if you want to insert additional information, as for
    example labels or borders of areas, in your network:
    Texts
    Legend
    Polygons
    Backgrounds
    Note: Graphic objects are network-independent, i.e. they are not part of the network
    model and do not have any influence on the calculations carried out by Visum.

    22.6

    Using texts in the network display


    You can use texts to add labels to your network display (see Fundamentals: Chpt. 10.5 , page
    707).
    Note: Other labeling options can be found in the legend (see "Creating legends" on page
    2255), the graphic parameters of network objects (see "Specifying basic settings for the
    network window" on page 2337), and in the Print menu (see "Printing the network display" on page 2499).

    22.6.1

    Inserting background/legend text


    1. In the Network window, click the

    Insert mode icon.

    2. Click the Texts button.

    2232

    PTVGROUP

    22.6.2 Editing background/legend text


    3. Click the position in the network or the legend where you want to insert the alignment point
    of the text.
    The Insert background text window or the Insert legend text window opens.
    4. Enter the desired data (see "Background/legend text parameters" on page 2234).
    5. Confirm with OK.
    The text is inserted in the network display.

    22.6.2

    Editing background/legend text


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Texts button.


    3. Double-click the text you want to edit.
    The Edit background text or Edit legend text window opens.
    4. Make the desired changes (see "Background/legend text parameters" on page 2234).
    5. Confirm with OK.
    The changes are applied.

    22.6.3

    Shifting a text
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Texts button.


    3. Click the text you want to shift, hold down the mouse button and move the text to the desired position.
    Note: The text alignment is not changed by the shifting.

    22.6.4

    Rotating a text
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Texts button.


    3. Click the text you want to rotate.
    The text is highlighted.
    4. Click the text again that you want to rotate.
    Four double arrows are displayed around the highlighted text.

    PTVGROUP

    2233

    22.6.5 Copying and pasting a text


    5. Click one of the arrow heads as precisely as possible, hold down the mouse button and
    rotate the text to the desired position.
    Note: You can also specify an exact rotation angle (see "Background/legend text parameters" on page 2234).

    22.6.5

    Copying and pasting a text


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Texts button.


    3. Click the text you want to copy.
    The text is highlighted.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Copy entry.
    The text is copied and can be moved freely.
    6. Move the text to the desired position and click the left mouse button.
    The copied text is pasted at the desired position.

    22.6.6

    Background/legend text parameters


    Element

    Description

    Text

    Text content

    Font

    Via this button, you can select the font.

    Size

    Font size in mm
    Enter the absolute font size in mm
    Network co-ordinates
    If the option is selected, the entry in the Size field is converted to a
    number relative to the network scale. If you scale the network, Visum
    adapts the font size accordingly. If you change the unit back to millimeters, the current font size is converted to millimeters.
    Note
    The option is only available for background texts.

    Color

    From the list, you can select the text color.

    Alignment

    Specify alignment point of the text


    Notes
    When pasting, the text is aligned according to the settings here.
    When rotating the text, the alignment point is the pivot.

    2234

    PTVGROUP

    22.6.7 Deleting a text

    22.6.7

    Element

    Description

    Position

    Coordinates of the alignment point

    Angle

    Angle of rotation in degrees when rotating the text around the alignment point

    Deleting a text
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Texts button.


    3. Click the text you want to delete.
    The text is highlighted.
    4. Press the ENTER key.
    The text is deleted.

    22.6.8

    Editing the font size of background / legend texts


    1. In the Network window, click the

    Edit mode icon.

    2. Right-click the Texts button.


    A shortcut menu opens.
    3. Select the Scale text sizes entry.
    The Edit text size window opens.
    4. Make the desired changes.
    Element

    Description

    Edit background texts

    If this option has been selected, the size of all background texts is
    changed according to the selected settings.
    If this option has not been selected, the size of all background
    texts remains unaltered.

    Edit legend
    texts

    If this option has been selected, the size of all legend texts is changed according to the selected settings.
    If this option has not been selected, the size of all legend texts
    remains unaltered.

    Enlargement
    factor

    Factor by which the text size shall be changed


    Reduction
    Values between 0 and 1
    Enlargement
    Values above 1

    5. Confirm with OK.


    PTVGROUP

    2235

    22.6.9 Editing the font of background / legend texts


    The font size is changed according to the selected settings.

    22.6.9

    Editing the font of background / legend texts


    1. In the Network window, click the

    Edit mode icon.

    2. Right-click the Texts button.


    A shortcut menu opens.
    3. Select the Edit font style entry.
    The Edit font style window opens.
    4. Make the desired changes.
    Element

    Description

    Edit background texts

    If this option has been selected, the font of all background texts is
    changed according to the selected settings.
    If this option has not been selected, the font of all background texts
    remains unaltered.

    Edit legend
    texts

    If this option has been selected, the font of all legend texts is changed according to the selected settings.
    If this option has not been selected, the font of all legend texts
    remains unaltered.

    New font type

    Via this button, you can select the font.

    5. Confirm with OK.


    The font is changed according to the selected settings.

    22.6.10 Deleting all existing background / legend texts


    1. In the Network window, click the

    Edit mode icon.

    2. Right-click the Texts button.


    A shortcut menu opens.
    3. Select the Multi-delete entry.
    The Delete texts window opens.
    4. Make the desired changes.

    2236

    Element

    Description

    Delete background texts

    Via this option you can delete all background texts of the network display simultaneously.

    Delete legend
    texts

    Via this option you can delete all legend texts of the network display
    simultaneously.

    PTVGROUP

    22.6.11 Saving texts


    5. Confirm with OK.
    The selected texts are deleted.

    22.6.11 Saving texts


    Note: When saving the graphic parameters or the version, texts are equally saved.
    1. In the File menu, point at the Save as entry.
    2. Select Texts.
    The Save Texts window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The texts are saved.

    22.6.12 Reading texts


    1. In the File menu, point to Open.
    2. Select Texts.
    The Open Texts window opens.
    3. Select the desired text file.
    4. Click the Open button.
    The texts are read in from file.

    22.7

    Using backgrounds in the network display


    Backgrounds (for example city maps, Internet maps, master plan) allow you to improve the network display through additional, scaled graphical information. They thus enhance the descriptive quality. You have the possibility of directly inserting maps from files or Internet services
    into the network display.
    Dynamically embedding background maps provided on the Internet
    Statically embedding background maps provided on the Internet
    Creating a background from a file

    22.7.1

    Inserting background images of map services on the Internet


    For the network section currently displayed, you can automatically download road maps or
    aerial photos from the Internet. You can download freely accessible maps (see Fundamentals:
    Chpt. 10.5.4 , page 714) or maps provided by commercial providers, such as Microsoft Bing
    Maps (see Fundamentals: Chpt. 10.5.3.3 , page 710).

    22.7.1.1

    Dynamically embedding background maps provided on the Internet


    The graphics layer Background map dynamically embeds maps and images by map providers into your network. The map material is always reloaded when you change the

    PTVGROUP

    2237

    22.7.1.1 Dynamically embedding background maps provided on the Internet


    respective network section or open the network again. Visum then always uses the latest map
    material available. To dynamically embed a background image, you will need a permanent
    Internet connection as the map data are not saved. This has several advantages:
    You always use the most recent maps provided.
    You can exchange projects between computers without having to account for the directories of maps.
    You do not use up additional storage space on your computer for maps.
    1. Make sure a coordinate system is set for the opened network (see "Selecting a coordinate
    system" on page 2207).
    2. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    3. In the navigator, select Background map.
    4. Make the settings of your choice.
    Element

    Description

    Layer background Select this option to create and show a separate layer for the
    map
    background map. The layer is automatically displayed after you
    start Visum.
    Tip
    Alternatively, can activate or deactivate the layer. To do so, in the
    Network editor window, on the Graphic parameters toolbar,
    .
    click the Enable/disable background map button
    Note
    If you select the option and a white background is displayed instead of the map, click the Display entire network button

    2238

    Map service

    In the list box, click the Internet map service from which you want
    to download map material for your background map layer.
    Notes
    In the list box, Visum's default map services are shown that you
    have specified under Edit> User Preferences> GUI> Background map (see "Specifying default settings for inserting background maps" on page 2240).
    The entry Default map service <map service name> is used
    with Bing Maps (aerial images) and OpenStreetMap (Mapnik). If
    you do not have a license for Bing Maps, OpenStreetMap is used
    automatically.

    Color settings

    Color
    Select this option to display the background map in color.
    Gray scale

    PTVGROUP

    22.7.1.2 Statically embedding background maps provided on the Internet


    Element

    Description
    Select this option has been selected to show the background
    map in different shades of gray.

    Intensity

    Use the slider for stepless scaling of color intensity. This allows
    you to vary the way your network is depicted.

    Note: If no coordinate system is set for the network, a message is displayed saying
    that no backgrounds can be embedded from online sources. In this case, you can
    only load graphic files as background images (see "Inserting background images of
    map services on the Internet" on page 2237).
    5. Confirm with OK.
    The Internet maps are downloaded and shown in the network display as a separate graphics
    layer in the background.
    Note: The map service is addressed via a name that is specified in the Basic settings. If
    you pass on a version file used with a user-defined map service, make sure the map service is available under the same name on the other computers. You can ensure this by
    exchanging a user preferences file (see "Saving, opening and restoring user preferences" on page 869).
    22.7.1.2

    Statically embedding background maps provided on the Internet


    1. Make sure a coordinate system is set for the opened network (see "Selecting a coordinate
    system" on page 2207).
    2. Mare sure that the part of the network for which you want to download Internet maps is displayed in the Network editor window.
    Note: Internet maps are only downloaded for the network section visible in the Network editor window.
    3. In the Network window, click the

    Insert mode icon.

    4. Click the Backgrounds button.


    5. Click in the network display.
    Note: If no projection is set for the network, a message is displayed saying that no
    backgrounds can be embedded from online sources. In this case, you can only load
    backgrounds from files (see "Inserting background images of map services on the
    Internet" on page 2237).
    The Create background window opens.
    6. Select the Internet maps option.
    PTVGROUP

    2239

    22.7.1.3 Specifying default settings for inserting background maps


    7. In the list box, click the map material of your choice.
    Note: Here the entries are displayed that are specified in the default settings (see
    "Specifying default settings for inserting background maps" on page 2240). Additional, user-defined map services can be used.
    Element

    Description

    OpenStreetMap
    (Mapnik)

    If this option has been checked, Slippy Maps are downloaded


    which were rendered with Mapnik.

    OpenStreetMap
    (CycleMap)

    If this option has been checked, OSM maps are downloaded


    which highlight bicycle paths and other items which are especially interesting for bikers.

    Bing Maps (aerophoto)

    If this option is checked, you will download aerial images provided by Bing Maps.

    8. Using the scroll bar you can set the desired zoom level.
    Notes: Using the zoom level, you specify the detail level of the map material provided
    by the map service. The more detailed you want the background to be, the more tiles
    will be downloaded. If you click on the Preview button, the maps are displayed
    without closing the Create background window.
    9. To download freely accessible maps, confirm the reference to the map provider's license
    terms and conditions.
    10. Confirm with OK.
    The Internet maps are downloaded and inserted in the network display as a background.
    22.7.1.3

    Specifying default settings for inserting background maps


    Besides the default map services embedded in Visum, you may add additional map services
    to Visum. You may use map services to dynamically or statically embed background maps.
    The default entries in blue font cannot be deleted or edited.
    Adding user-defined map services for background maps
    1. From the Edit menu, choose User Preferences.
    2. In the navigator, click GUI> Background map.
    3. Then click the

    symbol.

    The Create map service window opens.


    4. Make the settings of your choice.

    2240

    PTVGROUP

    22.7.1.3 Specifying default settings for inserting background maps


    Element

    Description

    Name

    Unique map service name

    URL template

    URL template for the map service, including prefix for its service
    type:
    http(s):// for Web Map Services (WMS)
    tile:// for map services that provide maps as tiles in
    various zoom levels (tile service).
    You have to use wildcards with the URL template that are automatically replaced with data when you download the maps.
    The following wildcards are required in the URL template of Web
    Map Services:
    %WIDTH% und %HEIGHT% for the image size in pixels
    %LEFT%, %TOP%, %RIGHT% and %BOTTOM% for the
    image section
    The following wildcards are required in the URL template of Map
    Tile Services:
    %TX, %TY% for the tile index
    %TZ% for the zoom index
    %TQUAD% for the quadkey, if used by the Map Tile Service.
    Note
    Quadkeys are used for economic indexing of tiles of various
    zoom levels in databases. Microsoft Bing Maps, e.g., uses
    quadkeys.
    %SUBDOMAIN% if required for alternative subdomains of
    the map service. If you want to use this wildcard, the Subdomain list box must contain entries.

    Subdomains

    Comma-separated list of subdomains available


    Note
    Many map services provide alternative URLS that are addressed
    by a URL prefix or suffix. Use cases for this are e.g. parallel URL
    download or omission of a URL.

    Projection

    Display of the coordinate system of the map service. Click this button to set a different coordinate system. If the Map Tile Service
    coordinate system and Visum network coordinate system are not
    compatible, you first have to download the tiles and then transform them into the Visum coordinate system format, in order to
    show the background map. OpenStreetMap and Bing Maps use
    WGS 84 - pseudo-Mercator (adapted EPSG 3857).
    Note
    The map is shown in tiles, if you ensure that the coordinate systems of the map service and Visum are the same.

    PTVGROUP

    2241

    22.7.1.3 Specifying default settings for inserting background maps


    Element

    Description

    Confirming license To download background maps from some map services, you first
    terms and conneed to confirm their license terms and conditions of use.
    ditions of use
    Testing map service

    Click this button to check whether your settings are correct. Visum
    then tries to download a background map in the appropriate
    zoom level. for the network section selected. If this is not possible
    for the current network section, Visum tries to download a default
    section to exclude the possibility that the network section you
    selected is invalid.

    5. Confirm with OK.


    The default settings are applied.
    Editing user-defined map services for background maps
    1. From the Edit menu, choose User Preferences.
    2. In the navigator, click GUI> Background map.
    3. In the table, click the map service you want to edit.
    4. Click the

    symbol.

    The Edit map service window opens.


    5. Make the desired changes (see "Adding user-defined map services for background maps"
    on page 2240).
    6. Confirm with OK.
    The map service is changed.
    Deleting user-defined map services for background maps
    1. From the Edit menu, choose User Preferences.
    2. In the navigator, click GUI> Background map.
    3. In the table, click the map service you want to delete.
    4. Click the

    icon.

    5. Confirm with OK.


    The map service is deleted.

    2242

    PTVGROUP

    22.7.2 Creating a background from a file

    22.7.2

    Creating a background from a file


    Notes: Visum supports various graphic formats, e.g. *.emf, *.bmp, *.wmf, *.gif, *.jpg, *.
    png, *.psd, *.tif, *.tga, *.dwg, *.dxf, *.ecw, *.jp2, *.shp, *.sid, *.svg, *.sgi, *.pct (see Fundamentals: Chpt. 10.5.3 , page 709).
    If there is a control file *.bgr for a background, the background is inserted automatically at
    the position specified in the control file and does not have to be positioned manually.
    If there is a World control file for backgrounds in *.tif, *.jp2, *.sid or *.ecw format, the background is automatically inserted at the position specified in the control file and does not
    have to be positioned manually. You can create World files for backgrounds displayed in
    the network (see "Generating world file" on page 2251).
    For backgrounds in *.shp or *.dxf format you are asked whether or not the graphics shall
    be inserted at the position specified in the file.
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Create background window opens.
    4. Select the Graphics file option.
    5. Confirm with OK.
    The Open background window opens.
    6. Select the desired background file.
    7. Confirm with OK.
    8. With the mouse pointer click the position at which the upper left corner of the background
    shall be placed, hold down the mouse button and draw a frame downward and to the right
    in the required size of the background.
    Note: The length to breadth ratio of the background is kept.
    The background is inserted in the required size, at the desired position, or at the position specified in a control file (see Fundamentals: Chpt. 10.5.3 , page 709).
    Notes: You can insert an unlimited number of backgrounds in a network.
    Visum saves graphic files in version and graphic parameters files only by reference. For
    this reason, referenced graphic files should not be deleted, renamed or moved to a different directory.
    Backgrounds are inserted as links. If you rename or move a background file, it will not be
    found when opening the version the next time. In that case change the path for backgrounds to the new directory under File> Project directories.

    PTVGROUP

    2243

    22.7.3 Editing the drawing order of backgrounds

    22.7.3

    Editing the drawing order of backgrounds


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. Make sure that the Drawing order tab has been selected.

    Note: The table of backgrounds shows the drawing order. Backgrounds further up in
    the table may cover the backgrounds further down.
    5. Make sure that the desired background is selected from the table of backgrounds.
    6. Select one of the following functions.
    Element

    Description
    Moves the background one position up
    Moves the background one position down

    The drawing order is changed accordingly.

    22.7.4

    Showing and hiding backgrounds


    1. In the Network window, click the

    2244

    Edit mode icon.

    PTVGROUP

    22.7.5 Editing a background manually


    2. Click the Backgrounds button.
    3. Click in the network display.
    The Background objects administration window opens.
    Element

    Description

    Draw

    If this option has been selected, the corresponding background is displayed.


    If this option has not been selected, the corresponding background is
    not displayed.
    Tip
    Via the Check all/Uncheck all buttons you can select or remove all
    backgrounds simultaneously.

    4. Click the Close button.


    The corresponding backgrounds are shown or hidden according to your selection.

    22.7.5

    Editing a background manually


    You can shift, rotate, enlarge, and reduce backgrounds.
    Note: Depending on the file format not all editing functions are applicable.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. Make sure that the desired background is selected from the table of backgrounds.
    5. Click the

    Change to mouse mode icon.

    The Background objects administration window closes and the Mouse mode window
    opens. Four squares at the corners and four double arrows are displayed around the selected background.

    6. The following functions are provided.


    Note: All changes are applied immediately.

    PTVGROUP

    2245

    22.7.6 Measuring links with the scale


    Element

    Description

    Shift

    Click in the selected background, hold down the mouse button and
    move the background to the desired position.

    Rotate (around Click one of the arrow heads as precisely as possible, hold down the
    the centre of
    mouse button and rotate the background to the desired position.
    the display)
    Notes
    You can only roate background of the formats *.bmp, *.emf, *.wmf,
    *.gif, *.jpeg, *.jpg, *.jpe, *.png, *.tiff, *.tif, and *.icon that are no larger
    than 5000 5000 pixels.
    You can also specify an exact rotation angle (see "Editing a background" on page 2247).
    Enlarge/reduce Click one of the four squares at the corners, hold down the mouse butproportionally ton and drag the mouse until the background has the desired size.
    Note
    The length to breadth ratio of the background is kept.
    Shrink

    Note
    The original length to breadth ratio of the background is changed
    (shrinking).
    While holding down the C TRL key, click one of the squares, hold
    down the mouse button and drag the mouse until the background
    takes the desired proportions.

    7. In the Mouse mode window, click the OK button.


    The Mouse mode window closes and the Background objects administration window
    opens.

    22.7.6

    Measuring links with the scale


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. Click the Scale button.
    The Background objects administration window closes and the mouse pointer turns into
    a scale.
    5. Click the starting point of the link to be measured, hold down the mouse button and drag
    the mouse pointer to the desired end point of the link to be measured.
    The Scale window opens.

    2246

    PTVGROUP

    22.7.7 Editing a background


    Element

    Description

    Distance

    Length of the measured link

    6. Confirm with OK.


    The Scale window closes and the Background objects administration window opens.

    22.7.7

    Editing a background
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. Make sure that the desired background is selected from the table of backgrounds.
    5. Click the Edit button.
    The Background objects window opens.

    6. Make the desired changes.


    Element

    Description

    File name

    Display of the file name of the selected background

    Image size

    Display of the original size of the background file

    Use tie points

    If this option has been selected, you can position the background using tie points.

    PTVGROUP

    2247

    22.7.7 Editing a background


    Element

    Description

    Top left

    Specify coordinates for upper left corner of the image


    Note
    If you have selected the option Use tie points, you can define
    the Top/Left tie point (see "Setting a tie point" on page 2249).

    Drop-down list

    From the list, select the desired method by means of which you
    want to define the size of the background. Depending on the
    selection the corresponding text boxes are displayed.

    Size = factor *
    image size

    The Factor section is displayed.


    Note
    Reduction: Values between 0 and 1
    Enlargement: Values above 1
    Proportional enlargement/reduction: Enter the same value in either box
    Horizontal
    Factor by which the breadth of the background is to be changed.
    Vertical
    Factor by which the height of the background is to be changed.

    Point Bottom/Right

    The section Bottom/Right is displayed.


    Define coordinates of the lower right corner of the image
    Note
    If you have selected the Use tie points option, you can define the
    Bottom/Right tie point (see "Setting a tie point" on page 2249).

    Absolute size

    The Extension section is displayed.


    Horizontal
    Breadth of background in network coordinate units
    Vertical
    Height of background in network coordinate units

    Rotate

    Angle in degree by which the background is to be rotated anticlockwise around the center of the display

    Transparency

    If this option has been selected, you can select the color contained in the background which is to be displayed transparently
    via the Transparent color field.
    If this option has not been selected, none of the background
    colors is displayed transparently.

    7. Click the OK button.


    The changes are applied and the Background objects window closes.

    2248

    PTVGROUP

    22.7.7.1 Setting a tie point


    22.7.7.1

    Setting a tie point


    1. Make sure that the Background objects window is open and the Use tie points option is
    selected for the background to which you want to add a tie point (see "Editing a background" on page 2247).
    2. Click the

    icon.

    The Tie point window opens.


    Note: Tie points have to lie within the background graphics.
    3. Click the desired position within the background graphics.
    The tie point coordinates are displayed in the Tie point window.
    Note: You can specify the position as often as necessary by clicking in the background graphics until you can accept the coordinates.
    4. Confirm the tie point coordinates with OK.

    22.7.8

    Editing backgrounds of type shape


    If you have inserted backgrounds of the type Shapefile, you can edit them as described below.
    Notes: All backgrounds of the type shape are displayed in one row of the Background
    objects administration window.
    The separate shapefile layers permit a transparent display of backgrounds.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. In the list, select the Shapefile layer row.
    5. Click the Layer button.
    The Extra layers window opens. All opened shapefile backgrounds are displayed in this
    window.
    6. Make the desired changes.
    Element

    Description

    Draw

    If this option has been selected, the respective layer is drawn.

    File name

    Name of the shapefile

    Line style

    Line width in mm

    PTVGROUP

    2249

    22.7.9 Deleting backgrounds


    Element

    Description
    Note
    You can edit the line width directly in the window.

    Color: Line

    In a separate window, you can select the color of the line style properties of the selected layer by clicking in the respective field.

    Color: polygon

    In a separate window, you can select the color for the polygon of the
    selected layer by clicking in the respective field.
    You can change the drawing order of the layers. Select the desired
    layer and use the icons to shift it one position up or down. The top layer
    is drawn first.

    Delete

    Use the button to delete the selected shapefile.

    Add

    Use this button to read further backgrounds of the type shape.

    7. Confirm with OK.


    The layers are displayed as desired.

    22.7.9

    Deleting backgrounds
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. Make sure that the desired background is selected from the table of backgrounds.
    5. Click the Delete button.
    The selected background is deleted immediately.

    22.7.10 Saving a background


    Backgrounds cannot be saved separately. It is, however, possible to save the entire current
    network display or the current screen display as a postscript, DXF file, JPG file, or SVG file
    (see "Printing the network display" on page 2499).
    The respective file includes all network objects and network-independent graphic objects of
    the print area.
    To backgrounds applies:
    When loading a background with a corresponding *.bgr file anew, the *.bgr file has to be
    located in the same directory as the background file. The object is inserted in the position
    specified in the control file.
    If you edit the position of a background for which a *.bgr file exists, the *.bgr file is deleted.
    No *.bgr files are saved for newly inserted backgrounds objects.
    Position data of background objects are saved with the version file.
    2250

    PTVGROUP

    22.7.11 Generating world file

    22.7.11 Generating world file


    You can generate a position file for a background file as described below.
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Backgrounds button.


    3. Click in the network display.
    The Background objects administration window opens.
    4. Make sure that the desired background is selected from the table of backgrounds.
    5. Click the World file button.
    For the selected background, a *.tfw file named like the background is generated and saved in
    the same directory as the background file.

    22.8

    Using polygons in the network display


    You can insert polygons as rectangles, lines, or polygons, hereby specifying their properties
    (for example with or without filling, fill style, line type, and color of boundary, fill color, fill style
    pattern).

    22.8.1

    Creating a rectangle
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Polygons button.


    3. With the mouse pointer click the position at which the upper left corner of the rectangle shall
    be positioned, hold down the mouse button and draw a frame downward and to the right in
    the required size of the rectangle.
    The Create polygon window opens.
    4. Select the desired option.
    Option

    Description

    Closed

    Rectangle with boundary and filling

    Open

    Rectangle with boundary but no filling

    5. Confirm with OK.


    The polygon is inserted into the network display.

    22.8.2

    Creating lines/polygons
    1. In the Network window, click the

    Insert mode icon.

    2. Click the Polygons button.

    PTVGROUP

    2251

    22.8.3 Editing the properties of a closed polygon


    3. While holding down the C TRL key, specify the starting point and the intermediate points of
    the line/polygon per mouse click.
    4. Release the C TRL key and specify the end point of the line/polygon per mouse click.
    The Create polygon window opens.
    5. Select the desired option.
    Option

    Description

    Closed

    Polygon with boundary and filling


    Note
    If you have drawn a line and select the option, the starting and
    end point of the line are connected to a polygon and its face is filled.

    Open

    Polygon with boundary but no filling

    6. Confirm with OK.


    The polygon is inserted into the network display.

    22.8.3

    Editing the properties of a closed polygon


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Polygons button.


    3. Double-click the desired polygon.
    The Edit polygon window opens.
    4. Make sure that the option Closed has been selected.
    5. Click the field of the fill color next to the Closed option.
    The Filling and boundary window opens.
    6. Make the desired changes.
    Section

    Description

    Fill style

    Fill color
    Select the desired color of the filling.
    Fill style
    Select the desired fill style pattern.
    Line distance
    Specify the desired line distance of the fill style pattern in mm.

    Boundary

    2252

    No boundary
    If the option has been selected, a boundary is not displayed.

    PTVGROUP

    22.8.4 Editing the properties of an open polygon


    Section

    Description
    Color like fill color
    If this option has been selected, the color of the filling is used for the
    boundary, too.
    Margin color
    If the option Color like fill color has not been selected, you can select
    the desired color for the boundary here.
    Line style
    In the list box, click the desired line style for the boundary.

    Preview

    Preview showing the edited filling and boundary

    7. Confirm with OK.


    The changes are applied.

    22.8.4

    Editing the properties of an open polygon


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Polygons button.


    3. Double-click the desired polygon.
    The Edit polygon window opens.
    4. Make sure that the option Open has been selected.
    5. Click the box of the fill color next to the Open option.
    6. The Color / Line style window opens.
    7. Make the desired changes.
    Element

    Description

    Color

    From the drop-down list select, the desired color for the boundary.

    Line style

    In the list box, click the desired line style for the boundary.

    Preview

    Preview showing the edited color and line style

    8. Confirm with OK.


    The changes are applied.

    22.8.5

    Shifting a polygon
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Polygons button.

    PTVGROUP

    2253

    22.8.6 Copying and pasting a polygon


    3. Click the polygon you want to shift, hold down the mouse button and move the polygon to
    the desired position.

    22.8.6

    Copying and pasting a polygon


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Polygons button.


    3. Click the polygon you want to copy.
    The polygon is highlighted.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Copy entry.
    The polygon is copied. It is freely movable.
    6. Move the polygon to the desired position and click the left mouse button.
    The copied polygon is pasted at the desired position.

    22.8.7

    Deleting a polygon
    1. In the Network window, click the

    Edit mode icon.

    2. Click the Polygons button.


    3. Click the polygon you want to delete.
    The polygon is highlighted.
    4. Press the ENTER key.
    The polygon is deleted.

    22.8.8

    Deleting all polygons


    1. In the Network window, click the

    Edit mode icon.

    2. Click the Polygons button.


    3. Make sure that no polygon is highlighted.
    4. Right-click in the network display.
    A shortcut menu opens.
    5. Select the Multi-delete entry.
    The Delete polygons window opens.
    6. Select the desired options.

    2254

    PTVGROUP

    22.8.9 Saving polygons


    Element

    Description

    Delete background polygons

    Via this option you can delete all background polygons of the network display simultaneously.

    Delete legend
    polygons

    Via this option you can delete all legend polygons of the network display simultaneously.

    7. Confirm with OK.


    The selected polygons are deleted.

    22.8.9

    Saving polygons
    Note: When saving the graphic parameters or the version, polygons are equally saved.

    22.9

    Creating legends
    You can create a legend with additional explanations and descriptions of objects (see Fundamentals: Chpt. 10.5.2 , page 708).
    Notes: The legend is available in the Network editor and in the schematic line diagram.
    You can create one legend per window at most.
    If the graphic parameters or the scale are changing, the legend will be updated automatically.
    You can also edit the legend in the Preview

    22.9.1

    display.

    Inserting legends
    1. On the toolbar, click the Edit legend symbol

    Tip: Alternatively, from the Graphics menu, choose > Legend.


    The Legend parameters window opens.
    2. Click Draw legend.
    Note: When you click the Preview button, the legend is displayed with the current settings, without the Legend parameters window being closed.
    3. In the Legend items tab, make the settings of your choice.

    PTVGROUP

    2255

    22.9.1 Inserting legends


    Element

    Description

    Available items

    Click this button to view the list of available legend items. To


    select the items, click the
    and
    buttons. To add multiple
    elements at the same time, press the C TRL key.
    Click the
    symbol to automatically choose a list of the items
    displayed.
    Note
    When you click the symbol, a window opens that allows you to
    either display all items active in the graphics parameters, or only
    those items that are active and have corresponding network
    objects in the network.

    Items displayed in
    the legend

    Click this button to view the items displayed in the legend and
    the respective headings they are grouped by.
    In the Items displayed in the legend list, click the item of your
    choice and use the symbols to move it to the top or bottom. This
    is how you specify the sequence in which the items are displayed.

    Number of columns Number of columns the legend items are displayed in.

    2256

    PTVGROUP

    22.9.1 Inserting legends


    Element

    Description

    Preview

    Basic preview showing in which columns the items are organized


    Note
    In the Items displayed in the legend list, the items selected are
    highlighted in the preview.

    Legend item parameters

    In the Items displayed in the legend section, select an item to


    edit its display settings. The settings available depend on the
    item type selected.
    The following settings can be made for different types of objects:
    Heading
    Into the box, enter a heading for the respective legend item.
    View passive objects
    Select this option to also show passive objects.
    Use layer order
    Select this option to use the layer order specified for classical (=
    conventional) display of graphic parameters to draw objects.
    Show no diagram
    Select this option to not show a diagram.
    View only diagram filling
    Select this option to show diagram fillings for the selected object
    in the legend.
    View fill style and scaling
    Select this object to show the diagram fillings and scaling of the
    selected object in the legend.
    Symbol width/symbol height
    Dimensions for the display in the legend in mm
    Note
    For objects that can be point or polygon objects, this entry refers
    to polygon objects only, as point objects have a fixed size.
    Line symbol/area symbol
    In the list box, click the symbol of your choice to show lines/areas of the selected object.
    Show bar filling/bar scaling
    Select this option to show the bar filling and scaling of the selected object in the legend.
    Draw point symbol/area symbol only - Show point symbol/area symbol
    Here you can specify whether objects that can be both point and

    PTVGROUP

    2257

    22.9.1 Inserting legends


    Element

    Description
    area symbols are shown as point symbols, area symbols or both
    in the legend.

    4. In the Layout tab, make the settings of your choice.


    Element

    Description

    Boundary

    In a separate window, you can specify a line style for the legend
    border (see "Setting parameters for the line style" on page
    2365).

    Background color

    Here you choose a background color for the legend.

    Alignment

    Use the symbols to specify the alignment of the legend in your


    view or print page layout:
    Bottom right
    Bottom left
    Top right
    Top left

    Margins

    Specifies the width of margins in mm

    Spacing between

    Specifies the spacing between legend items in mm


    Note
    The currently edited spacing is highlighted in color in the preview.

    Preview

    Shows a preview with all specified spacings.


    Note
    The preview is exemplary and does not reflect the settings made
    in other tabs. It contains the example of a footer and a scale.

    5. In the Text layout tab, make the settings of your choice.


    Section

    Description

    Title text

    Here you enter the title of the legend.

    Alignment of title

    Using the symbols, you can specify the alignment of the title:
    Left aligned
    Centered
    Right aligned

    Font settings

    In this section, you can specify a font, a size in mm, and a color
    for the elements selected.

    Preview

    Shows a preview of the text layout

    6. In the Footer tab, make the settings of your choice.

    2258

    PTVGROUP

    22.9.1 Inserting legends


    Section

    Description

    View footer texts

    Select this option to show footer text in the legend.


    Note
    If this option is not selected, the following options in the Legend
    parameters window are grayed out.

    Footer columns 1-3 Here you can make settings for the section below the legend.
    Column width
    Column format for the texts below the legend
    You can regulate the width of each column by entering a percentage.
    Notes
    The total need not amount to 100%. The width will be calculated proportionately.
    You can position the column contents left aligned, centered or
    right aligned by clicking the respective icon below.
    Row 1/Row 2
    Via the drop-down lists you can select auto texts, user-defined
    texts or graphics, which are inserted in two rows in up to three
    columns below the legend.
    user-defined
    Here you can enter a text of your choice into the empty field.
    empty
    If this entry is selected, the respective field is displayed
    empty.
    Help for auto
    values

    PTVGROUP

    Use the button to open a window with all available auto values.
    Note
    The entries in squared brackets are pre-defined by the program
    (auto values). They are replaced with the current values when
    drawing the print frame. Auto values are language dependent
    and can also be used as user-defined entries.
    If you want to display an [image], enter a comma and the path to
    the image. Example: [graphics, D:\logo.bmp]

    2259

    22.9.2 Editing the legend


    Section

    Description

    Height of images in Here you can enter the desired height of an image you want to
    the footer
    insert into the legend.
    Note
    In the list box, click [Graphics], in order to insert an image into
    the legend. In the list box, click the path to the image of your
    choice.
    View graphical
    scale

    Select this option to show a scale.


    Notes
    You can specify whether the scale is shown Above the footer
    text or Below the footer text.
    You can further align the scale left, right or center it.

    7. Confirm with OK.


    The legend is inserted according to your settings.

    22.9.2

    Editing the legend


    1. On the toolbar, click the Edit legend symbol

    The Legend parameters window opens.


    2. Make the desired changes (see "Inserting legends" on page 2255).
    3. Confirm with OK.
    The changes are applied.

    22.9.3

    Hiding the legend


    1. On the toolbar, click the Edit legend symbol

    The Legend parameters window opens.


    2. Deactivate the Draw legend option.
    3. Confirm with OK.
    The legend is hidden.
    Tip: Alternatively, you can deactivate the option Draw legend under Graphics> Edit
    graphic parameters> Layer.

    22.9.4

    Opening and saving legend parameters


    The parameters of a legend can be saved separately and reopened in a file of the format *.lgd.

    22.9.4.1

    Saving legend parameters


    1. Make the desired settings for the legend (see "Inserting legends" on page 2255).

    2260

    PTVGROUP

    22.9.4.2 Opening legend parameters


    2. In the File menu, point to Save as.
    3. Select Legend parameters.
    The Save legend parameters window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The legend parameters are saved.
    22.9.4.2

    Opening legend parameters


    1. In the File menu, point to Open.
    2. Select Legend parameters.
    The Open model template window opens.
    3. Open the desired file.
    4. Click the Open button.
    The legend parameters are loaded.

    22.10

    GPS tracking
    If a GPS receiver is connected to your PC, you can display the current position in the network
    diagram (see Fundamentals: Chpt. 10.6 , page 714).
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select Working environment> GPS tracking.

    3. Make the desired changes.


    PTVGROUP

    2261

    22.10.1 Setting graphic parameters for the GPS signal


    .

    Element

    Description

    GPS tracking is
    active

    If this option has been selected, the functionality is activated.

    No. of the COM port


    receiving the GPS
    signal

    Specification of the number of the COM port


    Tip
    Under Windows you will find the number in the Start menu
    under Control panel > System > Hardware > Device manager.

    Baud rate

    Specification of the baud rate of the GPS mouse


    Note
    The standard setting is 4800.

    Time interval in
    seconds after
    graphical position
    update

    Enter the desired time interval.

    4. Confirm with OK.


    GPS tracking is activated.
    Notes: You can shift the network display to the current GPS position (center of the
    screen) at a constant zoom level by clicking the
    Center GPS signal icon or by activating the function via menu View> Center GPS signal.

    22.10.1 Setting graphic parameters for the GPS signal


    You can specify the graphic display of the GPS signal as follows.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select GPS tracking.

    2262

    PTVGROUP

    22.10.1 Setting graphic parameters for the GPS signal

    3. Make the desired changes.


    Element

    Description

    Draw GPS
    tracking

    If this option has been selected, a GPS signal is drawn.


    Here you can specify how the GPS signal is depicted.
    In the drop down list, you can select one of the following symbols:
    Circle
    Square
    Triangle
    Open arrow
    Cross
    Stop German
    Stop English
    POI
    SC
    Stop sign
    Two-way stop / Two-way yield
    Roundabout
    Size
    Size in mm
    Color
    You can select the color of the GPS signal in a separate window

    PTVGROUP

    2263

    22.10.1 Setting graphic parameters for the GPS signal


    Element

    Description
    by clicking in the field.
    Sign
    If you select the Circle or Square symbol, you can activate the
    input field. To do so, select the check box. In the input field, you
    can enter a sign which will be displayed inside the circle or
    square. You can specify the color of the GPS signal in a separate
    window by clicking in the color field.

    4. Confirm with OK.


    The GPS signal is displayed according to the settings.

    2264

    PTVGROUP

    23 Settings for interactive analyses

    23

    Settings for interactive analyses


    Visum offers various functionalities that allow you to evaluate your traffic and transport model
    interactively (see Fundamentals: Chpt. 11 , page 716).
    Subjects
    Displaying flow bundles
    Displaying isochrones and the accessibility of network objects
    Searching for and displaying shortest paths

    23.1

    Displaying flow bundles


    Flow bundles are used to filter and graphically display loaded paths (obtained through assignment) according to various criteria (see Fundamentals: Chpt. 11.1 , page 716).
    The flow bundle shows volumes based on the paths found that meet the flow bundle conditions.
    Notes: Flow bundles can only be displayed if paths are stored during the assignments.
    The flow bundle results can also be output as a list (see "Limiting the path list display to a
    selection" on page 2316)
    If a PrT-assignment was calculated with blocking back model, the volumes for links, turns
    and connectors can differ from the actual volumes (e.g. volume PrT [Veh] (AP)), as traffic
    jams are not included in path volumes. Flow bundles therefore represent the filtered part
    of the volumes for links, turns and connectors (e.g. Volume PrT Demand [Veh] (AP)).

    23.1.1

    Inserting a flow bundle


    You insert a flow bundle by specifying the network objects via which the paths shall lead (see
    Fundamentals: Chpt. 23.1.1 , page 2265).
    1. In the Graphics menu, select the entry Flow bundle.
    The Graphics tools (Flow bundle) window opens, and the Flow bundle tool is active.
    2. In the list specify the desired flow bundle conditions:
    You can select network objects via which the paths shall lead (see "Setting a network
    object as flow bundle condition" on page 2266).
    You can specify the filter conditions that account for the status (active or passive) of the
    network objects and traffic type (see "Filtering paths via active and passive network
    objects and traffic types" on page 2271).
    You can define how you want multiple filter conditions combined (see "Linking flow
    bundle conditions with AND THEN and OR" on page 2273 and "Putting AND THEN
    flow bundle conditions into brackets" on page 2274).
    3. If required, make further changes in the Graphics tools (Flow bundle) window.

    PTVGROUP

    2265

    23.1.1.1 Setting a network object as flow bundle condition


    Element
    New service group

    Description
    Click this button to add an OR link (see "Linking flow bundle conditions with AND THEN and OR" on page 2273).
    Via the button you can delete the selected row from the list.

    Delete
    You can change the sequence of rows within a group linked by AND
    Move down- by selecting the desired row and clicking the corresponding button.
    wards /
    Move upwards
    Initialize

    Via this button you can delete the list of objects and all previously
    executed flow bundles.

    Alternative rou- If this option has been checked, first all paths will be identified which
    tes
    meet the conditions selected. Origin-destination relations are identified in the next stage. Finally, all paths with this type of origin-destination pair are selected. They, however, do not meet the conditions
    selected (see Fundamentals: Chpt. 23.1 , page 2265).
    Note
    If, for example, 60% of all trips of an OD pair traverse the marked
    link S, then the alternative routes comprise the trips found for the
    remaining 40% of this OD pair.
    Insert link bars
    if required

    If this option has been selected, a matching bar with flow bundle
    volumes will be inserted automatically when executing the flow
    bundle, if none exists yet.
    Notes
    If a matching bar already exists, the settings of the reference bar are
    applied to the new bar.
    The graphic parameters are always adjusted in such a way that the
    flow bundle bar is visible.

    4. Click the Execute symbol

    All paths which correspond to the filter settings will be identified. You can display them in a list
    and visualize the volumes as a flow bundle according to the graphic parameters selected (see
    "Displaying flow bundles in lists" on page 2277 and "Setting graphic parameters for the display of flow bundles" on page 2275).
    23.1.1.1

    2266

    Setting a network object as flow bundle condition


    You can set a network object as flow bundle criterion. In this case, the flow bundles will only
    be based on paths which lead or do not lead via this network object, depending on the settings.

    PTVGROUP

    23.1.1.1 Setting a network object as flow bundle condition


    1. Make sure the Graphics tools (Flow bundle) window is open and the graphics tool Flow
    bundle is activated.
    2. If applicable, click the row after which you want to insert a new flow bundle criterion.
    Notes: If no row has been highlighted, the new row will be inserted at the end of the
    list.
    A new criterion with a selected network object will be automatically linked to the previous criterion by selecting the criterion AND THEN. Instead you can also specify an
    OR link (see "Linking flow bundle conditions with AND THEN and OR" on page
    2273).
    3. Make the desired changes in the upper section.
    Element

    Description

    Term type

    PrT, PuT, PuT-Sys


    Here you can select the type of transport system.
    Notes
    Only transport systems for which an assignment was calculated are
    available.
    If the transport system PuT has been selected, you can display flow
    bundle volumes of the headway-based or timetable-based assignment.
    If the transport system PuT-Sys is selected, you can display volumes of
    the transport system-based assignment.

    Network
    object selection

    In the list, click the type of network object you want to specify. The following types are provided:
    Zone
    Node
    Main zone
    Main node
    Link
    Stop point (just for transport system PuT)
    Stop area (just for transport system PuT)
    Stop (just for transport system PuT)

    4. In the network, click on the desired object of the selected network object type.

    Note: If on the toolbar, the


    Click only active objects button is activated, you cannot
    use the mouse to select passive network objects (see "Marking only active network
    objects" on page 1005).
    A new row for the selected object is displayed in the Graphics tools (Flow bundle) window.
    5. Specify further options for the new row, if required.

    PTVGROUP

    2267

    23.1.1.1 Setting a network object as flow bundle condition


    Element

    Description

    Concatenation

    Click this button to specify the conditions for path selection. The button
    is labeled with the option selected. Click the button to switch between
    the options.
    First/And then
    For the first condition of a new group of flow bundle conditions, the
    option is First. For the following conditions, it is And then.
    If for the condition the option First/And then is selected, all paths are
    selected that fulfill the condition.
    Not/And then not
    For the first condition of a new group of flow bundle conditions, the
    option is Not. For the following conditions, it is And then not.
    If for the condition the option Not/And then not is selected, all paths
    are selected that do not fulfill the condition.
    Note
    If there are several conditions linked by And then, a condition only
    applies for the segment between the previous and next condition.

    Condition

    Display network object that is highlighted in the network.

    Condition

    Click the button to open the Edit flow bundle term window. In the window, you can change further settings for flow bundle conditions.
    Demand segments tab
    You can select the demand segments for all network objects.
    Supply tab
    You can select the PuT supply for PuT network objects (see
    "Using PuT network objects to make settings for flow bundle conditions" on page 2269).
    Passenger types tab
    You can specify the passenger type for PuT network objects (see
    "Using PuT network objects to make settings for flow bundle conditions" on page 2269)
    Traffic types tab
    You must define for (main) zones whether to take origin traffic or
    destination traffic, or both, into consideration.
    You must define the traffic type for filter conditions that you have
    specified using either the Active links or Active lines button (see
    "Filtering paths via active and passive network objects and traffic
    types" on page 2271)

    column

    6. Confirm with OK.


    The flow bundle criterion is now specified.

    2268

    PTVGROUP

    23.1.1.2 Using PuT network objects to make settings for flow bundle conditions
    23.1.1.2

    Using PuT network objects to make settings for flow bundle conditions
    For PuT network objects only passenger type and PuT supply can be reduced further. For
    example, you select boarding passengers for a specific line only. Or you select transfers from
    one operator to another. Various combined flow bundle calculations, for example, of boarders
    and changers, or alighters and changers at stops, are also possible.
    1. Make sure that the Graphics tools (Flow bundle) window is open.
    2. Select a row with the PuT network objects stop, stop point or stop area and click the
    ton in the Condition column.

    but-

    The Edit flow bundle term window opens.


    3. Select the Passenger types tab.
    4. Make the desired changes.
    Element

    Description

    Origin boardings

    If this option has been selected, all passengers boarding at the


    selected network object are taken into account.

    Destination alightings

    If this option has been selected, all passengers alighting at the


    selected network object are taken into account.

    Transfers

    If this option has been selected, all passengers alighting at the


    selected network object are taken into account.

    'Through' pasIf this option has been selected, all through passengers without
    sengers with stop stops at the selected network object are taken into account.
    event
    'Through' passengers without
    stop event

    If this option has been selected, all passengers alighting at the


    selected network object are taken into account.

    5. Select the Supply tab.


    6. Make the desired changes.
    Notes: The left panel in the window is for destination alighters, alighting passengers
    prior to changing, and for through passengers. The right panel is relevant for source
    boarders and for boarding passengers after changing. For transfers enter the conditions for the PuT services used by the passengers arriving at the network object. In
    the right-side pane you enter the conditions for the PuT services used by the passenger to continue his/her trip.
    Both columns of the window are always displayed; only options that are relevant to
    the selected traffic types are available.

    PTVGROUP

    2269

    23.1.1.2 Using PuT network objects to make settings for flow bundle conditions
    Element

    Description

    Drop-down list

    Use the drop-down list to select the public transport supply for which
    you want to set the condition.

    List

    Go to the list and select the network objects that have to be run by the
    selected network object.

    Also PuT-Walk
    Select this option to also include paths using a transport system of
    the type Walk at the selected network object.
    TSys
    Notes
    For a zone of the traffic type Origin traffic, for example, all paths,
    which use a PuT walk link after the origin connector node will be
    taken into account, irrespective of the following PuT path leg.
    For transfers, also all paths using a PuT walk link after or before the
    transfer are taken into account.
    If this option has not been selected, only paths which use the
    selected PuT supply at the selected network object will be taken into
    account.
    Note
    For districts of the traffic type Origin traffic only paths whose first PuT
    path leg uses the selected PuT services will be taken into account. A
    PuT walk link may precede.
    For transfers only paths which include path legs using the selected
    PuT supply directly before or after the transfer will be taken into
    account. There must be no PuT walk link in-between.
    Also PuT-Aux
    TSys

    Select this option to also include paths using a transport system of


    the type PuT-Aux at the selected network object.
    If this option has not been selected, paths with an additional transport system before or after the selected network object will not be
    taken into account.

    Display only
    supply at ...

    If this option has been selected, only the transport services operating at the selected network object will appear in the list.
    Note
    This option for example applies to all flow bundles via nodes or links
    and for flow bundles via stop points, stops and stop areas for which
    transfers are not regarded.
    If this option has been selected, the entire transport supply will be
    displayed in the list.
    In some cases ((main) zone flow bundle, stop point/stop/stop area
    flow bundle for transfers) lines may be relevant that do not operate
    directly at the selected network object, but can be reached via a footpath.

    All active

    2270

    Use this button to select the active network objects which are
    currently displayed in the list.
    PTVGROUP

    23.1.1.3 Filtering paths via active and passive network objects and traffic types
    7. Confirm with OK.
    The settings are applied.
    23.1.1.3

    Filtering paths via active and passive network objects and traffic types
    In the flow bundle display, you can filter paths by a traffic type (Internal traffic, Origin traffic, Destination traffic, Through trips, External trips, or Bypassing internal trips). To do so, set links or
    objects of the line hierarchy active or passive (see Fundamentals: Chpt. 11.1.2 , page 721).
    The following two examples illustrate the settings for traffic type-based flow bundles.
    Displaying through trips using a flow bundle
    In the following example, all paths which traverse at least one inner city link between start and
    end at an external zone are filtered with the aid of a traffic type-based flow bundle.
    1. Set the desired links within the inner city to active (see "Using filters to set network objects
    active or passive" on page 1008).
    2. Set the desired links within the external zone to passive.
    3. In the Graphics menu, select the entry Flow bundle.
    The Graphics tools (Flow bundle) window opens.
    4. Select the traffic type PrT below Term type.
    5. Click on the Active links button.
    Note: The option is available only if there are passive links in the network.
    A new Active links row is inserted.
    6. Click the

    icon in the Condition column.

    The Edit flow bundle term window opens.


    7. In the Traffic types tab, select the Through traffic type.
    8. Deselect the other options.
    Note: You can set several options as active, however not all at once.
    Element

    Description

    Internal trips

    Filters paths which only use active objects

    Origin demand

    Filters paths which start with an active object

    Destination
    demand

    Filters paths which end with an active object

    Through traffic

    Filters paths which start or end with a passive object and use at
    least one active object in-between

    PTVGROUP

    2271

    23.1.1.3 Filtering paths via active and passive network objects and traffic types
    Element

    Description

    External trips

    Filters paths which do not use active objects

    Bypassing internal trips

    Filters paths which start and end with an active object and use at
    least one passive object in-between

    9. Confirm with OK.


    The settings are applied.
    10. Insert further filter criteria, if required.
    11. Click the Execute symbol

    The flow bundle filters the Through traffic.


    Notes: Visum saves the information on which links are active during the flow bundle execution. A status that was subsequently changed in the network will be indicated by red
    text and a quick info in the Graphics tools (Flow bundle) window.
    You can display the volumes graphically in the network (see "Setting graphic parameters
    for the display of flow bundles" on page 2275) oder in der Liste anzeigen (see "Displaying flow bundles in lists" on page 2277).
    Displaying internal traffic with a flow bundle for active time profiles
    You can filter paths by the status of the lines used (active/passive). The program then takes
    into account which path legs are used by an active or passive line. In the following example,
    the filter determines all passengers which use long-distance trains on all path legs.
    1. Set all long-distance lines to active (see "Working with hierarchical filters" on page 1016).
    2. In the Graphics menu, select the entry Flow bundle.
    The Graphics tools (Flow bundle) window opens.
    3. Select the traffic type PuT below Term type.
    4. Click the Active lines button.
    Note: This option is available, if at least one object of the line hierarchy is passive and
    at least one other object is active (see "Working with hierarchical filters" on page
    1016).
    A new Active lines row is inserted.
    5. Click the

    icon in the Condition column.

    The Edit flow bundle term window opens.


    6. In the Traffic types tab, select the Internal trips type.
    Note: This option filters paths which use active objects only.

    2272

    PTVGROUP

    23.1.1.4 Linking flow bundle conditions with AND THEN and OR


    7. Deselect the other options.
    8. In the Filtering tab, select the Active lines option.
    9. Confirm with OK.
    10. Click the Execute button.
    The flow bundle filters the Internal trips.
    Notes: Visum saves the information on which network objects are active during the flow
    bundle execution. A status that was subsequently changed in the network will be indicated by red text and a quick info in the Graphics tools (Flow bundle) window.
    You can display the volumes graphically in the network (see "Setting graphic parameters
    for the display of flow bundles" on page 2275) oder in der Liste anzeigen (see "Displaying flow bundles in lists" on page 2277).
    23.1.1.4

    Linking flow bundle conditions with AND THEN and OR


    You can specify several conditions for a flow bundle. You can combine these conditions using
    AND THEN and OR. This means that you could e.g. combine PrT and PuT conditions (see Fundamentals: Chpt. 11.1.4 , page 725).
    Linking flow bundle conditions with AND THEN
    This flow bundle describes all paths from origin to destination which traverse all marked network objects in exactly the order in which they were marked.
    In the following example, the filter determines the volumes of the links listed in the Flow bundle
    window.
    1. In the Graphics menu, select the entry Flow bundle.
    The Graphics tools (Flow bundle) window opens.
    2. Select the desired traffic type below Term type.
    3. Select the network object type Link.
    4. In the network, click on the desired link.
    The selected object is shown in the table in the Graphics tools (Flow bundle) window with
    the listed First link.
    5. In the network, click the next desired link.
    The Graphics tools (Flow bundle) window lists the object and connects it with the previous
    object via the And then term.
    6. If required, select further objects for the flow bundle to traverse.
    7. If required, make further changes in the Graphics tools (Flow bundle) window (see "Inserting a flow bundle" on page 2265).
    8. Click the

    PTVGROUP

    Execute symbol.

    2273

    23.1.1.4 Linking flow bundle conditions with AND THEN and OR


    The volumes on the paths which traverse all selected links are determined.
    Putting AND THEN flow bundle conditions into brackets
    To ensure that the flow bundle is calculated correctly, you can put the flow bundle conditions
    into brackets.
    Brackets can only be set if at least three rows with flow bundle conditions have been defined
    and at least two of them are linked by And then. Nested brackets cannot be defined.
    1. Make sure that the Graphics tools (Flow bundle) window is open and at least three flow
    bundle conditions have been defined.
    2. In the Graphics tools (Flow bundle) window, select the rows you want to put in brackets. To
    do so, hold down the C TRL button and successively click on at least two entries listed below
    one another in the Condition column.
    The rows with the flow bundle conditions are highlighted.
    3. Click the

    Put into brackets button.

    4. If needed, click on the entry And then in the Combination column to change it to the opposite And then not. The change applies to the entire term in brackets. You cannot change
    the current settings for individual elements within the brackets.
    The selected flow bundle conditions are placed in brackets and the brackets are shown in the
    Condition column of the corresponding rows. Selected terms are displayed with brackets.

    Tips: To remove the brackets, select one of the conditions and click the
    Remove
    brackets button.
    To shift a bracket upwards or downwards, mark the particular row and click the corresponding icon

    or

    Combining flow bundle conditions with an OR term


    If you insert an OR term, the series of AND THEN terms ends. You can then add additional conditions. A flow bundle describes all paths that fulfill at least one of the filter conditions linked to
    an OR operation.
    In the following example we search for paths which either traverse two selected stops or
    nodes.
    1. In the Graphics menu, select the entry Flow bundle.
    The Graphics tools (Flow bundle) window opens.
    2. Select the desired traffic type below Term type.
    3. Select the desired network object type.
    4. Select the two network objects for the first condition in the network.

    2274

    PTVGROUP

    23.1.2 Setting graphic parameters for the display of flow bundles

    5. Click the

    New term button.

    An OR link is inserted in the Graphics tools (Flow bundle) window.


    6. Select the two network objects for the second condition in the network.
    7. If required, make further changes in the Graphics tools (Flow bundle) window (see "Inserting a flow bundle" on page 2265).
    8. Click the

    Execute symbol.

    The paths are calculated and displayed as flow bundle.

    23.1.2

    Setting graphic parameters for the display of flow bundles


    You can define the following graphics parameters for flow bundles:
    You can specify how the network objects, which have been selected for the flow bundles,
    are displayed.
    You can specify how the flow bundle bars are displayed.
    Editing the display of selected network objects
    You can specify a color for the network objects marked for the flow bundle.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Flow bundles entry.
    3. Make the desired changes.
    Element

    Description

    Display of selected flow bundle


    objects

    Color flow bundle objects


    You can specify the color of the selected network objects in a
    separate window by clicking in the color field.
    Use object filing color for labels
    If the option has been selected, the color which is used to display the bars is also used for the labels of the selected objects.
    If the option has not been selected, you can specify a color for
    the labels of the selected objects in the Color field.
    Use separate text color
    Via this button, you can specify a color for the labels of the objects
    selected in the network.

    4. Confirm with OK.


    The objects marked for the flow bundle are displayed according to your chosen settings.

    PTVGROUP

    2275

    23.1.2 Setting graphic parameters for the display of flow bundles


    Setting the display of flow bundle bars
    You can display flow bundle volumes as bars. These bars are drawn over the corresponding
    standard volume bars and not next to them.
    Note: You can insert flow bundle bars manually or automatically while calculating the
    flow bundle (see "Inserting a flow bundle" on page 2265).

    1. From the Graphics menu, choose Edit graphic parameters.


    The Edit graphic parameters window opens.
    2. In the navigator, select the Links > Bars > Display entry.

    3. Enter a bar.
    2276

    PTVGROUP

    23.1.3 Displaying flow bundles in lists


    4. In row ScaleAttrID, select the Volume Flow bundle PrT/PuT attribute.
    Note: Flow bundle bars are displayed together with their reference bar. The following
    bars are considered reference bars:
    Volume flow bundle PrT - Volume [Veh] PrT (AP)
    Volume flow bundle PuT - Volume [Pers] PuT (AP)
    Volume flow bundle TSys - Volume-TSys [Pers] (for PuT-Sys)
    or Volume TSys [Veh] (for PrT-Sys)
    If a matching reference bar exists, a query opens.
    5. In this case, decide if the graphic parameters of the flow bundle bars shall be automatically
    adjusted to the settings of the reference bar.
    The new column for the flow bundle bar is inserted. The new column and the reference bar
    may include a reference note to the other bar in the Related bar row. The flow bundle bar is
    always displayed on the right side of its reference bar.
    6. Specify any further settings you need.
    Notes: The settings are the same as those for link bars (see "Displaying properties via
    bars" on page 2367).
    You should specify the same scaling for the flow bundle bar and for the corresponding reference bar.
    In the preview only half width of the flow bundle bar is displayed in the upper section
    of the window so that the reference bar below remains visible.
    7. Confirm with OK.
    The flow bundle bars are displayed according to your chosen settings.

    23.1.3

    Displaying flow bundles in lists


    You can show flow bundles in the lists PrT paths and PrT path links.
    The PrT path list and the PrT paths on link level list
    1. Open the PrT path links list (see "Opening a list" on page 2299).
    2. In the tool bar, select the Flow bundle routes entry in the drop down list.

    The flow bundle routes are displayed in the list.


    Displaying flow bundle attributes
    You can also indicate flow bundle values by displaying the following attributes in the respective list.

    PTVGROUP

    2277

    23.1.4 Saving flow bundle volumes


    List

    Attribute

    Links

    Volume flow bundle PrT/PuT


    Volume flow bundle-TSys

    Turns,
    Main turns

    Volume flow bundle PrT/PuT

    Zones, Main zones Origin traffic flow bundle PrT/PuT


    Destination traffic flow bundle PrT/PuT
    Connectors

    Volume flow bundle PrT/PuT

    Stop points - basis, Passengers boarding flow bundle AH/AP


    Stops
    Passengers alighting flow bundle AH/AP
    Passengers transferring total flow bundle AH/AP
    Line route items,
    Time profile items

    23.1.4

    Volume flow bundle AH/AP

    Saving flow bundle volumes


    You can save your current flow bundle settings as follows:
    With graphic parameters, as a *.gpa file (see "Saving the graphic parameters of the network window" on page 2496).
    Note: If you read the graphic parameters file of a different network, the flow bundle
    results are discarded if they do not match the current network.
    As an attribute file *.att, for the desired list type (see "Importing and exporting list contents"
    on page 2325).
    As a flow bundle matrix, with the help of the Save demand matrix from route volumes
    procedure (see "Saving partial matrices during the execution of the procedure sequence"
    on page 1739).
    With the version, as a *.ver file (see "Opening and saving a version file" on page 840).
    Note: Flow bundle results are saved with the version and automatically loaded when reopening the file. Flow bundles are only recalculated when reading in older version files or
    separate graphics parameter files.

    23.2

    Displaying isochrones and the accessibility of network objects


    You have several possibilities to display the accessibility of network objects:
    Isochrones are lines, as on a chart or map, with the same time value. Starting at one or
    multiple network objects, they show the accessibility of each single point in the network
    (see Fundamentals: Chpt. 11.2 , page 732).
    You can display all network objects of one type classified according to their accessibility
    starting from selected network objects. For example you can use a color ramp to visualize
    the accessibility of all nodes from the currently selected zones.

    2278

    PTVGROUP

    23.2.1 Displaying isochrones and accessibility in PrT


    In PrT you can assign colors to links in accordance with their accessibility from marked network objects.
    Note: The accessibility of network objects can be displayed simultaneously in the network for both PuT and PrT (see Fundamentals: Chpt. 11.2.3 , page 740). For example,
    you can assign colors to links in accordance with their accessibility in PuT (see "Displaying the accessibility of links" on page 2281) and display PrT isochrones at the same
    time (see "Displaying PuT isochrones" on page 2285).

    23.2.1

    Displaying isochrones and accessibility in PrT


    With PrT, you have several possibilities to display the accessibility of network objects in the network:
    PrT isochrones display the accessibility of each point in the network from one or several
    marked nodes, main nodes, or zones.
    You can display links according to their accessibility from currently marked nodes, main
    nodes, or zones.
    You have the possibility to display nodes, main nodes, or zones classified according to
    their accessibility from currently marked network objects and use the Isochrones times
    PrT attribute for the classification.
    Note: You can use all display types all at the same time.

    23.2.1.1

    Displaying PrT isochrones


    1. In the Edit graphic parameters window, under 2D display, make the desired settings (see
    "Setting graphic parameters for the display of isochrones" on page 2288).
    Note: To show PrT isochrones, in the 2D display section, select Draw (see "Setting
    graphic parameters for the display of isochrones" on page 2288).
    2. In the Graphics menu, select the entry Isochrones.
    The Isochrones window opens.
    3. Select the PrT tab.
    4. Specify any further settings you need.

    PTVGROUP

    2279

    23.2.1.1 Displaying PrT isochrones


    Element

    Description

    Choice criterion

    Here you can select the choice criterion.


    tCur
    In-vehicle time in the loaded network
    t0
    In-vehicle time in the unloaded network
    Distance
    Link length
    Impedance
    Impedance according to the assignment parameters
    AddValue 1...3
    Attributes with user-defined values

    Unlimited search

    If this option is selected, the Route choice criterion is not limited.

    Cancel search
    when maximum
    value is reached

    If this option is selected, you can specify a maximum value for the
    Route choice criterion selected. The shortest path search is canceled when this value is reached. This saves computing time.

    Maximum value

    Entry field for the maximum value of the route choice criterion.
    Notes
    This field is only available, if the Cancel search when maximum
    value is reached option is selected.
    Press the button to start isochronous computation.
    Note
    This field is only available, if the Cancel search when maximum
    value is reached option is selected.

    Transport system Here you can select the transport system.


    Drop-down list for Here you select the network object type from which you want to
    network object type measure the distances.
    Nodes
    Main nodes
    Zone
    5. Depending on the network object type you selected, in the network click the nodes, main
    node or zone you want.

    Note: If on the toolbar, the


    Click only active objects button is activated, you cannot
    use the mouse to select passive network objects (see "Marking only active network
    objects" on page 1005).
    The distances between the selected network object and all points in the network are displayed according to your color settings.

    2280

    PTVGROUP

    23.2.1.2 Displaying the accessibility of links

    Note: The colors correspond to the graphic parameter settings in the Classification
    section, under 2D display (see "Setting graphic parameters for the display of isochrones" on page 2288).
    6. If required, click further nodes, main nodes, or zones.
    Tips: You can undo your selection by clicking a selected object again.
    You can select network objects of different object types simultaneously. To achieve
    this, change in the Isochrones window the entry in the network object type dropdown list.
    The colors visualize the distance to the next selected network object type.
    Notes: In isochronous mode, you can use the functions from the Network editor window's toolbars without leaving the isochrones.
    You can also switch off the display by clicking the Initialize button.
    23.2.1.2

    Displaying the accessibility of links


    1. In the Edit graphic parameters window, under 2D display page, in the Classification section, make the desired settings (see "Setting graphic parameters for the display of isochrones" on page 2288).
    Note: If you want to display the accessibility of links only (not of PrT isochrones), in the
    2D display section, deactivate the Active option (see "Setting graphic parameters for
    the display of isochrones" on page 2288).
    2. Make sure the Isochrones PrT layer is activated (see "Editing the display and order of drawing settings for graphic layers" on page 2339).
    3. In the Graphics menu, select the entry Isochrones.
    The Isochrones window opens.

    PTVGROUP

    2281

    23.2.1.2 Displaying the accessibility of links

    4. In the drop-down list, select the entry PrT.


    5. Specify any further settings you need.
    Element

    Description

    Choice criterion

    Here you can select the choice criterion.


    tCur
    In-vehicle time in the loaded network
    t0
    In-vehicle time in the unloaded network
    Distance
    Link length
    Impedance
    Impedance according to the assignment parameters
    AddValue 1...3
    Attributes with user-defined values

    Transport system Here you can select the transport system.


    Drop-down list for Here you select the network object type from which you want to
    network object type measure the distances.
    Node
    Main node
    Zone
    6. Depending on the network object type you selected, in the network click the nodes, main
    node or zone you want.
    Note: If on the toolbar, the
    Click only active objects button is activated, you cannot use the mouse to select passive network objects (see "Marking only active network objects" on page 1005).
    2282

    PTVGROUP

    23.2.1.3 Displaying the accessibility of network object types in PrT according to classes
    The distances between the selected network object and all link sections are displayed
    according to your color settings.
    Notes: The colors correspond to the graphic parameter settings in the Classification
    section, under 2D display (see "Setting graphic parameters for the display of isochrones" on page 2288).
    The line width of links depends on the line style settings made for the links selected
    (see "Displaying marked line objects" on page 2358).
    7. If required, click further nodes, main nodes, or zones.
    The colors of the links visualize the distance to the next selected network object type.
    Tip: You can undo your selection by clicking a selected object again.
    8. Click the Close button.
    Notes: The isochrones will still be displayed if you exit the window via Close.
    You can switch off the display by clicking the Initialize button.
    23.2.1.3

    Displaying the accessibility of network object types in PrT according to classes


    You can visualize the accessibility of nodes, main nodes, or zones of a selected network
    object. To achieve this, you use the Isochrones time PrT attribute to classify a network object
    type.
    Notes: The settings for zones, nodes, and main nodes are nearly identical. Here they are
    illustrated using the example of zones.
    You can define the classified display for several different network objects types at the
    same time.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Zones > Display > tab Active.
    3. Select the option Classified drawing mode.
    4. Via the button, select the attribute Isochrones time PrT.

    PTVGROUP

    2283

    23.2.1.3 Displaying the accessibility of network object types in PrT according to classes

    5. Insert the desired classes (see "Displaying classified objects based on attribute values" on
    page 2411).
    Tip: In the Text window pane you can specify for each class, how the network object
    are to be labeled. For example, here you can select Isochrones time PrT. Then for
    each zone the time period is displayed in which it can be reached.
    6. Confirm with OK.
    7. In the Graphics menu, select the entry Isochrones.
    The Isochrones window opens.
    8. In the drop-down list, select the entry PrT.
    9. Make any further settings required (see "Displaying the accessibility of links" on page
    2281).
    10. In the network display click the network object you want.
    The zones are displayed in the classified drawing mode. The display visualizes the distances from the selected network object to all zones in the network.
    11. If desired, click on further network objects.
    The classified drawing mode visualizes the distances to the closest selected network
    object.
    12. Click the Close button.

    2284

    PTVGROUP

    23.2.2 Displaying isochrones and accessibility in PuT


    Notes: The isochrones will still be displayed if you exit the window via Close.
    You can switch off the display by clicking the Initialize button.

    23.2.2

    Displaying isochrones and accessibility in PuT


    You can show the accessibility of PuT-relevant network objects (see Fundamentals: Chpt.
    11.2.2 , page 736).
    There are two possibilities of displaying the accessibility in the network.
    PuT isochrones display the accessibility of each point in the network from one or several
    marked zones, stop areas, or nodes.
    It is possible to use the classified drawing mode for nodes, main nodes, zones, stops, stop
    areas, and stop points to display their accessibility from the currently marked network
    objects.

    23.2.2.1

    Displaying PuT isochrones


    1. In the Edit graphic parameters window, under 2D display, make the desired settings (see
    "Setting graphic parameters for the display of isochrones" on page 2288).
    Note: PuT isochrones are only displayed, if in the 2D display section, Active is selected (see "Setting graphic parameters for the display of isochrones" on page 2288).
    2. In the Graphics menu, select the entry Isochrones.
    The Graphics tools (Isochrones) window opens.
    3. Select the PuT tab.
    4. Make the required changes.
    Element

    Description

    Mode

    Here you can select a PuT mode.

    Departure time

    If this option has been selected, you will search for connections
    that start within the specified time period and end before expiry of
    the extension period.

    Arrival time

    If this option has been selected, you will search for connections
    that start after the pre-extension time has started and arrive at the
    destination within the specified period of time.

    Time period: from Time period for the desired arrival or departure times of the rele- to
    vant connections.
    Notes
    When using a weekly or a daily calendar, you can select a day
    which is contained in the current calendar.
    For zones, the access time needs to be taken into account.

    PTVGROUP

    2285

    23.2.2.1 Displaying PuT isochrones


    Element

    Description

    Extension

    Time following the specified time period within which connections


    need to reach their destinations.

    Pre-extension

    Period of time before the specified time during which connections


    must start

    Drop-down list for


    PuT procedure

    Here you can select a PuT procedure.


    Note
    Currently, you can only select the timetable-based procedure.

    Drop-down list for Here you select the network object type for which you want to disnetwork object type play the isochrones.
    Note
    You can select zones, stop areas or nodes.
    Parameters

    Click this button to specify the settings for the connection search
    (see "Parameters of timetable-based assignment" on page 2021).
    Note
    In this window you can e.g. specify that only active vehicle journey sections will be taken into account.

    5. Depending on the network object type you selected, in the network click the zone, stop
    area, or node you want.

    Note: If on the toolbar, the


    Click only active objects button is activated, you cannot
    use the mouse to select passive network objects (see "Marking only active network
    objects" on page 1005).
    6. Click the Execute button.
    The distances between the selected network object and all points in the network are calculated and displayed as isochrones.
    Note: The colors correspond to the graphic parameter settings in the Classification
    section, under 2D display (see "Setting graphic parameters for the display of isochrones" on page 2288).
    7. If needed, click any further zones, stop areas, or nodes.
    Tips: You can undo your selection by clicking a selected object again.
    You can select network objects of different object types simultaneously. To achieve
    this, change in the Isochrones window the entry in the network object type dropdown list.
    8. Click the Execute button.

    2286

    PTVGROUP

    23.2.2.2 Displaying the accessibility of network object in PuT


    The isochrones for the selected network objects are calculated and displayed.
    Notes: In isochronous mode, you can use the functions from the Network editor window's toolbars without leaving the isochrones.
    You can switch off the display by clicking the Initialize button.
    23.2.2.2

    Displaying the accessibility of network object in PuT


    You can visualize the accessibility of nodes, main nodes, stops, stop areas, stop points, or
    zones. To do so, classify a network object type based on the Isochrones time PuT or Isochrones number of transfers PuT attribute.
    Note: The settings are almost identical for all available network object types. Here they
    are described using the example of stops.
    You can define the classified display for several different network objects types at the
    same time.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Stops > Display > tab Active.
    3. Select the option Classified drawing mode.
    4. Via the button, select the attribute Isochrones time PuT.

    Note: You can also classify the network object by the attribute Isochrones Number of
    transfers PuT.
    5. Insert the desired classes (see "Displaying classified objects based on attribute values" on
    page 2411).
    6. Confirm with OK.
    PTVGROUP

    2287

    23.2.3 Setting graphic parameters for the display of isochrones


    7. In the Graphics menu, select the entry Isochrones.
    The Isochrones window opens.
    8. Make the desired settings (see "Displaying PuT isochrones" on page 2285).
    9. In the network click a zone, stop area, or node.
    The stops are displayed in the classified drawing mode. The display visualizes the distances from the selected network object to all stops in the network.
    10. If desired, click on further network objects.
    The classified drawing mode visualizes the distances to the closest selected network object.

    23.2.3

    Setting graphic parameters for the display of isochrones


    You can define settings for the display of PuT and PrT isochrones, as well as for the accessibility of links in PrT.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry 2D display.

    3. In the 2D display section, make the desired settings.


    Note: The settings in the 2D display section are only relevant, if you want to display
    isochrones in 2D (see "Displaying PrT isochrones" on page 2279 and "Displaying
    PuT isochrones" on page 2285).

    2288

    PTVGROUP

    23.2.3 Setting graphic parameters for the display of isochrones


    Element

    Description

    2D display

    Draw
    If the option has been selected, the selected attribute is displayed in
    2D.
    Smooth color transition
    If the option has been selected, smooth color transitions visualize
    increasing or decreasing attribute values.
    Difference display
    If the option has been selected, for each network object the difference
    between the selected attributes is calculated and displayed according
    to the current classification settings.
    tMax-access (access time)
    For attribute values with an extrapolated attribute value > tMaxaccess, the program uses the color specified for the class Not reached.

    Attributes

    Drop-down list for network object type


    Here you select the network object type whose attribute values you
    want to use for the display of isochrones. The isochrones are drawn
    around the network objects of this type. With the button you select the
    attribute you need. To display the accessibility select one of the following attributes: Isochrones time PrT, Isochrones time PuT or Isochrones number of transfers PuT.
    Factor
    Prior to the extrapolation, the source attribute values of the point
    objects are multiplied by this factor.
    v-access
    Extrapolation speed for the calculation of the attribute values of point
    objects along virtual lines to each point in the network.

    Picture quality

    Here you can specify the speed/quality ratio for the graphical output.

    4. Define the settings you want in the Classification and Value ranges areas.
    Note: These settings are valid for the display of accessibility of links in PrT (see "Displaying the accessibility of links" on page 2281) and for the display of isochrones in
    PrT and PuT.

    PTVGROUP

    2289

    23.2.4 Displaying isochrones in lists


    Element

    Description

    Classification Time/Color
    Here you define the time intervals that you want to display in different
    colors. In a separate window you can select a color for each interval.
    To do this, click the relevant box.
    Not reached
    This color indicates network objects which are not reached.
    Value ranges

    Multiply
    You can multiply the interval values in the Classification section with
    the specified factor by clicking on the button.
    Factor
    Enter the desired factor.
    Tip
    With an appropriate factor, you can adjust the current interval values
    for a different unit.

    5. Confirm with OK.


    The settings are applied and used for the display of isochrones and the accessibility of links.

    23.2.4

    Displaying isochrones in lists


    The following lists contain the attributes that are relevant for isochrones:
    Isochrones time
    PrT

    23.2.5

    Node list

    Main node list

    Zone list

    Isochrones time
    PuT

    Isochrones Number
    of transfers PuT

    Stop list

    Stop area list

    Stop point list

    Saving isochrones
    You can save isochrones as follows:
    With graphic parameters as a *.gpa file (see "Saving the graphic parameters of the network window" on page 2496).
    With the version as a *.ver file (see "Opening and saving a version file" on page 840).
    Note: Isochrone results are saved with the version and automatically loaded when reopening the file. Isochrones are only recalculated when reading in older version files or
    separate graphic parameter files.

    2290

    PTVGROUP

    23.3 Searching for and displaying shortest paths

    23.3

    Searching for and displaying shortest paths


    Using the Shortest path search command, you can determine the best paths from a chosen origin to a chosen destination and display the result in the network (see Fundamentals: Chpt.
    11.3 , page 741).
    Note: You can carry out a shortest path search consecutively for the PrT and PuT and display the results simultaneously in the network.

    23.3.1

    Shortest path search PrT


    1. In the Graphics menu, select the entry Shortest path search.
    The Graphics tools (Shortest path search) window opens.
    2. Select the PrT tab.
    3. Make the desired changes.
    Element

    Description

    Drop-down list

    Here you can select the desired network object. You can select
    Zone, Node or Main node.

    Route choice criterion

    Here you can select the route choice criterion.


    tCur
    In-vehicle time in the loaded network
    t0
    In-vehicle time in the unloaded network
    Distance
    Link length
    Impedance
    Impedance according to the assignment parameters
    AddValue 1...3
    Attributes with user-defined values

    Transport system Here you can select a transport system of the PrT.
    Save route index
    to

    PTVGROUP

    Via this button, you can select a link attribute in a separate window which receives the number of the current position for each
    path leg on the shortest path and which is set to zero for all links
    which are not located on the shortest path.
    Note
    If you open the link list afterwards and sort it by the Index attribute,
    you can display all attributes along the links of the shortest path.
    Tip
    For this purpose you can also create a user-defined attribute (see
    "Managing user-defined attributes" on page 973).

    2291

    23.3.2 Shortest path search PuT


    4. In the network, click on the desired start object.
    Note: If on the toolbar, the
    Click only active objects button is activated, you cannot
    use the mouse to select passive network objects (see "Marking only active network
    objects" on page 1005).
    5. In the network, click on the desired destination object.
    Notes: The start object and the destination object do not have to be of the same network object type. You can change the type by selecting the desired type in the dropdown list of the Shortest path search window between marking objects in the network.
    If you mark a node or main node as destination object, you can mark further network
    objects and thus add additional paths legs.
    Zones can only be start or destination objects of a path. If zones are origins and/or
    destinations of paths, the respective origin or destination connector times are contained in the resulting output times.
    The shortest path is displayed according to your chosen settings.
    6. Close the Graphics tools (Shortest path search) window via the Graphical tools entry in
    the View menu.
    Notes: The shortest path view is still displayed after quitting the window via View> Graphics tools.
    You can switch off the display by clicking the Initialize button. The results of all shortest
    path searches will be discarded.
    Tips: If the shortest paths are not displayed as desired, you can set the required graphic
    parameters (see "Setting the graphic parameters for shortest paths" on page 2296).
    You can also display the shortest path search in lists (see "Displaying shortest path searches in lists" on page 2297).

    23.3.2

    Shortest path search PuT


    In PuT, you can perform a timetable-based or a transport-system based search (see Fundamentals: Chpt. 11.3 , page 741).
    Timetable-based search
    1. In the Graphics menu, select the entry Shortest path search.
    The Graphics tools (Shortest path search) window opens.
    2. Select the PuT tab.
    3. Make the desired changes.

    2292

    PTVGROUP

    23.3.2 Shortest path search PuT


    Element

    Description

    Drop-down list

    Here you can select the desired network object. You can select
    Zone and Stop area.

    Departure time/
    Arrival time

    Departure time
    If this option has been selected, you can enter the desired departure time for the shortest path search in the field.
    Notes
    The first possible connection past the departure time is determined. Here, also paths with a walk link before the first boarding
    stop or after the last alighting stop are found.
    When using a weekly or an annual calendar, you can select a
    day which is contained in the current calendar.
    Arrival time
    If this option has been selected, you can enter the desired arrival
    time for the shortest path search in the field.
    Notes
    The program determines the connection with the lowest impedance before or at the specified arrival time at the destination
    zone or stop area (reverse search). If there are several connections with the same impedance, the connection with the fewest
    transfers will be chosen.
    If an already calculated shortest path search is lengthened interactively, the arrival time refers to the new destination.
    You can use the button to start a shortest path search.

    Extension

    Enter the value for the extension

    Mode

    List box for PuT mode

    PTVGROUP

    2293

    23.3.2 Shortest path search PuT


    Element

    Description

    Search parameters

    Click this button to specify settings for the shortest path search by
    search parameters on the basis of timetable-based connection
    search (see "Parameters of timetable-based assignment" on
    page 2021).
    Note
    In this window you can e.g. specify that only active vehicle journey sections will be taken into account.

    Save route index


    to

    Via this button, you can select a link attribute in a separate window which receives the number of the current position for each
    path leg on the shortest path and which is set to zero for all links
    which are not located on the shortest path.
    Note
    If you open the link list afterwards and sort it by the Index attribute,
    you can display all attributes along the links of the shortest path.
    Tip
    For this purpose, you can also create a user-defined attribute
    (see "Managing user-defined attributes" on page 973).

    4. In the network, click on the desired start object.


    5. In the network, click on the desired destination object.
    Notes: The start object and the destination object do not have to be of the same network object type. You can change the type by selecting the desired type in the dropdown list of the Shortest path search window between marking objects in the network.
    Zones can only be start or destination objects of a path. If zones are origins and/or
    destinations of paths, the respective origin or destination connector times are contained in the resulting output times.
    The shortest path is displayed according to your chosen settings.
    6. Close the Graphics tools (Shortest path search) window via the Graphical tools entry in
    the View menu.
    Notes: The shortest path view is still displayed after quitting the window via View> Graphics tools.
    You can switch off the display by clicking the Initialize button. The results of all shortest
    path searches will be discarded.

    2294

    PTVGROUP

    23.3.2 Shortest path search PuT


    Tips: If the shortest paths are not displayed as desired, you can set the required graphic
    parameters (see "Setting the graphic parameters for shortest paths" on page 2296).
    You can also display the shortest path search in lists (see "Displaying shortest path searches in lists" on page 2297).
    Transport system-based search
    If you want to perform a transport system-based search, proceed as follows.
    1. In the Graphics menu, select the entry Shortest path search.
    The Graphics tools (Shortest path search) window opens.
    2. Select the PuT TSys tab.
    3. Make the desired changes.
    Element

    Description

    Drop-down list

    Here you can select the desired network object. You can select
    Zone and Node.

    Mode

    Here you can select a PuT mode.

    Search parameters

    Click this button to specify settings for the shortest path search by
    search parameters on the basis of transport system-based
    connection search (see "Parameters of the TSys-based assignment" on page 2007).

    Save route index


    to

    Via this button, you can select a link attribute in a separate window which receives the number of the current position for each
    path leg on the shortest path and which is set to zero for all links
    which are not located on the shortest path.
    Note
    If you open the link list afterwards and sort it by the Index attribute,
    you can display all attributes along the links of the shortest path.
    Tip
    For this purpose, you can also create a user-defined attribute
    (see "Managing user-defined attributes" on page 973).

    4. In the network, click on the desired start object.


    5. In the network, click on the desired destination object.

    PTVGROUP

    2295

    23.3.3 Setting the graphic parameters for shortest paths


    Notes: The start object and the destination object do not have to be of the same network object type. You can change the type by selecting the desired type in the dropdown list of the Shortest path search window between marking objects in the network.
    If you mark a node as destination object, you can mark further network objects and
    thus add additional paths legs.
    Zones can only be start or destination objects of a path. If zones are origins and/or
    destinations of paths, the respective origin or destination connector times are contained in the resulting output times.
    The shortest path is displayed according to your chosen settings.
    6. Close the Graphics tools (Shortest path search) window via the Graphical tools entry in
    the View menu.
    Notes: The shortest path view is still displayed after quitting the window via View> Graphics tools.
    You can switch off the display by clicking the Initialize button. The results of all shortest
    path searches will be discarded.
    Tips: If the shortest paths are not displayed as desired, you can set the required graphic
    parameters (see "Setting the graphic parameters for shortest paths" on page 2296).
    You can also display the shortest path search in lists (see "Displaying shortest path searches in lists" on page 2297).

    23.3.3

    Setting the graphic parameters for shortest paths


    You can edit the display of PrT and PuT shortest paths as follows.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Shortest path search entry.

    2296

    PTVGROUP

    23.3.4 Displaying shortest path searches in lists

    3. Make the desired changes.


    Element

    Description

    Selected network
    objects

    In a separate window, you can select a color for the objects marked for the shortest path search by clicking in the field.

    PrT paths

    In a separate window, you can select a color for the PrT route
    path in the network by clicking in the field.

    PuT paths

    In a separate window, you can select a color for the PuT route
    path in the network by clicking in the field.

    Note: In the network, the direction of the path and the transfer stops are indicated by
    an arrow.
    4. Confirm with OK.
    The shortest paths are displayed according to your chosen settings.

    23.3.4

    Displaying shortest path searches in lists


    In the lists PrT shortest path search and PuT shortest path search, you can show the corresponding routes (see "Opening a list" on page 2299)

    PTVGROUP

    2297

    23.3.5 Saving a shortest path search


    Notes: The list only displays the results of the timetable-based connection search.
    If a zone has been selected as start and/or destination of a PuT path, the list also contains the following row(s):
    First path leg
    Origin connector, from the zone selected to the connected node found
    Last path leg
    Destination connector, from the connected node found to the zone selected

    23.3.5

    Saving a shortest path search


    You can save shortest path searches as follows:
    With the version, as a *.ver file (see "Opening and saving a version file" on page 840).
    With graphic parameters, as a *.gpa file (see "Saving the graphic parameters of the network window" on page 2496).
    To an attribute file *.att for the corresponding list (see "Save list to attribute file" on page
    2325).

    2298

    PTVGROUP

    24 Displaying data graphically and in lists

    24

    Displaying data graphically and in lists


    Visum provides a wide range of graphical and tabular display options for the data of your traffic model.
    Subjects
    Working with lists
    Specifying basic settings for the network window
    Displaying point objects in the network window
    Displaying line objects in the network window
    Displaying properties via bars
    Displaying route courses in the network window
    Displaying stop catchment areas in the network window
    Displaying transfer relations between stop areas
    Displaying connections and transfer flows at stops
    Displaying lane allocations in the network window
    Labeling network objects with tables or charts
    Displaying classified objects based on attribute values
    Displaying desire lines
    Displaying turns, main turns, and turn volumes
    Showing/hiding extended markings
    Creating schematic line diagrams
    Displaying signal time-space diagrams
    Creating column charts
    Reading and saving the graphic parameters of the network window
    Printing the network display

    24.1

    Working with lists


    In Visum, you can access several types of lists:
    Network object lists: You can display the attribute values of each network object type in a
    list, in a node list, for example. You can edit input attribute values (see "Editing the properties of objects in lists" on page 2321).
    Evaluation lists: Evaluation lists contain the results of calculations or statistics. In evaluation lists, you cannot edit any values. The following lists count as evaluation lists:
    Path lists
    Passenger transfer lists
    Volume matrix between stop points lists
    Shortest path search lists
    Statistics
    List of matrices: You can display all matrices that exist in the network in a list.
    Matrix toll list (see "Specifying the matrix toll of a toll system" on page 1422)

    24.1.1

    Opening a list
    From the Lists menu, choose the entry of your choice, e.g. Network> Nodes.

    PTVGROUP

    2299

    24.1.1 Opening a list


    The List (Nodes) window opens.

    The table indicates all lists you can open via the Lists menu.

    2300

    PTVGROUP

    24.1.1 Opening a list


    First structural
    level
    Demand

    Network

    PrT

    PTVGROUP

    Second structural level

    Third structural level

    Transport system
    Modes
    Demand segments
    Demand strata
    Matrices
    OD pairs
    Main OD pairs
    Nodes
    Main nodes
    Turns
    Main turns
    Links
    Link types
    Zones
    Connectors
    Main zones
    Territories - basis
    Territories - PuT details
    POI
    GIS objects
    Screenlines
    Count locations
    Detectors
    Toll system
    Toll matrices
    Signal controls
    Signal groups
    Stages
    Legs
    Lanes
    Lane turns
    Crosswalks
    Geometry templates
    Leg templates
    Lane templates
    Crosswalk templates

    2301

    24.1.1 Opening a list


    PuT supply

    Stops

    Lines

    System routes

    Stops
    Stop areas
    Stop points - basis
    Stop points - arrivals/departures
    Transfers and walk times between
    stop areas at stop
    Time profiles: Transition walk
    times
    Transport systems: Transition
    walk times
    Main lines
    Lines
    Line routes
    Line route items
    Time profiles
    Time profile items
    Vehicle journey sections
    Coupling sections
    Coupling section items
    System routes
    System route items

    Fare zones

    2302

    PTVGROUP

    24.1.1 Opening a list


    PuT operation

    Paths

    PuT analyses

    Statistics

    Valid days
    Vacation days
    Operators
    Vehicle units
    Vehicle combinations
    Line block versions
    Blocks
    Block items
    PrT path sets
    PrT paths
    PrT paths on link level
    PuT OD pairs
    PuT paths
    PuT path legs
    PrT shortest path search
    PuT shortest path search
    Transfers and walk times between
    stop areas at stop
    Passenger transfer stops / time profiles
    Passenger transfer transport systems
    Volume matrix between two stop
    points - on path level
    Volume matrix between stop points
    - on path leg level
    Network information
    Goodness of PrT assignment
    Goodness of PrT assignment with
    ICA
    Assignment analysis
    PuT assignment statistics
    Emissions (HBEFA)

    Propagation of link
    information
    Tips: You can display one or more list windows of one or of different types of lists at the
    same time.
    You can choose which attributes you want to show in the list and you can format your list
    content (see "Viewing/Hiding attributes" on page 2309).

    PTVGROUP

    2303

    24.1.2 The list window

    24.1.2

    The list window


    Once you have selected a type of list, a list window opens.

    (1) Title bar


    The list header shows the name of the list in squared brackets. You can edit the name of the
    list (see "Editing window headers of lists" on page 2309).
    (2) Menu bar
    Once a list window is open, the List (<Network object type>) menu appears on the far right in
    the menu bar.
    (3) Column header
    As column header, either the short or the long name of the attributes is displayed, according to
    the setting. Any selected relations are put in front, for example Min:InLinks\FromNodeNo.
    Place the pointer in the column header: A quick info appears which provides further information about the displayed attribute.
    Here you can edit the current attribute selection (see "Viewing/Hiding attributes" on page
    2309), adjust the layout (see "Adjusting the list layout" on page 2308) or sort a list (see "Sorting a list" on page 2314).
    (4) Data
    Here you can view the values of the selected attributes. The context menu offers various
    editing options.
    Note: The first column of a list indicates the number of the row.
    (5) Toolbar
    In the toolbar, the following functions are provided:

    2304

    PTVGROUP

    24.1.2 The list window


    Symbol

    Name

    Description

    Save list to attribute


    file

    Saves the list to a text file (see "Save list to attribute file"
    on page 2325)

    Copy list to clipboard

    Copies the content to the Clipboard (see "Exchanging


    list contents via the Clipboard" on page 2328)

    Save list to database

    Saves the list to a database (see "Exporting attributes to


    a database" on page 2329)

    Paste content from


    clipboard

    Pastes the content from the Clipboard (see "Exchanging


    list contents via the Clipboard" on page 2328)

    Attribute selection

    Selection of the columns which are displayed in the list


    (see "Viewing/Hiding attributes" on page 2309)

    Show only active <net- Activate or deactivate, to show only active objects of the
    work objects>
    selected type (see "Show only active network objects"
    on page 2315)

    PTVGROUP

    Show/hide cross-section view

    If the icon is pressed only one row will be displayed for


    each network object. The direction-specific attribute
    values are summarized.
    If the icon is not pressed one row will be displayed for
    each direction of the network object. Separate attribute
    values will be displayed by direction.
    Notes
    This option is only provided for directed network object
    types such as links, turns, or OD pairs.
    How the attribute values are to be summarized is predefined by an inherent logic. For values that are not
    numerical, only the value that applies to the 'up' direction will be displayed.

    Searching for a network object

    Highlights the row with the desired network object (see


    "Finding an object in a list" on page 2318)

    Sort in ascending
    order

    The list is sorted in ascending order by one or multiple


    columns (see "Sorting a list" on page 2314)

    Sort in descending
    order

    The list is sorted in descending order by one or multiple


    columns (see "Sorting a list" on page 2314)

    Display/hide analysis
    row: Minimum

    If the icon is pressed another row will appear in the


    column headers. It shows the minimum value by
    column.

    Display/hide analysis
    row: Maximum

    If the icon is pressed another row will appear in the


    column headers. It shows the maximum value by
    column.

    2305

    24.1.3 Setting list options


    Symbol

    Name

    Description

    Display/hide analysis
    row: Average

    If the icon is pressed another row will appear in the


    column headers. It shows the mean value by column.

    Display/hide analysis
    row: Sum

    If the icon is pressed another row will appear in the


    column headers. It shows the sum by column.

    No synchronization
    with network editor

    There is not synchronization with other windows.

    Synchronization with
    network editor: Mark

    The objects marked in the list are highlighted in other


    windows and vice versa.

    Synchronization with
    network editor: Mark
    and shift view

    The objects marked in the list are highlighted in other


    windows and vice versa. If required, the network section
    is shifted in such a way that all marked objects are visible.

    Synchronization with
    network editor: Mark
    and auto zoom

    The objects marked in the list are highlighted in other


    windows and vice versa. Additionally, in the network an
    auto zoom is carried out for the marked objects.

    (6) Window selection


    Via the drop-down list, you can switch between all open windows.

    24.1.3

    Setting list options


    You can e.g. set font you want to use in lists and whether the lists and the network editor shall
    be synchronized.
    1. From the Edit menu, choose User Preferences.
    The User Preferences window opens.
    2. In the navigator, select the GUI> Lists page.
    3. Make the desired changes.

    2306

    Element

    Description

    Font for lists

    Select font
    Use the button to select a font, style and font size in a separate
    window for all lists.
    Reset
    Via the button you can reset the settings to the Visum default.

    Column headers

    Here you can specify whether the attributes in the column headers are displayed as short names or as long names.
    Short name
    If the option has been selected, all attributes are displayed with

    PTVGROUP

    24.1.3 Setting list options


    Element

    Description
    their short names.
    Long name
    If the option has been selected, all attributes are displayed with
    their long names.

    Row labels

    Here you can specify whether the attributes in the row labels are
    displayed as short names or as long names.
    Note
    Only in some statistics list, row headers are labeled with attribute
    names.
    Short name
    If the option has been selected, all attributes are displayed with
    their short names.
    Long name
    If the option has been selected, all attributes are displayed with
    their long names.

    Standard synchronization mode


    with network editor

    Synchronization means that objects which are marked in a list are


    simultaneously marked in the network display and in other windows as well, if applicable. The same applies vice versa.
    No synchronization
    List windows and other windows are not synchronized.
    Mark object(s)
    Network objects marked in a list window are also marked in other
    windows and vice versa.
    Mark and shift view
    Network objects marked in a list window are also marked in other
    windows and vice versa. If required, the network section of the network window is shifted in such a way that all marked objects are
    visible.
    Mark and autozoom
    Network objects marked in a list window are also marked in other
    windows and vice versa. Additionally, in the network an auto
    zoom is carried out for the marked objects.
    Notes
    Automatic synchronization will terminate at more than 100 marked network objects. In this case, you can right-click to open the
    context menu and click the Mark in the network entry for manual
    synchronization.
    You can change the synchronization individually for each open
    list window (see "Synchronizing network object lists with other

    PTVGROUP

    2307

    24.1.4 Adjusting the list layout


    Element

    Description
    windows" on page 2320).

    Miscellaneous

    Extended input options


    If the option has been selected, the input possibilities in lists
    change as follows:
    Logical values are controlled via activated/deactivated check
    boxes, for example Use automatic link orientation.
    The values of a set can be edited in drop-down lists, for example Control type.
    Values of a set of which you can select multiple items, are displayed as buttons labeled with the current selection. They
    open a new window. In the window, you can select multiple
    items, for example TSysSet.
    Values for user-defined attributes of type File are displayed
    as button, which are labeled with the name of the selected
    file. The button opens the Open file window, where you can
    make a new selection.
    Generating demand layout files when opening the zone list
    If this option is selected, the following pre-defined list layout files
    will be generated when the zone list is opened:
    EVA trip generation output
    EVA production rates
    EVA constraints
    EVA study area factors
    Person groups and structural properties
    Tour-based model - production results
    Tour-based model - production rates
    Tour-based model - study area factors
    Using these list layouts, you can immediately view the most
    important demand data.

    4. Confirm with OK.

    24.1.4

    Adjusting the list layout


    Internally, Visum uses a standard layout for each list type. You can save the settings that you
    have specified for a list as a list layout (see "Saving a list layout" on page 2313). You can
    reload this layout when required (see "Reading a list layout" on page 2314). The layout contains the number and the order of the displayed columns including the settings specified for
    decimal places, units, alignment, format, list header, and analysis rows.
    Note: If you do not save your changes to the list layout, the changes will be temporary.

    2308

    PTVGROUP

    24.1.4.1 Editing window headers of lists


    24.1.4.1

    Editing window headers of lists


    Each list window comes with a list header. The header appears in the title bar and can be
    changed.
    1. In the List (<Network object type>) menu, select the Change heading entry.
    The Change heading window opens.
    2. Enter the desired text.
    3. Confirm with OK.
    The list displays the entered header name.

    24.1.4.2

    Viewing/Hiding attributes
    For a list, you can specify the attributes you want to show and the attributes you want to hide.
    Simultaneously you define how the attribute values are to be displayed. You select the units,
    the number of decimal places and the alignment of the data in the columns, for example.
    Tip: To add or remove a column quickly, call the context menu of the column header and
    select either entry: Add column here or Remove column.

    1. Make sure that the list window of the required list is open.
    2. On the toolbar, click the

    Select attributes icon.

    Tip: Alternatively, you can select the Attribute selection command in the List (<Network object type>) menu, or the Attribute selection command in the context menu of
    the column header.
    The Attribute selection <network object type> window opens.
    3. Make the desired changes (see "The window used for the selection of multiple attributes"
    on page 968).
    4. Confirm with OK.
    In the list, the selected attributes and their values are displayed in the set order.
    24.1.4.3

    Adding statistical evaluation data rows to a list


    1. Make sure that the list window of the required list is open.
    2. On the toolbar, click the desired icon.

    PTVGROUP

    2309

    24.1.4.4 Fixing the columns of a list


    Symbol Name

    Description

    Display/hide analysis
    row: Minimum

    If the icon is pressed another row will appear in the


    column headers. It shows the minimum value by
    column.

    Display/hide analysis
    row: Maximum

    If the icon is pressed another row will appear in the


    column headers. It shows the maximum value by
    column.

    Display/hide analysis
    row: Average

    If the icon is pressed another row will appear in the


    column headers. It shows the mean value by
    column.

    Display/hide analysis
    row: Sum

    If the icon is pressed another row will appear in the


    column headers. It shows the sum by column.

    The settings are applied.


    24.1.4.4

    Fixing the columns of a list


    You can define that selected columns of a list are to be fixed. The fixed columns are always
    located at the left-hand margin of the list. You define up to which column the fixing applies. If
    you have to scroll to the right in a list which consists of numerous columns, then the fixed
    column and any column to the left of it will remain visible.
    1. With the right mouse key, click the header of a column.
    The shortcut menu opens.
    2. Select the Fix column command.
    The desired setting is applied.

    24.1.4.5

    Adjusting the column width to the contents


    You can adjust the column width of one or multiple or all columns to the content.
    1. Make sure that the list window of the required list is open.
    2. Mark the particular columns, if applicable.
    3. With the right mouse button, click the header of a marked column.
    The shortcut menu opens.
    4. Select the desired entry.
    Element

    Description

    Optimal width for


    all columns

    Adjusts the width of all columns to the length of the longest text
    entry.

    Optimum width for Adjusts the width of all marked columns to the length of the loncolumn
    gest text entry
    The desired setting is applied.
    2310

    PTVGROUP

    24.1.4.6 Aggregating rows of a list


    24.1.4.6

    Aggregating rows of a list


    Use this function to form a single row from the rows with identical attribute value. For any other
    attribute (i.e. columns) you need to decide, how to aggregate their attribute values.
    Grouping can be specified for one or several columns.
    Example: You want to determine the average length of links of type 20. For that purpose,
    group the links by attribute TypeNo in the list. For the length attribute, select the aggregation
    function Average.
    Notes: You can use Copy&Paste to output the numbers (see "Copying and pasting selected attribute values" on page 2328).
    This function is not provided in path lists and statistics.
    1. Make sure that the list window of the required list is open.
    2. Select the columns by which you want to group the data (see "Selecting list sections" on
    page 2319).
    3. Right-click one of the columns you selected.
    The shortcut menu opens.
    4. Select the Group columns entry
    Tip: Alternatively, you can define the grouping in the attribute selection window (see
    "Editing the display properties of attributes" on page 970).
    The list appears grouped. The headers of those columns which have been selected for grouping will change to Grp(<column header>). Visum aggregates the other attribute values of the
    grouped data rows. The particular function that has been selected for the aggregation is displayed in the column header. Subsequently you can select a different aggregate function for
    each column.
    Notes: In grouped lists, attribute value editing is restricted.
    The automatic synchronization of a grouped list with the network window is no longer
    active. In this case, you can right-click to open the context menu and click the Mark in the
    network entry for manual synchronization.
    Selecting an aggregate function for a column in a grouped list
    1. Make sure that a list window with a grouped list has been opened.
    2. With the right mouse key, click in the header of the selected column.
    Tip: In the header of the selected column, the currently used aggregate function is displayed.
    The shortcut menu opens.
    3. Select the Aggregate function entry and the desired sub-entry.

    PTVGROUP

    2311

    24.1.4.6 Aggregating rows of a list

    Element

    Description

    Minimum

    Minimum of the summarized attribute values

    Maximum

    Maximum of the summarized attribute values

    Average

    Mean value of the summarized attribute values

    Weighted
    mean

    Mean value of the summarized attribute values, weighted by an attribute. If this aggregate function is selected, initially 1.0 is set for weighting. You then select the desired attribute for weighting. To do so, in
    Attribute selection (see
    the Weight column, click the symbol
    "Editing the display properties of attributes" on page 970).
    Example: You want to calculate the average volume for a selected
    link type. Thereby, you would like to prioritize longer links accordingly
    over shorter ones. For that purpose, aggregate the list by link type,
    select 'weighted mean' as aggregate function for the volumes, and for
    the weighting attribute, select 'length'.

    Sum

    Sum of summarized attribute values

    Compare

    If all summarized attribute values are equal, this value is entered,


    otherwise * appears.

    Number

    Number of summarized rows

    Concatenate

    All attribute values of the summarized rows, separated by a separator


    You can select a different separator (see "Settings for decimal places
    and aggregate functions" on page 960).

    Histogram

    Numbers of occurrence of the summarized attribute values, separated


    by a separator
    Format: [value1:number1],[value2:number2], etc.
    You can select a different separator (see "Settings for decimal places
    and aggregate functions" on page 960).

    Distinct occurrence

    List of the occurring values

    Empty

    No entry

    According to the selected aggregate function, the values are aggregated.


    Tip: If the list includes an attribute multiple times, you can aggregate these attribute
    values in different ways.
    Ungroup columns
    1. Make sure that a list window with a grouped list has been opened.
    2. Select the column you would like to ungroup.
    3. With the right mouse key, click the header of the selected column.

    2312

    PTVGROUP

    24.1.4.7 Saving a list layout


    The shortcut menu opens.
    4. Select the desired entry.
    Element

    Description

    Ungroup selected
    columns

    The selected columns are no longer grouped.

    Ungroup all columns

    The list no longer contains grouped columns.

    The grouping is released.


    24.1.4.7

    Saving a list layout


    You have two possibilities of saving list layouts.
    First possibility
    1. Make sure that the list window of the required list is open.
    2. Make the desired changes to the list settings (see "Adjusting the list layout" on page 2308).
    3. In the List (<Network object type>) menu, select the Save layout entry.
    The Save list layout window opens.
    4. Save the file to the desired location.
    The settings are saved as *.lla file.
    Second possibility
    1. Make sure that the list window of the required list is open.
    2. Make the desired changes to the list settings (see "Adjusting the list layout" on page 2308).
    3. In the field of the Select list layout drop-down list, enter a name for the layout.
    4. Press the ENTER key.
    The settings are saved to an *.lla file in the project directory specified for list layout files (see
    "Opening and saving a project directories file" on page 838).
    Saving a list layout as standard layout
    Internally, Visum uses a standard layout for each list type. When opening a list, it is displayed
    in the standard layout of the list type. You can edit the standard layout of a list by saving the
    edited layout as standard layout.
    1. Make sure that the list window of the required list is open.
    2. Make the desired changes to the list settings.
    3. In the List (<Network object type>) menu, select the entry Save layout as standard
    layout.

    PTVGROUP

    2313

    24.1.4.8 Reading a list layout


    The settings are saved to an std_*.lla file, for example std_links.lla for links, in your home directory.
    Notes: The user-defined standard layout is used for each new list window of the list type.
    If you want to use the Visum-internal standard layout again, you have to delete the userdefined standard layout in your home directory.
    24.1.4.8

    Reading a list layout


    You have two possibilities of reading list layouts.
    First possibility
    1. Make sure that the list window of the required list is open.
    2. In the List (<Network object type>) menu, select the Open layout entry.
    The Open list layout window opens.
    3. Open the desired file.
    The saved settings are applied to the open list.
    Second possibility
    1. Make sure that the list window of the required list is open.
    2. On the toolbar, select the desired layout in the drop-down list by clicking on the entry.
    Note: In the drop-down list, you can select list layout files saved to the directory specified (see "Opening and saving a project directories file" on page 838).
    The list layout is loaded and the saved settings are applied to the open list.
    Tip: The saved list layout of a POI category can also be read in for a different POI category.

    24.1.5

    Sorting a list
    You can sort the data in a list by one or more columns.
    Note: In ascending sorting order empty values are listed at the top.

    24.1.5.1

    Sorting a list by one column


    1. Click the column header of the desired column.
    2. Click the Sort ascending

    icon or the Sort descending

    icon.

    Tip: Alternatively, in the context menu of the column header, you can select either
    command: Sort in ascending order or Sort in descending order.

    2314

    PTVGROUP

    24.1.5.2 Sorting a list by several columns


    The entries are sorted.
    24.1.5.2

    Sorting a list by several columns


    1. Click the column header of the desired column.
    2. Press the CTRL key and click on further column headers.
    3. Click the Sort ascending

    icon or the Sort descending

    icon.

    Tip: Alternatively, in the context menu of the column header, you can select either
    command: Sort in ascending order or Sort in descending order.
    Basically, the list is sorted according to the entries in the outermost-left one of the selected
    columns. If there are identical entries, these rows are sorted according to the entries in the
    next marked column etc.
    Tip: Via the context menu, you can also sort by one or more columns. For this purpose,
    with the right mouse button, click a column header and select the entry Sort in ascending order or Sort in descending order.

    24.1.6

    Applying filters to lists


    In certain lists, you can filter the objects listed.

    24.1.6.1

    Show only active network objects


    In lists storing network objects which can be set to the passive state or to the active state,
    respectively, you can specify that only the active networks are to be listed.
    1. Open the desired list.
    2. Click the

    Show only active <network objects> icon.

    The icon is pressed. The list shows only active network objects.
    Tip: Right-click on the icon to open the filter settings window for the particular network
    object type.
    In the Geometry > Legs list, a right-click on the icon opens a window where you can specify whether the node filter or the main node filter shall be opened.
    24.1.6.2

    Limiting list display to a selection


    In some lists, you can reduce the number of listed objects by specifying a selection criterion.
    Displaying GIS objects or POIs of one category only
    In the GIS objects or Points of Interest list, you can select a category. Then, the list displays
    only the objects of this category.
    1. Open the desired list (see "Opening a list" on page 2299).
    2. In the drop down list of the toolbar, select a category.

    PTVGROUP

    2315

    24.1.6.2 Limiting list display to a selection


    The list contains objects of the selected category only. In the case of POIs, it also contains all
    objects of the subcategories of the selected category.
    Limiting the display to a demand segment
    In some evaluation lists, you can limit the display to a demand segment.
    1. Open the desired evaluation list (see "Opening a list" on page 2299).
    The list is displayed.
    2. In the evaluation list DSeg, select a demand segment.
    The evaluations are displayed for the selected demand segment only.
    Limiting the display to a path set or to a demand segment
    In some evaluation lists, you can limit the display to a path set or to a demand segment.
    1. Open the desired evaluation list (see "Opening a list" on page 2299).
    The list is displayed.
    2. In the selection list DSeg / Path set, select the desired entry.
    The evaluations are displayed for the selected path set/demand segment only.
    Limiting the display to active time profiles or active links
    In some evaluation lists, you can limit the display to active time profiles (list PuT path legs) or
    links (list PrT paths on link level).
    1. Open the desired evaluation list (see "Opening a list" on page 2299).
    The list is displayed.
    2. Select the option Only active time profiles or Only active links.
    Only the active time profiles or links are displayed in the list.
    Limiting the path list display to a selection
    In paths or passenger transfers lists, you can reduce the list display to a selection.
    1. Open the desired path list (see "Opening a list" on page 2299).
    The list is displayed.
    2. Under Selection, select one of the following views.

    2316

    Element

    Description

    All routes

    All paths or routes of the assignment are displayed.

    Flow bundle
    routes

    All paths or routes of the current flow bundle output are displayed.
    Note
    This entry is only provided for the paths of a demand segment. It is
    not provided for the paths of a path set.

    Filter for OD
    pairs

    All paths or routes of the current OD pair filter are displayed.

    PTVGROUP

    24.1.7 Finding objects in lists


    The selection is displayed.
    Hiding walk links in PuT path lists
    The PuT path leg list usually displays all path legs including walk links. If required, you can
    hide all PuT walk links (egress, transfer and access) in the list.
    1. Open the PuT path leg list (see "Opening a list" on page 2299).
    The list is displayed.
    2. Select the Only PuT path legs option.
    In the list, the walk links are hidden.
    Displaying all transfers at a specific stop
    In the Passenger transfers > Stops/time profiles list, you can display the transfers at a specific stop. In addition, you can limit the display to a specific time profile.
    1. Open the Passenger transfers > Stops/time profiles list (see "Opening a list" on page
    2299).
    2. Above the list, click the button labeled with the Stop.
    The Find stop window opens.
    3. In the list, select the desired stop and click the Close button.
    Tip: If you click the All button, all transfers at all stops are displayed.
    4. If required, click the button labeled with the Time profile.
    The Find time profile window opens.
    5. In the list, select the desired time profile and click the Close button.
    Tip: If you click the All button, all transfers at all time profiles are displayed.
    The list is displayed for all passenger transfers which comply with both the stop selection and
    the time profile selection.
    Displaying sections in item lists
    In item lists, you can switch from the classical view to a view by section. The last item will not
    be displayed in this view.
    1. Open the desired item list (see "Opening a list" on page 2299).
    2. On the toolbar, click the

    Section view icon.

    The item list is displayed in the section view.


    Note: If you click the icon again, you will return to the classical view.

    24.1.7

    Finding objects in lists


    In lists, you can search for objects.

    PTVGROUP

    2317

    24.1.7.1 Finding an object in a list


    24.1.7.1

    Finding an object in a list


    How to find network objects in lists is described in the following section: (see Finding network
    objects in the network page 999).

    24.1.7.2

    Finding object in either direction


    In lists with objects stored by direction, such as links, turns and paths, you can highlight the
    opposite direction of the respective object.
    1. Open the desired list (see "Opening a list" on page 2299).
    2. With the right mouse button, click in the row of the desired object.
    A context menu opens.
    3. Select the appropriate entry: Go to reverse direction or Mark reverse direction.
    The network object found is selected in the list.

    24.1.7.3

    Searching for data records in PuT path lists


    In the PuT path and PuT path leg lists, you can search for the attribute Data record number.
    1. Open the desired list (see "Opening a list" on page 2299).
    2. Right-click in the list.
    A shortcut menu opens.
    3. Select the entry Searching for data record no.
    The Search for PuT paths window opens.
    4. Enter the desired data record number.
    5. Confirm with OK.
    The path searched for is selected in the list.

    24.1.7.4

    Finding objects in PrT paths lists


    You can search a PrT paths list for paths with a specific origin or destination zone.
    1. Open the desired list (see "Opening a list" on page 2299).
    2. Right-click in the list.
    A shortcut menu opens.
    3. Select the Find entry.
    The Find pair of zones window opens.
    4. On the left-hand side, either enter the number of the desired origin zone or select it in the
    list.
    5. On the right-hand side, either enter the number of the desired destination zone or select it
    in the list.
    6. Check the Only active ones option, if only active paths shall be found.

    2318

    PTVGROUP

    24.1.8 Selecting list sections


    7. Confirm with Close.
    In the list, the first path which complies with the desired properties is selected.

    24.1.8

    Selecting list sections


    You can use the mouse or the keyboard to select certain sections in the list.

    24.1.8.1

    Marking list sections with the mouse


    You can select individual cells as well as entire list sections in order to edit them afterwards,
    for example via the context menu.
    Note: Any existing markings are deleted once you select a new section.

    Selecting a single cell


    Left-click the desired cell.
    The cell is highlighted.
    Selecting several cells in consecutive order
    To select several cells in consecutive order, left-click the first cell of your choice. Then keep
    the mouse-button held down and move the mouse pointer over the other cells you want to
    highlight.
    Tip: Alternatively, press the SHIFT key to highlight consecutive cell sections. With the
    mouse button, click in the first cell that you want to mark, press the SHIFT key and click
    in the last cell that you want to mark.
    The cells are highlighted.
    Marking single rows or columns
    Click the header of the row or column that you want to mark.
    The section is marked.
    Marking several consecutive rows or columns
    1. Click the header of the first row or column that you want to mark.
    2. Hold down the SHIFT key.
    3. Click the last row or column that you want to mark.
    The section between the first and the last of the clicked rows or columns is marked.
    Marking non-consecutive rows or columns
    1. Mark one or several cells or rows or columns.
    PTVGROUP

    2319

    24.1.8.2 Selecting list sections via the keyboard


    2. Press the CTRL key and keep it pressed.
    3. Mark further cells or list sections.
    The cells are highlighted.
    Marking all cells
    Click the top-left cell in the list.
    All cells are selected.
    24.1.8.2

    Selecting list sections via the keyboard


    Alternatively, you can mark several consecutive cells, rows, or columns via the keyboard.
    In the list, select one or more cells, rows, or columns.

    24.1.9

    Hotkeys

    Description

    SHIFT + arrow keys

    Press the SHIFT key and the appropriate arrow key simultaneously to extend the currently selected section towards the
    particular direction, or reduce it, as applicable.

    SHIFT + POS 1

    Press SHIFT + POS1 to select all cells to the left of the selected
    cells.

    SHIFT + END

    Press SHIFT + END to select all cells to the right of the selected
    cells.

    SHIFT + PUP

    Press SHIFT + PUP to select all cells above the selected cells.

    SHIFT + PDN

    Press SHIFT + PDOWN to select all cells below the selected cells.

    CTRL + A

    Press CTRL + A to select all cells.

    Synchronizing network object lists with other windows


    You can synchronize network object lists with other windows such as the network window or
    the junction editor window, for example. If the windows are synchronized, you can mark one or
    several network objects in one window, which will automatically be marked in the other windows as well. Depending on the setting, in the network window the displayed section is automatically shifted or zoomed in.
    Example: The list of nodes and the network window are open at the same time. Now you can
    select a node in the list, this node is automatically highlighted in the network window.
    Note: This synchronization only works, if you activate the synchronization in all windows.
    You can also specify the synchronization settings simultaneously for all lists (see "Setting
    list options" on page 2306).
    Automatic synchronization will terminate at more than 100 marked network objects. In
    this case, you can right-click to open the context menu and click the Mark in the network
    entry for manual synchronization.
    1. Open the desired network object list.

    2320

    PTVGROUP

    24.1.10 Editing the properties of objects in lists


    2. On the toolbar of the list, click the desired icon.
    Symbol

    Name

    Description

    No synchronization
    with network editor

    There is not synchronization with other windows.

    Synchronization with
    network editor: Mark

    The objects marked in the list are highlighted in other


    windows and vice versa.

    Synchronization with
    network editor: Mark
    and shift view

    The objects marked in the list are highlighted in other


    windows and vice versa. If required, the network section
    of the network window is shifted in such a way that all
    marked objects are visible.

    Synchronization with
    network editor: Mark
    and auto zoom

    The objects marked in the list are highlighted in other


    windows and vice versa. Additionally, in the network an
    auto zoom is carried out for the marked objects.

    Note: If the synchronization is not active, you can immediately highlight a network object
    in the network window as follows: Right-click the object in the list and click the Auto
    zoom entry.
    The settings are applied.

    24.1.10 Editing the properties of objects in lists


    You can edit certain data in network object lists and matrix lists. Modifiable data is displayed
    on a white background in lists. Calculated data and IDs, for example the 'from node number' of
    a link, cannot be edited. It is highlighted in gray in lists. Attributes which can be overwritten yet
    cannot be edited due to missing access rights are highlighted in dark gray.
    Note: From most of the lists, you can edit the objects as follows: Right-click the desired
    object and select the Edit entry.
    24.1.10.1 Editing attribute values in a list
    In a list, attribute values can be edited. According to the data type of the object, an entry is
    required or either a selection list or a button is provided. Mandatory input attributes and output
    attributes are not subject to changes. These attributes are highlighted in light gray in lists.
    Tip: Alternatively, you can edit the attribute values of an object as follows:
    In the list, right-click the desired object and select the Edit entry. A window opens. In this
    window, you can edit the attribute values of the object. For a node, the junction editor
    appears, for example.
    Entering attribute values in a list
    In a list, you can edit numerical and alphanumerical values.

    PTVGROUP

    2321

    24.1.10.1 Editing attribute values in a list


    1. Select the desired cells (see "Selecting list sections" on page 2319).
    2. Enter the desired value.
    Note: For numerical data of the length or time type, regard the appropriate unit:
    If just a number is entered, the value is read in the format which is currently used
    for the attribute display. Example: If an attribute is displayed in the minutes format,
    the value 5 is read as 5 minutes.
    You can change the format in the attribute selection window (see "The window
    used for the selection of multiple attributes" on page 968).
    You can enter a value and the unit. In this case, Visum converts the value in such
    a way that it is displayed accordingly in the selected format. You may enter
    lengths in metric (m, km) or imperial (ft, mi) units.
    Example: If an attribute is displayed in the minutes format, you can enter 2h. After
    the confirmation, the value 120 will be displayed.
    3. Press the ENTER key.
    The values are modified.
    Tip: Numerical values can also be edited via the context menu Arithmetic operations on
    marked section> Set value.
    Using a selection list for attribute data editing in a list
    In a list, some attribute values can be edited via selection lists. This function is only provided if
    the following option has been selected: Edit> User Preferencesmenu > GUI> Lists, Extended input options (see "Setting list options" on page 2306).
    1. Select the desired cells (see "Selecting list sections" on page 2319).
    2. Click the symbol with the arrow

    3. Select the desired entry.


    The values are modified.
    Tip: Alternatively, you can use the context menu for data editing. You can find the provided values far down in the context menu.
    Using a button for attribute data editing in a list
    In a list, some attribute values can be edited via buttons. This function is only provided if the following option has been selected: Edit> User Preferences menu > GUI> Lists , Extended
    input options (see "Setting list options" on page 2306).
    1. Click the desired cell (see "Selecting list sections" on page 2319).
    A window opens.
    2. Select the desired entries.
    3. Confirm with OK.

    2322

    PTVGROUP

    24.1.10.2 Using attribute values for calculations in a network object list


    The values are modified.
    Tip: Alternatively, you can use the context menu for data editing. You can find the provided values far down in the context menu.
    24.1.10.2 Using attribute values for calculations in a network object list
    In network object lists, you can execute calculations using editable numerical values.
    Note: Not-editable attribute values are grayed-out.
    Tip: Alternatively, you can use attribute values for calculations as follows:
    In the list, you can select multiple network objects, then right-click to call the entry Edit.
    The Multi-edit window provides various arithmetic operations (see "Editing attribute
    values of network objects" on page 983).
    1. Make sure that a list window is open.
    2. Highlight the desired cells (see "Selecting list sections" on page 2319 and "Selecting list
    sections via the keyboard" on page 2320).
    3. Right-click a highlighted value.
    The shortcut menu opens.
    4. Select the Arithmetic operations on marked section entry.
    5. Select the desired entry.
    Element

    Description

    Set value

    Use this entry to allocate a new value to the attribute values. In a


    window, enter the desired new value.

    Add

    Use this entry to add a value to the attribute values. In a window,


    enter the desired value.

    Subtract

    Use this entry to subtract a value from the attribute values. In a window, enter the desired value.

    Multiply

    Use this entry to multiply the attribute values by a value. In a window, enter the desired value.

    Divide

    Use this entry to divide the attribute values by a value. In a window,


    enter the desired value.

    Raise to power

    Use this entry to raise the attribute values to a given power. In a window, enter the desired value.

    Form the minimum

    Use this entry to derive the minimum value from the particular attribute value and a value. In a window, enter the desired value.

    Form the maxi-

    Use this entry to derive the maximum value from the particular attri-

    PTVGROUP

    2323

    24.1.11 Delete object in list


    Element

    Description

    mum

    bute value and a value. In a window, enter the desired value.

    Exponential func- Use this entry to apply the exponential function to the selected attrition
    bute values.
    Natural logarithm

    Use this entry to take the natural logarithm of the selected attribute
    values.

    Reciprocal

    Use this entry to form the reciprocal of the selected attribute values.

    The attribute values are computed. A message will appear if some of the selected values are
    not subject to changes. You can decide by column whether editing shall be cancelled. Alternatively, editing can be performed for just those values which are subject to changes.
    Tip: Similar to the Quick view and matrix editing, the arithmetic operation can be entered
    directly. You can add the value 2, for example, as follows: Mark the desired attribute
    values and enter the term =+2. All arithmetic operations and terms provided are described in the QuickView (see "Editing attribute values in the Quick view with arithmetic
    operations" on page 995).

    24.1.11 Delete object in list


    You can delete objects in an opened list.
    1. Make sure that the list window of the required list is open.
    2. In the list, mark the desired objects.
    3. Right-click in one of the marked rows.
    A context menu opens.
    4. Select the Delete entry.
    A query opens.
    5. Confirm with OK.
    The Delete <object> window opens.
    6. Select which marked objects you want to delete.

    2324

    Element

    Description

    Yes

    The object listed in the window is deleted and also the network
    objects with a reference to the object.

    Yes for all

    All remaining marked objects are deleted, and also the network
    objects with a reference to the object.

    No

    Neither the object listed in the window is deleted nor the network
    objects with a reference to the object.

    No for all

    Neither of the remaining marked objects are deleted, nor the net-

    PTVGROUP

    24.1.12 Importing and exporting list contents


    Element

    Description
    work objects with a reference to these objects.

    Cancel

    The action is cancelled.

    Notes: If you click the Yes or No buttons, the query is displayed for the next marked
    row.
    With the Yes for all or No for all buttons, you only regard the remaining marked
    objects, for which neither Yes nor No has been clicked.
    The confirmed objects are deleted.

    24.1.12 Importing and exporting list contents


    For data exchange with other Visum network versions or for further data processing in external
    applications you can save the currently listed attribute data as an attribute file or to the clipboard or in a database.
    24.1.12.1 Save list to attribute file
    All attribute files are text files with the extension *.att. In an attribute file, you can save the data
    displayed in the current list window, i.e. the attribute values of network objects.
    1. Make sure that the required list window is open.
    2. Make the desired changes to the list settings.
    3. On the toolbar of list window, click the

    Save list to attribute file button.

    The Save attributes window opens.


    4. Enter the file name and the path, if required.
    Notes: By default, attribute files are saved to the directory specified in the project directories (see "Opening and saving a project directories file" on page 838).
    The extension *.att is used for all attribute files, regardless of the list type used to
    create them. You should thus name the file appropriately.
    5. Click the Save button.
    The Save attributes to file (<network object type>) opens.

    PTVGROUP

    2325

    24.1.12.1 Save list to attribute file

    6. Make the desired changes.


    Element

    Description

    Attribute data file


    is legible

    You cannot read attribute data from the following lists:


    Points of Interest
    GIS objects
    Territories - PuT Detail
    Stop points - Arrivals/Departures
    Evaluation lists (see "Importing and exporting list contents"
    on page 2325)
    Separator
    You can select one of the following separators from the dropdown list:
    Semicolon
    Blank
    Tabulator

    Note
    To read in the attribute files again, select either a semicolon or a
    tabulator as separator.
    List info

    Objects total
    Number of objects in the network
    Objects listed
    Number of active objects in the network
    Objects not listed
    Number of passive objects in the network
    Note
    The list statistics will display the state of the network, if you click
    the

    Identifiers

    Show only active <network objects> icon.

    Identifiers are allocated to attributes that allow for an unambiguous identification of network objects (see "Identifiers" on
    page 2327).

    7. Confirm with OK.


    2326

    PTVGROUP

    24.1.12.1 Save list to attribute file


    The attributes are saved to an *.att file according to the settings.
    Identifiers
    Identifiers identify network objects clearly. They are generated automatically in the first column
    (or columns) when saving an attribute file.
    In the table, you can see which attributes are saved as identifiers for the corresponding network object if you make the respective selection.
    Selection

    Identifiers for
    Links

    Turns

    link-related

    Number, From Node Number

    From Link Number, Via Node


    Number, To Node Number

    node-related

    From Node Number, To Node From Node Number, Via Node


    Number
    Number, To Node Number

    Link-related and node-rela- Link Number, From Node


    ted
    Number, To Node Number
    Line routes

    Time profiles

    Name

    Line Name, Name, Direction


    code

    Line Name, Line route Name,


    Direction code, Name

    ID

    ID (cannot be imported)

    ID (cannot be imported)

    Line route items

    Time profile items

    Name

    Line name, Line route name,


    Direction code, Index

    Line name, Line route name,


    Direction code, Time profile
    name, Index

    ID

    Line route ID, Index (cannot


    be imported)

    Time profile ID, Index (cannot


    be imported)

    For any network object types that are not listed here, there is just the respective standard category of identifiers, which you can select instead of the like list option, for example VehJourneyNo + No for vehicle journey sections.
    If you select the like list option, you might not be able to read in the generated *.att file any
    more, as only those attributes are saved which are displayed in the current list. Identifiers that
    are not displayed in the list window are not saved. An *.att file without identifiers cannot be
    read in and Visum does not check whether the current list contains identifiers.
    Notes: Identifiers cannot be overwritten when reading attribute files.
    If your list contains aliases instead of the usual attribute names, the aliases are saved to
    the attribute file (see "Specifying an alias for attribute names" on page 967) .
    If you read this file once more, Visum first checks whether a column identifier corresponds with an attribute ID. If this is the case, it is suggested. If this is not the case,
    Visum checks whether it is a valid alias.

    PTVGROUP

    2327

    24.1.12.2 Reading attribute data into lists


    24.1.12.2 Reading attribute data into lists
    Attribute values which were saved beforehand can be read from an attribute file into the network currently open (see "Reading an attribute file" on page 2646).
    Note: If you read an attribute file, the attribute values of the current network state are overwritten. If required, save the current network state beforehand.
    24.1.12.3 Exchanging list contents via the Clipboard
    Via the Windows clipboard, you can copy attribute data in order to paste it directly into a different Visum network version or a different program.
    Copying the complete list contents to the clipboard
    1. On the toolbar, click the Copy list to clipboard

    icon.

    The Save attributes (<network object type>) window opens.


    2. Make the desired settings (see "Save list to attribute file" on page 2325).
    3. Confirm with OK.
    The list contents are copied to the clipboard.
    Pasting the complete list contents from the clipboard
    If you want to paste list contents from the clipboard to a Visum list, proceed as follows.
    Tip: In external programs, use the respective paste function, if you want to paste Visum
    list contents.
    1. On the toolbar, click the Paste content from Clipboard

    icon.

    The Read attributes window opens.


    2. Make the desired settings (see "Reading an attribute file" on page 2646).
    3. Confirm with OK.
    The contents saved to the clipboard are inserted.
    Copying and pasting selected attribute values
    You can copy attribute values which are displayed in the list and paste them to another list or
    into an external program.
    Note: You cannot overwrite mandatory input attributes. They are grayed out.
    1. In the list, mark the section(s) that you want to copy (see "Selecting list sections" on page
    2319).
    The sections have been selected.
    2. Press CTRL + C.
    2328

    PTVGROUP

    24.1.12.4 Exporting attributes to a database


    3. Click the top-left cell of the section into which you would like to paste the data.
    4. Press CTRL + V.
    The copied values are pasted.
    Note: If list sections are selected which are not adjacent then the data in the sections inbetween will neither be copied nor pasted.
    Tip: You can also copy data via the Copy cells and Paste cells entries in the context
    menu.
    24.1.12.4 Exporting attributes to a database
    You can save the attributes of a list to a newly created or an existing database.
    Notes: If your list contains aliases instead of the usual attribute names, the aliases are
    saved to the database (see "Specifying an alias for attribute names" on page 967).
    For lists of the types PuT path legs and PrT paths on link level, select an appropriate
    export format prior to data export (see "Formatting the path list for database export" on
    page 2330).
    1. On the toolbar, click the

    button Save list to database.

    A query opens.

    2. Select the desired database format.


    3. Confirm with OK.
    Another window opens. Further proceedings depend on the format which you have chosen.
    Exporting attributes to an access database
    1. Select the option MS Access 2003 or earlier or MS Access 2007 or up.
    The Save Access 2007 database window opens.
    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The Save attributes to database (<network object type>) window opens.
    4. Make the desired changes (see "Save list to attribute file" on page 2325).
    5. Confirm with OK.
    The list content is saved to the database, where it can be edited.
    PTVGROUP

    2329

    24.1.12.4 Exporting attributes to a database


    Exporting attributes to an SQL database
    1. Select the MS SQL server option.
    The Data link properties window opens.
    2. Make sure that the Provider tab is selected.
    3. In the list, select a suitable provider, for example Microsoft OLE DB Provider for SQL Server.
    4. Click Next.
    The Connection tab is displayed.
    5. Enter a Server name or select a name in the list.
    6. Under User name, enter a name for the access to the SQL server.
    7. Under User name, enter a password for the access to the SQL server.
    8. Select the Allow saving of password option.
    9. Under topic 3, select a database from the list.
    10. If required, check the connection to the server by clicking the Check connection button.
    11. Confirm with OK.
    The Save attributes to database (<network object type>) window opens.
    12. Make the desired settings (see "Save list to attribute file" on page 2325).
    13. Confirm with OK.
    The list content is saved to the database, where it can be edited.
    Formatting the path list for database export
    You can export the PuT path leg list or the PrT paths on link level list to a database, if you specify the following settings.
    1. Open the desired list (see "Opening a list" on page 2299).
    The list is displayed.

    2. Under Format, select a display suitable for databases.


    2330

    PTVGROUP

    24.1.13 Printing a list and print settings

    Element

    Description

    Standard

    A header displays the basic information on the respective path.


    Below, the sections of the path are listed in which the key
    columns Origin zone number, Destination zone number, and
    Path Index are not allocated.
    Note
    This view offers the best overview. However, the list cannot be
    exported to a database in this view as the key columns are not filled in each row.

    suitable for databases (with header)

    Both in the header as in the rows of the individual sections, all


    key data are put first. The data can be exported to a database.
    Note
    The Index (PrT) and the Path leg index (PuT) columns display a
    zero in the header of the respective path.

    suitable for databases (without


    header)

    This view does not display a header. All key data are put first in
    each row. The data can be exported to a database.

    Tip: Alternatively, you can specify this setting in the List (PuT path legs) > Format
    menu.
    The list is displayed in the selected format.
    Tip: The setting of the Format option is saved with the list layout file (see "Saving a list
    layout" on page 2313).

    24.1.13 Printing a list and print settings


    You can print a list and specify settings for the printout beforehand.
    24.1.13.1 Specifying the layout for list printout
    You can specify the additional components that you want to print and the layout of the list printout.
    Setting margins for list printout
    1. In the List (<Network object type>) menu, select the Set print page entry.
    The window Lists: Set print page opens.
    Tip: Alternatively, in the File menu, point at Print and select the Set print page command, or in the Print: List window, click the Set print page button.
    2. In the Lists: Set print page window, select the Margins tab.
    3. Make the desired changes.

    PTVGROUP

    2331

    24.1.13.1 Specifying the layout for list printout

    Element

    Description

    Paper margin
    [mm]

    Here you can specify the desired distance from the paper margin.

    4. Confirm with OK.


    Specifying a print frame for the list printout
    1. In the List (<Network object type>) menu, select the Set print page entry.
    The window Lists: Set print page opens.
    2. In the Lists: Set print page window, select the Print frame tab.
    3. Make the desired changes.
    Element

    Description

    Print frame

    Draw
    If the option has been selected, a print frame is printed.
    Boundary
    To specify the display of the frame, click in the field (see "Setting the
    line style properties" on page 2363).

    4. Confirm with OK.


    Specifying a header for the list printout
    1. In the List (<Network object type>) menu, select the Set print page entry.
    The window Lists: Set print page opens.
    2. In the Lists: Set print page window, select the Header tab.
    3. Make the desired changes.

    2332

    PTVGROUP

    24.1.13.1 Specifying the layout for list printout


    Element

    Description

    Display

    Draw
    If the option has been selected, a header is printed.
    Font
    In a separate window, you can specify a Font and a Style by clicking in
    the field.
    Text size
    Text size in mm
    Color
    In a separate window, you can specify a color for the header by
    clicking in the field.
    Note
    You can position the header left, right or centered, if you click the
    respective icon.
    Minimum line height
    If the option has been selected, you can enter a minimum height for the
    row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    Text

    Use the drop-down list to select an entry which shall be inserted in the
    header.
    user-defined
    Here you can enter a text into the empty field.
    empty
    [VISUM version]
    Created on: [Date]
    Created on: [Date] / [Time]
    [Date] / [Time]
    [File name]
    [NetworkObjectType]
    [PageNumber]
    [NumberPages]
    Page [PageNumber] / [NumberPages]
    [ListHeader]
    Select this option to print the list header as the header.

    Help

    Use the button to open a window with all available auto values.
    Note
    The entries in squared brackets are pre-defined by the program (auto
    values). They are replaced with the current values when printing the
    list. Auto values are language-dependent and can also be utilized as
    user-defined entries.

    PTVGROUP

    2333

    24.1.13.1 Specifying the layout for list printout


    4. Confirm with OK.
    Tables in the list printout
    1. In the List (<Network object type>) menu, select the Set print page entry.
    The window Lists: Set print page opens.
    2. In the Lists: Set print page window, select the Table tab.
    3. Make the desired changes.
    Element

    Description

    Display

    Here you can specify the display of the printed table.


    Font
    In a separate window, you can specify a Font and a Style by clicking in
    the field.
    Text size
    Text size in mm
    Color
    In a separate window, you can specify a color for the table by clicking
    in the field.
    Minimum line height
    If the option has been selected, you can enter a minimum height for the
    row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    4. Confirm with OK.


    Specifying a footer for the list printout
    1. In the List (<Network object type>) menu, select the Set print page entry.
    The window Lists: Set print page opens.
    2. In the Lists: Set print page window, select the Footer tab.
    3. Make the desired changes.

    2334

    PTVGROUP

    24.1.13.1 Specifying the layout for list printout


    Element

    Description

    Display

    Draw
    If the option has been selected, a footer is printed.
    Font
    In a separate window, you can specify a Font and a Style by clicking in
    the field.
    Text size
    Text size in mm
    Image height
    Size of inserted graphics in mm
    Tip
    Graphics can be inserted via the drop-down lists in the Text section.
    Color
    In a separate window, you can specify a color for the footer by clicking
    in the field.
    Minimum line height
    If the option has been selected, you can enter a minimum height for the
    row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    Column format

    You can regulate the width of each column by entering a percentage.


    Notes
    The total need not amount to 100%. The width will be calculated proportionately.
    You can position the column contents left aligned, centered or right aligned by clicking the respective icon below.

    Text

    Use the drop-down list to select an entry which shall be inserted in the
    footer.
    user-defined
    Here you can enter a text into the empty field.
    empty
    [VISUM version]
    Created on: [Date]
    Created on: [Date] / [Time]
    [Date] / [Time]
    [File name]
    [NetworkObjectType]
    [PageNumber]
    [NumberPages]

    PTVGROUP

    2335

    24.1.13.2 Printing a list


    Element

    Description
    Page [PageNumber] / [NumberPages]
    [ListHeader]
    Select this option to print the list header as the header.
    [Graphics]
    If you select this option, in the list box, you can click the path to the
    image you want to display.

    Help

    Use the button to open a window with all available auto values.
    Note
    The entries in squared brackets are pre-defined by the program (auto
    values). They are replaced with the current values when printing the
    list. Auto values are language-dependent and can also be utilized as
    user-defined entries.

    4. Confirm with OK.


    24.1.13.2 Printing a list
    You can print the list content.
    Tip: You can make various print settings before printing a list (see "Specifying the layout
    for list printout" on page 2331).
    1. On the toolbar, click the

    Print icon.

    The Print: List window opens.


    2. Under Name, select an output device.
    3. To make additional settings, click the Set print page button (see "Printing the network display" on page 2499).
    Notes: When selecting a format, select the number of columns and rows as well as
    the column width and the font size.
    The list is printed on several pages if it does not fit on one page.
    4. Confirm with OK.
    The Print information window opens. It displays the number of pages and rows to be printed.
    5. Confirm with OK.
    The list is printed.
    24.1.13.3 Saving the list as a PDF

    2336

    PTVGROUP

    24.2 Specifying basic settings for the network window


    Tips: Lists saved as PDF files can easily be included in text documents.
    You can make various layout settings before saving a list as a PDF file (see "Specifying
    the layout for list printout" on page 2331).
    1. On the toolbar, click the

    Print icon.

    The Print: List window opens.


    2. Under Name, select the PDF option.
    3. Confirm with OK.
    The Save PDF as window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The Print information window opens. It displays the number of pages and rows to be printed.
    6. Confirm with OK.
    The PDF is created and the file is opened.

    24.2

    Specifying basic settings for the network window


    In the network window, you can adjust some basic settings for the graphical display of network
    objects.
    Note: Also for the windows listed below for example, graphic parameter settings can be
    adjusted:
    Smart Map (see "Setting the graphic parameters for the Smart map window" on
    page 816)
    Matrix editor window (see "Setting graphic parameters for the Matrix editor window"
    on page 1749)
    Timetable editor (see "Setting the graphic parameters of the tabular timetable" on
    page 1573)

    24.2.1

    Specifying basic settings


    In the basic settings, you can for example specify the color in which the marked network
    objects will be displayed or whether a legend will be drawn or not.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    .

    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.
    2. In the navigator, select the Basis entry.

    PTVGROUP

    2337

    24.2.1 Specifying basic settings

    3. Make the desired changes.

    2338

    Element

    Description

    Comment

    Here you can insert an internal comment on the graphic parameters.

    Draw legend

    If the option is selected, a legend is drawn (see "Creating


    legends" on page 2255).
    Note
    The display of the legend might overlap parts of the network display.

    Text sizing factor


    screen

    The text size displayed on screen results from the text size specified for each network object or graphic object in mm the text
    sizing factor specified here.
    Note
    The text sizing factor does not have an effect on printouts or
    during exports. It only affects the display on screen.

    Marking 1
    Marking 2

    You can specify the color and the stroke width for marked and
    related network objects in a separate window by clicking in the
    respective field.
    Note
    Marked network objects are displayed in Marking 1, related network objects in Marking 2.

    PTVGROUP

    24.2.2 Editing the display and order of drawing settings for graphic layers
    Element

    Description
    Note
    The marker settings on the Basis page are overwritten by the settings in the Marked tab, which you can set for individual objects
    (see "Displaying marked point objects" on page 2347).
    Use for all markings
    Via this button, you can apply the color specified for Marking 1 to
    the marked objects of all object types.
    Note
    As a result, the settings of the Marked tab of the respective object
    are overwritten.

    Coordinates

    Coordinates of the current network and the network section


    currently displayed on screen

    Note: If you click the Preview button, your changes will immediately be displayed
    though the Edit graphic parameters window is still open.
    4. Confirm with OK.
    The basic settings are applied.

    24.2.2

    Editing the display and order of drawing settings for graphic layers
    The network object types constitute individual layers which, in the network display, are drawn
    on top of each other. You can show or hide single graphic layers and specify the order of the
    layers.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.

    The Edit graphic parameters window opens.


    2. In the navigator, select the Layer entry.

    Tip: You can also call this page via the

    PTVGROUP

    Edit graphics layers icon.

    2339

    24.2.2 Editing the display and order of drawing settings for graphic layers

    3. Make the desired changes.


    Element

    Description

    Draw

    If the option has been selected, the layer is displayed in the network display.
    Tip
    Alternatively, you can hide or show the layer of certain network
    object types via the Overview window: In the Network tab, click
    the icon of the object type.

    Layer

    The list reproduces the drawing order of the layers. The layer at
    the bottom of the list is drawn first, the one at the top last.
    Note
    Each layer can overlap parts of previously drawn layers.

    Draw legend

    If the option has been selected, a legend is drawn (see "Creating


    legends" on page 2255).
    Note
    The display of the legend might overlap parts of the network display.
    Via these icons, you either select all layers or deselect all selected layers.

    4. If required, edit the order of the drawn layers in the list with the aid of the
    and mark the desired layer in the list.
    2340

    and

    icons

    PTVGROUP

    24.3 Displaying point objects in the network window

    Note: If you click the Preview button, your changes will immediately be displayed
    though the Edit graphic parameters window is still open.
    5. Confirm with OK.
    The settings are applied.

    24.3

    Displaying point objects in the network window


    Point objects are co-ordinate-bound network objects. Some point objects have polygons. The
    following network objects are point objects:
    Nodes and main nodes
    Stops, stop points and stop areas
    Count locations and detectors
    Zones, main zones, territories, toll systems
    Points of Interest and GIS objects
    For point objects, you can define how they are to be displayed in the network window. You can
    specify different settings for active, passive and marked point objects.
    Note: Tables or charts can be used for point object labeling (see "Labeling network
    objects with tables or charts" on page 2402).

    24.3.1

    Displaying active point objects


    You can configure the display of active point objects in the network window. The uniform display of point objects is described below. You can also display objects classified by attribute
    values (see "Displaying classified objects based on attribute values" on page 2411).
    1. In the Graphics menu, select the Edit graphic parameters entry.
    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Zones entry.
    Note: The graphic parameters for all point objects are nearly identical. This example
    describes the settings for the point-type object 'zone'.
    3. Make the desired changes.

    PTVGROUP

    2341

    24.3.1 Displaying active point objects


    Element

    Description

    Draw zones
    layer

    If the option has been selected, the layer is displayed in the network
    display.
    If the option has not been selected, the objects are not displayed.

    Avoid overIf the option has been selected, only point objects are drawn that do
    lapping when not overlap one another.
    drawing
    Note
    This applies to the centroid of two-dimensional point objects, not to
    their boundaries or faces. Tables and charts are only displayed if they
    do not overlap (see "Labeling network objects with tables or charts" on
    page 2402). They can, however, overlap point objects.
    If the option is not selected, all point objects of a layer are displayed,
    even if they overlap one another.
    Tip
    Zoom into the overlapping section, if required.
    4. In the navigator, select the entry Zones > Display > tab Active.
    Tip: Alternatively, you can call the graphic parameters page Display for a network
    object type by right-clicking the respective icon of the network object type in the Network window.

    5. Make the desired changes.

    2342

    PTVGROUP

    24.3.1 Displaying active point objects


    Element

    Description

    Uniform display

    If the option has been selected, all active objects are drawn consistently.
    Note
    The options described below are displayed if you select the uniform display.

    Classified display

    If the option has been selected, active objects can be classified and
    displayed by an attribute (see "Displaying classified objects based
    on attribute values" on page 2411).

    Options for the


    uniform display

    Preview
    Here you can see how a zone will be displayed according to the
    current settings.
    Draw object
    If the option has been selected, active point objects are displayed.
    Draw until scale
    If the option has been selected, point objects are drawn up to the
    set scale when zooming out (see "Editing the network scale" on
    page 2209).
    If the option has not been selected, the point objects are always
    displayed, no matter what scale is used in the network.
    Draw table
    If the option has been selected, point objects are labeled with a
    table, according to the settings on the Table page (see "Labeling
    network objects with tables" on page 2402).
    Draw chart
    If the option has been selected, point objects are labeled with a
    chart, according to the settings on the Chart page (see "Labeling
    network objects with column charts" on page 2405).
    Draw polygon
    If the option has been selected, existing margins and faces of twodimensional point objects are drawn. You can specify the fill style,
    the color, and a line style in a separate window. To do so, click in
    the field (see "Editing the properties of a closed polygon" on page
    2252).
    Note
    The option is only available for the network objects zones, main
    zones, POIs, main nodes, and toll systems.

    Point object type Here you select if the point object is displayed as text, symbol, or
    image.
    Tex-

    PTVGROUP

    Depending on the selected option, the point object is displayed as

    2343

    24.3.1 Displaying active point objects

    2344

    Element

    Description

    t/Symbol/Image

    text, symbol or image. The settings change accordingly.

    Text

    If the Text option is selected, the point object is displayed as a text.


    Content
    Via the button, select the attribute. The values of this attributes are
    used for the display of the point objects.
    Size
    Text size in mm
    Font
    You can specify the font and the style in a separate window by
    clicking in the field.
    Transparent
    If the option has been selected, the text is displayed without the
    white background, as text only.
    Color
    Use the selection list to select a color for the text.
    Frame
    If the option has been selected, the text is framed. Use the dropdown list to select a color for the text frame.
    Round
    Rounding factor for the attribute values
    Decimal places
    Enter the number of decimal places for the display of the attribute
    values.
    Note
    The option is only available for numerical attributes of the type decimal place.

    Symbol

    If the Symbol option is selected, the point object is displayed by the


    selected symbol.
    In the drop down list, you can select one of the following symbols:
    Circle
    Square
    Triangle
    Cross
    Stop (German)
    Stop (English)
    POI
    Signal control
    Stop sign
    Open arrow

    PTVGROUP

    24.3.1 Displaying active point objects


    Element

    Description
    Two-way stop
    Roundabout
    Two-way yield
    Size
    Symbol size in mm
    Color
    Use the drop-down list to select a color for the symbol . (see
    "Editing the properties of a closed polygon" on page 2252).
    Sign
    If you select the Circle or Square symbol, you can activate the
    input field by checking the box. In the input field, you can enter a
    sign which will be displayed inside the circle or square. Use the
    drop-down list to select a color for the sign.

    Image

    If the Image option has been selected, the point object is displayed
    by means of a graphic file.
    For the display of the point objects, you can select an image file
    (*.bmp, *.jpg, etc.) via the
    button.
    Notes
    When you have selected an image file, a query opens. Once you
    have confirmed the query, the specified height is replaced with the
    current image size. A preview displays the selected image file.
    The image file is inserted as link and will not be saved with the version file. If Visum does not find the path to the image file the next
    time it is opened, a warning is issued and the graphic will not be
    displayed. We thus recommend that all image files are saved to
    one directory which should be specified in the project directory file
    (see "Editing the storage location of files" on page 837).
    Height
    Image height in mm
    Description
    Draw

    If this option is checked, the image will be labeled. Click this button
    to open a separate window and select an attribute of the particular
    network object type for the labels.
    Height

    Height of the label (as percentage of the image height)


    Round

    Rounding factor for the attribute values


    Color

    PTVGROUP

    2345

    24.3.2 Displaying passive point objects


    Element

    Description
    Use the selection list to select a color for the labels.
    Decimal places

    Enter the number of decimal places for the display of the attribute
    values.
    Note
    The option is only available for numerical attributes of the type decimal place.

    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    6. Confirm with OK.
    The point objects are displayed according to your chosen settings.

    24.3.2

    Displaying passive point objects


    You can configure the display of passive network objects in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the page <Network object type> Display> Passive tab.

    3. Make the desired settings (see "Displaying active point objects" on page 2341).
    2346

    PTVGROUP

    24.3.3 Displaying marked point objects


    4. Confirm with OK.
    The passive objects are displayed according to your settings.

    24.3.3

    Displaying marked point objects


    You can configure the display of marked network objects in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the page <Network object type> Display> Marked tab.

    3. Make the desired settings (see "Displaying active point objects" on page 2341).
    4. Confirm with OK.
    The marked objects are displayed according to your settings.

    24.3.4

    Displaying traversed stop points


    You can specify particular settings for the display of stop points that are not served.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Stop points > Display > tab Traversed.

    PTVGROUP

    2347

    24.3.5 Displaying Points of Interest

    3. Make the desired settings (see "Displaying active point objects" on page 2341).
    4. Confirm with OK.
    Traversed stop points are displayed according to your chosen settings.

    24.3.5

    Displaying Points of Interest


    You can set special display options for Points of Interest (POIs).

    24.3.5.1

    Displaying Points of Interest


    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Points of Interest.

    2348

    PTVGROUP

    24.3.5.1 Displaying Points of Interest


    3. Make the desired changes.
    Element

    Description

    Draw layer POI


    points

    If this option is checked, the POI symbols or images will be displayed in the network window.

    Draw layer POI


    lines

    If this option is checked, the POI line shapes will be displayed in the
    network window. Furthermore, allocations of POIs are viewed as
    connections.
    Note
    Line-shaped POIs cannot be created by the user. You can generate
    them by importing a network file or a shape file.

    Draw layer POI


    polygons

    If this option is checked, polygons of POIs will be displayed in the


    network window.

    4. In the POI categories navigator, use the check boxes to select the categories which are to
    be displayed.
    Notes: Via the icons you can change the settings for several categories simultaneously:
    Check all POI categories
    Uncheck all POI categories
    Invert the POI category selection
    Tips: Use the icons to expand or close the navigator tree of the POI categories:
    Expand tree
    Reduce tree
    Next to the POI category, the POI preview appears according to the current settings.
    5. In the POI category list on the right, define the order for POI drawing.
    Notes: Click a category and click either icon:
    Shift POI category down: Layer will be drawn earlier
    Shift POI category up: Layer will be drawn later
    POI categories which are currently not displayed in the network window are gray-shaded in the list.
    6. Make the settings for the individual POI categories (see "Editing the display settings of a
    POI category" on page 2350).

    PTVGROUP

    2349

    24.3.5.2 Editing the display settings of a POI category


    7. Confirm with OK.
    According to your settings, the POIs are either displayed or faded out.
    24.3.5.2

    Editing the display settings of a POI category


    You can configure how the POIs of a POI category are to be displayed. If sub-categories have
    been defined for a POI category, the category settings can be applied to all sub-categories.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Points of Interest.
    3. In the POI category navigator, click the desired POI category.
    4. Click the

    Edit icon.

    The window Edit graphics parameters for POI category window opens.
    5. Make the desired changes (see "Displaying point objects in the network window" on page
    2341).
    6. Click the button to confirm.
    Element

    Description

    Apply to category

    The settings only apply to the selected POI category.

    Apply to category and


    sub-categories

    The settings only apply to the selected POI category and all
    included sub-categories.

    7. Confirm with OK.


    The POIs of the POI category are displayed according to the current settings.
    Note: For individual POIs, you can select a different image as their symbol (see "Changing the symbol of an individual POI" on page 1389).
    24.3.5.3

    Applying display settings to sub-categories


    The graphics parameters settings made for a POI category can also be applied to its sub-categories.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Points of Interest.
    3. In the POI category navigator, click the desired POI category.
    4. Click icon

    Apply the POI category graphics parameters to the sub-categories.

    The settings are copied from the selected POI category to the sub-categories of this category.

    2350

    PTVGROUP

    24.3.5.4 Defining the standard display for the display of POIs


    24.3.5.4

    Defining the standard display for the display of POIs


    You can select a standard image and define a standard height.. This standard image will only
    be displayed if for the particular POI category or for the particular POI itself no other image has
    been selected.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Points of Interest> Standard display.
    3. Make the desired changes.
    Element

    Description

    Standard
    image

    You can display all POIs by means of an image file, if you read in an
    button.
    image file (*.bmp, *.jpg, etc.) via the
    Notes
    When you have selected an image file, a query opens. Once you have
    confirmed the query, the specified height is replaced with the current
    image size. A preview displays the selected image file.
    The image file is inserted as link and will not be saved with the version
    file. If Visum does not find the path to the image file the next time it is opened, a warning is issued and the graphic will not be displayed. We thus
    recommend that you save all image files to one directory set in the project directory file, before you insert POIs (see "Editing the storage location of files" on page 837).

    Height

    Height of the standard image

    Preview

    Preview of the standard display of POIs according to the current settings

    4. Confirm with OK.


    The standard image has been defined.
    24.3.5.5

    Showing POI connections


    You can show allocations between POIs and other network objects as connections in the network window (see "POIs: Allocations tab" on page 1388).
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Points of Interest> Connections.
    3. Make the desired changes.

    PTVGROUP

    2351

    24.3.6 Displaying GIS objects


    Element

    Description

    Draw POI
    connections
    only for active
    POIs

    If the option has been selected, only connections of active POIs will
    be drawn.

    Connections

    Draw
    Via the check boxes, you can enable or disable the display of the
    connections for each network object type separately.
    Note
    In a separate window, you can select a color and a line type for the
    display of the different connections by clicking in the respective
    field. The field displays the current settings.
    Size of arrow head
    Size of the arrow head in mm

    4. Confirm with OK.


    The allocations are displayed by connecting lines.

    24.3.6

    Displaying GIS objects


    If you are connected to a Personal Geodatabase, you can specify the graphic settings for the
    display and labeling of GIS objects in the network (see "GIS objects" on page 2211).

    24.3.7

    Two-dimensional display of attribute values around point objects


    For point objects (for example nodes or stops), a two-dimensional display of the attribute value
    distribution is possible. Any numerical attribute can be selected for this purpose (see Fundamentals: Chpt. 12.12 , page 768).
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry 2D display.

    2352

    PTVGROUP

    24.3.7 Two-dimensional display of attribute values around point objects

    3. Make the desired changes.


    Element

    Description

    Criterion (iso- Current route choice criterion for PrT isochrones (see "Displaying isochrones)
    chrones and the accessibility of network objects" on page 2278)
    2D display

    In 2D display, the complete screen is colored. The color of any point


    results from the attribute value to the next network object.
    Active
    If the option has been selected, the selected attribute is displayed in
    2D.
    Smooth color transition
    If the option has been selected, smooth color transitions visualize increasing or decreasing attribute values.
    Difference display
    If the option has been selected, for each network object the difference
    between the selected attributes is calculated and displayed according
    to the current classification settings.
    tMax-access (access time)
    For attribute values with an extrapolated attribute value > tMaxaccess, the program uses the color specified for the class Not
    reached.

    Attributes

    Here you can select one or two point objects for the two-dimensional

    PTVGROUP

    2353

    24.4 Displaying line objects in the network window


    Element

    Description
    display.
    Factor
    Prior to the extrapolation, the source attribute values of the point
    objects are multiplied by this factor.
    V-access
    Extrapolation speed for the calculation of the attribute values of point
    objects along virtual lines into the network area to each pair of co-ordinates.

    Picture quality

    Here you can specify the speed/quality ratio for the graphical output.

    Classification

    Time/Color
    Set the intervals according to the values of the selected attribute. For
    each class, you can select a specific color in the selection list.
    Not reached
    All network objects which have an extrapolated attribute value higher
    than the current value tMax-access, are displayed in this color.
    Note
    The times and the colors in the Classification section also apply to PrT
    isochrones (see "Displaying isochrones and the accessibility of network objects" on page 2278).

    Value ranges Multiply


    You can multiply the interval values in the Classification section with
    the specified factor by clicking on the button.
    Factor
    Enter the desired factor.
    Tip
    With an appropriate factor, you can adjust the current interval values for
    a different unit.
    4. Confirm with OK.
    The attribute values are displayed according to your chosen settings.

    24.4

    Displaying line objects in the network window


    You can specify how to display line objects in the network window. You can set up different settings for active, passive and marked line objects.
    The following network objects are line objects:
    Links
    Connectors
    Screenlines

    2354

    PTVGROUP

    24.4.1 Displaying active line objects


    You can also display line routes in the network window (see "Displaying route courses in the
    network window" on page 2387).
    Note: In addition, you can show bars for links, connectors, and along lines or paths (see
    "Displaying properties via bars" on page 2367).

    24.4.1

    Displaying active line objects


    You can configure the display of active line objects in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Links entry.
    Note: The graphic parameters for all line objects are nearly identical. This example
    describes the settings for the line-type object 'link'.

    3. Make the desired changes.

    PTVGROUP

    2355

    24.4.1 Displaying active line objects


    Element

    Description

    Draw layer Here you can specify which elements of the link layer will be displayed.
    links
    If the option has been selected, links are displayed in the network display.
    If the option has not been selected, the subordinate options are
    grayed out.
    Draw: Links
    If the option has been selected, links are displayed.
    Draw labels
    If the option has been selected, the links are labeled(see "Labeling line
    objects" on page 2359).
    Draw bars
    If the option has been selected, link bars are displayed (see "Displaying
    properties via bars" on page 2367).
    Draw bar labels
    If the option has been selected, the link bars are labeled.
    Drawing
    order

    The list shows the order in which the layers are drawn. Use the

    and

    icons to edit the order of the drawn layers.


    4. In the navigator, select the entry Links> Display > tab Active.
    Tip: Alternatively, you can call this page as follows: In the Network window, right-click
    the icon of the network object type.

    2356

    PTVGROUP

    24.4.1 Displaying active line objects

    5. Make the desired changes.


    Element

    Description

    Uniform
    display

    If the option has been selected, all active objects are drawn consistently.

    Classified If the option has been selected, active objects can be classified and disdisplay
    played by an attribute (see "Displaying classified objects based on attribute values" on page 2411).
    Options for In this section, specify how the line objects are drawn.
    the uniform Preview
    display
    Here you can see how a link will be drawn according to the current settings.
    Draw object
    If the option has been selected, active point objects are displayed.
    Draw until scale
    If the option has been selected, line objects are drawn up to the set
    scale when zooming out (see "Editing the network scale" on page 2209).
    If the option has not been selected, the line objects are always displayed, no matter what scale is used in the network.
    Line style
    Here you can specify the style in which the lines are drawn (see "Setting
    parameters for the line style" on page 2365).

    PTVGROUP

    2357

    24.4.2 Displaying passive line objects


    Element

    Description
    Draw: Arrow head
    If the option has been selected, an arrow head is drawn. Specify the following settings for the arrow head.
    Via the drop-down list, select the symbol that will be displayed as arrow
    head.
    Size

    Size of arrow head in mm


    Color
    You can specify a color for the arrow head in a separate window. To do
    so, click in the field (see "Editing the properties of a closed polygon" on
    page 2252).
    Sign
    If you select the Circle or Square symbol, you can activate the input field
    by checking the box. In the input field, you can enter a sign which will be
    displayed inside the circle or square. Use the drop-down list to select a
    color for the sign.
    Note: If you click the Preview button, your changes will immediately be displayed
    though the Edit graphic parameters window is still open.
    6. Confirm with OK.
    The line objects are displayed according to your chosen settings.

    24.4.2

    Displaying passive line objects


    You can configure the display of passive line objects in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the page <Network object type> Display> Passive tab.
    3. Make the desired settings (see "Displaying active line objects" on page 2355).
    Note: Classification cannot be applied to passive line objects.
    4. Confirm with OK.
    The passive objects are displayed according to your settings.

    24.4.3

    Displaying marked line objects


    You can configure the display of marked line objects in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.

    2358

    PTVGROUP

    24.4.4 Displaying one-way roads


    2. In the navigator, select the page <Network object type> Display> Marked tab.
    3. Make the desired settings (see "Displaying active line objects" on page 2355).
    Note: Classification cannot be applied to marked line objects.
    4. Confirm with OK.
    The marked objects are displayed according to your settings.
    Note: Closed marked links are always displayed as thin lines, independent of the settings for marked links.

    24.4.4

    Displaying one-way roads


    You can specify special settings for the display of one-way roads. A one-way road is a link
    which, in one direction, is closed to all transport systems. The transport system Walk constitutes an exception as it can be open.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the page Links > Display > tab One-way roads.
    3. Make the desired changes (see "Displaying active line objects" on page 2355).
    4. Confirm with OK.
    The one-way roads are displayed according to your chosen settings.
    Note: In case of undirected values, one-way roads are labeled direction-based in the bar.
    Tip: If you want to display one-way roads or planned links, you can also classify links by
    the following attributes: IsOneWayRoad, IsOneWayRoad_TSys or PlanNo (see "Displaying classified objects based on attribute values" on page 2411).

    24.4.5

    Labeling line objects


    For links, connectors, and screen lines, the labels can be texts, symbols or images.
    Notes: The label of a line object is displayed half-way along the object.
    You can also use tables or charts to label line objects (see "Labeling network objects
    with tables or charts" on page 2402).

    24.4.5.1

    Labeling active line objects


    You can configure how active line objects are to be labeled in the network window.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the <Network object type> entry.

    PTVGROUP

    2359

    24.4.5.1 Labeling active line objects


    3. Select the option Draw labels.
    4. In the navigator, select the <Network object type> > Label entry.
    Tip: You can avoid an overlap of labels if you select the Avoid overlapping when drawing option. Labels are only displayed if they do not overlap.
    5. Select the page Links > Label > Display > tab Active.
    6. Make the desired changes (see "Displaying active point objects" on page 2341).
    Note: If you click the Preview button, your changes show immediately without the Edit
    graphic parameters window being closed.
    7. Confirm with OK.
    The labels of line objects are displayed according to your chosen settings.
    Example: Link labels by class
    By combining classified labels, external image files, and attribute displays as tables or charts,
    you can for example compose road class-dependent line object labels of symbols and network object attributes.
    On page Links > Labels > Display > tab Active, you can for example classify by attribute
    TypeNo and label the different link types with images, symbols and texts, as well as with
    tables and charts.
    The following settings result in the subsequent graphical display in the network:

    2360

    PTVGROUP

    24.4.5.1 Labeling active line objects

    PTVGROUP

    2361

    24.4.5.2 Labeling passive line objects

    24.4.5.2

    Labeling passive line objects


    You can configure how passive line objects are to be labeled in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the <Network object type> entry.
    3. Select the option Draw labels.

    2362

    PTVGROUP

    24.4.5.3 Labeling marked line objects


    4. In the navigator, select the page <Network object type> Label > Display> Passive tab.
    5. Make the desired settings (see "Labeling active line objects" on page 2359).
    Note: Classified labeling cannot be applied to passive line objects.
    6. Confirm with OK.
    The passive objects are displayed according to your chosen settings.
    24.4.5.3

    Labeling marked line objects


    You can configure how marked line objects are to be labeled in the network window.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the <Network object type> entry.
    3. Select the option Draw labels.
    4. In the navigator, select the page <Network object type> Label > Display> Marked tab.
    5. Make the desired settings (see "Labeling active line objects" on page 2359).
    Note: Classified labeling cannot be applied to marked line objects.
    6. Confirm with OK.
    The marked objects are displayed according to your settings.

    24.4.6

    Setting the line style properties


    For some objects, you can specify the line style as follows.
    1. Click in the respective field.
    The Line style parameters window opens.

    PTVGROUP

    2363

    24.4.6 Setting the line style properties

    2. Make the desired changes.


    Element Description
    Preview Here you can see how the line will be drawn.
    Width

    2364

    Line width in mm

    PTVGROUP

    24.4.7 Setting parameters for the line style


    Element Description
    Color

    In a separate window, you can specify a color for the line by clicking in the
    field.

    Line
    style

    The line style is composed of individual square "units" that determine the
    lengths and the distance of the displayed points or lines. You can also set a
    user-defined line style if you move the indicator along the scale and check
    single units.
    Alternatively, you can select a line style template.
    Notes
    Active units (black) are displayed as points or lines in the selected color and
    line width. Inactive units (white) are transparent and indicate the distance
    between two points or lines.
    The length of an individual line or a distance is based on the number of
    units per line or distance width of a single element. A line consisting of four
    units, for example, will be displayed at a length of 4 mm in the network display, if the width of the element is 1 mm.
    The height of each unit is determined by the set line width (=Width).
    Width of a single element
    Length of each unit in mm
    Note
    The indicator determines the total length of the pattern (= number of units
    width of the element).
    Line style templates
    Via this button, the Line style templates window opens. In this window, you
    can select a template for the line.
    Note
    The user-defined line style will be overwritten if you select a template. Line
    width and line color remain unchanged.

    3. Confirm with OK.


    The line is displayed according to your chosen settings.

    24.4.7

    Setting parameters for the line style


    You can define the line style in different program areas as follows:
    1. Click in the Line style field.
    The Line style parameters window opens.

    PTVGROUP

    2365

    24.4.7 Setting parameters for the line style

    2. Make the desired changes.


    Element

    Description

    Total preview

    Here you can see the display of all stroke layers together.

    Stroke
    layer

    Here you can see the individual layers which are drawn on top of each
    other.
    Via the
    and

    2366

    and

    buttons, you can insert or delete single layers. Via the

    buttons, you can edit the order in which the layers are drawn.

    PTVGROUP

    24.5 Displaying properties via bars


    Element

    Description

    Line style
    properties

    Adjust the settings for the selected layer.


    Preview
    Call the preview of the selected layer.
    Width
    Line width in mm.
    Color
    Use the drop-down list to select a color for the layer.

    Line style

    The line style is composed of individual square unitsthat determine the


    lengths and the distance of the displayed points or lines. You can also
    set a user-defined line style if you move the indicator along the scale
    and check single units.
    Alternatively, you can select a line style template.
    Notes
    Active units (black) are displayed as points or lines in the selected color
    and line width. Inactive units (white) are transparent and indicate the
    distance between two points or lines.
    The length of an individual line or a distance is based on the number of
    units per line or distance width of a single element. A line consisting of
    four units, for example, will be displayed at a length of 4 mm in the network display, if the width of the element is 1 mm.
    The height of each unit is determined by the set line width (=Width).
    Width of a single element
    Enter the length of each unit in mm.
    Note
    The indicator determines the total length of the pattern (= number of units
    width of the element).
    Line style templates
    Via this button, the Line style templates window opens. In this window,
    you can select a template for the line display.
    Note
    The user-defined line style will be overwritten if you select a template.
    Line width and line color remain unchanged.

    3. Confirm with OK.


    The line style is displayed according to your chosen settings.

    24.5

    Displaying properties via bars


    Along links and connectors, you can display one or multiple bars. Bars represent attribute
    values of the network objects, such as volumes. Bars along links can also represent the

    PTVGROUP

    2367

    24.5.1 Displaying bars and adjusting basic settings


    properties of lines or paths traversing these links.

    Turn volumes are a specific bar display type displayed along (main) turns (see "Displaying
    turns, main turns, and turn volumes" on page 2435).
    Matrix flow bundles are bars displayed along the virtual direct distance line of OD pairs, i.e. between (main) zones (see "Displaying desire lines" on page 2429).
    These bars can be labeled, if required.

    24.5.1

    Displaying bars and adjusting basic settings


    For the desired network object type, define whether bars are to be displayed. Then, enter the
    basic settings for all bars of this network object type.
    1. From the Graphics menu, choose Edit graphic parameters.
    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Links> Bars.
    Note: For connectors, the settings are almost alike. The example below describes the
    settings for links.
    3. Select the Layer control tab.
    4. Make the desired changes.
    Element

    Description

    Draw layer links

    If this option has been selected, bars and labels can be displayed
    with links.

    Draw bars

    If this option has been selected, bars can be displayed with links.

    Draw bar labels

    If this option has been selected, labels can be displayed with


    links.

    5. Select the General settings tab.


    6. Make the desired changes.

    2368

    PTVGROUP

    24.5.1 Displaying bars and adjusting basic settings


    Element

    Description

    Use crossIf the option has been selected, the values are determined based on
    the two directions of the object.
    section
    values
    If the option has not been selected, the values are determined separately for each direction.
    Note
    If an undirected value to be displayed is averaged, it is automatically divided by two, so that half of the undirected value counts as the upper limit
    for the scaling. If, for example, the scaling range is 1-1000 and the bar
    width is 10 mm, an undirected value of 2000 is displayed with a volume
    of 1000 on each side and a bar width of 10 mm.
    Hide short
    bars

    If the option has been selected, bars are not displayed if their length is <
    one pixel.

    Connect
    bar polygons

    If the option has been selected, the angle of the adjacent bar at the end
    of the bar is considered for the display.

    Distance
    between
    bars

    Distance between the link bars in mm

    Visibility of Always draw labels


    bar labeling If this option is selected, the bar labels are always drawn, even if they are
    longer than the relevant line section.
    Only draw labels if there is enough space
    If this option is selected, the bar labels are drawn only if the label is not
    longer than the relevant bar.
    Draw depending on position
    If this option is selected, the bar labels are drawn depending on their
    position.
    If the position is exactly 0.5, the labels are drawn only if they are not longer than the relevant bar. If the position has a value greater or lesser
    than 0.5, they are always drawn.
    Note
    The value for the position is displayed in the link attribute Bar text relative position.
    Avoid over- If this option is selected, bar labels that would overlap are not displayed.
    lapping
    Note
    when draThis option is independent of the settings for Visibility of bar labeling.
    wing
    Text posiNext to bar
    tioning: ver- If the option has been selected, the label is displayed next to the bar.

    PTVGROUP

    2369

    24.5.1 Displaying bars and adjusting basic settings


    Element

    Description

    tical

    Within bar
    If the option has been selected, the label is displayed within the bar.
    Text distance
    Distance of labels in mm
    Note
    If the Next to bar option is selected, the distance to the bar is displayed.
    If the Within bar option is selected, the distance to the link is indicated.

    Text posiAlong longest section


    tioning: hori- For links with an edited shape, the labels are placed along the longest
    zontal
    section in the link course.
    In the middle
    The bar label is displayed independently of the available space.
    Note
    The option is only available for links.
    Tip
    If the Along longest section option has been selected, you should
    reduce the text size in case the text is longer than the length of the section in the network display.
    7. Select the Text format tab.
    8. Make the desired changes.

    2370

    PTVGROUP

    24.5.1 Displaying bars and adjusting basic settings


    Element

    Description

    Font and Font


    color
    You can specify a Font and a Style in a separate window by clicking in the
    field.
    Text size
    Text size in mm
    Note
    If the text size is 0.0mm, no bar label is issued.
    Color like bar
    If the option has been selected, the text is displayed in the same color as
    the bar.
    Tip
    We recommend this option, if several bars are displayed.
    If the option has not been selected, you can select a color in the drop-down
    list.
    Text
    entry

    Transparent
    If the option has been selected, the bar label is displayed without the white
    background, as text only.
    Draw frame
    If the option has been selected, the label is drawn with a frame. From the
    selection list, you can select the color.
    Alignment
    You can specify the alignment and the display of several bar labels via the
    drop-down list:
    Horizontal
    The labels are displayed in a row.
    Vertical
    The labels are displayed one below the other.
    Vertical + Sum
    All labels are displayed one below the other and underneath, the sum of
    the values is displayed.
    Sum only
    Only the values of the sum are displayed.
    Line spacing
    Line distance in percent of the current text size

    9. Select the Link selection tab.


    10. Make the desired changes.

    PTVGROUP

    2371

    24.5.1 Displaying bars and adjusting basic settings


    Element

    Description

    Draw the bars only


    on active links

    If the option has been selected, bars are not drawn for passive
    links.

    Draw the bars also


    on blocked links

    If the option has been selected, bars are also drawn for closed
    links.

    Regard all links

    If the option has been selected, bars are drawn for all links.

    Draw the bars only


    on selected links

    If the option has been selected, you can hide bars of links with
    specific attribute values. Use the button below the option to
    select the desired attribute.
    Click the Edit button to create the classification (see "Displaying classified objects based on attribute values" on page
    2411). Use the check box in the Draw column to specify if bars
    will be drawn for links of the particular class.
    Use layer order
    If the option has been selected, you can set up the order of drawing for the bars by class. The order is specified via the numbers in the Layer column. This column appears as soon as the
    option is checked. By default, the network objects of the
    various classes are drawn in the order as specified by the
    order of the classes in the list.
    Copy classification of links
    Via this button, you can transfer the link classification settings
    from page Links> Display to the link bars.

    11. Select the Line and path bars tab.


    12. Make the desired changes.
    Element

    Description

    Standard bar style


    Draw
    for line and path bars If this option has been selected, all line and path bars for which
    no differing type of display has been defined on the Bars
    >Display page are drawn in the standard style.
    Fill style
    You can specify the filling and boundary of the standard line
    and path bars in a separate window by clicking in the field (see
    "Editing the properties of a closed polygon" on page 2252).
    For the selected network object type, bars are basically displayed and the basic configuration
    has been set up. Under <Network object type> > Bars > Display, you now have to insert the
    individual bars and specify their display properties (see "Defining one or multiple bars" on
    page 2373 and "Setting the display properties of a bar" on page 2374).

    2372

    PTVGROUP

    24.5.2 Defining one or multiple bars

    24.5.2

    Defining one or multiple bars


    Bars can be defined for various network object types.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. On the page <Network object type>> Bars, adjust the settings.
    3. In the navigator, select the <Network object type>> Bars> Display entry.

    In the upper section, a preview of the currently configured bars appears. The table below
    stores the description of the bars. Each column refers to one bar. The bars are displayed
    according to the column order: The first column describes the innermost bar, the last
    column describes the outermost bar. In the preview, the currently marked bar is indicated
    by two arrows; the respective label is highlighted in color. The arrows are filled for currently
    displayed bars. Otherwise they are empty.
    4. Click the column header to mark the desired column.
    5. Use the toolbar to adjust the settings accordingly.
    Icon

    Description
    Adds another column to the right of the currently marked column. Simultaneously, another bar is added.
    Copies the marked columns

    PTVGROUP

    2373

    24.5.3 Setting the display properties of a bar


    Icon

    Description
    Copies the marked columns and changes the bar colors
    Opens a window in which you can edit the display properties of the bar selected (see "Setting the display properties of a bar" on page 2374)
    Removes the marked columns. Simultaneously, the bars are removed
    Moves the columns currently selected by one position to the left
    The particular bars are shifted accordingly.
    Moves the currently marked columns by one position to the right
    The particular bars are shifted accordingly.
    Opens the Attribute selection window in which you can specify the attributes
    you want to show as table rows (see "The window used for the selection of
    multiple attributes" on page 968).
    Tip
    Right-click on a table row name calls the context menu: You can add or
    delete individual rows.
    Resets the attributes which are currently displayed as table row names to the
    standard selection.

    Tips: These functions can also be executed via the context menu. Here you can also
    adjust the column width settings.
    6. Confirm with OK.
    In the network window, the bars will be displayed according to the current settings.
    Notes: You have defined the number of bars displayed for the network object type. The
    contents of the table columns indicate bar display properties. The bar type selected defines the properties you can edit directly in the table. All bar display properties can be
    accessed via the icon

    24.5.3

    (see "Setting the display properties of a bar" on page 2374).

    Setting the display properties of a bar


    You can configure various bar types:
    Standard bar: The bar represents an attribute value. Standard bars are provided for links,
    connectors, turn volumes and desire lines.
    Difference bar: The bar represents the difference value between two attributes. Difference
    bars are provided for links, connectors, turn volumes and desire lines.
    Line bar: The bar represents the attribute value of the line route traversing the link. For
    several line routes per link, the values can be displayed by several bars or aggregated
    alternatively.

    2374

    PTVGROUP

    24.5.3.1 Setting the display properties of a standard bar


    PrT path bar: The bar represents the attribute value of the path item traversing the link. For
    several paths per link, the values can be displayed by several bars or aggregated alternatively.
    24.5.3.1

    Setting the display properties of a standard bar


    For links and connectors, you can display the values of an attribute of the particular network
    object by a bar. For desire lines, the values of an OD pair attribute are displayed. With turn
    volumes, the values of a (main) turn attribute are displayed.
    1. Make sure that the appropriate page has been opened in the Edit graphic parameters window:
    Links: Links> Bars> Display
    Connectors: Connectors> Bars> Display
    Desire lines for zones: Desire lines zones> Display
    Desire lines for main zones: Desire lines main zones> Display
    2. If required, add another column for a bar (see "Defining one or multiple bars" on page
    2373).
    3. Click in the header of the column for the desired bar.
    Tip: You can directly edit some of the display properties in the column. The Edit function provides access to the display properties.
    4. Click the

    Edit icon.

    The Edit bar <no> window opens.


    5. Select the Draw this bar option.
    6. In the Bar type section, select the option Standard bars.
    7. Select the Scaling tab.
    8. Make the desired changes.
    Element Description
    Scaling In a separate window, you can select the attribute which is to be displayed
    attribute as a bar when clicking this button.
    Scaling Maximum bar width
    Maximum bar width in mm
    Note
    With maximum width = 0, no bar will be displayed. The label, however, can
    be displayed.
    Use minimum width
    If the option has been selected, very thin bars, which cannot be displayed

    PTVGROUP

    2375

    24.5.3.1 Setting the display properties of a standard bar


    Element Description
    adequately with their actual values, are drawn in the minimum width. A quick
    info displays the attribute value range in which the minimum width is used.
    Manual scaling
    If this option has been checked, you can define the value range by bar: Enter
    the absolute values for the bar display. The lower scaling limit corresponds
    to the minimum bar width, the upper scaling limit to the maximum bar width.
    The bar width is identical for a bar representing a negative attribute value
    and a bar representing the respective positive attribute value. The scaling
    range has to be adjusted accordingly: For attribute values in the range between -200 and +100, enter 0 - 200 as scaling range.
    If the attribute value of an object is less than the lower scaling limit, the bar
    will not be displayed. If the attribute value of an object is greater than the
    upper scaling limit, the bar will be displayed in the maximum width.
    Notes
    For the optimum display of the bar, you should adjust the input limits to the
    displayed minimum and maximum values.
    For a constant bar width, enter the same value in both entry fields.
    Negative and positive values can be distinguished by the fill colors (Fill style
    tab).
    Automatic scaling
    If the option has been selected, the value range goes from 0 to the calculated Network maximum that has been determined from the attribute
    values and which is multiplied by a user-defined factor between 0.0 and 1.0.
    Calculate network minimum and network maximum
    If the option has been selected, the minimum and the maximum attribute
    values are calculated automatically.
    Note
    You can disable the option to avoid long computing times.
    9. Select the Label tab.
    10. Make the desired changes.

    2376

    PTVGROUP

    24.5.3.1 Setting the display properties of a standard bar


    Element

    Description

    General
    label settings

    Hide if (absolute) value <=


    If this option is checked, no label will be displayed if the absolute attribute
    value is less than the entered value.
    Priority in case of space limitation
    Enter a number which indicates the priority of the bar label. If several
    labels shall be displayed next to each other along a polyline object which
    is too short for the display of all labels, then the label with the lowest priority will be faded out first.
    Show title
    If this option is checked, another text portion will be added to the bar label:
    Name of the scaling attribute: Next to the value, the network object
    name will be displayed.
    Text: Next to the value, the text entered in the field will be displayed.

    Label type Value of scaling attribute


    If the option has been selected, the value of the attribute selected for the
    definition of the bar scaling is displayed (Scaling tab).
    Class name (only for classified fill style)
    If the option has been selected, the name of the class selected for the definition of the fill style will be displayed (Fill style tab).
    Value of the filling attribute (only for classified fill style)
    If the option has been selected, the value of the attribute selected for the
    definition of the fill style is displayed (Scaling tab).
    View format for
    attribute
    value

    Show attribute value


    If the option has been selected, the attribute value is displayed.
    Note
    Further settings in this section depend on the format of the value that has
    been selected for labeling. All settings only refer to the bar labels, they do
    not refer to the actual values.
    Multiply by
    Factor by which the attribute values are multiplied for the display
    Round to the multiple of
    Rounding value for the displayed attribute values
    Notes
    If you entered 100, for example, the values are rounded to the nearest hundred.
    Just attribute values are rounded. Class limits and class values are not
    rounded.
    Number of decimal places

    PTVGROUP

    2377

    24.5.3.1 Setting the display properties of a standard bar


    Element

    Description
    Number of decimal places of displayed attribute values
    Format
    Via this selection list you define the format for the display of values.
    Show unit
    If this option has been checked, the unit is added to the attribute value.

    11. Select the Fill style tab.


    12. Make the desired changes.
    Element

    Description

    Uniform
    display

    If this option has been checked, all bars are drawn with identical color and
    identical boundary. In the section on the right side, specify how the bars
    are drawn.
    Fill color
    Use the drop-down list to select a fill color.
    Fill style
    Select the desired fill style pattern.
    Line distance
    Specify the desired line distance of the fill style pattern in mm.
    No boundary
    If the option has been selected, no boundary is displayed.
    Color like fill color
    If this option has been selected, the color of the filling is also used for the
    boundary.
    Margin color
    If this option has been selected, select the desired boundary color from the
    color ramp.
    Line style
    From the drop-down list, select the desired line style for the boundary.
    Preview
    Preview showing the edited filling and boundary

    Classified If the option has been selected, you can classify the colors and boundisplay
    daries of bars based on an attribute (see "Displaying classified objects
    based on attribute values" on page 2411). With the button you select the
    attribute you need. Via the Like scaling attribute entry, you can automatically use the attribute that has been selected for scaling.

    Note: Via the buttons Previous bar and Next bar you can immediately switch to the
    display properties of other bars.
    2378

    PTVGROUP

    24.5.3.2 Configuring a difference bar display


    13. Confirm with OK.
    In the network window, the bar will be displayed according to the settings.
    24.5.3.2

    Configuring a difference bar display


    For links and connectors, you can display the difference between two attributes of a network
    object by a single bar. With flow bundle volumes, you can display the difference between two
    attributes of an OD pair accordingly by one bar. With turn volumes, you can display the difference between two turn attributes by one bar.
    The width of the bar indicates the difference of the two attribute values. Via the classification
    settings, you can classify the differences. Additionally, the classes can be distinguished by
    color.
    Example of a uniform display of difference values

    Example of a classified display of difference values

    1. Make sure that the appropriate page has been opened in the Edit graphic parameters window:
    Links: Links> Bars> Display
    Connectors: Connectors> Bars> Display
    Desire lines for zones: Desire lines zones> Display
    Desire lines for main zones: Desire lines main zones> Display

    PTVGROUP

    2379

    24.5.3.3 Configuring the display of a PuT line bar


    2. If required, add another column for a bar (see "Defining one or multiple bars" on page
    2373).
    3. Click in the header of the column for the desired bar.
    Tip: You can directly edit some of the display properties in the column. The Edit function provides access to all display properties.
    4. Click the

    Edit icon.

    The Edit bar <no> window opens.


    5. Select the Draw this bar option.
    6. In the Bar type section, select the option Difference bar.
    7. Select the Scaling tab.
    8. In the Scaling attribute section, make the desired settings.
    Element

    Description

    Plus sign

    Via this button, you select the first attribute of the network object type.

    Minus sign

    Via this button, you select the second attribute of the network object
    type.

    Note: For the bar width, the order of these two attributes is not regarded, as the bars
    will represent absolute values. Negative and positive values can be distinguished by
    color according to the classification settings in the Fill style tab.
    9. Adjust further settings (see "Setting the display properties of a standard bar" on page 2375).
    10. Click the Preview button.
    In the network window, the difference values are displayed as bars according to your settings.
    24.5.3.3

    Configuring the display of a PuT line bar


    You can display an attribute value of the respective line route along links via a bar. You can
    visualize the volume of the PuT line, for example.
    The attribute values of several line routes by link you can either display as several separate
    bars or aggregate for the following network objects:
    Transport systems
    Main lines
    Lines
    Operator
    Note: You can even display the lines themselves in the network window (see "Displaying
    route courses in the network window" on page 2387).

    2380

    PTVGROUP

    24.5.3.3 Configuring the display of a PuT line bar


    1. Make sure that in the Edit graphic parameters window the Links> Bars> Display tab has
    been opened.
    2. If required, add another column for a bar .(see "Defining one or multiple bars" on page
    2373).
    3. Click in the header of the column for the desired bar.
    Tip: You can directly edit some of the display properties in the column. The Edit function provides access to all display properties.
    4. Click the

    Edit icon.

    The Edit bar <no> window opens.


    5. Select the Draw this bar option.
    6. In the Bar type section, select the option Line bars.
    7. In the Scaling tab, make the desired changes (see "Setting the display properties of a standard bar" on page 2375).
    8. In the Label tab, make the desired changes (see "Setting the display properties of a standard bar" on page 2375).
    Note: In the General label settings section, the option Network object name is provided as title. If this option is selected, the name of the network object will be displayed that has been selected as aggregation level in the Fill style tab.
    The Label type section is grayed out.
    9. Select the Fill style tab.
    10. Make the desired changes.
    Element

    Description

    Regard only
    active line
    route for drawing

    If this option is selected, bars will be displayed only for active line routes in the network window.

    Show only
    active lines/line routes in
    the list

    If this option is selected, only for lines will be displayed in the list.
    Note
    This option is only provided for the aggregation levels Lines and Line
    routes.

    Aggregation
    level

    Select the level on which the attribute values of the line routes are to
    be aggregated. According to the selected option, the network objects
    will be listed to the right.
    Transport systems

    PTVGROUP

    2381

    24.5.3.3 Configuring the display of a PuT line bar


    Element

    Description
    Main lines
    Lines
    Line routes
    Operators

    Aggregate
    function

    In the selection list, select how the attribute values of the line routes
    are to be aggregated.
    Note
    This drop-down list is not available if the Line routes option has been
    selected, as no aggregation takes place in this case.
    Sum
    Sum of attribute values
    Minimum
    Smallest attribute value
    Maximum
    Greatest attribute value
    Mean value
    Average of the attribute values
    Weighted mean
    Mean of the attribute values weighted by an attribute. Select the attribute for the weighting via the <Attribute> button.

    Weighting attri- Attribute for the weighted mean


    bute
    Note
    The button is only available if you have selected the Weighted mean
    option.
    The button is labeled with the currently selected attribute.
    Separate display per
    <Aggregation
    level>

    If this option has been checked, all bars are drawn with identical
    color and identical boundary. In the section on the right side, specify
    how you want the bars drawn (see "Uniform display of line bars" on
    page 2382).

    Classified display

    If the option has been selected, you can classify the colors and boundaries of bars by an attribute. With the button you select the attribute
    you need. In the section on the right side, specify how you want the
    bars drawn (see "Displaying classified objects based on attribute
    values" on page 2411).

    Uniform display of line bars


    Line bars can be displayed in a uniform way per selected object, for example, per line or per
    transport system. The list contains all objects and their display properties. Alternatively, you
    can specify a classified display for line bars based on an attribute (see "Classified display of
    line bars" on page 2385).

    2382

    PTVGROUP

    24.5.3.3 Configuring the display of a PuT line bar


    1. Make sure that in the Edit bar <No.>window Fill style tab the Separate display per <Network object of selected aggregation level> option has been checked.
    2. In the list on the right side, adjust the display settings accordingly for each object.
    Note: In the Display column, the bars first are displayed in the standard style set for
    line and path bars. It can be adapted on the Links > Bars page > Line and path bars
    tab.
    Element

    Description

    Draw

    If the option has been selected, the bar will be drawn for the object.

    Name

    Name of the object

    Display

    Bar display preview


    You can specify the fill style and boundary of the bar in a separate window. To do so, click in the field (see "Editing the properties of a closed
    polygon" on page 2252).

    Note: Via the Edit button, you can specify settings for all objects at once.
    3. Click the Edit button.
    The Edit the <Aggregation level> view window opens.
    4. Make the desired changes.

    PTVGROUP

    2383

    24.5.3.3 Configuring the display of a PuT line bar


    Element

    Description

    Visibility

    Here you can specify the options that you want to set in the Draw column of
    the list of objects.
    Retain
    If the option has been selected, the settings for the individual objects are
    retained when editing settings in the Filling section.
    All
    If the option has been selected, you can use the Draw option to select or
    deselect all options in the Draw column.
    Check the active ones exclusively
    If the option has been selected, the options in the Draw column are
    checked for all active objects and unchecked for all passive objects.
    Note
    The option is only available for network objects which can be passive.
    The setting of the passive objects is not affected by it.
    Apply from classification
    If this option has been selected, the same selection is adopted for the Draw
    column as in the classified display.
    Like transport system/operator/main line/line
    If the option has been selected, the setting for the corresponding transport
    system, main line, line or operator is adopted for the Draw column.
    Note
    The selected aggregation level determines which options are displayed.

    Filling
    Here you can specify the colors that you want to set in the Display column
    and boun- of the list of objects.
    dary
    Retain
    If the option has been selected, the settings for the individual objects are
    retained when editing settings in the Draw section.
    Constant
    If the option has been selected, the selected color is applied to all objects
    of the aggregation level. Click in the field to select a color and a fill style
    (see "Editing the properties of a closed polygon" on page 2252).
    Qualitative color palette
    If the option has been selected, each object has a different color.
    Apply from classification
    If the option has been selected, the objects are displayed according to the
    settings of the classified display.
    Like transport system/operator/main line/line
    If the option has been selected, the setting for the corresponding transport

    2384

    PTVGROUP

    24.5.3.3 Configuring the display of a PuT line bar


    Element

    Description
    system, main line, line or operator is adopted for the Draw column.
    Note
    The selected aggregation level determines which options are displayed.

    5. If required, use the icons to edit the order of the objects.


    Element

    Description
    Use this icon to move the selected row up.
    Use this icon to move the selected row down.

    Notes: According to the specified order, the bars are drawn along the link from the
    inside out. The top entry is the one closest to the link.
    Use the Reset order button to go back to the original order.
    6. Confirm with OK.
    In the network window, the line bars are displayed according to the settings.
    Classified display of line bars
    The fill style of the line bars can be displayed in a classified way, per selected object, per line
    or per transport system, for example.
    1. Make sure that Edit bar <No.>> Fill style tab is open and that the option Classified display
    has been checked.
    2. Use the button labeled with the attribute name to select the attribute of the selected aggregation level by which you want to classify the display.
    3. In the list on the right side, adjust the display settings accordingly for each object.
    Element

    Description

    Draw

    If the option has been selected, the bar will be drawn for the class.

    Class

    Display of class limits

    Name

    Class name
    Note
    By default the class limits are issued. You can edit the values.

    Preview

    Bar display preview


    You can specify the fill style and boundary of the bar in a separate window. To do so, click in the field (see "Editing the properties of a closed
    polygon" on page 2252).

    PTVGROUP

    2385

    24.5.3.4 Configuring the display of a PrT path bar


    Note: Via the Edit button, you can specify settings for all objects at once. Via the
    Create button you can insert classes individually at the desired position. Via the
    Delete button you can delete the marked class.
    4. Click the Edit button.
    The Set up and edit classification window opens.
    5. Make the desired settings (see "Setting up classes and class limits for classification" on
    page 2412).
    6. Confirm with OK.
    The modifications are adopted and displayed in the table.
    Note: You can transfer the settings of the classification to the individual display by
    clicking the Transfer the classification to the individual display button.
    24.5.3.4

    Configuring the display of a PrT path bar


    Via a link bar, you can view an attribute value of the PrT path item traversing the link.
    1. Make sure that in the Edit graphic parameters window the Links> Bars> Display tab has
    been opened.
    2. If required, add another column for a bar (see "Defining one or multiple bars" on page
    2373).
    3. Click in the header of the column for the desired bar.
    Tip: You can directly edit some of the display properties in the column. The Edit function provides access to all display properties.
    4. Click the

    Edit icon.

    The Edit bar <no> window opens.


    5. Select the Draw this bar option.
    6. In the Bar type section, select the option PrT path bar.
    7. In the Scaling tab, make the desired changes (see "Setting the display properties of a standard bar" on page 2375).
    8. In the Label tab, make the desired changes (see "Configuring the display of a PuT line bar"
    on page 2380).
    9. In the Fill style tab, make the desired changes (see "Configuring the display of a PuT line
    bar" on page 2380).

    2386

    PTVGROUP

    24.6 Displaying route courses in the network window


    Notes: The following options differ from the settings for line bars:
    Regard only active paths: If this option has been selected, passive paths and path
    sets will be ignored.
    Show only active path sets in the list/Show only active paths in the list: If this
    option has been selected, only active paths and path sets will be displayed in the list
    on the right.
    Aggregation level: Here you can specify whether the path attribute values are displayed by path or as aggregate value by path sets. According to the selected option,
    the network objects will be listed to the right.
    10. Confirm with OK.
    In the network window, the PrT path bars are displayed according to the settings.

    24.6

    Displaying route courses in the network window


    You can configure the display of line routes or PuT lines in the network window. You can visualize each line by a different color, for example. For links which are traversed by multiple lines,
    you can define a specific color.
    Tip: You can additionally show line bars along lines (see "Configuring the display of a
    PuT line bar" on page 2380).
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Route course entry.
    3. Make the desired changes.
    Element

    Description

    Draw layer If the option has been selected, line routes can be displayed.
    line route
    course
    Drop-down
    list

    PuT line route courses can be displayed on four levels. Here you can
    select the desired level of detail.
    Transport systems
    Main lines
    Lines
    Line routes

    Draw links
    If this option has been checked, links which are used by several line
    being used routes, lines, main lines or transport systems are drawn.
    in common
    If the option has not been selected, PuT lines are not displayed on shared links.

    PTVGROUP

    2387

    24.6 Displaying route courses in the network window


    Element

    Description

    Line style
    of links
    used by
    multiple
    PuT lines

    Here, you can set the display of links which are used in common. You
    can specify the color and line style in a separate window. To do so, click
    in the Color field (see "Setting the line style properties" on page 2363).

    Draw

    If the option has been selected, the respective route course is displayed.
    Note
    Via the Edit button, you can specify settings for all objects at once.

    Name

    List of objects that exist in this level of detail

    Display

    You can select an individual color for each line in a separate window. To
    do so, click in the Color field (see "Setting the line style properties" on
    page 2363).
    Note
    Via the Edit button, you can specify settings for all objects at once.

    4. If required, click the Edit button.


    Note: Via this button, you can specify settings for all objects at once.
    The Edit the <network object type> view window opens.
    Element

    Description

    Visibility

    Here you can specify the options that you want to set in the Draw column
    of the list of objects.
    Retain
    If the option has been selected, the settings for the individual objects are
    retained when editing settings in the Line style properties section.
    All
    If the option has been selected, you can use the Draw option to select or
    deselect all options in the Draw column.
    Check the active ones exclusively
    If the option has been selected, the options in the Draw column are
    checked for all active objects and unchecked for all passive objects.
    Note
    The option is only available for network objects which can be passive.
    The setting of the passive objects is not affected by it.

    Line style Here you can specify the colors that you want to set in the Display column
    proof the list of objects.
    perties

    2388

    PTVGROUP

    24.7 Displaying stop catchment areas in the network window


    Element

    Description
    Retain
    If the option has been selected, the settings for the individual objects are
    retained when editing settings in the Draw section.
    Constant
    If the option has been selected, the selected color is applied to all objects
    of the chosen level. To select a color, click in the Color field (see "Editing
    the properties of a closed polygon" on page 2252).
    Qualitative color palette
    If the option has been selected, each object has a different color.

    5. Confirm with OK.


    The route courses are displayed according to your chosen settings.

    24.7

    Displaying stop catchment areas in the network window


    Using stop catchment areas, you can illustrate the PuT access quality in the network (see Fundamentals: Chpt. 12.10 , page 765).

    24.7.1

    Activating the display of stop catchment areas


    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Stop catchment areas entry.
    3. Select the Draw stop catchment areas layer option.
    Tip: You can avoid an overlap of objects if you select the Avoid overlapping when
    drawing option.
    4. Select the Stop catchment areas> Display page.
    5. Make the desired settings (see "Editing the graphic parameters of stop catchment areas" on
    page 2389).
    6. Confirm with OK.
    The stop catchment areas are displayed.

    24.7.2

    Editing the graphic parameters of stop catchment areas


    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. Select the Stop catchment areas page.
    3. Make sure that the Draw stop catchment areas layeroption is selected.

    PTVGROUP

    2389

    24.7.2 Editing the graphic parameters of stop catchment areas


    4. In the navigator, select the Stop catchment areas> Display entry.

    5. Make the desired changes.


    Element

    Description

    Draw only for


    active stops

    If the option has been selected, stop catchment areas are only
    displayed at active stops.
    If the option has not been selected, stop catchment areas are
    also displayed at passive stops.

    Classification

    Uniform display
    If the option has been selected, all stop catchment areas are
    drawn consistently.
    Classified display
    If the option has been selected, the stop catchment areas can be
    classified and displayed by an attribute.

    6. Make the desired changes in the Display section.


    Note: If you have selected the Classified display, specify the following settings individually for each class. Beforehand, click in the desired row of the list of classes.

    2390

    PTVGROUP

    24.7.2 Editing the graphic parameters of stop catchment areas


    Element

    Description

    Draw

    If the option has been selected, stop catchment areas are displayed.

    Radius

    The radius determines the extension of the circular area.


    Constant
    If the option has been selected, you can enter a constant radius for all
    displayed stop catchment areas.
    Determine from attribute
    If the option has been selected, via the button, you can select a numerical attribute and enter a factor in the input field. The radii are displayed in proportion to the product of the factor and the attribute
    values.

    Filling/Boundary

    The stop catchment area is displayed in the colors selected for the filling.
    Simple filling
    If the option has been selected, the stop catchment area is displayed
    consistently in the color specified under Color.
    Smooth color transition
    If the option has been selected, the circles around the nodes are displayed with a color gradient.
    Note
    The following options are only available, if the Smooth color transition option has been selected:
    Center color

    Use the color field to specify the color at the center of the circle.
    Margin color

    Use the color field to specify the color at the margin of the circle.
    Draw boundary

    If the option has been selected, the circles around the nodes are displayed with a boundary.
    Boundary

    You can specify the boundary style in a separate window. To do so,


    click in the field (see "Setting the line style properties" on page 2363).

    Note: If you click the Preview button, your changes will immediately be displayed
    though the Edit graphic parameters window is still open.
    7. Confirm with OK.
    The stop catchment areas are displayed according to your chosen settings.

    PTVGROUP

    2391

    24.8 Displaying transfer relations between stop areas

    24.8

    Displaying transfer relations between stop areas


    In the network, you can display volume bars for transfer relations between stop areas (see Fundamentals: Chpt. 12.9 , page 764), e.g. walk times or the total number of passengers transferring per demand segment.

    24.8.1

    Displaying transfer relations


    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Transfer relations entry.
    3. Make the desired changes in the Layer control, General settings, Text format and OD
    pair selection tabs.
    Note: The graphic parameter settings for transfer flows are identical to those for desire
    lines (see "Displaying desire line bars and adjusting basic settings" on page 2429).
    4. In the navigator, select the Transfer relations> Display entry.
    5. Make the desired changes.
    Note: The settings for transfer relations bars are identical to the settings for desire
    lines bars (see "Displaying bars for desire lines" on page 2433).
    6. Confirm with OK.
    The transfer relations are displayed.
    Tip: Under Lists> Passenger transfers> Transfers and stop area walk times in stop
    (see "Opening a list" on page 2299), you can view the transfer walk times for each stop
    as well as the passengers transferring between stop areas for each transport system.

    24.9

    Displaying connections and transfer flows at stops


    The transfers display of regular services allows you to display departure minutes, transfer
    flows, and connections between vehicle journeys at a stop in a clock image. It further enables
    you to analyze this data using different settings. The arriving and departing vehicle journeys at
    a stop are displayed around the outer edge of a circle. You can specify various settings for the
    display.

    24.9.1

    Activating the transfers display of regular services


    1. Before analyzing vehicle journeys or time profiles in the transfers display of regular services, make sure you have specified the desired settings for saving PuT assignment results
    (see "Settings for saving PuT assignment results" on page 1996) and have calculated a
    timetable-based or headway-based assignment (see "Parameters of headway-based assignment" on page 2010 and "Parameters of timetable-based assignment" on page 2021).
    2. In the Edit menu, select the Transfers display of regular services entry.

    2392

    PTVGROUP

    24.9.1 Activating the transfers display of regular services


    The Transfers display of regular services window opens.
    3. Make the desired changes.
    Element

    Description

    Stop

    Click this button to select the stop you want to analyze (see "Finding
    a stop" on page 1242).

    Vehicle journeys

    All
    If this option has been selected, all vehicle journeys of the analysis
    time interval are taken into account at the stop.
    Only active ones
    If the option is selected, only active vehicle journeys at the stop are
    taken into account (see "Setting individual network objects active or
    passive" on page 1035).
    Note
    The display will be refreshed automatically if the number of active
    vehicle journeys are changed via filter or selection.
    From timetable editor
    If this option is selected, all vehicle journeys active in the timetable
    editor are taken into account (see "Showing only active vehicle journeys" on page 1533).
    Note
    This option is displayed only if the timetable editor is open. The transfers display of regular services refreshes automatically, if you set active/passive lines in the timetable editor that serve the selected stop.
    From schematic line diagram
    If this option has been selected, all vehicle journeys are taken into
    account that are active in the schematic line diagram.
    Note
    This option is displayed only if the schematic line diagram is open.

    From

    Start time of the period examined in format hh:mm:ss


    Note
    If you have set a calendar, it is also displayed (see "Selecting a calendar " on page 1511). You can use the calendar to set the start time of
    the period of examination.

    To

    End time of the period examined in format hh:mm:ss


    Note
    If you have set a calendar, it is also displayed (see "Selecting a calendar " on page 1511). You can use the calendar to set the end time of
    the period of examination.

    PTVGROUP

    2393

    24.9.2 Setting the bar display for transfer flows


    Element

    Description

    Basic cycle

    Here you specify how the time interval of the specified period of
    examination will be distributed over the circle. You can enter the
    value with or without a time unit (h, min or s). If you do not enter a
    unit, your entry is interpreted as minutes.

    Tolerance

    Here you specify the conditions for the aggregation of vehicle journeys to service groups. Only vehicle journeys with the same direction
    (departure or arrival), line and direction code can be aggregated to
    one service group. You can enter the value with or without a time unit
    (h, min or s). If you do not enter a unit, your entry is interpreted as
    minutes.

    Large scale

    If this option has been selected, a scale will be displayed on the


    circle. The distance between the markings and their labels is based
    on the value entered in the input field. You can enter the value with
    or without a time unit (h, min or s). If you do not enter a unit, your
    entry is interpreted as minutes.

    Small scale

    If this option has been selected, an intermediate scale is displayed


    on the circle. The distance between the markings is based on the
    value the value entered in the input field.
    You can enter the value with or without a time unit (h, min or s). If you
    do not enter a unit, your entry is interpreted as minutes.

    24.9.2

    Setting the bar display for transfer flows


    Notes: An arrival group describes a set of vehicle journeys of a line that arrive at the
    same time at the selected stop. The defined tolerance value (see "Activating the transfers
    display of regular services" on page 2392) indicates the allowed deviation from the same
    arrival time under which vehicle journeys are displayed as one arrival group.
    A departure group describes a set of vehicle journeys of a line that depart at the same
    time at the selected stop. The defined tolerance value (see "Activating the transfers display of regular services" on page 2392) indicates the allowed deviation from the exact
    same departure time under which vehicle journeys are displayed as one arrival group.
    A service group can be either an arrival group or a departure group.
    The setting of the graphic parameters is identical for both groups, it is, thus, described for
    the arrival groups only. Proceed in the same manner when specifying the settings for the
    departure groups.
    You can select which transfer flows of service groups shall be displayed in the transfers display of regular services.
    1. Make sure the bars for the transfer flows are drawn (see "Setting the graphic parameters for
    transfer flows" on page 2397).
    2. Click the desired icon for the display of the transfer flows.

    2394

    PTVGROUP

    24.9.3 Synchronizing the transfers display of regular services with other windows
    Icon

    Name

    Description

    Draw all bars

    If this option has been selected, all transfer flows between all service groups are displayed.

    Draw the bars of


    all marked service groups

    If the option has been selected, all transfer flows are


    displayed that belong to the marked service groups.
    But also transfer flows of other than the marked service groups are displayed.

    Only draw bars


    between marked
    service groups

    If the option has been selected, only those transfer


    flows that run between the marked service groups are
    displayed.

    3. Mark the desired service groups.


    Tips: Click to the left of the arrow, to select the arrival group. Click to the right of the
    arrow, to select the departure group.
    Alternatively, you can select or deselect all arrival and departure groups. To do so,
    right-click into the transfers display of regular services and select one of the following
    entries from the context menu:
    Unmark all arrival groups
    Mark all arrival groups
    Mark all departure groups
    Unmark all departure groups
    The transfer flows of the desired service groups are displayed.

    24.9.3

    Synchronizing the transfers display of regular services with other windows


    You can synchronize the transfers display of regular services with the network editor. If the windows are synchronized, you can, for example, mark a stop in the network window and it is automatically displayed in the Transfers display of regular services window as well. Via the
    Network editor window, you can also synchronize with lists.
    1. Make sure that the Transfers display of regular services window is open (see "Activating
    the transfers display of regular services" on page 2392).
    2. In the Transfers display of regular services window, open the Synchronization with network editor entry.
    3. Select the desired entry.
    Element

    Description

    No synchronization

    The transfers display of regular services is not synchronized with


    the network window.

    Mark object(s)

    The stop selected in the transfers display of regular services is


    marked in the network window and vice versa.

    PTVGROUP

    2395

    24.9.4 Setting the graphic parameters for the Transfers display of regular services
    Element

    Description

    Mark and shift


    view

    The stop selected in the transfers display of regular services is


    marked in the network window and vice versa. Additionally, if
    required, the network section of the network window is shifted in
    such a way that the marked stop is fully visible.
    Note
    This does not affect the scale of the network editor.

    Mark and autozoom

    The stop selected in the transfers display of regular services is


    marked in the network window and vice versa. Additionally, in the
    network an auto zoom is carried out for the marked stop.

    The settings are applied.

    24.9.4

    Setting the graphic parameters for the Transfers display of regular services
    You can adjust the graphic parameters for the transfers display of regular services. The
    graphic parameters are valid for all transfers displays of regular services of the version and
    are saved in the version file.
    1. Make sure the Transfers display of regular services window is open (see "Activating the
    transfers display of regular services" on page 2392).
    2. From Transfers display of regular services menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    3. Specify the desired settings on the pages Arrival groups, Departure groups, Transfer
    flows, Transfer and walk times, Font and Print frame.

    24.9.4.1

    Setting graphic parameters for arrival and departure groups in the transfers display of
    regular services
    1. On the toolbar of the Transfers display of regular services window, click the
    graphic parameters icon.

    Edit

    Tip: Alternatively, in the Transfers display of regular services menu, select the Edit
    graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Arrival groups entry.
    3. On the pages of this window define the settings you need.

    2396

    PTVGROUP

    24.9.4.2 Setting the graphic parameters for transfer flows

    24.9.4.2

    Element

    Description

    Display

    You can specify graphic parameters for active, passive, and marked
    arrival groups on the three tabs Active, Passive, and Marked. The
    uniform and classified display are only available for active arrival
    groups (see "Displaying line objects in the network window" on page
    2354).

    Description

    Draw label
    If the option is selected, the objects are labeled (see "Labeling line
    objects" on page 2359).
    Primary label
    Use the button to select an arrival group attribute in a separate window to add an extra label to the arrival group arrow first.
    Note
    You can for example select the line and its end stop as label.
    Secondary label
    Use the button to select an arrival group attribute in a separate window to add an extra label to the arrival group arrow.

    Bars

    In the Layer control, General settings, Text format and Service


    group selection tabs, specify how and for which arrival groups bars
    will be drawn and which attributes will be displayed as bars. The bars
    are drawn on the outside of the circle at the display of the respective
    arrival group. The bar of the respective group is located to the right of
    the arrow in the direction of the arrow head.
    Note
    The setting of the display is the same as for the display of line objects
    (see "Defining one or multiple bars" on page 2373 and "Setting the display properties of a bar" on page 2374).

    Tooltips

    Use the 1st row to 4rth row buttons to select the attributes whose
    values shall be displayed in a quick info, if you point at the arrival
    groups in the transfers display of regular services.

    Setting the graphic parameters for transfer flows


    The transfer flow equals the amount of passengers transferring or passing through, between
    an arrival and a departure group.
    1. From Transfers display of regular services menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Transfer flows entry.
    3. Make the desired changes.

    PTVGROUP

    2397

    24.9.4.3 Setting graphic parameters for the print frame


    Element

    Description

    Bars

    In the tabs Layer control, General settings, Text format and


    Transfer flow selection, specify the transfer flows at which you
    want to draw bars, how to draw the bars, and which attributes will
    be displayed at the bars. The bars will be drawn within the circle
    at the service groups.
    Note
    The setting of the display is the same as for the display of line
    objects (see "Defining one or multiple bars" on page 2373 and
    "Setting the display properties of a bar" on page 2374).

    Transfer and walk Draw transfer and walk times


    times
    If this option is selected, the transfer and walk times are displayed.
    Transfer times and Minimum walk times
    Click the button to select the desired colors for the display of the
    transfer and walk times.
    Note
    Transfer times are displayed with a circle segment which
    connects the marked arrival group and the marked departure
    group. Inside of the circle segment, the time between the arrival
    and the next possible departure is displayed.
    Walk times are displayed in a different color as circle segment
    within the circle segment of the transfer time. The time is displayed in the circle segment (see "Properties and options of
    stops" on page 1238).
    24.9.4.3

    Setting graphic parameters for the print frame


    If you want to print the transfers display of regular services, you can specify the following settings for the print frame.
    1. From Transfers display of regular services menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Print frame entry.
    3. Make the desired settings (see "Setting the print frame" on page 2504).

    24.9.5

    Reading and saving graphic parameters for the Transfers display of regular services
    Note: The graphic parameters of the transfers display of regular services are saved to a
    file of the type *.gpta file.

    2398

    PTVGROUP

    24.9.5.1 Saving the graphic parameters of the transfers display of regular services
    24.9.5.1

    Saving the graphic parameters of the transfers display of regular services


    1. Edit the graphic parameters as desired (see "Setting the graphic parameters for the Transfers display of regular services" on page 2396).
    2. In the Transfers display of regular services menu, select the Save graphic parameters
    entry.
    The Save: Transfers display of regular services - graphic parameters window opens.
    3. Enter the desired file name and path, if required.
    4. Click the Save button.
    The graphic parameters of the transfers display of regular services are saved.

    24.9.5.2

    Opening graphic parameters of the transfers display of regular services


    1. From the Transfers display of regular services menu, choose Open graphic parameters.
    The Open: Transfers display of regular services - graphic parameters window opens.
    2. Open the desired file.
    3. Confirm with Open.
    The graphic parameters of the transfers display of regular services are opened.

    24.9.6

    Printing or exporting the transfers display of regular services


    You can print the transfers display of regular services or export it as graphics file.

    24.9.6.1

    Printing the transfers display of regular services


    1. Specify the settings you need for printing the signal time-space diagram.
    Note: You define print frame settings in the graphic parameters, in the Print frame
    section (see "Setting the graphic parameters for the Transfers display of regular services" on page 2396).
    Other print settings correspond to those for printing the network display (see "Printing
    the network display" on page 2499).
    2. Make sure that the Transfers display of regular services window is open (see "Activating
    the transfers display of regular services" on page 2392).
    3. In the File menu, select the Print entry.
    The Print: Transfers display of regular services window opens.
    4. Make the desired settings (see "Starting print output" on page 2508).
    5. Confirm with OK.
    The transfers display of regular services is printed.

    PTVGROUP

    2399

    24.9.6.2 Exporting the transfers display of regular services as graphics file


    24.9.6.2

    Exporting the transfers display of regular services as graphics file


    You can save the transfers display of regular services to a graphics file of the type *.svg or
    *.dxf.
    1. Make sure the Transfers display of regular services window is open (see "Opening a
    signal time-space diagram" on page 2480).
    2. In the Transfers display of regular services menu, select one of the SVG Export or DXF
    Export entries.
    The Save SVG file or Save DXF file window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    The SVG export or DXF export window opens.
    5. Make the desired settings (see "SVG export" on page 2656 and "DXF export" on page
    2654).
    6. Confirm with OK.
    The Transfers display of regular services is saved in a *.svg or *.dxf file.
    Tip: You can also export the transfers display of regular services as a graphics file. To do
    so, from the Transfers display of regular services menu, choose JPG export (screenshot) or in the Transfers display of regular services window, on the toolbar, click the
    JPG export (screenshot) button (see "Exporting screenshots" on page 2663).

    24.10

    Displaying lane allocations in the network window


    You can display lane allocations at nodes and main nodes in order to visualize the node topology in the network editor (see Fundamentals: Chpt. 12.11 , page 766).

    24.10.1 Activating the display of lane allocations


    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Lane allocation entry.
    3. Make the desired changes.
    Element

    Description

    Draw lane allocation layer

    If this option is checked, lane turns will be displayed.

    Avoid overlapping If this option is checked, Visum will draw the lane turns in such a
    when drawing
    way that they do not overlap.
    Transport sys-

    2400

    Via this button you call a separate window for the specification

    PTVGROUP

    24.10.2 Setting graphic parameters for lane allocation


    Element

    Description

    tems

    whether all lane turns are to be displayed or only those which are
    permitted for selected transport systems.

    4. In the navigator, select the Lane allocation> Display entry.


    5. Make the desired settings (see "Setting graphic parameters for lane allocation" on page
    2401).
    6. Confirm with OK.
    The lane allocation is displayed.

    24.10.2 Setting graphic parameters for lane allocation


    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. In the navigator, select the entry Lane allocation > Display > tab Active.
    Notes: You cannot mark lane allocations in the network.
    You cannot set lane allocations passive. They are, however, displayed according to
    the settings specified in the Passive tab, if the associated nodes are passive.
    The settings in the Active and Passive tabs are nearly identical. Therefore, only the
    settings of the Active tab will be described in detail.
    3. Make the desired changes.
    Element

    Description

    Uniform display

    If the option has been selected, the lane allocations of all active
    nodes are displayed consistently.

    Classified display If this option is selected, you can classify and show lane allocation based on an attribute (see "Displaying classified objects
    based on attribute values" on page 2411).
    Note: If you have selected the Classified display option, specify the following settings
    individually for each class. Beforehand, click in the desired row of the list of classes.
    4. Make the desired changes in the Display section.
    Element

    Description

    Draw

    If the option has been selected, the lane allocation is drawn.

    Draw until scale

    If this option is selected, lane allocation is drawn up to the


    scale set when you zoom out (see "Editing the network scale" on
    page 2209).

    PTVGROUP

    2401

    24.11 Labeling network objects with tables or charts


    Element

    Description
    If the option has not been selected, the lane allocation will
    always be displayed, irrespective of the network scale.

    Color/Size

    Size
    Size of the lane allocation display in mm
    Color
    Use the selection list to select a color for the lane allocation
    arrows.
    Draw frame
    If the option has been selected, the lane allocation is drawn with
    a frame.

    5. Edit the settings in the Passive tab in the same manner if necessary.
    6. Confirm with OK.
    The lane allocation is displayed according to your settings.

    24.11

    Labeling network objects with tables or charts


    Also tables or charts can be used for network object labeling. The display of tables or charts
    can be set separately for each state (active, passive, and marked).

    In the example, the network objects are labeled with column charts and tables.

    24.11.1 Labeling network objects with tables


    In the network window, you can label network objects with freely configurable tables. In these
    tables, you can display up to five rows and two columns with attribute names and their values
    or a text (see Fundamentals: Chpt. 12.4 , page 757).
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. For line objects make sure, that in the <Network object type> tab the option Draw labels
    has been selected.
    3. Make sure that the table display has globally been enabled for the desired network object
    type and status:

    2402

    PTVGROUP

    24.11.1 Labeling network objects with tables


    Point object: Navigator entry <Network object type>> Display> desired tab> option
    Draw table> is active.
    Line object: Navigator entry <Network object type>> Label> Display> option Draw
    table> is active.
    Note: For classified display of a network object type, define by class whether tables
    are to be displayed.
    4. In the navigator, select the desired entry:
    Point object: Navigator entry <Network object type>> Table
    Line object: Navigator entry <Network object type>> Label> Table

    5. Make the desired changes.


    Note: The Table page provides two columns for the labeling of the network objects. A
    table with up to five rows is generated if you combine column 1 and column 2.
    Element

    Description

    Draw table If the option has been selected, the links are labeled with tables.
    Note
    The tables will only be drawn if the Draw table option has been selected
    in theDisplay tab.
    Distance

    PTVGROUP

    Distance between table and network object in mm

    2403

    24.11.1 Labeling network objects with tables


    Element

    Description

    Text size

    Text size in mm

    Distance

    Line distance in percent of the current text size

    Font

    Font
    In a separate window, you can specify a Font and a Style by clicking in
    the field.
    Transparent
    If the option has been selected, the text is displayed without the white
    background, as text only.

    Alignment Use the drop-down menu to specify the alignment of the table to the network object.
    Same
    color for
    all

    2404

    If the option has been selected, all (attribute) texts of the table are displayed in the same color. Use the selection list to select a text color.
    If the option has not been selected, you can specify a color for each
    attribute or text below the numbers in section Column 1 and Column 2.

    PTVGROUP

    24.11.2 Labeling network objects with column charts


    Element

    Description

    Draw
    frame

    If the option has been selected, each table is drawn with a frame.
    Use the drop-down list to select a color for the margin.

    Column 1 / Here you can specify the display of the five possible rows and the two
    Column 2 columns of the table. For each item, you can switch the display on or off
    by selecting the respective item via the check box behind the numbers.
    Text alignment
    In the drop-down list, you can select the text alignment left or right.
    Title/Value/Text
    Via the drop-down list, you can specify whether the attribute title, the attribute value or a user-defined text will be displayed, that you can enter in
    the input field below the list, if the Text option has been selected.
    Attribute
    The button opens the attribute selection window in which you can select
    an attribute. Its name or value will be displayed in the table.
    Tip
    If you select the title in column 1 and the value in column 2 and the same
    attribute for both columns, each row of the table displays the attribute title
    and the corresponding value.
    Decimal places
    Number of decimal places for the display of the attribute value
    Note
    The field is only active when selecting numerical attributes with decimal
    places.
    U (underlined)
    If the option has been selected, the respective attribute is underlined.
    Tip
    If you want to display the total of several attribute values in the bottom
    row, select option U for the attribute in the second last row.

    Note: If you click the Preview button, your changes will immediately be displayed
    though the Edit graphic parameters window is still open.
    6. Confirm with OK.
    The network objects are labeled with the tables according to your chosen settings.

    24.11.2 Labeling network objects with column charts


    You can show up to five attributes of network objects as column charts where the label is positioned.

    PTVGROUP

    2405

    24.11.2 Labeling network objects with column charts

    Note: Based on the settings in the Edit graphic parameters window > page Zones >
    Chart, the attribute Total is displayed above the zone number with a column width of 9
    mm. The attributes UDA 1, 2, 3 are displayed as 3 parallel columns on the base (Total).
    The width of each of the parallel columns on a base results from the current column width
    and the number of parallel columns 9 : 3 = 3 mm.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. For line objects make sure, that in the <Network object type> tab the option Draw labels
    has been selected.
    3. Make sure that the chart display has been enabled for the desired network object type and
    status:
    Point object: Navigator entry <Network object type>> Display> desired tab> option
    Draw chart> is selected.
    Line object: Navigator entry <Network object type>> Label> Display> option Draw
    chart> is selected.
    Note: For classified display of a network object type, define by class whether charts
    are to be displayed.
    4. In the navigator, select the desired entry:
    Point object: Navigator entry <Network object type>> Chart
    Line object: Navigator entry <Network object type>> Label> Chart

    2406

    PTVGROUP

    24.11.2 Labeling network objects with column charts

    5. Make the desired changes.


    Element

    Description

    Draw chart If the option has been selected, the network objects are labeled with
    charts.
    Note
    The charts will only be drawn if the Draw chart option has been selected
    in the Display tab.
    Display

    Columns
    If the option has been selected, a column chart is displayed.
    Pie
    If the option has been selected, a pie chart is displayed.

    Column
    width

    Width of each column, if the columns are arranged in parallel


    Note
    If the Base option has been selected, the respective columns are displayed one above the other.

    Description

    Font
    In a separate window, you can specify a Font and a Style by clicking in
    the field.
    Transparent
    If the option has been selected, the text is displayed without the white

    PTVGROUP

    2407

    24.11.2 Labeling network objects with column charts


    Element

    Description
    background, as text only.
    Color
    Use the selection list to select a color for the labels.
    Size
    Size of the label in mm
    Notes
    Texts which are longer than the column height are displayed above the
    column. Texts which are longer than the column width are not displayed.
    Draw
    If the option has been selected, the charts are labeled.
    Color like column
    If the option has been selected, all labels have the same color as the
    corresponding column.
    If the option has not been selected, you can specify a consistent color
    for all chart labels.
    Decimal places
    Number of decimal places for the display of the value

    Draw

    If the option has been selected, the selected attribute is displayed.

    Attribute

    The button opens the attribute selection window in which you can select
    an attribute. Its value will be displayed in the chart.

    Scaling

    Here you can adjust the scaling to the current value range.

    Height

    Height of the maximum scaling value in mm

    Round

    Rounding factor for the label

    Color

    You can select the color and fill style for attribute display in a separate
    window. To do so, click in the box (see "Editing the properties of a closed
    polygon" on page 2252).

    Base

    If the option has been selected, the respective attribute is displayed as


    base. Hereon, all other attributes are arranged in parallel.

    Hide if
    (absolute)
    value

    Enter minimum value


    Note
    If an attribute value is smaller than the entered values, no column will be
    displayed.

    Calculate
    min/max

    If the option has been selected, the minimum and the maximum value are
    calculated.
    Note
    You can disable the option to avoid long computing times.

    2408

    PTVGROUP

    24.11.3 Labeling network objects with pie charts


    Tip: You can edit the order of the columns by clicking the handle right behind each
    number (1-5) and drag the row to the desired position.
    6. Confirm with OK.
    The network objects are labeled with the tables according to your chosen settings.

    24.11.3 Labeling network objects with pie charts


    You can show up to five attributes of network objects as by pie charts where the label is positioned.

    1. In the Graphics menu, select the Edit graphic parameters entry.


    The Edit graphic parameters window opens.
    2. For line objects make sure, that in the <Network object type> tab the option Draw labels
    has been selected.
    3. Make sure that the chart display has been enabled for the desired network object type and
    status:
    Point object: Navigator entry <Network object type>> Display> desired tab> option
    Draw chart> is selected.
    Line object: Navigator entry <Network object type>> Label> Display> option Draw
    chart> is selected.
    Note: For classified display of a network object type, define by class whether charts
    are to be displayed.
    4. In the navigator, select the desired entry:
    Point object: Navigator entry <Network object type>> Chart
    Line object: Navigator entry <Network object type>> Label> Chart
    5. Make the desired changes.

    PTVGROUP

    2409

    24.11.3 Labeling network objects with pie charts


    Element

    Description

    Draw chart If the option has been selected, the network objects are labeled with
    charts.
    Note
    The charts will only be drawn if the Draw chart option has been selected
    in the Display tab.
    Display

    Columns
    If the option has been selected, a column chart is displayed.
    Pie
    If the option has been selected, a pie chart is displayed.

    Parameters

    Pie area
    Here you can enter the pie area for the maximum scaling value in mm.
    Scaling
    Here you can adjust the scaling to the current pie area.

    Description Font
    In a separate window, you can specify a Font and a Style by clicking in
    the field.
    Transparent
    If the option has been selected, the text is displayed without the white
    background, as text only.
    Draw
    If the option has been selected, the charts are labeled.
    Color like segment
    If the option has been selected, all labels are displayed in the same
    color as the corresponding segment.
    If the option has not been selected, you can specify a consistent color
    for all chart labels.
    Color
    Use the selection list to select a color for the labels.
    Size
    Size of the label in mm
    Decimal places
    Number of decimal places for the display of the value

    2410

    Draw

    If the option has been selected, the selected attribute is displayed.

    Attribute

    The button opens the attribute selection window in which you can select
    an attribute. Its value will be displayed in the chart.

    PTVGROUP

    24.12 Displaying classified objects based on attribute values


    Element

    Description

    Round

    Rounding factor for the label

    Color

    You can select the color and fill style for attribute display in a separate
    window. To do so, click in the box (see "Editing the properties of a closed
    polygon" on page 2252).

    6. Confirm with OK.


    The network objects are labeled with the tables according to your chosen settings.

    24.12

    Displaying classified objects based on attribute values


    In the network editor, you can specify a classified display of active network objects based on
    the attribute values of the network objects (see Fundamentals: Chpt. 12.3 , page 755). The network objects will then be displayed differently based on their attribute values. Furthermore,
    you can classify the display of labels and bars.
    For a classified display, you first need to insert classes either automatically or manually. Then
    define either for all classes or for each class separately, if and how the particular network
    objects are to be displayed.
    In the example, six classes have been inserted for zones with a value range of 08. Each
    class is displayed in a different color.

    The table stores the description of the individual classes. Each row describes a different class.
    You can edit the classes directly in the table, via the toolbar, or via the buttons. The column
    that displays the class limits is not aligned. In the case of alphanumerical values, the column is
    aligned.
    Note: A classified display is not possible for passive or marked objects.
    Subjects
    Setting up classes and class limits for classification
    Editing the classification classes
    Creating and deleting an individual class
    Editing the display settings and class limits of a class

    PTVGROUP

    2411

    24.12.1 Setting up classes and class limits for classification

    24.12.1 Setting up classes and class limits for classification


    You can specify classes and class limits for point objects and line objects. You can insert all
    desired classes at the same time and edit the display of newly inserted or existing classes
    simultaneously.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.
    The Edit graphic parameters window opens.
    2. In the navigator, select the desired entry.
    Note: You can set the option on different pages, for example under Zones> Display.
    3. Select the Classified display option.
    4. Use the button labeled with the attribute name to select the attribute by which you want to
    classify the display.
    For the selected attribute classes are displayed.
    Notes: Optionally, for alphanumerical, Boolean attributes and enumeration types a
    separate class is created for each characteristic of the selected attribute. Then the
    classes are automatically allocated correct default values.
    If you reject the automatic default setting, you can set it later via the Create classification for discrete values entry in the context menu of the classification grid.
    5. Click the Redefine all classes button.
    The Edit classification: Redefine all classes window opens.
    6. In the Class limits section, specify the desired settings.
    Note: For attributes which are not numerical the class limits are not subject to changes.

    2412

    PTVGROUP

    24.12.1 Setting up classes and class limits for classification


    Element

    Description

    Distribution of
    class limits

    User-defined
    If the option has been selected, you can enter the first and the last
    class limit in the input fields. All limits in between are determined automatically.
    Equidistant
    If the option has been selected, you can enter values for the first two
    classes in the input fields next to the scale. All other limits are determined automatically according to the difference between the first two
    values. Each new class limit is determined by adding the difference
    between the first two classes to the previous class limit. If you enter a
    new value, the limits are recalculated immediately.
    Logarithmically
    If the option has been selected, you can enter values for the first two
    classes in the input fields next to the scale. All other limits are determined automatically according to the difference between the first two
    values. Each new class limit is determined by multiplying the difference between the first two classes by the previous class limit. If
    you enter a new value, the limits are recalculated immediately.
    Natural breaks
    If the option has been selected, all class limits are generated automatically. Based on the attribute values that exist in the network and
    the current number of classes, a meaningful classification is generated.
    Note
    The method aims at determining the class limits in such a way that
    each class contains approximately the same number of items.

    Number of clas- Desired number of classes


    ses
    Note
    The right side of the scale is adjusted immediately.
    7. In the entry fields next to the left column of the scale, enter the desired thresholds for different classes.
    Note: You can enter the two thresholds which differentiate between the lower three
    classes. Further thresholds are automatically calculated by Visum. You can edit these
    values later on, if required (see "Editing the display settings and class limits of a
    class" on page 2423).
    8. Make the desired changes in the Default section (see "Changing the classification settings
    of a point object" on page 2414 and "Changing the classification settings of a line object"
    on page 2415).
    9. Confirm with OK.
    PTVGROUP

    2413

    24.12.2 Editing the classification classes


    10. Via the buttons, adjust the settings for the display.
    Element

    Description

    Edit the colors


    for all classes

    Click this button to edit the color allocation of the classes (see
    "Editing the colors of all classes" on page 2416).

    Edit the size for Click this button to edit the size of texts and/or symbols (see "Editing
    all classes
    the sizes for all classes" on page 2421).

    24.12.2 Editing the classification classes


    You can adjust either all or selected classification settings.
    24.12.2.1 Changing the classification settings of a point object
    The following example of the network object zone illustrates how to change the properties of a
    classification of a point object.
    1. In the navigator, select the Zones > Display entry.
    2. Click the Redefine all classes button.
    The Edit classification: Redefine all classes window opens.
    3. In the Default section, adjust the desired settings.
    Element

    Description

    Draw object

    If the option has been selected, the objects are displayed.

    Draw until scale

    If the option is selected, the objects are drawn up to the scale


    set when you zoom out (see "Editing the network scale" on page
    2209).
    If the option has not been selected, the objects are always displayed, no matter what scale is used in the network.

    2414

    Table

    If the option has been selected, the objects are labeled with tables
    according to the settings on the Table page (see "Labeling network objects with tables" on page 2402).

    Chart

    If the option is selected, the objects are labeled with charts according to the settings on the Chart page (see "Labeling network
    objects with column charts" on page 2405)

    Polygon

    If the option has been selected, existing margins and faces of twodimensional point objects are drawn. You can specify the fill style,
    the color, and a line style in a separate window. To do so, click in
    the field (see "Editing the properties of a closed polygon" on page
    2252).

    Text/Symbol/Image

    Depending on the selected option, the object is displayed as text,


    symbol or image. The section below the option changes accordingly (see "Displaying active point objects" on page 2341).

    PTVGROUP

    24.12.2.2 Changing the classification settings of a line object


    4. Adjust the settings in the Color settings section and make the desired changes to the color
    scale (see "Editing the colors of all classes" on page 2416).
    5. Confirm with OK.
    The settings are applied and displayed in the right column of the scale.
    Tip: Use the Cancel button to discard the settings of the right column of the scale and
    restore the settings of the left columns.
    24.12.2.2 Changing the classification settings of a line object
    The following example of the network object link illustrates how to change the classification settings of a line object.
    1. In the navigator, select the Links > Display entry.
    2. Click the Redefine all classes button.
    The Edit classification: Redefine all classes window opens.
    3. In the Default section, adjust the desired settings.
    Element

    Description

    Preview

    Here you can see how the line object will be displayed according to
    the current settings.

    Draw object

    If the option has been selected, the objects are displayed.

    Draw until
    scale

    If the option is selected, the objects are drawn up to the scale set
    when you zoom out (see "Editing the network scale" on page 2209).
    If the option has not been selected, the objects are always displayed, no matter what scale is used in the network.

    Line style

    Here you can specify the line style (see "Setting parameters for the
    line style" on page 2365).

    Line width

    Enter the line width in mm

    PTVGROUP

    2415

    24.12.2.3 Editing the colors of all classes


    Element

    Description

    Line color

    Selection of a color for the line in a separate window

    Draw arrow
    head

    If the option has been selected, an arrow head is drawn. Specify the
    following settings for the arrow head.
    Via the drop-down list, select the symbol that will be displayed as
    arrow head.
    Size
    Size of arrow head in mm
    Color
    You can specify a color for the arrow head in a separate window. To
    do so, click in the field (see "Editing the properties of a closed polygon" on page 2252).
    Sign
    If you select the Circle or Square symbol, you can activate the input
    field by checking the box. In the input field, you can enter a sign
    which will be displayed inside the circle or square. Use the dropdown list to select a color for the sign.

    4. Adjust the settings in the Color settings section and make the desired changes to the color
    scale (see "Editing the colors of all classes" on page 2416).
    5. Confirm with OK.
    The settings are applied and displayed in the right column of the scale.
    Tip: Use the Cancel button to discard the settings of the right column of the scale and
    restore the settings of the left columns.
    24.12.2.3 Editing the colors of all classes
    You can edit the colors of all classes at the same time.
    Editing the colors of the classification of a point object
    The following example of the network object zone illustrates how to change the colors of the
    classes.
    1. In the navigator, select the Zones > Display entry.
    2. Click the Edit the colors for all classes button.
    The Edit classification: Edit the colors for all classes window opens.

    2416

    PTVGROUP

    24.12.2.3 Editing the colors of all classes

    3. In the Color settings: Point object section, specify the desired setting.
    Element

    Description

    Text color/Fill
    color from
    color ramp

    If the option has been selected, the color from the color ramp is used.
    If the option has not been selected, the color of the previously set
    color is used.
    Note
    Depending on the selected point type, the color is called text color or
    fill color.

    Margin color
    from color
    ramp / Frame
    color from
    color ramp

    For classified symbol or image display you can select the filling color
    and the margin color here.
    For classified text display you can select the text color and the frame
    color here.
    If the option has been selected, the color from the color ramp is also
    used for the margin or frame.

    Margin color
    constant /
    Frame color
    constant

    If the option has been selected, you can select the color for the margin or frame, as applicable, via the color field.

    Margin color
    unchanged /
    Frame color
    unchanged

    If the option has been selected, the color already set for the margin
    or frame is used.

    PTVGROUP

    2417

    24.12.2.3 Editing the colors of all classes


    4. In the Color settings: Polygon section, adjust the desired settings, if applicable.
    Note: Here you can specify the polygon fill color and the frame color for the polygons.
    This section is only available, if the network object has a polygon. These options correspond to those for point objects.
    5. Right-click in the color scale.
    Note: Use the color scale to specify the class colors and distances between the classes. The left column visualizes the current settings, whereas the right column presents the preview for the new settings.
    The context menu opens.
    6. Select the desired entry.
    Element

    Description

    Create color here

    Via this entry, you add another color to the selected position in the
    color scale.
    Note
    Click the arrow to the right of a color field in order to allocate a
    new color.

    Set color gradient Via this entry you decide to connect the two colors next to your
    for this section
    click position in the scale by a color gradient.
    Set constant color Via this entry you decide that the section between the two colors
    for this section
    next to your click position will be displayed by the color of the
    color section on top.
    Reset to standard Via this entry, you reset the color scale to a default value.
    color ramp
    Invert color ramp

    Via this entry, you rotate the given scale by 180.

    Delete any additional color

    Via this entry, you delete all additional colors.

    Create qualitative Via this entry, you create a qualitative scale for all classes Thus,
    scale for current each class is allocated its own color.
    number of classes
    Set transparency
    for all colors

    Via this entry, you enter a percentage which defines the degree of
    transparency for the colors in the color ramp.

    Set color gradient Via this entry you define that all sections between two colors are
    for all sections
    to be displayed by color gradients.
    Set constant
    colors for all sections

    2418

    Via this entry you define that all sections between two colors will
    be displayed by the color of the color section on top.

    PTVGROUP

    24.12.2.3 Editing the colors of all classes


    Notes: Within the scale, you can shift a color: Keep the mouse-key pressed while dragging the pointer up or down. Alternatively, you can right-click a color and select the
    Edit position entry: Enter a value between 0.01 and 0.99.
    You can copy a color in the scale: Keep the C TRL key pressed while shifting it.
    You can delete an additional color: Keep the mouse-key pressed while dragging the
    pointer to the right. Alternatively, you can right-click a color and select the Delete
    color entry.
    7. Confirm with OK.
    The settings are applied and displayed in the table.
    Editing the colors of the classification of a line object
    The following example of the network object link illustrates how to change the classification settings of a line object.
    1. In the navigator, select the Links > Display entry.
    2. Click the Edit the colors for all classes button.
    The Edit classification: Edit the colors for all classes window opens.

    3. In the Color settings section, specify the desired setting.

    PTVGROUP

    2419

    24.12.2.3 Editing the colors of all classes


    Element

    Description

    Line color/Fill
    color from
    color ramp

    If the option has been selected, the color from the color ramp is used.
    If the option has not been selected, the color of the previously set
    color is used.
    Notes
    In case of several stroke layers the color is called fill color. In case of
    just one stroke layer, the color is called line color.
    The following options are available only if several stroke layers have
    been defined.

    Frame color
    from color
    ramp

    If the option has been selected, the color from the color ramp is also
    used for the frame.

    Frame color
    constant

    If the option has been selected, you can select the color for the frame
    via the color field.

    Frame color
    unchanged

    If the option has been selected, the color already set for the frame is
    used.

    4. Right-click in the color scale.


    Note: Use the color scale to specify the class colors and distances between the classes. The left column visualizes the current settings, whereas the right column presents the preview for the new settings.
    The context menu opens.
    5. Select the desired entry.
    Element

    Description

    Create color here

    Via this entry, you add another color to the selected position in the
    color scale.
    Note
    Click the arrow to the right of a color field in order to allocate a
    new color.

    Set color gradient Via this entry you decide to connect the two colors next to your
    for this section
    click position in the scale by a color gradient.
    Set constant color Via this entry you decide that the section between the two colors
    for this section
    next to your click position will be displayed by the color of the
    color section on top.
    Reset to standard Via this entry, you reset the color scale to a default value.
    color ramp
    Invert color ramp

    2420

    Via this entry, you rotate the given scale by 180.

    PTVGROUP

    24.12.2.4 Editing the sizes for all classes


    Element

    Description

    Delete any additional color

    Via this entry, you delete all additional colors.

    Create qualitative Via this entry, you create a qualitative scale for all classes Thus,
    scale for current each class is allocated its own color.
    number of classes
    Set transparency
    for all colors

    Via this entry, you enter a percentage which defines the degree of
    transparency for the colors in the color ramp.

    Set color gradient Via this entry you define that all sections between two colors are
    for all sections
    to be displayed by color gradients.
    Set constant
    colors for all sections

    Via this entry you define that all sections between two colors will
    be displayed by the color of the color section on top.

    Notes: Within the scale, you can shift a color: Keep the mouse-key pressed while dragging the pointer up or down. Alternatively, you can right-click a color and select the
    Edit position entry: Enter a value between 0.01 and 0.99.
    You can copy a color in the scale: Keep the C TRL key pressed while shifting it.
    You can delete an additional color: Keep the mouse-key pressed while dragging the
    pointer to the right. Alternatively, you can right-click a color and select the Delete
    color entry.
    6. Confirm with OK.
    The settings are applied and displayed in the table.
    24.12.2.4 Editing the sizes for all classes
    The size of all symbols, images and texts of a classified point object or the line width of a classified line object can be changed as follows.
    Editing the size settings for symbols, images or texts of a point object
    The following example of the network object zone illustrates how you can change the size of
    the symbols, images or texts of all classes.
    1. In the navigator, select the Zones > Display entry.
    2. Click the Edit the size for all classes button.
    The Edit classification: Resize all classes window opens.
    3. In the Class limits section, make the settings of your choice (see "Setting up classes and
    class limits for classification" on page 2412).
    4. Click the small arrow above the size scale and select the desired entry.

    PTVGROUP

    2421

    24.12.3 Creating and deleting an individual class


    Element

    Description

    Constant size

    Via this entry field, you can specify the size value for all displayed
    objects.

    Continuous definition

    Via two entry fields, you can enter the size values for the first
    class and the last class. The size continuously changes for the
    classes in-between.

    Discontinuous
    definition

    Via three entry fields, you can enter the size values for the first
    class and the last class and the class in the middle. The size continuously changes for the classes in-between.

    5. Confirm with OK.


    The settings are applied and displayed in the table.

    Changing the width of a classified line object


    The following example of the network object link illustrates how to change the line width of a
    line object.
    1. In the navigator, select the Links > Display entry.
    2. Click the Edit the size for all classes button.
    The Edit classification: Change size window opens.
    3. In the Class limits section, make the settings of your choice (see "Setting up classes and
    class limits for classification" on page 2412).
    4. Click the small arrow above the size scale and select the desired entry.
    Element

    Description

    Constant size

    Via this entry field, you can specify the size value for all displayed
    objects.

    Continuous definition

    Via two entry fields, you can enter the size values for the first
    class and the last class. The size continuously changes for the
    classes in-between.

    Discontinuous
    definition

    Via three entry fields, you can enter the size values for the first
    class and the last class and the class in the middle. The size continuously changes for the classes in-between.

    5. Confirm with OK.


    The settings are applied and displayed in the table.

    24.12.3 Creating and deleting an individual class


    For a classification setup, you can add or delete classes one by one. The procedure is the
    same for point objects and line objects.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    2422

    PTVGROUP

    24.12.4 Editing the display settings and class limits of a class


    The Edit graphic parameters window opens.
    2. In the navigator, select the desired entry.
    3. Select the Classified displayoption.
    4. In the table, click the row after which you want to insert a new class.
    5. Click the

    Create button.

    Tip: Alternatively, you can duplicate an existing class with the set graphic parameters
    via the

    Duplicate class icon.

    The class is created. The class limit of the new class lies between the selected class and the
    next one.
    Notes: You may edit the class limits and other properties later on (see "Editing the display settings and class limits of a class" on page 2423).
    You can delete a class by marking it in the table and clicking the
    cannot delete the last class.

    Delete button. You

    Tip: Alternatively, you can call the editing functions in the context menu of the table.

    24.12.4 Editing the display settings and class limits of a class


    In a classification, you can edit individual classes subsequently. Alternatively, you can edit all
    classes at the same time (see "Editing the classification classes" on page 2414).
    24.12.4.1 Editing the display settings and class limits of a point object class
    1. Create classes for display (see "Setting up classes and class limits for classification" on
    page 2412 and "Creating and deleting an individual class" on page 2422).
    2. Select the Use layer order option, if required.
    Note: If the option has been selected, you can set up the order of drawing for the network objects by class. The order is specified via the numbers in the Layer column.
    This column appears as soon as the option is checked.
    By default, the network objects of the various classes are drawn in the order as specified by the order of the classes in the table.
    3. Make the desired changes in the table if necessary.

    PTVGROUP

    2423

    24.12.4.1 Editing the display settings and class limits of a point object class
    Notes: You can edit the values of the white cells if you double-click the respective cell.
    A quick info displays the respective values.
    Use the
    Attribute selection icon to select the attributes for display in the table
    columns (see "The window used for the selection of multiple attributes" on page 968).
    Right-click a column header to call the context menu and add or delete individual
    columns.
    Use the
    Reset to default attribute selection icon to reset the attributes displayed
    as columns to the default settings.

    Element

    Description

    UpperLimit

    For numerical attributes, the column displays the upper class limit. You
    can edit the values directly (units: hours and kilometers).

    Draw

    If the option has been selected for the respective class, the class is
    drawn according to the specified options. Deactivate the respective
    checkbox, if you do not want to display a specific class.

    Preview

    Here you can see the display of the class according to your current settings.
    If you click this field, the display properties of the class are displayed in
    a new window. Here you can edit the class and switch to the next class
    in order to edit it by clicking the Next class button.

    LegendName

    By default, the class limit for attributes is displayed. You can edit the
    values.
    Note
    You can reset the class name to the class limit. To do so, right-click in
    the column header and select the entry Reset all class names.
    For example, class names are displayed in the legend.

    LayerNo

    The numbers indicate the order of drawing for the classes in the network display.
    Notes
    The column is only displayed, if the Use layer order option has been
    selected.
    You can also use this order for the display of classes in the legend (see
    "Inserting legends" on page 2255).

    2424

    Point type

    Here the selected type is displayed.


    If you click the field, you can pick a different type in a drop-down list.
    Note
    Depending on the selected type further attribute fields are grayed out.

    Form

    Depending on the selected point type, the selected text attribute or the

    PTVGROUP

    24.12.4.1 Editing the display settings and class limits of a point object class
    Element

    Description
    selected symbol is displayed here.
    If you select the point type text and click the field, you can select a different attribute.
    If you select the point type symbol and click the field, you can select a different symbol in a drop-down list.
    Note
    If you select the point type image, the field is disabled.

    Size

    Depending on the selected point type, the size of the text or symbol or
    the image height is displayed here. You can edit the values.

    Display

    The color and, where applicable, the line style of the displayed point
    object are displayed here.
    If you select the point type text and click the field, you can select a different color for the displayed text.
    If you select the point type symbol and click the field, depending on the
    selected symbol, you can specify a different fill color and a different line
    style.
    Notes
    If you pick certain symbols, the field is disabled.
    If you select the point type image and click the field, the
    played. Use the icon to select an image file.

    icon is dis-

    Draw polygon

    If the option is selected for the respective class, a polygon is drawn.


    Deactivate the respective checkbox, if you do not want to display a polygon for a specific class.

    Polygon

    Preview of the display of the polygon


    Notes
    A polygon is drawn only if you have selected the Draw polygon option
    in the respective row.
    If a polygon is drawn, you can specify the fill style and the boundary in a
    separate window by clicking in the field.

    4. In the table, click in the row of the desired class.


    5. On the toolbar, click the

    Edit graphic parameters icon.

    Tip: Alternatively, you can double-click the cell of the desired class.
    The Edit the graphic parameters of class <number> window opens.
    6. Make the desired changes.

    PTVGROUP

    2425

    24.12.4.2 Editing the display settings and class limits of a line object class
    Element

    Description

    Preview

    Here you see the display of the class according to your current settings.

    Draw object

    If the option has been selected, the selected class is displayed in


    the network.

    Draw until scale

    If the option is selected, the objects are drawn up to the scale set
    when you zoom out (see "Editing the network scale" on page
    2209).
    If the option has not been selected, the objects are always displayed, no matter what scale is used in the network.

    Draw table

    If the option has been selected, the objects are labeled with tables
    according to the settings on the Table page (see "Labeling network
    objects with tables" on page 2402).

    Draw chart

    If the option is selected, the point objects are labeled with a chart,
    according to the settings on the Chart page (see "Labeling network
    objects with column charts" on page 2405).

    Draw polygon

    If the option has been selected, existing margins and faces of twodimensional point objects are drawn. You can specify the fill style,
    the color, and a line style in a separate window. To do so, click in
    the field (see "Editing the properties of a closed polygon" on page
    2252).

    Point object type Here you select if the point object is displayed as text, symbol, or
    image.
    Text/Symbol/Image

    Depending on the selected option, the point object is displayed as


    text, symbol or image. The settings change accordingly (see "Displaying active point objects" on page 2341).

    Previous
    Use the buttons to switch to and directly edit the previous or the
    class/Next class next class.
    7. Confirm with OK.
    The changes are applied.
    Tip: Alternatively, you can call the editing functions in the context menu of the table.
    24.12.4.2 Editing the display settings and class limits of a line object class
    1. Create classes for display (see "Editing the classification classes" on page 2414 and "Creating and deleting an individual class" on page 2422).
    2. Select the Use layer order option, if required.

    2426

    PTVGROUP

    24.12.4.2 Editing the display settings and class limits of a line object class
    Note: If the option has been selected, you can set up the order of drawing for the network objects by class. The order is specified via the numbers in the Layer column.
    This column appears as soon as the option is checked.
    By default, the network objects of the various classes are drawn in the order as specified by the order of the classes in the table.
    3. Make the desired changes in the table if necessary.
    Notes: You can edit the values of the white cells if you double-click the respective cell.
    A quick info displays the respective values.
    Use the
    Attribute selection icon to select the attributes for display in the table
    columns (see "The window used for the selection of multiple attributes" on page 968).
    Right-click a column header to call the context menu and add or delete individual
    columns.
    Note: Use the
    Reset to default attribute selection icon to reset the attributes displayed as columns to the default settings.
    Element

    Description

    UpperLimit

    For numerical attributes, the column displays the


    upper class limit. You can edit the values directly
    (units: hours and kilometers).

    Draw

    If the option has been selected for the respective


    class, the class is drawn according to the specified
    options. Deactivate the respective checkbox, if you
    do not want to display a specific class.

    Preview

    Here you can see the display of the class according


    to your current settings.
    If you click this field, the display properties of the
    class are displayed in a new window. Here you can
    edit the class and switch to the next class in order to
    edit it by clicking the

    LegendName

    PTVGROUP

    button.

    By default, the class limit for attributes is displayed.


    You can edit the values.
    Note
    You can reset the class name to the class limit. To do
    so, right-click in the column header and select the
    entry Reset all class names.
    For example, class names are displayed in the
    legend.

    2427

    24.12.4.2 Editing the display settings and class limits of a line object class
    Element

    Description

    LayerNo

    The numbers indicate the order of drawing for the


    classes in the network display.
    Notes
    The column is only displayed, if the Use layer order
    option has been selected.
    You can also use this order for the display of classes
    in the legend (see "Inserting legends" on page
    2255).

    Stroke

    Here you can specify the line style (see "Setting parameters for the line style" on page 2365).

    StrokeWidth

    Enter the stroke width in mm.

    StrokeColor

    Selection of a color for the stroke in a separate window

    Arrow drawing

    If the option has been selected, the selected class is


    displayed with an arrow head.

    4. In the table, click in the row of the desired class.


    5. On the toolbar, click the

    Edit graphic parameters icon.

    Tip: Alternatively, you can double-click the cell of the desired class.
    The Edit the graphic parameters of class <number> window opens.
    6. Make the desired changes.
    Element

    Description

    Preview

    Here you see the display of the class according to your current settings.

    Draw
    object

    If the option has been selected, the selected class is displayed in the network.

    Draw until
    If the option is selected, the objects are drawn up to the scale set when
    scale
    you zoom out (see "Editing the network scale" on page 2209).
    If the option has not been selected, the objects are always displayed,
    no matter what scale is used in the network.
    Line style Here you can specify the line style (see "Setting parameters for the line
    style" on page 2365).
    Line width Enter the line width in mm
    Line color Selection of a color for the line in a separate window
    Draw

    2428

    If the option has been selected, an arrow head is drawn. Specify the fol-

    PTVGROUP

    24.13 Displaying desire lines


    Element

    Description

    arrow
    head

    lowing settings for the arrow head.


    Via the drop-down list, select the symbol that will be displayed as arrow
    head.
    Size
    Size of arrow head in mm
    Color
    You can specify a color for the arrow head in a separate window. To do
    so, click in the field (see "Editing the properties of a closed polygon" on
    page 2252).
    Sign
    If you select the Circle or Square symbol, you can activate the input field
    by checking the box. In the input field, you can enter a sign which will be
    displayed inside the circle or square. Use the drop-down list to select a
    color for the sign.
    Use the icons to switch to and directly edit the previous or the next class.

    7. Confirm with OK.


    The changes are applied.

    24.13

    Displaying desire lines


    Desire lines display the values of OD pairs between zones or main zones, for example the
    direct distance or the journey time (see Fundamentals: Chpt. 12.7 , page 760).
    Notes: The current parameter settings are saved with the version and the graphic parameters (see "Opening and saving a version file" on page 840 and "Printing the network
    display" on page 2499).
    The attribute values are also saved with the version and can additionally be saved as
    matrices (see "Modeling demand" on page 1606).

    24.13.1 Displaying desire line bars and adjusting basic settings


    You decide whether you want to display desire lines for zones or main zones and adjust the
    basic settings. Desire line display can include the following:
    Desire line bars
    Desire line bar labels
    Desire line links
    1. From the Graphics menu, choose Edit graphic parameters.
    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.

    PTVGROUP

    2429

    24.13.1 Displaying desire line bars and adjusting basic settings


    The Edit graphic parameters window opens.
    2. In the navigator, select the Desire lines zones entry.
    Note: For the display of desire lines between main zones, select the navigator entry
    Desire lines main zones. The parameters are the same.
    3. Select the Layer control tab.
    4. Make the desired changes.
    Element

    Description

    Draw layer desire If this option has been selected, desire lines can be displayed.
    lines (zones)
    Draw bars

    If this option has been selected, desire line bars can be displayed.

    Draw bar labels

    If this option has been selected, bar labels can be displayed.

    Draw desire line


    links

    If this option has been selected each OD pair is displayed by a


    linear slope.

    5. Select the General settings tab.


    6. Make the desired changes.
    Element

    Description

    Use crossIf the option has been selected, the mean value is calculated from
    section
    both directions.
    values
    If the option has not been selected, the values are determined separately for each direction.
    Note
    If an undirected value to be displayed is averaged, it is automatically divided by two, so that half of the undirected value counts as the upper limit
    for the scaling. If, for example, the scaling range is 1-1000 and the bar
    width is 10 mm, an undirected value of 2000 is displayed with a volume
    of 1000 on each side and a bar width of 10 mm.
    Distance
    between
    bars

    2430

    Distance between the desire line bars in mm

    PTVGROUP

    24.13.1 Displaying desire line bars and adjusting basic settings


    Element

    Description

    Line style
    properties

    You can edit the line style in a separate window. To do so, click in the
    box (see "Setting the line style properties" on page 2363).

    Text posiNext to bar


    tioning: ver- If the option has been selected, the label is displayed next to the bar.
    tical
    Within bar
    If the option has been selected, the label is displayed within the bar.
    Text distance
    Distance between label and desire line link (if the option Within bar has
    been selected) or the distance between label and bar (if the option Next
    to bar has been selected).
    7. Select the Text format tab.
    8. Make the desired changes.
    Element

    Description

    Font and Font


    color
    You can specify a Font and a Style in a separate window. To do so, click in
    the field.
    Text size
    Text size in mm
    Note
    If the text size is 0.0mm, no bar label is issued.
    Color like bar
    If the option has been selected, the text is displayed in the same color as
    the bar.
    Tip
    We recommend this option, if several bars are displayed.
    If the option has not been selected, you can select a color in the drop-down
    list.
    Text
    entry

    PTVGROUP

    Transparent
    If the option has been selected, the bar label is displayed without the white
    background, as text only.
    Draw frame
    If theoption is selected, the label is drawn with a frame. From the selection
    list, you can select the color.
    Alignment
    You can specify the alignment and the display of several bar labels via the
    drop-down list:

    2431

    24.13.1 Displaying desire line bars and adjusting basic settings


    Element

    Description
    Horizontal

    The labels are displayed in a row.


    Vertical

    The labels are displayed one below the other.


    Vertical + Sum

    All labels are displayed one below the other and underneath, the sum of
    the values is displayed.
    Sum only

    Only the values of the sum are displayed.


    Line spacing
    Line distance in percent of the current text size
    9. Select the OD pair selection tab.
    10. Make the desired changes.
    Element

    Description

    OD pairs are displayed

    Maximum number of OD pairs displayed


    . OD pairs with the greatest scaling attribute values are drawn
    (see "Setting the display properties of a bar" on page 2374).

    Draw only active OD


    pairs

    If the option has been selected, only active OD pairs are displayed.

    Regard all OD pairs

    If the option has been selected, all OD pairs are displayed.

    Draw only selected


    OD pairs

    If the option has been selected, you can display OD pairs with
    specific attribute values. Use the button below the option to
    select the desired attribute.
    Click the Edit button to create the classification (see "Displaying classified objects based on attribute values" on page
    2411). Via the check box in the Draw column you decide whether the OD pairs of the particular class are to be drawn.
    Use layer order
    If the option has been selected, you can specify the order of
    drawing for the classes. The order is specified via the numbers
    in the Layer column. This column appears as soon as the
    option is checked. By default, the network objects of the
    various classes are drawn in the order as specified by the
    order of the classes in the list.

    Desire lines are always displayed and the basic settings have been preset. In the Desire lines
    zones > Display section, you now have to define the individual bars and their display pro-

    2432

    PTVGROUP

    24.13.2 Displaying bars for desire lines


    perties (see "Defining one or multiple bars" on page 2373 and "Setting the display properties
    of a bar" on page 2374).

    24.13.2 Displaying bars for desire lines


    For desire lines, you can display bars. The bars represent an attribute value between the linked (main) zones.
    1. From the Graphics menu, choose Edit graphic parameters.
    The Edit graphic parameters window opens.
    2. Make the desired changes on the Desire lines zones page.
    Note: For the display of desire lines between main zones, select the navigator entry
    Desire lines main zones. The parameters are the same.
    3. In the navigator, select the Desire lines zones > Display entry.

    In the upper section, a preview of the currently configured bars appears. The table below
    stores the description of the bars. Each column in the table describes a bar.
    4. If applicable, mark the desired columns by a click in the column header.
    5. Make the desired changes.

    PTVGROUP

    2433

    24.13.3 Hiding the display of single desire lines


    Element Description
    Adds another column to the right of the currently marked column. Simultaneously, another bar is added.
    Copies the marked columns
    Copies the marked columns and changes the bar colors
    Opens a window in which you can edit the display properties of the bar
    selected (see "Setting the display properties of a bar" on page 2374)
    Removes the marked columns. Simultaneously, the bars are removed
    Moves the currently marked columns by one position to the left
    Moves the currently marked columns by one position to the right
    Opens the Attribute selection window in which you can specify the attributes you want to show as table rows (see "The window used for the selection of multiple attributes" on page 968).
    Resets the attributes which are currently displayed as table row names to
    the standard settings.
    You have defined the number of bars for the matrix flow bundle. The contents of the table
    columns indicate some bar display properties. Some of them you can directly edit. All bar display properties can be accessed via the icon
    on page 2374).

    (see "Setting the display properties of a bar"

    24.13.3 Hiding the display of single desire lines


    For zones, you can hide the display of individual desire lines by direction. For main zones, this
    is not possible.
    1. In the Graphics menu, select the Desire lines entry.
    The Graphics tools (Desire line) window opens.
    2. Click the zone (= From zone) at which the desire line starts that you want to switch off.
    The From zone is displayed in the Graphics tools (Desire line) window.
    3. Click the zone (= To zone) at which the desire line ends that you want to switch off.
    The To zone is displayed in the Graphics tools (Desire line) window.
    4. Disable the Draw bar option.

    2434

    PTVGROUP

    24.14 Displaying turns, main turns, and turn volumes


    Notes: Via the Draw bar label option, you can also hide the label of the selected
    desire line.
    Via the Shift label option, you can shift the labeling of the selected desire line along
    the desire line link. if you have clicked the button, you can specify the new position
    along the desire line link with the mouse.
    If you would like to deselect the display of desire lines, you have to deselect the relevant
    option in the menu Graphics> Edit graphic parameters (see "Displaying desire line bars and
    adjusting basic settings" on page 2429).

    24.14

    Displaying turns, main turns, and turn volumes


    You have various options for the display of turns and main turns. Turns can be displayed as
    arrows, for example.
    The turn volumes view displays turns as bars. These are weighted by attributes. Furthermore,
    a circle can be displayed around the node which contains the turns. Outside of the circle, you
    can display labels.

    24.14.1 Displaying turns and main turns


    You can display turns, prohibited turns, U-turns, and major flows at nodes.
    1. From the Graphics menu, choose Edit graphic parameters.
    Tip: Alternatively, you can open the window by pressing the C TRL and G keys at the
    same time.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Turns entry.

    3. Make the desired changes.

    PTVGROUP

    2435

    24.14.1 Displaying turns and main turns


    Element

    Description

    Draw turns
    layer

    If the option has been selected, you can display turns, main turns,
    and turn volumes in the network window.
    Draw turns
    If the option has been selected, you can display turns and main turns
    in the network window.
    Draw turn volumes
    If the option has been selected, you can display turn volumes in the
    network window (see "Adjusting the basic settings for the display of
    turn volumes" on page 2437).
    Draw bars
    IIf the option has been selected, you can display the bars of turn volumes in the network window (see "Adjusting the basic settings for the
    display of turn volumes" on page 2437).
    Draw bar labels
    If the option has been selected, you can display the bar labels of turn
    volumes in the network window (see "Adjusting the basic settings for
    the display of turn volumes" on page 2437).

    Layer on top
    will be drawn
    last

    The list shows the order in which the turns and turn volumes will be
    drawn. Use the
    layers.

    and

    icons to edit the order of the drawn

    Turns/ProHere you can specify for each object if and how it is displayed in the
    hibited turns/ U- network.
    turns/Major
    flows
    Color/Line style In a separate window, you can specify the color and the line style in
    which each object will be drawn by clicking in the field with the line.
    Draw

    If the option has been selected, the respective object is displayed in


    the network.

    Arrow head
    mm

    Size of the arrow head in mm

    Transport systems

    You can either select one transport system or All, if you want to display all turns which are permitted for all PrT and PuT transport systems.
    Note
    For major flows, you cannot select a transport system.
    The transport system PuT Walk is not displayed.

    4. Confirm with OK.


    The objects are displayed according to your chosen settings.

    2436

    PTVGROUP

    24.14.2 Adjusting the basic settings for the display of turn volumes

    24.14.2 Adjusting the basic settings for the display of turn volumes
    You can specify how you want to display turn volumes. The settings apply to both, turns and
    main turns. To display turn volumes, you need to show them (see "Displaying turn volumes" on
    page 2441).
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    Tip: Alternatively, you can open the window by clicking the Open graphic parameters button in the Turn volumes window.
    2. In the navigator, select the Turns> Turn volumes entry.
    3. Select the Layer control tab.
    4. Select the Draw turn volumes option.
    5. Make the desired changes.
    Element

    Description

    Draw bars

    If the option has been selected, the turns are displayed as bars.

    Draw bar labels

    If the option has been selected, the bars are labeled.

    Draw edges

    If the option has been selected, an edge is displayed in the


    middle of each turn.

    6. Select the General settings tab.


    7. Make the desired changes.
    Element

    Description

    Use crossIf the option has been selected, the values are determined based on
    section
    the two directions of the object.
    values
    If the option has not been selected, the values are determined separately for each direction.
    Note
    If an undirected value to be displayed is averaged, it is automatically divided by two, so that half of the undirected value counts as the upper limit
    for the scaling. If, for example, the scaling range is 1-1000 and the bar
    width is 10 mm, an undirected value of 2000 is displayed with a volume
    of 1000 on each side and a bar width of 10 mm.
    Distance
    between
    bars

    Distance between the bars in mm

    Line style

    For each turn, the central line is displayed if in the Layer control tab, the

    PTVGROUP

    2437

    24.14.2 Adjusting the basic settings for the display of turn volumes
    Element

    Description

    properties

    option Draw edges has been checked. You can specify the line style in a
    separate window. To do so, click in the field (see "Setting the line style
    properties" on page 2363).

    Text posiNext to bar


    tioning: ver- If the option has been selected, the label is displayed next to the bar.
    tical
    Within bar
    If the option has been selected, the label is displayed within the bar.
    Text distance
    Distance of labels in mm
    Note
    If the Next to bar option is selected, the distance to the bar is displayed.
    If the Within bar option is selected, the distance to the link is indicated.

    Standard
    for text
    blocks

    All turns
    If the option has been selected, all turns are labeled consistently.
    Only incoming turns
    If the option has been selected, by default, only incoming turns are labeled at turn volumes.
    Only outgoing turns
    If the option has been selected, by default, only outgoing turns are labeled at turn volumes.

    Notes: If you change the settings in the Standard for text blocks section, a message
    will appear. You can decide whether the new setting is to be applied to currently displayed turn volumes.
    Apply for all: The new setting is applied to all currently displayed turn volumes.
    Only for standard: The new setting is applied to all turn volumes which are
    currently displayed according to the standard settings.
    No modification: The current turn volume display is not changed.
    If you mark a node while the Turn volumes window is open, you can select the Reset
    text blocks to standard entry via the context menu of a visible turn volume. The text
    blocks are then displayed according to the current settings in the graphic parameters.
    8. Select the Text format tab.
    9. Make the desired changes.

    2438

    PTVGROUP

    24.14.2 Adjusting the basic settings for the display of turn volumes
    Element

    Description

    Font and Font


    color
    You can specify a Font and a Style in a separate window. To do so, click in
    the field.
    Text size
    Text size in mm
    Note
    If the text size is 0.0mm, no bar label is issued.
    Color like bar
    If the option has been selected, the text is displayed in the same color as
    the bar.
    If the option has not been selected, you can select a color in the dropdown list.
    Tip
    We recommend this option, if several bars are displayed.
    Text
    entry

    Transparent
    If the option has been selected, the bar label is displayed without the white
    background, as text only.
    Draw frame
    If theoption has been selected, the label is drawn with a frame. From the
    selection list, you can select the color.
    Alignment
    You can specify the alignment and the display of several bar labels via the
    drop-down list:
    Horizontal
    The labels are displayed in a row.
    Vertical
    The labels are displayed one below the other.
    Vertical + Sum
    All labels are displayed one below the other and underneath, the sum of
    the values is displayed.
    Sum only
    Only the values of the sum are displayed.
    Matrix
    The label is displayed as two-row table grid: On top, the titles are stored,
    underneath the values accordingly. The last column contains the total sum.
    Line spacing
    Line distance in percent of the current text size

    10. Select the Turn selection tab.


    PTVGROUP

    2439

    24.14.2 Adjusting the basic settings for the display of turn volumes
    11. Make the desired changes.
    Element

    Description

    Draw bars only for


    active turns

    If the option has been selected, bars are not drawn for passive
    turns.

    Draw the bars also


    on blocked turns

    If the option has been selected, bars are also drawn for closed
    turns.

    Regard all turns

    If the option has been selected, bars are drawn on all turns that
    correspond to the above options.

    Draw the bars only


    on selected turns

    If the option has been selected, you can hide bars of turns with
    specific attribute values. Use the button below the option to
    select the desired attribute.
    Click the Edit button to create the classification (see "Displaying classified objects based on attribute values" on page
    2411). Via the check box in the Draw column you decide whether the turns of the particular class are to be drawn.
    Use layer order
    If the option has been selected, you can set up the order of drawing for the bars by class. The order is specified via the numbers in the Layer column. This column appears as soon as the
    option is checked. By default, the network objects of the
    various classes are drawn in the order as specified by the
    order of the classes in the list.

    12. Select the Circle display tab.


    13. Make the desired changes.
    Element

    Description

    Arrow display

    Draw arrows
    If the option has been selected, an arrow head is displayed outside of
    the circle, which indicates the direction.
    Arrow display like first bar
    The arrow heads use the color of the innermost bar.
    Apply individual arrow display
    You can specify a color for the arrow head in a separate window. To do
    so, click in the field (see "Editing the properties of a closed polygon" on
    page 2252).

    Circle display Draw circle


    If this option is checked, a circle is placed around each selected node.
    In the circles, the turns will be displayed.
    Simple filling

    2440

    PTVGROUP

    24.14.3 Displaying turn volumes


    Element

    Description
    If the option has been selected, all circles around the nodes are displayed with the color selected in the Color section. To edit the color
    and/or fill style, click in the field (see "Editing the properties of a closed
    polygon" on page 2252).
    Smooth color transition
    If the option has been selected, the circles around the nodes are displayed with a color gradient.
    Margin color

    Use the color field to specify the color at the margin of the circle.
    Center color

    Use the color field to specify the color at the center of the circle.
    Draw boundary

    If the option has been selected, the circles around the nodes are displayed with a boundary. You can specify the boundary style in a separate window. To do so, click in the field (see "Setting the line style
    properties" on page 2363).
    Standard
    radius

    Standard value for the radius of the circles around the nodes. The
    value is displayed in the Turn volumes window the next time you open
    it.

    Cut off the


    link bars at
    the circle

    If the option has been selected, link bars are not displayed within the
    turn volume circles.

    14. Confirm with OK.


    For turn volumes, the basic configuration has been set up. Now you have to define the bars
    and their individual display properties under Turns > Turn volumes > Display (see "Defining
    one or multiple bars" on page 2373 and "Setting the display properties of a bar" on page
    2374).

    24.14.3 Displaying turn volumes


    With the aid of turn volumes you can display attributes of turns and main turns at one or more
    nodes or main nodes.

    PTVGROUP

    2441

    24.14.3.1 Displaying turn volumes at single nodes

    Note: Information on the nodes and main nodes for which turn volumes are displayed
    and on graphic parameter settings are saved with the version and in the graphic parameters (see "Opening and saving a version file" on page 840 and "Printing the network
    display" on page 2499).
    You can also display turn volumes in the junction editor (see "Displaying turn volumes in
    the Junction editor" on page 1501).
    24.14.3.1 Displaying turn volumes at single nodes
    You can display turn volumes at individual nodes.
    1. Make sure the desired display options for turn volumes are set (see "Adjusting the basic settings for the display of turn volumes" on page 2437).
    2. Make sure that in the Overview window, in the Network tab, the Edit mode is selected (see
    "The operating modes of the network model" on page 996).
    3. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    4. Click a node.

    Notes: You cannot click passive nodes if the


    Click only active objects icon has
    been pressed on the toolbar.
    If you click a main node and the selected scaling attribute does not exist for main
    turns, a corresponding message is issued.
    The node is marked for the display of the turn volumes. The turn volumes via the node are
    displayed as bars according to your settings. If you have set the options accordingly, the
    turn volume display includes bars, a circle and labels.
    Note: If the node does not lie within the current window, the turn volumes are not displayed.
    5. Click another node.

    2442

    PTVGROUP

    24.14.3.2 Displaying the turn volumes of the visible nodes


    The node is marked for the display of the turn volumes. The turn volumes of the node are
    displayed.
    Note: At the currently marked node, at least the circle around the node is always displayed. At the previously marked nodes, only the display elements that you have chosen remain visible.
    6. If desired, click further nodes.
    The turn volumes of the marked nodes are displayed according to your chosen settings.
    Tips: The toolbar of the Turn volumes window always displays the number of the
    most recently marked node.
    You do not have to close the Turn volumes window in order to edit the graphic parameters. To open the graphic parameters immediately, click the Open graphic parameters button.
    7. Click the Close button.
    The Turn volumes window closes. The turn volumes are still displayed.
    Note: You can adjust the radius and the labels of turn volumes later on (see "Editing the
    display of turn volumes in the network window" on page 2445).
    You can hide individual turn volumes or all turn volumes simultaneously (see "Hiding
    turn volumes" on page 2444).
    24.14.3.2 Displaying the turn volumes of the visible nodes
    You can display the turn volumes of the nodes that are currently in view in the network window. You can either select all nodes or just the active nodes. Turn volumes of nodes which are
    not in view in the network window will still be displayed.
    1. Make sure the desired display options for turn volumes are set (see "Adjusting the basic settings for the display of turn volumes" on page 2437).
    2. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.

    PTVGROUP

    2443

    24.14.4 Hiding turn volumes

    3. Click the Switch on at all visible nodes or Switch on at all visible active nodes button.
    The turn volumes are displayed according to your chosen settings.
    Note: If the node does not lie within the current window, the turn volumes are not displayed.
    Tips: Alternatively, you can display the turn volumes of all visible nodes, if you rightclick in the network window and select either entry Switch on at all visible nodes or
    Switch on at all visible active nodes.
    You do not have to close the Turn volumes window in order to edit the graphic parameters. To open the graphic parameters immediately, click the Open graphic parameters button.
    4. Click the Close button.
    The Turn volumes window closes. The turn volumes are still displayed.
    Note: You can adjust the radius and the labels of turn volumes later on (see "Editing the
    display of turn volumes in the network window" on page 2445).
    You can hide individual turn volumes or all turn volumes simultaneously (see "Hiding
    turn volumes" on page 2444).

    24.14.4 Hiding turn volumes


    You can hide the turn volumes of nodes or main nodes.
    Hiding the turn volumes of a node
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2. Click a node with a turn volume display.
    The node is marked.
    2444

    PTVGROUP

    24.14.5 Editing the display of turn volumes in the network window


    3. Click the node again.
    The turn volumes at the node are no longer displayed.
    Tip: Alternatively, you can disable the turn volumes at a node if you click a node and
    then right-click in the network window and select the Disable turn volume entry. Or
    you can hold down the C TRL key and, at the same time, click a node.
    4. Click the Close button.
    Disabling all turn volumes
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2. Click the Switch off all button.
    The turn volumes are no longer displayed.
    Tip: Alternatively, you can disable the turn volumes of all nodes, if you right-click in
    the network window and select the Switch off all entry.
    3. Click the Close button.

    24.14.5 Editing the display of turn volumes in the network window


    You can edit the radius and the labels of turn volumes directly in the network window.
    24.14.5.1 Editing the radius of turn volumes
    You can edit the radius of one or of all turn volumes.
    Editing the radius of the turn volumes of a node
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2. Click the desired node.
    3. With the mouse, point at the turn volumes.
    A circle is displayed at the position of the mouse pointer.
    4. Click the mouse and hold down the mouse button.
    5. Drag the circle to the desired size.
    Tip: In the Turn volumes window, you can immediately see the length of the radius.
    6. Release the mouse button.
    The radius of the turn volumes is adjusted.

    PTVGROUP

    2445

    24.14.5.2 Hiding/Showing turn volume labels


    Tip: Alternatively, you can edit the radius, if, with the right mouse button, you click the
    node and select the Define radius entry in the context menu. Here you can enter the desired radius directly.
    Editing the radius of the turn volumes of all nodes
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2. In the Standard radius input field, enter the desired value.
    3. Click the Set radius for all button.
    The radius of the turn volumes is adjusted.
    24.14.5.2 Hiding/Showing turn volume labels
    For a selected turn volume display you can enable or disable the label display.
    Hiding/Showing all turn volume labels
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2. Hold down the SHIFT key and click in a turn volume circle.
    All texts of the turn volumes are displayed/hidden.
    Tip: Alternatively, you can click a node and then right-click in the network window and
    select the Switch on/off all texts entry.
    Hiding/Showing the text label of a turn volume display
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2. Click the desired node.
    3. Click the desired label.
    The text is displayed/hidden.

    24.14.6 Exporting turn volumes


    You can export one, all visible, all marked or all active turn volumes as graphics.
    Note: If you want to export only one or several selected turn volumes, you can mark the
    desired node(s) or main node(s) in the network display, select the Export turn volume
    entry in the context menu, and specify the settings in the Parameters: Multi-export of
    turn volumes window.
    1. In the Graphics menu, select the Turn volumes entry.
    The Turn volumes window opens.
    2446

    PTVGROUP

    24.14.6 Exporting turn volumes


    2. Click the Open export parameters button.
    The Parameters: Multi-export of turn volumes window opens.
    3. In the Size tab, make the desired changes.
    Element

    Description

    Parameters

    Here you can specify the proportions for the export. All changes are
    immediately visible in the preview.
    Width
    Enter the output width of the entire graphics in the desired unit
    Height
    Enter the output height of the entire graphics in the desired unit
    Margin
    Enter the width of the margin
    Circle size
    Enter the circle size in percent
    Note
    At 100%, the circle covers the entire space, at 0%, no circle is displayed. The display of the node legs covers the remaining share.
    Portrait / Landscape
    Select the export format of the turn volume

    Preview

    Graphic preview of the size and width-to-height ratio of the turn


    volume circle

    4. In the File names tab, make the desired changes.


    Note: In this tab, you can specify which names shall be generated automatically for
    the turn volume graphics. Prior to the export start, a warning will appear if an existing
    files could be replaced due to your settings.
    Element

    Description

    Prefix

    Here you can enter the first component of the file name.

    Variable name The middle part of the file name is variable. It consists either of a concomponent
    secutive number, a node attribute, or a header for the print frame.
    Consecutive number
    If this option has been selected, the graphics are numbered consecutively and you can enter a Start no., which shall be used for the
    next exported graphics. Moreover, you can set the number of Digits
    for the number. If necessary, zeros are inserted in front of the entered
    number (e.g. 01, 0022, ....). If the Increase start number for export

    PTVGROUP

    2447

    24.15 Showing/hiding extended markings


    Element

    Description
    option has been selected, the start number is increased automatically
    during the next export and existing data will not be overwritten.
    From node attribute
    If this option has been selected, you can select a node attribute which
    will be a component of the graphics name.
    Header for the print frame
    If this option has been selected, the header specified for the print
    name will be part of the name.
    Note
    The settings for the print frame are specified in the junction editor,
    under Junction Editor > Print frame (see "Specifying settings for the
    print frame of turn volumes" on page 1502).

    Suffix

    Here you can enter the final component of the file name.

    5. In the File tab, make the desired changes.


    Element

    Description

    File type

    Here you can select the file type of the graphics to be saved.

    Resolution

    Select the desired resolution.


    Note
    The default dpi value is the specified resolution or a multiple of the
    user's screen. The option is not provided, if you have selected the file
    type *.svg.

    Quality

    If you have selected the file type *.jpg, you can specify the desired quality for the exported graphics.

    6. Confirm with OK.


    7. If required, click the Export all switched on turn volumes or Export for all active nodes
    button.
    8. Click the Start the export button.
    The turn volumes are exported according to the settings.
    Tips: You can edit this path in the project directories file via Exported turn volumes.
    The junction editor also allows you to simultaneously export individual or multiple turn
    volumes (see "Displaying turn volumes in the Junction editor" on page 1501).

    24.15

    Showing/hiding extended markings


    In addition to the marked objects, in the network display, you can highlight the network objects
    that are network model-related to the marked object.

    2448

    PTVGROUP

    24.15.1 Highlighting related network objects permanently


    Note: The relations between network object types are listed in the Attribute.xls file, which
    is located in the Doc directory of your Visum installation (Relation tab) (see "Managing
    attributes" on page 958).
    The highlighting of the related network objects is called extended marking. It can be permanent or temporal.
    Note: To specify the colors and line styles for display of the selected objects and their
    related network objects, from the Graphics menu, choose Edit graphic parameters>
    Basis> Marking 1 or Marking 2 (see "Specifying basic settings" on page 2337).

    24.15.1 Highlighting related network objects permanently


    1. On the toolbar, in theNetwork editor window, click the
    button.

    Show/hide extended markings

    The icon is pressed and the related network objects are highlighted permanently.
    Tip: You can also activate the highlighting of the related network objects permanently
    via the menu Graphics> Extended markings.
    2. In the Network window, click the

    Edit mode icon.

    3. In the network, select the network objects of your choice (see "Marking network objects in
    the network" on page 1004).
    The network objects are marked. The related network objects are highlighted permanently yet
    not marked.

    The following table indicates which related network objects are highlighted if a specific network object is marked.
    Marked network object

    Related network objects that are highlighted

    Node

    All outgoing links

    Link

    From node and To node

    Turn

    From node, Via node, and To node

    Zone

    All origin connectors

    PTVGROUP

    2449

    24.15.2 Disabling the highlighting of the related network objects permanently


    Marked network object

    Related network objects that are highlighted

    Connector

    Zone centroid and connecting node

    Main node

    All partial nodes

    Main turn

    Not available

    Main zone

    All partial zones

    Territory

    POI

    All allocations

    GIS object

    Screenline

    All links intersecting the screenline

    Count location

    Link of the count location

    Detector

    Count location of the detector (optional)

    Toll system

    All allocated links

    Stop point

    Node or link the stop point refers to

    Stop area

    All stop points

    Stop

    All stop areas

    System route

    Start and end stop point

    Line

    All line routes

    Line route

    All traversed stop points

    24.15.2 Disabling the highlighting of the related network objects permanently


    On the toolbar in theNetwork editor window, click the
    markings.

    button Show/hide extended

    The highlighting of the related network objects is disabled permanently.


    Tip: You can also disable the highlighting of the related network objects permanently via
    the menu Graphics> Extended markings.

    24.15.3 Highlighting related network objects temporarily


    1. Make sure that in the View menu the Network entry has been selected.
    2. In the Network window, click the

    Edit mode icon.

    3. In the network, select the desired network objects (see "Marking network objects in the network" on page 1004).
    The network objects are marked.
    4. Hold down the SHIFT key.

    2450

    PTVGROUP

    24.16 Creating schematic line diagrams


    As long as the SHIFT key is pressed, the related network objects are highlighted yet not marked.

    Tip: If, in the toolbar of the Network editor window, the


    Show/hide extended markings icon is pressed, you can disable the highlighting of the related network objects temporarily by pressing the SHIFT key. Once you release the SHIFT key, the related network
    objects are highlighted again.

    24.16

    Creating schematic line diagrams


    Note: The schematic line diagram is only available after you have activated the Schematic line diagram add-on (see "Enabling or disabling installed add-ons" on page 886).
    Using the schematic line diagram, you can visualize your timetables, plan and optimize
    connections, and display volumes or transfer flows (see Fundamentals: Chpt. 12.13 , page
    770).
    If you want to create a new line network based on your network, take the following steps after
    opening the schematic line diagram window:
    1. Select the aggregation level you want to show (see "Selecting display level for displayed
    edges" on page 2452).
    2. Insert the desired stops as transfer nodes (see "Displaying individual stops as transfer
    nodes" on page 2452 and "Displaying active stops as transfer nodes" on page 2452).
    3. Create the desired vehicle journeys (see "Displaying vehicle journeys in the schematic line
    diagram" on page 2453).
    4. Edit the graphical display as required (see "Setting graphic parameters for the schematic
    line diagram" on page 2455).
    5. Post-edit the display as desired (see "Post-processing schematic line diagrams" on page
    2467).
    6. Make the layout settings (see "Setting the layout for schematic line diagrams" on page
    2475) and save them if required (see "Reading and saving the layout of schematic line diagrams" on page 2478).

    24.16.1 Opening schematic line diagrams


    This is how you open the window for creating a schematic line diagram.
    1. In the Edit menu, select the Schematic line diagram entry.
    The Schematic line diagram window opens.
    2. In the Schematic line diagram menu, make the desired changes.

    PTVGROUP

    2451

    24.16.2 Selecting display level for displayed edges


    Note: You can open any number of line diagram windows and set different graphic parameters for the schematic line diagrams.
    Visum memorizes the graphic parameters and layout settings for the duration of the session. If you close the Schematic line diagram window, you can use these settings again
    when you reopen it.

    24.16.2 Selecting display level for displayed edges


    Via the aggregation level you can specify in which form the edges between the transfer nodes
    are displayed in the line diagram. An edge groups all spatial sections of vehicle journeys between successive transfer nodes or within a transfer node, which belong to the same transport
    system, operator, line etc. (see Fundamentals: Chpt. 12.13.2 , page 771).
    1. In the Schematic line diagram menu, select the Layout parameters entry.
    The Layout parameters for schematic line diagram window opens.
    2. Select the General tab.
    3. In the Aggregation level list, click the desired level (see "Setting the layout for schematic
    line diagrams" on page 2475).
    4. Confirm with OK.
    The edges are displayed in the desired aggregation level.

    24.16.3 Displaying stops in the schematic line diagram


    You can select individual stops for display or display all active stops. In the schematic line diagram you can visualize the transfer nodes. They are arranged automatically based on the geographical position of the stops in the network. You can adjust the position of the transfer nodes
    in the schematic line diagram later on (see "Manually editing schematic line diagrams" on
    page 2467).
    24.16.3.1 Displaying individual stops as transfer nodes
    You can select individual stops for display in the schematic line diagram.
    1. On the toolbar, click the

    icon.

    Tip: Alternatively, in the Schematic line diagram menu, you can select the Create
    stop as transfer node entry.
    The Find stop window opens. It displays all stops that are not display in the schematic line
    diagram yet.
    2. Select the desired stop for display.
    3. Confirm with Close.
    The selected stop is displayed as transfer node in the schematic line diagram.
    24.16.3.2 Displaying active stops as transfer nodes
    You can display all active stops in the schematic line diagram.
    2452

    PTVGROUP

    24.16.4 Displaying vehicle journeys in the schematic line diagram


    1. Set the desired stops to active (see "Setting stops active/passive" on page 1242).
    2. On the toolbar, click the

    icon.

    Tip: Alternatively, in the Schematic line diagram menu, you can select the Create all
    active stops entry.
    A query opens.
    3. Confirm with OK.
    All active stops are displayed as transfer nodes in the schematic line diagram.

    24.16.4 Displaying vehicle journeys in the schematic line diagram


    You can select the vehicle journeys that you want to display in the schematic line diagram as
    follows.
    1. On the toolbar, click the

    icon.

    Tip: Alternatively, from the Schematic line diagram menu, select the Edit vehicle journey selection entry.
    The Vehicle journey selection window opens. The window lists all lines, time profiles and
    vehicle journeys that exist in the network.
    Notes: Click the plus sign to display subordinate elements.
    2. Select the lines, line routes, time profiles and directions whose vehicle journeys you want to
    display in the schematic line diagram.
    Element

    Description
    Show or hide, so that only active lines are shown in the navigator (see
    "Using filters to set network objects active or passive" on page 1008 and "Setting network objects active/passive via the spatial selection" on page 1033)..
    Right-click the icon to open the filter editing window for lines.
    Note
    The function is activated if the icon is pressed (red).
    All stops served by marked vehicle journeys will be displayed as transfer
    nodes
    Note
    The icon is only available, if at least one vehicle journey is marked.
    Display start and end stops of marked vehicle journeys as transfer nodes
    Note

    PTVGROUP

    2453

    24.16.4 Displaying vehicle journeys in the schematic line diagram


    Element

    Description
    The icon is only available, if at least one vehicle journey is marked.
    Display vehicle journeys of a specific time slot
    Note
    The icon opens a new window. Here you can specify a time slot and filter
    conditions. Vehicle journeys that comply with the filter conditions can be
    selected, deselected or exclusively selected.
    Valid day
    Select the valid day
    Start time/End time
    Enter a start time and an end time for the time slot
    Filter condition
    Here you can pick one of the following conditions:
    Vehicle journeys which depart from their start stop points within the
    given time slot
    Vehicle journeys which are running within the given time slot
    Vehicle journeys which satisfy the filter conditions
    Here you can specify, if the vehicle journeys that meet the filter criteria will be
    displayed.
    Select

    If the option is selected, the vehicle journeys that comply with the filter conditions will be selected in addition to the already selected vehicle journeys.
    Deselect

    If the option is selected, the vehicle journeys that comply with the filter conditions will be removed from the selection.
    Select exclusively

    If the option is selected, only the vehicle journeys that comply with the filter
    conditions will be selected. All others will be removed from the selection.
    Keep selected, uncheck all other vehicle journeys

    If this option is selected, the selected vehicle journeys remain selected. All
    vehicle journeys that do not comply with the filter conditions will be removed
    from the selection.
    Select all vehicle journeys that exist in the network
    Select no vehicle journeys
    Invert the current selection
    3. Confirm with OK.
    The selected vehicle journeys are displayed in the schematic line diagram.

    2454

    PTVGROUP

    24.16.5 Setting graphic parameters for the schematic line diagram

    24.16.5 Setting graphic parameters for the schematic line diagram


    Similar to the network display, you can specify graphic parameters for the schematic line diagram according to your wishes.
    Note: You can save your graphic parameter settings for the schematic line diagram in a
    graphic parameters file. In addition, you can save a layout file with a selection of transfer
    nodes and vehicle journeys, including their positions and courses, in the line diagram
    (see "Reading and saving the layout of schematic line diagrams" on page 2478).
    24.16.5.1 Showing help grids
    As an option, you can specify the display of a help grid.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Help grid page.

    3. Make the desired changes.

    PTVGROUP

    2455

    24.16.5.2 Setting the display of transfer nodes


    Element

    Description

    Help grid

    Here you can specify the settings for the help grid.
    Draw axes
    If the option has been selected, axes are drawn.
    Draw grid points
    If the option has been selected, grid points are displayed. You can specify the following settings for the grid points.
    Point size

    Screen dots in mm
    Color

    Use the drop-down list to select a color for the grid.


    Draw grid lines
    If the option has been selected, grid lines are displayed. You can specify the following settings for the grid lines.
    Distance

    Distance between the grid lines in raster units


    Line style

    Here you can specify the grid lines style (see "Setting the line style properties" on page 2363).
    4. Confirm with OK.
    The settings are applied.
    24.16.5.2 Setting the display of transfer nodes
    In the schematic line diagram, transfer nodes represent the stops of the network (see Fundamentals: Chpt. 12.13.1 , page 770). The size of the transfer nodes is based on the number
    of vehicle journeys operating at the stop. They are positioned automatically. You can edit the
    display of transfer nodes as follows.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Transfer nodes entry.

    2456

    PTVGROUP

    24.16.5.2 Setting the display of transfer nodes

    3. Make the desired changes.

    PTVGROUP

    2457

    24.16.5.2 Setting the display of transfer nodes


    Element

    Description

    Uniform display

    If the option has been selected, all transfer nodes are displayed uniformly. You can specify the following settings for transfer nodes in the
    lower part of the window.
    Draw object
    If the option has been selected, transfer nodes are displayed.
    Round corners
    If the option has been selected, transfer nodes are displayed with rounded corners.
    Node display
    A new window opens if you click the field. Here you can specify the settings for the File style and the Boundary of the display.
    Text color
    Use the drop-down list to select a color for the text.
    Draw text frame
    If the option has been selected, frames will be drawn around the
    labels of the transfer nodes. A new window opens if you click the field.
    Here you can specify the settings for the Fill style and the Boundary
    of the text frame.
    Preview
    Preview of the modified display of the transfer nodes and text frames

    Table

    In the table section, you can select up to three attributes as labels for
    the transfer nodes. The three labels are displayed centered one below
    the other.
    Notes
    If you want to display just one attribute, select No label in the other
    rows.
    In the table, you can specify further settings for the display of the label,
    if required, by clicking or double-clicking the respective cells.

    Classified dis- If the option is selected, different classes of transfer nodes are display
    played (see "Displaying classified objects based on attribute values"
    on page 2411).
    Use the button to select an attribute by which you want to classify the
    display.
    Use the toolbar to insert the desired classes and attributes (see "Creating and deleting an individual class" on page 2422 and "Editing the
    display settings and class limits of a class" on page 2423). In the table,
    you can specify the desired settings for the classes.
    4. If required, in the same way, edit the settings for marked Transfer nodes in the Marked tab.
    5. Confirm with OK.

    2458

    PTVGROUP

    24.16.5.3 Setting the display of edge courses


    The transfer nodes are displayed according to your chosen settings.
    24.16.5.3 Setting the display of edge courses
    In the schematic line diagram, an edge course represents a set of vehicle journeys (see Fundamentals: Chpt. 12.13.2 , page 771). Edge courses can be drawn both outside and inside of
    transfer nodes.
    Note: To visualize the edge items within transfer nodes, you have to select a transparent
    fill color for the transfer nodes (see "Setting the display of transfer nodes" on page 2456).
    Setting the display of edge courses
    You can set the display of the edge courses as follows.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Edge courses entry.
    3. Make the desired changes.

    PTVGROUP

    2459

    24.16.5.3 Setting the display of edge courses


    Element

    Description

    Uniform display

    If the option has been selected, all edge courses are displayed uniformly.
    In the Display section, you can specify the following settings for the display:
    Draw
    If the option has been selected, edge courses are displayed.
    Frequency
    The frequency of service is an integer value between 1 and 4. It indicates the number of lines drawn for each edge course. The lines are
    drawn in parallel.
    Use the drop-down list to select the desired value.
    Edge course
    A new window opens if you click the field. Here you can specify the
    line style used to draw the edge courses (see "Setting parameters for
    the line style" on page 2365).
    Arrow head
    If the option has been selected, an arrow head is drawn. A new window opens if you click the field. In this window you can specify how the
    arrow head will be drawn.
    Note
    An arrow head will only be drawn for the outward direction. If both
    directions are displayed in one edge course, no arrow head will be
    drawn.
    Centered label
    If the option has been selected, a label is drawn in the middle of the
    item.
    Click into the field to open the window Graphic parameters: Edit text
    in which you can make additional settings (see "Setting the display of
    edge courses" on page 2459).
    Centered label by direction
    If the option has been selected, a centered label by direction, i.e. one
    label per direction, will be drawn.
    Click into the field to open the window Graphic parameters: Edit text
    in which you can make additional settings (see "Labeling forms for
    edge courses" on page 2462).
    Start label
    Select this option to draw the beginning of a label.
    It is drawn at the beginning of an edge course to the right of the edge.
    Click into the field to open the window Graphic parameters: Edit text

    2460

    PTVGROUP

    24.16.5.3 Setting the display of edge courses


    Element

    Description
    in which you can make additional settings (see "Labeling forms for
    edge courses" on page 2462).
    End label
    Select this option to draw the end of a label.
    It is drawn at the end of an edge course, to the right of the edge.
    Click into the field to open the window Graphic parameters: Edit text
    in which you can make additional settings (see "Labeling forms for
    edge courses" on page 2462).
    End node label
    If the option has been selected, a label is drawn within the end node.
    A new window opens if you click the field.
    Click into the field to open the window Graphic parameters: Edit text
    in which you can make additional settings (see "Labeling forms for
    edge courses" on page 2462).
    Notes
    A transfer node is the end node of an edge course if the edge begins
    or ends at the node. The edge begins or ends if there is no other edge
    at the transfer node on which the vehicle journey can continue.
    The labels of the edge courses are only displayed at the outer edge
    courses, i.e. not inside of transfer nodes. The label is drawn only if at
    least one of the two transfer nodes of an edge course is drawn.
    If you have selected the Uniform display option, you can still classify
    the display of the edge courses in the lower part of the window using
    the Classified display option.
    In the same way, you can specify settings for marked edge courses in
    the Marked tab.

    Classified dis- If the option is selected, different classes of edge courses are display
    played (see "Displaying classified objects based on attribute values"
    on page 2411)..
    Use the button to select an edge course attribute by which you want to
    classify the display.
    Use the toolbar to insert the desired classes and attributes (see "Creating and deleting an individual class" on page 2422 and "Editing the
    display settings and class limits of a class" on page 2423). In the table,
    you can specify the desired settings for the classes.
    Note
    Within the edit window of the individual classes, you can further classify, e.g. to combine the display of the frequency of service with the
    standard colors for specific lines.
    4. Confirm with OK.

    PTVGROUP

    2461

    24.16.5.3 Setting the display of edge courses


    The edge courses are displayed according to your settings.
    Labeling forms for edge courses
    You can use labeling forms to set how you want to display the text of edge courses.
    1. In the window Edit graphic parameters: Schematic line diagram, in the navigator, select
    Edge courses> Labeling forms.
    The default labeling forms are displayed in a table. By default, all display attributes are
    shown.
    Default
    Note
    This is the only labeling form that cannot be deleted. This default labeling is restored
    after user-defined labeling forms are deleted.
    Default center label
    Default center label by direction
    Default start label
    Default end label
    Default end node label
    2. Make the desired settings.
    Element Description
    Adds a new labeling form with the Default settings.
    Duplicates one or multiple label forms selected
    Deletes the labeling form selected
    Opens the Attribute selection window in which you can specify the attributes
    you want to show as table columns (see "The window used for the selection of
    multiple attributes" on page 968).
    Restores the default settings for the attributes listed in the table as columns.
    Preview Preview of selected settings for labeling form

    2462

    Draw
    object

    Select this option to show the labeling in the schematic line diagram.

    Name

    Name of labeling type

    Font

    Font for labeling in schematic line diagram

    Size

    Relative font size for labeling in schematic line diagram

    Line
    text
    color

    Select this option to adopt the text color for labeling from the corresponding line.

    Text

    A new window opens if you click the field. Here you can select a text color.

    PTVGROUP

    24.16.5.3 Setting the display of edge courses


    color
    Draw
    frame

    Select this option to draw a frame around the text.

    Frame

    A new window opens if you click the field. Here you can specify the settings for
    the Fill style and the Boundary of the text frame.

    Line
    frame
    color

    Select this option to adopt the color for the frame from the corresponding line.

    3. Confirm with OK.


    The edge courses are labeled according to your settings.
    Setting labeling variants for departure and arrival times
    Labeling variants apply a labeling format to text format. They take effect when attributes are displayed that represent the arrival and departure times that take place every 2 and 15 minutes.
    There are 4 labeling variants whose values can be edited.
    Arrival and departure times (even hour): not in italics, not in bold, no prefix.
    Arrival and departure times (uneven hour): in italics, not in bold, no prefix.
    Arrival and departure times (second hour): not in italics, bold, no prefix.
    Arrival and departure times (third hour): in italics, bold, no prefix.
    Note: Labeling variants are only relevant for labeling 2 or 4 hour service frequencies.
    The respective attribute for labeling must be selected.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, click Edge courses> Labeling variants.
    The labeling variants are displayed in a table.
    3. Make the desired settings.
    Element Description
    Preview Preview of settings selected for labeling variant
    Name

    Name of labeling variant

    Prefix

    Prefix preceding the attribute value. You may add an additional character to
    improve visibility.

    Italic

    Font is shown in italics

    Bold

    Select this option to adopt the text color for labeling from the corresponding line.

    4. Confirm with OK.


    The edge courses are labeled according to your settings.

    PTVGROUP

    2463

    24.16.5.4 Setting graphics parameters for the label of the edge courses
    24.16.5.4 Setting graphics parameters for the label of the edge courses
    You can set different label forms for each label element when labeling the edge courses (see
    "Labeling forms for edge courses" on page 2462).
    Set label forms for classified display
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters: Schematic line diagram window opens.
    2. In the window Edit graphic parameters: Schematic line diagram, select Edge courses in
    the navigator.
    3. Select the desired class and click the button

    The Edit the graphic parameters of class <number> window opens.


    4. In the Display area click on the field behind the desired label type Centered label, Centered label by direction, Start label, End label or End node label.
    The Edit graphic parameters window opens.
    5. Make the desired changes.

    2464

    Element

    Description

    Content

    A new window opens if you click the field. In this window, you can select an attribute for the label.
    Note
    You can use Labeling variants for the label forms Start label and End label in
    the classes 2-hour intervals and 4 hour interval. Depending on the regular service, you can use the following attributes to display in a different manner the
    arrival and departure times that fall in even hours (2.32 p.m., 4.51 p.m., 6.20
    p.m.) or odd hours (1.42 p.m., 3.33 p.m., 5.22 p.m.).
    You can select the following attributes:
    Departure times two-hourly
    Arrival times two-hourly
    Departure times four-hourly
    Arrival times four-hourly
    Most frequent two-hourly departure times
    Most frequent two-hourly arrival times
    Most frequent four-hourly departure times
    Most frequent four-hourly arrival times

    Labeling
    type

    Select one of the defined label forms from the list (see "Setting the display of
    edge courses" on page 2459)

    PTVGROUP

    24.16.5.5 Setting the display properties of edge course bars


    Align label If this option is selected, the label forms are aligned parallel to the labeled
    along edge edge.
    course
    Always
    If this option is selected, the label form is always aligned horizontally regardalign label less of the edge course.
    horizontally
    6. Confirm with OK.
    The edge courses are displayed according to your settings.
    Set label forms for uniform display
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters: Schematic line diagram window opens.
    2. In the window Edit graphic parameters: Schematic line diagram, select Edge courses in
    the navigator.
    3. In the Display area click on the field behind the desired label type Centered label, Centered label by direction, Start label, End label or End node label.
    The Edit graphic parameters window opens.
    4. Make the desired settings as for the classified display.
    5. Confirm with OK.
    The edge courses are displayed according to your settings.
    24.16.5.5 Setting the display properties of edge course bars
    Along the edge courses, you can display different properties as bars.
    Note: Because of the hidden intermediate stops, volumes are usually different when
    departing at the first transfer node and when arriving at the second transfer node. In this
    case, different bars are drawn before and past the centered label.
    You can specify the display of the edge course bars as follows.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Edge course bars entry.
    3. Make the desired changes.
    Note: The settings for edge course bars are mostly the same as for line objects (see
    "Displaying properties via bars" on page 2367)..
    4. Confirm with OK.

    PTVGROUP

    2465

    24.16.5.6 Setting the display properties of transfer bars


    The edge course bars are displayed according to your settings.
    24.16.5.6 Setting the display properties of transfer bars
    Within the transfer nodes you can display the transfer flows between the ingoing and outgoing
    edge courses as bars. The transfer bars are displayed between the slots of the transfer nodes.
    You can specify the display of the transfer bars as follows.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Transfers bar page.
    3. Make the desired changes.
    Note: The settings for transfer bars are mostly the same as for line objects (see "Displaying properties via bars" on page 2367).
    4. Confirm with OK.
    The transfer bars are displayed according to your settings.
    24.16.5.7 Setting the display properties for branches
    You can display branches for coupled vehicle journeys in the schematic line diagram. You can
    specify the display of the branches as follows.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Branches entry.
    3. Make the desired changes.
    Element

    Description

    Draw: Branches

    If this option has been selected, branches are displayed.

    Draw branIf the option has been selected in addition to the above option, branches only
    ches will only be drawn if the branch is either start or end of a coupling
    where the
    section of at least one underlying vehicle journey.
    coupling section either
    starts or ends
    Symbol

    2466

    In the drop-down list, you can select a symbol for the branch display.
    Size
    Symbol size in raster units
    Color
    Use the drop-down list to select a color for the symbol (see "Editing the

    PTVGROUP

    24.16.5.8 Setting the display properties of the print frame


    Element

    Description
    properties of a closed polygon" on page 2252).
    Sign
    If you select the Circle or Square symbol, you can activate the input
    field by checking the box. In the input field, you can enter a sign which
    will be displayed inside the circle or square. Use the drop-down list to
    select a color for the sign.

    4. Confirm with OK.


    The branches are displayed according to your settings.
    24.16.5.8 Setting the display properties of the print frame
    You can specify the following settings for the print frame.
    1. In the Schematic line diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Print frame page.
    3. Make the desired settings (see "Setting the print frame" on page 2504).
    4. Confirm with OK.
    The settings are applied.
    24.16.5.9 Creating legend for the schematic line diagram
    You can create a legend with additional explanations and descriptions of objects.
    1. Click the

    Legend button in the toolbar of the schematic line diagram.

    The Legend parameters window opens.


    2. Make the desired settings (see "Creating legends" on page 2255).
    3. Confirm with OK.
    The settings are applied.

    24.16.6 Post-processing schematic line diagrams


    You can edit the automatic layout of the items of the schematic line diagram.
    24.16.6.1 Manually editing schematic line diagrams
    You can select and directly edit transfer nodes, edge courses, and access points of vehicle
    journeys in the schematic line diagram. You can post-process the diagram as follows:
    Creating transfer nodes as intermediate stops
    Shifting a transfer node
    Enlarging a transfer node
    Reducing a transfer node to its minimum size
    Placing transfer nodes to adjacent nodes as in network
    PTVGROUP

    2467

    24.16.6.1 Manually editing schematic line diagrams


    Rearranging edge courses and slots at nodes
    Deleting a transfer node
    Repositioning the slots of vehicle journeys
    Bundling edges
    Editing the courses of edges
    Separating edges
    Deleting vehicle journeys from the display
    Note: You can center the display of a desired transfer node or vehicle journey using the
    Find transfer node or Find vehicle journey function in the Schematic line diagram
    menu.
    Creating transfer nodes as intermediate stops
    You can create hidden transfer nodes as intermediate stops on an edge course. Bundled
    edges generally are not separated in this case. A separation would be necessary, for example, if a part of the bundled vehicle journeys does not call at the new transfer node.
    1. Select the desired edge course.
    2. Right-click the selected edge course.
    A context menu opens.
    3. Select the Create intermediate stops entry.
    Note: The entry Create intermediate stops is active only if there are hidden transfer
    nodes on the selected edge course.
    The Create intermediate stops window opens.
    4. If required, select the option Show only those stops where boarding or alighting is permitted to restrict the number of displayed transfer nodes.
    5. Select the desired transfer node in the column Create transfer node in the list of possible
    transfer nodes.
    6. Confirm with OK.
    The transfer nodes are displayed as intermediate stops.
    Shifting a transfer node
    You can shift transfer nodes in the display as follows.
    1. Click the desired transfer node and hold down the mouse button.
    2. Drag the transfer node to the desired position.
    The transfer node is shifted to the new position. The edge courses are automatically adjusted.

    2468

    PTVGROUP

    24.16.6.1 Manually editing schematic line diagrams


    Notes: You can shift several transfer nodes at the same time, if you hold down the C TRL
    key while marking the transfer nodes.
    If you hold down the SHIFT key while shifting the transfer nodes, depending on the shifting direction, all transfer nodes to the left or to the right, respectively, and those located
    on the same coordinate will also be shifted. This way, the distances between the transfer
    nodes are retained.
    Enlarging a transfer node
    You can enlarge the transfer node as follows.
    1. Click a corner of the desired transfer node and hold down the mouse button.
    2. Drag the corner until the transfer node has reached the desired size.
    The transfer node is enlarged.
    Reducing a transfer node to its minimum size
    You can minimize a transfer node as follows. The size of the transfer node is then reduced in
    such a way that all access points of vehicle journeys can still be displayed.
    1. Right-click the desired transfer node.
    A shortcut menu opens.
    2. Select the Minimum size entry.
    The transfer node is minimized.
    Note: You can minimize several transfer nodes at the same time, if you hold down the
    CTRL key while marking the transfer nodes.
    Placing transfer nodes to adjacent nodes as in network
    You can place a transfer node relative to its adjacent nodes in the network if the transfer node
    has at least two adjacent nodes.
    1. Right-click the desired transfer node.
    A shortcut menu opens.
    2. Select the Compared to next node(s), place as in network entry.
    The transfer node is positioned in the network relative to its adjacent nodes.
    Rearranging edge courses and slots at nodes
    You can optimize the positions of edge courses and slots at the transfer nodes, for example
    after having moved a transfer node.
    1. Right-click the desired transfer node.
    A shortcut menu opens.
    2. Select the Rearrange edge courses and slots at nodes entry.
    The edges and slots are rearranged at the marked node.

    PTVGROUP

    2469

    24.16.6.1 Manually editing schematic line diagrams

    Note: You can rearrange the slots and edges of several transfer nodes simultaneously if
    you keep the C TRL key pressed when marking the transfer nodes.
    Deleting a transfer node
    You can delete transfer nodes in the display as follows.
    1. Right-click the desired transfer node.
    A shortcut menu opens.
    2. Select the Delete entry.
    The transfer node is deleted.
    Note: You can delete several transfer nodes at the same time, if you hold down the C TRL
    key while marking the transfer nodes.
    Repositioning the slots of vehicle journeys
    You can reposition the slots of vehicle journeys as follows.
    1. Click the desired access point of a transfer node of a vehicle journey.
    The access point is displayed as a square of the size of a screen dot.
    2. Click the square and hold down the mouse button.
    3. Drag the square to the desired position.
    Note: You can shift the square exclusively along the frame of the marked transfer
    node.
    The new position is indicated by a square.
    Note: You can shift several access points of a transfer node at the same time, if you
    hold down the C TRL key while marking the access points.
    4. Release the mouse button.
    The access point is moved to its new position.
    Note: If an access point is shifted to a different access point, the edges remain separate
    and the access points are shifted. If you hold down the SHIFT key, the corresponding
    edges are bundled.
    Bundling edges
    If an access point is shifted to the position of another access point, the associated edges are
    merged, if they have the same start and end transfer nodes.
    1. Click the desired access point of a transfer node of a vehicle journey.
    The access point is displayed as a square of the size of a screen dot.
    2470

    PTVGROUP

    24.16.6.1 Manually editing schematic line diagrams


    2. Drag the square to the position of the access point whose edges you want to merge with
    the edges of the selected access point.
    The edges are merged.
    Editing the courses of edges
    You can edit the course of an edge as follows.
    1. Right-click the edge course that you want to edit.
    A context menu opens.
    2. Select the Edit shape entry.
    Small squares are displayed on the selected edge course. You select the points at which
    the edge course can be changed.
    3. On the edge, click the point that you want to shift and hold down the mouse button.
    4. Drag the point to the new position.
    5. If required, drag further points to new positions.
    6. Delete existing points, if required, by pressing the C TRL key and clicking the polygon point.
    7. Insert further points, if required, by pressing the C TRL key and clicking the edge.
    8. Press the ENTER key.
    The course of the edge is changed.
    Notes: The edge courses are always aligned with the grid points, and thus add additional
    points if necessary and adjust the edge course accordingly (see "Showing help grids" on
    page 2455).
    If you change an edge course within a transfer node, note that you cannot shift the intermediate points outside of the transfer node. If you realign the edge courses with a transfer node (see "Rearranging edge courses and slots at nodes" on page 2469) all edge
    courses are also realigned within the transfer node and the intermediate points are omitted within the transfer node.
    If you shift the transfer node, the intermediate points remain in the node.
    Notes: If you change the size of the transfer node, all intermediate points that are then outside the node are deleted.
    Separating edges
    If several edges belong to an edge course, they can be separated.
    1. Right-click the desired edge course in the display.
    A context menu opens.
    2. Select the Separate edges entry.
    The edges of the edge course are separated.

    PTVGROUP

    2471

    24.16.6.2 Separating all edges


    Tip: Alternatively, you can separate all edges of all edge courses (see "Separating all
    edges" on page 2472).
    Deleting vehicle journeys from the display
    You can remove vehicle journeys from the display as follows.
    1. Right-click the desired edge.
    A context menu opens.
    2. Select the Delete vehicle journeys from the selection entry.
    All vehicle journeys associated with the edge will be deleted from the vehicle journey selection.
    24.16.6.2 Separating all edges
    If several edges belong to an edge course, they can be separated. In this case, for all contained edges (but one), further courses will be created parallel to the existing edge course.
    In the Schematic line diagram menu, select the Separate all edges entry.
    The edges are separated.
    Tip: Alternatively, you can separate edges individually (see "Separating edges" on page
    2471).
    24.16.6.3 Bundling edges according to conditions
    Visum provides various conditions according to which you may bundle edges.
    Bundling all coupled edges
    For all edges, coupling partners can be bundled. In this case, for the edges between each pair
    of transfer nodes, the program checks if one of the vehicle journeys of one edge has a coupling partner in another edge to bundle those edges.
    From the Schematic line diagram menu, choose Bundle edges> Bundle all coupled
    edges.
    The edges are grouped.
    Bundling selected coupled edges
    1. Select the edge courses you want to group to edges.
    2. Right-click one of the edge courses selected.
    A shortcut menu opens.
    3. Click Group edges with conditions> Bundle coupled edges.
    The edges are grouped.
    Bundling all edges by regular service patterns
    All edges for which the vehicle journeys form a common service trip pattern can be bundled.

    2472

    PTVGROUP

    24.16.6.3 Bundling edges according to conditions


    1. From the Schematic line diagram menu, choose Bundle edges> Bundle all edges by
    regular service patterns.
    The Bundle edges by regular service pattern window opens.
    2. Make the desired changes.
    Element

    Description

    Bundle only edges with vehicle journey sections running in the same
    direction

    If this option is selected, only those edges are


    bundled whose vehicle journeys operate in the
    same direction.

    Only bundle edges whose vehicle


    journeys have the same total run
    time between the from and to transfer node

    If this option is selected, only those edges are


    bundled whose vehicle journeys have the same
    vehicle time between transfer nodes.

    Only bundle edges whose vehicle


    journeys serve the same intermediate stops

    If this option is selected, only those edges are


    bundled whose vehicle journeys serve the same
    intermediate stops.

    Identifying service trip patterns with


    any service interval

    Select this option to group vehicle journeys with


    the same differences into service trip patterns.
    The time differences may differ between trip patterns.

    Only fractured multiples of the base


    headway are permitted as service
    intervals for a service trip pattern

    Select this option to specify a base headway that


    limits the service trip patterns possible (see "Calculate service trip patterns" on page 2086).

    3. Confirm with OK.


    The edges are merged.
    Bundling marked edges by regular service patterns
    1. Select the edge courses you want to group to edges.
    2. Right-click one of the edge courses selected.
    A context menu opens.
    3. Select Group edges with conditions> Bundle edges by regular service pattern.
    The Bundle edges by regular service pattern window opens.
    4. Make the desired settings (see "Bundling all edges by regular service patterns" on page
    2472).
    5. Confirm with OK.
    The edges are merged.

    PTVGROUP

    2473

    24.16.6.4 Deleting unused edge courses


    Bundling all edges with the same attribute value
    You can define an attribute by which the vehicle journeys of the edges are compared. The
    edges are bundled with the same attribute value.
    1. From the Schematic line diagram menu, choose Bundle edges> Bundle all edges by
    attribute.
    The Bundle edges by attribute window opens.
    2. Make the desired changes.
    Element

    Description

    Attribute

    You can use the button to select an attribute according to which the vehicle journeys of the edges are
    compared

    Bundle only edges with vehicle jour- If this option is selected, only those edges are bundney sections running in the same
    led whose vehicle journeys operate in the same
    direction
    direction.
    3. Confirm with OK.
    The edges are merged.
    Bundling marked edges with the same attribute value
    1. Select the edge courses you want to group to edges.
    2. Right-click one of the edge courses selected.
    A context menu opens.
    3. Select the entry Group edges with conditions> Bundle edges by attribute.
    4. Make the desired settings (see "Bundling all edges with the same attribute value" on page
    2474).
    5. Confirm with OK.
    The edges are merged.
    24.16.6.4 Deleting unused edge courses
    Edge courses that are not used by any edges are not automatically deleted, as they can be
    reused if required. You can, however, delete edge courses that are not used as follows.
    In the Schematic line diagram menu, select the Delete unused edge courses entry.
    The edge courses are deleted.

    24.16.7 Synchronizing the schematic line diagram with other windows


    You can synchronize the schematic line diagram with other windows. The setting applies to
    the network window, the quick view, stop lists and open transfers displays of regular services.
    Note: This synchronization only works, if you activate the synchronization in all windows.
    2474

    PTVGROUP

    24.16.8 Setting the layout for schematic line diagrams


    If the windows are synchronized, you can mark one or several objects in one window, which
    will automatically be marked in the other window as well. Depending on the setting, in the network window the displayed section is automatically shifted or zoomed in.
    1. Make sure the Schematic line diagram window is open (see "Opening schematic line diagrams" on page 2451).
    2. In the Schematic line diagram window open the Synchronization with network editor
    entry.
    3. Select the desired entry.
    Element

    Description

    No synchronization

    The display is not synchronized with other windows.

    Mark object(s)

    The objects highlighted in the display are also highlighted in the


    other windows and vice versa.

    Mark and shift


    view

    The objects highlighted in the display are also highlighted in the


    other windows and vice versa. If required, the network section of
    the network window is shifted in such a way that all marked
    objects are visible.
    Note
    This does not affect the scale of the network editor.

    Mark and autozoom

    The objects highlighted in the display are also highlighted in the


    other windows and vice versa. Additionally, in the network an
    auto zoom is carried out for the marked objects.

    The settings are applied.

    24.16.8 Setting the layout for schematic line diagrams


    You can specify settings for the layout of a schematic line diagram. You can save the layout
    parameters to a separate layout file *.xml (see "Reading and saving the layout of schematic
    line diagrams" on page 2478) and apply the settings to other timetables (see Fundamentals:
    Chpt. 12.13.4 , page 772). Additionally you can specify the stops to which the edges are
    connected and limit the display of the edges to a time slot.
    1. Make sure the Schematic line diagram window is open (see "Opening schematic line diagrams" on page 2451).
    2. On the toolbar, click the

    icon.

    Tip: Alternatively, from the Schematic line diagram menu, select the Layout parameters... entry.
    The Layout parameters for schematic line diagram window opens.
    3. Select the General tab.
    PTVGROUP

    2475

    24.16.8 Setting the layout for schematic line diagrams


    4. Make the desired changes.
    Element

    Description

    Name

    Enter a name for the layout

    Aggregation level Here you can select the desired level of aggregation.
    Note
    An edge groups all spatial sections of vehicle journeys between
    successive transfer nodes or within a transfer node, which belong
    to the same transport system, operator, line etc. A set of edges is
    determined by the number of transfer nodes, the vehicle journey
    selection, and the aggregation level selected (see Fundamentals:
    Chpt. 12.13.2 , page 771).
    Select one of the following levels:
    Transport system directed / undirected
    Operator directed / undirected
    Main line directed / undirected
    Line directed / undirected
    Line route
    Time profile
    Vehicle journey
    Service trip pattern number

    Identification attri- Here you can select an identification attribute to allocated the
    bute for unused
    vehicle journeys to the edge courses.
    edge courses
    Notes
    The selection depends on the specified aggregation level. The
    selected attribute is saved to the layout file*.xml.
    When editing the timetable data or the layout parameters, vehicle
    journeys will be reallocated to the edge courses on the basis of
    this attribute. Your layout parameters for hidden edge courses will
    not be lost (see Fundamentals: Chpt. 12.13.4 , page 772). You
    can use the layout of a timetable for further timetables.
    Vehicle journey
    identification attribute for vehicle
    journey selection

    Here you can select an identification attribute for vehicle journeys. The vehicle journeys selected for display will be saved to
    the layout file *.xml with this attribute. Select one of the following
    attributes:
    Vehicle journey: Number
    Vehicle journey: Name

    Extend vehicle
    journeys virtually
    to the entire time
    profiles

    2476

    If the option has been selected, vehicle journeys will be virtually


    extended to the entire time profile.
    Note
    Vehicle journeys will then be treated as if they would reach from
    the first to the last time profile item, their actual spatial extent will
    thus be ignored.

    PTVGROUP

    24.16.8 Setting the layout for schematic line diagrams


    5. Select the Connection of edges tab.
    6. Make the desired changes.
    Element

    Description

    Connect edges of
    a journey to...

    You can specify to which stops edges are connected. Under the
    options you will find an illustrating example.
    Edges are generally connected to all stops where boarding or
    alighting is permissible.
    All stops where boarding or alighting is permissible
    If this option has been selected, edges are only connected to
    stops where boarding or alighting is permissible.
    All stops with profile points of the time profile
    If this option has been selected, edges are additionally connected
    to stops which are profile points of the time profile.
    All stops with route points of the line route
    If this option has been selected, edges are additionally connected
    to stops which are route points of the line route.
    All stops of the line route
    If this option has been selected, edges are additionally connected
    to all stops of the line route.
    Example
    A line route runs from A to C via B. A und C are profile points of
    the time profile where boarding or alighting is permissible, B is
    only a route point of the line route. If one of the first two options
    has been selected, the edges are only connected to the transfer
    nodes for A and C, but run past B. If one of the last two options
    has been selected, the edges run between the transfer nodes for
    A and B as well as between the transfer nodes for B and C.

    Edges of a trip at a This option provides a further filtering possibility.


    stop...
    If the option has been checked, you can select a line route item
    attribute. Edges are only connected to those stops at which this
    attribute is either not equal to zero or not empty.
    Note
    Still edges are always connected to stops where boarding or
    alighting is permissible.
    7. Select the Time slot tab.
    8. Make the desired changes.

    PTVGROUP

    2477

    24.16.9 Reading and saving the layout of schematic line diagrams


    Element

    Description

    Display only
    edges in time slot

    If the option has been selected, only edges of a vehicle journey


    that comply with the below filter conditions will be selected.
    Note
    Unlike in the window where you select the displayed vehicle journeys by setting a time slot in which vehicle journeys are displayed, you can specify here which edges of a vehicle journey
    are displayed within a certain time slot.

    The edges of a
    vehicle journey
    only are displayed...

    Here you can specify which edges of a vehicle journey are displayed within the below defined time slot.
    Departs from the 'from transfer node'
    If this option has been selected, only the edges of a vehicle journey which depart from the from transfer node are displayed.
    Between 'from transfer node' and 'to transfer node'
    If this option has been selected, only the edges of a vehicle journey are displayed whose time interval (departure time at from
    transfer node, arrival time at to transfer node) overlaps with the
    fixed time slot.

    Time slot

    Here you can specify the desired time slot.


    Valid day
    Select the valid day
    Start time/End time
    Enter a start time and an end time for the time slot

    9. Confirm with OK.


    The layout settings are saved.

    24.16.9 Reading and saving the layout of schematic line diagrams


    You can save a selection of the objects displayed and the position of transfer nodes and edge
    courses to a layout file, separate from the version file. This way you can apply the layout of
    schematic line diagrams to different timetables (see Fundamentals: Chpt. 12.13.4 , page 772).
    Note: The layout of the schematic line diagram is also saved with the version.
    24.16.9.1 Saving the layout of a schematic line diagram
    Note: The layout of a schematic line diagram is saved to an *.xml file.
    1. Specify the desired settings in the schematic line diagram (see "Setting the layout for schematic line diagrams" on page 2475).
    2. In the Schematic line diagram menu, select the Save layout as entry.
    The Save: Schematic line diagram: Layout window opens.

    2478

    PTVGROUP

    24.16.9.2 Reading the layout of a schematic line diagram


    3. Enter the desired file name and path, if required.
    4. Click the Save button.
    The layout parameters of the schematic line diagram are saved.
    24.16.9.2 Reading the layout of a schematic line diagram
    1. In the Schematic line diagram menu, select the Open layout entry.
    The Open: Schematic line diagram: Layout window opens.
    2. Open the desired file.
    3. Confirm with Open.
    The layout parameters of the schematic line diagram are read from file.

    24.16.10 Displaying statistics


    You can display statistical data for an open schematic line diagram.
    On the toolbar, click the Statistics button.
    The Statistics window opens. The various statistics are displayed for your illustrated network.

    24.17

    Displaying signal time-space diagrams


    Note: This function is only available, if the Signal offset optimization add-on is activated
    (see "Enabling or disabling installed add-ons" on page 886).
    Using the signal time-space diagram, you can display the signal times of signal controls along
    a path (see Fundamentals: Chpt. 12.14 , page 773). The green bands start at the green times
    of the upstream (initial direction) signal controls. In accordance with the defined run time, they
    extend in driving direction to the next signal control. The diagram indicates whether a green
    band encounters a green time at the next signal control. In the diagram, you can adjust the offsets of signal controls in order to synchronize the green bands.
    For a signal time-space diagram, you need at least one user-defined path allocated to a userdefined path set (see "Creating a PrT path" on page 1224). The path must traverse at least two
    nodes or main nodes with signal controls. Start and end nodes are not counted here. Additionally, the cycle times of the signal controls must meet the following requirement: The longest
    cycle time must not exceed the greatest common divisor of all cycle times multiplied by eight.

    PTVGROUP

    2479

    24.17.1 Opening a signal time-space diagram


    Notes: If you want to find out how many user-defined paths exist in your version, choose
    the Network tab. Position the mouse pointer on the PrT paths button. A quick info displays the information you are looking for.
    External signal controls can have several signal programs. In Visum only one signal program is allocated to a signal control. The signal time-space diagram shows the signal
    times for the currently allocated signal control.
    The allocation can be changed manually in the junction editor, for example (see "Switching off or manually changing signal programs in Visum" on page 2558). Via the procedure Set signal programs , you can automatically set the signal program for the
    relevant time period during a procedure sequence (see "Adding procedures to the procedure sequence" on page 1848).

    24.17.1 Opening a signal time-space diagram


    1. In the Edit menu, select the Signal time-space diagram entry.
    The Signal time-space diagram window opens.

    Tips: You can also open the signal time-space diagram by clicking the
    Open
    signal time-space diagram icon.
    If a window with a signal time-space diagram is already open, you can open a second
    signal time-space diagram. To do so, select the Signal time-space diagrammenu >
    Next signal time-space diagram entry.
    2. Click the Path (initial direction) button.
    The Select path (initial direction) window opens. Here you see a list of all user-defined
    paths that traverse at least two nodes or main nodes with signal controls.
    3. Make the desired changes.

    2480

    Element

    Description

    Key

    You can use this input field to jump directly to a path in the list below.
    The path key consists of the path set number, a semicolon, and the
    path number.
    Enter a number to select the first path of a path set.
    Example: Enter 5 to select the first path of path set 5.
    Enter a semicolon and the number of the path to select the first
    path with this number.
    Example: Enter ;3 to select the first path with the number 3.

    Path set

    Use the drop-down list to specify that only paths of one path set are displayed in the list.
    Note
    In this context only user-defined path sets are available. Demand seg-

    PTVGROUP

    24.17.1 Opening a signal time-space diagram


    Element

    Description
    ments are not displayed.

    Filtering

    Use the drop-down list to restrict the number of paths that are displayed
    in the list.
    All routes
    All routes are displayed.
    Filter for OD pairs
    The list only contains paths with a zone as a start and ending point. The
    properties of this zone must correspond to the current OD pairs filter
    (see "Exception: Filter for OD pairs" on page 1026).

    4. In the drop-down list, select the desired path.


    5. Confirm with OK.
    The path you selected is displayed in the signal time-space diagram.
    Tip: Alternatively, to open the signal time-space diagram, in the Paths window, rightclick the path of your choice. Then, from the context menu, choose Signal time-space
    diagram for path (see "Opening the Paths window" on page 1228). In this case you
    have the advantage that you see the course of the path in the network. Another possibility is to use the PrT paths list and right-click the path you want. Then you select in
    the context menu the Signal time-space diagram for path entry.
    6. If required, use the Path (reverse direction) button to insert a path for the reverse direction.
    Note: For the reverse direction you can only use paths which have the following properties:
    The path must have at least two common nodes with the path of the initial direction.
    The common nodes of the initial and reverse direction must occur in reverse
    order.
    The paths of your choice are displayed in the signal time-space diagram (see "The signal
    time-space diagram window" on page 2482).

    PTVGROUP

    2481

    24.17.2 The signal time-space diagram window

    24.17.2 The signal time-space diagram window

    (1) Toolbar
    Here you specify settings to change the current display (see "Adjusting the signal time-space
    diagram" on page 2483).
    (2) Path display
    The path is schematically displayed. In the default view the icons have the following meanings:
    Filled circle: Signalized node which is traversed by both paths
    Empty circle: Node without signal control which is traversed by both paths
    Filled triangle: Signalized node which is traversed by just one path (initial or reverse direction)
    Filled triangle: Node without signal control which is traversed by just one path (initial or
    reverse direction)
    You can change the color of icon borders and fillings as well as the link display (see "Setting
    graphic parameters for the signal time-space diagram" on page 2487).
    (3) Node labels
    You can specify up to four attribute values for each node (see "Setting graphic parameters for
    the signal time-space diagram" on page 2487).

    2482

    PTVGROUP

    24.17.3 Adjusting the signal time-space diagram


    (4) Cycle time and offset
    Here the cycle time and offset of the signal controls are displayed. You can change the offset
    (see "Changing offsets in the signal time-space diagram" on page 2487).
    (5) Diagram
    The diagram graphically displays the green bands. The X-axis is the time axis, the Y-axis is
    the spatial axis. The path's initial direction is top-down, its reverse direction is bottom-up. On
    the spatial axis you see horizontal red lines at the height of each signalized node. The green
    horizontal bars represent the green times of the signal controls. The bars of the initial direction
    are on top of the red line. The bars of the reverse direction are below the red line. You can
    adjust the display (see "Setting graphic parameters for the signal time-space diagram" on
    page 2487).
    Notes: Links and nodes which are within a main node are not displayed.
    In the signal time-space diagram you can zoom in or zoom out, you can shift the view or
    reset it to the initial setting. These functions correspond with those in the network window. You can call them via the View menu, the buttons on the toolbar or the mouse
    wheel (see "Network editor window" on page 818).
    Additionally, you can stretch or compress the time axis. If you place the mouse cursor on
    the label of the time axis, it is displayed as horizontal double arrow. Click and move the
    mouse pointer parallel to the axis to stretch or compress it.

    24.17.3 Adjusting the signal time-space diagram


    1. Make sure the Signal time-space diagram window is open (see "Opening a signal timespace diagram" on page 2480).
    2. Select the settings you need in the upper window pane.
    Element

    Description

    Path (initial
    direction)

    Use this button to select a different path as initial direction (see "Opening a signal time-space diagram" on page 2480).

    Path (reverse
    direction)

    Use this button to select a different path as reverse direction (see


    "Opening a signal time-space diagram" on page 2480).

    Parameters

    Use the Edit button to change the basic settings of the signal timespace diagram (see "Defining demand segment filters and travel
    times for the signal time-space diagram" on page 2484).

    PTVGROUP

    2483

    24.17.3 Adjusting the signal time-space diagram


    Element

    Description

    Max. signal
    time

    Define the period of time that you want to display on the time axis of
    the signal time-space diagram.
    Note
    By default Visum determines the time period as follows: It calculates
    the least common denominator of all cycle times displayed in the diagram and multiplies this value with two.

    Signal timespace diagram mode

    Flowing off
    On the basis of green times of the displayed turn on a signal control, a
    green band visualizes the possible range in which vehicles can drive
    with the predefined run time to the next signal control.
    Arterial bands
    The green band visualizes only the range in which a vehicle which drives at the predefined speed reaches all signal controls on the path at
    green (progressive signal system). Therefore it is a subset of the
    green bands visualized with the Flowing off option. If this constellation does not exist, no green band is displayed.

    The settings are applied.


    Defining demand segment filters and travel times for the signal time-space diagram
    1. Make sure the Signal time-space diagram window is open (see "Opening a signal timespace diagram" on page 2480).
    2. In the upper window area next to Parameters click Edit.
    The General procedure settings window opens. In the navigator PrT settings > Signal offset optimization is selected.
    Note: These and other parameters are also relevant for signal offset optimization (see
    "Signal offset optimization" on page 1923).
    3. Make the desired changes.

    2484

    PTVGROUP

    24.17.4 Synchronizing the signal time-space diagram with other windows


    Element

    Description

    Use demand segment filter

    If this check box is selected, the signal time-space diagram only


    displays those signal times which are valid for the selected
    demand segments. Click the unnamed button to select the
    demand segments you need.
    The signal timing of the signal group with the longest red phase is
    used, if the following conditions apply: Several demand segments
    have been selected or this filter is not used and the signal timing
    of the demand segments is not identical.
    Note
    A turn can have several lanes which may be allocated to different
    signal groups. The lane turns and allocated signal groups may
    refer to different traffic systems. In this mode each demand segment is allocated to exactly one transport system. Therefore, with
    the selection of the demand segment the signal group is selected
    as well.

    Travel times

    Here you specify the travel times for the following network
    objects: links, turns, and main turns. You use the button to select
    an attribute for each network type. This attribute can be multiplied
    by a factor. The travel times between two signal controls in the
    signal time-space diagram is the sum of the travel times needed
    for traversing the network objects. Travel times of links and nodes
    within main nodes are not considered because they are contained in the main turns.

    4. Confirm with OK.


    The changes are applied.

    24.17.4 Synchronizing the signal time-space diagram with other windows


    You can synchronize the signal time-space diagram with other windows, for example with the
    network window, the junction editor, or the nodes or main nodes list. If the windows are synchronized and you mark one or several nodes or main nodes in one window, they are automatically marked in the other windows as well. Depending on the setting, in the network
    window the displayed section is automatically shifted or zoomed in.
    Example: You simultaneously open the signal time-space diagram and the junction editor,
    with the signal timing view (see "Editing the signal timing of a node" on page 1487).. If you
    select a node in the signal time-space diagram, this node is automatically displayed in the
    junction editor.

    PTVGROUP

    2485

    24.17.4 Synchronizing the signal time-space diagram with other windows

    Note: For synchronization to work, you need to enable it in the other respective windows
    as well (see "The list window" on page 2304 and "Using the Junction editor" on page
    1435).
    1. Make sure the Signal time-space diagram window is open (see "Opening a signal timespace diagram" on page 2480).
    2. In the Signal time-space diagram window open the Synchronization with network editor
    entry.
    3. Select the desired entry.
    Element

    Description

    No synchronization

    The signal time-space diagram is not synchronized with other windows.

    Mark object(s)

    Nodes or main nodes that are marked in the signal time-space


    diagram are also marked in other windows (or vice versa).

    Mark and shift


    view

    Nodes or main nodes that are marked in the signal time-space


    diagram are also marked in other windows (or vice versa). If required, the network section of the network window is shifted in such
    a way that all marked objects are visible.
    Note
    This does not affect the scale of the network editor.

    Mark and autozoom

    Nodes or main nodes that are marked in the signal time-space


    diagram are also marked in other windows (or vice versa). Additionally, in the network an auto zoom is carried out for the marked
    objects.

    The settings are applied.


    2486

    PTVGROUP

    24.17.5 Changing offsets in the signal time-space diagram


    4. In the signal time-space diagram, click under Path the node or main node you need.
    Note: The nodes that all paths traverse are by default displayed as circles. All other
    nodes are displayed as triangles.
    In all other open windows the nodes or main nodes are also marked.

    24.17.5 Changing offsets in the signal time-space diagram


    1. Make sure the Signal time-space diagram window is open (see "Opening a signal timespace diagram" on page 2480).
    2. In the signal time-space diagram, position the mouse pointer on one of the horizontal bars
    of a node.
    The pointer appears as double-arrow.
    3. Click the mouse and hold down the mouse button.
    4. Drag the mouse pointer to the left or right.
    The offset of the selected signal control changes. The value in the left input field is adjusted.
    Tips: You can also enter the value directly into the input field.
    You can also edit offsets in the junction editor (see "Editing the signal timing of a node"
    on page 1487). If you have the junction editor and the signal time-space diagram open
    simultaneously, changes are displayed immediately in both windows.

    24.17.6 Setting graphic parameters for the signal time-space diagram


    You can adjust the graphic parameters for the signal time-space diagram. The graphic parameters are valid for all signal time-space diagrams of this version and are saved in the version
    file.
    1. Make sure that the Signal time-space diagram window is open (see "Opening a signal
    time-space diagram" on page 2480).
    2. In the Signal time-space diagram menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens. If desired, make further changes on the following pages: Paths, Chart and Print frame.
    Setting graphic parameters for the paths in the signal time-space diagram
    1. Make sure that the Edit graphic parameters window is open for the signal time-space diagram.
    2. In the navigator, select the Paths entry.
    3. On the pages of this window define the settings you need.

    PTVGROUP

    2487

    24.17.6 Setting graphic parameters for the signal time-space diagram

    2488

    Page

    Description

    Font

    Font
    Click the field to specify the font and the font style for the signal timespace diagram in a separate window.
    Size
    Text size in mm
    Color
    Click the field to select the color of the font in a separate window.

    Label

    Use the four buttons to specify four attribute values that are displayed
    in the signal time-space diagram for each node or main node under
    Labels at nodes and main nodes. The buttons are labeled with the
    currently selected attributes; by default, it is the Number of the node,
    for example. In addition to the node attributes and indirect attributes,
    the Corridor and Crossing road attributes can also be selected in the
    selection window (see "The window used for the selection of one attribute" on page 963).
    Corridor: Name of the last link on the path before the node.
    Crossing road: Name of a link which is not connected with the
    node and not part of the path.

    Line style

    Here you can specify the line style which is used for displaying the
    links of the path under Path.
    Uniform display
    If the option has been selected, all links are drawn consistently.
    Classified display
    If this option is selected, links can be classified and displayed based
    on an attribute (see "Displaying classified objects based on attribute
    values" on page 2411).
    Display
    Here you can select a link's width, color, and line style.

    Signalized
    nodes

    You can specify graphic parameters for active, passive, and signalized nodes or main nodes on the three tabs Active, Passive, and
    Marked. The uniform display and the classified display are only
    available for active (main) nodes. For passive and marked (main)
    nodes, only the Display option is available.
    Uniform display
    If this option has been selected, all active (main) nodes are drawn consistently.
    Classified display
    If this option is selected, you can classify the display of active (main)
    nodes based on an attribute (see "Displaying classified objects based
    on attribute values" on page 2411).

    PTVGROUP

    24.17.6 Setting graphic parameters for the signal time-space diagram


    Page

    Description
    Display
    Click in the field to select the color of the filling and the margin of the
    (main) nodes in a separate window.
    Note
    If you have selected the Classified display option, the setting is valid
    for the currently selected class.

    Unsignalized
    nodes

    Here you specify the graphic parameters for the unsignalized (main)
    nodes. Here you can define the same settings as on the Signalized
    nodes page.

    4. Confirm with OK.


    The settings are applied.
    Setting graphic parameters for the signal time-space diagram
    1. Make sure that the Edit graphic parameters window is open for the signal time-space diagram.
    2. In the navigator, select the Chart entry.
    3. On the pages of this window you define the settings you need.
    Page

    Description

    Grid settings

    Background color
    Use the drop-down list to select a color for the background of the diagram
    Subordinate time axis unit
    Temporal distance of the grids displayed on the time axis in minutes
    Line style for the superior time axis unit
    The line style for the central grid of the time axis
    Line style for the subordinate time axis unit
    The line style for the grids on the time axis
    Line style for signalized nodes
    The line style for the lines of the signalized nodes on the spatial axis
    Line style for unsignalized nodes
    The line style for the lines of the non-signalized nodes on the spatial
    axis
    Note
    If you click in the field, you change the line style.

    Green times

    PTVGROUP

    Line style for the green time of the initial direction

    2489

    24.17.7 Saving and reading the graphic parameters of the signal time-space diagram
    Page

    Description
    The line style for the green time bars of the (main) nodes along the
    path in the initial direction (parallel to time axis)
    Line style for the green times of the reverse direction
    The line style for the green time bars of the (main) nodes along the
    path in the initial direction (parallel to time axis)
    Green band of the initial direction
    Draw
    If this option has been selected, the green band for the path is drawn
    in the initial direction.
    Fill/Margin color
    Click in the field to change the display of the green band.
    Green band of the reverse direction
    Here you specify the same settings as for Green band of the initial
    direction.

    4. Confirm with OK.


    The settings are applied.
    Setting the graphic parameters for the print frame in the signal time-space diagram
    1. Make sure that the Edit graphic parameters window is open for the signal time-space diagram.
    2. In the navigator, select the Print frame entry.
    3. Make the desired settings (see "Setting the print frame" on page 2504).
    4. Confirm with OK.
    The settings are applied.

    24.17.7 Saving and reading the graphic parameters of the signal time-space diagram
    Note: The graphic parameters of the signal time-space diagram are saved to a file of the
    type *.gptsd file.
    24.17.7.1 Saving the graphic parameters of the signal time-space diagram
    1. Edit the graphic parameters as desired (see "Setting graphic parameters for the signal timespace diagram" on page 2487).
    2. In the Signal time-space diagram menu, select the Save graphic parameters as... entry.
    The Save: Signal time-space diagram graphic parameters window opens.
    3. Enter the desired file name and path, if required.
    4. Click the Save button.

    2490

    PTVGROUP

    24.17.7.2 Opening graphic parameters of the signal time-space diagram


    The graphic parameters of the signal time-space diagram are saved.
    24.17.7.2 Opening graphic parameters of the signal time-space diagram
    1. In the Signal time-space diagram menu, select the Open graphic parameters entry.
    The Open: Signal time-space diagram graphic parameters window opens.
    2. Open the desired file.
    3. Confirm with Open.
    The graphic parameters of the signal time-space diagram are opened.

    24.17.8 Printing or exporting the signal time-space diagram


    You can print the signal time-space diagram or export it as graphics file.
    Printing the signal time-space diagram
    1. Specify the settings you need for printing the signal time-space diagram.
    Note: You define print frame settings in the graphic parameters on the Print frame
    page (see "Setting graphic parameters for the signal time-space diagram" on page
    2487).
    Other print settings correspond to those for printing the network display (see "Printing
    the network display" on page 2499).
    2. Make sure the Signal time-space diagram window is open (see "Opening a signal timespace diagram" on page 2480).
    3. Choose the File menu. Then point to Print.
    4. Select the Print entry.
    The Print: Signal time-space diagram window opens.
    5. Make the desired settings (see "Starting print output" on page 2508).
    6. Confirm with OK.
    The signal time-space diagram is printed.
    Exporting the signal time-space diagram as graphics file
    You can save the signal time-space diagram directly in a graphics file of the type *.svg or *.dxf.
    1. Make sure the Signal time-space diagram window is open (see "Opening a signal timespace diagram" on page 2480).
    2. In the Signal time-space diagram menu, select one of the SVG Export or DXF Export entries.
    The Save SVG file or Save DXF file window opens.
    3. Enter the file name and the path, if required.
    4. Click the Save button.
    PTVGROUP

    2491

    24.18 Creating column charts


    The SVG export or DXF export window opens.
    5. Make the desired settings (see "SVG export" on page 2656 and "DXF export" on page
    2654).
    6. Confirm with OK.
    The signal time-space diagram is saved in a *.svg or *.dxf file.
    Tip: To export the signal time-space diagram to a graphics file, from the Signal time
    space diagram menu, choose JPG export (screenshot), or in the Signal time space
    diagram window, on the toolbar, click
    , the JPG export (screenshot) button (see
    "Exporting screenshots" on page 2663).

    24.18

    Creating column charts


    You can create column charts with attribute values for network objects (see Fundamentals:
    Chpt. 12.14 , page 773). You can export the column charts afterwards.
    Note: You can also display negative attribute values. These are drawn below the baseline of the chart by means of negative columns.

    24.18.1 Displaying column charts


    1. In the network display, select the network object for which you want do display a column
    chart.
    2. Right-click in the network display.
    A context menu opens.
    Tip: Alternatively, select a network object in an open list and right-click it to open its
    shortcut menu (see "Working with lists" on page 2299).
    3. Select the Column charts entry.
    The Column chart for <network object, number> window opens.
    4. Click the Settings button.
    The Graphic parameters: Column chart for <network object, number> window opens.

    2492

    PTVGROUP

    24.18.1 Displaying column charts

    5. Make the desired changes.


    Note: The settings apply to all column charts of the network object type. You can thus
    specify just one display per network object type.
    Element

    Description

    Charts

    Here you can specify the number of charts for the selected network object
    type.
    Note
    If you insert several rows, the individual charts are displayed one below
    the other.
    Name
    You can enter a name for each chart, if you double-click in the respective
    row.
    Note
    In the display, the name is displayed as chart title.
    Create
    Use this button to create a row for a new chart.
    Delete
    Use this button to delete the selected row.
    Note
    If you create more than one row, the following settings apply to the selected row/chart.

    X-axis

    You can select one of the following options in order to display one or

    PTVGROUP

    2493

    24.18.1 Displaying column charts


    Element

    Description
    several column charts.
    one column per network object
    If the option has been selected, you can select the network object or a
    relation in a separate window when clicking on the button.
    Tips
    A multi-level selection is possible. The set union of all objects is then
    selected. You can, for example, select the relation Origin connectors/Node/In Links of Zones. This means that the set of all incoming links
    at all connected nodes has been selected. You can thus, for example, display all volumes of the incoming links at a specific node.
    one column per analysis time interval
    If the option has been selected, the chart displays one column per time
    interval for one or more attributes.
    Notes
    This option facilitates the graphical display of the temporal course of, for
    example, volumes at links, stops, lines and so on. Each attribute is displayed as a separate row.
    X-axis label
    Enter a text which will be displayed at the x-axis of the chart.
    X-values labels
    You can select an attribute of the chosen network object type in a separate window when clicking the button.
    Notes
    The columns are labeled with the attribute value at the x-axis. The option
    is only available, if the one column per network object option has been
    selected. If the one column per analysis time interval option has been
    selected, the x-axis is labeled with the currently existing analysis time
    intervals.

    Y-axis

    2494

    Here you can specify the value range and the attributes which you want to
    display.
    Min value
    Minimum value displayed at the y-axis
    Max value
    Maximum value displayed at the y-axis
    Create
    Use this button to create a row for a new attribute.
    Note
    You can create as many attribute rows as you like.
    Attribute

    PTVGROUP

    24.18.1 Displaying column charts


    Element

    Description
    In this column, you can select an attribute which you want to display when
    clicking on the button. The button is labeled with the selected attribute.
    Color
    You can select a color for the display of the attribute values in a separate
    window when clicking the button in the Color column.
    Delete
    Use this button to delete the selected attribute row.

    Draw
    legend

    If the option has been selected, next to the respective chart, a legend features the short names and the colors of the displayed attributes.
    Note
    You need to set the option separately for each chart. To do this, select the
    desired chart in the list of the Charts section.

    Note: If you click the Preview button, your changes show immediately without the Graphic parameters: Column chart for <network object, number> window being closed.
    6. Confirm with OK.
    The column chart is displayed according to your chosen settings.
    Notes: If you make changes to the network or the time intervals, the column chart is refreshed.
    The parameter settings of the column charts are saved with the version file and with the
    graphic parameters file.
    Example of a column chart
    The settings pictured in the Graphic parameters: Column chart for link 53 (51>52) window,
    yield the following column chart.

    PTVGROUP

    2495

    24.18.2 Exporting a column chart


    Tip: Horizontal dividers separate the individual charts. You can change the proportions of
    the charts if you drag the divider.

    24.18.2 Exporting a column chart


    If you have created a column chart, you can export the individual charts to different graphic formats or, via the clipboard, insert them directly in reports.
    1. In the Graphic parameters: Column chart for <network object, number> window, rightclick the chart which you want to export.
    A context menu opens.
    2. Select the Export entry.
    The Export chart window opens.
    3. Make the desired changes.
    Element

    Description

    Copy chart to clip- Uncompressed bitmap


    board
    If this option has been checked, the chart is exported as uncompressed bitmap.
    Vector graphics
    If this option has been checked, the chart is exported as vector
    graphics.
    Copy
    Copy the selected chart to the clipboard by clicking on the button.
    Tip
    Afterwards, you can use the respective paste functionality to
    insert the chart in the external program.
    Export chart as
    file

    Save
    You can export the chart to a graphics file if you click the button.
    Note
    In the Save image file window, you can specify the file extensions *.emf, *.jpg or *.bmp.

    4. Save the file to the desired location.

    24.19

    Reading and saving the graphic parameters of the network window


    You can save the current graphic parameters of the network display to a graphic parameters
    file and read them in again.

    24.19.1 Saving the graphic parameters of the network window


    Note: The graphic parameters of the network window are saved to a *.gpa file.

    2496

    PTVGROUP

    24.19.2 Reading graphic parameters of the network window


    There are two ways to save the graphic settings.
    First possibility
    1. Edit the graphic settings as desired.
    2. In the File menu, point at Save as.
    3. Select the Graphic parameters entry.
    The Save graphic parameter file window opens.
    4. Enter the desired file name and path, if required.
    5. Click the Save button.
    The graphic parameters of the network window are saved.
    Second possibility
    1. Edit the graphic settings as desired.
    2. In the Select GPar field, enter a name for the file.
    3. Press the ENTER key.
    The settings are saved under the name entered to a graphic parameters file *.gpa in the project directory for graphic parameter files (see "Saving a project directories file" on page 839)..

    24.19.2 Reading graphic parameters of the network window


    If you have saved your settings to a graphic parameters file *.gpa , you can read in your
    graphic settings as follows. There are two ways to read in graphic settings.

    First possibility
    1. In the File menu, place the pointer on the Open entry.
    2. Select the Graphic parameters entry.
    The Open graphic parameter file window opens.
    3. Open the desired file.
    4. Confirm with OK.
    The Reading graphic parameters: Select window opens.
    5. Make the desired changes.
    Element

    Description

    Read all graphic


    parameters

    If the option has been selected, all graphic parameters are read
    in.

    Read selected
    parameters

    If the option has been selected, the graphic parameters selected


    in the list are read in.
    GPar

    PTVGROUP

    2497

    24.19.2 Reading graphic parameters of the network window


    Element

    Description
    List of all graphic parameters
    Read
    If the option has been selected, the corresponding graphic parameters are read in.
    Note
    The option is only available, if the corresponding parameters are
    contained in the file.
    Additionally
    If the option has been selected, the corresponding graphic parameter is added to the existing graphic parameters.
    Note
    The option is only available for background items.
    All off
    Use this button to deactivate all options.
    All on
    Use this button to select all options of the Read column. The
    selection shown in the Additively column will be deleted.

    Limit to network
    If the option has been selected, the following parameters are not
    indep. parameters read in:
    Window coordinates
    Bing Maps backgrounds
    Backgrounds
    Background polygons
    Background texts
    Turn volumes
    Desire line Zones Text position
    Column charts
    Flow bundle
    6. Confirm with OK.
    The graphic parameters of the network window are read in.
    Second possibility
    On the toolbar, select the desired graphic parameters file in the drop-down list by clicking
    the entry.
    Note: In the drop-down list, you can select a graphic parameter file saved to the project directory specified (see "Saving a project directories file" on page 839).
    The file is read in and the saved settings are applied.

    2498

    PTVGROUP

    24.20 Printing the network display


    Note: You can also have a graphic parameters file automatically opened when you start
    the program (see "Starting Visum with different settings" on page 887)

    24.20

    Printing the network display


    You can print the current network display.
    Note: Alternatively, you can save the display to a file. Visum offers different formats for
    this purpose (see "Graphics interfaces" on page 2650).
    If you want to print the network display, you should follow the processing steps listed below:
    Set print page
    Specifying the print area
    Setting the print frame
    Preview of the print output
    Starting print output

    24.20.1 Set print page


    The print page is defined by the adjustable paper margin, the output section and the positioning.

    Tip: To check your settings immediately, open the page preview (see "Preview of the
    print output" on page 2508).
    1. In the File menu, point at Print.
    2. Select the Set pint page.
    The Set print page window opens.

    PTVGROUP

    2499

    24.20.1 Set print page

    3. Make the desired changes.


    Element

    Description

    Margins

    Limits of the in printable area of the current output device in mm

    Output section Here you can specify the section which you want to print.
    Current view
    If the option has been selected, the current view of the Visum window
    will be printed.
    Tip
    You can also select this section in the Print area window via the from
    window button. The window opens when you click the Print area button.
    Print area
    If the option has been selected, the defined print area will be printed
    (see "Specifying the print area" on page 2502).
    Entire graphical display
    If the option has been selected, the entire network display will be printed.
    Note
    For the Current view and Entire graphical display options, the current scale is used unless the Scaling to page size option has been
    selected.
    Positioning

    2500

    Scaling to page size


    If this option has been selected, the output section is scaled to the
    print area.

    PTVGROUP

    24.20.1 Set print page


    Element

    Description
    Note
    The output section is scaled either horizontally or vertically so that it
    covers the print area completely in one of the two directions. Hereby,
    the selected scale is adjusted (both zoomed in and out).
    Expand to page size
    If this option has been selected, the output section is extended to the
    entire print area. Hereby, the top left corner of the output section
    remains fixed. The horizontal and vertical extension is adjusted to the
    print area. The selected scale is remains unchanged.
    If for the selected scale the output section is greater than the print
    area in vertical and horizontal direction, the Cut off at margin, Scale
    to page size, and Print tiles options are displayed when you print
    (see "Starting print output" on page 2508).
    Tip
    You can also select the Expand to page size function in the File>
    Print menu, Print area entry, if you click the To page size button
    there.
    Note
    If both options Scale to page size and Expand to page size have
    been selected, the output section is first scaled and then expanded in
    the direction in which the print area is not filled out. The scale is adjusted.
    Horizontal centering/Vertical centering
    If one of the options or both have been selected, the print is aligned
    horizontally and/or vertically.
    Note
    If none of the two options has been selected, the output section is aligned at the top left corner of the printable section.

    Scaling

    Scale absolute sizes in mm


    If the option has been selected, the difference in scale between the
    soft copy and the print will be adjusted.
    Note
    For this purpose, the scaling factor between the two scales is calculated and all absolute sizes in mm are multiplied by this factor.

    Print area

    Use this button to open the Print area window (see "Specifying the
    print area" on page 2502).

    Printing

    Use this button to open the Print: Network editor window (see "Starting print output" on page 2508).

    Preview

    Use this button to immediately check your settings when the page preview is open (see "Preview of the print output" on page 2508).

    PTVGROUP

    2501

    24.20.2 Specifying the print area


    4. Confirm with OK.
    The current settings of the print page are applied.

    24.20.2 Specifying the print area


    You can display the limits of the print area on the screen.
    1. In the File menu, point at Print.
    2. Select the Print area entry.
    The Print area window opens and, in the network, the print area is indicated by a rectangle.

    Tips: Once the Print area window is open, you can use the right mouse button to
    enlarge or reduce the size of the rectangle.
    Alternatively, you can use the right mouse button to drag a new rectangle and thus
    define a new print area.
    3. Make the desired changes.

    2502

    PTVGROUP

    24.20.2 Specifying the print area


    Element

    Description

    Drop-down list

    Here you can select the following options.


    Keep scale

    If the option has been selected, the scale does not change when
    editing the print area.
    Note
    If you enlarge the print area with the mouse pointer, you might
    exceed the available paper size. This is indicated by red values
    in the Size section.
    Keep size

    If the option has been selected, the height and the width of the
    printable area remain unchanged when editing the print area with
    the mouse. The scale is adjusted accordingly.
    Size

    X, Y
    Width and height of the print area in mm
    Note
    If the values are red, the print area exceeds the available paper
    size.
    To page size
    You can expand the print area to the specified page format by
    clicking on this button.

    Scale

    PTVGROUP

    Enter the scale


    Note
    If the Keep size option has been selected, a different section of
    the network will be displayed when editing the scale. If the Keep
    scale option has been selected, the width and the height change
    when editing the scale.

    2503

    24.20.3 Setting the print frame


    Element

    Description

    Window

    Here you can define the print area by entering co-ordinates.


    Note
    You can click the arrows to shift the print area. The print area will
    then be shifted by the size of the print area in the direction of the
    arrow.

    Print area

    From window
    Use this button to set the print area to the size of the current
    Visum window.
    To max. scale
    Use this button to maximize the scale for the network display of
    the set print area in such a way, that the print area fits the printable area of the print page.
    Auto zoom
    Use the button to zoom into the print area. The entire print area is
    displayed on screen.

    4. Confirm with OK.


    The settings for the print area are applied.
    Tip: You can display the print area as a rectangle with broken lines, if you select the
    respective option under Graphics > Edit graphic parameters > page Print frame. The
    print area is only displayed, if the Print area option has been selected in the Set print
    page window (see "Set print page" on page 2499).

    24.20.3 Setting the print frame


    If you want to print the network display, you can specify the following settings for the print
    frame.
    1. In the Graphics menu, select the Edit graphic parameters entry.
    The Edit graphic parameters window opens.
    2. In the navigator, select the Print frame entry.
    3. Make the desired changes.

    2504

    PTVGROUP

    24.20.3 Setting the print frame


    Element

    Description

    Draw

    If the option has been selected, a print frame is drawn.


    Note
    If the option has been selected, a single frame is drawn, if the
    Draw Header and Footer options are not selected on the respective page.

    Boundary

    You can specify the boundary style in a separate window. To do


    so, click in the field (see "Setting the line style properties" on page
    2363)..

    Show print area on If the option has been selected, the print area is displayed on
    screen
    screen as a rectangle with broken lines.
    Note
    The print area is only displayed, if the Print area option has been
    selected in the Set print page window (see "Set print page" on
    page 2499).
    4. Select the Header page, if you want to insert a header.
    Note: The header extends over the complete width of the print frame.
    5. Make the desired changes.
    Element

    Description

    Draw

    If the option has been selected, a header is displayed.

    Font

    You can specify the font and the style in a separate window by
    clicking in the field.
    Note
    You can position the header left, right or centered, if you click the
    respective icon on the right.

    Text size

    Text size in mm

    Color

    Use the drop-down list to select a text color.

    Minimum line
    height

    If the option has been selected, you can enter a minimum height
    for the row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    Text

    Use the drop-down list to select text entries which will be inserted
    in the header.
    user-defined
    Here you can enter a text into the empty field.

    PTVGROUP

    2505

    24.20.3 Setting the print frame


    Element

    Description
    empty
    [VISUM version]
    Created on: [Date]
    Created on: [Date] / [Time]
    [Date] / [Time]
    [File name]
    [Scale]
    [Scale factor]

    Help

    Use the button to open a window with all available auto values.
    Note
    The entries in squared brackets are pre-defined by the program
    (auto values). They are replaced with the current values when drawing the print frame. Auto values are language-dependent and
    can also be utilized as user-defined entries.

    6. Select the Footer page, if you want to insert a footer.


    Note: The footer can consist of up to six fields, which are displayed at the bottom of
    the print area.
    7. Make the desired changes.

    2506

    Element

    Description

    Draw

    If the option has been selected, a footer will be drawn.

    Font

    You can specify the font and the style for the footer in a separate
    window by clicking in the field.

    Text size

    Text size in mm

    Image height

    Size of inserted graphics in mm


    Tip
    Graphics can be inserted via the drop-down lists in the Text section.

    Color

    Use the drop-down list to select a text color.

    Minimum line
    height

    If the option has been selected, you can enter a minimum height
    for the row. Enter a height in mm.
    Note
    The height of the row should exceed the text height; otherwise the
    height of the row will be twice the text size.

    Column format

    You can regulate the width of each column by entering a percentage.


    Notes

    PTVGROUP

    24.20.3 Setting the print frame


    Element

    Description
    The total need not amount to 100%. The width will be calculated
    proportionately.
    You can position the column contents left aligned, centered or
    right aligned by clicking the respective icon below.

    Text

    Use the drop-down list to select text entries which will be inserted
    in the footer.
    user-defined
    Here you can enter a text of your choice into the empty field.
    empty
    Hide cell
    Select this option to hide the respective field.
    [VISUM version]
    Created on: [Date]
    Created on: [Date] / [Time]
    [Date] / [Time]
    [File name]
    [Scale]
    [Scale factor]
    [Graphics]
    If you select this option, in the list box, you can click the path
    to the image you want to display.

    Help

    Use the button to open a window with all available auto values.
    Notes
    The entries in squared brackets are pre-defined by the program
    (auto values). They are replaced with the current values when drawing the print frame. Auto values are language dependent and
    can also be used as user-defined entries.
    If you want to display an image of type [Graphics], enter a
    comma and the path to the image. Example: [graphics, D:\logo.bmp] The size is specified in the Display section under Image
    height.

    Note: If you click the Preview button, your changes will immediately be displayed
    though the Edit graphic parameters window is still open.
    8. Confirm with OK.
    The settings for the print frame are applied.
    Tip: For a detailed description of a Visum network display, a legend is more suitable. You
    can insert the legend at a corner of the print area (see "Creating legends" on page 2255).

    PTVGROUP

    2507

    24.20.4 Preview of the print output

    24.20.4 Preview of the print output


    Before you print the network display, you can take a look at the layout in the preview. The preview gives a print preview which, for example, visualizes graphical defects like overlapping
    objects or poor legibility of texts. You can correct possible faults directly in the preview.
    Note: In the preview, all network and graphic objects are displayed with the correct scale
    because the text enlargement factor for screen displays is not applied to print outputs
    (see "Specifying basic settings" on page 2337).
    1. In the File menu, point at Print.
    2. Select the Preview entry.

    Tip: Alternatively, you can open or close the view via the
    bar.

    Preview icon on the tool-

    The preview opens.


    3. Make the required changes.
    Tip: You can correct possible deficiencies directly in the preview, since all relevant
    editing functionalities can be carried out in this view. You can, for example, edit the
    graphic parameters or lists.

    24.20.5 Starting print output


    Once you have specified the desired settings, you can start print output.
    1. In the File menu, point at Print.
    2. Select the Print entry.
    Tip: Alternatively you can open the window by pressing the C TRL and P keys at the
    same time.
    The Print: Network editor window opens.

    2508

    PTVGROUP

    24.20.5 Starting print output


    3. Make the desired changes.
    Element

    Description

    Printer

    Name
    In the drop-down list, you can select the desired printer.
    Note
    You can either print the network display on your printer or as a
    PDF file (see "PostScript-PDF export" on page 2651).
    Properties
    Here you can, for example, specify the paper feed and type or the
    orientation.

    Paper

    Here you can specify the paper Size and Source.

    Orientation

    Here you can set either a Portrait or Landscape output.

    File output

    Print to graphics file


    If the option is selected, the network display is exported to a
    graphics file of the format *.dxf or *.svg (see "Graphics interfaces"
    on page 2650).

    Set print page

    Use this button to open the Set print page window (see "Set print
    page" on page 2499).

    4. Confirm with OK.


    If the output section exceeds the print page, the Select printing mode window opens.

    5. Make the desired changes.


    Element

    Description

    Cut off at margin

    If the option has been selected, the graphics to be printed is cut


    off at the margins.

    Scaling to page
    size

    If the option has been selected, the graphics is expanded to the


    size of the entire page without changing the width-to-height ratio.

    PTVGROUP

    2509

    24.20.5 Starting print output


    Element

    Description
    Note
    If this option has already been selected in the Set print page window, the Select printing mode window does not open.

    Print tiles

    If the option has been selected, the print is output in the form of
    tiles.
    Notes
    We recommend this kind of output, if you want to print a large network but no large-sized printer is available.
    The window indicates the number of tiles that will be printed with
    the current settings.
    If the option has been selected, the following options are provided in the Settings section:
    Overlapping
    Overlap of the tiles in mm
    Draw stripline
    If the option has been selected, striplines will be drawn at the cutting edges. We recommend the display of striplines, if the overlap
    is not zero in order to join the individual tiles more precisely.

    6. Confirm with OK.


    The display is printed according to your chosen settings.

    2510

    PTVGROUP

    25 Using interfaces for data exchange

    25

    Using interfaces for data exchange


    There are various ways to exchange data between Visum and other programs:
    Saving a Visum network as abstract network model and exporting it to Vissim or reading
    an ANM network into Visum
    Editing signal controls in an external program (Vissig)
    Reading connections and routes from a file into Visum
    Importing HAFAS data into Visum
    Importing railML data in a Visum network
    Importing EMME/2 data in a Visum network
    Importing TModel data in a Visum network
    Importing SATURN network data into Visum
    Creating a Visum network from OpenStreetMap data
    Reading VDV 452 data into a Visum network or saving a Visum network as VDV 452 data.
    Saving a Visum network in a database or reading data from database in a Visum network
    Saving attributes in a file and reading attribute files in a Visum network
    Exchanging attributes via the clipboard
    Saving Visum data as shapefiles and reading shapefiles into a Visum network (see "The
    Shapefiles interface" on page 2221)
    Saving the graphical display of a Visum network as graphics files in different formats
    Note: Files in text format can generally be exchanged.
    Subjects
    ANM interface
    Editing a signal control in Vissig
    Reading connections and routes
    HAFAS import
    RailML interface
    EMME/2 import
    TModel import
    SATURN import
    OpenStreetMap import
    VDV 452 interface
    Database interface
    Attribute interface
    Graphics interfaces

    25.1

    ANM interface
    Note: ANM export is only available after you activate the Vissim export add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    Using a Visum network, you can generate an abstract network model (ANM), which can then
    be imported into and edited in Vissim (see "Transferring data from Visum to Vissim" on page

    PTVGROUP

    2511

    25.1.1 Transferring data from Visum to Vissim


    2512). Modifications of the Visum network can also be added later to a network previously
    exported and edited in Vissim. In the Vissim network, only the parts affected by the Visum modifications will be adjusted then.
    In addition, you can read ANM files from different sources into an empty Visum network (see
    "Reading an abstract network model" on page 2516).
    Note: Click the
    in Vissim.

    25.1.1

    Vissim node preview button to call a window which shows the node

    Transferring data from Visum to Vissim


    To use Visum data in Vissim, proceed as follows:
    1. First, edit a Visum network.
    2. If you want to export the current network status to Vissim, save an abstract network model
    from Visum to an *.anm file which only contains the data relevant to Vissim (see "Saving an
    abstract network model" on page 2512).
    3. Import the abstract network model (ANM) into Vissim.
    Vissim then generates a Vissim network (*.inp).
    4. Edit the Vissim network.
    Tip: At the same time you can edit the Visum network.
    5. Save another abstract network model from Visum, if you want to export the Visum network
    again later (see "Saving an abstract network model" on page 2512).
    Note: The same *.anm file can be used as for the previous export. The content of the
    previous *.anm file is stored internally.
    6. Import the new abstract network model into Vissim.
    Vissim compares this model with the model delivered by Visum during the previous export and
    determines modified or inserted and deleted objects. Depending on the kind of modification,
    the previous Vissim network is altered in such a way that the Visum modifications are displayed. Parts of the network which were not modified in Visum remain untouched, just like any
    modifications on the Vissim side.

    25.1.2

    Saving an abstract network model


    For the export to Vissim Visum network data can be saved as abstract network model in an
    *.anm file. Routes and matrices can be saved in a route file *.anmRoutes. Both types of files
    can be stored in XML format (see "Brief introduction to the *.xml data format" on page 1872).
    1. In the File menu, select the Export> Vissim (ANM) entry.
    The ANM export parameters window opens.
    2. Make the desired changes.

    2512

    PTVGROUP

    25.1.2 Saving an abstract network model

    Element

    Description

    ANM file

    Network data
    If this option has been selected, the network data of the current network
    can be saved in an *.anm file. Select the directory, if applicable, and
    enter the file name or click the Browse button.

    ANMRoutes file

    Routes
    If this option has been selected, the route information is saved to a route
    file *.anmRoutes. Select the directory, if applicable, and enter the file
    name or click the Browse button.
    Note
    For the import in Vissim, you can specify if you want to read in static or
    dynamic path information.
    Matrices
    If this option has been selected, the demand matrices of the current network are saved to an ANM route file *.anmRoutes. Select the directory, if
    applicable, and enter the file name or click the Browse button.

    3. Select the Vehicle categories tab.


    4. From the selection list, allocate each Visum transport system you want to export to a Vissim
    vehicle category.
    Note: Transport systems of type PuT Walk are not exported to Vissim and are therefore not listed.
    Tip: If you do not want to export a Visum transport system to Vissim, select the Do not
    export entry from the drop-down list.
    5. Select the Driving behavior tab.
    6. In the selection lists, select a Vissim default driving behavior for each Visum link type.
    Tip: If you click the C TRL key and hold it down while clicking the desired rows with the
    left mouse key and click the Multiple button, you can specify driving behavior for multiple link types simultaneously in a separate window.
    7. Select the PuT tab.
    8. In the Vissim stops section, adjust the desired settings.

    PTVGROUP

    2513

    25.1.2 Saving an abstract network model


    Element

    Description

    Stop length from


    stop point attribute

    Via this button, select the attribute from which the length of the PT
    stop in Vissim is to be determined.
    Tip
    You can, for example, create a user-defined attribute for stop
    points, enter data for this attribute and select this attribute.

    As lay-by, if stop
    point attribute is
    'true' or differs
    from 0

    Via this button, select a stop point attribute which defines whether
    the exported stop points are of the street or lay-by type.
    Tip
    You can, for example, allocate an AddValue of 1 to all stop points
    that you want to export as lay-bys, and a 0 to all stop points that
    you want to export as on street stops. If you then select the attribute AddValue, the stop points are exported as desired.

    Node stop point


    before the node, if
    the stop point attribute is true or differs from 0

    Via this button, select the stop point attribute which controls whether the stop point is located before the node or behind it.
    Notes
    This applies to node stop points only.
    For line routes which terminate at a node, the last stop point is
    always placed before the node.
    If no attribute is selected, the stop points will be placed behind the
    node.

    9. In the PT telegrams section, make the desired settings.

    2514

    Element

    Description

    PT line sends PT
    telegrams

    Click this button and select the vehicle journey attribute which
    defines whether the vehicle journey (which is a line in Vissim)
    sends PT telegrams. In Vissim in the PT telegrams window, this
    value is displayed via the check box PT line sends PT
    telegrams.
    If in Visum the attribute value is zero, the check box will be disabled.

    Line

    Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the PT line field.

    Route

    Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Route field.

    Priority

    Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Priority field.

    PTVGROUP

    25.1.2 Saving an abstract network model


    Element

    Description

    Tram length

    Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Tram length field.

    Manual direction

    Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Manual direction field.

    10. Select the Further settings tab.


    11. Make the desired changes.
    Element

    Description

    from / to

    Enter the beginning and the end of a time interval for the Vissim
    simulation period under From and To in the time format (hh:mm:ss).
    Notes
    The beginning and the end of the time interval may fall on two
    consecutive days as long as the period does not exceed 24
    hours.
    If you use a calendar, you also need to select a day of the week
    or a date (see "Selecting a calendar " on page 1511).

    Number of either
    SC signal program
    or daily signal program list for Vissig controllers

    From attribute
    If this option has been checked, click the button and select the
    desired SC attribute. By default, the signal program number is
    selected. Due to this setting, the currently selected Vissig signal
    program is exported. This is useful if each signal control has only
    one signal program or if you have selected the relevant signal program for each signal control for the export. Signal programs can
    be selected manually (see "Properties and options of signal controls" on page 1465 and "Switching off or manually changing
    signal programs in Visum" on page 2558) or are set automatically
    during the procedure sequence (see "Adding procedures to the
    procedure sequence" on page 1848).
    Instead of the signal program number, for example, you can
    select a user-defined attribute which stores the number of the
    daily signal program list.
    Unique number
    If this option has been checked, enter a number in the entry field.
    This is useful, if the same daily signal program list number is used
    by all signal controls in the selected time interval. Example: Monday 101, Tuesday 102 etc.

    Settings for lane


    turns

    Attribute for definition of the reduced-speed zone


    Click this button to choose a lane turn attribute.

    PTVGROUP

    2515

    25.1.3 Saving settings for a Vissim export


    Element

    Description
    Note
    After import into Vissim, this attribute is used to create a reducedspeed zone.

    Note: In Visum, there are nodes that allow turns, but do not have a lane definition. If
    after ANM data export from Visum you want Vissim connectors for these nodes, deactivate the (main) node attribute Use lane definition. Then information on a turn level
    will be used for these nodes, instead of detailed geometry data (i.e. here lane turn
    data).
    12. Confirm with OK.
    The abstract network model is saved.

    25.1.3

    Saving settings for a Vissim export


    You can save the settings for a Vissim export in an ANM export parameter file *.anmp.
    1. In the File menu, select the Export> Vissim (ANM) entry.
    The ANM export parameters window opens.
    2. Make the desired settings (see "Saving an abstract network model" on page 2512).
    3. Click the Save button.
    The Save ANM export parameters window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The current settings are saved to an ANM export parameters file *.anmp.

    25.1.4

    Reading settings for a Vissim export


    You can read settings for a Vissim export from an ANM export parameters file *.anmp.
    1. Make sure the ANM export parameters window is open (see "Saving an abstract network
    model" on page 2512).
    2. Click the Open button.
    The Open ANM export parameters window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings are read from file.

    25.1.5

    Reading an abstract network model


    In Visum, you can read a file *.anm into an empty network and edit the data read from file.

    2516

    PTVGROUP

    25.1.6 Exporting subnetworks via ANM interface


    1. In the File menu, select the Import> ANM entry.
    The Open: ANM network window opens.
    2. Select the desired file.
    3. Click the Open button.
    The ANM file is read in.

    25.1.6

    Exporting subnetworks via ANM interface


    Using the subnetwork generator, you can generate a subnetwork and import it into Vissim via
    the ANM interface. For the subnetwork, you can then carry out the procedure sequence of the
    version opened again.
    1. From the Calculate menu, choose ANM export of a subnetwork.
    The ANM export subnetwork window opens.
    2. Make the desired settings.
    Element

    Description

    Subnetwork
    generator

    Use parameter file


    Select this option to enter the path and name of the subnetwork parameter
    icon to select a file.
    file *.xml, or click the
    Specify parameters for subnetwork generator
    Select this option to click to the Subnetwork generator button and specify
    the settings for the subnetwork generator (see "Subnetwork generation" on
    page 1602)

    Procedure sequence section


    Procedure
    sequence

    No procedure sequence
    If this option is selected, no procedure sequence is carried out for the subnetwork.
    only PrT assignments as in version opened
    If this option is selected, the same PrT assignments are carried out as in
    the opened version.
    Note
    The program performs an assignment for each PrT demand segment with a
    demand matrix exported into a subnetwork. The settings last calculated in
    the opened version are adopted.
    as in opened version
    If this option is selected, only the active procedures of the opened version
    are carried out.
    Note
    The program only accounts for PrT demand segments with a demand

    PTVGROUP

    2517

    25.1.7 Description of the data generated by an ANM import


    Element

    Description
    matrix that were exported into a subnetwork. The settings last calculated in
    the opened version are adopted.
    From file
    Select this option to enter the path and name of a procedure parameter file
    symbol (see "Reading pro*.par or *.xml, or to select a file via the
    cedure parameter settings from file" on page 1868).

    ANM export

    Use parameter file


    Select this option to enter the path and name of the ANM export parameter
    file *.anmp, or click the
    icon to select a file.
    Specify parameters for ANM export
    Select this option to click the Subnetwork generator button and specify the
    settings for the subnetwork generator (see "Saving an abstract network
    model" on page 2512)

    Importing
    If this option is selected, the subnetwork is automatically opened in a new
    files into PTV instance of PTV Vissim.
    Vissim
    Note
    Routes are imported as static routes into Vissim. Do not select this option if
    you want to carry out dynamic assignment in Vissim. In this case, you need
    to import the subnetwork manually via the ANM interface into Vissim.
    3. Confirm with OK.
    The ANM export subnetwork is created.

    25.1.7

    Description of the data generated by an ANM import


    ANM files can only be read into an empty network. PuT data cannot be read in at present.
    The following description explains what network data that will be saved in Visum when importing ANM data.
    ABSTRACT NETWORK MODEL
    An *.anm file contains the XML root element <ABSTRACTNETWORKMODEL>. The following
    elements of the root element are used in Visum.

    2518

    ANM

    Visum

    VERSNO

    ---

    FROMTIME

    ---

    TOTIME

    ---

    NAME

    Name under file info


    Note

    PTVGROUP

    25.1.7 Description of the data generated by an ANM import


    ANM

    Visum
    After an ANM import, in menu File> File info, you can find the
    name and the path of the read in file, as well as the date and the
    time of the import.

    NETWORK

    The subordinate element <NETWORK> contains information on


    inter alia, transport systems, nodes, zones, links, and link types.

    MATRICES

    ---

    ROUTING

    The subordinate element <ROUTING> contains information on


    routes and volumes.

    NETWORK
    An *.anm file contains the superordinate XML element <NETWORK>.
    ANM

    Visum

    LEFTHANDTRAFFIC

    Left-hand traffic in network settings

    The <NETWORK> element contains the following subordinate elements. The mapping of the
    subordinate elements to Visum objects is subsequently described in detail.
    ANM

    Visum

    VEHTYPES

    Determine the type of transport system (PuT, PrT) Each VEHTYPE


    is mapped to a demand segment.

    VEHCLASSES

    List of XmlAnmVehClass objects Each one is mapped to a transport system.

    NODES

    Are mapped to nodes

    ZONES

    Are mapped to zones

    LINKTYPES

    Are mapped to link types

    LINKS

    Are mapped to links

    PTSTOPS

    ---

    PTLINES

    ---

    SIGNALCONTROLS

    Are mapped to signal controls

    VEHCLASSES
    The <VEHCLASSES> are mapped as follows:

    PTVGROUP

    2519

    25.1.7 Description of the data generated by an ANM import


    ANM

    Visum

    VEHTYPEID

    Code and name of the transport system


    Note
    Several VEHTYPES can belong to one VEHCLASS. For each
    VEHCLASS, Visum creates a transport system and a mode, for
    each VEHTYPE a demand segment. The transport system is allocated to the mode with the same name, and the mode is allocated
    to all demand segments created from the VEHTYPES contained in
    that VEHCLASS.

    VEHTYPES
    The <VEHTYPES> are mapped as follows:
    ANM

    Visum

    NO

    ---

    NAME

    Code and name of the demand segment

    VEHCATEGORY

    Type of the transport system (of the corresponding VEHCLASS)


    Note
    If the first VEHTYPE of a VEHCLASS is bus or tram, the entire
    VEHCLASS is mapped as PuT. The categories of all further
    VEHTYPES of this VEHCLASS are ignored.

    NODES
    The <NODES> are mapped as follows:
    Note: Main nodes are not inserted.
    ANM

    Visum

    NO

    Number of the node

    NAME

    Name of the node

    XCOORD, YCOORD, Coordinates of the node


    ZCOORD

    2520

    CONTROLTYPE

    Control type of the node

    IGNOREDIFF

    ---

    NUMLANES

    Number of lanes in roundabout for control type roundabout

    TURNS

    Turn

    LANES

    Lanes

    LANETURNS

    Lane turns

    CROSSWALKS

    Crosswalks

    PTVGROUP

    25.1.7 Description of the data generated by an ANM import


    LANES
    The lane information of a leg has to be consistent. The number of through lanes has to be the
    same as the Number of lanes in Visum.
    The <LANES> are an element of the <NODES>. They are mapped as follows:
    ANM

    Visum

    LINKID

    Link number

    INDEX

    Lane numbers

    POCKET

    Determines if this is a pocket


    Note
    If it is a pocket, the corresponding origin lane has to be located on one of the sides of the pocket.

    POCKETLENGTH

    Indicates the length of the pocket

    WIDTH

    Width

    BLOCKEDVEHICLECLASS- Set of transport systems blocked on this lane


    ES
    STOPLINEPOS

    Leg\stop lines position


    Note
    The leg attribute is the average of the values of all the
    inbound lanes in Visum.

    TRAFFICSIGN

    Determines the major flow of the node


    Note
    If the traffic signs of a node are consistent, a manual major
    flow will be defined on the node.
    If lanes are defined on a node, the information of the traffic
    signs of the lanes overwrites the information on the turns.

    DETECTORS

    Detectors that are allocated to the lane

    DETECTORS
    In ANM files, detectors can be allocated to crosswalks, lane turns and lanes. In Visum, detectors and lane turns cannot be connected directly. Here, detectors are connected to crosswalks
    or lanes. Only one detector can be allocated to a crosswalk. A lane can have several detectors. If a crosswalk with several detectors is read in, only the first detector will be read in.
    The <DETECTORS> are a subordinate element of the <LANES>. They are mapped as follows:
    ANM

    Visum

    TYPE

    Type of the detector

    SCNO

    Number of the signal control

    PTVGROUP

    2521

    25.1.7 Description of the data generated by an ANM import


    ANM

    Visum

    PORTNO

    Channel number

    NAME

    Name of the detector

    POSOFFSET

    Stop line distance

    LENGTH

    Detector length

    AFFECTEDPTLINES

    ---

    AFFECTEDVEHCLASSE- Transport system set of the detector


    S
    LANETURNS
    The <LANETURNS> are an element of the <NODES>. They are mapped as follows:
    ANM

    Visum

    FROMLINKID,
    FROMLANEINDEX,
    TOLINK-ID,
    TOLANEINDEX

    From link number, From lane number, To link number and To


    lane number of the lane turn

    BLOCKEDVEHCLASSES Set of transport systems blocked on this lane turn


    LANETURNPOLY

    ---

    DETECTORS

    Detectors on lane turns are not read in

    SCNO

    Number of the signal control to which the signal group under


    <SGNO> is allocated
    Note
    The number has to be identical for all lane turns and crosswalks of a node.

    SGNO

    Signal group number


    Note
    The signal group belongs to the signal control of the lane turn.

    ORSGNO

    Number of a second signal group

    SIGNALTYPE

    ---

    CROSSWALKS
    Visum crosswalks are read in from the two ANM classes <CROSSWALK> and
    <CROSSWALKSIDE>. In Visum a crosswalk is defined by the leg it belongs to, the direction
    and an index from 1 to 3. So there can be a maximum of six crosswalks belonging to one leg.
    A <CROSSWALKSIDE> on the left side is mapped to a crosswalk with the direction "false" in
    Visum. On the right side, it has the value "true".
    Note: As in Visum there can only be one crosswalk of each type, i.e. up to six all in all, it
    is possible that crosswalk data from the ANM model will be discarded during the import.
    2522

    PTVGROUP

    25.1.7 Description of the data generated by an ANM import


    The <CROSSWALKS> are an element of the <NODES>. They are mapped as follows:
    ANM

    Visum

    LEFTSIDE,
    RIGHTSIDE

    References to the directions

    INLINKID,
    OUTLINKID

    Numbers of the links crossed by the crosswalk

    CHANNELIZEDTUR- Indicates whether the crosswalk leads to a channelized turn


    N
    Note
    The value can only be "true" if the leg\channelized turn length of
    the respective leg is unequal to zero.
    SCNO

    Defines the signal control which is allocated to the node. The


    SCNO has to be the same for all lane turns and crosswalks on the
    node.

    INDEX

    ---

    WIDTH

    Width
    Note
    If references to LEFTSIDE or RIGHTSIDE exist, the width of each of
    the two crosswalks is half the ANM width.

    OFFSET

    ---

    CROSSWALKSIDES
    The <CROSSWALKSIDES> define the direction of the crosswalks. ANM crosswalks have two
    directions.
    ANM

    Visum

    DETECTORS

    Allocated detector

    SGNO

    Signal group

    PEDVOL

    Pedestrian volume

    BIKEVOL

    ---

    XCOORD, YCOORD

    ---

    TURNS
    The <TURNS> are a subordinate element of the <NODES>. The <TURNS> are mapped as follows:

    PTVGROUP

    2523

    25.1.7 Description of the data generated by an ANM import


    ANM

    Visum

    BLOCKEDVEHICLECLASS- Set of transport systems blocked on this turn


    ES
    FROMLINKID, TOLINK-ID

    From link number and To link number of the turn

    TRAFFICSIGN

    Determines the major flow of the node


    Note
    If the traffic signs of a node are consistent, a manual major
    flow will be defined on the node.
    If lanes are defined on a node, the information of the traffic
    signs of the lanes overwrites the information on the turns.

    ZONES
    The <ZONES> are a subordinate element of the <NODES>. They are mapped 1:1 to zones.
    ANM zones have no polygon. Therefore the generated Visum zones do not have polygons either.
    ANM

    Visum

    NO

    Number of the zone

    XCOORD, YCOORD, Coordinates of the zone


    ZCOORD
    Note
    The Z-Coordinates are not read in.
    CONNECTORS

    Connectors of the zone

    CONNECTORS
    The <CONNECTORS> are a subordinate element of the <ZONES>. They are mapped as follows:
    ANM

    Visum

    BLOCKEDVEHCLASSE- Set of transport systems blocked on this connector.


    S

    2524

    NODENO

    Node number

    DIRECTION

    Direction
    Note
    The direction indicates whether the connector leads towards
    zone or away from it. "False" means source, "true" means destination. In Visum each connector automatically has a reverse
    direction. If the reverse connector is not contained in the ANM
    file, the reverse direction is closed to all transport system in
    Visum.

    PTVGROUP

    25.1.7 Description of the data generated by an ANM import


    LINKTYPES
    The <LINKTYPES> are a subordinate element of the <NODES>. The link type set in Visum
    does not change because of the import. Only the names of the link types are used.
    ANM

    Visum

    NO

    Link type number


    Note
    The ANM link type 0 is imported as link type 100 in Visum.

    NAME

    Link type name

    DRIVINGBEHAVIOU- --R
    LINKS
    The <LINKS> are a subordinate element of the <NODES>. They are mapped as follows:
    ANM

    Visum

    ID

    Link number
    Note
    Visum tries to find a matching link number. It can be any string.
    If the ANM file was exported from Visum, the original numbers
    can be reallocated.

    FROMNODENO,
    TONODENO

    From node number, To node number

    NAME

    Name of the link

    LINKTYPENO

    Link type number

    SPEED

    v0 PrT

    NUMLANES

    Number of lanes

    REVERSELINK

    --Note
    The reverse direction is added automatically in Visum.

    BLOCKEDVEHCLASSES Set of transport systems blocked on this link


    LINKPOLY

    Course of the link


    Note
    The link courses of the opposite directions in ANM may differ,
    in Visum they may not. If both courses have the same number
    of elements, the average of the coordinates will be used. If the
    number of elements is not the same, the course with the higher
    number of elements will be used.

    TURNONRED

    Turn on red permitted

    PTVGROUP

    2525

    25.1.7 Description of the data generated by an ANM import


    ANM

    Visum

    TRIANGLEISLANDLENG- Is mapped to the inbound node leg of the associated link.


    TH
    Note
    The attribute Channelized turn length is defined on the leg in
    Visum.
    SLO, ELO, SLOL, ELOL

    These numbers determine the width and the length of the central island in Visum.
    Note
    SLO and ELO indicate the width, SLOL and ELOL indicate the
    length.

    CLO

    ---

    FROMNODERADIUS

    Roundabout exit radius of the leg at the From node


    Note
    The attribute is defined at the leg in Visum.

    TONODERADIUS

    Roundabout exit radius of the leg at the To node


    Note
    The attribute is defined at the leg in Visum.

    PTSTOPS and PTLINES


    Public transit data are currently not imported.
    SIGNALCONTROLS
    The <SIGNALCONTROLS> are mapped to signal controls. They are mapped as follows:
    ANM

    Visum

    SIGNALGROUPS

    Signal groups of the signal control

    INTERGREENS

    Intergreens of the signal control

    NO

    Number of the signal control

    NAME

    Name of the signal control

    CYCLETIME

    Cycle time of the signal control

    TIMEOFFSET

    Offset of the signal control

    SIGNALIZATIONTYP- Signal control type of the signal control


    E
    Note
    The type is determined by the ANM attribute Programfile.

    2526

    CYCLETIMEFIXED

    ---

    PROGRAMNO

    Program number

    PROGRAMFILE

    Determines the signal control type in Visum

    PTVGROUP

    25.1.7 Description of the data generated by an ANM import


    ANM

    Visum
    Note
    Only the signal control types Fixed time, RBC and External are supported. If the attribute is empty, the signal control type is set to
    signal-group based in Visum. Otherwise it gets type External.

    SUPPLYFILE1

    File name

    SUPPLYFILE2,

    ---

    WTT1, 2, 3

    ---

    SIGNALGROUPS
    ANM

    Visum

    NO

    Number of the signal group

    NAME

    Name of the signal group

    GTSTART

    Green time start

    GTSTART2

    ---

    GTEND

    Green time end

    GTEND2

    ---

    RATIME

    ---

    ATIME

    ---

    MINGTIME

    Minimum green time

    MINRTIME

    ---

    ALLRED

    Allred

    SIGNALGROUPTYP- --E
    INTERGREENS
    ANM

    Visum

    FROMSGNO,
    TOSGNO

    From signal group, To signal group

    INTERGREEN

    Intergreen
    Note
    The value is added to the intergreen matrix of the signal control.

    ROUTING
    If the ANM file contains routing information, the routes are assumed to consist of three nodes.
    These nodes are used to uniquely determine a Visum turn. No routes are created in Visum. Instead the given volumes are assigned to user-defined turn attributes per vehicle type.

    PTVGROUP

    2527

    25.2 Editing a signal control in Vissig


    ANM

    Visum

    VEHTYPETIS

    Connects a time interval to an ANM VEHTYPEID


    Note
    An ANM VEHTYPEID is an element of an ANM VEHCLASS that is
    mapped to a transport system in Visum.

    ROUTES

    Turn volumes per transport system

    VEHTYPETIS
    ANM

    Visum

    INDEX

    ---

    FROMTIME, TOTIME

    ---

    VEHTYPEID

    Determines the transport system of the route

    ROUTES
    The import only works for routes with exactly three items. The ANM nodes that the items refer
    to have to correspond to Visum nodes which uniquely define a Visum turn. That means that
    the first node and the third node have to be neighbors of the second node.

    25.2

    ANM

    Visum

    ITEMS

    Pair consisting of a node and an optional link

    DEMANDS

    Can be defined for each Visum transport system. They are mapped
    to user-defined Visum turn attributes.

    FROMZONENO,
    TOZONENO

    ---

    INDEX

    ---

    Editing a signal control in Vissig


    Note: This function is only provided with the Vissig add-on activated (see "Enabling or
    disabling installed add-ons" on page 886).
    Vissig is an external program which enables you to manage complex signal control data. In
    the process, existing signal control data can be converted into new external controllers. The
    external signal control data is saved in a *.sig file. When opening a version file and when determining node impedance via ICA, the data is read from the Vissig file and temporarily converted into Visum data.
    After editing a signal control in Vissig, it is no longer possible to edit the attributes of this signal
    control in Visum. This is only possible if you re-convert the signal control into a Visum control
    again (see "Converting a Vissig signal control into a Visum signal control" on page 2560).
    In Vissig, you can for example edit data as follows:

    2528

    PTVGROUP

    25.2.1 Creating a signal control of the type Vissig


    Edit green times graphically
    Edit stages and display and edit the stage allocations of signal groups graphically
    Time-varying allocation of different signal programs to different time intervals at identical
    nodes
    Manage complex signal controls located in the Visum network
    Edit signal control data for a later Vissim export

    25.2.1

    Creating a signal control of the type Vissig


    If you want to edit a signal control in Vissig, you have to create a Vissig signal control at the
    desired node or main node or convert an existing signal control to a Vissig signal control.
    Creating a new signal control of the type Vissig
    If no signal control has been allocated to the node, insert a signal control of the type Vissig:
    1. In the junction editor, open the selected node or main node (see "Displaying a network
    object in the Junction editor" on page 1439).
    2. Allocate a signal control to the node via the

    Create SC icon.

    The Create SC window opens.


    3. Enter the desired data and select the signal control type Vissig.
    4. Confirm with OK.
    The Save external control window opens.
    5. Enter the file name and the path, if required.
    6. Click the Save button.
    The program Vissig opens for further processing of the signal control.
    Converting an existing Visum-internal signal control for Vissig
    If a signal control of the signal control type Signal group-based or Stage-based is already allocated to the node, convert the signal control:
    1. In the junction editor, open the selected node or main node (see "Displaying a network
    object in the Junction editor" on page 1439).
    2. In the toolbar, click the

    Convert to external controller icon.

    The Save external control window opens.


    3. In the File type selection list, select the entry External control (*.sig).
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    A control file *.sig is saved and the program Vissig opens for further processing of the signal
    control.

    PTVGROUP

    2529

    25.2.2 Editing a controller of the type Vissig

    25.2.2

    Editing a controller of the type Vissig


    Start the Vissig software program to edit a signal control of the type Vissig. You can do this in
    two ways (see "Editing the external control of a signal control" on page 1471):
    from the list of signal controls
    from the junction editor

    25.2.3

    The Vissig window

    (1) List header


    The header displays the program name, the number of the selected signal control and the
    name of the loaded signal control file *.sig.
    (2) Menu bar
    Via the menus, you can call the program functions.
    (3) Toolbar
    The toolbar provides the specific functions.
    (4) Navigator
    Here, you can select the object that you want to edit.
    Tip: You can hide or show the navigator by clicking the

    icon.

    (5) Object display


    Here, the object selected in the navigator is displayed.

    25.2.4

    Setting a language in Vissig


    You can pick a language for the Vissig display. By default, the language set in Visum is used.

    2530

    PTVGROUP

    25.2.5 Specifying general settings for the signal control


    1. In the Edit menu, select the Options entry.
    The Options window opens.
    2. Select the Common tab.
    3. In the drop-down list, select the desired language.
    4. Confirm with OK.

    25.2.5

    Specifying general settings for the signal control


    1. In the navigator, select the My signal control entry.
    2. Make the desired changes.

    25.2.6

    Element

    Description

    Name

    Enter a name for the signal control


    Note
    The name is displayed in the navigator.

    Controller frequency

    Enter the signal control steps per second (standard: 1/second)

    Description

    Enter a specific description of the signal control, if desired.

    Signal states in Vissig


    The following signal states are used in Vissig:
    Element Description
    Red
    Red/Amber
    Green
    Amber
    Flashing
    green
    Flashing
    amber
    Off

    Note: In Vissig, five default signal sequences are predefined. You can allocate these to
    the desired signal group in the respective editing view (see "Editing signal groups" on
    page 2533).

    PTVGROUP

    2531

    25.2.7 Managing signal groups

    25.2.7

    Managing signal groups


    Normally, each approaching flow of a node represents a separate signal group. However, you
    can also display conflict free approaching flows in one signal group. In Vissig, you can insert,
    duplicate, edit or delete signal groups.

    Notes: You can edit signal groups via the toolbar or via the context menu.
    You can edit the No and the Name of the signal group directly in the table by clicking in
    the respective cell. Double-click the Notes column to open the editing view of the respective signal group.
    25.2.7.1

    Creating a signal group


    1. In the navigator, select the My signal control > Signal groups entry.
    2. On the toolbar, click the

    New button.

    The signal group is inserted.


    Note: The next free number is allocated automatically to the new signal group. To each
    newly inserted signal group, the signal state sequence Red Red/Amber Green
    Amber is allocated. You can change it via the drop-down list Default sequence in the
    editing view of the signal group (see "Editing signal groups" on page 2533).
    25.2.7.2

    Duplicating a signal group


    You can duplicate an existing signal group. The new signal group has a new number yet the
    same attributes.
    1. In the navigator, select the My signal control > Signal groups entry.
    2. In the table, mark the signal group that you want to duplicate.

    2532

    PTVGROUP

    25.2.7.3 Editing signal groups

    3. On the toolbar, click the

    Duplicate button.

    The selected signal group is duplicated.


    Note: The next free number is allocated automatically to the new signal group.
    25.2.7.3

    Editing signal groups


    You can, for example, edit the default sequence and associated signal state times.
    1. In the navigator, select the My signal control > Signal groups entry.
    2. In the table, mark the signal group that you want to edit.
    3. On the toolbar, click the

    Edit icon.

    The editing view of the signal group opens.


    4. Make the desired changes.
    Element

    Description

    Name

    Enter a name for the signal group

    Default sequence

    Use the drop-down list to allocate a signal sequence to a signal


    group. Select from the following predefined default sequences:
    Red Red/Amber Green Amber
    Red Green
    Red Red/Amber Green Flashing Green Amber
    Red Green Flashing Green
    Red Green Amber
    Note
    Seven different signal states are used in Vissig .

    Default durations

    Graphic display of the set signal sequence and signal state times
    Notes
    You can edit the predefined duration of a signal state by doubleclicking the desired cell. The default times set here are applied to
    all signal programs. The times of signal group-based signal programs can later be adjusted individually .
    In the case of signal states with a variable duration (Red and
    Green) in the signal state sequence, the entered value is interpreted as minimum duration. In the case of the remaining signal
    states, the value is interpreted as duration.

    Description

    Enter an individual description of the signal group, if desired.

    All changes are applied immediately.

    PTVGROUP

    2533

    25.2.7.4 Deleting a signal group


    25.2.7.4

    Deleting a signal group


    1. In the navigator, select the My signal control > Signal groups entry.
    2. In the table, mark the signal group that you want to delete.
    3. On the toolbar, click the

    Delete icon.

    The signal group is deleted.

    25.2.8

    Managing intergreen matrices


    Intergreen is the time that needs to elapse between the green time end of a clearing flow and
    the green time start of an entering flow. The intergreen guarantees that no conflict arises between the clearing flow and the entering flow. Intergreens are managed in intergreen matrices.
    You can insert, duplicate, edit, and delete intergreen matrices.
    Notes: Intergreens cannot be calculated, they can only be entered. The intergreens and
    the symmetry in the intergreen matrices are not checked.
    You can import intergreens from Excel TM (see "Importing intergreens from Excel" on
    page 2535).

    Notes: You can edit intergreens via the toolbar or via the context menu.
    No and Name of the intergreen matrices can be edited directly by clicking the respective
    cell of the table.
    An intergreen matrix can be selected as Default (see "Editing stage assignments" on
    page 2538). It is marked by an x in the Default column. This intergreen matrix will be applied when creating stages, interstages and stage-based signal programs. If you doubleclick the Default column, the editing view of the associated intergreen matrix opens.
    2534

    PTVGROUP

    25.2.8.1 Creating an intergreen matrix


    25.2.8.1

    Creating an intergreen matrix


    1. In the navigator, select the My signal control > Intergreen matrices entry.
    2. On the toolbar, click the

    New icon.

    The intergreen matrix is inserted.


    25.2.8.2

    Duplicating an intergreen matrix


    You can duplicate an existing intergreen matrix. The new intergreen matrix has a new number
    yet the same attributes.
    1. In the navigator, select the My signal control > Intergreen matrices entry.
    2. In the table, mark the intergreen matrix that you want to duplicate.
    3. On the toolbar, click the

    Duplicate icon.

    The selected intergreen matrix is duplicated.


    Note: The next free number is automatically allocated to the new intergreen matrix.
    25.2.8.3

    Editing an intergreen matrix


    1. In the navigator, select the My signal control > Intergreen matrices entry.
    2. In the table, mark the intergreen matrix that you want to edit.
    3. On the toolbar, click the

    Edit icon.

    The editing view of the intergreen matrix opens.


    4. Enter the desired intergreens directly in the cells.
    Notes: You cannot enter values in the grey cells of the diagonal.
    If you mark a cell in the intergreen matrix, the corresponding cell is also marked in the
    opposite triangle.
    25.2.8.4

    Deleting an intergreen matrix


    1. In the navigator, select the My signal control > Intergreen matrices entry.
    2. In the table, mark the intergreen matrix that you want to delete.
    3. On the toolbar, click the

    Delete icon.

    The intergreen matrix is deleted.


    25.2.8.5

    Importing intergreens from Excel


    You can import intergreens available in Excel TM into Vissig.
    1. Create a new intergreen matrix (see "Creating an intergreen matrix" on page 2535).
    2. Select the data of your choice and press C TRL + C to copy it to your Excel TM file.

    PTVGROUP

    2535

    25.2.9 Managing stages

    Notes: The data in the Excel TM file need to match the format of the intergreen matrix
    so that the import succeeds. You cannot enter values in the grayed out cells of the diagonal.
    You can also enter sections of the Excel TM file. However, the copied section in
    ExcelTM needs to have the same size as the marked section in Vissig.
    3. In Vissig, click the selection field of the intergreen table.

    The entire table is marked.


    4. Press CTRL + V to paste your data from Excel TM into the table.
    The data are pasted into the table.

    25.2.9

    Managing stages
    You can insert, edit, duplicate, and delete stages.

    25.2.9.1

    Adjusting the stage display


    You can adjust the display of the stages on the pages Stages, Stage assignments and Stage
    sequence editing as desired.
    1. In the Edit menu, select the Options entry.
    The Options window opens.
    2. Select the View tab.
    3. Make the desired changes in the Stages section.
    Element

    Description

    Show signal group If the option has been selected, signal group numbers are disids
    played in the graphic view of the stages.
    Use compact view If the option has been selected, a compact view is displayed instead of a to-scale display.
    4. Confirm with OK.
    The stages are displayed according to your chosen settings.
    25.2.9.2

    Creating a stage
    1. In the navigator, select the My signal control > Stages entry.
    2. On the toolbar, click the

    New icon.

    The stage is inserted.


    2536

    PTVGROUP

    25.2.9.3 Editing stages


    25.2.9.3

    Editing stages

    1. In the navigator, select the My signal control > Stages entry.


    2. Make the desired changes.
    Element

    Description

    No

    Click in the cell and enter the desired number.

    Name

    Click in the cell and enter the desired name.

    Pseudo stage

    If this option has been selected, the stage duration is zero. This
    value is not subject to changes, neither during the graphical editing
    of interstages nor during the signal cycle and split optimization.
    By a pseudo stage, two interstages can inseparably be linked to
    each other. In this way, a scenario can be modeled with several
    state changes of a signal group within one interstage.
    This option is only active if the stage has just been created or is not
    used in any interstage.

    Stage diagram

    This column displays graphically the allocations of the stage to the


    signal groups (see "Editing stage assignments" on page 2538).
    For the display of arrows, lane turns need to be provided in Visum.

    The settings are adjusted.

    PTVGROUP

    2537

    25.2.9.4 Duplicating a stage


    25.2.9.4

    Duplicating a stage
    You can duplicate an existing stage. The new stage has a new number yet the same attributes.
    1. In the navigator, select the My signal control > Stages entry.
    2. In the table, mark the stage that you want to duplicate.
    3. On the toolbar, click the

    Duplicate icon.

    The selected stage is duplicated.


    Note: The next free number is automatically allocated to the new stage.
    25.2.9.5

    Deleting a stage
    1. In the navigator, select the My signal control > Stages entry.
    2. Mark the stage that you want to delete.
    3. On the toolbar, click the

    Delete icon.

    The stage is deleted.

    25.2.10 Editing stage assignments


    On the Stage assignments page of the navigator, you can block or clear signal groups for
    each stage or classify their state as not relevant.

    Double-click the desired cell of the table or click an arrow in the graphics to edit the state of a
    signal group in the respective stage. The following states are provided:

    2538

    PTVGROUP

    25.2.10.1 Selecting a default intergreen matrix


    Element Description
    The signal group is cleared in the stage.
    The signal group is blocked in the stage.
    The state of the signal group is not relevant in the stage.
    25.2.10.1 Selecting a default intergreen matrix
    1. In the navigator, select the Stage assignments page.
    2. In the Default Intergreen matrix drop-down list on the right, select the intergreen matrix
    that you want to set as default.
    The intergreen matrix is set as standard and is marked with an x on the Intergreen matrices
    page.
    25.2.10.2 Assigning stages
    1. In the navigator, select the Stage assignments page.
    2. Double-click the cells of the table one by one to clear or block a signal group in the respective stage or classify its state as not relevant.
    Notes: You can adjust the graphic display of the stages via the context menu. Here,
    you can also specify, whether the signal group IDs shall be displayed in the graphics
    or not. Your settings will be applied on the Stage sequence editing page and when
    exporting stage sequences. You can specify this setting and other settings for signal
    programs and interstages under menu Edit > Options > View.
    You can change the width of table and graphics by dragging the divider between the
    table and the graphics with the mouse.
    Your settings are displayed immediately in the graphics.
    Note: If an intergreen matrix has been selected as default, conflicting flows will be
    checked during the assignment of the stages. If you clear conflicting signal groups in the
    same stage, they will be highlighted in red in the table.

    25.2.11 Specifying a stage sequence and creating a signal program


    You can specify the sequence of the stages and then create stage-based or signal groupbased signal programs based on the existing stages.
    All existing stages are displayed in the upper section of the Stage sequence editing page.
    The generated stage sequence is displayed in the lower section.

    PTVGROUP

    2539

    25.2.11 Specifying a stage sequence and creating a signal program

    Notes: You can edit the height of the sections by dragging the divider between the stages
    and the stage sequence.
    You can export a stage sequence as a graphics (see "Exporting a stage sequence" on
    page 2541).
    1. In the navigator, select the Stage sequence editing page.
    2. Click the stage that shall be the first stage of the stage sequence.
    3. Hold the CTRL key down and click the second desired stage.
    4. Hold the CTRL key down and, in the desired order, click all further stages that you want to
    add to the stage sequence.
    5. Open the context menu with a right-click.
    6. Select the desired entry.
    Element

    Description

    Create sequence

    Use this entry to create a stage sequence.

    Add to sequence

    Use this entry to add further stages to an already existing stage


    sequence.
    Note
    Alternatively, you can double-click the desired stage.

    The stage sequence is displayed in the lower section of the page.

    2540

    PTVGROUP

    25.2.11.1 Exporting a stage sequence


    Note: Double-click a stage in the display of the sequence to remove single stages
    from the sequence. Use the Clear sequence entry in the context menu to delete the
    entire stage sequence.
    7. Enter the desired Cycle time for the signal program.
    8. Click the desired button.
    Element

    Description

    Create stage based


    signal program

    Use this button to create a stage-based signal program with


    a preset cycle time.

    Create signal group


    based signal program

    Use this button to create a signal group-based signal program with a preset cycle time.

    Note: Before creating a signal program, you need to select an intergreen matrix as
    default on the Stage assignments page (see "Selecting a default intergreen matrix"
    on page 2539).
    The signal program is calculated. In the navigator, the editing view opens under Signal programs. If required, interstages are created automatically for all transitions between any used
    stages.
    Notes: You can edit the interstages in the navigator under Interstages (see "Managing
    interstages" on page 2549).
    They can also be inserted manually (see "Inserting an interstage manually" on page
    2549). Before creating interstages, you can specify general settings for the optimization
    of the interstages (see "Optimizing interstages" on page 2552).
    25.2.11.1 Exporting a stage sequence
    You can export a given stage sequence as a graphics. You can save stage sequences in the
    formats *.bmp, *.gif, *.png, *.jpeg, *.svg and *.tif.
    Note: Beforehand, you can specify settings for the export (see "Specifying settings for the
    export of graphic files" on page 2555).
    1. In the navigator, select the Stage sequence editing page.
    2. Specify the desired stage sequence (see "Specifying a stage sequence and creating a
    signal program" on page 2539).
    3. Right-click the section of the page that contains the stage sequence.
    A shortcut menu opens.
    4. Select the Export entry.
    The Save As window opens.

    PTVGROUP

    2541

    25.2.12 Managing signal programs


    5. Enter the file name and the path, if required.
    6. Select the desired file type.
    7. Click the Save button.
    The stage sequence is saved in the chosen format.

    25.2.12 Managing signal programs


    A signal program is either stage-based or signal group-based. In the navigator, the type is displayed in italics under the name of the signal program.
    Stage-based signal programs can only be created from stage sequences (see "Specifying a
    stage sequence and creating a signal program" on page 2539). Signal group based signal programs can also be inserted in the navigator.

    Notes: You can create signal group based signal programs in the table on the Signal programs page. All signal programs can be edited, duplicated, deleted and exported.
    In the table, you can directly edit the Number and the Name of the signal programs by
    clicking the desired cell. If you double- click the Intergreens , Cycle time , Offset or
    Switch point columns, the editing view of the signal program opens, where you can edit
    the data.
    25.2.12.1 Creating signal group-based signal programs manually
    You can create signal group-based signal programs from stage sequences (see "Specifying a
    stage sequence and creating a signal program" on page 2539) or insert them manually in the
    navigator. Manually, you insert a signal program as follows:
    1. In the navigator, select the Signal programs page.

    2542

    PTVGROUP

    25.2.12.2 Editing signal group-based signal programs

    2. On the toolbar, click the

    New icon.

    A signal group-based signal program is inserted.


    Note: Stage-based signal programs cannot be inserted manually, but only from stage
    sequences (see "Specifying a stage sequence and creating a signal program" on page
    2539).
    25.2.12.2 Editing signal group-based signal programs
    You can edit signal programs or signal times individually. They can be edited in the graphics
    or in the table.
    1. Open the editing view of the desired signal program.

    2. If necessary, edit the following attributes of the signal program.


    Element

    Description

    Name

    Here, you can adjust the name of the signal group as desired.

    Intergreens

    Here, you can select the desired intergreen matrix (see "Managing intergreen matrices" on page 2534).

    Cycle time

    Here, you can enter the desired cycle time in seconds.

    PTVGROUP

    2543

    25.2.12.2 Editing signal group-based signal programs


    Element

    Description

    Offset

    Here, you can enter the desired offset in seconds.


    Note
    The entire signal plan will then be shifted by the entered time.

    Switch point

    Here, you can enter a time at which you can switch to another
    signal program.

    3. Make the desired changes.


    Note: You can stretch, compress, and edit a signal-group based signal program
    graphically or extract interstages. The respective icon needs to be pressed in the toolbar for editing.
    Element

    Description
    Editing signal states (see "Editing signal times in the graphics" on page
    2545)
    Stretch/Compress (see "Stretching or compressing signal programs" on
    page 2546)
    Extracting interstage (see "Extracting interstage" on page 2546)

    Adjusting the editing view


    You can adjust the display of the editing view as desired.
    1. Right-click the signal program.
    A shortcut menu opens.
    2. Select the desired entry.
    Element

    Description

    Appearance

    The display of the signal times can be Classic or in 3D (3d tubes


    or 3d boxes).

    Resize automatically

    If this entry has been selected, the height of the signal groups is
    adjusted automatically to the size of the window, so that all signal
    groups are displayed.

    Show entire signal Use this entry to adjust the signal program to the window size, so
    program
    that all signal groups and all selected columns are displayed.
    The settings are applied.
    Note: You can adjust the height of the individual cells by dragging the dividers in the row
    headers up or down.
    2544

    PTVGROUP

    25.2.12.2 Editing signal group-based signal programs


    Adjusting the column display
    You can specify which columns shall be displayed in the editing view.
    1. Right-click the signal program.
    A shortcut menu opens.
    2. Select the Edit columns entry.
    The Select time columns to be displayed window opens.
    3. Select the items that you want to display as columns.
    Tip: In the same way, you can remove signal states from the display.
    4. Confirm with OK.
    Your selection of signal states is displayed in the editing view.
    Editing signal times in the graphics
    You can edit the signal times of signal groups directly in the graphics.
    1. On the toolbar, click the

    Edit signal states button.

    2. Click the desired row of the signal program.


    3. Move the mouse over the signal times of the selected row.
    Depending on the location, the mouse pointer changes.
    Element

    Description
    If a hand is displayed, you can shift the entire signal state while
    holding down the mouse key.
    If arrows are displayed, you can shift the start time or end time of
    the signal state while holding down the mouse key.

    Notes: You can only shift signal states with a variable duration. You cannot shift
    signal states with a fixed duration (amber states) alone.
    Reserve times are indicated by a green background and intergreen violations are indicated by an orange background.
    4. Make the desired changes.
    Notes: You can also edit the signal states individually in the table to the right of the
    graphics and overwrite standard times.
    If you move the mouse over the signal times column, you can shift the entire signal program while holding down the mouse key.

    PTVGROUP

    2545

    25.2.12.2 Editing signal group-based signal programs


    Stretching or compressing signal programs
    You can stretch or compress a signal program.
    1. Open the editing view of the desired signal program.
    2. In the toolbar, click the

    Stretch/Compress icon.

    3. Move the mouse over the labels of the time axis of the signal program.
    The mouse pointer changes into a double arrow.

    4. Stretch or compress the signal program as follows.


    Element

    Description
    Compressing a signal program:
    If you move the mouse within the axis labels to the left while holding down
    the left mouse key, the signal program is compressed. The section highlighted in red is cut out.
    Stretching a signal program:
    If you move the mouse within the axis labels to the right while holding
    down the left mouse key, the signal program is stretched. The duration of
    the section highlighted in green is inserted at the beginning of the section
    highlighted in green.
    Note
    If the marked section is grey, you cannot stretch or compress the signal program, because at least one minimum duration is violated.

    Extracting interstage
    In signal group-based signal programs, you can directly cut out a section and then create an
    interstage from it.
    1. Open the editing view of the desired signal program.
    2. On the toolbar, click the

    Extract interstage button.

    3. Move the mouse over the labels of the time axis of the signal program.
    The mouse pointer changes into a cross.
    4. Drag the mouse over the desired section to the right while holding down the mouse key.
    Notes: If the marked section is highlighted in green, the interstage is valid. If the marked section is grey, the interstage is invalid, because an amber time has not been
    marked entirely, for example. Even if a green time is marked entirely, a valid interstage cannot be created.

    2546

    PTVGROUP

    25.2.12.3 Editing stage-based signal programs


    5. Release the mouse button.
    A new interstage is created. The editing view of the interstage opens (see "Editing an interstage" on page 2550).
    Adding second green time to a signal group
    You can add a second green time to a signal group of a signal group-based signal program.
    Here, the signal group needs to have already a green time. This existing green time must be
    short enough so that a second green time still fits. The second green time is regarded for the
    ICA calculation.
    1. Right-click the row of the signal group for which you want to insert a second green time.
    A shortcut menu opens.
    2. Select the Second green time entry.
    A second green time is inserted.
    Note: You can delete one of these green times as follows: Right-click the green time and
    select entry Second green time.
    25.2.12.3 Editing stage-based signal programs
    The editing of stage-based signal programs is similar to the editing of signal group-based
    signal programs (see "Editing signal group-based signal programs" on page 2543). The
    editing functionalities of stage-based signal programs are limited, however.
    In stage-based signal programs, you cannot edit individual signal times. Moreover, the times
    of the amber states are allocated with the standard values of the signal group definitions.
    1. Open the editing view of the desired signal program.

    2. In the toolbar, click the

    PTVGROUP

    Edit signal states icon.

    2547

    25.2.12.4 Exporting a signal program as graphics file


    3. Edit the graphical display as desired (see "Editing signal group-based signal programs" on
    page 2543).
    Element

    Description
    You can shift the start or end markings of the interstages.
    You can shift the labels of the interstages in the header. The start or the
    end of the interstage is then also shifted.
    Tip
    Instead of the interstage number, you can display the name of the
    interstage in the header. You can specify this setting under Options in
    the Edit menu. On the View page of the Options window, the Show full
    interstage name in the stage based signal programs option needs to
    be selected.
    You can shift the interstages within the signal program, if they do not
    have a duration of 0.

    Notes: You can also stretch and compress stage-based signal programs (see "Stretching or compressing signal programs" on page 2546).
    The Extract interstage option is provided for signal group based signal programs
    only.
    25.2.12.4 Exporting a signal program as graphics file
    You can export a created signal program as a graphics. You can save signal programs in the
    formats *.bmp, *.gif, *.png, *.jpeg, *.svg and *.tif.
    Note: Before the export, you can specify export settings (see "Specifying settings for the
    export of graphic files" on page 2555).
    1. In the navigator, select the Signal programs entry.
    2. In the table, select the signal program that you want to export.
    3. Right-click the desired signal program.
    A shortcut menu opens.
    4. Select the Export entry.
    The Save As window opens.
    5. Enter the file name and the path, if required.
    6. Select the desired file type.
    7. Click the Save button.
    The signal program is saved in the chosen format.

    2548

    PTVGROUP

    25.2.13 Managing interstages

    25.2.13 Managing interstages


    Interstages need to be defined between the individual stages of a signal program. Interstages
    are inserted automatically when creating a signal program (see "Specifying a stage sequence
    and creating a signal program" on page 2539) . In case of signal group-based signal programs, interstages can be extracted directly from the signal program (see "Extracting interstage" on page 2546) . They can also be inserted manually (see "Inserting an interstage
    manually" on page 2549).
    Moreover, you can duplicate, edit, and delete interstages under Interstages.

    Notes: In the table, you can directly edit the Number and the Name of the interstages by
    clicking the desired cell. Double-clicking the graphic display of the stages opens the
    editing view of the associated interstage.
    Before editing interstages, you can specify general settings for optimization of the interstages (see "Optimizing interstages" on page 2552).
    25.2.13.1 Inserting an interstage manually
    On the Stage sequence editing page, you can create individual interstages manually or use a
    suitable existing interstage.
    1. In the navigator, select the Stage sequence editing entry.
    2. Create the desired stage sequence (see "Specifying a stage sequence and creating a
    signal program" on page 2539).
    3. Right-click the grey section between two stages for which you want to create an interstage.
    A shortcut menu opens.

    PTVGROUP

    2549

    25.2.13.2 Duplicating an interstage

    4. Select the Interstages > Create entry.


    Tip: You can also select an existing interstage.
    The interstage is inserted and listed under Interstages.
    25.2.13.2 Duplicating an interstage
    You can duplicate an existing interstage. The new interstage has a new number yet the same
    attributes.
    1. In the navigator, select the My signal control > Interstages entry.
    2. In the table, mark the interstage that you want to duplicate.
    3. On the toolbar, click the

    Duplicate icon.

    The selected interstage is duplicated.


    Note: The next free number is allocated to the new interstage.
    25.2.13.3 Editing an interstage
    1. In the navigator, select the My signal control > Interstages entry.
    2. In the table, mark the interstage that you want to edit.
    3. On the toolbar, click the

    Edit icon.

    The editing view of the selected interstage opens.

    2550

    PTVGROUP

    25.2.13.3 Editing an interstage

    4. Make the desired changes.


    Element

    Description

    Name

    Here you can edit the name of the interstage as desired.

    From stage
    To stage

    Here you can select a different From stage or To stage. The selection
    of a new From stage or To stage leads to an automatic recalculation of
    the interstage.
    Notes
    The backgrounds of the phases of the selection lists have different
    colors. The colors have the following meaning:
    White background: the stage is consistent with the interstage. The
    interstage is not recalculated.
    Purple background: indicates a stage that is not consistent with the
    interstage when moving the mouse over the stage. The selection
    leads to an automatic recalculation of the interstage.
    Pink background: the stage is consistent with the interstage. The
    interstage is recalculated.
    (black dash): the stage is not relevant.

    Begin
    End

    Here you can edit the duration of the interstage.


    Notes
    If you want to add time at the beginning of the interstage, you need to
    enter a negative value under Begin for example -2. This way, the stage
    is extended and the entered time is added at the beginning. The time
    entered under End indicates the end of the interstage. You can also
    edit this time. You can only shorten the interstage up to the duration of
    the longest amber state (amber/red amber).

    PTVGROUP

    2551

    25.2.13.4 Optimizing interstages


    5. Edit the signal times, if necessary.
    Note: The signal times of the interstages are edited like the signal times of signal
    group-based signal programs. You can edit the signal times in the graphics and in the
    table (see "Managing signal programs" on page 2542).
    25.2.13.4 Optimizing interstages
    You can specify the following optimization settings for interstages in advance.
    1. In the Edit menu, select the Options entry.
    The Options window opens.
    2. Select the Optimizations tab.
    3. Make the desired changes.
    Element

    Description

    Add minimum
    If the option has been selected, the target signal states of the inditimes in interstage vidual signal groups have at least the minimum duration specified
    for the signal groups.
    Use optimal length If the option has not been selected, the green time ends at the
    in front
    start of the interstage when switching from green to red.
    Use optimal length If the option has not been selected, the green time only begins at
    in back
    the end of the interstage when switching from red to green.
    4. Confirm with OK.
    The settings are applied.
    25.2.13.5 Deleting an interstage
    1. In the navigator, select the My signal control > Interstages entry.
    2. In the table, mark the interstage that you want to delete.
    3. On the toolbar, click the

    Delete icon.

    The interstage is deleted.


    25.2.13.6 Exporting interstages as graphic files
    You can save interstages in the formats *.bmp, *.gif, *.png, *.jpeg, *.svg and *.tif.
    Note: Before the export, you can specify settings for the export (see "Specifying settings
    for the export of graphic files" on page 2555).
    1. In the navigator, select the Interstages entry.
    2. Right-click the desired interstage.
    A shortcut menu opens.
    2552

    PTVGROUP

    25.2.13.7 Exporting interstages as PUA files


    3. Select the Export entry.
    The Save As window opens.
    4. Enter the file name and the path, if required.
    5. Select the desired file type.
    6. Click the Save button.
    The interstage is saved in the selected format.
    Tips: You can also call the export functionality in the editing view of the individual interstages.
    You can also export interstages in format *.pua , if you want to use them in a VAP signal
    control logic in Vissim (see "Exporting interstages as PUA files" on page 2553).
    25.2.13.7 Exporting interstages as PUA files
    In Vissig, you can save interstages in file format *.pua and then use them in a VAP signal control logic.
    1. In the File menu, select the Export> PUA entry.
    The Vissig PUA Export window opens.
    Note: Settings which do not comply with the *.pua format conventions are listed in a
    separate window. The errors need to be fixed before the export.
    2. Click the

    button.

    The Save As window opens.


    3. Enter the file name and the path, if required.
    4. Select the file type *.pua.
    5. Click the Save button.
    6. In the Vissig PUA Export window, select the Start stages.
    7. Click the Export button.
    The interstages are saved in *.pua format.

    25.2.14 Managing daily signal program lists


    You can specify which signal program is used at a given time of the day. This information is
    saved in a daily signal program list. You can create different daily signal program lists, for
    example for weekends or holidays.
    25.2.14.1 Creating a daily signal program list
    1. In the navigator, select the Daily signal program lists entry.
    2. On the toolbar, click the
    PTVGROUP

    New icon.
    2553

    25.2.14.2 Duplicating daily signal program lists


    A daily signal program list is inserted.
    25.2.14.2 Duplicating daily signal program lists
    You can duplicate an existing daily signal program list. The new daily signal program list has a
    new number yet the same attributes.
    1. In the navigator, select the Daily signal program lists entry.
    2. In the table, mark the daily signal program list that you want to duplicate.
    3. On the toolbar, click the

    Duplicate icon.

    The selected daily signal program list is duplicated.


    25.2.14.3 Editing a daily signal program list
    1. In the navigator, select the Daily signal program lists entry.
    2. In the table, mark the daily signal program list that you want to edit.
    3. On the toolbar, click the

    Edit icon.

    The editing view of the selected daily signal program list opens.

    4. Make the desired changes.

    2554

    Element

    Description

    Name

    Here, you can edit the name of the daily signal program list as
    desired.

    Time

    Here, you can allocate signal programs to times, which shall run
    during the specified time.

    PTVGROUP

    25.2.14.4 Deleting a daily signal program list


    Element

    Description
    Notes
    Use the

    New icon to insert further time rows.

    Use the
    Delete icon to remove the selected rows. The icons
    are provided on the toolbar and in the context menu. You can
    adjust the times in the Time column to the nearest second, if you
    click the desired cell a second time.
    Signal Program

    In the drop-down list, you can select a signal program for the specified time period.

    Description

    Enter an individual description of the daily signal program list, if


    desired.

    All changes are applied immediately.


    25.2.14.4 Deleting a daily signal program list
    1. In the navigator, select the Daily signal program lists entry.
    2. In the table, mark the daily signal program list that you want to delete.
    3. On the toolbar, click the

    Delete icon.

    The daily signal program list is deleted.

    25.2.15 Specifying settings for the export of graphic files


    You can export stage sequences, signal programs and interstages as graphics. Before the
    export, you can specify settings for the export.
    1. In the Edit menu, select the Options entry.
    The Options window opens.
    2. Select the Export tab.
    3. Make the desired changes.
    Element

    Description

    Common

    Render mode
    Here, you can specify whether a Fixed scale or a Fixed width
    shall be used.
    Signal group height
    Here, you can specify the signal group height in pixels for all
    graphic exports.

    Signal programs

    PTVGROUP

    Picture width

    2555

    25.2.16 Export to Excel


    Element

    Description
    Here, you can specify the Picture width of the export graphics in
    pixels.
    Pixel per second
    Here, you can specify the number of pixels that represent one
    second in the export graphics.

    Interstages

    Picture width
    Here, you can specify the Picture width of the export graphics in
    pixels.
    Pixel per second
    Here, you can specify the number of pixels that represent one
    second in the export graphics.

    Stage sequence

    Here, you can specify the width of the export graphics in pixels.

    4. Confirm with OK.


    The settings are applied.

    25.2.16 Export to Excel


    You can save any fixed time control data to an Excel file.
    1. In the File menu, select the Export> Excel Workbook entry.
    The Save As window opens.
    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The data are saved in an *.xlsx file.
    Tip: You can also open the file with Microsoft Excel 2003. For the required conversion, install the Microsoft Office Compatibility Pack under www.microsoft.com.

    25.2.17 Detecting inconsistent planning scenarios


    Caused by the interdependencies between the individual data objects of your signal control,
    changes to the properties of an object may lead to inconsistencies in objects that depend on
    the modified object. Those inconsistencies are explicitly permitted so that the user is not restricted in the editing process. The following object checks have been implemented to detect inconsistencies.
    25.2.17.1 Detecting intergreen violations
    An increase of the intergreens can lead to intergreen violations in the associated signal programs or interstages. Inserting additional entries into an intergreen matrix can lead to invalid
    stages.
    In the navigator, open the Stage assignments page.

    2556

    PTVGROUP

    25.2.17.2 Detecting invalid interstages

    Colored backgrounds indicate conflicting green and thus invalid stages.


    25.2.17.2 Detecting invalid interstages
    Subsequent processing of stage allocations may lead to invalid interstages, because the initial
    state or the target state of a signal group has changed. Two cases need to be distinguished
    here:
    If, under Stage assignments, the condition of a signal group are changed from cleared or
    blocked to not relevant, the allocated interstages remain valid and the interstages are not
    recalculated.
    Note: If you want to recalculate the interstages after editing a stage, you first need to
    select a different stage and then the edited stage.
    If under Stage assignments, the state of a signal group is changed to cleared or blocked,
    the allocated interstages become invalid and their names are highlighted in the navigator.
    In the editing view of an invalid interstage, the schematic view of the causing stage and
    the deviating stages in the graphic are highlighted in pink.

    The explicit selection of a stage highlighted in pink leads to the recalculation of the interstage, so that it is consistent again with the edited stage. Editing interstages can lead to
    inconsistent associated signal programs. If this is the case, the name of the signal program
    is highlighted in the navigator.

    PTVGROUP

    2557

    25.2.18 Returning to Visum from Vissig

    25.2.18 Returning to Visum from Vissig


    When signal control processing in Vissig is finished, you can return to Visum.
    Notes: The external signal control can no longer be edited in Visum. However, you can
    select a different signal program for it or switch it off (see "Switching off or manually changing signal programs in Visum" on page 2558 and "Automatically changing or switching
    off signal programs in Visum" on page 2558).
    Furthermore, you can convert a Vissig control into a Visum signal control (see "Converting a Vissig signal control into a Visum signal control" on page 2560).
    1. Edit your signal control in Vissig as desired.
    2. In the File menu, select the Save entry.
    3. In the toolbar, click the

    Back to Visum icon.

    The Vissig window closes.


    Notes: The name of the *.sig file is saved and referenced in the Visum version file.
    On the Visum Junction editor toolbar, click the
    Update control data of the SC button
    to update the control data later in Visum, if required.

    25.2.19 Switching off or manually changing signal programs in Visum


    In Visum, just one signal program is allocated to a signal control. If in Vissig a signal control
    includes several signal programs then only the currently allocated signal program will be displayed in the junction editor. You can change to another signal program or switch the signal
    control off.
    1. Open the Signal timing view of the Junction editor (see "Using the Junction editor" on page
    1435).
    2. In the Signal program drop-down list in the top right corner, select the desired signal program.
    Tip: Alternatively, you can change the signal program in the External tab (see "Properties and options of signal controls" on page 1465) or set it automatically during the
    procedure sequence (see "Adding procedures to the procedure sequence" on page
    1848).
    The signal program is changed. The signal timing is displayed in the lower section of the junction editor. The currently selected signal program is taken into account by the concerned procedures, i.e. assignment with ICA, signal cycle and split optimization and signal offset
    optimization.

    25.2.20 Automatically changing or switching off signal programs in Visum


    In the Visum procedure sequence you can automatically change the signal programs of Vissig
    signal controls. Here, Visum transfers the desired time and the number of the desired daily

    2558

    PTVGROUP

    25.2.20 Automatically changing or switching off signal programs in Visum


    signal program list to Vissig. To Visum, Vissig returns the number of the particular signal program and the green times. Visum then converts all signal controls to the signal program which
    applies for that time. If no signal program exists for the chosen time, the signal control will be
    switched off.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Select the desired position in the procedure sequence and add the procedure Set signal
    programs from the Assignments category.
    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Set signal programs window opens.

    4. Make the desired changes.


    Element

    Description

    Reset the signal programs of external controls to the signal program that is active at
    the following time

    Time to be set for all external controllers

    Number of the daily signal program list to


    be used

    External daily signal program list which


    is to be used

    Note: The signal programs are implemented accordingly, including for RBC controllers. For RBC controllers, the number of the daily signal program list to be used
    will be ignored.
    5. Confirm with OK.
    6. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The signal programs are changed. The currently selected signal programs are taken into
    account by the concerned procedures, i.e. assignment with ICA, signal cycle and split optimization and signal offset optimization.

    PTVGROUP

    2559

    25.2.21 Converting a Vissig signal control into a Visum signal control

    25.2.21 Converting a Vissig signal control into a Visum signal control


    You can convert an Vissig controller to Visum. This leads to the loss of all data that go beyond
    the Visum data model. All other data are imported. In Visum, the signal control type is set to
    signal group-based.
    1. In the junction editor, open the selected node or main node (see "Displaying a network
    object in the Junction editor" on page 1439).
    2. In the toolbar, click the

    Convert SC to Visum controller icon.

    3. Click OK to confirm.
    The signal control is converted.

    25.3

    Reading connections and routes


    Instead of using connections and routes determined in Visum, you can read connections and
    routes from files.

    25.3.1

    Connections:importing
    You can import assigned connections from a connection file *.con into the current network(see
    Fundamentals: Chpt. 7.10.7 , page 513).
    Note: This master file contains information on other files for the import. They are generated automatically with the same number and an appended index number during
    connection export (see "Timetable-based assignment:Connection export tab" on page
    2047).
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Select the desired position in the procedure sequence, and add the procedure Connection
    import from the Assignments category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. In the row of the added procedure, click in the Variant/file column.
    The icon
    4. Click the

    is displayed.
    icon.

    The Open: PuT connections window opens.


    5. Select the desired file.
    6. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell of the Variant/file column and enter
    the path and file name manually.

    2560

    PTVGROUP

    25.3.2 Importing routes


    7. Make sure the added procedure is marked. Then, in the Operations section, click the Edit
    button.
    The window Connection export parameters opens.
    Tip: Alternatively, in the Reference object(s) column, double-click the empty box.
    8. Select Read additively if required.
    Notes: Select this option to add the volume data of the connection file to the existing
    data. This way, the volumes of existing network paths are not replaced by the data of
    the connection file. Fare point and fare data saved to paths (and/or legs) are replaced
    by the data in the connection file.
    If in a demand segment, paths are saved as routes, additive reading is not possible.
    If you have assigned multiple demand segments separately, you cannot perform an
    additive connection import.
    9. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The connections and their volumes are imported and inserted into the network similar to PuT
    assignment results, i.e. as paths and network volumes (see Fundamentals: Chpt. 7.10.7 , page
    513).
    Notes: Assigned connections outside the analysis period of the current network are not
    imported.
    During the connection import the same settings are considered that apply to the assignment. For example, the connections are aggregated to routes, if the respective option
    is selected (see "Settings for saving PuT assignment results" on page 1996).

    25.3.2

    Importing routes
    You can import externally calculated PrT routes for a demand segment from a route import file
    *.rim.
    Note: After a dynamic assignment in Vissim you can generate route import files *.rim from
    a Vissim network additionally to a Visum network file containing the basic Vissim network
    (nodes/edges) via the menu File> Export> Visum> Nodes/edges. They contain the
    aggregated routes and volumes from the last Vissim simulation run generating a path file
    *.weg for one calculation interval each of the dynamic assignment.
    1. On the toolbar, click

    Open Procedure sequence.

    The Procedure sequence window opens.


    2. Select the desired position in the procedure sequence and add the procedure Route
    import from the Assignments category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. In the row of the inserted procedure, click the button in the Reference object(s) column.
    PTVGROUP

    2561

    25.3.3 Extended route import


    The Select demand segment window opens.
    4. From the drop-down list, select the demand segment for which you want to import PrT routes.
    5. Confirm with OK.
    The demand segment selected is listed in the Reference object(s) column.
    6. In the row of the added procedure, click in the Variant/file column.
    The icon
    7. Click the

    is displayed.
    icon.

    The Open: PrT routes window opens.


    8. Select the desired file.
    9. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell of the Variant/file column and enter
    the path and file name manually.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The PrT routes are imported and will be stored in the network like a PrT assignment result.
    Tip: Alternatively externally calculated network and route volumes can be imported for
    multiple demand segments (see "Extended route import" on page 2562).
    Example of a route import file *.rim
    $VISION
    $ROUTEIMPORT
    $VERSION 1
    *FromZoneNo;ToZoneNo;Vol(3DecPlaces);NodeNo;...NodeNo;-1
    50;40;4,000;11;12;5;-1
    50;10;1,000;11;18;17;6;1;-1
    50;70;3,000;11;18;8;7;17;-1
    50;40;2,000;11;12;-1

    25.3.3

    Extended route import


    The extended route import provides flexible possibilities when reading in externally calculated
    PrT assignment results in the form of route import files *.rim.
    In addition to or instead of PrT routes you can import externally calculated PrT assignment
    results (network volumes for links, turns, main turns and connectors) for one or multiple
    demand segments into Visum.
    You can read in dynamic and static assignment results.

    2562

    PTVGROUP

    25.3.3 Extended route import


    Network and route volumes can be imported for an unspecified assignment period or for
    individual time intervals and optionally the currently defined analysis time intervals can be
    replaced by the imported time intervals.
    1. On the toolbar, click the

    Open 'Procedure sequence' window button.

    The Procedure sequence window opens.


    2. Select the desired position in the procedure sequence and add the procedure Extended
    route import from the Assignments category (see "Setting up and starting the procedure
    sequence" on page 1847).
    3. Make sure that the inserted operation is marked and click the Edit button in the Operations
    section.
    The Parameters: Extended route import window opens.
    4. Make the desired changes.
    Element

    Description

    Use time intervals


    If the option has been selected, the analysis time intervals specified in Visum are replaced by time intervals contained in the
    from file as anaroute import file.
    lysis time intervals
    If the option has not been selected, the values of the time intervals from the route import file are aggregated consistently with the
    analysis time intervals defined in Visum
    5. Confirm with OK.
    6. In the row of the added procedure, click in the Variant/file column.
    The icon
    7. Click the

    is displayed.
    icon.

    The Open: PrT routes window opens.


    8. Select the desired file.
    9. Click the Open button.
    The file name appears in the Variant/file column.
    Tip: Alternatively, you can double-click the cell of the Variant/file column and enter
    the path and file name manually.
    10. Execute the procedure (see "Executing procedures in the procedure sequence" on page
    1857).
    The PrT assignment results are imported.

    PTVGROUP

    2563

    25.3.3 Extended route import


    Example of a route import file *.rim for extended route import
    The following data are contained in a *.rim file.
    $VISION
    $VERSION:VERSNR;FILETYPE;LANGUAGE
    3.000;PrtExtRouteImport;ENG
    $ASSIGNEDDEMANDSEGMENT:CODE;CALCNETVOLUMES
    C;1
    H;1
    $TIMEINTERVAL:CODE;NAME;DAYINDEX;STARTTIME;ENDTIME
    * NAME(def=CODE) and DAYIND(def=1) is optional
    3_4;Null-Eins4;1;03:00:00;04:00:00
    0_1;Null-Eins1;1;00:00:00;01:00:00
    1_2;Null-Eins2;1;01:00:00;02:00:00
    2_3;Null-Eins3;1;02:00:00;03:00:00
    $ROUTE:NO;FROMZONENO;TOZONENO;VOLVEH_DSEG(P,AP);VOLVEH_DSEG(C,0_1);
    VOLVEH_DSEG(C,1_2);VOLVEH_DSEG(C,2_3);VOLVEH_DSEG(C,3_4);VOLVEH_DSEG(H,3_4)
    1;100;200;1211.000;1212.000;1213.000;555;666;777
    2;100;200;1221.000;1222.000;1223.000;555;666;777
    3;100;200;1231.000;0;3213.000;555;666;777
    4;100;200;1241.000;4213.000;;555;666;777
    $ROUTEITEM:ROUTENO;INDEX;NODENO
    1;1;10
    1;2;11
    1;3;20
    1;4;21
    1;5;30
    1;6;31
    1;7;40
    $LINKVOLUME:LINKNO;FROMNODENO;IMP_PRTSYS(C,2_3);IMP_PRTSYS(C,3_4);
    QUEUELENGTH(AP)
    1;10;3849;1111;10
    1;11;1780;2222;20
    2;11;2619;2222;11
    2;20;3980;1112;20
    3;20;1819;1113;20
    3;21;2580;443;21
    4;20;360000000;4;20

    $TURNVOLUME:FROMNODENO;VIANODENO;TONODENO;QUEUELENGTH(AP);
    QUEUELENGTH(1_2);IMP_PRTSYS(H,1_2);IMP_PRTSYS(C,AP);
    IMP_PRTSYS(C,2_3)
    10;11;10;44;55;56;77;33
    10;11;20;;;0;0;0
    10;11;41;;;0;0;0
    11;10;11;;;0;360000000;0
    11;10;12;;;0;0;0
    11;20;11;;;0;360000000;0
    11;20;21;;;0;0;0
    11;20;40;;;0;360000000;0
    20;11;10;;;0;0;0

    2564

    PTVGROUP

    25.4 HAFAS import


    $MAINTURNVOLUME:FROMNODENO;FROMCORDONNODENO;TOCORDONNODENO;TONODENO;QUEUELENGTH
    (AP);QUEUELENGTH(1_2);IMP_PRTSYS(H,1_2);IMP_PRTSYS(C,AP);
    IMP_PRTSYS(C,2_3)
    20;21;31;40;144;155;156;177;133
    40;31;21;20;244;255;256;277;233
    20;21;21;20;344;355;356;377;333
    40;31;31;40;444;455;456;477;433
    $CONNECTORVOLUME:ZONENO;NODENO;DIRECTION;IMP_PRTSYS(L,2_3);
    IMP_PRTSYS(C,1_2);QUEUELENGTH(0_1);QUEUELENGTH(AP)
    100;10;O;3;4;1;1
    100;10;D;2;650;6;3
    100;11;O;0;0;;
    100;11;D;0;0;0;
    100;12;O;0;0;0;
    100;12;D;0;0;0;
    200;31;O;0;0;0;
    200;31;D;0;0;0;
    200;40;O;0;0;0;
    200;40;D;0;0;2000;
    200;41;O;0;0;0;
    200;41;D;0;0;0;

    Notes: If, in table ASSIGNEDDEMANDSEGMENT, for an existing demand segment Calcnetvolumes = 1 is set, the network volumes are determined from the routes and, for
    the analysis period, distributed to all links, turns, and connectors of the routes. Otherwise
    they are set to 0.
    Existing impedances of network objects are determined per network object by summing
    them up along the routes and interpreting them as journey time in seconds. If no impedance is defined, t0 is used.

    25.4

    HAFAS import
    Note: This function is only provided with the HAFAS import add-on (see "Enabling or
    disabling installed add-ons" on page 886).
    The HAFAS interface enables users to import data sets in HAFAS raw data format in Visum.
    This procedure corresponds to the (non-additional) reading of a network (see "Opening and
    saving a network file and adding comments" on page 844), i.e. data are read into an initially
    empty network.
    The HAFAS raw data format consists of many text files with a fixed column format and no precise naming convention. For the HAFAS import you specify the files to be imported and further
    import parameters. The settings can be saved in a HAFAS project file *.haf and re-used later.
    You can import the following files of the HAFAS raw data format:
    Train types
    Stop directory
    Stop coordinates
    Connections between stops
    Time shifts of stops

    PTVGROUP

    2565

    25.4.1 Importing HAFAS data


    Stop-related transfer walk times
    Transfer times related to the pair of vehicle journeys
    Timetable period data
    Valid days of the vehicle journeys
    Operator data
    Combined runnings
    Timetable data files

    25.4.1

    Importing HAFAS data


    1. In the File menu, select the Import> HAFAS entry.
    The HAFAS import settings window opens.
    2. Select the Files tab.
    3. Depending on the type of HAFAS data file for which you want to import data, click the
    respective button

    The Open <file type> window opens.


    Notes: For the Timetable file(s) file type you can select more than one file. By clicking
    the
    button in the Timetable file(s) row, the Timetable files window opens. Here
    you can add several timetable files to or delete from the selection via the Add und
    Delete button.
    Be careful if reading includes a destination coach train. Select the pulling train data
    files first and the destination coach train data files then.
    4. Select the desired file.
    5. Click the Open button.
    File name and directory are used for the File name entry.
    Tip: You can delete the allocation of a file to be imported by clicking the respective
    Delete button.
    Note: If additionally obligatory HAFAS data files of a different file type are required to
    complement a selected HAFAS data file, these file types are marked by a red bar.
    6. Decide whether warnings are to be displayed on screen during importation process.

    2566

    Element

    Description

    No warnings

    If this option has been selected, no warnings are displayed on the


    screen during importation process. However, warnings are saved
    to the message file if the options Save warnings and details to
    the message file and Create new file are selected (see "Specifying settings for protocol files" on page 876).
    PTVGROUP

    25.4.1 Importing HAFAS data


    7. Select the Transport systems tab.
    Note: The settings in the Transport systems tab are only accessible if a HAFAS data
    file of the Train types file type has been selected.
    8. Make the desired changes.
    Element

    Description

    Import

    In this column, you can specify per transport type, whether you want to
    import it as a Visum transport system. If the check box is disabled, the
    train type will not be imported.

    Train type
    code
    Train type
    name

    Display of the HAFAS train type attributes

    TSys code
    TSys name

    Short and long name of the imported transport system


    By double clicking into the desired cell you can change short and long
    names.
    Tip
    You can aggregate several train types to one Visum transport system
    using the same TSys code and TSys name for all train types.
    Note
    For all PuT transport systems one mode and one demand segment only
    are generated.

    Check all

    Via this button, you may select all train types for the import.

    Uncheck all

    Via this button, you may uncheck all train types for the import.

    9. Select the Calendar tab.


    10. Make the desired changes.
    Element

    Description

    Calendar type From the drop-down list you may select a calendar type to specify the
    calendar period.
    Note
    The calendar types Weekly calendar and Annual calendar are only
    provided, if the Calendar / valid days add-on is activated (see "Enabling or disabling installed add-ons" on page 886).
    Dates

    PTVGROUP

    Calendar period for which vehicle journeys are imported


    Note
    If a timetable period data file is imported, the complete time table

    2567

    25.4.1 Importing HAFAS data


    Element

    Description
    period is used as calendar period.
    From, To
    button you can open a calendar and select the beginning
    Via the
    or the end of the calendar period with a mouse click on the desired
    date.
    Notes
    This option is only available if the Weekly calendar or Annual calendar is selected as calendar type.
    All vehicle journeys with at least one valid day within the range of
    dates are imported if no filter is defined.

    Filters

    Using the filter you may limit the number of vehicle journeys to be
    imported to those journeys operating on the days you specified.
    Click the
    button to open a calendar. To select a key date, click the
    date of your choice.
    Click the Add button to add a key date to the list.
    Click the Delete button to delete the key dates selected in the list.
    Via the Delete all button you delete all key dates simultaneously.

    Time shifts

    Select this option to enter a postponement of arrival and departure


    times of journeys at stops in the Resulting time shift box, or import the
    postponement from a time shift file and calculate it for each stop,
    based on the evaluation point in time.
    Via the
    button you can open a calendar and select the key date
    with a mouse click on the desired date. Enter the evaluation point in
    time in time format (hh:mm:ss).

    11. Select the Vehicle journey names tab.


    Note: In this tab you define from which data the names of the lines and vehicle journeys will be generated in Visum. The lists on the left contain the data used to create
    the names in the order specified. The list to the right stores the data which is available
    for the naming process.
    12. In the Line name section in the list to the left, select the entry on top of which you would
    like to add another name component.
    13. In the Line name section in the list to the right, select the entry which you would like to add
    to the line name.
    14. Click the

    icon.

    The entry is made on the left above the currently selected entry.

    2568

    PTVGROUP

    25.4.1 Importing HAFAS data


    15. In the Line name section at the Separator prompt, enter a character for the separation of
    the naming components, if applicable
    Note: Semicolon is not permitted as separator.
    16. Add further entries, if required.
    Note: You can remove an entry from the list to the left by selecting the desired entry
    and clicking the

    button.

    17. In the Vehicle journey names section, specify the naming conventions accordingly.
    18. Select the Destination coach journey names tab.
    Note: In this tab you define, from which data the names of the lines and vehicle journeys are to be generated for destination coach journeys in Visum. For a better differentiation between other lines and vehicle journeys, you can set up a character
    string that appears in a certain position in the name.
    19. In the Decisive train is section, select the desired option.
    Element

    Description

    First pulling journey

    If this option has been checked, the following data is gained from
    the train data in the first row *KWZ: HAFAS train type code,
    HAFAS line name, HAFAS train number, HAFAS operator administration and the Visum transport system code.

    Top-ranking pulling journey

    If this option has been checked, the data mentioned above is gained from the *KWZ data row of the top-ranking train. If there are
    several top-ranking trains, the first one will be regarded.

    20. Enter the desired character strings in the entry fields Fixed name component for line and
    Fixed name component for vehicle journey.
    Note: For the name generation, the appropriate string is provided as Mandatory
    name component.
    21. Like in the Vehicle journey names tab, set up the data for the naming of lines and vehicle
    journeys.
    22. Confirm with OK.
    The selected HAFAS data are imported.
    Note: During a HAFAS import, a separate line route is generated from each HAFAS
    vehicle journey. Then you can aggregate line routes (see "Aggregating line routes" on
    page 1360).
    PTVGROUP

    2569

    25.4.2 Notes on the imported HAFAS data

    25.4.2

    Notes on the imported HAFAS data


    Train types
    HAFAS train types are transferred with the following data:
    Train type code (up to 3 digits)
    Product category
    Train type name
    List of stops, stop coordinates
    Number, name and coordinates of the stations are taken from both files.
    For each station, a combination of a node, a stop, a stop area, and a stop point are inserted at
    a ratio of 1:1:1:1. Name and code are both made up of the HAFAS name. If the HAFAS name
    contains several alternative names separated by $, only the first name is transferred.
    If you import a stop coordinates file only, no names are generated.
    Connections between stops
    Stop groups (2nd field of information) are turned into stops with several stop areas.
    In the process, all stop points positioned to the right of mark :are aggregated below the stop
    on the left side in case it exists (meta-stops are thus ignored) and if it has not already been
    assigned in a previous step.
    The stops of the stop points to be aggregated are deleted and their stop areas are allocated to
    the superordinate stop on the left side.
    Transition relations (1st field of information) are interpreted in different ways. If there is a transition within a stop (group), the transition time (optionally accurate to the nearest second) is
    saved to the matrix of transitions between the corresponding stop areas of the stops. The
    matrix can be asymmetric.
    However, if there is a transition between stop points of different stops, a link is created which is
    open to the PuTWalk type of transport system in the stated direction.
    Time shifts of stops
    Stop-related transfer walk times
    The general transfer times between any train types apart from the IC (German express train)
    are transferred. The transition time is entered at the diagonal item of the transition matrix that
    corresponds to the specified stop point between the stop areas (of its stop). By default the diagonal is initialized by the value below 9999999and then can be overwritten by special
    values for individual stop points.
    Note: If in the HAFAS files no transition time between stop areas is defined, Visum uses
    as walking time the maximum walk time between the stop areas within the stop.

    2570

    PTVGROUP

    25.4.2 Notes on the imported HAFAS data


    Transfer times related to the pair of vehicle journeys
    At the respective stop specific transfer walk times are applied on time profile level. Per HAFAS
    trip number/administrative ID, a specific transfer walk time is set for all the time profiles determined by the line number and operator name during HAFAS import. At the stop of the stop
    area, a specific transfer walk time from time profile 1 to time profile 2 with the indicated time is
    inserted.
    Timetable period data, valid days of the vehicle journeys
    The start date and the end date of the timetable period are copied.
    If No calendar is set, each section of a vehicle journey section is inserted with the valid day
    daily. If the Weekly calendar is set, the valid days code is interpreted according to HAFAS
    modulo 1 week. If the Annual calendar is set, the valid days code is adopted unchanged
    apart from the specified range of dates if it is shorter than the timetable period.
    Operator data
    The number, the abbreviated name and the full name of the operator are transferred. Via the
    administrative ID an operator number can be assigned to a vehicle journey. If this file is missing, no operators are assigned.
    Combined runnings
    Combined runnings are transferred as coupled time profiles.
    From the pairs (train number, administrative ID) for the two trains the corresponding time profiles are determined. They then can be coupled between the items that correspond to the specified FromStops/ToStops of the coupled section.
    Note: Only absolute stop numbers - no indices - are permitted in the combined runnings
    file. For loop trips and side trips the information is thus not clear. In their case, the first
    occurrence of the From Stop/To Stop is used and no coupling is inserted if the To Stop is
    located before the From Stop.
    Timetable
    The timetable file stores the data for the following issues: Trains (*Z), destination couch journeys (*KW), destination couch trains (*KWZ), prohibited alighting/boarding for destination coaches (*B), regular services (*T), valid days (*A VE), line codes (*L), and line courses. Service
    trips are ignored when importing.
    Trains (*Z): For each train, a combination of a line, a line route, a time profile and a vehicle
    journey is created at a ratio of 1:1:1:1. The line name is created based on the settings in
    the Vehicle journey names tab. The transport system of the line is set to the transport system that you have assigned to the train type (*G) of the train (for more than one row of the
    highest train type = lowest product category). The line route is always named 1. The
    direction is derived from the coordinates of the origin and destination stop. The time profile is always named 1. The vehicle journey number is assigned consecutively and the
    vehicle journey name created according to the settings in the Vehicle journey names tab.
    The operator is determined by the administrative ID and the information from the HAFAS
    operator data file. The course of the line route and the time profile are constructed

    PTVGROUP

    2571

    25.4.2 Notes on the imported HAFAS data


    according to the information by HAFAS on the course of the train. Since the network does
    not contain any links initially, links are created step-by-step in between nodes of consecutive stops and opened up to the transport system of the line. If a link already exists, it
    is opened up to the new transport system only where applicable. Different trains are displayed on the line routes of a sole line if they are given the same line name according to
    the user-defined formation of names. This way, for example, all trains can be arranged in
    lines according to their transport system. If the attributes Headway number and Headway time are indicated, Visum creates several vehicle journeys (and vehicle journey sections) for HAFAS trips.
    *Rows marked *A VE (valid days): For each *row marked A VE a vehicle journey section
    is inserted. Its valid day is determined in the same way as described above for the timetable period data file. If a Visum valid day with the same bit string already exists, it is reused; otherwise it is newly created. The ID of a valid day is generated arbitrarily, e.g. the
    HAFAS valid day number is used. Valid day dailycan be clearly identified in HAFAS
    (000000) and is assigned to the invariably existing Visum valid day daily (ID 1). If the Weekly calendar is set, no valid days with the same content are created, i.e. valid days with
    an identical OR projectionbut a deviant HAFAS number might be assigned to a single
    valid day.
    *Rows marked *L (line ID): If a line ID is available, it is used when generating a line name
    and vehicle journey name in Visum, where applicable. Moreover, the newly-created
    Visum line is assigned to a Visum main line whose name is identically equal to the
    HAFAS line ID. Merely on the level of main lines, trips imported from HAFAS can be combined securely, as different train types and thus different transport systems might occur
    within a HAFAS line ID.
    Destination coach (*KW): Section by section, destination coaches are hauled by trains. In
    Visum, a destination coach is a separate vehicle journey which is coupled section-wise
    with a pulling vehicle journey. The vehicle journey data is gained from the references to
    the pulling train. This is why pulling train data is required prior to the import of destination
    coaches.
    For each destination coach journey, a line route is created and a time profile as well. A
    line is also created, if a line with the required properties does not yet exist. For the vehicle
    journey and the line, the names are generated according to the settings in the Destination coach journey names tab. Since a destination coach does not store any administrative management or line or train type data, this data is gained from a train which is
    listed in the subsequent rows *KWZ. Here you have the choice: Either the first row can be
    used or the row of top-ranking train. If there are several top-ranking trains, the first one will
    be regarded. Line routes and time profiles are named similar to those of usual vehicle journeys.
    According to row *B, destination coaches can be excluded from boarding/alighting. This
    information is read into the time profile. However, the following restriction applies in
    Visum: At the start of a coupled section, boarding has to be permitted, and alighting has to
    be permitted at the end of a coupled section. Thus, prohibitions can only be regarded as
    long as the given standards are not violated.
    Route course: Departure and arrival times of value 9999 are interpreted as if boarding
    and alighting were not permitted. Vehicle journeys indicating 9999 at the From Stop or the
    To Stop are ignored. A warning is recorded in the log file.

    2572

    PTVGROUP

    25.4.3 Saving settings for HAFAS import

    25.4.3

    Saving settings for HAFAS import


    You can save the settings and HAFAS data files selected for HAFAS import as a HAFAS project file *.haf.
    1. In the File menu, select the Import> HAFAS entry.
    The HAFAS import settings window opens.
    2. Make the desired settings (see "Importing HAFAS data" on page 2566).
    3. Click the Save button.
    The Save PuT interfaces project window opens.
    4. Enter the file name and the path, if required.
    5. Select the file type *.haf.
    6. Click the Save button.
    The current settings and the HAFAS data selected are saved as a HAFAS project file *.haf.

    25.4.4

    Reading settings for the HAFAS import


    You can load settings and HAFAS data files for HAFAS import from a HAFAS project file *.haf.
    1. Make sure the HAFAS import settings window is open (see "Importing HAFAS data" on
    page 2566).
    2. Click the Open button.
    The PuT interfaces project window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings and the HAFAS data are read according to the HAFAS project.

    25.4.5

    Resetting the HAFAS import settings


    You can restore the default settings for HAFAS import and delete the allocations of HAFAS
    data files.
    1. Make sure the HAFAS import settings window is open (see "Importing HAFAS data" on
    page 2566).
    2. Click the Reset button.
    The settings are reset and the allocations of the HAFAS data files are deleted.

    25.5

    RailML interface
    Note: This function is available if you have activated the add-on modules RailML import
    and RailML export (see "Enabling or disabling installed add-ons" on page 886).
    The railML import interface enables users to import timetable data sets in railML format in
    Visum. This procedure corresponds to the additional reading of a network (see "Reading

    PTVGROUP

    2573

    25.5.1 Importing RailML data


    network data additionally" on page 851), i.e. data are read into an existing network. You can
    also export Visum to railML (see "Exporting Visum data to railML" on page 2585).
    RailML is a data format which has been agreed between different parties involved as joint
    universal data format. It is available in form of an XML scheme containing descriptions with
    regard to contents. Details can be found under http://www.railml.org. In Visum this format can
    be imported. For the import please specify the file to be read as well as further import parameters. You can save the settings to a railML project *.puti and use them again later (see
    "Saving settings for railML import" on page 2584 and "Reading in settings for railML import"
    on page 2584).
    The import focuses on timetable data and reads other schemes only if they are necessary for
    the import of the timetable data (see "Notes on imported railML data" on page 2581). Thus,
    objects of the line hierarchy can be created in Visum.

    25.5.1

    Importing RailML data


    Note: You can import files of *.xml type realizing the railML scheme in version 2.0 or
    2.1. For the import you select only one file, which can refer to others via an "include" statement. These have to be in the same directory as the selected file.
    1. In the File menu, select the Import> RailML entry.
    The RailML import parameters window opens.
    2. Select the Basic settings tab.
    3. Click the

    button next to Import from file.

    The Open RailML file window opens.


    4. Select the desired file.
    5. Click the Open button.
    File name and directory are adopted into the entry field.
    6. Specify any further settings you need.

    2574

    Element

    Description

    Directions

    The directions of the line routes created in Visum are determined


    by the train number. If no train number is specified, the outward
    direction is assumed.
    If a number is specified, you can use the option to determine whether even numbers are allocated to outward directions and
    uneven numbers to the opposite direction or vice versa.

    Line route

    As route information a series of stop points is available in Visum.


    Additionally information on arrival and departure times as well as
    boarding and alighting. In Visum a route point on the line route is
    created for each stop point with time data. You can use the fol-

    PTVGROUP

    25.5.1 Importing RailML data


    Element

    Description
    lowing options to generate further route points.
    Create additional route points for all explicitly stated stop
    points
    If this option has been selected, route points are created for all
    stop points contained in the railML file and found in the target
    network, even those without times and lengths.
    Create additional route points for all stop points with 'to'
    length data
    If this option has been selected, route points are created also for
    all stop points to which 'to' length data are attached in the
    railML file.
    Do not create additional route points
    If this option has been selected, route points are only created for
    stop points with time data.

    For a change of the


    railML category,
    create a separate
    vehicle journey for
    each category

    If this option has been selected, Visum creates a separate


    vehicle journey for each category if the railML category is changed.
    Note

    Couple train sets


    (vehicle journey
    sections are merged, if applicable)

    If this option is not selected, no coupling data is read in.

    Do not show warnings during the


    import

    If this option has been selected, the output of warnings can be


    suppressed.

    So, for example, empty trips are turned into vehicle journeys.

    7. Select the Transfer to target network tab.


    8. Make the desired changes.

    PTVGROUP

    2575

    25.5.1 Importing RailML data


    Element

    Description

    Use the secondary matching


    attribute for stop
    points (track information)

    If this option has been selected, you can select an attribute to


    obtain track information within an OCP ("trackinfo") in a Visum
    attribute.
    Note
    Equivalents in the target network can be searched using different
    levels of details. You can select either a primary Visum attribute
    only to model OCPs on one stop point each or additionally select
    a secondary Visum attribute for track information within the OCP.
    Furthermore, you can compare link information.

    Use link information

    If this option has been selected, you can choose matching attributes for link information.
    If this option has not been selected, line routes are determined
    via the shortest path search.

    Identify blank and


    underscore in primary stop point
    matching attribute

    2576

    If this option has been selected, prior to the search for correspondences blanks are replaced by underscore in the railML
    file and in Visum.
    Notes
    This option makes sense if in the file to be read blanks are used
    instead of underscores.
    Since in Visum the codes required have to be unique, the import
    will fail if two stop points differ only by this sign in the identification
    attribute.

    PTVGROUP

    25.5.1 Importing RailML data


    Element

    Description

    Transfer of Operation Control


    Points (OCP) to
    stop points

    Here you can allocate Visum stop point attributes to the OCPs in
    railML.
    Notes
    The selection of railML elements depends on the content of the
    railML file you want to read in.
    In the target network you can create user-defined stop point attributes with matching names and store the information there.
    Primary matching attribute (course-independent)
    Selection of a course-independent railML element whose information shall be stored in a Visum stop point attribute
    Secondary matching attribute (track info, course-dependent)
    Selection of a course-dependent railML element whose information shall be stored in a Visum stop point attribute
    Notes
    This is only possible if you have selected the Use the secondary
    matching attribute for stop points (track information) option.
    This is track information within an OCP.

    Matching attriIf the Use link information option has been selected, you can allobutes for link infor- cate Visum link attributes to the following railML attributes.
    mation
    For railML attribute 'section'
    Here you allocate the 'section' attribute to a link attribute, which
    adopts the link number.
    For railML attribute 'trackinfo'
    Here you allocate the 'trackinfo' attribute to a link attribute, which
    adopts the track information on the link.
    Note
    If you insert a user-defined attribute for the direction, you can allocate the desired direction to the links in Visum.
    Note: During railML import in Visum missing or unclear information on the course of
    line routes is always determined via shortest path searches.
    9. Select the Transport systems tab.
    Note: To access the settings in the Transport systems tab, in the Basic settings tab,
    select a railML file.
    10. Make the desired settings.

    PTVGROUP

    2577

    25.5.1 Importing RailML data


    Element

    Description

    Import

    In this column, you can specify per transport type, whether you want to
    import it as a Visum transport system. If the check box is disabled, the
    train type will not be imported.

    Train type
    code
    Train type
    name

    Display of the 'abbreviation' and 'name' attributes from the railML file.
    Note
    If you move the mouse over the columns, a quick info additionally displays the value of the 'description' and 'trainUsage' railML attributes.
    This is useful, for example, if you want to avoid the import of empty trips.
    Those have the 'deadrun = true' characteristic.

    TSys code
    TSys name

    Short and long name of the imported transport system


    Notes
    Use the drop-down list in the TSys code column to select the desired
    transport system. It contains all PuT line TSys of the network.
    You can aggregate several train types to one Visum transport system
    using the same TSys code and TSys name for all train types.

    Check all

    Via this button, you may select all train types for the import.

    Uncheck all

    Via this button, you may uncheck all train types for the import.

    11. Select the Calendar tab.


    12. Make the desired changes.
    Element

    Description

    Target network
    calendar

    Calendar type
    Here the calendar type of the loaded Visum network is displayed.
    Notes
    If no calendar is set, the valid day daily will always be selected.
    An import in a weekly calendar is not possible.
    Please set a different calendar type, if necessary, prior to the
    import into Visum.

    Filters

    Source network calendar


    Here the range of dates of the source file is displayed.
    The imported range of dates is intersected with the calendar set
    in Visum.
    Via the filter you can select days from the range of dates. Then
    only journeys operating on the days you have specified are imported.
    button to open a calendar. To select a key date, click
    Click the
    the date of your choice.

    2578

    PTVGROUP

    25.5.1 Importing RailML data


    Element

    Description
    Click the Add button to add a key date to the list.
    Click the Delete button to delete the key dates selected in the list.
    Via the Delete all button you delete all key dates simultaneously.

    Time shifts

    Time shift in target network with respect to UTC


    Here the arrival and departure times of trips in Visum can be shifted with respect to the Universal Time Coordinated. A shift of one
    hour corresponds to the Central European Time (CET).

    13. Select the Names tab.


    Notes: In this tab you define from which data the names of the lines and vehicle journeys will be generated in Visum. The lists on the left contain the data used to create
    the names in the order specified. The list to the right stores the data which is available
    for the naming process.
    If in Visum there is a line with the set name components, they will be used if the transport system fits. If there is no line with set name components, a new one is created. If
    there is a line with the same name but a different transport system than the one required, the import for this line will fail. This situation can be avoided if the transport system code is selected as component of the line name.
    14. In the Line name section in the list to the left, select the entry on top of which you would
    like to add another name component.
    15. In the Line name section in the list to the right, select the entry which you would like to add
    to the line name.
    16. Click the

    icon.

    The entry is made on the left above the currently selected entry.
    17. In the Line name section at the Separator prompt, enter a character for the separation of
    the naming components, if applicable
    Note: Semicolon is not permitted as separator.
    18. Add further entries, if required.
    Note: You can remove an entry from the list to the left by selecting the desired entry
    and clicking the

    button.

    19. In the Vehicle journey name section, specify the naming conventions accordingly.
    20. Enter the desired character strings in the entry fields Fixed name component for line and
    Fixed name component for vehicle journey.
    Note: For the name generation, the appropriate string is provided as Mandatory
    name component.
    PTVGROUP

    2579

    25.5.1 Importing RailML data


    21. In the Line route name section, make the desired settings.
    Element

    Description

    Line route name


    like vehicle journey name

    If this option has been selected, the name of the vehicle journey
    is also used for the line route and the time profile.
    Note
    If there is already a line route or time profile with this name, it will
    be suffixed (by 1, 2, etc.).

    Name of the line


    If this option has been selected, the combination first OCP_last
    route from first
    OCP is used for naming the line route, if necessary, comOCP and last OCP plemented by a consecutive number.
    of the course
    22. Select the Attributes tab.
    23. Make the desired changes.
    Element

    Description

    Flag of imported
    vehicle journeys

    Flag
    Enter the desired name for the import.
    in attribute
    Selection of the timetable attribute storing the ('formation ID') information
    Store vehicle information in attribute
    The vehicle information read is saved as text in the selected
    vehicle journey section attribute (see "Identification of vehicles
    (from RollingStock)" on page 2581).
    Note
    For each railcar a vehicle journey section is created.

    Attribute selection Information


    for further inforListing of the imported 'trainPart' elements
    mation
    Note
    From each element one or several vehicle journey sections are
    created.
    Object
    Visum object created from the element
    Target attribute
    Attribute storing the information
    Note
    You can select the attributes individually or generate user-defined target attributes for all source attributes.

    2580

    PTVGROUP

    25.5.2 Notes on imported railML data


    Element

    Description

    Generate

    Via this button you can generate automatically user-defined attributes for all non-allocated source attributes.

    Note: If you do not want to use an attribute, you can select the entry No selection in
    the attribute selection window. The respective railML information is then not read in.
    The same applies to the optional Flag and the Vehicle information.
    24. Confirm with OK.
    Die railML data is imported.
    Note: Data which cannot be imported are transferred to the log file (see "Notes on imported railML data" on page 2581).

    25.5.2

    Notes on imported railML data


    From the following railML subschemas, elements are adopted into Visum:
    Infrastructure
    RollingStock
    Timetable
    Below it is explained which elements of the individual subschemas are imported and how the
    course is determined in Visum based on the railML data.
    Allocation of Operation Control Points to stop points
    From the 'Infrastructure' subschema only the 'OperationControlPoints' (OCPs) element is
    taken. It contains the OCPs used in the timetable. In Visum OCPs are modeled as stop points.
    For this purpose, per each entry the OCP ID and the selected OCP matching attribute is retrieved and this attribute value is searched for in the values of the stop point matching attribute. All
    corresponding stop points are checked further. If the value does not exist, the OCP cannot be
    allocated and will be listed in the log file. Normally only part of the OCPs exist in the Visum target network. The import fails if an OCP cannot be allocated. However, a warning will be displayed which allows aborting the import process if an OCP which is relevant with regard to
    traffic cannot be allocated. An OCP is considered as relevant with regard to traffic if its 'propService' element is specified and the 'passenger' attribute is true.
    If the target network has several stop points with a matching attribute value, the exact allocation depends on the track information. If the use of track information within an OCP has been
    switched off or if the stop points in the matching attribute for track information equally contain
    the same values, the allocation for this OCP will fail, too.
    An import in case of non-allocated, relevant OCPs may lead to a loss of stops for the vehicle
    journeys concerned or to their split-up into several journeys.
    Identification of vehicles (from RollingStock)
    From this subschema the vehicles ('formation ID') are transferred. For each railcar a vehicle
    journey section is created and allocated with the textual representation of a vehicle group

    PTVGROUP

    2581

    25.5.2 Notes on imported railML data


    which subsequently can be realized as concrete vehicle combinations. The number of entries
    matches the number of railcars among the vehicles of 'formation'.
    Identifying vehicle journeys
    Vehicle journeys and the related objects of the line hierarchy in Visum are generated for the
    'train' elements of the railML data stock. These 'train' elements themselves do not comprise
    any information on the course, but contain so-called 'trainPart' elements. These carry information on the course and the times as well as - optionally - on the valid day, on the vehicles,
    the operator, the line and the category. Hereby, a 'train' element contains 1 to n 'trainPartSequence' elements with a reference to 1 to n 'trainPartSequence' elements. Each 'trainPartSequence' element represents one local section, the 'trainPart' elements displayed herein are
    vehicle groups/train parts which jointly cover this section. Accordingly, the 'ocptts', i.e. the
    details of place and time of the 'trainParts' occurring together in a 'trainPartSequence' element,
    have to match.
    This structure allows two different views on the same data. They are realized by trains of the
    'operational' type as well as by those of the 'commercial' type. A train of the 'operational' type
    describes the network view, according to which there can only be one train at each time and
    each place. If several train parts are operating together (coupling, destination coaches etc.),
    there is only one operational train which combines several 'trainParts' on this local section
    i.e. in this 'trainPartSequence'.
    The commercial train describes the traffic view. Hereby each vehicle group takes a defined
    path, possibly stretching over several train numbers. Therefore, jointly operating vehicle
    groups are in separate commercial trains.
    In Visum the focus is on 'commercial trains' mainly. Each 'commercial train' becomes one or
    several vehicle journeys. 'Train' elements of operational type are not read as vehicle journeys.
    The course of a vehicle journey, i.e. the data of its line route and its time profile, result section
    per section from the course data of the integrated 'trainPart' elements. Hereby, the 'trainParts'
    become vehicle journey sections in Visum - apart from a few exceptional cases.
    The data of a vehicle journey are determined from a 'train' element of 'commercial' type by processing the 'trainPartSequence' entries one after the other as follows:
    First of all, such 'trainParts' whose 'category' cannot be found in the categories to be read
    are filtered out. Furthermore, all 'trainParts' whose valid day does not operate in the given
    filter period are ignored.
    If the 'trainPartSequence' is not empty and if there has not been a course so far, the transport system of the vehicle journey is determined to be the transport system allocated to the
    railML 'category' to which the 'trainPart' element belongs.
    If there is a course from previous 'trainPartSequences', it will be checked optionally whether the transport system allocated to the first 'trainPart' matches that of the vehicle journey. If not, a new vehicle journey will be created, if the options have been selected
    accordingly.
    Is the 'trainPartSequence' of the 'train' is empty after the filtering, it will be ignored. If there
    has already been a non-empty 'trainPartSequence' for the current trip (i.e. the trip has

    2582

    PTVGROUP

    25.5.2 Notes on imported railML data


    already a non-empty course), a new trip will be created. This means that the same commercial train may generate several trips.
    If the 'trainPartSequence' is not empty, the course for the first 'trainPart' element found is
    calculated (the courses of the other 'trainParts' have to be matching).
    For that purpose each OCP occurring on the course (represented by an 'ocptt' element) is allocated to a stop point in Visum. This is achieved by comparing the contents
    of the matching attribute on source (railML data) and target side (Visum stop point
    attribute). If there are several stop points and if track information is used, that stop point
    is taken which lists the specified track information in its secondary matching attribute. If
    an OCP cannot be allocated, it will be deleted from the course.
    Arrival and departure times are directly transferred from the railML data, whereby the
    times of 'scope' 'published' are preferred.
    If link information is used, too, links with the specified link number and direction (in the
    sense of timetable links, not Visum link numbers) starting from each stop point of the
    course are searched, thus clearly determining the path to the subsequent stop point. If
    no matching links can be found, a shortest path search to the subsequent stop point
    will be started in the target network.
    If the import does not use link information, a shortest path search from each stop point
    to its successor on the course will be started.
    In each case, the paths found between the stop points form the line route.
    From each 'trainPart' element of a 'trainPartSequence' one or several vehicle journey sections may be created. The number of vehicle journey sections corresponds to the number
    of railcars contained in the 'formation' of the railML data related to that 'trainPart'. As
    vehicle information each vehicle journey section contains a text describing this 'formation'.
    No vehicle units or combinations are generated or allocated in the target network.
    Normally each of the journey sections stretches over exactly that part of the course originating from this 'trainPartSequence' and is provided with the valid day of the
    'trainPart' element.
    The case in which the change from one 'trainPartSequence' to the subsequent one
    coincides with a passing ('ocptt' of type 'pass') is an exception. In the Visum data model
    a vehicle journey section can start or end only at a stop. Therefore, in this case the
    vehicle journey sections cover the change of 'trainPartSequence' connected to a passing. This generates data distortions if the train ('formation') or the valid day changes
    here. But it has to be considered a data error in the input data.
    The case in which the vehicle journey is coupled to two subsequent 'trainPartSequence' elements with the same partners constitutes another exception. Since in
    Visum vehicle journey sections must not begin or end in the coupled section, here, too,
    the vehicle journey sections are extended over the change, or alternatively the coupling is neglected.
    If a vehicle journey including its sections is created that way, the vehicle journey sections
    which do not overlap locally but have the same valid day and identical vehicle (and other)
    information are aggregated.

    PTVGROUP

    2583

    25.5.3 Saving settings for railML import


    Note: You can enter the number of calendar days a vehicle journey section is served,
    then output the data to a Visum attribute in order to perform projection calculations. To do
    so, in the RailML import parameters window, in the Attributes tab of Number of occurrences, assign the target attribute of your choice or create a user-defined attribute (see
    "Importing RailML data" on page 2574).
    Identifying couplings
    A coupling group in Visum is created when two or more 'trainPart' elements from different 'commercial trains' operate jointly in one 'operational train', i.e. which is in the same 'trainPartSequence'. This means that the 'operational trains' are read and checked for such
    'trainPartSequence' elements. For each 'trainPartSequence' containing 'trainPart' elements
    belonging to different 'commercial trains' found a coupling is generated for the part of the
    course it describes.
    Example for filtering the categories: Filtering the categories is useful to cut off usually undesired sequences before and after the actual train course in Visum. A typical train course of an
    IC from Hamburg, for example, does not start in Altona but as an empty coaching stock from
    Langenfelde to Altona. In railML this is displayed as separate trainPartwith a separate
    trainPartSequenceand normally filtered out, so that in Visum the vehicle journey actually
    starts in Hamburg-Altona only, having the IC product then and not the empty coaching stock.

    25.5.3

    Saving settings for railML import


    You can save your settings and the railML data file selected for railML import to a railML
    project file *.puti.
    1. In the File menu, select the Import> RailML entry.
    The RailML import parameters window opens.
    2. Make the desired settings (see "Importing RailML data" on page 2574).
    3. Click the Save button.
    The Save PuT interfaces project window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The current settings and the railML data selected are saved as a railML project file *.puti.

    25.5.4

    Reading in settings for railML import


    You can read in settings and railML data files for the railML import from a railML project file
    *.puti.
    1. Make sure that the RailML import parameters window is open (see "Importing RailML
    data" on page 2574).
    2. Click the Open button.
    The Open railML project window opens.
    3. Select the desired file.

    2584

    PTVGROUP

    25.5.5 Resetting the railML import settings


    4. Click the Open button.
    The settings and the railML data are read according to the railML project.

    25.5.5

    Resetting the railML import settings


    You can restore the default settings for railML import and delete the allocation of the railML
    data file.
    1. Make sure the RailML import parameters window is open (see "Importing RailML data"
    on page 2574).
    2. Click the Reset button.
    The settings are reset and the allocations of the railML data file are deleted.

    25.5.6

    Exporting Visum data to railML


    You can export your Visum data to railML . An *.xml file is generated according to railML
    schema 2.1. It contains stop point, timetable, and vehicle data. Export your data as follows.
    1. In the File menu, select the Export> RailML entry.
    The RailML export parameters window opens.
    2. Select the Basic settings tab.
    3. Next to Export to file, click the

    button.

    The Save RailML file window opens.


    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The file name and directory are adopted into the entry field.
    6. Make the settings of your choice.
    Element

    Description

    Extent of exported Export active vehicle journey sections only


    data
    Select this option to only export active vehicle journey sections
    and their infrastructure.
    Line route

    Export only route points as route course


    Select this option to only export route points as route courses.
    If this option is not selected, all stop points that lie on a line route's (active) vehicle journey section served are exported as route
    courses.

    Timetable period

    PTVGROUP

    You can set the timetable period, if the export network has a weekly calendar or no calendar.
    Note
    This section is not available, if an annual calendar has been set.

    2585

    25.5.7 Saving settings for railML export


    Element

    Description
    Start of the exported timetable period
    Click this button to specify a start time for the timetable period
    exported.
    End of the timetable period
    The end of the timetable period depends on the start time chosen.

    7. Select the Attributes tab.


    8. Make the desired changes.
    Element

    Description

    Attribute selection Data object


    for data objects in List of export file elements
    export file
    Target attribute
    Attribute of export file element to which information is saved.
    Source attribute
    Visum attribute used to create the element
    Note
    Here you select the attributes you want to export. Only those attributes for which you have chosen a source attribute are exported.
    If you do not want to use an attribute, you can select the entry No
    selection in the attribute selection window.
    9. Confirm with OK.
    The data are exported to an *.xml file.

    25.5.7

    Saving settings for railML export


    You can save the railML export settings as a PuT interfaces project *.putp.
    1. In the File menu, select the Export> RailML entry.
    The RailML export parameters window opens.
    2. Make the desired settings (see "Exporting Visum data to railML" on page 2585).
    3. Click the Save button.
    The Save PuT interfaces project window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The current settings are saved as a PuT interfaces project file *.putp.

    2586

    PTVGROUP

    25.5.8 Loading settings for railML export

    25.5.8

    Loading settings for railML export


    You can load settings for railML export from a railML project file *.putp.
    1. Make sure the RailML export parameters window is open (see "Exporting Visum data to
    railML" on page 2585).
    2. Click the Open button.
    The PuT interfaces project window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings of the PuT interfaces project. are loaded.

    25.5.9

    Resetting railML export settings


    You can restore the default settings for railML export.
    1. Make sure the RailML export parameters window is open (see "Exporting Visum data to
    railML" on page 2585).
    2. Click the Reset button.
    The settings are restored.

    25.6

    EMME/2 import
    Note: This function is only available after you activate the EMME Import add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    EMME/2 is a software program meant for demand modeling, whose models can be imported
    into Visum.
    The EMME/2 data to be imported are contained in different data files. They can be selected
    individually for import.
    EMME/2 data file

    Contains

    In Visum imported as

    EMME/2 modes

    Modes

    Transport systems, modes, demand segments

    EMME/2 network

    Network

    Zones, nodes, links, connectors, stop


    points, stop areas, stops

    EMME/2 turns

    Turn

    Turn

    EMME/2 vehicles

    Vehicles

    Vehicle units, Vehicle combinations

    EMME/2 transit lines

    Line routes

    Lines, line routes, time profiles

    EMME/2 trip tables

    Trips (demand)

    Demand matrices

    PTVGROUP

    2587

    25.6.1 Importing EMME/2 data

    25.6.1

    Importing EMME/2 data


    1. In the File menu, select the Import> EMME/2 entry.
    The EMME/2 - import parameters window opens.
    2. Select the Files tab.
    3. Depending on the type of EMME/2 data file for which you want to import data, click the
    respective button

    The Open <file type> window opens.


    4. Select the desired file.
    5. Click the Open button.
    File name and directory are used for the File name entry.
    Note: You can delete the allocation of a file to be imported by clicking the respective
    Delete button.
    6. Select the Units tab.
    7. Make the desired changes.
    Element

    Description

    Lengths / Speeds

    From the drop-down list select the units used for EMME/2 length
    and speed data.
    Kilometers
    Miles
    Factor
    Factor by which the EMME/2 values are converted into the units
    used in Visum.

    Coordinates

    From the drop-down list select the units used for EMME/2 coordinates:
    Feet
    Kilometers
    Miles
    Factor
    Factor by which the EMME/2 values are converted into the units
    used in Visum.
    Note
    Visum adopts the coordinates unaltered. The network scale is
    adjusted in order to reproduce the coordinate and length conditions correctly (see "Editing the coordinate system and scale"
    on page 2207).

    8. Select the Links tab.


    2588

    PTVGROUP

    25.6.1 Importing EMME/2 data


    9. Make the desired changes.
    Element

    Description

    Capacity PrT

    From the drop-down list you can select whether links featuring a
    constant PrT capacity are to be imported or whether the value of
    an EMME/2 user-defined attribute is to be adopted for the PrT
    capacity per link.
    Constant
    If this option has been selected, enter the PrT capacity value.

    v0 PrT

    From the drop-down list you can select an EMME/2 user-defined


    attribute whose value is to be copied per section for the speed in
    the unloaded network.

    Note: For links Visum interprets parameter a in EMME/2 files and automatically inserts
    both directions of a link with the same attribute values.
    10. Select the Transport systems tab.
    Notes: The settings of the Transport systems tab are only available if you have selected an EMME/2 modes file for import.
    If an EMME/2 modes file has been selected for import, EMME/2 transport systems are
    automatically allocated to Visum types of transport systems applying the following
    rule:
    EMME/2 mode type 1 = Visum transport system type PrT
    EMME/2 mode type 2 = Visum transport system type PuT
    EMME/2 mode type 3 (transit walk links) = Visum transport system type PuTWalk
    EMME/2 mode type 4 (walk links) = Visum transport system type PrT
    11. If necessary, you can modify the allocation of EMME/2 transport systems to Visum types of
    transport systems via the respective Visum TSysType drop-down list.
    Notes: For each PrT transport system a mode and a demand segment are generated
    automatically, yet just one single mode and one demand segment for all PuT,
    PuTWalk and PuTAux transport systems.
    If no PuTWalk transport system is imported, a standard transport system PuTWalk is
    generated which is permitted on all connectors, yet on no links.
    12. Select the Demand matrices tab.
    Note: The settings of the Demand matrices tab are only available if you have selected an EMME/2 modes file for import.
    13. Per demand segment for which you want to import an EMME/2 demand matrix click the
    button

    The Open window opens.


    PTVGROUP

    2589

    25.6.1 Importing EMME/2 data


    14. Select the desired file.
    15. Click the Open button.
    File name and directory are used for the File name entry.
    Notes: You can delete the allocation of a file to be imported by clicking the respective
    Delete button.
    Alternatively, you may read demand matrices of a foreign format directly into Visum or
    into the matrix editor (see "Managing matrices" on page 1607).
    Additionally to the demand matrix a standard time series is generated for the PuT
    demand segment.
    16. Select the TFF tab.
    Note: The settings of the TFF tab are only available if you have selected an EMME/2
    transit lines file for import.
    17. Make the desired changes.
    Element

    Description

    TTF index

    Index number of the TTF function to be imported (Transit Time


    Function) for calculating the speeds of the line routes. It is read
    from the selected EMME/2 transit lines file.

    Link attribute

    You can specify whether the speed of the line route is to be constant or whether it is to be calculated from a link attribute and a
    factor.
    Via the button you may select in a separate window either the
    Constant speed or any link attribute.

    Factor / speed

    If Constant speed has been selected as link attribute, enter the


    speed value.
    If any link attribute has been selected, enter a factor the attribute
    value is multiplied by.

    Notes: For each imported EMME/2 stop of an EMME/2 line Visum creates a node, a
    stop, a stop point, and a stop area - the stop area being allocated to the node.
    Since EMME/2 does not distinguish between stops and nodes (stops, zones, nodes =
    centroids), each centroid in the course of a line route is interpreted as a stop unless
    it is explicitly stated in EMME/2 that the line route does not stop at this point.
    Incomplete EMME/2 line route courses can be completed similarly as to reading networks (see "Reading a network file with incomplete line routes or system routes" on
    page 861).
    18. Select the General tab.
    19. Make the desired changes.
    2590

    PTVGROUP

    25.6.2 Saving the settings for the EMME/2 import

    Element

    Description

    Create a separate
    node for each
    EMME/2 connector and connect it
    to the network by
    an additional link

    If this option has been selected, a zone and a node are created for each EMME/2 centroid as well as a connector that links the
    two. For all EMME/2 links from/to the EMME/2 centroid, links
    from/to the new node are generated.
    If the option has not been selected, EMME/2 centroids are just
    read as zones. Visum generates a zone and per EMME/2 link a
    connector.

    Generate both line


    If this option has been selected, both directions of a line route
    are generated on the basis of EMME/2 line data.
    directions from
    line data
    Note
    By means of the layover time (lay= layover) that is specified in
    EMME/2, Visum decides where to begin / end a line route course.
    If a layoveris specified within the course of an EMME/2 line
    route, Visum creates two directions, i.e. two line routes. If a layoveris specified at the end of the course or not defined at all,
    Visum generates just one direction and one line route.
    If the option has not been selected, only one direction is generated.
    20. Confirm with OK.
    The selected EMME/2 data are imported.

    25.6.2

    Saving the settings for the EMME/2 import


    You can save the settings and the selected EMME/2 data files for the EMME/2 import as
    EMME project *.emme.
    1. In the File menu, select the Import> EMME/2 entry.
    The EMME/2 - import parameters window opens.
    2. Make the desired settings (see "EMME/2 import" on page 2587).
    3. Click the Save button.
    The Save EMME project window opens.
    4. Enter the file name and the path, if required.
    5. Enter the file extension *.emme.
    6. Click the Save button.
    The current settings and the selected EMME/2 data are saved as EMME project *.emme.

    25.6.3

    Reading the settings for an EMME/2 import


    You can read the settings and EMME/2 data files for EMME/2 import from an EMME project file
    *.emme.

    PTVGROUP

    2591

    25.6.4 Resetting the EMME/2 import settings


    1. Make sure the EMME/2 - import parameters window is open (see "EMME/2 import" on
    page 2587).
    2. Click the Open button.
    The Open EMME project window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings and the EMME/2 data are read according to the EMME project.

    25.6.4

    Resetting the EMME/2 import settings


    You can restore the default settings for EMME/2 import and delete the allocations of EMME/2
    data files and demand matrices.
    1. Make sure the EMME/2 - import parameters window is open (see "EMME/2 import" on
    page 2587).
    2. Click the Reset button.
    The settings are reset and the allocations of EMME/2 data and demand matrices are deleted.

    25.7

    TModel import
    Visum provides an interface for the import of TModel data.

    25.7.1

    Importing TModel data


    1. In the File menu, select the Import> TModel entry.
    The TModel import settings window opens.
    2. Select the Files tab.
    3. Depending on the type of TModel data file for which you want to import data, click the
    respective button

    The Open <file type> window opens.


    4. Select the desired file.
    5. Click the Open button.
    File name and directory are used for the File name entry.
    Note: You can delete the allocation of a file to be imported by clicking the respective
    Delete button.
    6. Select the Parameters tab.
    7. Make the desired changes.

    2592

    PTVGROUP

    25.7.1 Importing TModel data


    Element

    Description

    Number of zones

    Number of TModel centroids to be imported as zones.

    Units

    Via the option you can select the units used in the TModel files for
    lengths and speeds.
    Metric
    Imperial

    Import of loading Via this option you can specify how TModel centroids and related
    links (from/to zone objects are to be imported:
    centroids)
    Loading links as Visum connectors. Centroids as Visum zones
    If the option has been selected, the entered number of TModel
    centroids is imported as Visum zones and links connected to TModel centroids are imported as Visum connectors.
    Loading links as Visum links. Centroids are duplicated as
    Visum zones and VISUM nodes
    If the option has been selected, all TModel links are imported as
    Visum links and the entered number of TModel centroids is imported as Visum zones and Visumconnector nodes.
    Note
    The corresponding connectors between zones and nodes feature
    a length of zero.
    Close turns for t0
    >

    Maximum permissible turning time in minutes


    Note
    Turns whose turning time exceeds the entered value are closed.

    Replace Capacity
    If the option has been selected, capacity PrT, turn type and turn
    PrT, Type and
    VD functions are overwritten by values of the TModel files, except
    VDFs
    for the case that the value of the turn type in row 2 of the turn type
    file *.tpt is zero. In that case turn type and turn VD functions of the
    existing network remain unaltered and capacity PrT is 99999 for
    all turns.
    If the option has not been selected, turn type and turn VD functions of the existing network remain unaltered and capacity PrT is
    99999 for all turns.
    8. Select the Link type definition tab.
    9. Make the desired changes.

    PTVGROUP

    2593

    25.7.2 Saving settings for the TModel import


    Element

    Description

    User-defined

    If the option has been selected, you can modify the pre-defined
    allocation of TModel classes to Visum link types and rank by double clicking the desired row.

    From TModel link


    file

    If this option has been selected, you can select one of the three
    TModel data columns for import of link type values to Visum.
    TModel class
    TModel type
    TModel zone

    10. Select the Node type definition tab.


    11. Make the desired changes.
    Element

    Description

    User-defined

    If he option has been selected, you can alter the pre-defined allocation of TModel classes to Visum node types by double clicking
    the desired row in the Visum type no column.

    12. Confirm with OK.


    The selected TModel data are imported.

    25.7.2

    Saving settings for the TModel import


    You can save the settings and the selected TModel data files for TModel import as a TModel
    project *.tla.
    1. In the File menu, select the Import> TModel entry.
    The TModel import settings window opens.
    2. Make the desired settings (see "TModel import" on page 2592).
    3. Click the Save button.
    The Save TModel project window opens.
    4. Enter the file name and the path, if required.
    5. Click the Save button.
    The current settings and the selected TModel data are saved as TModel project *.tla.

    25.7.3

    Reading settings for the TModel import


    You can read settings and TModel data files for TModel import from a TModel project *.tla.
    1. Make sure the TModel import settings window is open (see "TModel import" on page
    2592).
    2. Click the Open button.

    2594

    PTVGROUP

    25.7.4 Resetting the TModel import settings


    The Open TModel project window opens.
    3. Select the desired file.
    4. Click the Open button.
    The settings and the TModel data are read according to the TModel project.

    25.7.4

    Resetting the TModel import settings


    You can restore the default settings for TModel import and delete the allocations of the TModel
    data files.
    1. Make sure the TModel import settings window is open (see "TModel import" on page
    2592).
    2. Click the Reset button.
    The settings are reset and the allocations of the TModel data are deleted.

    25.8

    SATURN import
    Note: This function is only provided with the SATURN import add-on (see "Enabling or
    disabling installed add-ons" on page 886).
    In Visum, you can import network data which has been created and provided in SATURN
    (Simulation and Assignment of Traffic in Urban Road Networks). Visum currently supports
    SATURN data provided with SATURN 10.8. Matrix data are excluded by SATURN, but can be
    exchanged via text files (e.g. *.csv) between Visum and SATURN.
    SATURN data may be available in one or several files. Either they are in just one file of the
    type *.dat or the file of the type *.dat contains only central data and links to embedded files (for
    example with $include <file name>) which have the following formats: *.cen, *.buf, *.ban,
    *.cor, *.bus, or *.plb.
    Subjects
    Importing SATURN data
    Description of the network file generated through SATURN import
    SATURN import: Notes on changes to the network topology
    Notes on data adjustment for assignment with ICA

    25.8.1

    Importing SATURN data


    1. In the File menu, select the Import> SATURN entry.
    The SATURN window opens.
    2. Make the desired changes.

    PTVGROUP

    2595

    25.8.2 Description of the network file generated through SATURN import


    Element

    Description

    SATURN file

    In the input field, enter the path and file name of the file with the
    icon to look for the file.
    *.dat file extension, or click the
    Note
    If the file with the *.dat file extension contains links to external
    files, the external files must be in the same directory.

    Save created net


    file (*.net)?

    If this check box is selected, after the import the files are saved
    as network file and this network file is opened.
    If this check box is not selected, during the import process the
    files are written into a temporary network file which is opened in
    Visum. Afterwards, the file is deleted.

    Output network
    file

    In the input field, enter the path and name of the network file in
    which you want to save the imported data, or click the
    look for the file.

    icon to

    3. Confirm with OK.


    The data are imported. A temporary network file is created and imported into Visum (see "Description of the network file generated through SATURN import" on page 2596). Due to different
    data structures, the network topology is modified as well (see "SATURN import: Notes on changes to the network topology" on page 2610).

    25.8.2

    Description of the network file generated through SATURN import


    The network file which is generated during the import contains table and attribute names in
    English. The file contains all data required for the import. As soon as the network file is opened
    in Visum, Visum automatically adds additional data, for example the opposite direction of oneway roads. If you save the network again, it is written in the language you selected. Depending
    on the settings for saving the network file, it contains additional tables and attributes.
    Notes: The tables and attributes are listed in the same order in which they appear in the
    network file. The names of the tables and attributes of Visum correspond to the names
    that are used in the network file by default.
    The names of the SATURN files correspond to the names in the SATURN MANUAL
    (V10.8). The column numbers (Cols) refer to data containing the SATURN parameter
    DUTCH = FALSE.
    Visum table: $VERSION

    2596

    Visum attribute

    Attribute value

    VERSNR

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

    FILETYPE

    NET

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value

    LANGUAGE

    ENG

    UNIT

    KM

    Visum table: $USERATTDEF


    The following user-defined attributes are created. The origin of the values is specified in detail
    in the respective network object type tables:
    Visum network
    object type

    User-defined attribute

    Description

    LINEROUTE

    SATURNBUSTRIPSPERHOURPC- Number of bus trips weighted by


    U
    the car unit factor

    LINK

    SATURN_V_CAP

    Speed when reaching capacity


    (parameter for SATURN speed
    flow function)

    SATURN_N

    Exponent (parameter for


    SATURN speed flow function)

    SATURN_STACKINGCAP

    Blocking back capacity

    SATURN_LINKINDEX

    Reference to SATURN speed


    flow function and parameters
    used

    SATURN_SIMULATIONLINK

    = 1, if link is part of the simulation


    network

    SATURN_TRAVELTIMEPENALTY Minimum of transport system specific time penalties, if defined


    SATURN_BANNED
    TURN

    = 1, if link is closed for at least


    one PrT system

    SATURN_TRAVELTIMEPENALTY Minimum of transport system specific time penalties, if defined


    SATURN_BANNED

    = 1, if turn is closed for at least


    one PrT system

    SATURN_PRIORITY

    = 1, if turning flow must not yield


    right of way

    SATURN_SATFLOW

    Saturation flow rate

    SATURN_GAP

    Gap

    Visum table: $NETWORK

    PTVGROUP

    2597

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value

    SCALE

    LEFTHANDTRAFFI- If the SATURN parameter LEFTDR = T, then LEFTHANDTRAFFIC =


    C
    1.
    RIGHTHANDTRAFFIC
    If the SATURN parameter LEFTDR = F, then RIGHTHANDTRAFFIC
    = 1.
    TURNTYPEDEFAU- AUTOMATICICA
    LT
    Visum table: $TSYS
    The table $TSYS automatically contains at least two transport systems: one PrT system and
    one PuTWalk system. Additionally, for each entry of the SATURN parameter BUSPCU a PuT
    system is created. The number of actually generated PrT systems is determined by the
    SATURN parameter NOMADS. The code of these PrT systems is composed of the letter C and
    a consecutive number.

    2598

    Visum attribute

    Attribute values of PuT transport systems

    CODE

    B<consecutive number>

    NAME

    B<consecutive number>

    TYPE

    PuT

    PCU

    Corresponds to the SATURN parameter BUSPCU

    Visum attribute

    Attribute values of the transport system Car

    CODE

    C<consecutive number>

    NAME

    Car

    TYPE

    PrT

    PCU

    Visum attribute

    Attribute values of the transport system Walk

    CODE

    NAME

    Walk

    TYPE

    PuTWalk

    PCU

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Visum table: $DIRECTION
    contains Visum default entries
    Visum table: $NODE
    The nodes are generated from the nodes of SATURN. Additional nodes are created due to the
    modification of the network topology (see "SATURN import: Notes on changes to the network
    topology" on page 2610).
    Visum attribute

    Attribute value

    NO

    = 55555, node number, Cols 2-5

    CONTROLTYPE

    The value is calculated from: 11111, record type 1: JTYPE:


    If JTYPE = 1, then CONTROLTYPE = 2 (two-way stop).
    If JTYPE = 2 or 5, then CONTROLTYPE = 5 (roundabout).
    If JTYPE = 3, then CONTROLTYPE = 3 (signalized).
    If JTYPE = 0 or 4, then CONTROLTYPE = 0 (unknown).
    Note
    Under certain circumstances, nodes cannot be used for an assignment with ICA. These nodes are set to control type unknown during
    the import (see "SATURN import: Nodes with control type "unknown""
    on page 2613).

    XCOORD

    = 55555, X co-ordinate

    YCOORD

    = 55555, Y co-ordinate

    Visum table: $ZONE


    The zones are generated from the zones of SATURN.
    Visum attribute

    Attribute value

    NO

    = 55555, zone number, Cols 2-5

    XCOORD

    = 55555, X co-ordinate

    YCOORD

    = 55555, Y co-ordinate

    Visum table: $LINK


    Links are created from the relationships between ANODE-NODE in section 11111 and section 33333 of SATURN's topology description. In SATURN there are internal links (in the
    simulation network) and external links (in the buffer network ). You find the internal links in
    section 11111 , you find the external links in section 33333. Both types are transferred as
    links to Visum. Additional links are created due to the modification of the network topology
    (see "SATURN import: Notes on changes to the network topology" on page 2610).
    Note: The attributes of internal links and external links are described separately.

    PTVGROUP

    2599

    25.8.2 Description of the network file generated through SATURN import

    2600

    Visum attribute

    Attribute value of internal links

    NO

    The links are numbered sequentially, starting with 1.

    FROMNODENO

    = 11111, record type 2, ANODE

    TONODENO

    = 11111, record type 1, NODE

    TYPNO

    The value depends on whether for the link (record type 2) a


    record type 2B exists or not:
    If no record type 2B exists, then TYPNO = 30.
    If the record type 2B exists, then TYPNO = 40.

    TSYSSET

    The value is calculated from: 11111, record type 2, LANES


    If LANES = 0, the value is empty. That means that the link is
    closed for all transport systems.
    If LANES < 0, then all PuT systems are allocated.
    If LANES > 0, then all PrT and PuT systems are allocated.
    Deviations are possible if for all or certain transport systems in
    44444 a value <0 is defined. In this case the link is closed for
    the respective PrT system.

    LENGTH

    The value is calculated from: 11111, record type 2, IDIST


    LENGTH = IDIST / 1000 (conversion of meters in kilometers)

    NUMLANES

    = 11111, record type 1, LANES

    CAPPRT

    The value is calculated from: 11111, record type 2B, LCAPY(link


    capacity)
    If LCAPY is not empty, then CAPPRT = LCAPY.
    If LCAPY is empty or if there is no record type 2B, then
    CAPPRT = LANES 1600.
    If the value in 11111 record type 2B is not defined and a link
    index is indicated, the value is imported from the default definition for this link index in 33333.

    V0PRT

    The value is calculated from: 11111, record type 2, IDIST; 11111,


    record type 2B, TFF and SATURN parameter SPEEDS
    If SPEEDS = T (= True), then V0PRT = TFF.
    If SPEEDS = F (= False), then V0PRT = (IDIST / TFF) 3.6.
    If the value of TFF (speed in an unloaded network) in 11111
    record type 2B is not defined and a link index is indicated, the
    value is imported from the default definition for this link index
    in 33333.

    SATURN_V_CAP

    The value is calculated from: 11111, record type 2, IDIST and


    11111, record type 2B, TCAP and SATURN parameter SPEEDS
    If SPEEDS = T (= True), then SATURN_V_CAP = TCAP
    If SPEEDS = F (= False), then SATURN_V_CAP = (IDIST /
    TCAP) 3.6

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value of internal links


    If the value of TCAP (link run time when capacity is reached)
    in 11111 record type 2B is not defined and a link index is indicated, the value is imported from the default list in 33333.

    SATURN_N

    = 11111, record type 2B, N


    If the value of parameter N in 11111 record type 2B does not exist
    and a link index is indicated, the value is imported from the default
    definition for this link index in 33333.

    SATURN_
    LINKINDEX

    = 11111, record type 2B, INDEX

    SATURN_
    STACKINGCAP

    = 11111, record type 2, STACK (blocking back capacity of the


    link)

    SATURN_
    SIMULATIONLINK

    1 = internal link

    SATURN_
    If for at least one transport system a time penalty is defined in
    TRAVELTIMEPENALT- 44444, the value results from the minimum of all time penalties.
    Y
    Otherwise, the value is 0.
    SATURN_BANNED

    The attribute has the value 1, if the link is closed for at least one
    PrT system. If the link is opened for all PrT systems, the value is 0.

    Visum attribute

    Attribute value of external links

    NO

    The attribute value of the link depends on whether the opposite


    direction has already been imported as internal link:
    If the opposite direction exists, then NO = NO of the link of the
    opposite direction.
    Otherwise, the links are numbered subsequently.

    FROMNODENO

    = 33333, RECORD 1, A-node (Cols 2-5)

    TONODENO

    = 33333, RECORD 1, B-node (Cols 7-10)

    TYPNO

    The value depends on whether link flow data exist for the link.
    More specifically, whether in section 33333 a line starting with D
    exists for this link:
    If no link flow data exist, then TYPENO = 50.
    If link flow data exist, then TYPENO = 60.

    PTVGROUP

    2601

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value of external links

    TSYSSET

    If the link has already been imported as internal link, then


    TSYSSET = TSYSSET of the existing link.
    Otherwise, all transport systems are opened.
    Deviations for PrT systems are possible if in 44444 a value <0 is
    defined. In this case the link is closed for the corresponding PrT
    system.

    LENGTH

    The value is determined from the link length (33333, RECORD 1,


    Cols 31-35)
    LENGTH = link length / 1000 (conversion of meters in kilometers)

    NUMLANES

    If the link has already been imported as internal link, then


    NUMLANES = NUMLANES of the existing link.
    Otherwise, the value is calculated from the capacity (33333,
    RECORD 1, Cols 21-25):
    If 0 < capacity 1600, then NUMLANES = 1.
    If 1600 < capacity 3200, then NUMLANES = 2.
    If 3200 < capacity 4800, then NUMLANES = 3.
    If 4800 < capacity 6400, then NUMLANES = 4.
    If 6400 < capacity, then NUMLANES = 5.

    2602

    CAPPRT

    = 33333, RECORD 1, Cols 21-25

    V0PRT

    The value is calculated from the link length (33333, RECORD 1,


    Cols 31-35), the journey time in an unloaded network (33333,
    RECORD 1, Cols 11-15) and the SATURN parameter SPEEDS
    If SPEEDS = T (= True), then V0PRT = speed.
    If SPEEDS = F (= False), then V0PRT = (link length / journey
    time) 3.6.

    SATURN_V_CAP

    The value is calculated from the link length (33333, RECORD 1,


    Cols 31-35), the journey time or speed when the capacity is reached (33333, RECORD 1, Cols 16-20) and the indicator for time/speed (33333, RECORD 1, Col 29).
    If Indicator = S, then SATURN_V_CAP = speed.
    If Indicator <> S, then SATURN_V_CAP = (link length / journey time) 3.6.

    SATURN_N

    = 33333, RECORD 1, Cols 36-40

    SATURN_
    LINKINDEX

    = 33333, RECORD 1, Cols 43-45

    SATURN_
    SIMULATIONLINK

    0 =external link

    SATURN_

    If for at least one transport system a time penalty is defined in

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value of external links

    TRAVELTIMEPENALT- 44444, the value results from the minimum of all time penalties.
    Y
    Otherwise, the value is 0.
    SATURN_BANNED

    The attribute has the value 1, if the link is closed for at least one
    PrT system. If the link is opened for all PrT systems, the value is 0.

    Visum table: $TURN


    A turn is defined in record type 2, section 11111, if valid values are stored in the data triple
    LSAT, LANE1 and LANE2, i.e. neither empty nor 0. After each node of the type ANODE you
    find in the same row several triple data for each permitted turn. The turns lead via the NODE in
    Record type 1 (Visum: VIANODENO) to the other ANODEs of the same NODE. They are in
    the same order as the other ANODEs which follow after record type 2 in clockwise direction.
    During the import, for each turn relationship a permitted turn is created. Additional turns are
    created due to the modification of the network topology (see "SATURN import: Notes on changes to the network topology" on page 2610). By the definitions in 44444 additionally transport
    system specific time penalties and closures for turns are considered.
    Visum attribute

    Attribute value

    FROMNODENO

    = 11111, record type 2, ANODE

    VIANODENO

    = 11111, record type 1, NODE

    TONODENO

    = 11111, record type 2, ANODE (for all existing turn relationships)

    TSYSSET

    The value is calculated from: 11111, record type 2, LSAT (saturation flow rate)
    If LSAT < 0, then all PuT systems are allocated.
    If LSAT = 0, no transport system is allocated.
    If LSAT > 0, then all PrT and PuT systems are allocated.
    By values < 0 in 44444 turns are closed for these PrT systems.

    CAPPRT

    = 11111, record type 2, LSAT

    T0PRT

    The value is calculated from: 11111, record type 2, LSAT


    If LSAT < 0 or LSAT > 0, i.e. there is a transport system, then
    T0PRT = 0.
    If LSAT = 0, then T0PRT = 100000 (hours).
    If for at least one PrT system a time penalty (i.e. value >0) is
    defined in 44444, T0PRT is set to the minimum value of the
    time penalties of all PrT transport systems.

    PTVGROUP

    2603

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value

    SATURN_PRIORITY

    The value is calculated from: 11111, record type 2, TPM (marking


    the subordinate leg)
    If TPM is not empty, then SATURN_PRIORITY = 0.
    If TPM is empty, then SATURN_PRIORITY = 1.
    The value is used to define the node attributes MajorFlowOri1
    and MajorFlowOri2.

    SATURN_SATFLOW

    = 11111, record type 2, LSAT (saturation flow rate)

    SATURN_GAP

    = 11111, record type 1, GAP/GAPR

    SATURN_
    If for at least one PrT system a time penalty (i.e. value >0) is defiTRAVELTIMEPENALT- ned in 44444, the value results from the minimum of all time penY
    alties. Otherwise, the value is 0.
    SATURN_BANNED

    The attribute has the value 1 if the turn is closed for at least one
    PrT system. Is the turn permitted for all PrT systems, the value is 0.

    Visum table: $CONNECTOR


    The connectors are created from simulation centroid connectors and certain entries in the
    buffer network/link data in SATURN. You find the first in section 22222, the latter in section
    33333. Both types are transferred as connectors to Visum. For each connector, an origin and a
    destination connector are created automatically.
    Visum attribute

    2604

    Attribute value

    ZONENO

    If the connector is a simulation centroid connector, then ZONENO =


    22222, Cols 1-5 (for simulation centroid connectors).
    If the connector comes from the buffer network and 33333, Col1 = C,
    then ZONENO = 33333, Cols2-5.
    If the connector comes from the buffer network and 33333, Col6 = C,
    then ZONENO = 33333, Cols7-10.

    NODENO

    If the connector is a simulation centroid connector, it is connected


    with a newly generated node (see "SATURN import: Notes on changes
    to the network topology" on page 2610). The new node numbers are 6digit numbers and in DUTCH format 9-digit numbers.
    If the connector comes from the buffer network and 33333, Col1 = C,
    then NODENO = 33333, Cols7-10.
    If the connector comes from the buffer network and 33333, Col6 = C,
    then NODENO = 33333, Cols2-5.

    DIRECTION

    For each connector one entry each is created with D and O.

    TSYSSET

    All transport systems are allocated, the only exception are PuT systems.

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Visum table: $LANE
    For each link (both directions) the number of lanes (NUMLANES) is determined. For the From
    Node and To Node the lanes are sequentially numbered in counterclockwise direction (seen
    from the middle of the node).
    Apart from this, additional lanes are created due to the modification of the network topology
    (see "SATURN import: Notes on changes to the network topology" on page 2610).
    Visum attribute

    Attribute value

    NODENO

    Corresponds to the number of the node of the link (FROMNODENO


    and TONODENO)

    MAINNODENO

    LINK NO

    Corresponds to the NO of the corresponding link

    NO

    The lanes are numbered consecutively and in counterclockwise direction per node and link, starting with 1 up to the value of NUMLANES
    of the link (both directions).
    For incoming lanes the APPTYPE = 1.
    For outgoing lanes the APPTYPE = 0.

    APPTYPE
    ORIGINLANENO

    TSYSSET

    The value is calculated from: 11111, record type 2, LSAT


    If LSAT < 0, then all PuT systems are allocated.
    If LSAT = 0, no transport system is allocated.
    If LSAT > 0, then all PrT and PuT systems are allocated.

    Visum table: $LANETURN


    Lane turns are written for all defined turn relations for all lanes from LANE1 to LANE2.
    Additional lane turns are created due to the modification of the network topology (see
    "SATURN import: Notes on changes to the network topology" on page 2610).
    Visum attribute

    Attribute value

    NODENO

    = 11111, record type 1, NODE

    MAINNODENO

    FROMLINKNO

    NO of the link which was created between ANODE and NODE

    TOLINKNO

    NO of the link which was created between NODE and TONODE

    FROMLANENO

    The value is calculated from: 11111, record type 2, LANE1 and


    LANE2
    The lane turns are numbered sequentially within each link from
    LANE1 to LANE2.

    TOLANENO

    The value is determined as follows:

    PTVGROUP

    2605

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value
    For left turns and straight turns, the lane turn with FROMLANENO
    = 1 is assigned the highest TOLANENO of the to link. The lane
    turn with the value FROMLANENO = 2 is assigned the second
    highest TOLANENO etc.
    For right turns and U-turns, the lane turn with the highest
    FROMLANENO is assigned the lowest TOLANENO of the exit
    lane. The lane turn with the second highest FROMLANENO is
    assigned the second lowest TOLANENO of the exit lane, etc.
    If the total number of the FROMLANENO is higher than the total number of the TOLANENO, the turns without a corresponding
    TOLANENO are linked with the TOLANENO that was last assigned.

    TSYSSET

    Corresponds to the TSYSSET of the respective turn

    Visum table: $SIGNALCONTROL


    For each entry in section 11111, which has a record type 3, a SC is created.
    Visum attribute

    Attribute value

    NO

    The signal controls are numbered continuously, starting with 1.

    CODE

    empty

    NAME

    empty

    CYCLETIME

    The value is calculated from: 11111, record type 1, LCY (cycle


    time) or 11111, record type 3, STAGL (stage lengths) and 11111,
    record type 3, INTG (intergreens)
    If LCY <> 0, then CYCLETIME = LCY.
    If LCY = 0, then CYCLETIME = sum of all STAGL + INTG of all
    allocated signal groups in record type 3.

    TIMEOFFSET

    = 11111, record type 1, OFFSET (offset)

    SIGNALIZATIONTYP- SIGNALIZATIONSIGNALGROUPBASED
    E
    Visum table: $SIGNALCONTROLTONODE
    For each SC the allocation to a node is defined.
    Visum attribute

    Attribute value

    SCNO

    Corresponds to the NO of the respective SC

    NODENO

    = 11111, record type 1, NODE

    MAINNODENO

    Visum table: $SIGNALGROUP


    For each Record type 3 of a SC a signal group is created.
    2606

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Furthermore, an additional signal group is created for each signal control with a left-turn for
    left-hand traffic and with a right-turn for right-hand traffic to which no signal group has been
    allocated in the SATURN network (see "SATURN import: New signal group for unsignalized
    left turns" on page 2614).
    Visum attribute

    Attribute value

    SCNO

    Corresponds to the NO of the respective SC

    NO

    The signal groups are numbered continuously, starting with 1.

    NAME

    The name consists of the NO and the prefix SG_.

    GTSTART

    The value is calculated from: 11111, record type 1, OFFSET (offset)


    and 11111, record type 3, INTG (intergreens)
    For the first signal group of a SC the following applies: GTSTART =
    OFFSET
    For all further signal groups the following applies: GTSTART =
    GTENDof the previous signal group+ INTGof the previous signal
    group.

    GTEND

    The value is calculated from: 11111, record type 3, STAGL (stage


    lengths)
    GTSTART = GTSTART + STAGL

    Visum table: $SIGNALGROUPTOLANETURN


    In section 11111, record type 3, the From Nodes (GNA , Cols 26-30 , 36-40 etc.) and To
    Nodes (GNC , Cols 31-35 , 41-45 etc.) of the lane turns are defined which are allocated to the
    signal group. An entry into this table is created for each GNA-GNC pair of each lane turn.
    Additionally, with the modification of the network topology, additional signal groups for lane
    turns are created (see "SATURN import: Notes on changes to the network topology" on page
    2610).
    Visum attribute

    Attribute value

    NODENO

    = 11111, record type 1, NODE

    MAINNODENO

    FROMLINKNO

    Corresponds to the FROMLINKNO of the respective lane turn

    FROMLANENO

    The value is calculated from: 11111, record type 3, GNA


    Corresponds to the FROMLANENO of the respective lane turn

    TOLINKNO

    Corresponds to the TOLINKNO of the respective lane turn

    TOLANENO

    The value is calculated from: 11111, record type 3, GNC


    Corresponds to the TOLANENO of the respective lane turn

    SGNO

    Corresponds to the NO of the respective signal group

    Visum table: $INTERGREEN

    PTVGROUP

    2607

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value

    SCNO

    Corresponds to the NO of the respective SC

    FROMSGNO

    Corresponds to the NO of the respective signal group

    TOSGNO

    Number of the signal group which comes after FROMSGNO


    If FROMSGNO is not the number of the last signal group of the
    SC, then TOSGNO = FROMSGNO + 1.
    If FROMSGNO is the number of the last signal group of the SC,
    then TOSGNO = FROMSGNO of the first signal group of the SC.

    INTERGREEN

    = 11111, record type 3, INTG

    Visum table: $STOP


    All nodes that are part of lines (section 66666) are automatically imported as stop points.
    Visum attribute

    Attribute value

    NO

    Corresponds to the NO of the respective node

    XCOORD

    Corresponds to the XCOORD of the respective node

    YCOORD

    Corresponds to the YCOORD of the respective node

    Visum table: $STOPAREA


    For each stop point automatically a stop area is created.
    Visum attribute

    Attribute value

    NO

    Corresponds to the NO of the respective stop

    STOPNO

    Corresponds to the NO of the respective stop

    XCOORD

    Corresponds to the XCOORD of the respective stop

    YCOORD

    Corresponds to the YCOORD of the respective stop

    Visum table: $STOPPOINT


    All nodes which are part of a line (section 66666) are automatically imported as stop points.
    Visum attribute

    Attribute value

    NO

    Corresponds to the NO of the respective stop

    STOPAREANO Corresponds to the NO of the respective stop area

    2608

    TSYSSET

    All traffic systems are allocated.

    DIRECTED

    PTVGROUP

    25.8.2 Description of the network file generated through SATURN import


    Visum attribute

    Attribute value

    NODENO

    Corresponds to the NO of the respective node

    FROMNODEN- empty
    O
    LINK NO

    empty

    RELPOS

    empty

    Visum table: $LINE


    Lines are listed in the sections 66666 . For each PuT system there is one section 66666. All
    lines from all sections 66666 are imported.
    Visum attribute

    Attribute value

    NAME

    The value is determined from: 66666, Cols 1-5


    If this name is unique, the name is directly transferred.
    If the line name is not unique, from the second occurrence onwards, a
    blank and a continuous number is appended to the name.

    TSYSCODE

    The value is determined depending on the sections 66666 in which the


    line is.
    If the line is in the first section 66666, then TSYSCODE = B1.
    If the line is in the second section 66666, then TSYSCODE = B2 etc.

    Visum table: $LINEROUTE


    For each line one or two line routes are created. This depends on the entry in 66666, Col 6.
    Visum attribute

    Attribute value

    LINENAME

    Corresponds to the NAME of the respective line

    NAME

    Corresponds to the NAME of the respective line

    DIRECTIONCODE

    Value is determined from: 66666, Col 6


    If Col 6 is empty, then DIRECTIONCODE = >.
    If Col 6 = T, then a line route is created for each direction.
    If Col 6 = R, then DIRECTIONCODE = <

    ISCIRCLELINE

    SATURNBUSTRIPSPERHOU- Value is determined from: 66666, Cols 7-10


    RPCU
    SATURNBUSTRIPSPERHOURPCU = <entry> PCU
    Visum table: $LINEROUTEITEM
    For each line route at each stop point, a line route element is created.

    PTVGROUP

    2609

    25.8.3 SATURN import: Notes on changes to the network topology


    Visum attribute

    Attribute value

    INDEX

    The line route items are numbered consecutively.

    LINENAME

    Corresponds to the NAME of the respective line

    LINEROUTENAM- Corresponds to the NAME of the respective line route


    E
    DIRECTIONCODE Corresponds to the DIRECTIONCODE of the respective line route
    ISROUTEPOINT

    NODENO

    Corresponds to the NO of the respective node

    STOPPOINTNO

    Corresponds to the NO of the respective stop point

    SATURN data which are not imported into Visum


    The following SATURN data are not imported into Visum:
    SATURN Options
    Section 11111: Record type 2: TPMod
    Section 33333: Record 2
    Section 55555: Cols 16-20 (Sectors)
    Section 77777
    Section 88888

    25.8.3

    SATURN import: Notes on changes to the network topology


    In SATURN a connector from section 22222 connects a zone with a directed link. In Visum a
    connector is the connection between a zone and a node. Therefore, when importing data, the
    network topology has to be changed. These changes affect the following network objects:
    Node
    Links
    Turn
    Lanes
    Lane turns
    Signal groups to lane turns

    25.8.3.1

    Basic rules for reading connectors in the simulation network


    In SATURN, zones in the simulation network are connected to directed links (simulation centroid connectors), in Visum to nodes. Therefore, for each connector the relevant link is split in
    the middle. The link is split and four new nodes are inserted.
    Hereby, the original link is split into four links of the same length. The first node is inserted after
    25 % of the original link length. If the original link can be traversed in both directions, this partial link, too, can be traversed in both directions. For the second and third partial link one node
    each is inserted for both directions. To these two nodes a zone can be connected. The new
    links can only be traversed in one direction. For the third and fourth partial link the fourth node
    is inserted. If the original link can be traversed in both directions, the fourth partial link can also
    be traversed in both directions. Except for the length all attributes of the directed links are

    2610

    PTVGROUP

    25.8.3.2 Different cases for importing connectors


    transferred to the partial links. The original link is deleted. All turns concerned are adjusted.
    Depending on the type of link or connector, different cases are distinguished (see "Different
    cases for importing connectors" on page 2611).
    25.8.3.2

    Different cases for importing connectors


    One-way road
    If the connected link is a one-way road, the link (initial and opposite direction) is split in the
    middle. In accordance with the basic rules, the new links are closed in the relevant direction
    (dashed line).
    Initial link

    Split link

    Note: If there is a connector for the closed direction of a one-way road, it will be permitted.
    A link is permitted in both directions, connectors for both directions
    If the connected link is permitted in both directions and if all connectors are valid for both directions, the link (initial and opposite direction) is split in the middle.
    Initial link

    Split link

    The U-turns at the nodes 3 and 5 (4-3-6, 6-5-4) are blocked, i.e.
    TSysSet = empty (no transport system)
    t0 = 100000h

    PTVGROUP

    2611

    25.8.3.2 Different cases for importing connectors


    CapPrT = 0
    A link is permitted in both directions, different connectors
    If the connected link is permitted in both directions and if not all connectors are valid for both
    directions, both the initial and the opposite direction are split in the middle. The zones are
    connected with the relevant nodes.
    Initial link

    Split link

    The U-turns have to be closed at the nodes 3 and 5 (4-3-6, 6-5-4):


    TSysSet = empty (no transport system)
    t0 = 100000h
    CapPrT = 0
    A link is permitted in both directions, the connector only in one direction
    If the connected link is permitted in both directions and if the connectors are valid for just one
    direction, both directions are split in the middle.
    Initial link

    Split link

    The U-turns have to be closed at the nodes 3 and 5 (4-3-6, 6-5-4):


    TSysSet = empty (no transport system)
    t0 = 100000h

    2612

    PTVGROUP

    25.8.4 Notes on data adjustment for assignment with ICA


    CapPrT = 0
    The other turns are not explicitly written. They are automatically opened by Visum.

    25.8.4

    Notes on data adjustment for assignment with ICA


    Usually SATURN data is imported to carry out an ICA assignment in Visum (see "Assignment
    with ICA" on page 1946).
    For this purpose, Visum adjusts some SATURN data when the network file is created or opened.

    25.8.4.1

    SATURN import: Node and turn attribute values


    For the assignment with ICA two node attributes and one turn attribute have to be adjusted.
    The attribute values are edited automatically, when the network file that has been generated
    from the SATURN data is opened in Visum.
    Note: These changes are not stored you save the data as network or version file in
    Visum.
    All nodes that satisfy the following conditions are modified:
    The control type corresponds to one of the following types: two-way stop, two-way yield,
    signalized, all-way stop or roundabout.
    In SATURN, all links from/to the node which are permitted for PrT are links of the simulation network.
    The following attribute values are defined for these nodes:
    The node attribute Use preset method for impedance at node is set to the value 'active'.
    The node attribute Method for impedance at node is set to the value Node impedance
    calculation (ICA).
    The following attribute is defined for turns:
    The Type number attribute is automatically defined in accordance with the setting All
    turns via a node which are open for ICA are preset automatically, otherwise type 0
    (see "Specifying an automatic allocation of the turn type" on page 1097).

    25.8.4.2

    SATURN import: Nodes with control type "unknown"


    In two cases, nodes are set to control type 0 (unknown) when being read in Visum.
    Nodes with implausible major flows
    Signalized nodes with external links
    A corresponding message is written to the Protocol.txt file.
    Nodes with implausible major flows
    In the SATURN data, a turn is marked as major flow as follows: The turn capacity (11111,
    Record type 2, LSAT) is followed by a blank (11111, Record type 2, TPM = blank).

    PTVGROUP

    2613

    25.8.4.3 SATURN import: New signal group for unsignalized left turns
    Visum verifies the major flow marks in SATURN nodes when reading SATURN data from file. If
    major flows are not plausible in Visum, the control type of the node will be set from Two-way
    stop to Unknown.
    The following scenarios are not permitted in Visum:

    The example on the left side shows equal major flows, and on the right side, the left turn itself
    is the major flow which turns into an existing major flow.
    Signalized nodes with external links
    In SATURN, the topology is defined in the simulation network (section 11111 ) section. If an
    external link from the buffer network (section 33333) is connected to the simulation network
    at a signalized node, the topology of the node changes. Since the turns from and to external
    links are not allocated to any signal group and do not have any capacities either, such a node
    cannot be used in the assignment with ICA.
    25.8.4.3

    SATURN import: New signal group for unsignalized left turns


    In SATURN networks, at signalized nodes left-turns can exist for left-hand traffic and right turns
    for-right hand traffic which have not been allocated to a signal group. Such a turn is indicated
    by the following: Subsequently to the turn capacity (11111, Record type 2, LSAT), an F flag follows (11111, Record type 2, TPM = F).
    To model this in Visum, for each concerned signal control an additional signal group is created for these left-turns or right-turns during the SATURN data import. The green time of this
    signal group is as long as the cycle time.
    Note: This correction can only be successful, if the left-turn (left-hand traffic) has a separate lane. If the left turn and the straight turn use a shared lane, for example, no ICA calculation can be performed for this node. In this case a window will appear when the
    assignment is started. The message that two signal groups have been allocated to one
    lane will be returned. The assignment is cancelled. You need to decide how to solve the
    conflict: You can either discard one of the two allocations, for example, or select control
    type 'unknown' for the node.

    25.9

    OpenStreetMap import
    The OpenStreetMap import interface enables users to read in data from the database of the
    Internet map provider OpenStreetMap (OSM) in Visum. The imported data is used to create a

    2614

    PTVGROUP

    25.9.1 Notes on the data generated from OpenStreetMap data


    new network. Additive import is not intended. The data provided on the OpenStreetMap website is collected by volunteers and entered in the OSM database. The main purpose of the data
    is the cartographic representation of the so-called "slippy map" on the OpenStreetMap website
    or in other services which create specific maps for, for example, cyclists, hikers, or skiers from
    the data on the basis of filters or layouts (see "Inserting background images of map services
    on the Internet" on page 2237). Due to the application areas, the focus of the data collection is
    on those aspects of the objects that are visible in maps. Dimensions concerning the contents,
    which are interesting for the use in transportation models, can be maintained less intensely.
    The geographical and contentual coverage of the data varies according to the interests of the
    respective volunteers and is thus inconsistent. There is no guarantee that usable data is available in the desired detail for a specific region.
    Besides cartographic maps, the entire underlying database is freely available. When converted suitably, you can use the data in Visum as a basis for your network model. For the flexible OSM data model, Visum provides a variable importer for OSM data. Using the
    configurations provided, you can import data that is consistent with the most common applications or adjust the settings to any further requirements.
    Note: The OSM data are supplied under the Open Database License and are protected
    by copyright. Please note the license agreements when using the data in your projects.
    Subjects
    Notes on the data generated from OpenStreetMap data
    Importing OpenStreetMap data
    Adapting the import process
    Structure of the configuration sets

    25.9.1

    Notes on the data generated from OpenStreetMap data


    Depending on the configuration, the OSM importer imports different parts of the OSM database
    to Visum. You can import
    the basic link network, including nodes, links, link polygons, turns, various attributes for
    road and rail networks
    stops and PuT line routes, if available
    point and surface POIs, e.g. for land use or the location of facilities
    into Visum.
    The OSM importer takes over the basic link network with the attributes that are relevant to the
    setup of a network model. Nodes, links, and blocked turns are transferred to the Visum network. An essential part of the conversion is the setup of a network topology that is suitable for
    Visum, which is not available in the OSM data. For example, OSM does not differentiate between topological nodes and simple intermediate points. Moreover, parallel edges and even
    loops are possible between two nodes. These specialties are taken into account when suitably converting the OSM data during the import. The result only contains some of the original
    nodes as nodes and the ways are divided onto several individual links, if required.
    Generally, you cannot expect specific attribute values to be supplied for an entire area in OSM
    data. Particularly attributes that are not shown on the map display, e.g. the maximum speed

    PTVGROUP

    2615

    25.9.1 Notes on the data generated from OpenStreetMap data


    limit, are only rarely available. The OSM importer thus initially uses default values for many of
    the attributes that are normally defined via link types. Depending on the configuration, the
    default values available are then overwritten by the precise attributes for individual objects, or
    the individual data is merely saved to user-defined link attributes. If required, you can use the
    multi-edit function to overwrite the default data manually with object-specific data.
    In the following table, under Notes, you can see whether the values are adopted from the
    OSM data or link type. The display corresponds to the results when using the provided configuration sets. In case of user-defined configurations in particular, deviations from this scheme
    may occur and further attributes can be fed with data.
    Object type

    Attribute

    Notes

    Node

    OSM_NODE_ID

    Original ID of the corresponding OSM node

    Node

    XCoord, YCoord

    Directly from OSM

    Links

    OSM_WAY_ID

    Original ID of the corresponding OSM way

    Links

    O2V_WAYSECIDX

    Consecutive number of the section on the corresponding OSM way

    Links

    Name

    Directly from OSM

    Links

    TypeNo

    Directly from OSM

    Links

    WKT (link polygon)

    Directly from OSM

    Links

    TSysSet

    From link type and in user-defined attribute


    O2V_TSYSSET
    In case of one-way roads only for the direction
    open to traffic

    Links

    CapPrT

    From link type

    Links

    NumLanes

    From link type and in user-defined attribute


    O2V_LANES

    Links

    V0PrT

    From link type and in user-defined attribute


    O2V_MAXSPEED

    Turn

    TSysSet

    Directly from OSM (only blocked)

    During the import, the following steps are taken in Visum:


    Importing and checking the configuration files
    Importing the OSM files
    Prefiltering the relevant OSM objects
    Setting standard values for tags (for use in filters)
    Overwriting standard values with specific data of the objects, if available
    Determining derived information like trafficability by transport systems, allocation of a link
    type
    Transfer of further attributes, where applicable
    Processing of the link topology
    Identifying prohibited turns

    2616

    PTVGROUP

    25.9.2 Importing OpenStreetMap data


    Writing a network file (converted objects and template with definitions of TSys, link types
    etc.)
    Reading the network file into Visum

    25.9.2

    Importing OpenStreetMap data


    The section below describes how to create a Visum network from OSM data.

    25.9.2.1

    Downloading and preparing OpenStreetMap data


    For an import into Visum, the OpenStreetMap data must be available as files with the file extension *.osm, an XML format defined by OpenStreetMap. You can download the raw data from
    various websites and edit the data later.
    For small sections of the network, you can download such files directly from the
    OpenStreetMap website. For larger territories such as states or provinces, you may obtain files
    from different services, e.g. Geofabrik http://www.geofabrik.de / ) or CloudMade ( http://maps.cloudmade.com/) as zip archives. Before data import into Visum, files of the type
    *.osm must be unzipped from the archive. Since the Visum importer always imports these files
    entirely, it is advisable to prepare the data before the import to make the import as effective
    and comprehensible as possible. With the freely available tool osmosis ( (http://wiki.openstreetmap.org/wiki/Osmosis) you can, for example, extract geographic sections
    from OSM files or filter the data based on content.

    25.9.2.2

    Running the import process with a predefined configuration


    1. In the File menu, select the Import> OpenStreetMap entry.
    The OpenStreetMap window opens.
    2. Make the desired changes.
    Element

    Description

    OSM Files

    Select the OSM files via the

    Import configuration

    Configuration set
    In the drop-down list, click the desired configuration set. Each set
    contains at least one *.xml file, one *.cfg file and one *.net file.
    Optionally, a readme file can also be part of the configuration set.
    Notes
    The names of the configuration sets are derived from the folder
    names. You can choose from the provided configuration sets,
    which cannot be modified, and user-defined sets.
    Alternatively, you can select the configuration files individually
    without using a configuration set when selecting the entry "Userdefined".
    Description
    Display of the text of the readme file, which is saved in the selec-

    PTVGROUP

    icon. You can select multiple files.

    2617

    25.9.2.3 Checking the import results


    Element

    Description
    ted configuration set.
    Note
    If, under Workflow config, Parameters and Base network, you
    replace a configuration set of the drop-down list with other files,
    the contents of the field will be deleted.
    Workflow config, Parameters, Base network
    Display of the files *.cfg, *.xml, *.net from the configuration set.
    Note
    The options Workflow config, Parameters and Base network
    are only relevant, if a user-defined configuration set has been
    selected under Configuration set.
    You can select another file each using the

    Output network
    file

    icon.

    In the input field, enter the path and name of the network file in
    which you want to save the imported data, or click the
    icon to
    choose the path.
    Note
    This option is only relevant if option Save user-defined output
    network file has been selected.

    Save user-defined If the option has been selected, the temporarily generated netoutput network file work file will be saved in your temporary files, if you do not specify
    a storage location under output net file.
    Note
    If the option has not been selected, a temporary network file will
    be generated during the import, which is not saved automatically
    by Visum.
    3. Confirm with OK.
    The data are imported and a temporary network file is generated, which is displayed in
    Visum.
    25.9.2.3

    Checking the import results


    After the import of the OSM data, you should carry out some plausibility checks.
    Applying a classified display
    A simple plausibility check of the imported data can be achieved by a classified display of link
    types/categories in the imported network. Make sure, that the folder with the configuration files
    contains a Visum graphic parameters file with a matching file name or use one of the provided
    configuration sets. If a matching graphic parameters file exists, it will be loaded automatically
    after the import. Haben Sie keine passende Grafikparameter-Datei hinterlegt, knnen Sie die
    klassifizierte Darstellung des Netzes manuell vornehmen (see "Displaying classified objects
    based on attribute values" on page 2411)

    2618

    PTVGROUP

    25.9.3 Adapting the import process


    Calculating a shortest path search
    Another step of the plausibility check is the calculation of shortest paths in the imported network on a random basis. They should follow plausible routes (see "Searching for and displaying shortest paths" on page 2291).
    Evaluating protocol files
    In Visum log files, essential steps of the import process and possible error messages are logged(see "Using protocol files" on page 876).

    25.9.3

    Adapting the import process


    To meet the large content and regional differences in OSM data and the requirements of
    various use cases, you can adjust the data for data import in order to meet your individual
    needs. To do so, you can create user-defined configuration sets for the OpenStreetMap importer. You can e.g. use the configuration sets to control the level of detail of imported link networks or the allocation of link types and other attributes.

    25.9.3.1

    Running the import process with a user-defined configuration


    Copy and rename the provided configuration sets to derive user-defined configuration sets.
    User-defined configuration sets are saved to the application data folder of the respective Windows user under:%APPDATA%\PTV Vision\PTV Visum 13\Importer\OSM. This folder is not
    affected by a Visum update, so that your user-defined configuration sets are not lost.
    The provided configuration sets are stored in a read-only folder where they cannot be modified. Proceed as follows, if you want to customize the provided configuration sets:
    1. In the directory of your Visum installation under ...\Exe\Importer\OSM\, copy the configuration folder that you want to customize.
    2. Copy the folder to the directory %APPDATA%\PTV Vision\PTV Visum 13\Importer\OSM.
    3. Name the folder and the configuration files identically without changing the file extension.
    4. Customize the *.cfg file in a text editor (see "Configuration file for import parameters" on
    page 2620).
    5. Customize the *.net file in a text editor (see "Network file with default settings" on page
    2620).
    6. In the *.xml file, check whether the same tag names are used as in the files *.cfg and *.net
    (see "[NodeAttributeMappings], [LinkAttributeMappings],..." on page 2623).
    7. In the File menu, select the Import> OpenStreetMap entry.
    The OpenStreetMap window opens.
    8. Make the desired settings (see "Running the import process with a predefined configuration" on page 2617).
    9. Confirm with OK.
    The data are imported and a temporary network file is generated, which is displayed in Visum.

    PTVGROUP

    2619

    25.9.4 Structure of the configuration sets

    25.9.4

    Structure of the configuration sets


    The process of data transfer to Visum is described in several configuration set files.
    Visum network file with default settings (*.net)
    Configuration file for import parameters (*.cfg)
    XML file for control of the processing sequence (*.xml)
    Text file with a description (content is shown in a dialog) (*.readme, optional)
    Visum graphic parameters (automatically loaded after data import) (*.gpa, optional)
    The files must be saved to a folder under %APPDATA%\PTV Vision\PTV Visum 13\Importer\OSM. The file name must correspond to the name of the folder, plus the file extension.
    This document does not describe the structure of the configuration files and possible parameters in detail. Please also note the tutorial included in the scope of your delivery. It contains
    further information on this topic.

    25.9.4.1

    Network file with default settings


    This configuration file is read into Visum together with the results of the conversion. The
    objects referenced in the transformed data like, for example, transport systems and link types
    are defined in this file and basic settings like the coordinate system can be specified. The network file must define all transport systems that are used in the conversion process with the correct codes. A majority of the link attributes is derived from the link types specified in this file.
    The settings specified here regarding capacity, number of lanes, speed and permitted transport systems initially define the properties of the links. These general allocations can be overwritten by object-specific data that is saved in user-defined attributes.
    You can adjust these files. You can, for example, specify a classification of link types or model
    customary speed regulations.

    25.9.4.2

    Configuration file for import parameters


    The configuration file *.cfg is a text file that is structured similarly to Windows files of the type
    *.ini. Parameter values for the import process are defined in this file, which particularly control
    the allocation of transport systems and link types based on tag values in the OSM data. You
    can adjust these files in order to, for example, control the allocation of link types to links. The
    adjustments should be consistent with the modifications of the network file with presettings.
    The settings in this file are divided into several sections which start with the section name in
    square brackets. A section contains either single settings as key-value pairs of the form key =
    value or comprehensive configuration tables which, for example, define the standard allocation for tags for all link types. Those tables contain a header with the tag name or specific
    names and several rows with values or expressions for these tags below. All values in these
    tables are separated by a semicolon. Text values are in quotation marks or double quotation
    marks. Texts that are not in quotation marks, are interpreted as names of tags evaluated accordingly. Based on numbers, texts, tag names and miscellaneous relational operators, logical
    operators and arithmetic operators, you can enter expressions and conditions in the tables.
    Example:

    2620

    PTVGROUP

    25.9.4.2 Configuration file for import parameters

    The most important sections of this file are briefly described in the following paragraphs.
    [SetTSysSet]
    Controls the allocation of OSM modes to Visum transport systems. During the import process,
    the OSM modes are addressed via tags with names like O2V_ CAR. In this section, one or
    several (comma-separated) transport system codes are allocated to each OSM mode used
    according to the Network file with the default settings. Visum transport systems can be allocated to several OSM modes. OSM modes that are not listed in this section or contain an
    empty code are not incorporated in the results.
    [LinkDefaults]
    In this section, standard configurations are defined for some tags which are only generated
    during the import process. Drop-off values are defined here, which simplify formulating expressions and filter conditions as it is not necessary to pay attention to the possible absence of the
    used tags. The configuration table consists of a Condition column and any number of other
    columns whose names are each used for an artificially generated tag at all ways.
    In the Condition column, you can define a condition each. For each way, all of these conditions will be evaluated row by row later. Based on the first row whose condition is met, new
    tags will be generated for all other column names with the column values of this row as value.
    A specific row with the entry "* " as condition defines the standard values, if none of the conditions apply. The conditions in the Condition column should only refer to tags, which are normally contained in the OSM data, in particular the Highway tag.

    PTVGROUP

    2621

    25.9.4.2 Configuration file for import parameters


    The names of the tags generated by this section need to match the tags in the import process
    and those in the configuration. In the provided process definitions, the following artificial tags
    are used.
    Day

    Values

    Description

    O2V_CATEGORY motorway, trunk,


    rail,

    Type of link, content of highway, junction and


    rail tags (only one should exist)

    O2V_LANES

    1...n

    Number of lanes

    O2V_ONEWAY

    yes|no|-1

    Indication on whether the link is a one-way road


    The value -1 means the driving direction is
    opposite to the digitalization direction

    O2V_
    MAXSPEED-

    0...

    Permitted speed for cars

    O2V_CAR

    yes|no

    Can be used by cars

    O2V_HGV

    yes|no

    Can be used by HGVs

    O2V_LGV

    yes|no

    Can be used by LGVs

    O2V_PUT

    yes|no

    Can be used by public transport (busses)

    O2V_BIKE

    yes|no

    Can be used by bicycles

    O2V_FOOT

    yes|no

    Pedestrian

    You should define standard values for these tags. If specific values are found for the tags
    during the import process, Visum overwrites the standard values. Values set in such a way are
    usually overwritten during the import process, if specific information is available, for example
    for the trafficability of individual ways by HGVs.
    [LinkTypeRules]
    In this section, you define the allocation of link types to links. The rules for the allocation are
    stated in a configuration table as a series of criteria for each individual link type. The link types
    are run through one after the other. If for a link type all criteria defined are fulfilled, it is allocated to links generated based on a way. In this section before the table, you can define a
    Default Type. It specifies how to proceed with a link that cannot be allocated to a link type as it
    does not fulfill all the criteria of a link type.
    Element

    Description

    DefaultType = 99

    Links get value "99"

    DefaultType =
    DELETE

    Links are not included in the result

    The configuration table consists of a LinkType column and any number of other columns
    whose names match the tags to be evaluated.

    2622

    PTVGROUP

    25.9.4.3 Defining the import process


    The LinkType column lists numbers of the link types that are considered. All other columns are
    either empty or contain a criterion expression. The expression consists of the tag name of the
    column and the value.
    Field content

    Form of the criterion expression

    a numerical or
    alphanumerical
    constant (in quotation marks)

    column name ~= value

    a tag name (alpha- column name == value (tag name)


    numerical value
    without quotation
    marks)
    value of the form
    [xxx]

    column name value


    Note
    "Value" can be either a value list or an area definition [x...y]

    If the field value


    begins with a
    known operator

    column name value (operator, etc.)

    [NodeAttributeMappings], [LinkAttributeMappings],...
    In these sections the attributes are specified that are adopted into Visum. Using rows of the
    type Visum attribute name = tag name , you specify which (internal) tag is assigned to
    which attribute in Visum. The Importer converts the Visum attribute names into user-defined
    attributes of the respective object type. If instead Visum internal attributes are described, an
    asterisk*is added at the beginning of the attribute name, as in the above example with
    *Name and *NumLanes.
    25.9.4.3

    Defining the import process


    The workflow of the actual import process consists of a chain of various elementary steps. The
    definition of this workflow can be flexibly configured. This is done in the *.xml file within the
    import configuration. The structure and the possible contents of this process configuration file
    are not described here. However, the tag names used in the network file and in the *.cfg file
    need to match this configuration file.

    25.9.4.4

    Expressions
    Expressions can be used in the parameter configuration and in the process configuration to formulate filters and set tag/attribute values.
    The expressions are listed as simple strings in the configuration files and interpreted by the
    importer. In the expressions, values for tags can be called via the respective tag names. Apart
    from that, the operators listed below can be used to link the values. You can nest expressions
    if you put them in brackets.

    PTVGROUP

    2623

    25.9.4.4 Expressions
    Arithmetic operators
    Element

    Description

    +, -, *, /

    Plus, minus, multiplication, division

    //

    Integer division

    Modulo, rest

    **

    Exponent

    Relational operators
    Element

    Description

    =, ==

    equal to

    <>, !=

    not equal to

    >

    greater than

    >=

    greater than or equal to

    <

    less than

    <=

    less than or equal to

    Logical operators
    Element

    Description

    Not, Negation

    && and/or
    AND

    And

    || and/or OR

    Or

    String operators/functions

    2624

    Element

    Description

    =,==

    Exact equality

    ~=

    Comparison without consideration of the spelling of the letters and comparison with wildcard *' as prefix and postfix

    Concatenation

    PTVGROUP

    25.10 VDV 452 interface


    Other
    Element

    Description

    ()

    Parenthesis

    (x) ? a : b

    If condition x is TRUE then a, otherwise b

    x [a,b,c]

    If x is contained in set [a,b,c], then TRUE, whereby a,b,c can be numbers,


    strings, etc.

    x ~ [a,b,c]

    If x is contained in set [a,b,c], then TRUE, whereby a,b,c are strings that can
    be represented by a wildcard *.

    x ! [a,b,c]

    If x is not part of set [a,b,c] then TRUE

    x [n...m]

    If x is contained in interval n m (only numbers, both inclusive), then TRUE

    Tag operators

    25.10

    Element

    Description

    x??

    If tag x is defined TRUE, otherwise FALSE

    x:*?

    If a tag is defined, which has a prefix x: TRUE, otherwise FALSE


    A lot of tags are qualified in the form a:b. Here, only the existence of a prefix is checked, for example restriction :*? This results in restriction:motorcar
    TRUE

    x ?= y

    If a tag y is defined, tag x is assigned the value of y, otherwise x remains


    unchanged.

    VDV 452 interface


    Note: This function is available if you have activated the add-on modules VDV 452
    Import and VDV 452 Export (see "Enabling or disabling installed add-ons" on page
    886).
    Via the VDV 452 interface, you can import data of the PuT data model 5.0 (described in VDV
    Guideline 452, 03/2008), available in Visum in VDV-452 format, version 1.4. You may also
    export Visum data to VDV 452.
    VDV 452 is a file format for data exchange between PuT applications. The interface description in VDV Guidelines 451 and 452, as well as further information on German transport
    operators can be found here http://www.vdv.de/wir_ ueber_ uns/vdv_ projekte/oepnv_ datenmodell.html.
    With the import, you will receive a Visum network, including a timetable. The import process is
    similar to the (non-additive) reading of a network. Only parts that are relevant for use in the
    Visum data model, including any additional attributes, are adopted from VDV 452. Line block
    data is not imported. During data export, the Visum data model tables that can be supplied to
    the VDV data model are exported, i.e. line block data is not exported.

    PTVGROUP

    2625

    25.10.1 Importing VDV 452 data


    Using the interface, you can import both the German and English file format. Both naming schemes defined in VDV 451 are supported, i.e. file names with a table number and files names
    with a table name. The language setting for data export from Visum into the VDV 452 format is
    German, if the Visum user interface is set to German. If the user interface is set to a different
    language, the language setting for data export is English (see "Language of the graphical user
    interface" on page 875).
    Due to differences between data models, the import of a VDV 452 data record might not
    always be congruent, and not all details maintained in Visum can be exported to VDV 452.
    This is why even periodic VDV 452 import and export might not always s lead to identical data
    records. Examples of such cases are:
    IDs of valid days: The numbers of valid days might have to be adjusted, as valid day 1 is a
    default setting in Visum and is thus already assigned a meaning. The new numbers are
    also used for data export (see "Visum table $CALENDARPERIOD" on page 2635).
    Names and IDs of lines, line routes, etc.: In the PuT data model, line hierarchy objects are
    identified via numeric IDs, while in the Visum data model, keys are made up of the names
    of the respective objects (line, line route, direction, time profile). The numeric IDs are
    saved to user-defined attributes. When you re-import previously exported data, objects
    thus might be have different IDs or names.
    Number of lines, etc.: During data export from Visum, only line hierarchy and network
    objects referenced by (active) vehicle journey sections are exported. Lines without vehicle
    journey sections are not included in data export, so that when you re-import data, there
    are less lines.
    Number of vehicle journeys: In Visum line routes may service a stop point multiple times
    (circle lines). This case is not provided for in the PuT data model. During data export into
    the VDV 452 format, these line routes are thus split into route legs. This leads to a higher
    number of line routes vehicle journeys also after the re-import into Visum, i.e. circle lines
    are then not automatically created again.
    Topics
    Importing VDV 452 data
    Exporting Visum data to VDV 452
    Comparison of VDV 452 and Visum data model

    25.10.1 Importing VDV 452 data


    1. From the File menu, choose Import>VDV 452.
    The VDV 452 Import window opens.
    2. Make the desired changes.

    2626

    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


    Element

    Description

    VDV 452 directory In the input field, enter the path and file name of the desired files
    *.x10, or click the
    Save created net
    file (*.net)?

    icon to select the files.

    If this check box is selected, after the import the files are saved
    as a network file, and the network file is opened.
    If this check box is not selected, during the import process the
    files are written into a temporary network file which is opened in
    Visum. Afterwards, the file is deleted.

    Output network
    file

    In the input field, enter the path and name of the network file in
    icon to
    which you want to save the imported data, or click the
    look for the file.
    Note
    The file name automatically assigned by Visum reflects the creation date and time: YYYY-MM-DD_HHMMSS.net

    3. Confirm with Execute.


    Note: You can save multiple versions of the data to a VDV data folder. In general, these
    so-called base versions are defined within a database via the table 485 - 'BASE_
    VERSION'. By naming the files with table numbers, you can continue to save multiple
    databases with a different export date to the same folder. When you import data into
    Visum, only one base version can be adopted. If there are multiple base versions in the
    folder specified, a window containing a list is opened, in which you can select the desired
    base version.
    The data are imported. A temporary network file is created and imported into Visum(see "Comparison of VDV 452 and Visum data model" on page 2627).

    25.10.2 Comparison of VDV 452 and Visum data model


    The network file which is generated during the import contains table and attribute names in
    English. The file contains all data required for the import. It is opened in Visum during data
    import. Visum then automatically adds tables and attributes to it. After data import, you can
    save the network as a Version file in the language of your choice.
    During data export, the corresponding VDV 452 files are generated directly from the Visum
    data model. The allocation of tables and attributes of the data models corresponds to the
    import and export of the following data:
    Notes: The tables and attributes are listed in the same order in which they appear in the
    network file. The names of the tables and attributes of Visum correspond to the names
    that are used in the network file by default.
    The names of VDV 452 data correspond to those in the German version of VDV PuT data
    model 5.0.

    PTVGROUP

    2627

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum table: $VERSION
    Visum attribute

    Attribute value

    VERSNR

    8.200. The network files are compatible with version 11.5 and higher.

    FILETYPE

    NET

    LANGUAGE

    ENG

    UNIT

    KM

    Visum table: $USERATTDEF


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

    2628

    Visum network object type

    User-defined attribute

    TSYS

    ORG_BEREICH_NR

    NODE

    ORG_ORT_REF_ORT_LANGNR

    LINEROUTE
    LINEROUTEITEM
    VEHJOURNEY

    ORG_LI_NR

    LINEROUTE
    LINEROUTEITEM
    VEHJOURNEY

    ORG_STR_LI_VAR

    LINEROUTE

    ORG_ROUTEN_NR

    LINEROUTE

    ORG_LIDNAME

    LINEROUTEITEM

    ORG_LI_LFD_NR

    LINEROUTEITEM

    ORG_FAHRERKURZTEXT

    LINEROUTEITEM

    ORG_SEITENTEXT

    LINEROUTEITEM

    ORG_ZNR_TEXT

    LINEROUTEITEM

    ORG_ZNR_CODE

    TIMEPROFILE

    ORG_FGR_NR

    VEHJOURNEY

    ORG_LI_KU_NR

    VEHJOURNEY

    ORG_FAHRTART_NR

    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum network object type

    User-defined attribute

    VEHLOURNEY

    VDVNO

    VEHLOURNEYSECTION

    VDVNO

    Visum table: $TSYS


    In the VDV 452 data format, the modes of transport of the timetable are not explicitly identified.
    In the VDV 452 table MENGE_ BEREICH , however, operation branches??? can be defined
    and assigned to the supply. These are depicted in the Visum network as transport systems
    and modes.
    If the VDV 452 table MENGE_ BEREICH contains additional attributes, these are saved as
    user-defined attributes in the Visum table $TSYS.
    If the VDV 452 table MENGE_ BEREICH does not contain any data records for the version
    selected, data import is canceled. Data without a transport system cannot be meaningfully
    used in Visum.
    Visum attri- Source table
    bute

    Source attribute/value/type

    CODE

    OPERATING_DEPARTMENT

    OP_DEP_ABBR

    NAME

    OPERATING_DEPARTMENT

    OP_DEP_DESC

    PCU

    1.0

    TYPE

    PuT

    ORG_
    OPERATING_DEPARTMENT
    BEREICH_
    NR

    OP_DEP_NO

    Visum table $MODE


    Visum attri- Source table
    bute

    Source attribute/value/type

    CODE

    PuT

    NAME

    PuT

    TSYSSET

    OPERATING_DEPARTMENT

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

    TYPE

    Visum table $INFO


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

    PTVGROUP

    2629

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum attri- Source table
    bute

    Source attribute/value/type

    INDEX

    Starting at 1

    TEXT

    BASE_VERSION

    BASE_VERSION/BASE_VERSION_
    DESC/BASE_VERSION_VALID

    Visum table: $DIRECTION


    Visum attri- Source table
    bute

    Source attribute/value/type

    NO

    Forward = 1
    Reverse = 2

    CODE

    Forward = >
    Reverse = <

    NAME

    Direction = up
    Direction = down

    Visum table $VEHUNIT


    All trips are saved with default vehicles. For each entry in the MENGE_BEREICH , a default
    vehicle combination is created and used for respective trips.
    Visum attri- Source table
    bute

    Source attribute/value/type

    TSYSSET

    OPERATING_DEPARTMENT

    OP_DEP_ABBR

    NO

    OPERATING_DEPARTMENT

    OP_DEP_NO

    CODE

    OPERATING_DEPARTMENT

    OP_DEP_ABBR

    NAME

    OPERATING_DEPARTMENT

    OP_DEP_DESC

    Visum table $VEHCOMB

    2630

    Visum attri- Source table


    bute

    Source attribute/value/type

    NO

    OPERATING_DEPARTMENT

    OP_DEP_NO

    CODE

    OPERATING_DEPARTMENT

    OP_DEP_ABBR

    NAME

    OPERATING_DEPARTMENT

    OP_DEP_DESC

    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum table $VEHUNITTOVEHCOMB
    Visum attribute

    Source table

    Source attribute/value/type

    VEHCOMBN- OPERATING_DEPARTMENT
    O

    OP_DEP_NO

    CODE

    OP_DEP_NO

    OPERATING_DEPARTMENT

    NUMVEHUNI- TS

    Visum table: $NODE


    In the table REC_ ORT, the field Ort_ Nr is only unambiguous together with ONR_ TYP_ NR .
    This allows the program to generate unambiguous node numbers. According to VDV 452, the
    coordinates must be specified in WGS84, in the format dddmmssnnn (number of degrees,
    minutes, seconds with 3 decimal places/milliseconds. A positive (+) longitude value refers to
    eastern or northern hemisphere, a negative (-) longitude value refers to the western or
    southern hemisphere.
    If the VDV 452 table REC_ORT contains attributes that are not directly adopted into Visum attributes, these are also saved as user-defined attributes in the Visum table NODE.
    Visum attribute

    Source
    table

    Source attribute/value/type

    NO

    STOP

    Starting at 1

    CODE

    STOP

    POINT_NO

    TYPE

    STOP

    POINT_TYPE

    NAME

    STOP

    POINT_DESC

    XCOORD

    0 (optional from STOP.POINT_


    LONGITUDE)

    YCOORD

    0 (optional from STOP.POINT_LATITUDE)

    ORG_ORT_REF_ORT_
    LANGNR

    STOP

    STOP_LONG NO

    Visum table: $STOP


    For stops, only data records of REC_ORT are relevant, for which the ORT_ REF_ ORT_ TYP
    value is 1. Coordinates are adopted analogous to the NODE.
    The stop points depicted are grouped into stops. Stop points and stop areas are 1:1 representations, n stop areas are assigned to a stop. The superordinate stop is formed of Number
    of ORT_REF_ORT + name of ORT_REF_ORT_NAME.

    PTVGROUP

    2631

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum attribute

    Source table

    Source attribute/value/type

    NO

    STOP

    STOP_NO

    CODE

    STOP

    STOP_ABBR

    NAME

    STOP

    STOP_DESC

    XCOORD

    0 (optional from STOP.POINT_LONGITUDE)

    YCOORD

    0 (optional from STOP.POINT_LATITUDE)

    Visum table: $STOPAREA


    For stop areas, only the data records listed in the STOP table are relevant for which the
    POINT_TYPE value is 1. Coordinates are adopted analogous to the NODE.
    Visum attribute

    Source table

    Source attribute/value/type

    NO

    STOP

    POINT_NO

    CODE

    STOP

    POINT_DESC

    NAME

    STOP

    POINT_DESC

    TYPENO

    STOP

    POINT_TYPE

    XCOORD

    STOP

    0 (optional from STOP.POINT_LONGITUDE)

    YCOORD

    STOP

    0 (optional aus REC_Ort.ORT_POS_BREITE)

    STOPNO

    STOP

    STOP_NO

    Visum table: $STOPPOINT


    For stop points, only data records of the table REC_ OR T are relevant, for which the ONR_
    TYP_NR value is 1. Data records with ONR_TYP_NR =2 (depots) are not adopted.
    As DIRECTED is automatically set to 1 when you read in the network file generated by Visum,
    the field is left empty.
    In the VDV 452 data model, stop points always implicitly form nodes of the link network, while
    in the Visum data model, stop points may also lie on links. If there are stop points on links, a
    representation is generated during data export, in which these stop points are also nodes of
    the link network (see "Visum table: $LINK" on page 2634).

    2632

    Visum attribute

    Source table

    Source attribute/value/type

    NO

    STOP

    POINT_NO

    NODENO

    STOP

    Automatically generated node number


    (see "Visum table: $NODE" on page
    2631)

    CODE

    STOP

    STOP_ABBR

    NAME

    STOP

    POINT_DESC

    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum attribute

    Source table

    Source attribute/value/type

    TSYSSET

    OPERATING_ OP_DEP_ABBR (comma-separated conDEPARTMENT catenation of all values)

    STOPAREANO

    STOP

    POINT_NO

    FROMNODENO

    empty

    DIRECTED

    empty

    LINK NO

    empty

    DEPOTVEHCOMBSTANDARD STOP

    False

    RELPOS

    empty

    Visum table $FAREZONE


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

    Source table

    Source attribute/value/type

    NO

    STOP

    ZONE_CELL_NO

    CODE

    STOP

    ZONE_CELL_NO

    NAME

    STOP

    ZONE_CELL_NO

    Visum table $STOPTOFAREZONE


    Visum attribute

    Source table

    Source attribute/value/type

    FARZONENO

    STOP

    ZONE_CELL_NO

    STOPNO

    STOP

    STOP_NO

    Visum table $LINKTYPE


    Visum attri- Source table
    bute

    Source attribute/value/type

    NO

    TSYSSET

    OPERATING_
    DEPARTMENT

    OP_DEP_ABBR (comma-separated concatenation


    of all values)

    CAPPRT

    99999

    VMINPRT

    RANK

    PTVGROUP

    2633

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum table: $LINK
    Import:
    When you generate links in the Visum data model, the VDV 452 tables LINK, POINT_ON_
    LINK , and STOP are taken into account. Links are created as straight lines (without intermediate points) between two points. The intermediate points specified in POINT_ ON_ LINK
    are not implemented as simple polygon points, but as full-fledged nodes. This way, the entries
    in STOP that are not implemented because of their type are adopted as nodes or route points
    of time profiles. Subsequent to data import, any two-leg nodes created can be deleted if required (see "Deleting several marked nodes" on page 1085). A node pair <FromNode, ToNode>
    is assigned the same link number as <ToNode, FromNode>.
    If the LINK table contains coordinates, these are adopted for the nodes, but here no length is
    entered for the links. When the network file is imported into Visum, the link lengths are calculated automatically. However, the attribute LINK_DISTANCE is adopted as a user-defined
    attribute for the link.
    If the LINK or POINT_ON_LINK table contain attributes that are not directly adopted into Visum
    attributes, these are saved as user-defined attributes to the Visum table LINK.
    Export:
    Note: The LINK table is not generated based on Visum links. It is based on line routes.
    There are no polygon points for instance.
    To generate the tables LINK and POINT_ ON_LINK during data export, not the actual links of
    the Visum network model are used, but an abstract link network that consists of line routes and
    stop points. The route points defined within the line routes are represented in the LINK entries.
    In addition, line route items that are not route points are exported as intermediate points into
    POINT_ON_ LINK. Polygon points of the underlying link network are not exported. Details of
    the LINK_ DISTANCE column that are used during data export are adopted from route points
    in the POSTLENGTH attribute. For other line route items, they are adopted from the LENGTH
    attribute.

    2634

    Visum attribute Source table

    Source attribute/value/type

    NO

    Start value 1, incremented by 1

    FROMNODENO LINKPOINT_ON_
    LINK

    Automatically generated node number (see "Visum


    table: $NODE" on page 2631)

    TONODENO

    LINKPOINT_ON_
    LINK

    Automatically generated node number (see "Visum


    table: $NODE" on page 2631)

    TYPENO

    TSYSSET

    OPERATING_
    DEPARTMENT

    OP_DEP_ABBR (comma-separated concatenation


    of all values)

    LENGTH

    LINK

    if nodes do not contain coordinates: LINK_


    DISTANCE (in m -> / 1000).
    if nodes do contain coordinates: Visum calculates
    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


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

    Source table

    Source attribute/value/type

    NO

    VALIDFROM

    PERIOD

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

    VALIDUNTIL

    PERIOD

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

    TYPE

    Annual calendar (type 0 = 3)

    CODE

    BASE_VERSION

    BASE_VERSION + BASE_VERSION_DESC

    NAME

    empty

    Visum table $VALIDDAYS


    For each type of day listed in the DAY_TYPE table, a row is generated in the VALIDDAYS
    table.
    The DAYVECTOR is generated for the entire time period listed in the CALENDERPERIOD
    table. For all days between the first and last service day, it is initially set to 0.
    In the following step, all values of the current day type in the PERIOD table are compared.
    Then for all service days listed with the same day type, the DAYVECTOR is set to 1.
    In Visum, by default, the number 1 assigned to valid days means daily. If the VDV 452 import
    data includes a valid day with the DAY_TYPE_NO = 1, the program checks whether this refers
    to daily . This is the case, if all calendar days listed in the PERIOD table are assigned to it.
    Then the data with the valid day 1 is adopted. Otherwise a new valid day with the next number
    available is generated. In this case, the numbers of the following valid days imported might
    change, as each time the next available unique number is assigned.
    If the DAY_TYPE table contains attributes that are not directly adopted into Visum attributes,
    these are saved as user-defined attributes to the Visum table VALIDDAYS.
    Visum attribute

    Source
    table

    Source attribute/value/type

    NO

    DAY_
    TYPE

    DAY_TYPE_NO*(see above for description)

    CODE

    DAY_
    TYPE

    DAY_TYPE_NO

    NAME

    DAY_
    TYPE

    DAY_TYPE_NO

    DAYVECTOR

    PTVGROUP

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


    PERIOD table:

    2635

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum attribute

    Source
    table

    Source attribute/value/type
    0 = does not take place
    1 = takes place

    FROMSYSTEM

    Visum table: $LINE


    Only regular service trips are considered (i.e. LINE data records with ROUTE_TYPE = 1). Arrival, departure, and approach trips are not considered.
    .

    Visum attri- Source table


    bute

    Source attribute/value/type

    NAME

    LINE

    LINE_ABBR

    VEHCOMB

    LINE

    OP_DEP_NO

    TSYSCODE OPERATING_
    DEPARTMENT

    OP_DEP_ABBR via LINE.Op_Dep_No = OPERATING_


    DEPARTMENT.Op_Dep_No

    Visum table: $LINEROUTE


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

    Source Source attribute/value/type


    table

    NAME

    Start value 1, incremented by 1

    LINENAME

    LINE

    LINE_ABBR

    DIRECTIONCODE LINE

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

    ISCIRCLELINE

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

    ORG_LI_NR

    LINE

    LINE_NO

    ORG_STR_LI_
    VAR

    LINE

    ROUTE_ABBR

    ORG_ROUTEN_
    NR

    LINE

    ROUTE_NO

    ORG_LIDNAME

    LINE

    LINE_DESC

    Visum table: $LINEROUTEITEM


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

    2636

    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


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

    Source table

    INDEX

    Source attribute/value/type
    Consecutive index

    ISROUTEPOINT

    POSTLENGTH

    LINK

    LINK_DISTANCE/1000 (via LINK.OP_DEP_NO and


    LINK.POINT_NO and LINK.TO_POINT_NO) is required as there are no coordinates.

    LINENAME

    LINE

    LINE_ABBR

    DIRECTIONCODE

    LINE

    DIRECTION (value1 is replaced by > = up, value 2


    is replaced by < = down. See Visum table
    DIRECTION )

    LINEROUTENAME

    LINE

    NAME generated in LINEROUTE

    STOPPOINTNO

    ROUTE_
    SEQUENCE

    POINT_NO

    NODENO

    ROUTE_
    SEQUENCE
    If provided:
    POINT_ON_
    LINK

    Automatically generated node number (see "Visum


    table: $NODE" on page 2631)

    ORG_
    DESTINATION DEST_BRIEF_TEXT
    FAHRERKURZTEXT
    ORG_SEITENTEXT

    DESTINATION DEST_SIDE_TEXT

    ORG_ZNR_TEXT

    DESTINATION DEST_FRONT_TEXT

    ORG_LI_LFD_NR

    ROUTE_
    SEQUENCE

    SEQUENCE_NO

    Visum table $TIMEPROFILE


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

    Source
    table

    NAME

    JOURNEY LINE_NO + |+ ROUTE_ABBR + |+ TIMING_


    TIMING_ GROUP.TIMING_GROUP_NO + |+ TIMING_
    GROUP.TIMING_GROUP.Text (via Timing_Group_No)
    GROUP

    LINENAME

    LINE

    PTVGROUP

    Source attribute/value/type

    LINE_ABBR via JOURNEY.LINE_NO = LINE.LINE_NO


    and JOURNEY.ROUTE_ABBR = LINE.ROUTE_ABBR

    2637

    25.10.2 Comparison of VDV 452 and Visum data model


    Visum attribute

    Source
    table

    Source attribute/value/type

    DIRECTIONCODE LINE

    DIRECTION via JOURNEY.LINE_NO = LINE.LINE_NO


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

    LINEROUTENAME LINE

    NAME generated in LINEROUTE

    VEHCOMBNO

    LINE

    OP_DEP_NO

    ORG_FGR_NR

    JOURNEY TIMING_GROUP_NO

    Visum table $TIMEPROFILEITEM

    2638

    Visum attribute

    Source
    table

    Source attribute/value/type

    INDEX

    Start value 1, incremented by 1

    LRITEMINDEX

    ROUTE_
    ROUTE_SEQUENCE.SEQUENCE_NO via
    SEQUENCE JOURNEY.LINE_NO = ROUTE_SEQUENCE.LINE_
    NO and JOURNEY.ROUTE_ABBR = ROUTE_
    SEQUENCE.ROUTE_ABBR
    The latter is used to create the index of the corresponding line route items.

    LINENAME

    LINE

    LINE.LINE_ABBR via JOURNEY.LINE_NO =


    LINE.LINE_NO and JOURNEY.ROUTE_ABBR =
    LINE.ROUTE_ABBR

    DIRECTIONCODE

    LINE

    DIRECTION via JOURNEY.LINE_NO = LINE.LINE_


    NO and JOURNEY.ROUTE_ABBR = LINE.ROUTE_
    ABBR
    DIRECTION (value 1 is replaced by > = up, value 2 is
    replaced by < = down. See Visum table DIRECTION )

    LINEROUTENAME

    JOURNEY

    NAME generated in LINEROUTE

    TIMEPROFILENAME JOURNEY
    TIMING_
    GROUP

    LINE_NO + |+ ROUTE_ABBR + |+ TIMING_


    GROUP.TIMING_GROUP_NO + |+ TIMING_
    GROUP.TIMING_GROUP.TEXT (via TIMING_
    GROUP_NO)

    BOARD

    For the last data record of a time profile the value is 0,


    otherwise it is 1.

    ALIGHT

    For the first data record of a time profile the value is 0,


    otherwise it is 1.

    ARR

    TRAVEL_
    TIME

    TRAVEL_TIME (added, modulo 24h)

    DEP

    TRAVEL_
    TRAVEL_TIME.TRAVEL_TIME (added) + WAIT_
    TIME+
    TIME.WAIT_TIME (modulo 24h)
    WAIT_TIME
    PTVGROUP

    25.10.2 Comparison of VDV 452 and Visum data model


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

    Source
    table

    Source attribute/value/type

    NO

    Start value 1, incremented by 1

    DEP

    JOURNEY

    FRT_START (modulo 24h)

    LINENAME

    LINE

    LINE_ABBR/char(6) vai JOURNEY.LINE_NO =


    LINE.LINE_NO and JOURNEY.ROUTE_ABBR
    = LINE.ROUTE_ABBR

    DIRECTIONCODE

    LINE

    DIRECTION (value 1 is replaced by > = up,


    value 2 is replaced by < = down. See Visum
    table DIRECTION )

    LINEROUTENAME

    JOURNEY

    NAME generated in LINEROUTE

    TIMEPROFILENAME

    JOURNEY
    TIMING_
    GROUP

    TIMEPROFILE.NAME (= LINE_NO + |+
    ROUTE_ABBR + |+ TIMING_
    GROUP.TIMING_GROUP_NO + |+ TIMING_
    GROUP.TIMING_GROUP_Text via TIMING_
    GROUP_NO)

    FROMTPROFILITEMINDEX -

    TOTPROFILITEMINDEX

    ROUTE_
    Value = Number of data records found for
    SEQUENCE which the following is true:
    JOURNEY.LINE_NO =
    ROUTE_SEQUENCE.LINE_NO and
    JOURNEY.ROUTE_ABBR = ROUTE_
    SEQUENCE.ROUTE_ABBR

    VDVNO

    JOURNEY

    JOURNEY_NO

    ORG_FAHRTART_NR

    JOURNEY

    JOURNEY_TYPE_NO

    ORG_LI_KU_NR

    JOURNEY

    RUN

    Visum table $VEHICLEJOURNEYSECTION


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

    Source
    table

    NO
    VALIDDAYSNO

    PTVGROUP

    Source attribute/value/type
    Always 1

    JOURNEY

    DAY_TYPE_NO according to VALIDDAYS

    2639

    25.10.3 Exporting Visum data to VDV 452


    Visum attribute

    Source
    table

    Source attribute/value/type
    table (see "Visum table $CALENDARPERIOD"
    on page 2635)

    VEHCOMBNO

    LINE

    FROMTPROFILITEMINDEX TOTPROFILITEMINDEX

    OP_DEP_NO
    1

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

    VEHJOURNEYNO

    JOURNEY

    NO generated in VEHJOURNEY

    VEHCOMBSET

    JOURNEY
    TIMING_
    GROUP

    Empty

    VDVNO

    JOURNEY

    JOURNEY_NO

    25.10.3 Exporting Visum data to VDV 452


    During data export from Visum to VDV 452 the following elements are taken into account:
    Element

    Description

    Network

    Nodes,
    Links,
    Link polygons,
    Stop hierarchy,
    Fare zones

    Basic data

    Transport systems,
    Calendars.

    PuT Supply

    Timetable (vehicle journeys)

    Vehicles

    Vehicles (simple)

    Data export is generally based on the PuT supply of the existing vehicle journey sections. The
    vehicle journey sections, including all their network elements (trips, time profiles, lines, stop
    points, links, etc.), are exported. Optionally, you may limit the export to active vehicle journey
    sections (see Fundamentals: Chpt. 11.1.3 , page 725)
    Note: For data export in Visum, the coordinate system WGS84 must be set (see "Selecting a
    coordinate system" on page 2207)
    1. From the File menu, choose Export> VDV 452:
    The VDV 452Export window opens.
    2. Make the desired settings.
    2640

    PTVGROUP

    25.10.3 Exporting Visum data to VDV 452

    Element

    Description

    VDV 452 path

    Into the input field, enter the path of the desired files *.x10, or
    select the path via the

    icon.

    Reference date

    Date the VDV 452 version references in the format DD.MM.YYYY.


    This data is used to define the base version in VDV file and to
    create the file names.

    Export user-defined attributes


    (UDAs)

    If this option is selected, all UDAs are exported that are listed in
    tables relevant for data export.

    Export only active If this option is selected, only active vehicle journey sections,
    vehicle journey
    including their PuT supply objects and the network are exported.
    sections (including all required
    basic data)
    3. Confirm with Execute.
    The data is exported and each VDV 452 table is saved to a separate file.
    File name

    VDV 452 table

    i222DDD0.x10

    TIMING_GROUP

    i225DDD0.x10

    DEAD_RUN

    i226DDD0.x10

    LINE

    i229DDD0.x10

    STOP_POINT

    i246DDD.x10

    ROUTE_SEQUENCE

    i247DDD0.x10

    DEAD_RUN_TIME

    i253DDD0.x10

    STOP

    i282DDD.x10

    TRAVEL_TIME

    i290DDD0.x10

    DAY_TYPE

    i293DDD.x10

    VEHICLE_TYPE

    i295DDD0.x10

    ACTIVATION_POINT

    i299DDD.x10

    LINK

    i332DDD0.x10

    JOURNEY_TYPE

    i333DDD.x10

    OPERATING_DEPARTMENT

    i348DDD0.x10

    PERIOD

    i485DDD0.x10

    BASE_VERSION_VALID

    i715DDD.x10

    JOURNEY

    PTVGROUP

    2641

    25.11 Database interface


    File name

    VDV 452 table

    i992DDD.x10

    TRANSPORT_COMPANY

    i993DDD0.x10

    BASE_VERSION

    i994DDD.x10

    DESTINATION

    i995DDD0.x10

    POINT_ON_LINK

    i996DDD.x10

    ANNOUNCEMENT

    i997DDD0.x10

    STOP_TYPE

    i998DDD0.x10

    POINT_TYPE

    i999DDD0.x10

    WAIT_TIME

    Note: All VDV 452 files are saved to a directory folder and named according to the naming
    scheme in VDV 451: iNNNDDD0.x10, where NNN is the table number and DDD is the day
    number of the reference data specified.

    25.11

    Database interface
    Via the database interface you can export Visum network data to or import from a database.

    25.11.1 Exporting Visum data to an Access database


    1. Make sure the desired decimal separator is selected (see "Selecting a decimal point" on
    page 873).
    2. In the File menu, select the Export> Database entry.
    The Select database window opens.
    3. Select the entry MS Access 2003 or earlier or MS Access 2007 or up.
    4. Confirm with OK.
    The Save Access database window opens.
    5. Enter the file name and the path, if required.
    Tip: Alternatively you can select an existing Access database, which will be overwritten.
    6. Click the Save button.
    The Save network (user-defined) window opens.
    7. Make the desired settings (see "Saving a network file" on page 846).
    8. Confirm with OK.
    The selected network tables and attributes are exported to the Access database.

    2642

    PTVGROUP

    25.11.2 Exporting Visum data to an SQL database


    Notes: When exporting to an Access database, primary keys are also exported.
    When exporting attribute names with more than 64 characters, Visum abbreviates the
    names during the export.
    Example of a Visum network exported to an Access database

    25.11.2 Exporting Visum data to an SQL database


    Note: This function is only provided with the MS SQL server interface add-on (see
    "Enabling or disabling installed add-ons" on page 886).
    1. In the File menu, select the Export> Database entry.
    The Select database window opens.
    2. Select MS SQL server.
    3. Confirm with OK.
    The Data link properties window opens.
    4. Select the Provider tab.
    5. Select the appropriate provider for SQL servers, for example Microsoft OLE DB provider
    for SQL server.
    6. Select the Connection tab.
    Tip: Alternatively you can click the Next button in the Provider tab.
    7. Enter the server name where the SQL database is.

    PTVGROUP

    2643

    25.11.3 Importing an Access database


    Tip: Alternatively select the name from the drop-down list.
    8. Enter user name and password to access the SQL server.
    9. Select the option Allow password to be saved.
    10. From the drop-down list select the desired database on the SQL server.
    Tip: You can check whether the connection to the SQL server has been established
    and export to the database can take place by clicking the Test connection button.
    11. Confirm with OK.
    The Save network (user-defined) window opens.
    12. Make the desired settings (see "Saving a network file" on page 846).
    13. Confirm with OK.
    A query opens.
    14. Click Yes to confirm.
    The selected network tables and attributes are exported to the database on the SQL server.

    25.11.3 Importing an Access database


    You can read complete networks from an existing Access database or selected network tables
    additionally to the current network table.
    Note: The database has to contain table $Version which is required for the import.
    1. In the File menu, select the Import> Database entry.
    The Select database window opens.
    2. Select the entry MS Access 2003 or earlier or MS Access 2007 or up.
    3. Confirm with OK.
    The Open Access database window opens.
    4. Select the desired file.
    5. Click the Open button.
    The Read network window opens.
    6. Make the desired settings (see "Opening a network file" on page 845 and "Reading network data additionally" on page 851).
    7. Confirm with OK.
    The import of network data from the Access database is started. If you have selected the option
    Read network file additionally, the Read network data additionally window also opens (see
    "Reading network data additionally" on page 851). If the network data contains incomplete line
    routes or system routes, i.e. at least one link or stop point is missing in the route course or
    2644

    PTVGROUP

    25.11.4 Importing an SQL database


    blocked for the transport system, the Read network (completing LineRoute/SystemRoute)
    window also opens (see "Reading a network file with incomplete line routes or system routes"
    on page 861).

    25.11.4 Importing an SQL database


    You can read complete networks from an existing SQL database or selected network tables
    additionally to the current network table.
    Note: The database has to contain table $Version which is required for the import.
    1. In the File menu, select the Import> Database entry.
    The Select database window opens.
    2. Select MS SQL server.
    3. Confirm with OK.
    The Data link properties window opens.
    4. Select the Provider tab.
    5. Select the appropriate provider for SQL servers, for example Microsoft OLE DB provider
    for SQL server.
    6. Select the Connection tab.
    Tip: Alternatively you can click the Next button in the Provider tab.
    7. Enter the server name where the SQL database is.
    Tip: Alternatively select the name from the drop-down list.
    8. Enter user name and password to access the SQL server.
    9. Select the option Allow password to be saved.
    10. From the drop-down list select the desired database on the SQL server.
    Tip: You can check whether the connection to the SQL server has been established
    and export to the database can take place by clicking the Test connection button.
    11. Confirm with OK.
    The Read network window opens.
    12. Make the desired settings (see "Opening a network file" on page 845 and "Reading network data additionally" on page 851).
    13. Confirm with OK.
    The import of network data from the SQL database is started. If you have selected the option
    Read network file additionally, the Read network data additionally window also opens (see
    "Reading network data additionally" on page 851). If the network data contains incomplete line

    PTVGROUP

    2645

    25.11.5 Connecting Visum to a Personal Geodatabase


    routes or system routes, i.e. at least one link or stop point is missing in the route course or
    blocked for the transport system, the Read network (completing LineRoute/SystemRoute)
    window also opens (see "Reading a network file with incomplete line routes or system routes"
    on page 861).

    25.11.5 Connecting Visum to a Personal Geodatabase


    You can display GIS objects in your network by connecting to a Personal Geodatabase (PGD)
    (see "GIS objects" on page 2211).
    Note: For data exchange you need an ArcView license for version 8.3 and higher.
    Connecting a Personal Geodatabase
    From File menu, choose Import> Connect to Personal Geodatabase (see "Connecting
    Visum to a Personal Geodatabase" on page 2211).
    Disconnecting a Personal Geodatabase
    From the File menu, choose Import> Disconnect Personal Geodatabase (see "Disconnecting a Personal Geodatabase" on page 2217).

    25.12

    Attribute interface
    The attribute interface is used to exchange attribute data of Visum network objects (e.g. node
    names or link volumes) with other programs or other Visum networks.
    You may save the attribute values in attribute files *.att which you can read in Visum, spreadsheet programs or databases in *.csv format. Using the Windows clipboard you can import them
    into another Visum network or in other programs, too.

    25.12.1 Saving an attribute file


    To save attribute values of network objects, open the list of the desired network object and
    save the attribute data displayed as an attribute file *.att (see "Save list to attribute file" on page
    2325).

    25.12.2 Reading an attribute file


    You can read attribute values from an attribute file *.att into a Visum network.
    1. Click the

    Open icon.

    The Select file type window opens.


    2. Select Attributes.
    3. Confirm with OK.
    The Open attributes window opens.
    4. Select the desired file.
    5. Click the Open button.
    The Read attributes window opens.
    2646

    PTVGROUP

    25.12.2 Reading an attribute file

    6. Make the desired changes.


    Element

    Description

    Column

    The numbers reflect the order in which the attribute columns are
    read.

    SourceAttributeID

    The codes of the attributes read are displayed.


    Note
    The codes correspond to the column identifiers of the attribute
    file.

    SourceAttributeName

    The long names of the attributes read are displayed.

    Target attribute

    Use this button to select a target attribute (and a subattribute, if


    available) for each source attribute in a separate window, into
    which the values of the source attribute are read (see "The window used for the selection of one attribute" on page 963).
    Tip
    Alternatively, you can create a user-defined attribute as target
    attribute.
    Notes
    If no target attribute is selected for a source attribute, the attribute values of the source attribute are not read.
    If the same target attribute is selected for multiple source attributes, only the attribute values of the source attribute last read
    (highest column number of the same target attribute) is taken,
    whose value range corresponds to the value range of the target
    attribute.

    New

    PTVGROUP

    Use this button to create a user-defined attribute as target attribute for each source attribute in a separate window (see "Mana-

    2647

    25.12.2 Reading an attribute file


    Element

    Description
    ging user-defined attributes" on page 973).

    Generate

    Via this button you can create simultaneously user-defined attributes for all source attributes to which no target attribute is allocated. Select the data type for the new, user-defined attributes
    from the selection list in a separate window (see "Generating
    user-defined attributes when reading attributes" on page 977).

    Sum up

    If this option has been selected, the values of the read source
    attributes are added to those of the selected target attributes in
    the existing network.
    If the option has not been selected, the values of the target
    attributes are replaced by those of the source attributes.
    Note
    This option is only available for numerical target attributes.

    Extended

    Click this button to define settings for a shortest path search of


    links between To node and From node in a separate window
    (see "Exception: Reading link attributes for links that do not exist
    within the network" on page 2648).
    Note
    We recommend carrying out the shortest path search if link attributes with node-related key attributes are to be read that cannot
    be allocated to any links within the network.

    7. Confirm with OK.


    The attribute values of the attribute file are read into the network.
    Note: If you read an attribute file, Visum first checks whether a column identifier corresponds to an attribute ID. If this is the case, it is suggested. If this is not the case, for
    example, because the file contains aliases as attribute names, Visum checks whether it
    is a valid alias (see "Specifying an alias for attribute names" on page 967).
    Exception: Reading link attributes for links that do not exist within the network
    If you want to read in link attributes with node-related key attributes (From node and To node;
    i.e. without link number) that cannot be allocated to any links within the network, you can perform a shortest path search between the From nodes and To nodes of the corresponding links.
    1. Read in a link attribute file (see "Reading an attribute file" on page 2646).
    The Read attributes window opens.
    2. Click the Advanced button.
    The Read link attributes: Search parameters window opens.

    2648

    PTVGROUP

    25.12.2 Reading an attribute file

    3. Make the desired changes.


    Element

    Description

    Ignore link

    If the option has been selected, attribute values for which no links
    with the relevant From nodes and To nodes are found in the network are disregarded when reading the file.

    Search for shortest path

    If this option has been selected, a shortest path search From


    node to To node with the set search parameters is carried out.

    Transport system From the list, select the transport system the shortest path search
    is to be carried out.
    Note
    The list is only available if the Search for shortest path option
    has been selected.
    Tip
    You can also carry out the shortest path search for all transport
    systems defined in the network by selecting All in the list. Blocked
    links and turns are disregarded.
    Use also closed
    links for routing

    If this option has been selected, links actually closed for the
    transport system are considered open for the transport system.
    If the option has not been selected, closed links are not regarded for the shortest path search.
    Note
    This option is only available if the shortest path search is carried
    out for one transport system only.

    Use also closed


    turns for routing

    If this option has been selected, turns closed for the transport
    system are considered open for the transport system.
    If the option has not been selected, closed turns are not regarded for the shortest path search.

    PTVGROUP

    2649

    25.12.3 Exchanging attribute data via the clipboard


    Element

    Description
    Note
    This option is only available if the shortest path search is carried
    out for one transport system only.

    Search criterion

    Any numerical link attribute and its subattribute, if applicable, can


    be selected from the list and can serve as a search criterion.
    Note
    The list is only available if the Search for shortest path option
    has been selected.

    Attribute data / dis- From the list, select how attribute values are to be assigned to
    tribution
    links that are found within the network.
    Assign only to the first link
    If this option has been selected, the attribute data is used just for
    the first link of the route that was found.
    Use for all links
    If this option has been selected, the attribute value is used for all
    links found within the network between the From Node and the To
    Node.
    Note
    The list is only available if the Search for shortest path option
    has been selected.
    4. Confirm with OK.
    The settings are applied.

    25.12.3 Exchanging attribute data via the clipboard


    Using the Windows Clipboard, you can copy attribute data in order to paste it directly into a different Visum network version or a different program (see "Exchanging list contents via the Clipboard" on page 2328).

    25.13

    Graphics interfaces
    You can export the current network display as a graphics file for later editing in Visum or other
    external graphics programs.
    The following graphics interfaces are available:
    PostScript-PDF export
    DXF export
    SVG export
    Exporting screenshots
    General graphics interface for various common graphics data formats (see "Using backgrounds in the network display" on page 2237)

    2650

    PTVGROUP

    25.13.1 PostScript-PDF export


    In Visum, you can also import graphics files as a background (see "Inserting background
    images of map services on the Internet" on page 2237).
    The following figure illustrates the possible data exchange between Visum and external
    graphics programs.

    25.13.1 PostScript-PDF export


    PostScript and PDF files have several advantages over files in original format in that they are
    platform-independent, that no loss of formatting occurs and that you do not need to have the
    software version with which they were created.
    You can edit and process the exported images without any restrictions whatsoever. Thus,
    Visum network displays can be easily made accessible for further flexible processing in DTP,
    layout and image editing software. In a *.pdf file imported into, for example, Macromedia
    FreeHand 8.0, all lines, surfaces, labels etc. can be freely edited.
    There are also no problems using the Portable Document Format (PDF) of Adobe for displays
    on the Internet (e.g. in Internet Browser) and in interactive media. It can contain hyperlinks,
    comments and bookmarks and supports various compression formats such as JPEG or LZW.
    Last but not least, *.pdf documents can be indexed by search engines such as Excite for Web
    Servers. Because of these advantages, the *.pdf format has become the main standard for the
    document exchange on the Internet.
    Note: Visum does not offer a direct graphic export in *.pdf format, because this is only possible by using commercial software (for example Acrobat Distiller as a module of Adobe
    Acrobat).

    PTVGROUP

    2651

    25.13.1.1 Exporting the network display as a PostScript file


    Tip: You can create a *.pdf file from a Visum network display by exporting it into a PostScript file using a PostScript-enabled Windows printer driver, and then to convert it into
    *.pdf format (see "Converting a PostScript file into a PDF file" on page 2654).
    25.13.1.1 Exporting the network display as a PostScript file
    1. Make sure that a PostScript-enabled Windows printer driver is installed.
    Note: The following description is for the operating system Windows 7. In the Visum
    user manual 12 or earlier, you find the description for the operating system Windows
    XP.
    2. In Windows, open the printer management.
    3. Select the desired printer driver.
    4. In the menu, choose the Print server properties entry.
    The Properties of Print server window opens.
    5. Select the Ports tab.
    6. For the printer driver set up the FILE connection.

    7. Confirm with OK.


    8. In the Visum menu File, point at the Print entry.
    9. Select the Print entry.
    The Print: Network window opens.
    10. In the Printer section, select the printer driver from the Name drop-down list.
    11. Make sure that the Print to graphics file option has not been selected.
    2652

    PTVGROUP

    25.13.1.1 Exporting the network display as a PostScript file

    Note: This option is only relevant when exporting into *.svg and *.dxf format (see "DXF
    export" on page 2654 and "SVG export" on page 2656).
    12. Click the Properties button.
    The <Name of printer driver> printer properties window opens.
    13. Make the desired changes.
    14. Close the <Name of printer driver> printer properties window with OK.
    15. If desired, click the Set up print page button.
    The Set up page window opens.
    16. Make the desired settings (see "Set print page" on page 2499).
    17. Confirm with OK.
    18. Close the Print settings window with OK.
    The Print to file window opens.

    19. Enter file name, select directory and file extension *.ps or *.eps.
    Notes: By entering the file extension *.ps, the PostScript file is directly readable by
    PDF conversion programs.
    By entering the file extension *.eps the PostScript file is directly readable in many text
    and layout programs such as Microsoft Word, for example, if it was generated as an
    Encapsulated PostScript file.
    20. Confirm with OK.
    The network display is exported as PostScript file.
    Note: PostScript can be extremely large. The *.pdf file that is subsequently generated,
    however, can even be 20 times smaller than the original file.
    Tip: You can open and edit PostScript files in image processing, graphics, desktop publishing and word processing programs. The following programs are supported (tested for
    the stated versions and onwards):
    Drawing and graphics programs: CorelDraw 7+, Macromedia FreeHand 7.0, Adobe
    Illustrator 7.0
    Word processing and page layout programs: Microsoft Word 6.0, Adobe Pagemaker
    6.5, Quark X Press 4.0
    Image processing systems: Corel Photo-Paint 7+, Adobe Photoshop 3.0
    Presentation programs: Microsoft PowerPoint 97
    PTVGROUP

    2653

    25.13.1.2 Converting a PostScript file into a PDF file


    Notes: In CorelDraw 7+ the PostScript file can be opened directly as vector graphic. Figures and text, however, can no longer be edited as a string.
    In Adobe Photoshop 4+ the PostScript file can be opened directly as a raster image by
    entering target parameters such as resolution, color system etc. The edited PostScript file
    can be saved in *.bmp, *.jpg and *.gif format.
    If the PostScript file has been saved as Encapsulated PostScript with the extension *.eps,
    it is directly readable by many text and layout programs such as Microsoft Word, for example. The file cannot be displayed on screen or its size be modified if the program does
    not provide a preview functionality (e.g. *.tif). We recommend using a graphic converter
    or another suitable graphics tool to generate either a raster graphics file (for example
    *.bmp) or a vector graphics (for example *.wmf, which is supported by Microsoft Word)
    from the PostScript file first and open it then. For Microsoft application you can also use
    the OLE function.
    25.13.1.2 Converting a PostScript file into a PDF file
    There are several ways to generate a *.pdf file from a Visum network display.
    To export the network display directly as *.pdf file you need the commercial software Acrobat Distiller as a module of Adobe Acrobat. After installing Distiller, it is used by Visum just
    like any other Windows printer driver.
    You can also export the network display as PostScript file, using a PostScript-enabled Windows printer driver (see "Exporting the network display as a PostScript file" on page
    2652), and subsequently convert it into *.pdf format.
    To convert a PostScript file to a *.pdf file you can use non-commercial software, for example
    the freeware tool Aladdin Ghostview/Ghostscript, available at the URL http://pages.cs.wisc.edu/~ghost/.
    You can also use non-commercial online conversion services provided by universities and universities of applied sciences, for example, available on the Internet from http://convert.neevia.com/ and http://www.ps2pdf.com/convert.htm.

    25.13.2 DXF export


    Using the DXF export interface, you can save the current network display as a graphic file
    *.dxf.
    There are two ways to save the current network display as graphic file *.dxf.
    First possibility of a DXF export
    1. From the File menu, choose Export> DXF export.
    The Save DXF file window opens.
    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The DXF export window opens.

    2654

    PTVGROUP

    25.13.2 DXF export

    4. Select the line style for the display of the lines in the *.dxf graphics file.
    5. Confirm with OK.
    The current network section is saved as a graphic file *.dxf.
    Tips: You can open the *.dxf graphics file for further editing in an external graphics program or read it into Visum as a background (see "Inserting background images of map
    services on the Internet" on page 2237).
    You can also export other views as files in the *.dxf format. To do so, from the menus
    Timetable editor, Signal time-space diagram or Transfers display of regular services,
    choose DXF Export. From the Schematic line diagram menu, choose Export> DXF
    export, and continue with step 2.
    Second possibility of a DXF export
    1. Choose the File menu. Then point to Print.
    2. Select the Print entry.
    The Print: Network editor window opens.
    3. In the File output section, select Print to graphics file.
    4. Confirm with OK.
    The Save: Graphics file window opens.
    5. From the File type drop-down list, select Graphics file (*.dxf).
    6. Enter the file name and the path, if required.
    7. Click the Save button.
    The DXF export window opens.
    8. Select the line style for the display of the lines in the *.dxf graphics file.
    9. Confirm with OK.
    The current screen window is saved as *.dxf graphics file.
    Tip: You can open the *.dxf graphics file for further editing in an external graphics program or read it into Visum as a background (see "Inserting background images of map
    services on the Internet" on page 2237).

    PTVGROUP

    2655

    25.13.3 SVG export

    25.13.3 SVG export


    Note: This function is only provided with the SVG export add-on (see "Enabling or disabling installed add-ons" on page 886).
    The SVG (Scalable Vector Graphics) format developed by the World Wide Web Consortium
    (W3C) is a graphics format for the Internet based on XML.
    The *.svg graphics files can be viewed with browsers natively supporting the *.svg format or
    having an SVG plug-in.
    You can edit these files in other graphics programs, for example Adobe Illustrator, or with the
    Open Source vector graphics editor Inkscape, available from http://www.inkscape.org. Moreover, you can edit the files using a text editor. The *.svg format is ideal as a graphics exchange
    format and offers numerous advantages compared to other graphics formats:
    Scalability with no loss in quality
    Rotatable and infinite zoomability
    Embedded information on objects
    Interactive access to objects
    Manipulation through script
    Animation
    You can read *.svg graphics files in Visum as background (see "Inserting background images
    of map services on the Internet" on page 2237).
    Tip: You can also export other views as files in the *.svg format. To do so, from the menus
    Timetable editor, Signal time-space diagram or Transfers display of regular services,
    choose SVG export. From the Schematic line diagram menu, choose Exporti> SVG
    export.
    25.13.3.1 Exporting a network display as a *.svg graphics file
    There are two possibilities to export an *.svg graphics file.
    First possibility to export an *.svg graphics file
    1. From the File menu, choose Export> SVG export.
    The Save SVG file window opens.
    2. Enter the file name and the path, if required.
    3. Click the Save button.
    The SVG export: <Name of the selected view> window opens.

    2656

    PTVGROUP

    25.13.3.1 Exporting a network display as a *.svg graphics file

    Note: The window contains a button which is labeled either with Extend or Reduce. If
    you click the Extend button, more export options are displayed in the window. If you
    click the Reduce button, the window is reduced.
    4. Make the desired changes.
    Element

    Description

    Output file

    With the option you specify whether the exported file shall be
    adjusted for a display in a browser, as Visum background, or for
    further editing in Adobe Illustrator (see "Notes on Visum SVG files
    in Adobe Illustrator" on page 2661) or Inkscape.
    Optimized for browser display
    If the option has been selected, the exported file is optimized for a
    display in a browser.
    Optimized as Visum background
    If the option has been selected, the exported file is optimized for a
    display as Visum background.
    Optimized for Inkscape
    If the option has been selected, the exported file is optimized for
    Ink-scape.
    Optimized for Adobe Illustrator
    If the option has been selected, the exported file is optimized for
    Adobe Illustrator.
    Note
    If the SVG export is optimized for further editing in Adobe Illustrator or Inkscape, the graphics is transformed to an output page.
    The settings for the output page are specified in a separate window that opens automatically, if you confirm with OK.

    General options

    In this section, useful settings are predefined, depending on the


    selection in the Output file section.

    PTVGROUP

    2657

    25.13.3.1 Exporting a network display as a *.svg graphics file


    Element

    Description
    Embed SVG file in HTML
    If the option has been selected, an *.svg file and an *.html
    page with the *.svg file embedded are exported. In addition, a
    *.css is exported, which you can use to adjust the layout of the
    Html page.
    If the option has not been selected, only an *.svg is exported.
    Note
    This option is only relevant for browser display.
    Tip
    An *.svg file embedded in Html has the advantage that the Html
    page contains a control of all levels which can be used to switch
    the respective levels on or off in the browser.
    Create clipping rectangle
    If selected, this option defines a rectangular area where all graphical objects are inserted. This area is the current screen window.
    All objects that exceed the rectangle are cut off.
    No line width scaling
    If this option has been selected, lines are displayed at constant
    width when zooming in the SVG graphics. A link can thus for
    example always be displayed with a constant millimeter width.
    If this option has not been selected, the line width is scaled
    when zooming in the SVG graphics.
    Note
    Most browsers do not interpret the SVG characteristics correctly
    which is used when selecting the option. Opera from version 9 is
    an exception. We thus recommend choosing this option only
    when using the exported SVG file as Visum background.
    Use original coordinates
    If this option has been selected, in the *.svg file the original
    coordinates are used for all elements and then transformed into
    the SVG coordinate system.
    If the option has not been selected, the coordinates are transformed in Visum before the export.

    Connections

    Use absolute paths


    If this option has been selected, the absolute paths referring to
    the graphics files integrated in the version are saved to the *.svg
    file.
    If the option has not been selected, the relative paths referring
    to the graphics files integrated in the version are saved to the
    *.svg file.

    2658

    PTVGROUP

    25.13.3.1 Exporting a network display as a *.svg graphics file


    Element

    Description
    Note
    We recommend using relative paths.
    Copy images to SVG folder
    If the option has been selected, a copy of the graphics file integrated in the version (e.g. POI, backgrounds or symbols for point
    objects) are saved to the same directory as the *.svg file.
    If the option has not been selected, the *.svg file continues to
    use the graphics files integrated in the version.

    JavaScript

    Create Onclick Event Handler


    If the option has been selected, a Javascript Event Handler is
    generated.
    Note
    If you display the SVG file in a browser and activate JavaScript for
    your browser, you can access the objects in the *.svg file interactively by clicking individual objects when selecting the option. A
    separate window then displays information (key attributes) on the
    objects and the layers containing objects. You can add further
    user-defined functions, for example COM commands, to the
    JavaScript file.
    Swap function to file
    If the option has been selected, the JavaScript code is swapped to an external file.
    If the option has not been selected, the JavaScript code is
    saved to the SVG file.
    Notes
    The option is only available, if the Create Onclick Event Handler
    option has been selected.
    An external file is useful if you want to modify the script and have
    to call this function from several different SVG files.

    5. Confirm with OK.


    If you have selected the option Optimized for browser display, the network display is
    exported directly. If you have selected the option Optimized for Adobe Illustrator, the Set
    up the output page for SVG export window opens.
    6. Make the desired changes for the size of the graphic for output.
    Element

    Description

    Preview

    Preview of the output page with the current settings

    Parameters

    Use the drop-down list to select a predefined page size (e.g.

    PTVGROUP

    2659

    25.13.3.1 Exporting a network display as a *.svg graphics file


    Element

    Description
    DINA4 or DINA3).
    Width
    Here you can adjust the width of the output page manually.
    Height
    Here you can adjust the height of the output page manually.
    Margin
    Here you can adjust the width of the margin.
    In another drop-down list, you can select the desired length unit.
    Portrait / Landscape
    Here you can select the desired page format.

    7. Confirm with OK.


    The network display is exported as *.svg graphics file.
    Notes: All fonts installed on the system can be exported in *.svg format. We recommend
    using standard fonts, for example Arial or Times New Roman, for text and labeling, since
    the display of some fonts in the SVG Viewer is not compatible with the Visum screen display.
    SVG files can only display raster graphics in the formats *.jpg , *.gif and *.png . If raster
    graphics in other formats are integrated in the version, a copy in format *.png is generated and integrated into the SVG graphics.
    Second possibility to export an *.svg graphics file
    1. Choose the File menu. Then point to Print.
    2. Select the Print entry.
    The Print window opens.
    3. In the File output section, select Print to graphics file.
    4. Confirm with OK.
    The Save: Graphics file window opens.
    5. From the File type drop-down list, select Graphics file (*.svg).
    6. Enter the file name and the path, if required.
    7. Click the Save button.
    The SVG export window opens.
    8. Make the desired settings (see "First possibility to export an *.svg graphics file" on page
    2656).
    9. Confirm with OK.

    2660

    PTVGROUP

    25.13.3.2 Notes on Visum SVG files in Adobe Illustrator


    If you have selected the option Optimized for browser display, the network display is
    exported directly. If you have selected the option Optimized for Adobe Illustrator, the Set
    up the output page for SVG export window opens.
    10. Make the desired changes for the output size of the graphic (see "First possibility to export
    an *.svg graphics file" on page 2656).
    11. Confirm with OK.
    The network display is exported as *.svg graphics file.
    Example of a network display exported in *.svg format
    The screen section is saved to an *.svg file embedded in HTML. The layers for the connector
    and stop point objects are de-activated and therefore not visible.

    25.13.3.2 Notes on Visum SVG files in Adobe Illustrator


    When exporting a network display as *.svg file optimized for Adobe Illustrator, you should take
    the following into account.
    Position
    If you open an *.svg file using Adobe Illustrator, the SVG file is automatically placed in the
    middle of the standard page. This is A4 portrait usually. The SVG ViewBox offset is ignored.

    PTVGROUP

    2661

    25.13.3.3 Changing the coding of Visum SVG files


    If you want to move the graphics to a different position on the page, you have to do it manually.
    Dimensions
    The output size of the rectangle is predefined in the Set up the output page for SVG export
    window (see "Exporting a network display as a *.svg graphics file" on page 2656). Thickness
    of lines and other settings may deviate slightly (in the 1/100 mm range), as co-ordinates are
    converted into world co-ordinates in Visum first and transformed and recalculated then.
    Patterns
    When exporting patterns, the correct size is used, which can, nevertheless, not be interpreted
    correctly by the Adobe Illustrator. Hatchings appear to be either too large or too small. Try to
    avoid specification of patterns for an export which is optimized for Adobe Illustrator.
    Arrows
    Paths with arrow heads are exported correctly and also displayed correctly in the SVG Viewer.
    Using Adobe Illustrator, arrow heads will be displayed, but not the arrows themselves. This problem has been solved by saving the arrows twice, once with and once without reference to the
    arrow head.
    In case of objects added to the clipping rectangle, neither arrows nor arrow heads will be displayed in Adobe Illustrator. Therefore, we recommend deactivating the Create clipping rectangle option for images with arrows (see "Exporting a network display as a *.svg graphics file"
    on page 2656).
    Objects outside of the draw area
    In Adobe Illustrator, an SVG image is placed in the center of the page. Here, the program does
    not use the ViewBox settings of the image, but the frame (bounding box) containing all objects.
    When exporting from Visum, the objects are not cut out if they exceed the current display. If a
    large proportion of the objects exceeds the display, the actual visible display might be located
    outside the Adobe Illustrator page. In case of objects exceeding the maximum drawing area of
    Adobe Illustrator, nothing will be displayed. Even adding objects to a clipping rectangle does
    not change anything.
    Length units
    In Adobe Illustrator, only SVG elements in millimeter sizes are interpreted correctly. When
    exporting an SVG from Visum, only millimeter sizes are thus used if the export is optimized for
    Adobe Illustrator. The selection of a different unit in the Set up the output page for SVG
    export window only serves the purpose of a simplified handling, if you prefer a different unit.
    Illustrator-optimized SVG graphics in browsers
    In a browser, you can display an *.svg file optimized for Adobe Illustrator, but the display is of a
    poor quality. Line widths are incorrect since Adobe Illustrator interprets the data differently
    than the SVG viewer.
    25.13.3.3 Changing the coding of Visum SVG files
    Both *.svg and *.html files are stored in the international Unicode font. The coding is UTF-8,
    which is the standard coding for XML documents. The HTML page you can embed the SVG

    2662

    PTVGROUP

    25.13.4 Exporting screenshots


    file in is in XHTML and thus can be coded using UTF-8, too.
    You have to change the coding in the browser in case of incorrect display of special characters causing incorrect layer control.
    Edit the coding in the Internet Explorer browser as follows:
    1. Right-click the HTML page.
    A shortcut menu opens.
    2. Select the Coding> Unicode (UTF-8) entry.
    The UTF-8 coding is applied.

    25.13.4 Exporting screenshots


    You can save a screenshot of the current window (without the frame) as a graphic file with the
    extension *.jpg, *.bmp, *.gif, *.tiff, *.png, *.emf or *.wmf.
    1. In the Network editor window, on the toolbar, click
    Save screenshot window opens.

    JPG export (screenshot). The

    Tip: Alternatively, from the File menu, choose Export> JPG export (screenshot).
    2. Enter the file name and the path, if required.
    3. From the File type drop-down list, select the desired type of file.
    4. Click the Save button.
    The Save screenshot window opens.
    5. From the file type drop-down list, select the desired type of file.
    Notes: The default dpi value is the specified resolution or a multiple of the user's
    screen.
    If you save a *.jpg file, you can also specify the desired quality of the exported
    graphics.
    6. Confirm with OK.
    The current screen display is saved as graphics file.
    Tips: You can also export other views as a screenshot. To do so, on the toolbar of the windows Timetable editor, Signal time-space diagram, Transfers display of regular services or Schematic line diagram, click the
    JPG export (screenshot). Then
    continue with step 2.
    You can open the graphics file for further editing in an external graphics program or open
    it in Visum as a background (see "Inserting background images of map services on the
    Internet" on page 2237).

    PTVGROUP

    2663

    26 Working with scripts

    26

    Working with scripts


    You can incorporate your own script files in Visum in order to adapt the program to your needs
    and to automate recurring tasks. Furthermore, some scripts allow editing script parameters
    directly in Visum, i.e. without using a text editor and without versed programming skills.
    Subjects
    Running script files
    Editing the script menu
    Embedding add-ins automatically via a project directory
    Integrating script files or script code into the procedure sequence
    Python as additional script language

    26.1

    Running script files


    1. In the Scripts menu, select the Run script file.
    The Open script window opens.
    2. Select the desired script file.
    Note: You can only use script files with the extensions *.vbs, *.js, *.pys or *.py.
    3. Click the Open button.
    The script file is read and run.

    26.2

    Editing the script menu


    You may insert script files as user-defined entries in the Scripts menu. Moreover, you can
    define shortcuts for a quick opening of the script files.

    1. In the Scripts menu, select Edit script menu.


    The Edit script menu window opens. The entries and the submenu entries of the Scripts
    menu are displayed.

    2664

    PTVGROUP

    26.2.1 Creating a new entry in the script menu

    2. Make the desired changes.


    Element

    Description
    Move entry (with all possibly existing subentries) one position up.
    Move entry (with all possibly existing subentries) one position down.

    Open

    Open existing script menu file including entries

    Save

    Save all entries in the script menu as script menu file in XML format

    Create

    Create new entry (see "Creating a new entry in the script menu" on
    page 2665) or submenu entry (see "Creating a new submenu entry in
    the script menu" on page 2666) at the selected position

    Edit

    Edit selected entry or submenu entry (see "Editing a submenu entry


    or an entry in the script menu" on page 2666)

    Delete

    Delete selected entry

    Clean up

    Delete all invalid entries (highlighted) from the script menu


    Note
    All entries appear invalid, if access to the scripts on the saved path is
    not possible, for example, if the path has changed or the connection
    to the respective network drive is interrupted.

    3. Confirm with OK.


    The settings are applied.

    26.2.1

    Creating a new entry in the script menu


    You can create script files or add-ins as entries in the script menu.
    1. In the Scripts menu, select Edit script menu.
    The Edit script menu window opens. The entries and the submenu entries of the Scripts
    menu are displayed.
    2. Select the level at which the new entry is to be created.

    PTVGROUP

    2665

    26.2.2 Creating a new submenu entry in the script menu


    3. Click the Create button.
    The Script menu entry window opens.
    4. Make the desired changes (see "Functions in the script menu entry window" on page
    2667).
    5. Confirm with OK.
    The new entry is created in the script menu.

    26.2.2

    Creating a new submenu entry in the script menu


    Using submenu entries you can create new, subordinate levels in the script menu. They serve
    as containers for entries with script files or add-ins. Thus, you can structure the script menu thematically.
    1. In the Scripts menu, select Edit script menu.
    The Edit script menu window opens. The entries and the submenu entries of the Scripts
    menu are displayed.
    2. Select the level on which you want to create a submenu entry.
    3. Click the Create button.
    The Script menu entry window opens.
    4. Select the Submenu entry option.
    The fields which are not relevant for submenu entries are hidden.
    5. Make the desired changes (see "Functions in the script menu entry window" on page
    2667).
    6. Confirm with OK.
    The new submenu entry is created in the script menu.

    26.2.3

    Editing a submenu entry or an entry in the script menu


    1. In the Scripts menu, select Edit script menu.
    The Edit script menu window opens. The entries and the submenu entries of the Scripts
    menu are displayed.
    2. Select the submenu entry or the entry you want to edit.
    3. Click the Edit button.
    Note: Alternatively double-click the submenu entry or the entry to be edited.
    The Script menu entry window opens.
    4. Make the desired changes (see "Functions in the script menu entry window" on page
    2667).
    5. Confirm with OK.

    2666

    PTVGROUP

    26.2.4 Functions in the script menu entry window


    Changes are applied.

    26.2.4

    Functions in the script menu entry window

    Element

    Description

    Submenu entry Select this option to add a submenu entry to the script menu. All fields
    below the Valid range section are hidden.
    Menu command

    Name of the submenu entry or the script menu entry

    Valid range

    User
    Entry only available to the current user currently logged on
    Computer
    Entry available to all users of the computer

    Script

    If this option has been checked, you can select the desired script file
    for the entry via the
    path directly.

    Add In

    button in the Script name section or enter the

    If this option has been checked, you can select the desired add-in in
    the Add In section.
    Parameters
    Use this button to open the corresponding window with the parameters of the add-in and adjust them, if necessary.
    Show parameter dialog before execution?
    If this option has been selected, the corresponding parameter window is displayed before the execution of the add-in.

    Key combination

    26.3

    Configure the shortcuts by which you want to open the script file or
    the add-in. All combinations of C TRL and/or SHIFT and/or ALT and a letter or a digit are possible.

    Embedding add-ins automatically via a project directory


    If you save add-ins in the specified project directory (menu File> Project directories> Edit
    project directories , file type Visum add-ins ), Visum scans this directory at every program

    PTVGROUP

    2667

    26.3.1 Adjusting parameters of add-ins


    start-up and creates the add-ins both in the Scripts menu and if appropriate as procedure
    in procedure selection (see "Integrating script files or script code into the procedure sequence"
    on page 2668).

    26.3.1

    Adjusting parameters of add-ins


    1. In the Scripts menu, select Edit script menu.
    The Edit script menu window opens. The entries and the submenu entries of the Scripts
    menu are displayed.
    2. Select the submenu entry or the add-in whose parameters you want to edit.
    3. Click the Edit button.
    Note: Alternatively double-click the submenu entry or the entry to be edited.
    The Script menu entry window opens.
    4. Select the Add In option.
    5. In the Add In section, click the Parameters button.
    The Parameters of add-in name window opens.
    6. Make the desired changes.
    7. Confirm with OK.
    8. In the Script menu entry window confirm with OK.
    9. In the Edit script menu window confirm with OK.
    Changes are applied.

    26.4

    Integrating script files or script code into the procedure sequence


    You can call a script file or script code at each point of the procedure sequence.
    Note: Only actions that would disrupt current running procedures, for example, LoadVersion, are not permitted.
    1. From the Calculate menu, choose Procedure sequence.
    The Procedure sequence window opens.
    2. Click the Create button.
    The Procedure window opens.
    3. Select Miscellaneous> Run script.
    Note: You will find scripts integrated as add-ins in Visum in the AddIn folder (see
    "Embedding add-ins automatically via a project directory" on page 2667).

    2668

    PTVGROUP

    26.4.1 Integrate script file


    4. Confirm with OK.
    The Run script procedure is inserted into the procedure sequence.

    26.4.1

    Integrate script file


    1. In the row of the created procedure, click the button in the row Variant/File.
    The Open script window opens.
    2. Select the desired script file.
    Note: You can only use script files with the extensions *.vbs, *.js, *.pys or *.py.
    3. Click the Open button.
    The script file is read from file and displayed in the Variant/file column (see "Setting the procedure sequence" on page 1847).

    26.4.2

    Integrate script code


    1. In the Operations section, select Edit.
    2. Select the option Directly enter script code.
    3. Enter the desired script code in the input field.
    Note: Only script code in the Python language is permissible.
    4. Confirm with OK.
    The script code is integrated into the procedure sequence.

    26.5

    Python as additional script language


    Scripting and COM allow adding new functions to Visum and automating recurrent tasks.
    Since release 9.4, Python is supported besides VBA/VBS. Python excels in providing easy-touse functions for matrix editing. It also helps the user to easily create charts and design user
    interfaces. Python provides for the setup of a user guidance tailored to a particular project.
    Python and all additional libraries are open source programs without any confinements concerning their use.
    Setup
    Precondition is the prior installation of the Python interpreter and the PythonWin supplement
    providing Python with a COM functionality.
    The Visum setup optionally installs a package of the Python basic system and useful additional libraries.
    Documentation and example data
    The directory ...User\Public\Documents\PTV Vision\PTV Visum 13\COM\Examples_ ComDocu\Python in your Visum installation contains sample files in Python.

    PTVGROUP

    2669

    26.5.1 Example 1 for applying script language


    The file ...User\Public \Documents\ PTV Vision\PTV Visum 13\COM\Introduction to the PTV
    Visum COM-API.pdf) contains the documentation for the VisumPy Python library.

    26.5.1

    Example 1 for applying script language


    As an example of the possibilities of the script language, the following dialog shows a Gantt
    bar chart of the blocks visualizing the contents of the block lists. Blue segments correspond to
    vehicle journeys, white ones to dwell times and red ones to empty trips.

    26.5.2

    Example 2 for applying script language


    The example shows the new transport mode distribution on the basis of known, prior distribution and old/new utility values (Pivot point).
    Via the Calculate> Procedure sequence menu an example has been configured to show
    how demand reacts to changes of PuT journey time.
    For example, if some journey times are changed and then the procedure is carried out, changes in demand will result which can be visualized by means of the desire line display.
    In the example, the following steps are taken:
    Via the Calculate PuT skim matrix procedure the new PuT journey times are calculated.
    Via the Combination of matrices and vectors procedure the PuT journey times are multiplied by -1 to determine the utility. The actual case utilities of PrT and PuT have already
    been calculated.
    Via the Run script procedure one of the variants of the Python script will be called up.
    They differ in the following respect:
    2A has been formulated in greater detail and includes clarifying comments (see "2A"
    on page 2671)

    2670

    PTVGROUP

    26.5.2 Example 2 for applying script language


    2B has been formulated more concisely and therefore saves storage capacity (see
    "2B" on page 2672)
    The scripts can be used for various kinds of models.
    Note: In the last row, you have to replace each matrix number correspondingly.
    The Combination of matrices and vectors procedure exclusively serves aesthetic purposes. The new PuT demand will be subtracted from the old one to be able to visualize
    the changes in the results by means of the desire line display.
    2A

    from numarray import *


    import numarray.ieeespecial as ieee
    def errormsg(msg):
    import Tkinter
    import tkMessageBox as tkmsg
    tk = Tkinter.Tk()
    tkmsg.showerror("Pivot point mode choice", msg)
    tk.destroy()
    def Pivot(Visum, T_old_no, T_new_no, U_old_no, U_new_no):
    """Calculate pivot point mode choice model.
    T_old_no = list of prior OD matrix numbers
    T_new_no = list of posterior OD matrix numbers (0 = don't save)
    U_old_no = list of prior utility (skim) matrix numbers
    U_new_no = list of posterior utility (skim) matrix numbers """
    # fetch all matrices into numarrays
    T_old = []
    U_old = []
    U_new = []
    ODs = Visum.Net.ODMatrices
    skims = Visum.Net.SkimMatrices
    for no in T_old_no:
    try:
    T_old.append(ODs.ItemByKey(no).GetValues())
    except:
    errormsg("%d is not a valid OD matrix number." % no)
    return
    for no in U_old_no:
    try:
    U_old.append(skims.ItemByKey(no).GetValues())
    except:
    errormsg("%d is not a valid skim matrix number or does not contain data."
    return
    for no in U_new_no:
    try:
    U_new.append(skims.ItemByKey(no).GetValues())
    except:
    errormsg("%d is not a valid skim matrix number or does not contain data."
    return
    # convert lists into arrays
    T_old = array(T_old)
    U_old = array(U_old)

    PTVGROUP

    2671

    26.5.2 Example 2 for applying script language


    U_new = array(U_new)
    # compute pivot point model
    T_old_sum = sum(T_old)
    # total trips
    p_old = T_old / T_old_sum
    # prior mode shares
    p_old[ieee.isnan(p_old)] = 0
    # set results of division by zero to 0
    p_new = p_old * exp(U_new-U_old) # posterior mode shares
    p_new_sum = sum(p_new)
    T_new = T_old_sum * p_new / p_new_sum
    T_new[ieee.isnan(T_new)] = 0
    # set results of division by zero to 0
    # save matrices
    for i, no in enumerate(T_new_no):
    if no > 0:
    try:
    ODs.ItemByKey(no).SetValues(T_new[i])
    except:
    errormsg("%d is not a valid OD matrix number or saving failed." % no)
    return
    """ In the example I am going to change only the PuT supply. The prior
    utility matrices are no. 1 for PrT and no. 4 for PuT. The posterior
    PuT utilities are in no.4 and I reuse no.1 for PrT, because I do
    not change PrT.
    Prior OD matrices are no.1 for PrT and no.3 for PuT. I am only
    interested in posterior PuT demand, so I set the posterior PrT OD
    matrix number to zero (= don't save) and store the posterior PuT
    demand in matrix no. 6. """
    Pivot(Visum, [1,3], [0,6], [1,4], [1,3])

    2B
    from numarray import *
    import numarray.ieeespecial as ieee
    def errormsg(msg):
    import Tkinter
    import tkMessageBox as tkmsg
    tk = Tkinter.Tk()
    tkmsg.showerror("Pivot point mode choice", msg)
    tk.destroy()
    def Pivot(Visum, T_old_no, T_new_no, U_old_no, U_new_no):
    """Calculate pivot point mode choice model.
    T_old_no = list of prior OD matrix numbers
    T_new_no = list of posterior OD matrix numbers (0 = don't save)
    U_old_no = list of prior utility (skim) matrix numbers
    U_new_no = list of posterior utility (skim) matrix numbers """
    # fetch all matrices into numarrays
    T = []
    U_old = []
    U_new = []
    ODs = Visum.Net.ODMatrices
    skims = Visum.Net.SkimMatrices
    for no in T_old_no:
    try:
    T_old.append(ODs.ItemByKey(no).GetValues())
    except:
    errormsg("%d is not a valid OD matrix number." % no)
    return

    2672

    PTVGROUP

    26.5.2 Example 2 for applying script language

    for no in U_old_no:
    try:
    U_old.append(skims.ItemByKey(no).GetValues())
    except:
    errormsg("%d is not a valid skim matrix number or does not contain data."
    return
    for no in U_new_no:
    try:
    U_new.append(skims.ItemByKey(no).GetValues())
    except:
    errormsg("%d is not a valid skim matrix number or does not
    contain data." % no)
    return
    # convert lists into arrays
    T = array(T)
    U_old = array(U_old)
    U_new = array(U_new)
    # compute pivot point model
    Ts = sum(T)
    # total trips
    p = T / Ts
    # prior mode shares
    p[ieee.isnan(p)] = 0
    # set results of division by zero to 0
    p *= exp(U_new-U_old)
    # posterior mode shares
    Ts /= sum(p)
    # total matrix / sum of posterior shares
    Ts[ieee.isnan(Ts)] = 0
    # set results of division by zero to 0
    # save matrices
    for i, no in enumerate(T_new_no):
    if no > 0:
    try:
    ODs.ItemByKey(no).SetValues(p[i] * Ts)
    except:
    errormsg("%d is not a valid OD matrix number or saving failed." % no)
    return
    """ In the example I am going to change only the PuT supply. The
    utility matrices are no. 1 for PrT and no. 4 for PuT.
    The posterior PuT utilities are in no.4 and I reuse no.1 for
    PrT, because I do not change PrT.
    Prior OD matrices are no.1 for PrT and no.3 for PuT. I am only
    interested in posterior PuT demand, so I set the posterior PrT
    OD matrix number to zero (= don't save) and store the posterior
    PuT demand in matrix no. 6. """
    Pivot(Visum, [1,3], [0,6], [1,4], [1,3])

    PTVGROUP

    2673

    27 Appendix

    27

    Appendix
    This is an overview of the file types and matrix file data formats used in Visum.
    Subjects
    File types
    Matrix formats

    27.1

    File types
    The table below lists all file types used in Visum according to the standard settings in the standard project directory file std.pfd (see "Opening and saving a project directories file" on page
    838). The entries are sorted by file extension.
    The file extensions of skim matrices suggested by default are described elsewhere (see Fundamentals: Chpt. 7.4 , page 456), (see Fundamentals: Chpt. 6.6 , page 311).

    2674

    Extension

    File type

    Description

    *. ...

    Skim matrix

    Matrix with skim value by OD pair (see "User-defined PrT


    skims" on page 1986 and "Calculating PuT skim matrices" on page 2076)

    *.adrp

    Parameters for
    additive demand
    reading

    Settings for additive reading of demand data from file


    (see "Reading OD demand data additively" on page
    1837)

    *.ane

    Active network
    objects

    State (active/passive) of network objects due to spatial


    selection (see "Setting network objects active/passive via
    the spatial selection" on page 1033)

    *.anm

    ANM network

    Abstract Network Model for data export to Vissim (see


    "ANM interface" on page 2511)

    *.anmp

    ANM export parameters

    Settings for ANM export to Vissim (see "ANM interface"


    on page 2511)

    *.anmRoutes

    ANM routes

    Dynamic routes and demand matrices for Dynamic Assignment in Vissim (see "Saving an abstract network
    model" on page 2512)

    *.anrp

    Parameters for
    additive network
    reading

    Settings for additive reading of network data from file


    (see "Reading network data additionally" on page 851)

    *.att

    Attributes

    Attributes and attribute data of a network object type (see


    "Importing and exporting list contents" on page 2325)
    Intervals, e.g. for the classification (see "Setting graphic
    parameters for the Matrix editor window" on page 1749)
    or calibration (see "Estimate gravitation parameters
    (KALIBRI)" on page 1703)

    *.bmp, *.gif,

    Image

    Window section in various graphics data formats (see

    PTVGROUP

    27.1 File types


    Extension

    File type

    *.jpg ...

    Description
    "Exporting screenshots" on page 2663)

    *.cod

    Code file

    Instructions for matrix editing functions, such as aggregation, classification

    *.con

    PuT connections

    Connections in the Visum connection data format (see


    Fundamentals: Chpt. 7.10.7.4 , page 517), (see "Timetable-based assignment:Connection export tab" on page
    2047 and "Connections:importing" on page 2560)

    *.dll

    User-defined
    During startup Visum searches the corresponding direcVolume-delay func- tory for all DLL files of this kind and loads the contents so
    tion (VDF) DLL
    that the function types are available in the VD functions
    files
    window (see "Applying user-defined volume-delay functions" on page 1899).

    *.dmd

    Demand description

    Demand description data, e.g. time series, times, matrices, activities, person groups (see "Reading and saving
    demand data" on page 1836)

    *.dxf

    Graphics

    Window section in *.dxf format (see "DXF export" on page


    2654)

    *.emf, *.wmf, Background


    *.bmp ...

    Additional graphical data underlaying the network (see


    "Using backgrounds in the network display" on page
    2237)

    *.emme

    EMME project

    Settings for EMME/2 data import (see "EMME/2 import"


    on page 2587)

    *.fil

    Filters

    Filter settings for all network object types (see "Reading


    and saving filters" on page 1024)

    *.fma

    Matrix

    Demand matrix or skim matrix (see "Managing matrices"


    on page 1607)

    *.gpa

    Graphic parameters of the network

    Settings for graphical network display (see "Specifying


    basic settings for the network window" on page 2337)

    *.gpm

    Graphic parameters of the


    matrix editor

    Settings for the display in the Matrix editor window (see


    "Setting graphic parameters for the Matrix editor window"
    on page 1749)

    *.gpt

    Timetable editor
    graphic parameters

    Settings for data display in the tabular timetable and in


    the graphical timetable (see "Setting the graphic parameters of the tabular timetable" on page 1573 and "Setting the graphic parameters of the graphical timetable" on
    page 1577)

    *.gpta

    Transfer headway Settings for the transfer headway display (see "Setting
    display graphics
    the graphic parameters for the Transfers display of regu-

    PTVGROUP

    2675

    27.1 File types


    Extension

    2676

    File type

    Description

    parameters

    lar services" on page 2396)

    *.gptsd

    Graphic parameters for the


    signal time-space
    diagram

    Settings for the display in the signal time-space diagram


    (see "Saving the graphic parameters of the signal timespace diagram" on page 2490)

    *.haf, *.puti,
    *.putp

    PuT interfaces pro- Settings for HAFAS data import (see "HAFAS import" on
    ject
    page 2565) and import and export of railML data (see
    "RailML interface" on page 2573)

    *.jpg, *.wmf,
    *.bmp...

    Exported turn volu- Turn volume export in different graphics file formats (see
    mes
    "Exporting turn volumes" on page 2446)

    *.jpg, *.wmf,
    *.bmp...

    Screenshot

    Window section in various graphics data formats (see


    "Exporting screenshots" on page 2663)

    *.lgd

    Legend parameters

    Settings for legend display (see "Opening and saving


    legend parameters" on page 2260)

    *.lla

    List layout

    Layout of a list (see "Adjusting the list layout" on page


    2308)

    *.mdb, *.accdb

    Access database

    Access file storing Visum network data (see "Database


    interface" on page 2642)

    *.mlg

    MUULI Log file

    Protocol of matrix processing steps in the matrix editor


    (see "Editing matrix values using a log file during the procedure sequence run" on page 1775)

    *.mly

    Matrix editor layout Settings for the display in the Matrix editor window (see
    "Saving and loading the layout of a Matrix editor or Histogram window" on page 1747)

    *.mtx, *.mx

    Matrix

    Demand matrix or skim matrix (see "Managing matrices"


    on page 1607)

    *.net

    Network

    Network data (see "Opening and saving a network file


    and adding comments" on page 844)

    *.nmp

    Network merge
    parameters

    Settings for reading a merged network (see "Merging networks" on page 902)

    *.nse

    External signal
    control

    Editor settings for U.S.-specific signal control modeling


    (NEMA)

    *.par

    Procedure paraParameters of the currently selected procedures (see


    meters (binary for- "Saving procedure parameters to a file and loading them
    mat)
    from a file" on page 1867)

    *.pfd

    Project directories Standard paths for all Visum file types (see "Opening and
    saving a project directories file" on page 838)

    *.prj

    Projection

    Coordinate systems (see "Selecting a coordinate system"


    on page 2207)

    PTVGROUP

    27.1 File types


    Extension

    File type

    Description

    *.qla

    Quickview layout

    Layout of the Quickview window (see "Selecting attributes for the Quick view display" on page 811)

    *.rim

    PrT routes

    Externally calculated PrT routes (see "Importing routes"


    on page 2561)

    *.shp

    ESRI shape file

    Shape files (see "The Shapefiles interface" on page


    2221)

    *.sig

    External signal
    control

    Editor settings for signal control modeling (VISSIG)

    *.smg

    Smart Map graphic Layout settings for the Smart Map window display (see
    parameters
    "The Smart map window" on page 813)

    *.svg

    SVG file

    Window section in *.svg format (see "SVG export" on


    page 2656)

    *.tla

    TModel project

    Parameter settings for TModel data import (see "TModel


    import" on page 2592)

    *.tly

    Timetable editor
    layout

    Layout settings for tabular timetable and graphical timetable display (see "Specifying the layout of the Timetable
    editor" on page 1568)

    *.tra

    Model transfer file

    Difference between two models, i.e. network and


    demand data (see "Creating and applying model transfer
    files" on page 908)

    *.trc

    Activity protocol

    Protocol of user actions (see "Using protocol files" on


    page 876)

    *.txt

    Text file

    Legend or background texts (see "Saving texts" on page


    2237 and "Reading texts" on page 2237)

    *.upa

    Environmental cal- Parameter settings for noise and air pollution calculation paraculations (see "Saving a file" on page 831 and "Setting
    meters
    environmental impact parameters" on page 2183)

    *.vai

    Visum AddIn

    During startup Visum searches in the corresponding


    directory for all files of this kind and loads the contents in
    the Scripts menu and in the procedure selection (see
    "Embedding add-ins automatically via a project directory"
    on page 2667)

    *.vbs, *.py, Script


    *.js, *.pys
    ...

    Scripts for automating repetitive tasks (see "Working with


    scripts" on page 2664)

    *.ver

    Version

    Network, demand data, skim matrices, attributes and


    various parameter settings (see "Opening and saving a
    version file" on page 840)

    *.vhd

    VISEM *.VHD file

    Model data from the demand calculation program

    PTVGROUP

    2677

    27.2 Matrix formats


    Extension

    File type

    Description
    VISEM8.x (see "Reading tour-based demand models
    from VISEM data files (*.vhd)" on page 1619)

    27.2

    *.vpdb

    Visum project data- Project file where the scenario management data is
    base
    managed (see "Scenario management" on page 921)

    *.wmt

    EVA weighting
    matrix

    EVA weighting matrix file (see "Managing weighting matrices" on page 1677)

    *.xml

    XML files for different purposes

    File with settings, for example


    Procedure parameters (see "Saving procedure parameters to a file and loading them from a file" on page
    1867)
    Settings for calculations with matrices (see "Saving
    settings for special matrix operations" on page 1815)
    Settings for the layout of the schematic line diagram
    (see "Saving the layout of a schematic line diagram"
    on page 2478)
    Settings for calculations with matrices (see "Saving
    settings for special matrix operations" on page 1815)
    Settings for the layout of the schematic line diagram
    (see "Saving the layout of a schematic line diagram"
    on page 2478)
    Settings for the subnetwork generator (see "Using
    the subnetwork generator" on page 1601)

    *.xml

    Script menu file

    Commands in the Script menu (see "Editing the script


    menu" on page 2664)

    Matrix formats
    This part illustrates the various data formats to be used for matrix data processing.
    Visum-specific matrix file formats
    Data structures of matrices in Visum-specific text formats
    Format CSV for skim matrices

    27.2.1

    Visum-specific matrix file formats


    The following table includes all Visum-specific matrix file formats that you can read and/or
    save in Visum.

    2678

    PTVGROUP

    27.2.2 Data structures of matrices in Visum-specific text formats


    Format
    code

    Description

    Notes

    $V

    Standard Visum format, symmetrical


    (Number of origin objects x number of destination objects)

    Text format
    For PuT skim matrices, the partial
    V format is provided additionally.

    $O

    An OD pair per row:


    Origin object, destination object, matrix
    value

    Text format
    Only values not equal to zero are
    displayed.

    $E

    An origin object per row:


    Text format
    Minus sign, origin object no., destination
    object numbers (sorted in ascending order)
    and matrix values

    $S

    An origin object per row:


    Text format
    Origin object no., destination object numOnly provided for Save opebers (sorted in ascending order) and matrix rations in Visum.
    values

    $T

    Partial matrix or asymmetric matrix


    (Number of origin objects x number of destination objects)

    Text format

    Depending on the settings made for saving matrices, it is possible to save the following additional parameters (see "Saving matrices" on page 1733):
    Parameters

    Description

    Matrix values are randomly rounded (RandomRound).


    Data file format code without R means, that matrix values are either not rounded or rounded arithmetically (if the respective number of decimal places
    has been set).

    Number of decimal places for the matrix values (if > 0)


    Data file format code without D means, that the matrix values are integers.

    Number of the transport mode (only for the partial V format)

    At the end of the matrix file, in section $NAMES, the numbers and the name of the source and
    target objects are listed.

    27.2.2

    Data structures of matrices in Visum-specific text formats


    Generally, matrices in text format have the following data structure:
    First row: Format code, e.g. $VR;D2
    $V, $O, $E, $S, $T for the matrix file format
    R for random rounding and or M
    D and the number of decimal places (if > 0)

    PTVGROUP

    2679

    27.2.2.1 Format $V

    Note: For the additional parameters R, D and M please refer to the examples below
    which illustrate the combination with the format $V (see "Format $V" on page 2680).
    Header corresponds to the selected options, meaning with or without transport mode identifier (only in the partial V format)
    From - To: assignment time interval
    Data block
    The data block is described below, with example matrices.
    $NAMES
    List of numbers and names of the rows and columns
    Comment lines
    Visum adds specific comments to the file, depending on the format (e.g. the total amount
    per origin or destination object).
    They are permitted in the header as well as in the data block.
    They must begin with *
    They are skipped by the program.
    27.2.2.1

    Format $V
    Square <Number of origin objects x number of destination objects> matrix with the following
    data:
    Number of objects (rows/columns)
    Network object numbers
    Origin traffic per origin object row
    Destination traffic per destination object column
    Notes: The standard format is $V (with time interval and factor).
    The data formats are compatible for Visum, the matrix editor and VISEM.
    $V (no random rounding, no decimal places)
    $V
    * From To
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.10
    * Number of network objects
    3
    * Network object numbers
    100
    200
    *
    * Object 100 Total = 8
    2
    3
    4
    * Object 200 Total = 15
    4
    5
    6
    * Object 300 Total = 24

    2680

    300

    PTVGROUP

    27.2.2.1 Format $V
    7
    8
    9
    * Network object names
    $NAMES
    100 "ObjectA"
    200 "ObjectB"
    300 "ObjectC"

    $VR (no random rounding, no decimal places)


    $VR
    * From To
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.11
    * Number of network objects
    3
    * Network object numbers
    100
    200
    *
    * Object 100 Total = 8
    1
    3
    4
    * Object 200 Total = 15
    4
    5
    6
    * Object 300 Total = 24
    7
    8
    9
    * Network object names
    $NAMES
    100 "ObjectA"
    200 "ObjectB"
    300 "ObjectC"

    300

    $V;D3 (no random rounding, no decimal places)


    $V;D3
    * From To
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.11
    * Number of network objects
    3
    * Network object numbers
    100
    200
    *
    * Object 100 Total = 7.500
    1.500 2.500 3.500
    * Object 200 Total = 15.000
    4.000 5.000 6.000
    * Object 300 Total = 24.000

    PTVGROUP

    300

    2681

    27.2.2.2 Format $O
    7.000 8.000 9.000
    * Network object names
    $NAMES
    100 "ObjectA"
    200 "ObjectB"
    300 "ObjectC"

    Partial V format
    PuT skim matrices can also be saved in the partial V format ($VM), if certain OD pairs have
    been selected by specifying the range of origin zones for skim value calculation.
    $VM
    * Transport mode number
    3
    * From To
    0.00 24.00
    * Factor
    1.00
    * created with:
    Visum Version 12.000
    * created on:
    31.05.11
    * Matrix values:
    Journey time
    * Network/VersFile:
    D:\PTV_Vision\VISUM\EXAMPLE.VER
    * Assignment procedure:
    Timetable-based
    * Analyzed OD pairs:
    All
    * Aggregation:
    Avg value
    * Weighted:
    Yes
    * Demand segment:
    P;PuT
    * Number of network objects
    3
    * Network object numbers
    100
    200
    300
    *
    * Object 100 Total = 336
    0
    101
    236
    * Object 200 Total = 322
    105
    0
    217
    * Object 300 Total = 452
    236
    217
    0
    * Network object names
    $NAMES
    100 "A Village"
    200 "X City"
    300 "Y City"

    27.2.2.2

    Format $O
    The individual OD pairs (origin object, destination object and matrix value) are listed row by
    row.
    Notes: The matrix editor does not distinguish between character O and figure 0.
    The OD pairs do not have to be sorted in ascending order.
    Relations with value = 0 are not output, but may occur in an input file in $O format.

    2682

    PTVGROUP

    27.2.2.3 Format $E
    $O;D3
    * From To
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.11
    100
    100
    100
    200
    100
    300
    200
    100
    200
    200
    200
    300
    300
    100
    300
    200
    300
    300
    * Network object names
    $NAMES
    100 "ObjectA"
    200 "ObjectB"
    300 "ObjectC"

    27.2.2.3

    1.500
    2.500
    3.500
    4.000
    5.000
    6.000
    7.000
    8.000
    9.000

    Format $E
    OD pairs row by row for each origin object with destination object numbers in ascending order:
    -Origin object number, minimum destination object number, matrix value, ..., maximum destination object number, matrix value
    $E;D3
    * From To
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.11
    -100 100 1.500 200 2.500 300 3.500
    -200 100 4.000 200 5.000 300 6.000
    -300 100 7.000 200 8.000 300 9.000
    * Network object names
    $NAMES
    100 "ObjectA"
    200 "ObjectB"
    300 "ObjectC"

    27.2.2.4

    Format $S
    OD pairs row by row for each origin object with destination object numbers in ascending order:
    -Origin object number, minimum destination object number, matrix value, ..., maximum destination object number, matrix value
    $S;D3
    * From

    PTVGROUP

    To

    2683

    27.2.2.5 Format $T
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.11
    100 100 1.500 200 2.500 300 3.500
    200 100 4.000 200 5.000 300 6.000
    300 100 7.000 200 8.000 300 9.000
    * Network object names
    $NAMES
    100 "ObjectA"
    200 "ObjectB"
    300 "ObjectC"

    27.2.2.5

    Format $T
    Square <Number of origin objects x number of destination objects> matrix or partial matrix with
    the following data:
    Number of objects (rows/columns)
    Row numbers
    Column numbers
    Origin traffic per origin object row
    Destination traffic per destination object column
    $T;D3
    * From To
    0.00 24.00
    * Factor
    1.00
    *
    * VISUM Developer
    * 31.05.11
    * Row numbers
    1
    2
    *
    * Column numbers
    1
    2
    *
    * Object 1 Total = 9.500
    2.000 2.000 2.000 1.500
    * Object 2 Total = 54.500
    7.500 36.000 2.000 7.000
    * Object 3 Total = 18.000
    7.000 2.000 2.000 2.000

    -1

    -1

    2.000
    2.000
    5.000

    * Network object names


    $NAMES
    1 "ObjectA"
    2 "ObjectB"
    3 "ObjectC"
    4 "ObjectD"
    5 "ObjectE"

    2684

    PTVGROUP

    27.2.3 Format CSV for skim matrices

    27.2.3

    Format CSV for skim matrices


    For further data processing in a spreadsheet program you can save skim matrices in *.csv format.
    This format has the following features:
    Comma, semicolon, tabulator or blank may serve as separator
    Note: The selected separator needs to match the spreadsheet program.
    For skim matrices, the means of transport number for VISEM is stored with the file.
    The file does not contain a specific format code
    The calculated skims are listed in comment rows.
    Row $Relations consists of the column headers: OZonNo, DZonNo and the skim codes of
    all currently computed skims.
    The matrix file extension is *.csv.
    PuT skim matrices
    $VISION
    $VERSION: VersNr;FileType;Language
    1.0;Matrix;E
    *
    *File info
    $INFO:Text
    Means of transport no.
    3
    Time interval
    0.00
    24.00
    Created with:
    Visum Version 12.500
    Created on:
    07/04/12
    Network/Version file:
    D:\PTV_Vision\Manual\Matrixeditor\EXAMPLE.VER
    Assignment procedure:
    Timetable-based
    Aggregation:
    Mean value
    Weighted:
    Yes
    Demand segment:
    P;PuT
    $
    * Calculated skims:
    * MFW
    In-vehicle distance
    * JRT
    Journey time
    * MUH
    Number of transfers
    $Relations: OrigZoneNo DestZoneNo MFW JRT MUH
    100 100 0 0 0.0
    100 200 24713 101 0.4
    100 300 20000 236 0.0
    200 100 27500 105 0.0
    200 200 0 0 0.0
    200 300 7500 217 0.0
    300 100 20000 236 0.0
    300 200 7500 217 0.0
    300 300 0 0 0.0

    PTVGROUP

    2685

    27.2.3 Format CSV for skim matrices


    PrT skim matrices
    $VISION
    $VERSION: VersNr;FileType;Language
    1.0;Matrix;E
    *
    *File info
    $INFO:Text
    Transport mode
    4
    Time interval
    0.00 24.00
    Created with
    :
    Visum Version 11.50
    Created on
    :
    31.05.10
    Network/VersFile :
    D:\PTV_Vision\Manual\Matrixeditor\EXAMPLE.VER
    Demand segment
    :
    C C
    Path choice
    :
    Assignment
    All OD pairs
    Weighting
    :
    Mean over volumes
    Output values summed up from:
    Links
    Origin connectors
    Dest. connectors
    Turns
    $
    * Calculated skims:
    * TT0
    t0
    * TTC
    tCur
    * VP0
    v0
    * VPC
    vCur
    * IMP
    Impedance
    * DIS
    Distance
    $Relations:OZonNo DZonNo TT0 TTC VP0 VPC IMP DIS
    100 100 0 0 0 0 0 0
    100 200 23 23 89 88 1391 34000
    100 300 28 29 71 70 1718 33574
    200 100 23 23 89 89 1368 34000
    200 200 0 0 0 0 0 0
    200 300 22 22 63 63 1337 23574
    300 100 28 28 71 71 1697 33574
    300 200 22 22 63 63 1339 23574
    300 300 0 0 0 0 0 0

    2686

    PTVGROUP

    Index

    Index
    A
    Abstract network model 2511
    exporting subnetwork 2517
    notes on imported data 2518
    Activities 19, 132, 1606, 1624
    attributes (EVA) 142
    creating 1624
    editing attribute values 1626
    properties and options 1625
    Activity chains 134, 175-176, 1624
    creating 1631
    editing attribute values 1632
    properties and options 1632
    Activity pairs 19, 133, 1624
    attributes (EVA) 142
    creating 1627
    editing attribute values 1629
    properties and options 1628
    Activity protocol 876, 879, 881
    Add-ins
    adjusting parameters 2668
    embedding 2667
    Add-ons 5
    enabling or disabling 886
    Adding complex terms 203
    Aerial images
    see Backgrounds 2237
    Air pollution emissions 682
    calculating 2188
    displaying 2190-2191
    saving 2191
    setting parameters 2183
    Akcelik (VD function) 238
    Allocating crosswalks 1491
    Analysis
    analysis horizon 98
    analysis period 98
    analysis time intervals 99, 102
    analysis time slots 98
    PTVGROUP

    Analysis period
    defining 1860
    Analysis time intervals
    defining 1861
    saving results 1863
    ANM
    see Abstract network model 2511
    ANM export
    see Vissim export 2511
    Annual calendar 95
    Applying hierarchical filters 1016
    Assessment types 166, 1671
    Assignment analysis 1879
    PrT 446
    PuT 528
    Assignment procedure
    see Assignments 226
    Assignment quality 329
    Assignment time interval 98
    Assignment with ICA
    evaluation 376
    Assignments
    deleting results 1879
    demand segments 49
    distribution models 329
    PrT procedures
    see PrT assignment
    procedures 226, 1931
    PuT procedures
    see PuT assignment
    procedures 449, 1995
    results per analysis time
    intervals 1863
    Attraction 138, 146, 150, 164, 1641,
    1669
    Attribute files 2646
    reading 2646
    saving from lists 2325
    Attributes 958, 962
    accessing attributes 963
    activities 1625
    activity chains 1632
    activity pairs 1628
    2687

    Index

    aggregate functions 960


    alias definition 967
    block versions 2093
    calculating the weighted mean 1701
    connectors 1161-1162
    count locations 1404
    decimal places 960
    demand models 1618
    demand segments 1062
    demand strata 1635
    demand time series 1615
    detectors 1411-1412
    direct 103
    displaying short or long names 959
    DUE 1133
    editing 983
    editing display setting 970
    exporting 2329
    indirect 104
    line blocks 2133
    line routes 1311
    lines 1292
    links 1107
    main lines 1365
    main zones 1196
    managing 958
    managing time-varying attributes 979
    matrices 1733
    modes 1060
    nodes 1066
    output attributes 984
    person groups 1620
    POIs 1387
    presetting the analysis time slot 967
    PrT paths 1226
    reading 2646
    relation types and aggregate functions
    of indirect attributes 966
    saving 2325
    screenlines 1429
    selecting attributes 963
    selecting several 968

    2688

    standard sorting 959


    standard time series 1609
    stop areas 1256
    stop points 1267
    stops 1238
    structural properties 1623
    system routes 1371
    territories 1208
    time-varying 114
    time-varying attributes 979
    creating 980
    editing 982
    toll systems 1419
    transport systems (TSys) 1057
    user-defined 110
    user-defined attributes 973
    creating 973, 977
    creating while reading 977
    deleting 979
    editing 979
    formula attributes 973
    managing 973
    Timetable editor 1538
    user-defined attributes editing 978
    vacation days 1522
    valid days 1513
    vehicle combinations 1287
    vehicle units 1284
    zones 1137
    Attributes.xls 962
    Average Excess Cost AEC (PrT assignment quality) 329

    B
    Background formats 712
    Background map
    dynamically embed 2237
    statically embed 2239
    Backgrounds 709, 2237
    automatic positioning 713
    by Bing Maps 710

    PTVGROUP

    Index

    creating 2243
    deleting 2250
    dynamically embed
    from the Internet 709
    editing 2247
    editing the drawing order 2244
    from Shapefile 2249
    from the Internet 2237
    hiding/showing 2244
    manual editing 2245
    measuring links 2246
    saving 2250
    statically embed
    from the Internet 710
    tie points 2249
    Bar display 21, 753
    Bars
    displaying 2367, 2435
    Base version
    see Scenario management 925
    Best-route assignment 337
    Bing Maps 710
    see Backgrounds 2237
    Block check
    running 2099
    Block display
    editing line blocks 2129
    Block item types 573
    managing 2102
    Block items 573
    Block version 568
    Block versions
    attributes and options 2093
    block item types 2102
    coverage verification 2098
    creating 2091
    editing 2097, 2129
    Block view 2119
    graphic parameters 2124
    Blocking back model 314-315, 1925
    Blocks 570
    Bounding 501
    Box-Cox model 331
    PTVGROUP

    BPR (VD function) 235


    Branch and Bound 499
    Buffer 701

    C
    C-Logit approach 391
    Calculate skim matrix (procedure) 311
    Calculated results
    temporal distinction 102
    Calculating
    PuT skim matrices 2073
    Calculating PrT skim matrices 1984
    Calculation results
    temporal distinction 102
    Calendar 68, 94
    selecting 1511
    Calendar period 98
    Capacities
    adjusting to demand values 103
    Capacity restraint functions
    see VD functions 1892
    Cascetta 391
    Changing attribute values
    links 1113
    Changing the language of the graphical
    user interface 875
    Charts 21
    column charts 758, 775
    pie charts 759
    Choice models
    with independence 508
    Cold start excess emissions
    calculation according to HBEFA 688
    Column charts 21, 775, 2492
    displaying 2492
    example 2495
    exporting 2496
    Command line parameters 887
    Commonality factor 391
    Comparison of run and dwell
    times 1328
    Comparison pattern 948-949
    2689

    Index

    Configuration file 887


    example 890
    Conical (VD function) 235
    Conical marginal (VD function) 236
    Connecting activity pairs and standard
    time series 1630
    Connecting edges to desired stops 2475
    Connection choice
    timetable-based assignment 505
    Connection search 499
    Connections
    exporting 2047
    importing 2560
    independence (timetable-based assignment) 506
    saving 1890
    skims 457
    Connectors 58, 1159
    allocating VD functions 1894
    copying attribute values 1166
    creating 1160
    deleting 1168
    destination connector 58
    displaying bars 2367
    distributing PrT demand 1888
    distributing traffic demand
    PrT 59, 312
    distributing travel demand
    PuT 59, 469
    distribution of demand 59, 312
    editing attribute values 1164
    generating 1166
    impedances 232
    marking 1163-1164
    Multi Point Assignment (MPA) 59, 312
    origin connector 58
    properties and options 1161-1162
    selecting transport systems 1163
    setting standard values 1159
    Connectors selecting 1163-1164
    Constant from time profile attribute (headway calculation) 475
    Constraints 150, 175
    2690

    Control types at node 245


    Convergence
    number of non-converging objects 1892
    Convergence criteria 1982
    Coordinate systems 705
    switching 2207
    Coordination groups 495
    for headway-based assignment 2004
    Copying attribute values 1166
    Cordon links 61
    editing 1187
    Cordon nodes
    toll system 1422
    Cost (PuT) 648
    Cost model
    of PuT 2153
    Costs (PuT)
    infrastructure 2153
    vehicle-bound 2153
    Count data (PuT) 2051
    Count locations 84, 1403
    creating 1403
    deleting 1409
    editing attribute values 1406
    marking 1405-1406
    properties and options 1404
    selecting 1405-1406
    setting polygon allocation 1408
    shifting 1407
    Coupling time profiles 77
    Coverage verification
    of block versions 2098
    Creating
    an operator 1281
    turn standards 1090
    Crosswalks 91
    creating 1478
    editing attributes 1483
    Cycle and split optimization 1921
    Cycle time optimization 298

    PTVGROUP

    Index

    D
    Data
    exporting 2511
    importing 2511
    Data model 962
    Database export
    Access 2642
    SQL 2643
    Database import
    Access 2644
    SQL 2645
    Decimal places 960
    Default setting 864
    Defining constraints 1662
    Delete assignment results 1879
    Deleting
    activities 1626
    demand strata 1637
    person groups 1621
    Deleting activity chains 1632
    Deleting activity pairs 1630
    Deleting boundaries
    main zones 1200
    polygonal network objects 1052
    zones 1144
    deltaT
    early 504
    late 504
    DeltaT 504
    Demand
    calculating
    EVA model for passenger
    demand 1661
    Standard 4-step model 1638
    Tour-based model 1684
    distributing to PrT connectors 1888
    see transport demand 129
    Demand data files
    reading 1836
    reading additively 1837
    saving 1842

    PTVGROUP

    Demand description 1606


    reading 1836
    reading additively 1837
    saving 1842
    Demand matrices 17, 130, 1606-1607,
    1716
    calibrating (PrT) 1834
    combining with demand
    segment 1607
    updating 210
    Demand model 15, 17, 129
    Demand model structure 131, 1606
    Demand models 15, 17, 1617
    activity chain based
    see Demand models, Tour-based
    model 174
    creating 1617
    deleting 1618
    editing attribute values 1618
    EVA model for passenger
    demand 18, 142
    properties and options 1618
    reading in predefined 1619
    Standard 4-step model 18, 136
    time series 19
    Tour-based model 19, 174
    Demand objects 19, 129
    Demand segments 46, 48, 130
    Demand segments (DSeg) 1055, 1061
    adding up volumes 2003
    creating 1061
    deleting 1063
    editing attribute values 1062
    properties and options 1062
    Demand strata 19, 134, 1606, 1633
    attraction 138, 146, 150, 164
    attributes (EVA) 143
    creating 1633
    automatically 1634-1635
    editing attribute values 1637
    editing the demand
    EVA model for passenger
    demand 1669
    2691

    Index

    Standard 4-step model 1641


    Tour-based model 1687
    home trips 164, 178
    production 138, 146, 150, 164
    properties and options 1635
    Demand time series 1614
    combining with demand segments 1616
    creating 1614
    deleting 1616
    properties and options 1615
    Desire lines 760, 2429
    hiding individual 2434
    Detectors 84, 1410
    at nodes
    creating 1478
    editing attributes 1483
    creating 1410
    detectors 1416
    editing attribute values 1414-1415
    marking 1413
    properties and options 1411-1412
    selecting 1413
    shifting 1415
    Difference network
    see Networks, merging 902
    Direct assignment 540
    Direct assignment of survey data 2071
    Display
    2D 768
    Displaying
    isochrones in lists 2290
    Displaying connections and transfer flows
    at stops 2392
    Displaying license information 886
    Displaying program information 886
    Displaying transfer flows 765
    Displaying turn volumes 759
    Distribution models 329
    Box-Cox model 331
    Kirchhoff model 330
    Logit model 331
    Lohse model 332

    2692

    Distribution models_Lohse model


    with variable beta 333
    DMRB guideline TD 16/93 (roundabouts)
    293
    Documents 2
    Dominance 500
    Dongles 4
    DUE 410
    see Dynamic User Equilibrium 1969
    DXF
    export 1568
    DXF export 2654
    DXFexport
    transfers display of regular
    services 2400
    Dynamic equilibrium assignment
    example 431
    Dynamic stochastic assignment 439,
    1976
    evaluation 441
    input and output attributes 441
    procedure 388, 443
    Dynamic User Equilibrium (DUE) 410,
    1969
    evaluation 410
    input and output attributes 433

    E
    E-ticketing 534
    Edge 120
    Editing
    turn standards 1092
    Editing attribute values 983, 2321
    activities 1626
    activity chains 1632
    activity pairs 1629
    allocating values 988, 990
    allocating with source attribute 993
    as procedure 990
    connectors 1164
    count locations 1406

    PTVGROUP

    Index

    demand models 1618


    demand strata 1637
    detectors 1414-1415
    exchanging values 993-994
    line routes 1336-1337
    lines 1297
    main lines 1366
    main nodes 1173-1174
    main zones 1198-1199
    multiplying by factor 987
    nodes 1066
    operators 1282
    path sets 1222
    person groups 1621
    POIs 1390-1391
    recalculating 989
    screenlines 1431
    set attributes 985
    standard time series 1609
    stop areas 1258
    stop points 1273-1274
    stops 1243
    structural properties 1623
    system routes 1374
    territories 1209-1210
    Timetable editor 1541, 1554
    toll systems 1420
    user-defined attributes 978
    valid days 1519
    vehicle combinations 1289
    vehicle units 1285
    zones 1142
    Editing constraint values 1665
    Editing project directories 838
    Editing PuT directions 1290
    Editing shapes
    polygonal network objects 1042
    zones 1144
    Editing the directory file 838
    Editing the scale 2209
    Editing the script menu 2664
    Emission calculation
    displaying results 2203
    PTVGROUP

    graphical display of results 2204


    saving results 2205
    settings 2191
    Emissions
    calculating according to
    HBEFA 2198
    EMME/2 import 2587
    settings
    resetting 2592
    saving 2591
    EMME/2 import settings
    reading 2591
    Empty trips
    ee Interlining trip 2148
    Environmental impact model 679, 2183
    air pollution emissions 682
    calculating 2188
    displaying 2190-2191
    saving 2191
    editing link attributes 2185
    noise volume 679
    noise volumes
    calculating 2185
    saving 2188
    Pollution-Emis procedure 682
    resetting calculation 2185
    setting parameters 2183
    Environmental impact model noise volumes
    displaying 2187
    Equilibrium assignment 342, 1934
    evaluation 342
    examples 343, 350
    input and output attributes 345
    procedure 347
    Equilibrium_Lohse 366, 1942
    evaluation 374
    examples 367
    input and output attributes 371
    procedure 373
    EVA
    see EVA model for passenger
    demand 129
    2693

    Index

    EVA model for passenger demand 18,


    129, 142
    activities 142
    activity pairs 142
    assessment types 166
    balance factors 171, 174
    balancing 155
    constraints 150
    demand strata 143
    elasticity functions 169
    evaluation 166
    evaluation functions 165, 167
    weighting probabilities 166
    Furness method
    trilinear 171
    home trips 164
    mobility rates 149
    mode choice 165
    multi procedure
    trilinear 172
    structural properties 143
    study area factors 149
    trip distribution 165
    trip generation 146
    zones 145
    Evaluating the goodness of the PrT assignment 1982
    Exporting 2511
    DXF 2654
    graphics 2650
    PostScript 2652
    converting into PDF 2654
    screen 2663
    screenshot 2663
    Shapefiles 2230
    SVG 2656, 2660
    VDV452 2625
    Vissim 2511
    Exporting database
    Access 2642
    SQL 2643
    Extended projection 2165

    2694

    F
    Face items 120
    Faces 120
    Fares 468
    Fields of application
    planning tasks PrT 1
    planning tasks PuT 1
    Fij matrices
    see Demand matrices 130, 1607
    File extensions 2674
    Files
    opening 831, 833
    saving 831
    settings 835
    Filter for OD pairs 1026
    Filters
    applying hierarchical filters 1016
    bracketing in filter terms 1015
    defining filter conditions 1009
    initializing filter conditions 1023
    reading 1025-1026
    saving 1024
    setting active/passive 1008
    using 1022-1023
    using OD pair filters 1026
    Finding
    in lists 2317
    Finding data record number in list 2318
    Finding errors in the network 1504
    Fixing errors in the network 1510
    Fleet compositions
    defining 2192
    Flow bundles 21, 716
    alternative routes 730
    combining flow bundle criteria 725
    creating 2265, 2273
    defining flow bundles 718
    displaying 2265
    displaying attributes in lists 2277
    displaying in lists 2277
    displaying paths 730

    PTVGROUP

    Index

    link flow bundles 720


    main node flow bundles 719
    node flow bundles 718
    putting conditions into brackets 2274
    saving volumes 2278
    selecting network objects 718
    selecting types of traffic 721
    setting graphic parameters 2275
    setting the bar display 2276
    stop point, stop area, and stop flow
    bundles 720
    traffic type-based flow bundle 2271
    zone and main zone flow
    bundles 720
    Forced chainings 2144
    Formula matrix 1727, 1730

    G
    Gap (PrT assignment quality) 329
    Generating world file 2251
    Geographic information systems (GIS)
    691
    Georeferencing 705
    GIS objects 86, 691, 2211
    creating 2211
    deleting 2217
    displaying in lists 2217
    editing attribute values 2214
    finding 2212
    marking 2213
    selecting 2213
    setting graphic parameters 2215,
    2352
    Go to procedure 196, 198
    Go to procedure (procedure) 18, 198
    Go to the procedure 1697
    Goodness of PrT assignment
    convergence criteria 1982
    GoTo
    see Go to the procedure 1697
    GPS tracking 714, 2261
    setting graphic parameters 2262
    PTVGROUP

    Gradients
    displaying 1129
    Graphic objects 707, 2232
    backgrounds 2237
    legend 2255
    polygons 2251
    texts 2232
    Graphic parameters 2337
    2D display of attributes 2352
    basic settings 2337
    block view 2124
    classified display (attribute values)
    2411
    displaying bars 2367
    displaying bars along lines 2380
    displaying bars along paths 2386
    displaying difference values of
    bars 2379
    displaying lane allocations 2400
    displaying route courses 2387
    displaying stop catchment
    areas 2389
    displaying traversed stop
    points 2347
    displaying turns 2435
    editing layers 2339
    GIS objects 2215, 2352
    isochrones 2278
    labeling with charts 2405
    labeling with pie charts 2409
    labeling with tables 2402
    line objects 2354
    matrix window 1749
    one-way roads 2359
    point objects 2341
    POIs 2348
    saving and reading 2496
    schematic line diagram 2455
    shortest path search 2296
    signal time-space diagrams 2487
    specifying line style properties 2363
    specifying the line style 2365
    transfer relations 2392
    2695

    Index

    transfers display of regular


    services 2396
    turn volumes 2437
    Graphical display 744
    Graphical timetable 779
    see Timetable editor 1567
    Graphics interfaces 2650
    Gravity model 139, 188
    calculating 188
    calibrating 187
    Green time optimization 298-299
    Green times
    optimization 1921
    GUI
    changing the language 875

    H
    HAFAS import 2565
    settings
    reading 2573
    resetting 2573
    saving 2573
    HBEFA
    allocating input attributes 2197
    basis for calculating cold start excess
    emissions 688
    basis for calculating warm
    emissions 686
    defining fleet compositions 2192
    displaying results 2203
    displaying results graphically 2204
    emission calculation 685
    resetting emission calculation 2203
    saving results 2205
    settings for emission calculation 2191
    HBEFA-based emission calculation 685
    HCM 244
    Headway-based assignment 473, 2010
    coordination 495
    generalized costs 476
    headway calculation 475

    2696

    impedance 476
    Headway calculation
    from mean headway 475
    from mean wait time 476
    Highway Capacity Manual (HCM) 244
    Histogram 201
    Home trips 164, 178, 1669, 1687
    Hypothetic vehicle impedance (PrT assignment quality) 329

    I
    ICA 244
    assignment
    with ICA 380
    assignment with ICA 1946
    calculating and exporting 1499
    importing data from SATURN 2595
    node impedance calculation 1914
    Impact models 15, 20, 220
    Environmental impact model 222
    Operator model 221
    User model 220
    Impedance functions 222
    at node 241
    EVA model for passenger demand 166
    for transport systems 1908
    headway-based assignment 476
    PrT assignments 231
    timetable-based assignment 502
    Impedances
    connectors 232
    headway-based assignment 476
    links 232
    main turns 233
    nodes 232
    preloaded volume 233
    routes 231
    turns 232
    Imperial system
    as standard setting 865

    PTVGROUP

    Index

    Importing 2511
    connections 2560
    EMME/2 data 2588
    HAFAS data 2565-2566
    railML data 2573
    routes 2561
    SATURN data 2595
    Shapefiles 2221
    SQL database 2645
    TModel data 2592
    VDV452 data 2625
    Importing Access database 2644
    Importing ANM 2517
    Incremental assignment 336, 1932
    evaluation 341
    examples 337
    input and output attributes 339
    procedure 338
    Independence of connections 506
    Indicators 224
    aggregation along line hierarchy 673
    availability 3
    calculating aggregation levels 542
    calculation for coupled sections 676
    calculation for partially traversed
    links 675
    calculation principles 669
    documentation 3
    examples 543, 546, 549
    global indicators 225
    projection of additional attributes 676
    projection to analysis horizon 669
    source 3
    temporal dependencies (example)
    670
    territory-based cut 675
    Territory-based evaluation (aggregation levels) 545
    time cut 674
    Indirect attributes
    aggregation functions 106
    Average and AverageActive 107

    PTVGROUP

    Concatenate and
    ConcatenateActive 108
    Count and CountActive 106
    Distinct and DistinctActive 109
    Frequency and FrequencyActive 108
    Max and MaxActive 107
    Min and MinActive 106
    relations 105
    Sum and SumActive 107
    Infrastructure costs (PuT)
    entering 2153
    INRETS (VD function) 237
    Interactive analyses
    flow bundles 716
    isochrones 732
    shortest path search 741
    Interfaces 2511
    Interim results
    logging 876
    Interlining matrix
    calculating 2148
    Interlining trip 2148
    Intermediate points 120
    Internet maps
    see Backgrounds 2237
    Intersecting
    network objects 2217
    Intersecting objects 2217
    Intersection Capacity Analysis
    see ICA 1914
    Intersection Capacity Analysis (ICA)
    244
    all-way stop 279
    roundabouts 287
    signalized nodes 246
    two-way stop nodes 268
    uncontrolled nodes 245
    Interview data (PuT) 2051
    Isochrones 21, 732
    accessibility of link sections 2281
    accessibility of nodes and
    zones 2283

    2697

    Index

    combining PrT and PuT isochrones 740


    displaying 2278
    PrT 2279
    PrT isochrones 734
    PuT 2285
    PuT isochrones 736
    PuTclassified display 2287
    saving 2290
    setting graphic parameters 2288
    IsochronesPrT
    2D display 2279
    IsochronesPuT
    2D display 2285

    J
    Journey sections 72
    Journeys 72
    Junction
    traffic-related modeling 88
    Junction editor
    adjusting the attribute selection 1440
    calculating ICA 1499
    closing turns 1453
    creating crosswalks 1478
    creating detectors 1478
    creating signal controls 1464
    editing leg attributes 1479
    editing link attributes 1460
    editing links 1458
    editing main node attributes 1447
    editing main nodes 1446
    editing main turn attributes 1456
    editing main turns 1454
    editing node attributes 1443
    editing nodes 1441
    editing signal times in graphics 1490
    editing the geometry 1475
    editing the major flow 1446
    editing time-varying attributes 1499
    editing TModel attributes 1462
    editing turn attributes 1452

    2698

    editing turns 1450


    lanes and lane turns 1477
    opening 1439
    signal controllers 1463
    signal groups 1473
    specifying link orientations 1459
    specifying major flows 1442
    stretching and compressing stagebased signal programs 1491
    switching link labels on/off 1463
    switching to another network
    object 1439
    using 1435
    Junction model 88
    signal control 92
    Junction modeling 88

    K
    KALIBRI 1703
    Kirchhoff model 330

    L
    Labeling network objects with pie
    charts 2409
    Lane allocations
    displaying 2400
    setting graphic parameters 2401
    Lane turns
    allocating 1491
    editing attributes 1482
    Lanes 91
    creating pockets 1476
    displaying attributes 1480
    editing attributes 1481
    lane allocation 766
    lane turns 91
    resetting data 1075
    Layover time 1553
    Leg templates 92

    PTVGROUP

    Index

    Legend 708, 2255


    creating 2255
    editing 2260
    hiding/showing 2260
    opening 2260
    saving 2260
    Wizard 2255
    Legs 90
    editing attributes 1480
    marking 1476
    Length and speed data
    standard settings 865
    Level of Service 278
    Level of Service (ICA)
    all-way stops 1919
    Kreisverkehr 1919
    roundabouts 1918
    signalized nodes 1917
    two-way stops 1918
    Limiting edge display to time slot 2475
    Line block check 582
    common 584
    forced 584
    Line blocking 553-554
    block check 582
    block item and block item type 573
    block version 568
    blocks 570
    cost function 575
    coverage check 585
    data model 557
    depots 577
    displaying results 2119
    displaying results in lists 2119
    distributing empty trips and empty
    times 601
    evaluation of the procedure 556
    examples 557
    executing 2104
    exporting Block view PuT line
    blocks 2129
    initializing 2118
    layover times 577
    PTVGROUP

    lists 749
    optimization problem 555
    parameters 2105
    parameters with vehicle
    interchange 2114
    print output of the block display 2129
    procedure description 586
    PuT interlining matrix 601
    with vehicle interchange 2104
    procedure description 595
    without vehicle interchange 585,
    2104
    Line blocks
    attributes and options 2133
    block view 2119
    displaying 2119
    editing 2129
    Line hierarchy 68
    data consistency 76
    Line routes 69, 1306
    aggregating 76, 1360
    connecting 1355
    copying 1353
    creating 1307
    creating profile points
    automatically 1315
    creating the opposite direction 1357
    deleting 1362-1363
    editing attribute values 1336-1337
    editing line route items 1313
    editing shape 1307, 1311
    editing shape with system routes 80
    editing the shape of a line route
    course 1338, 1340
    generating from system routes 1347
    marking 1335-1336
    opening the Timetable editor 1358
    opening window 1306
    properties and options 1311
    selecting 1334-1336
    setting directions 1360
    setting lengths 1360
    setting parameters 1309
    2699

    Index

    setting profile points 1361


    setting route points 1314
    setting standard values 1291
    specifying lengths 74
    time profiles 1316, 1320
    Linear bottle-neck (VD function) 239
    Lines 69, 1291
    aggregating 1300
    copying 1298
    creating 1292
    deleting 1305-1306
    disaggregating 1303
    displaying 2380
    editing attribute values 1297
    marking 1295-1296
    opening the Timetable editor 1299
    properties and options 1292
    selecting 1295-1296, 1527
    setting standard values 1291
    Link attribute values
    replacing 1102
    specifying 1099
    Link orientations 89
    Link types
    allocating VD functions 1893
    defining 1099
    Links 52
    adapting VD functions 384
    allocating VD functions 1893
    blocking back model 1110
    calculating gradient from zcoordinates 1128
    changing attribute values 1113
    checking the symmetry of the
    directions 1127
    copying attributes 1120
    creating 1105
    defining link types 1099
    deleting 1134
    determining link course based on shortest path search 1125
    displaying bars 2367
    Dynamic User Equilibrium (DUE) 1111
    2700

    environmental impact analysis 1110


    generalizing link polygons 1118
    generating link attributes 1130
    generating link run times 1132-1133
    impedances 232
    interpolating z-coordinates 1129
    labeling link bars 1120
    link courses
    correcting 1116
    editing the shape 1115
    link types 53
    major flows 53
    managing 1099
    marking 1112
    node impedance calculation (ICA) 1112
    permitted transport systems 54
    properties and options 1107
    PrT capacity 55
    PrT speed 55
    PrT travel time 55
    PuT run time 56
    resetting DUE attributes 1133
    resetting link polygons 1118
    selecting 1112
    specifying lengths 74
    specifying link run time 74
    specifying settings
    PrT 1109
    PuT 1109
    specifying the PuT run time 1099
    splitting 1119
    List windows
    synchronizing 2320
    Lists 21, 745
    adjusting the layout 2308
    aggregating rows 2304, 2311
    assignment analysis 752
    attributes
    displaying 2309
    exporting 2329
    hiding 2309
    reading 2325

    PTVGROUP

    Index

    saving 2325
    coupling section items 749
    coupling sections 749
    different types 2299
    editing attribute values 2321
    editing window titles 2309
    emissions HBEFA 753
    filtering objects 2315
    finding a data record number in path
    lists 2318
    finding a network object 2317
    formatting 2306, 2309
    GIS objects lists 2217
    item lists 749
    line blocks 749
    line block items 749
    line block lists 749
    line block versions 749
    line lists 749
    line route items 749
    list layout
    adjusting 2308
    reading 2314
    saving 2313
    saving as standard layout 2313
    network information 752
    OD pair lists 748
    opening 2299
    path lists
    exporting to database 2330
    finding zone pairs 2318
    preselecting a category 2315
    printing 2336
    PrT
    quality assignment with ICA 752
    PrTassignment quality 752
    PrTpath sets 750
    PrTpaths 750
    PrTpaths on link level 750
    PuT
    assignment statistics 753
    OD pairs 750
    path legs 751
    PTVGROUP

    PuT assignment statistics 753


    PuTdetail list 748
    PuTpaths 751
    restricting to a selection 2315
    saving as PDF 2337
    sections
    selecting via the keyboard 2320
    selecting with the mouse 2319
    selecting columns 2309
    setting column headers 2306
    setting options 2306
    shortest path search 751, 2297
    sorting 2314
    stop lists 748
    stop points - arrivals/departures 748
    stop transfers and stop area walk
    times 748
    system route items 749
    territory lists 747
    time profile items 749
    time profiles
    transition walk times 748
    toolbar 2304
    transfers 751
    transport systems
    transition walk times 748
    values
    copying and pasting 2328
    vehicle journey items 749
    window 2304
    Log file 876
    Protocol.txt 879
    Log.txt 876
    Logit model (Distribution model) 331
    Lohse (VD function) 239
    Lohse model 332
    with variable beta 333
    LUCE
    Linear User Cost Equilibrium 1939

    2701

    Index

    M
    Main lines 69, 1364
    adding lines 1365
    creating 1364
    deleting 1367-1368
    deleting lines 1366
    editing attribute values 1366
    properties and options 1365
    selecting 1366
    setting active/passive 1366
    Main node
    creating 1169
    fuzzy surface alignment 1185
    Main nodes 60, 1169
    allocating nodes 1181
    allocating signal controls 1467
    boundaries
    deleting 1180
    editing shape 1175
    deleting 1186
    deleting enclaves 1183
    displaying main turns 2441
    editing attribute values 1173-1174
    editing cordon links 1187
    marking 1173
    normalizing surfaces 1184
    resetting lane data 1180
    selecting 1173
    setting coordination groups for signal
    controls 1178
    setting labels 1182
    setting polygon allocation 1176
    shifting the centroid 1175
    specifying major flows 1175, 1446
    updating impedances 1073, 1177
    Main OD pairs 1159
    Main relations 62
    Main turns 61
    allocating values to 1190
    calculating main turn lengths from shortest paths 1193

    2702

    closing 1457
    creating 1188
    deleting 1194
    displaying turn volumes 2441
    editing 1454
    editing attribute values 1190
    editing attributes 1456
    graphic parameters 2435
    impedances 233
    recalculating transport systems 1192
    selecting 1189
    setting active/passive 1189
    viewing in the Junction editor 1189
    Main zone matrices
    disaggregating 205, 1808
    Main zones 62, 1194
    boundaries
    deleting 1200
    editing shape 1200
    creating 1194
    deleting 1205-1206
    deleting enclaves 1203
    displaying the traffic demand 1197
    editing attribute values 1198-1199
    fuzzy surface alignment 1204
    marking 1197
    merging zone polygons 1202
    properties and options 1196
    selecting 1197
    setting labels 1201
    shifting centroids 1200
    Major flows 53
    Managing signal coordination
    groups 1497
    Map service
    adding 2240
    deleting 2242
    editing 2242
    Marking
    POIs 1390
    Marking window 810
    Matched transfers 496

    PTVGROUP

    Index

    Matrices 17, 130, 1607


    adding columns or rows 206, 1810
    adding complex term 203, 1798
    adding up 1777
    aggregating 207, 1808
    aggregating columns or rows 1811
    aggregating zone matrices to main
    zone matrices 1808
    areas
    selecting via the keyboard 1763
    average
    calculating 1700
    calculating combinations 1798-1799
    calculating formula-based 1727
    calibrating 1834
    calibrating (PrT) 218
    changing the view 1742, 1744, 1746
    classifying matrix values 201
    combining matrices and vectors 202
    combining with demand
    segment 1607
    comparing 1756
    copying the diagonal 1770
    correcting 209, 1816
    correcting with TFlowFuzzy 18171818
    generating filter matrices 1833
    correcting with TFlowFuzzy
    diagnosis 1830
    deleting 1757
    demand matrices 130
    diagonal 1732
    extracting 201
    setting 202, 1765
    disaggregating 1808
    disaggregating main zone matrices to
    zone matrices 1808
    dividing 1785
    editing 199, 1775
    functions 199
    editing attribute values 1731
    estimating gravitation
    parameters 1703

    PTVGROUP

    exponential function 202, 1792


    extending 206, 1810
    see Matrices, splitting 208
    forming maximum or minimum 202
    forming reciprocal 202, 1787
    generating 1725
    graphic parameters 1749
    gravity model
    calculating 188
    calibrating 187
    histogram 1752
    interactive editing of matrix
    values 1763
    main zones 1732
    making symmetric 202
    matrix values
    copying 1769
    editing 1763
    marking 1761
    reading 1764
    replacing 1764
    matrix valuesreplacing 1767
    maximum 1793
    mean value
    upper/lower triangle 1797
    mean value upper/lower triangle 202
    minimum 1795
    multiplying 1783
    OD pair 1715
    opening 1721
    overview 810, 1715
    projecting 203, 1800
    projecting path volumes (PrT) 218,
    1833
    projection by territory 1805
    projection of aggregated areas 205
    properties 1731
    properties and options 1733
    raising to power 202, 1788
    reading $O format 1761
    reading an external matrix into the network 1731
    reading in 1731
    2703

    Index

    reflecting 201
    lower triangle 1773
    upper triangle 1772
    rounding 1777
    saving 1733, 1738
    as file 1733
    as partial matrix 1738
    settings 1760
    saving partial matrices 1734, 1739
    scatter plot 1756
    setting values 1764
    settings
    display 1758
    editing 1758
    read 843
    skim matrices 130
    splitting 208, 1814
    subtracting 1781
    symmetrizing 1797
    taking the logarithm 202, 1790
    transposing 201, 1774
    updating with TFlowFuzzy
    preparing data 1817
    using Log file 1775
    weighting matrices 174
    window 1718
    zones 1732
    Matrices correcting with TFlowFuzzy opening old settings 1833
    Matrix comparison 1756
    Matrix correction 209, 1816
    calibrating matrix (PrT) 218
    projecting path volumes (PrT) 218
    TFlowFuzzy 210
    Matrix editor 19, 130, 199, 1717
    Matrix editor window 1717
    layout 1747
    Matrix toll 1422
    Matrix types 1716
    Matrix values
    aggregated display 1744
    export 1771

    2704

    filtering 1744
    reading 1770, 1780
    rounding 1777
    Matrix window
    graphic parameters 1749
    setting options 1758
    Mean value
    calculating
    attributes 198
    matrices 198
    Merge network 29
    opening 903
    terminating 904
    Merging networks 902
    Message file 876-877, 881, 883
    Messages window 883
    Messages.txt 876, 883
    Method of Successive Averages 198,
    1700-1701
    Metric system
    as standard setting 865
    Mode choice 18, 1606, 1633
    allocating modes
    EVA model for passenger
    demand 1680
    Standard 4-step model 1648
    Tour-based model 1688
    EVA model for passenger demand 165,
    1680
    nested (Standard 4-step model) 137,
    140
    Standard 4-step model 139, 1649
    nested 1653
    utility function nested 1657
    Tour-based model 182, 1689
    Model transfer file
    applying 916
    creating 908
    Model transfer files 31
    Models
    comparing 22
    Modes 46, 48, 1055, 1059
    creating 1059
    PTVGROUP

    Index

    deleting 1061
    properties and options 1060
    Modifications 925
    MPA
    see Multi-point assignment 1888
    see Multi Point Assignment 59
    MSA
    see Method of Successive
    Averages 198, 1700-1701
    Multi-point assignment 1888
    Multi Point Assignment 59, 312
    Multi procedure 188, 191, 204
    trilinear (EVA) 172

    N
    NCHRP 255 445, 1983
    Nested Mode Choice
    see Mode choice, nested 140
    see Mode choice, Standard 4-step
    model, nested 1653
    Network
    checking 1505
    displaying the check results 1510
    editing 957
    finding errors 1505
    fixing errors 1510
    generating subnetwork 1601
    rotating or shifting 2210
    window 808
    Network check 94
    Network data
    reading with incomplete line routes or
    system routes 861
    Network display
    bars 753
    classified 755
    labeling with charts 757
    labeling with tables 757
    Network editor
    synchronizing 1436
    Network files
    opening 844
    PTVGROUP

    reading additively 851


    Network merge 28
    analysis time intervals 30
    examples 28
    Network model 15-16
    Network object types 958, 962
    displaying in the network 1040
    Network objects
    block 570
    block item 573
    block item types 44
    block version 568
    block versions 44
    buffer 701
    checking the state 1040
    classified display 2411
    column charts 2492
    connectors 41, 58
    count locations 45, 84
    customizing window 825
    deleting 2324
    demand segments 40, 46, 48, 130
    detectors 45, 84
    editing 1008, 1033
    editing attribute values 983, 990, 993
    fare zones 45
    filters
    reading 1025-1026
    saving 1024
    finding in the network 999
    editing results 1003
    GIS objects 45, 86, 691
    initializing filter conditions 1023
    intersecting 696, 701
    labeling with charts 2405
    labeling with tables 2402
    line blocking 557
    line routes 43, 69
    lines 43, 69
    link types 41
    links 41, 52
    main lines 44, 69
    main nodes 41, 60
    2705

    Index

    main OD pairs 62
    main turns 41, 61
    main zones 41, 62
    marking 1004
    modes 40, 46, 48
    network object types 958
    nodes 40, 50
    OD pairs 42
    Operator model (PuT) 551
    paths 42, 63
    Points of Interest (POI) 45, 81
    PuT coordination groups 45
    PuT operators 44, 67
    PuT vehicles 68
    screenlines 46, 87
    selecting 1004
    setting network objects active/passive by
    spatial selection 1033, 10381039
    showing and hiding 2339
    specifying boundaries 1042
    stop areas 42, 66
    stop points 43, 65
    stops 42, 67
    system routes 44, 80
    territories 41, 63
    ticket types 45
    time profiles 43, 70
    toll systems 45
    transport systems 40, 46
    turn standards 41
    turns 40, 50
    using filters to set network objects active
    or passive 1008
    valid days 42, 68, 95
    vehicle combinations 44, 68
    vehicle journey sections 43, 72
    vehicle journeys 43, 72
    vehicle units 44, 68
    zones 41, 56
    Network window 808
    changing the view 814-815, 818-821
    customizing 809
    2706

    display by analysis time interval 821


    displaying the entire network 820
    order of layers 2339
    printing 2499
    refreshing the view 821
    Networks
    comparing 22
    merging 902
    Node geometry 90, 1475
    crosswalks 91
    lane turns 91
    lanes 91
    leg templates 92
    link orientations 89
    node legs 90
    node templates 92
    Node impedance
    methods 1921
    Node impedance calculation
    ICA 1914
    Nodes VDF 1914
    selecting the method 1911
    Turns VDF 1913
    Node impedances 241
    calculate according to HCM 244
    calculating 1911
    nodes VD function (TModel) 243
    turns VD function 243
    Node templates 92
    Node topology 90
    graphically displaying 766
    Node types
    allocating VD functions 1894
    Nodes 50, 1063
    aggregating isolated 1076
    allocating main nodes 1181
    allocating signal controls 1466
    allocating VD functions 1894
    control types 245
    creating 1063
    creating leg templates 1485
    creating node templates 1486

    PTVGROUP

    Index

    deleting 1083-1085, 1088


    displaying turns 2441
    displaying turns as bars 2435
    editing attribute values 1066
    editing in the Junction editor 1435
    finding 1066
    impedances 232, 241
    merging 1069
    properties and options 1066
    resetting lane data 1075
    selecting 1066
    setting polygon allocation 1071
    shifting 1068
    signal control 92
    signal time optimization 298
    signal timing
    editing 1487, 2487
    signal group-based control 1488
    stage-based control 1492
    specifying major flows 1070, 1442
    stages
    creating 1493
    deleting 1494
    editing 1494
    editing signal group
    allocation 1493
    updating impedances 1073
    updating impedances with signal
    cycle and split
    optimization 1072
    Nodes VD function (TModel) 243
    Nodes VDF 1914
    Noise-Emis-Nordic 222
    Noise-Emis-Rls90 procedure 222
    Noise volume 679
    Noise-Emis-Nordic procedure 679680
    Noise-Emis-Rls90 procedure 679
    Noise volumes
    calculating 2185
    displaying 2187
    saving 2188
    setting parameters 2183
    PTVGROUP

    Normalizing 124, 1052

    O
    OD matrices
    see Demand matrices 130, 1607
    OD pairs 57, 1159
    One-way roads
    displaying 2359
    OpenStreetMap (CycleMap)
    see Backgrounds 2237
    OpenStreetMap (Mapnik)
    see Backgrounds 2237
    OpenStreetMap import 2614
    checking import results 2618
    configuration sets 2620
    defining import processes 2623
    downloading data 2617
    editing data 2617
    using default configuration 2617
    using user-defined
    configuration 2619
    OpenStreetMap importadapting the
    import process 2619
    Operating modes 996
    Operator model 551, 2091
    Operator model (PuT) 221, 541
    examples 543, 546, 549-550
    Indicators (aggregation levels) 542
    line blocking 553
    network objects 551
    Territory-based evaluation (aggregation levels) 545
    work flow 552
    Operators
    editing attribute values 1282
    in the operator model 551
    Optimizing cycle and green time 298,
    302, 1501
    Optimizing offset times 302
    Origin-destination pair 1715
    Origin wait time (Timetable-based assignment) 503
    2707

    Index

    Overview
    the Matrices tab 1716

    P
    Parallelization 873
    Parameter files
    saving 1815
    Passenger sample survey 2051, 2059
    Passenger survey 531
    direct assignment 540
    reading survey data 2055
    survey data
    assignment 540
    plausibilization 535
    reading 535
    Path legs
    PrT 230
    PuT 453
    Path search
    setting parameters 1225
    Path sets
    creating 1218
    deleting 1223
    editing attribute values 1221-1222
    marking 1220
    properties and options 1219
    selecting 1219-1220
    setting active/passive 1221
    Paths 63, 223, 1218
    displaying (flow bundles) 730
    editing the course 1232
    filtering (flow bundles) 716
    finding 1225
    PrT 230
    PuT 453
    saving 1890
    settings 1996
    PDF export 2654
    Perceived journey time 467, 502
    Person groups 19, 132, 1606, 1620
    creating 1620

    2708

    editing attribute values 1621


    properties and options 1620
    Person groupsediting the number of persons 1621
    Personal Geodatabase 2646
    connecting 2211
    disconnecting 2217
    Personal Geodatabase (PGD) 691
    PGD
    see Personal Geodatabase 2646
    Plausibilization of survey data 2059
    POI categories
    creating 1384
    deleting 1385
    editing 1385, 1396
    using user-defined attributes 1386
    Point 120
    Points of Interest (POI) 81
    POIs
    aggregating 1393
    allocating 1388, 1398
    creating 1386
    deleting 1401
    deleting enclaves 1394
    editing attribute values 1390-1391
    editing category 1396
    editing image size and rotation
    angle 1389
    fuzzy surface alignment 1395
    graphic parameters 2348
    managing 1384
    normalizing surfaces 1395
    properties and options 1387
    selecting 1390
    setting active/passive 1390
    shifting 1392
    Pollution-Emis 222
    Pollution-Emis procedure 682
    Polygons 120, 714, 2251
    copying 2254
    creating line/polygon 2251
    creating rectangles 2251

    PTVGROUP

    Index

    deleting 2254
    deleting all 2254
    editing 2252-2253
    merging points 1053
    normalizing surfaces 1052
    saving 2255
    see Polygons 2251
    shifting 2253
    Position data 2243
    PostScript export 2652
    Preset the analysis time slot 959
    Printing 2499
    print output
    preview 2508
    starting 2508
    setting a print page 2499
    specifying a print area 2502
    specifying a print frame 2504
    Procedure description
    line blocking without vehicle interchange 585
    Procedure parameters
    in the scenario management 935
    opening and saving 1867
    Procedure sequence 1847
    adding procedure 1848
    creating 1707
    creating and editing group 1854
    executing procedures 1857
    general settings 1860
    opening 1847
    opening and saving 1867
    setting up and starting 1847
    viewing the calculation status 1887
    Procedure settings 1860
    opening and saving 1867
    Procedures
    line blocking 2104
    PuT interlining matrix 2148
    Processor cores 873
    Production 138, 146, 150, 164, 1641,
    1669
    Program interface 804
    PTVGROUP

    Program start 891


    Project
    see Scenario management 922
    Projecting path volumes (PrT) 218
    Projection 98
    examples 99
    matrices 1800
    vehicle journey section
    attributes 2165
    Projections 705
    Protocol files 876
    activity protocol 876, 879
    examples 879
    log file 876
    message file 876
    settings 876
    specifying settings 876
    Protocol.txt 879
    PrT
    path legs 230
    path objects 63
    paths 230
    PrT assignment procedures 226, 1888,
    1931
    convergence criteria 329
    dynamic stochastic assignment 439,
    1976
    Dynamic User Equilibrium (DUE)
    410, 1969
    equilibrium assignment 342, 1934
    Equilibrium_Lohse 366, 1942
    example network 228
    impedance functions 231
    incremental assignment 336, 1932
    Level of detail for results 1890
    Linear User Cost Equilibrium (LUCE)
    1939
    settings 1888
    stochastic assignment 385, 1951
    taking basic volume into
    account 1891
    toll 397
    TRIBUT 397

    2709

    Index

    TRIBUT - Equilibrium assignment 1961


    TRIBUT - Equilibrium_Lohse 1966
    using solution as initial solution 233
    VD functions 233
    with blocking-back model 1925
    PrT path sets 1218
    PrT paths
    converting 1232
    creating 1224
    deleting 1235
    displaying 2386
    distributing a matrix to paths 1236
    editing attribute values 1230
    opening paths 1228
    parameters for the path search 1225
    properties and options 1226
    selecting 1229
    setting active/passive 1230
    PrT skims
    user-defined 1986
    PuT
    Aux transport systems 512
    operating indicators 604
    cost per hour 651
    examples 657
    kilometer costs 651
    line route and timetable
    analysis 633
    link costs 652, 654
    network performance
    measurement 643
    operator costs 656
    stop point costs 655
    transport supply measurement 639
    vehicle costs 651
    vehicle type costs 650-651
    Operating indicators
    distributing empty trips and empty
    times 601
    Operator model 20, 551
    operators 67, 551
    passenger surveys 531
    path legs 453
    2710

    paths 453
    revenues 659
    calculate using fare model 663
    distribute across PuT path legs 664
    fixed revenue per
    PTripUnlinked 660
    fixed revenue per traversed fare
    point 661
    vehicles 68
    PuT assignment procedures 449, 1995,
    2006
    headway-based 473, 2010
    settings 1995
    timetable-based 498, 2021
    TSys-based 471, 2007
    PuT connections and transfer flows 765
    PuT cost model 2153
    PuT interlining matrix 601
    PuT line blocking
    see Line blocking 2104
    PuT line blocks
    see Line blocks 2091
    PuT operating indicators
    deleting 2166
    PuT operator model 2091
    PuT revenues
    cost coverage calculation 668
    PuT transfer relations 764
    PuToperating indicators
    cost and revenue model 648
    examples 630
    operating cost 648-649
    revenue calculation 659
    Python
    script language 2669

    Q
    Queues 236
    Quick view
    customizing window 825
    opening layout file 813

    PTVGROUP

    Index

    saving layout 813


    settings 812
    window 810
    Quick View
    editing attribute values 995
    Quick view window 810

    R
    RailML
    exporting data to railML 2585
    importing 2573
    loading import settings 2584
    notes on imported data 2581
    resetting export settings 2587
    restoring import settings 2585
    saving export settings 2586
    saving import settings 2584
    RailMLloading
    reading in export settings 2587
    Ramp metering 236
    RBC 1470
    manual 4
    Reading an abstract network
    model 2517
    Reading network data additively
    adjusting settings 852
    defining conflict avoidance and handling 857
    selecting data tables 854
    Reading stage templates 1495
    Recalculating lengths 2209
    Rectangles 2251
    Redo
    restoring the previously undone
    action 871
    Regular services
    creating 1536
    editing 1546
    Resetting DUE attributes 1133
    Result analysis 21
    Revenues (PuT) 648
    fares 468
    PTVGROUP

    RLS-90 222, 679


    Rounding
    attribute value 990
    demand and volume 1995
    matrix values 1777
    Rounding demand data 1995
    Rounding volume data 1995
    Route loading
    TSys-based assignment 473
    Route search
    TSys-based assignment 473
    Routes
    distribution of demand 329
    impedances 231
    importing 2561
    importing (extended) 2562
    saving 1890
    skims 457

    S
    Sample surveys 2051
    SATURN import 2595
    Saving
    PrT assignment results 1890
    user preferences 869
    Saving a backup copy 836-837
    Saving an abstract network
    model 2512
    SC
    see Signal controllers 1463
    Scalable Vector Graphics 2656
    Scenario management 31, 921
    creating new project 922
    distributed computing 938
    adding compute nodes
    manually 945
    calculating scenarios 946
    copying files to compute
    node 943
    downloading result files 944
    managing compute nodes 941

    2711

    Index

    settings of Scenario calculation server 939


    exporting data 955
    modifications 925
    specifying procedure parameters 935
    work flow 921
    Scenarios 31, 921
    calculating 36, 938
    comparing 948
    create based on modifications 36
    defining modifications 35
    distributed calculation 37
    managing 933
    Schematic line diagram 770
    creating legend 2467
    Schematic line diagrams 2451
    bundling coupled edges 2472
    deleting unused edge courses 2474
    displaying 2451, 2453, 2455
    displaying demand and transfer
    flows 772
    displaying individual stops 2452
    displaying stops 2452
    displaying supply 771
    editing 770
    manual post-processing 2467
    saving and reading the layout 2478
    selecting aggregation level 2452
    selecting vehicle journeys 2453
    separating all edges 2472
    setting the layout 2475
    transferring the layout 772
    Schematic line network
    displaying statistics 2479
    Screenlines 87, 1428
    course
    editing shape 1432
    resetting 1433
    creating 1428
    creating the opposite direction 1433
    deleting 1434-1435
    editing attribute values 1431

    2712

    marking 1430-1431
    properties and options 1429
    selecting 1430-1431
    Screenshot
    exporting 2663
    Script code
    integrating into the procedure
    sequence 2668
    Script files
    integrating into the procedure
    sequence 2668
    Python 2669
    running 2664
    Selecting a decimal point 873
    Selecting the direction of traffic 864
    Service trip patterns
    calculating 2086
    displaying 1547
    Service trips
    see Vehicle journey sections 1556
    see Vehicle journeys 1533
    Setting coordination groups for signal controls 1074
    main nodes 1178
    Setting polygon allocation
    count locations 1408
    main nodes 1176
    nodes 1071
    stop areas 1261
    stop points 1278
    stops 1247
    Setting route points 1314
    Shape files 692, 2221
    importing 2221
    Shapefiles
    exporting 2230
    Shortcuts in Visum 829
    Shortest path search 21, 501, 741, 2291
    displaying in lists 2297
    PrT 21, 742, 2291
    PuT 21, 743, 2292
    timetable-based search 2292

    PTVGROUP

    Index

    transport system-based
    search 2295
    saving 2298
    setting graphic parameters 2296
    Showing/hiding extended
    markings 2448
    Signal control 92
    calculating coordination 1921
    offset analysis 1925
    signal offset analysis 1925
    signal timing coordination of several
    SC 1923
    stage templates 94
    Signal controls 1463
    allocating main nodes 1467
    allocating nodes 1466
    creating 1464
    deleting 1472
    editing 1469, 1472
    in RBC 1470
    editing signal times 1487, 2487
    editingin Vissig 2528
    external 2528
    optimizing cycle and green time 298,
    302, 1501, 1921
    optimizing offset times 302
    see Signal controllers 1463
    signal time-space diagram 2479
    Signal coordination 298, 302, 1501
    Signal groups 1473
    allocating
    lane turns or crosswalks 1484
    lanes or legs 1484
    allocating crosswalks 1491
    allocating lane turns 1491
    creating 1473
    deleting 1475
    editing attributes 1485
    properties and options 1474
    Signal programs
    changing 1470, 1488, 2558
    managing (Vissig) 2542
    switching off 1470, 1488, 2558
    PTVGROUP

    Signal time-space diagram 773


    Signal time-space diagrams 2479
    exporting (SVG) 2491
    setting graphic parameters 2487
    Signal time optimization 298
    Signal times
    adjusting the column display 1489
    display options 1489
    displaying all 1490
    Signal timing
    coordination 1923
    stage-based control 1492
    Signal timing coordination 1921
    Skim matrices 21, 130, 1607, 1716
    calculating for PrT 1984
    calculating for PuT 2073
    main diagonal
    specifying values 1866
    meta data 1865
    settings 1865
    Skims 224
    calculating (PrT) 311
    PuT 457, 459-460
    skim matrices 224
    Smart map
    applying graphic parameters 817
    customizing window 825
    refreshing 814
    window 813
    Spatial selection
    displaying network object types 1040
    inverting active/passive 1038
    mode 997
    reading from file 1039
    setting active/passive 1033
    Specifying boundaries 1042
    creating new faces 1050
    deleting faces 1051
    deleting polygon points 1046
    main nodes 1175
    main zones 1200
    merging polygon points of two polygons 1047
    2713

    Index

    polygon points 1044


    separating merged polygon points 1049
    shifting polygons 1045
    territories 1211
    toll systems 1423
    Specifying directories 837
    Specifying major flows
    main nodes 1175
    nodes 1070
    Specifying project directories 837
    Stages
    deleting templates or template
    sets 1495
    Standard 4-step model 18, 129, 136
    mode choice 139
    nested 137, 140
    time-of-day choice 141
    trip distribution 139
    trip generation 138
    Standard time series 1608
    creating 1608
    deleting 1614
    editing attribute values 1609
    editing for pairs of zone types 1615
    editing the start time 1613
    properties and options 1609
    time intervals
    creating 1609, 1611
    deleting 1612
    editing 1612
    Stochastic assignment 385, 1951
    commonality factor 391
    distribution models 329
    evaluation 385
    examples 393
    Stop areas 1255
    connecting (nodes) 1262
    creating 1255
    deleting 1264-1265
    editing attribute values 1258
    marking 1258
    opening the Timetable editor 1261

    2714

    properties and options 1256


    selecting 1258
    setting access nodes 1262
    shifting 1260
    Stop areas setting
    polygon allocation 1261
    Stop catchment areas
    displaying 2389
    setting graphic parameters 2389
    Stop points 65, 1266
    creating 1266
    deleting 1279-1280
    displaying time profiles 1271
    displaying transport systems 1271
    displaying vehicle combinations 1272
    duplicating 1275
    editing attribute values 1273-1274
    marking 1272-1273
    matrix with volumes 1999
    merging 1275
    opening the Timetable editor 1277
    properties and options 1267
    selecting 1272-1273
    setting polygon allocation 1278
    shifting 1275
    Stops 67, 1237
    creating 1237
    deleting 1253-1254
    deleting walk and wait times 1251
    displaying catchment areas 762
    editing attribute values 1239, 1243
    editing the matrix 1240-1241
    hierarchies 64
    marking 1242
    merging 1245
    opening the Timetable editor 1246
    properties and options 1238
    selecting 1242
    setting specific transition walk
    times 1250
    shifting 1244
    stop areas 66

    PTVGROUP

    Index

    Stops setting
    polygon allocation 1247
    transfer walk times 1248
    Straps 1422
    Structural properties 138, 1606, 1622
    creating 1622
    deleting 1623
    editing values 1623
    EVA model for passenger
    demand 143
    properties and options 1623
    tour-based model 175
    Subnetwork
    generating 1602, 2517
    options for line routes 1604
    Subnetwork generator 117
    Surface items 121
    Surface model 120
    multi-part surface 124
    normalizing surfaces 124
    tables 120
    Surfaces 120
    fuzzy alignment 127, 1053-1054,
    1156, 1185, 1204, 1216, 1395,
    1426
    normalizing 1052
    Survey data
    assignment 540
    plausibilization 535
    reading 535
    SVG 2656
    export 1568, 2656, 2660
    SVG export
    editing the coding 2662
    signal time-space diagrams 2491
    SVGexport
    transfers display of regular
    services 2400
    Swap file 1760
    Synchronization
    list window 2320
    model transfer file 915
    network editor 1436
    PTVGROUP

    schematic line diagram 2474


    signal time-space diagram 2485
    transfers display of regular
    services 2395
    System optimum 236, 342
    System routes 80, 1368
    applying run times 1328
    changing time attributes 1372
    copying 1376
    creating 1368, 1378
    creating a run time per vehicle combination 1372
    creating the opposite direction 1377
    deleting 1383-1384
    editing attribute values 1374
    editing the course 1375
    marking 1372-1373
    properties and options 1371
    selecting 1372-1373
    setting parameters 1370
    using for empty trips 2094
    using for line routes 1347

    T
    Tables 21
    Tabular display 744
    Tabular timetable 776
    Taking basic volume into account (PrT)
    1891
    tCur 233
    Temporal utility 468
    Territories 63, 102, 1206
    creating 1206
    deleting 1217-1218
    deleting enclaves 1215
    editing attribute values 1209-1210
    fuzzy surface alignment 1216
    marking 1209
    normalizing surfaces 1215
    properties and options 1208
    selecting 1209
    setting labels 1214
    2715

    Index

    shifting centroids 1211


    specifying boundaries 1211
    Texts 708, 2232
    changing the font 2236
    copying 2234
    creating 2232
    deleting 2235
    deleting all 2236
    editing 2233
    editing the font size 2235
    opening 2237
    rotating 2233
    saving 2237
    shifting 2233
    TFlowFuzzy 210
    example diagnosis list 1830
    example statistics list 1831
    see Matrices, correcting with
    TFlowFuzzy 1817
    Tie points 2247, 2249
    Time
    entering 866
    entering units 866
    Time-of-day choice
    calculating 1658
    utility function 1660
    Time-of-Day Choice
    Standard 4-step model 141
    Time-varying attributes 114
    Time data
    entering 866
    Time intervals
    see Analysis time intervals 1861
    Time profiles 70, 1316, 1320
    accessing 1317
    copying 1320
    coupling 77, 1331
    creating 1320
    deleting 1334
    deleting unused profile points 1331
    editing 1317, 1321-1322
    editing run and dwell times 1328

    2716

    editing vehicle combinations 1322


    setting a reference stop point 1327
    setting times for time profile items 1326
    shifting the departure times of vehicle
    journeys 1327
    specifying a reference journey 1318
    specifying fare points 1330
    specifying run times 74
    Time series 96, 131, 1606
    examples 100
    managing 1608
    matrix numbers 19, 97, 131
    percentage 19, 97, 131
    Timetable-based assignment 498, 2021
    adjusting the registry 2049
    connection choice 505, 510
    connection preselection 502
    connection search 499
    Branch and Bound 499
    shortest path search 501
    distribution of trips over
    connections 505
    evaluation 499
    fare 505
    impedance 502
    independence of connections 506
    opening 513
    perceived journey time 502
    PuT-Aux TSys 512
    speeding up calculation 2049
    temporal utility 468
    temporal utility of a connection 504
    Timetable editor 22, 776, 1526
    calculating the stop sequence 1558
    creating new user-defined
    attributes 1538
    displaying attributes 1568-1570
    displaying line routes 1358
    displaying stops 1246, 1261
    editing attribute values 1541, 1554
    evaluations 776

    PTVGROUP

    Index

    graphical timetable 779, 1526, 1565,


    1567
    export (DXF) 1568
    export (SVG) 1568
    printing 1600
    setting graphic parameters 1577
    graphics parameters
    reading 1600
    resetting 1599
    saving 1599
    layout
    reading 1572
    saving 1571
    specifying 1568
    opening 1526
    selecting lines 1299, 1527
    stop points 1277
    tabular timetable 776, 1526
    exporting 1600
    printing 1600
    setting graphic parameters 1573
    specifying the background of the
    table 1574
    specifying the table font 1576
    vehicle journey sections 1531
    vehicle journeys 1531
    window 1530
    Timetable network graph
    see Schematic line diagrams 2451
    Timetables 75
    TModel 243
    uncontrolled nodes 1919
    using 1914
    TModel import 2592
    settings
    reading 2594
    resetting 2595
    saving 2594
    Toll in the assignment 397
    Toll systems 85, 1417
    creating 1417
    deleting 1427-1428
    deleting enclaves 1424
    PTVGROUP

    editing attribute values 1420


    finding 1419
    fuzzy surface alignment 1426
    marking 1420
    normalizing surfaces 1425
    properties and options 1419
    selecting 1419-1420
    setting labels 1424
    shifting centroids 1423
    specifying boundaries 1423
    specifying the matrix toll 1422
    Toolbars
    customizing 824-825
    overview 823
    resetting settings 827
    scaling 825
    Total Excess Cost TEC (PrT assignment quality) 329
    Tour-based model 19, 129, 174
    activity chain based model 174
    constraints 175
    destination choice 178
    home trips 178
    mode choice
    combined 182
    structural properties 175
    trip distribution
    combined 178
    trip generation 176
    utility function 179, 182
    Traffic demand
    distributing across PrT
    connectors 312
    distributing across routes 329
    Transfer relations 764
    displaying 2392
    setting graphic parameters 2392
    Transfer wait time (Timetable-based
    assignment) 503
    Transfers display of regular services
    displaying 2392
    exporting (DXF) 2400
    exporting (SVG) 2400
    2717

    Index

    printing 2399
    reading graphic parameters 2399
    saving and reading graphic
    parameters 2398
    saving graphic parameters 2399
    setting graphic parameters 2396
    setting the bar display for transfer
    flows 2394
    setting the graphic parameters for transfer flows 2397
    specifying a print frame 2398
    synchronizing 2395
    Transport demand 129
    model 15, 17, 136
    see Demand 1606
    time reference 96
    time series 96
    Transport system-based
    assignment 471, 2007
    Transport systems 46
    Transport systems (TSys) 1055
    creating 1055
    deleting 1058
    properties and options 1057
    Travel demand 15, 17
    distribution to PuT connectors 469
    Travel demand matrices
    see Demand matrices 17
    TRIBUT - Equilibrium assignment 1961
    TRIBUT - Equilibrium_Lohse 1966
    TRIBUT procedure 397
    Trip distribution 18, 1606, 1633
    EVA model for passenger demand 165,
    1680
    generating demand matrices
    EVA model for passenger
    demand 1679
    Standard 4-step model 1642
    Tour-based model 1688
    Standard 4-step model 139, 1643
    Tour-based model 178, 1689
    Tour-based model editing the curve progression 1696

    2718

    Tour-based model utility function 1695


    Trip generation 18, 1606, 1633
    EVA model for passenger demand 146,
    1666
    Standard 4-step model 138, 1638
    Tour-based model 176, 1684
    TSys-based assignment
    evaluation 472
    route loading 473
    route search 473
    Turn standards
    deleting 1093
    Turn types
    allocating VD functions 1896
    Turn volumes
    angle from link orientation 1502
    displaying 2441
    displaying in the Junction editor 1502
    exporting as graphics 1503
    print frame parameters 1502
    setting graphic parameters 2437
    Turn volumes display 21
    Turns 50
    adapting VD functions 384
    allocating standard data 1095
    allocating VD functions 1896
    automatic allocation of the turn
    type 1097
    closing 1453
    closing U-turns when inserting 1093
    copying attributes to reverse
    direction 1454
    creating 1093
    deleting 1098
    displaying bars 2435
    displaying turn volumes 2441
    editing attribute values 1094
    editing in the Junction editor 1450
    graphic parameters 2435
    impedances 232
    managing 1090
    PrT capacity 52
    PrT turn time 52
    PTVGROUP

    Index

    recalculating transport systems 1096


    selecting 1094
    turn standards 51
    turn types 51
    Turns VD function 243
    Turns VDF 1913
    Tutorials 2

    U
    Undirected values 2304
    Undo 870
    redo 871
    Undoing actions 870
    Updating impedances
    main nodes 1073, 1177
    nodes 1072-1073
    User-defined attributes 110
    User models 20
    User optimum 236, 342
    User preferences
    opening the window 870
    overview 867
    restoring 870
    Using the subnetwork generator 1601
    Utility terms
    adding up 1798

    V
    Vacation days
    creating 1521
    deleting 1525
    editing attribute values
    properties and options
    Valid days 68, 95
    creating 1512
    deleting 1520
    editing attribute values
    properties and options
    Value of time (VT) 399

    PTVGROUP

    1525
    1522

    1519
    1513

    VD functions 233, 1892


    Akcelik 238
    allocating connectors 1894
    allocating link types 1893
    allocating node types 1894
    allocating turn types 1896
    BPR (according to Traffic Assignment
    Manual) 235
    calculating node impedances 1911
    conical 235
    conical marginal 236
    INRETS 237
    linear bottle-neck 239
    logistic 237
    Lohse 239
    quadratic 237
    SIGMOIDAL_MMF_LINKS 237
    SIGMOIDAL_MMF_NODES 237
    specifying parameters 1896
    user-defined 240, 1899
    VDV 452 import 2625
    Vehicle-bound costs (PuT)
    defining 2153
    Vehicle combination set 595
    Vehicle combinations 68, 1282
    creating 1286
    deleting 1290
    editing attribute values 1289
    in the operator model 551
    properties and options 1287
    replacing on vehicle journey
    sections 1554
    specifying cost rates 1289
    storing vehicle combination
    sets 1289
    vehicle units
    adding 1288
    deleting 1289
    editing 1288
    Vehicle journey sections 72
    creating 1551
    deleting 1557
    editing 1551, 2141
    2719

    Index

    normalizing 1556
    projecting attributes 2165
    replacing vehicle combinations 1554
    Vehicle journeys 72
    automatic numbering 1291
    coupling in pairs 1544
    creating 1534, 1536
    deleting 1550
    displaying 1533
    editing 1541, 2141
    finding 1536
    marking 1539
    separating 1545
    shifting temporally 1542
    shifting to a different line 1543
    Vehicle units 68, 1282
    creating 1283
    deleting 1285
    editing attribute values 1285
    in the operator model 551
    properties and options 1284
    specifying cost rates 1285
    Version comparison 23, 893
    deleting 902
    editing 901
    saving values in attribute 899
    updating 902
    Version files
    comparing 893
    Versions
    comparing 22, 892
    opening 840
    saving 840-841
    settings 835, 843
    Vissig 2528
    Vissim export 2511
    node preview 2512
    settings
    reading 2516
    saving 2516
    Visum
    description of interfaces 3

    2720

    documents 2-3
    dongle 4, 7
    FAQs 10
    fields of application 1
    installation 9
    installation guide 3
    interfaces 7
    manuals 2
    Online Help 2
    Quick Start 3
    Release Notes 3
    settings for program start 891
    start 9
    support 10
    system requirements 6
    tutorials 2
    update 10
    Volume delay functions
    defining 1892
    Volumes
    saving 2003
    saving additively 2003

    W
    Warnings
    settings 877
    Weekly calendar 95
    Weighting
    calculating 1671
    weighting function
    editing the curve progression 1676
    Weighting (EVA) 166, 174
    evaluation functions 165, 167
    Box-Cox 168
    Box-Tukey 168
    combined 168
    EVA1 168
    EVA2 168, 170
    Kirchhoff 168
    Logit 168
    Schiller 168, 171

    PTVGROUP

    Index

    TModel 168
    weighting matrices 174
    weighting probabilities 166
    Weighting matrices 130, 1607, 1677
    editing 1678
    reading in 1677
    saving 1677
    setting to zero 1678
    Window
    Network editor 818
    Timetable editor 1530
    Windows
    arranging 806
    customizing 824-825, 827
    docking windows together 807
    grouping 807
    list window 2304
    moving 807
    Quick view 810
    removing docking 808
    resetting settings 827
    scaling 825
    Smart map 813
    World files 713

    editing attribute values for emission


    calculation 1141
    editing productions and
    attractions 1140
    fuzzy surface alignment 1156
    generating 1152
    marking 1141
    normalizing surfaces 1155
    properties and options 1137
    setting labels 1153
    shifting centroids 1144
    specifying connectors 1138
    splitting 1145

    Z
    Zone
    selecting 1141
    Zone matrices
    aggregating 205, 1808
    Zones 56, 1135
    aggregating 1147, 1150
    attributes (EVA) 145
    boundaries
    deleting 1144
    editing shapes 1144
    creating 1136
    deleting 1157
    deleting enclaves 1154
    displaying the demand
    segments 1139
    editing attribute values 1142
    PTVGROUP

    2721

    Potrebbero piacerti anche