| Basis tab | |
|---|---|
|
Element |
Description |
|
Delete ridership data section |
At the beginning of the procedure Do not delete ridership data If this option is selected, the data is added to the existing data set. Conflict handling ensures the uniqueness of the ridership data keys. Delete ridership data of the reference demand statement If the option is selected, the data of the selected demand segment is replaced by the newly imported data. Delete all ridership data If this option is selected, all ridership data, including that of the other demand segments, is deleted and replaced by the newly imported data. |
|
Read additively |
If the option is selected, the data will be read in addition to (either after or prior to plausibilization) data already available for the selected demand segment. |
|
Conflict handling |
Use these options to specify what should happen if the data to be imported contains ridership data whose data set number and index already exist. Ignore new data set If this option has been checked, the data set is not read from file. Overwrite old data set If this option has been checked, the new data set is read from file this way replacing the existing data set. Cancel reading completely If this option has been checked, reading is canceled. Create data set with new number If this option is selected, a new data set number is assigned to the ridership data. |
|
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 (Using protocol files). In file If this option has been checked, a protocol file is generated. Click the |
button to select a path and file name. The protocol file stores messages and details on data not read from file.|
Attributes tab |
|
|
Element |
Description |
|
Column name |
Listing of column names in the ridership data file |
|
Attribute |
Visum attributes into which the values of the attributes in the Column name column are written. Click the button to change the allocation of the attribute |
|
Create user-defined attributes |
Click this button to generate user-defined attributes for PuT paths if there is no matching attribute for an entry under Column name. The ID, code and name of the attribute is derived from the corresponding entry in the Column name column. |
