Settings for the plausibility check of survey data

Plausibilization of survey data:General parameters tab

Element	Description
General extent of plausibilization	All data records If this option has been selected, all data records – even those previously unprocessed – are checked with the selected parameters. Note Since this procedure costs a lot of computation time, this option should be applied carefully. For example, you can use it to conclusively check the plausibility of all data together with uniform parameters, after you have previously checked the plausibility of various datasets with different parameters independently of each other. Only unprocessed data records If this option has been selected, only unprocessed data records - having plausibility status G0 – are checked. Only unprocessed and unplausible data records If this option has been selected, only data records with either plausibility status G0 (untreated records) or plausibility status G9 (unsuccessful plausibilization result = implausible) are checked.
Extent of plausibilization by dataset type	All If this option has been selected, all data records are checked with the selected parameters. Only types from / to If this option has been selected, only data records of the specified types are checked.
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 (Format of a multi-row survey file). 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 (Loading survey data).
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 (Example of a log file).

Plausibilization of survey data:Survey path leg tab

In this tab you configure the parameters for plausibilization of survey path legs.

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 If this option has been selected, Visum first searches 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	Max. permitted difference from the specified departure time (+/-) 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.
Connection search	Connection search from boarding to alighting stop if no line route could 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 options	Parameters for timetable-based connection search (Shortest path search). Consider 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 exceeds 0, 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 (Timetable-based assignment: Shortest path search page). Correction (reverse) (Timetable-based assignment: Shortest path search page)
Section Stay on board before and past the survey path leg	In this section, you can enforce a transfer before or after the survey path leg, because it is known from the survey that the corresponding transfer took place. Force boarding right before the survey path leg Opens the Attribute (PuT path) , which allows you to select an attribute. If the value of the attribute is greater than zero, during plausibilization, boarding can be enforced before the survey path leg. Force alighting right before the survey path leg Opens the Attribute (PuT path) , which allows you to select an attribute. If the value of the attribute is greater than zero, during plausibilization, alighting can be enforced before the survey path leg.

Plausibilization of survey data:Pre-/Succeeding tab

In this tab you configure the parameters for plausibilization of preceding and succeeding path legs.

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 sub-legs 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.

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 departure time 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 Max. 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 search. Via Max. permitted deviation from specified time of departure (+/-) you can enter the desired tolerance range. Max. permitted difference from the specified departure time (+/-) 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 departure time has not been checked. This option applies to multi-row survey data records only, since single-row 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.
Connection search	Find connection for 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. In doing so, ignore the possibly specified transport system 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-part preced./succeed. part 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 (or succeeding) section.
Search options	Parameters for timetable-based connection search (Shortest path search). Consider 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 exceeds 0, 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 (Timetable-based assignment: Shortest path search page). Correction (reverse) (Timetable-based assignment: Shortest path search page)