Hyperpath configuration parameters

Attribute map of the attribute names in the database (field name) and the TDE internal names.

The structure of the map is:
key1=value1, key2=value2, … keyN=valueN

• “key” is the name of an attribute in the street, link, or street turn attribute set (LATTlist, SATTlist, STURlist)
• “value” is the name used in TDE to handle the attribute

Do not use this map for the attributes that handle the information about the street hierarchy (HIER), speed (SPED), disabling (DISA), intersection time (ITIM), green share (GREN), and cycle time (CYCL). There are specific parameters for these.

List of coefficients of cost attributes that have to be imported from the PREF table in addition to the standard fields.

Usually this is done to enable customizable route choice because mode preferences are sensitive to these attributes.

The list has comma-separated values.

Code of the default preference group used for preferences.

Default: default

List of the names of the custom attributes that have to be imported from the LINK table in addition to the standard fields.

Usually this is needed to enable customizable route choice because mode preferences are sensitive to custom attributes (see → User Defined Attributes (UDAs)).

The list is formatted as comma separated values.

Maximum hierarchy to include in the primary network. Streets that have a higher hierarchy are ignored.

Default: 9

Maximum value that a coefficient may have. If any coefficient is greater than or equal to this value, it is considered infinite and the corresponding attribute yields infinite cost if greater than 0.

Validity: ≥ 0
Default: 99999

Minimum hierarchy to include in the primary network. Streets that have a lower hierarchy are ignored.

Default: 0

Maximum number of transport system types in preference coefficients.

Default: 5

List of the names of the custom attributes that have to be imported from the STRT table in addition to the standard fields.

Usually this is needed to enable customizable route choice because mode preferences are sensitive to custom attributes (see → User Defined Attributes (UDAs)).

The list is formatted as comma separated values.

This signature is often used as a suffix or prefix in IO files to identify the file owner. Also it is used to avoid workflow conflicts among different instances of the same software.

Data type: Integer

Enables the Graphic User Interface (GUI).

• 0: do not show the GUI.
• 1: show the GUI (Execute button disabled).
• 2: show the GUI.

Default value: 2

• 0 = run normally
• 1 = run without any user interaction
• 2 = run completely in background

Validity: [0, 2]
Default: 0

• 0 = do not enable debug mode
• 1 = enable debug mode

Validity: [0, 1]
Default: 0

• WEB_SERVICE
• DARS
• ALGORITHM_CALIBRATION

The needed reservations to add (SQLite dependencies for the .NET Framework) are defined according to the value of this input variable.

• en
• it
• de

Unit: km/h

Unit: km/h
Validity: (MIES, 90]

• A high value means low accuracy in externalities evaluation but fast import
• A low value means high accuracy in externalities evaluation but slow import

Unit: km/h

If a coefficient is greater than this value, the streets with the corresponding attribute are not excluded from the path solution.

≤ 0 = do not update event

Unit: s

≤ 0 = do not update traffic state

Unit: s

Unit: m/s

• If empty, only one range exists, which is from 0 to infinite.
• If empty and also AstarDistValueList is empty, a linear trend is used.

Unit: m

AstarDistValueList(i) is the value of the A* parameter for the request that has an estimated distance ∈ [ AstarDistList(i-1), AstarDistList(i) ].

nAstarDistValueList = nAstarDistList + 1

• If empty, there exists only one range, which is from 0 to infinite.
• If empty and also AstarDistValueList is empty, a linear trend is used.

Format: modeCode_distValue

Example:
car_10000,car_100000,car_1000000,carshortest_10000,
carshortest_100000,carshortest_1000000,bicycle_10000,
bicycle_100000,bicycle_1000000,pedestrian_10000,
pedestrian_100000,pedestrian_1000000

AstarModeDistValueList(i) is the value of the A* parameter for the request that has an estimated distance ∈ [ AstarModeDistList(i-1), AstarModeDistList(i)].

nAstarModeDistValueList = nAstarModeDistList +1

For the distance intervals, the variable used is the variable AstarModeDistList if it includes the current mode. Else the variable used is the variable AstarDistList.

Format: modeCode_astarValue

Example:
car_0,car_1,car_1.1,car_1.1,carshortest_0,carshortest_1,
carshortest_1.1,carshortest_1.1,bicycle_0,bicycle_1,
bicycle_1.1,bicycle_1.1,pedestrian_0,pedestrian_1,
pedestrian_1.1,pedestrian_1.1

Unit: m

Unit: m

It is only considered if it is greater than or equal to 0.

If not specified, an automatic precomputation is performed.

If empty and NumberOfClusters > 0, precomputation is performed for all modes.

Format: comma-separated list

If cluster data is used, LabelCorrecting is forced to be TRUE.

Validity: [0, 1]

The condition used for the check is:

d(gi−gj) ≥= b × (d(i−gi) + d(gj−j))

• d(gi−gj) is the straight line distance between gates
• d(i−gi) is the straight line distance between the i-th node (included in the k-th cluster) and the gates gi of the k-th cluster

Validity: [1, ∞]

≤ 0 = do not update the event (evnt)

Unit: s

Interval between each update travel time session

≤ 0 = do not update the current performance (cdyn)

Unit: s

≤ 0 = do not update mid-term forecast data

Unit: s

≤ 0 = do not update the observed performance (tsta)

Unit: s

≤ 0 = do not update and do not import for the first time

Unit: s

Unit: %

• 0 = no
• 1 = yes
• 2 = only permit if the unique possible turn between two links

If TRUE, the transport system “pedestrian” can make any turn.

Good value = True with LABC = False, not relevant otherwise.

Typically, setting this the value to FALSE is a good choice, but if you do not admit backward jumps, setting LabelCorrecting to TRUE can guarantee the optimality of the solution even if OrderIntraBucket is FALSE.

If not specified for a mode, the variable LabelCorrecting is used.

Format: modeCode_distValue modeCode_Inf --> it exists only one range from 0 to Inf for the mode with code modeCode.

Unit: m

• 1 = yes
• 0 = no

Overwrites the variable AstarDistValueList.

AstarModeDistValueList(i) is the value of the A* parameter for the request that has an estimated distance ∈ [ AstarModeDistList(i-1), AstarModeDistList(i) ] .

nAstarModeDistValueList = nAstarModeDistList + 1

For the distance intervals, the variable used is the variable AstarModeDistList if it includes the current mode. Else the variable used is the variable AstarDistList.

Format: modeCode_astarValue

If x ≤ SMALL_ANG, x is considered to be a small angle.

Unit: deg
Validity: [0, 180]

If x ≥ LARGE_ANG, x is considered to be a large angle.

Unit: deg
Validity: [0, 180]

Unit: s

Unit: s

Format: set of comma-separated fields

Format: set of comma-separated fields

The search is stopped if: t − t' > t * TimeMultiplier

Unit: m

Unit: s

Unit: km/h

Unit: s

Unit: m

Unit: m

Unit: m

Unit: m

Unit: m

Unit: m

Unit: m

• If > 0, the PuT calendar is: [FDAY_PUT, Min(LDAY_PUT, FDAY_PUT + MAX_PUT_DAYS)].
• If ≤ 0, the PuT calendar is: [FDAY_PUT, LDAY_PUT]

Unit: s

0 = no waiting time

Unit: s

Filter type can be:

• O = “OR” condition
• A = “AND” condition

The condition structure is “attribute operator value”.

• The attribute is the code of the attribute of the condition, such as sped, tort, urbn, etc.
• Available operators are: “=”, “<>”, “>”, “<”, “>=”, “=<”.

The elements of each filter are separated by an underscore: “_”

Example:

O tunn > 0,O brdg > 0,A urdn > 0,A sped > 0

(Considers all the active (sped > 0) tunnels and bridges in an urban area.)

Filter type can be:

• O = “OR” condition
• A = “AND” condition

The condition structure is “attribute operator value”.

• The attribute is the code of the attribute of the condition, such as sped, tort, urbn, etc.
• Available operators are: “=”, “<>”, “>”, “<”, “>=”, “=<”.

The elements of each filter are separated by an underscore: “_”

Example:
O tunn > 0,O brdg > 0,A urdn > 0,A sped > 0

(Considers all the active (sped > 0) tunnels and bridges an urban area.)

• Among attributes, the separator is a comma (“,”).
• Among modes, the separator is a semicolon (“;”).

Example:
car=disa,daut;bicycle=disa,dbik;pedestrian=disa,dped

(Considers all alias code.)

For the mapped street attributes, consider the alias code.

For the mapped street attributes consider the alias code.

For each link element of the response XML, there is defined a list that contains the values of the changeable attributes. If the value of one of the changeable attributes differs between the current link and the next link of the path result, this attribute is included in the list of the link XML element. Its new value is given.

The elements of this list must be contained in SATTlist. If an element of CATRlist is included in the street attributes map (ATTmap), the alias value must be used.

Unit: s

RequestTimeout_constant ms + 1000 * RequestTimeout_coefficient s/km * OD_distancekm

Unit: ms

RequestTimeout_constant ms + 1000 * RequestTimeout_coefficient s/km * OD_distancekm

Unit: s/km

If, for a distance interval, not all the request had been found, the calibration by is performed using only the created request.

If not specified, random requests are considered.

If not specified, the calibration considers the Now Date.

Format: yyyy/MM/dd HH:mm

If not specified, the calibration will consider the From Date + 30 days.

Format: yyyy/MM/dd HH:mm

If not specified, requests are not exported.

If not specified, the result is exported to a file named AlgorithmCalibrationResult.txt, located in the same folder as Hyperpath.exe.

Predefined step for incrementing the A* parameter when optimizing the algorithm.

If this number is negative, all steps between the minimum and the maximum A* values are considered.

Format: comma-separated list

Format: comma-separated list