Settings for decimal places, aggregation functions, and connecting journeys

1. From the Network menu, choose Network settings.

The Network settings window opens.

2. Select the Attributes tab.

3. Make the desired changes.

Standard number of decimal places by data type section
Element	Description
Co-ordinates	The co-ordinates 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 (Editing a background) Editing graphic parameters (Specifying basic settings) Editing network objects: Zones, territories, detectors, main zones, nodes, POIs, stops, stop areas Status bar of program window (cursor position) (Program interface) Note The setting does not affect the normalization of surfaces. When merging surfaces, the value can be set directly in the corresponding window. The value set here is accepted as the default setting, but can be changed (Merging all polygon points with identical co-ordinates and Importing Shapefiles).
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 (Setting graphic parameters for the display of isochrones) Default values of connectors (Specifying default values for connectors)
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 (Intersecting objects)
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 (Managing detectors and Managing stop points) Window PuT fares (Defining PuT fares) Displaying turn volumes (Adjusting the basic settings for the display of turn volumes) Aggregating nodes (Aggregating isolated nodes)
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: Window PuT fares (Defining PuT fares) Editing operators (Editing the attribute values of operators) Vehicle units and vehicle combinations (Properties and options of vehicle units and Properties and options of vehicle combinations)
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 (Editing main node attributes in the list view) Editing main turns (Editing main turn attributes in the list view)
Other floating-point numbers	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 (Creating a user-defined attribute)
Output to file with maximum precision	This option is enabled by default. Values are saved in files of the type .net, .dmd, .tra and .att with the maximum possible number of decimal places (twelve at maximum). Other settings for numbers with decimal places are ignored. Note This setting does not affect files of the type *.xml. Parameters are always saved to these files with maximum accuracy.

Aggregation function section
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 text length (empty = 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.

Connecting journeys section
Element	Description
Show connecting journeys only between different lines	If this option is selected, only transfers to vehicle journeys of different lines are counted as connecting journeys.
Maximum wait time for reached connecting journeys	Enter the transfer wait time up to which a transfer from one vehicle journey to another is classified a connecting journey. The wait time only applies to the connecting journeys reached.
Maximum negative wait time for missed connecting journeys	Enter the maximum time period that may elapse between arrival and missed vehicle journey so that this vehicle journey is counted as a missed connecting journey. This period does not include the walk time between vehicle journeys. The walk time is added when calculating the missed connecting journeys.

Tip: Alternatively, you can access the settings by clicking the Network settings for connecting journeys button in the Connecting journeys list.

Walk links section
Walk links within a stop	Search without restrictions Shortest path search accounts for all PuT Walk path legs of a network. Based on the stop matrix, Visum automatically determines all possible (even indirect) transfers and the most favorable transfer for each pair of stop areas. In the process, it uses the combined time of an indirect transfer instead of the direct transfer if it is less than the direct time. For stop areas which are connected to the same access node, the transfer time is 0 since each stop area without a time penalty is connected to its access node. Example According to the stop matrix, the transfer from stop area A to stop area C takes 5 minutes. The transfer from stop area A to stop area B takes 1 minute and the transfer from stop area B to stop area C takes 2 minutes. In this case, Visum identifies a transfer 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. The shortest path search is expensive in case of a large number of paths. However, we recommend using this option, as it is the only one that finds the shortest walk link (time) between two points in all cases. Do not permit search via access node The shortest path search is restricted to PuT Walk path legs of the stop matrix. The transfer times are taken into account like for the search without restrictions; the access node, however, is ignored, so that the transfer time from the matrix is used for transfers 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. Note When using this option and the option No search, use the matrix as specified, it cannot be guaranteed in all cases that a shortest walk link (time) will be found. You should therefore use this option carefully and check the results for plausibility. The background to this special behavior is: the local restriction of routing options in the search algorithm can lead to optimal paths being dominated by alternatives that are actually faster to reach the common end of the path, but cannot be continued to more distant points in a permitted manner (Example). No search, use the matrix as specified The PuT Walk path legs are generated exactly according to the entered transfer times. Visum does not determine indirect transfers. Any transfers for which no transfer 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 transfer including a change between stop areas, the given transfer time is also used for this change. The existence of blocked transfers within the stop matrix might lead to the blocking of further paths. Example According to the stop matrix, the transfer from stop area A to stop area C takes 5 minutes. The transfer from stop area A to stop area B takes 1 minute and the transfer from stop area B to stop area C takes 2 minutes. Nevertheless, Visum would use 5 minutes for the transfer from stop area A to stop area C. This makes sense if, for example, streets have to be crossed for the indirect transfer or if the 'intermediate' stop area is not used, since it is located underground. Notes We recommend this option only for experienced users since you have to ensure that the matrix contains meaningful and matching entries. If the direct transfer time between two stop areas is much higher than the combined time, which would be needed for indirect transfers, Visum might find useless connections (Example).

Walk links section

Element

Description

Walk links within a stop

Search without restrictions

Shortest path search accounts for all PuT Walk path legs of a network. Based on the stop matrix, Visum automatically determines all possible (even indirect) transfers and the most favorable transfer for each pair of stop areas. In the process, it uses the combined time of an indirect transfer instead of the direct transfer if it is less than the direct time. For stop areas which are connected to the same access node, the transfer time is 0 since each stop area without a time penalty is connected to its access node.

Example

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. The shortest path search is expensive in case of a large number of paths. However, we recommend using this option, as it is the only one that finds the shortest walk link (time) between two points in all cases.

Do not permit search via access node

The shortest path search is restricted to PuT Walk path legs of the stop matrix. The transfer times are taken into account like for the search without restrictions; the access node, however, is ignored, so that the transfer time from the matrix is used for transfers 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.

Note

When using this option and the option No search, use the matrix as specified, it cannot be guaranteed in all cases that a shortest walk link (time) will be found. You should therefore use this option carefully and check the results for plausibility. The background to this special behavior is: the local restriction of routing options in the search algorithm can lead to optimal paths being dominated by alternatives that are actually faster to reach the common end of the path, but cannot be continued to more distant points in a permitted manner (Example).

No search, use the matrix as specified

The PuT Walk path legs are generated exactly according to the entered transfer times. Visum does not determine indirect transfers. Any transfers for which no transfer 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 transfer including a change between stop areas, the given transfer time is also used for this change.
The existence of blocked transfers within the stop matrix might lead to the blocking of further paths.

Example

According to the stop matrix, the transfer from stop area A to stop area C takes 5 minutes. The transfer from stop area A to stop area B takes 1 minute and the transfer from stop area B to stop area C takes 2 minutes. Nevertheless, Visum would use 5 minutes for the transfer from stop area A to stop area C. This makes sense if, for example, streets have to be crossed for the indirect transfer or if the 'intermediate' stop area is not used, since it is located underground.

Notes

We recommend this option only for experienced users since you have to ensure that the matrix contains meaningful and matching entries.

If the direct transfer time between two stop areas is much higher than the combined time, which would be needed for indirect transfers, Visum might find useless connections (Example).

4. Confirm with OK.