Subnetwork generation

Enter or select a path and file name under which you want to save the version file.

Selection of a procedure to deal with line routes which intersect the limits of the subnetwork (Selecting options for line routes).

If this option is selected, stop points, stop areas, and stops that are located on active links or nodes but are not served by active line routes are also included in the subnetwork.

This selection is only available if an assignment has already been calculated.

Selection of the demand segments (of internal and private transport) for which the existing demand is to be saved with the subnetwork under the specified name. In the Export as column, you can see whether the demand is exported as a total matrix or as a single matrix with a matrix time series.

If one or more matrix time series exist in the network because the assignment is dynamic, the matrix time series are automatically created in the subnetwork, too.

Note

In private transport, a matrix time series is only calculated if there is the result of a simulation-based assignment (SBA) or pseudo-dynamic volumes (PDV).

In public transport, paths must be saved as connections in the assignment so that matrix time series can be exported to the subnetwork (Settings for saving PuT assignment results).

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

Notes

The option is only relevant to PrT networks. If you do not select 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.

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.

Note

Make sure that zone numbers do not occur twice in the subnetwork.

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

If the option has been selected, the cordon zones are numbered consecutively.

Note

Make sure that zone numbers do not occur twice in the subnetwork.

Minimum number for cordon zones

Enter the number at which the numbering starts.

Enter the number of the zone type (0..9), to which the cordon zones shall be allocated.

If the option has been selected, only those cordon zones will be generated to the subnetwork that are required according to the assignment.

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.

Opening a subnetwork generator parameter file of the type *.xml.