Release OmniTRANS V6.0.4

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

Features

Graphical User interface

• Introduced an "absolute value" box for the label values in the Object Colour and Bandwidth Designers.

OtQuery

• Introduced OtQuery.filter and OtQuery.filtered.

Fixes

Documentation

• The documentation for the new class OtEmission has been improved.
• The documentation about the Emission Parameters is extended.

Graphical User interface

• Previously, adding a mode to multiple link types will only add default values to the last link type. This has been fixed.
• Previously, applying animated compare bandwidths in the Bandwidth Designer with more than one purpose resulted in an error. This has been fixed.
• Previously, copying Google Maps while editing links resulted in an error. This has been fixed.
• Previously, extending a transit line could result in a missing stop at the end. This has been prevented.
• Previously, it was possible to create multiple links between two nodes when downgrading nodes. This has been prevented.
• Previously, lay-out changes in the info tab were not saved. This has been fixed.
• Previously, reading the link data stopped when a corrupt link (with data, but without one of the nodes) was found. This lead to a network where not all links had the correct data (e.g. missing junction data and wrong colour of the link). This has been fixed.
• Previously, the "Copy to other direction" in the Attribute Editor didn't work in combination with Super Mode. This has been fixed.
• Previously, the drawing of transit line did not follow some of the underlying links if the line spacing was set to 0. This has been corrected.
• Previously, the OtChart buttons were confused in Windows 7 layout. This has been fixed.
• Previously, the project setup could crash when adding new dimensions which were also used as extended parameter. This has been fixed.
• Previously, using the legend within a split screen could result in different views between both windows. This has been fixed.
• Since the release of OmniTRANS 6.0.2, values could not be shown on the desire lines. This has been fixed.

Import/Export

• Previously, areas with many area points (approx> 34,000 points) were not imported correctly during the shape file import. This has been fixed.
• Previously, some errors messages in job outputs were replaced by your Windows username. This has been corrected.
• Previously, the ASCII import could not handle more than 10,000 new records. This has been fixed.

OtNetwork

• It is no longer possible to generate a new project with OtNetwork.makeSubNet where there are multiple connectors for the same centroid in the selection. This is because makeSubNet cannot create the correct new centroids and links for it.
• Previously, OtNetwork.makeSubNet lost information of junctions (including the turns) when the link which enters the junction was in the cordon selection. This has been corrected.
• Previously, OtNetwork.makeSubNet was copying some outdated data (for nodes and turns) to the new project. This has been corrected.

OtTraffic

• Important: Previously, the shortest path engine within OtTraffic stopped searching for the shortest path after finding a path including a connector linked with the destination centroid. Therefore, other connectors linked with the destination centroid where not used from that origin which meant that potentially shorter paths to that destination were not found. This has been fixed in OtTraffic.modelVersion 9 (default modelVersion from OmniTRANS 6.0.4). To preserve your old assignment results, you have to define OtTraffic.modelVersion = 8. Please note that this only applies for projects in which centroids have more than one connector.
• Previously, generating cordon matrices for multiple cordons with the multi class assignment failed. This has been corrected.
• Previously, OtTrafficV60 resulted in different rounding (last digits) when using multi-threading (OtTraffic.numberOfThreads). This has been fixed. Please note that the significance of these rounding is approximately 1*10^-12 vehicles. In theory only dynamic assignments results (e.g. StreamLine), for which OtTraffic results are used as static loads, will be influenced by this fix.
• Previously, results of OtTraffic.cordonMatrix were always stored in iteration 1 instead of the defined iteration number. This has been fixed.
• Previously, screenline, selected link and skim matrices were calculated incorrectly in a multi class assignment. This has been corrected.
• The previous implementation of the property OtTraffic.loadPercentages is removed. OtTraffic.loadPercentages is now an alias of OtTraffic.loadFractions.

Update

•  Previously, reports and designs including a current selection could not deal with <current selection> when updated from OmniTRANS 5.1 to OmniTRANS 6.0. This has been fixed.