Generating Transfers By Same Line
These transfers are generated for single lines where opposite direction connections are required, for example, trips that are built for scheduling purposes that terminate in the schedule but the passenger continues on the route in the opposite direction.
- Open the Automatic tab.
- In the Functions field, select the Same Line check box.
-
In the From Lines field, select the lines from which transfers
start. Alternatively, to choose all lines, click ALL.
To deselect all lines, click NONE.
- In the To Lines field, select the lines to which transfers end.
-
From the Existing Transfers list, choose one of the following
options:
- Keep Old: Does not overwrite transfers that exist (for example, if a transfer is inactive, it is not enabled and the level and no cost status remain intact).
- Save new: Overwrites existing transfers with the selected new level, enable transfer.
- Use Highest Level: Uses the transfer along with its other attributes that has the highest transfer level. Use Lowest Level: Uses the transfer along with its other attributes that has the lowest travel level.
-
Click Refresh.
The Transfers by Node frame displays all common node>stops for the selected lines.
- Optional:
Select a node/stop and click Zoom to zoom to it on the system
map.
The point is highlighted with a blue square.
-
Press CTRL and highlight each node at which a transfer is to be
created.
Alternatively, click ALL to create transfers at all common nodes. (Click NONE to clear your selections.)
- Optional: Fill in the Level and Min. Time fields.
- Optional:
In the Cost list, select 0 - Zero
Cost.
Same Line transfers are often but not always no cost transfers.
- Optional: In the Validity frame, enter a time period in the From and To fields.
- Select the days of the week when the transfers are applied.
- Optional: In the Comment field, enter any information you want to add regarding the transfers.
-
Click Generate.
A message appears to verify your selections.
- Click OK.
A confirmation message appears showing the number of transfers generated.
The CTM itinerary algorithm does not count these as actual transfers and any itinerary detailed is compressed (that is, shows passenger getting on route 1N and off route 1S rather than on 1N, off 1N, on 1S and off 1S).