Release OmniTRANS V6.0.8

There is a new version of OmniTRANS V6.0 available: 6.0.8. Below you find the release notes.

Features

Graphical User interface

• Previously, it was not possible to change the area's centroid number manually in the Attribute Editor. This is made possible (in Super Mode only).
• The OtEmission calculation output is now included in the Loads & Costs tab.
• Enlarged the number of characters for report columns to 100 characters instead of 50.

 OtEmission

• The Delft Tutorial Project has been expanded with jobs and designs that provide examples of the features of OtEmission.
• Introduced useSaturationSpeedFactors to determine whether the saturationSpeedFactors property should be used or not.
• Extended the saturationVCFactors format. It's now possible to add factors per OmniTRANS link type.
• Extended the saturationSpeedFactors such that the speed factors can be link dependent.
• OtEmission's totalLoad property is replaced by the saturationLoad property. This property allows you to calculate emission values per user class with loads from a multi-class (multi-mode) assigment.

OtMatrixEstimation

• Extended the input of lockMatrices. It is now allowed to provide an array including multiple arrays, like [[1,3,2,1],[1,2,2,11]].

Fixes

 
Graphical User interface

• Previously, adding a new transit line in a large network was slow. This has been improved.
• Previously, a query disappeared when toggling between 'Simple expression' and 'SQL' in the Queries Editor. The query is now preserved until the user makes changes
• Previously, a transit line could not be shortened when the last link was an one-way link. This has been fixed.
• Previously, in the 'Turn Settings', the 'show turns without manual data' tick box did only take the impedance value into account. This has been corrected.
• Previously, it was not possible to animate combination data on links. This has been corrected.
• Previously, it was not possible to set data on a manually added turn field. This has been corrected.
• Previously, link direction arrows were too thick when printing on a large size paper. This has been corrected.
• Previously, plots did not take "hide label on small links" option into account. This has been fixed.
• Previously, 'current selection' in the bandwidth designer did not work. This has been corrected.
• Previously, the designer's halo checkbox did not trigger the save design arrow on top of the window. This has been fixed.
• Previously, the legend was printed behind object labels. This has been fixed.
• Previously, the link attributes could be switched from direction when moving the connected node. This has been fixed.
• Previously, the outline colour for one-way links was not used. This has been corrected.
• Previously, the print preview opacity, 1-99%, was working reversed. This has been fixed.
• Previously, the transit line and stop editor always showed the first dimension as active in the pull-down menu of the clock button. The data was actually from the selected time dimension. This has been fixed.
• Previously, when changes were made for the transit shortest path engine and applied, the shortest path engine was not always reloaded. This has been corrected.
• Previously, when checking the junction in the Junction Editor, it could report an error while the junction layout was ok. This has been corrected.
• Previously, when deleting a transit line, the attribute editor was not cleared correctly. So when selecting a new transit line, it looks like two transit lines were selected. This has been corrected.
• Reading link based data (bandwidth data) was accidentally made slower since 6.0.2. This has been corrected.

Import/Export

• Introduced an additional check for non-existing selections during a shape file export. When providing a non-existing selection, the user receives an error message.
• Previously, the calculation of coordinates of counts was link shape independent. The position is now calculated based on the link's shape.
• Removed the "transit line 0 could not be found" messages during the OmniTRANS import.

Job Engine

• Previously, the BDE could supply an 'Insufficient disk space'-error which occurred when the disk free space is near to a multiple of 4GB. This has been fixed.

Manual

• Introduced the manual page "OtEmission - Theoretical Background".

OtEmission

• Previously, the pcu property of OtEmission didn't accept natural numbers. This has been fixed.
• Replaced the property saturationICFactors by saturationVCFactors.

OtMatrixEstimation

• Previously, when the property mapScreenlineMatrices received a mapped pmturi which is equal to his original, OmniTRANS blocked. Supplying the same pmturi is now prevented, because this is undesired behaviour.

OtQuery

• Previously, the OtQuery class couldn't read blobs as part of an array. This has been fixed.

OtSeedPoint

• Previously, the interval size of the property aggregation was overruled by the step size. This has been corrected.

OtTable

• Previously, the OtTable class couldn't read blobs as part of an array. This has been fixed.

OtTraffic

• Previously, no error was given when a non-existing cordonMatrix was defined in a cordon assignment. This has been corrected.
• Previously, OtTraffic was sometimes unstable with multiple threads. This has been fixed.
• Previously, the assign method REPLACECOST deleted the load values by accident. This has been corrected.
• Previously, some error messages were not always readable. This has been corrected.
• Previously, the shortest path engine could give a colour to links that were not part of the shortest route. This has been corrected.
• Previously, when insufficient memory was available for multi-threading, the assignment could terminate unexpectedly, without providing a warning/error. This has been corrected. Now OtTraffic will provide an error if there is insufficient memory informing the user that the assignment is not completed.

OtTransit

• Previously, the OtTransit path showed the wrong colour for the access mode. This has been corrected.
• Previously, the second parameter (phiAccessLineChoice) of the property logitParameters was not used. This has been corrected.