Main New Features

Below, you find the list of all features:
 
Graphical User Interface

• A report can now be saved as a CSV file (or copied to clipboard) with the headers included.

• Introduced arrows in the Junction Editor behind the Mode and Time options. This makes it more clearer that junction settings are mode/time dependent.
• Introduced two RSE (Relative Standard Error) items (RSE to value1 and RSE to value2) for Bandwidth Comparison, Desire Line Comparison, and Report Column Comparison.
• The output-matrices (skim, screenline and cordon matrices) in the Matrix Editor are now ordered by the PMTURI, instead of date.
• The issue tracker is now automatic loaded when starting OmniTRANS (related to Remote Hosting).

Job Engine

• Previously, when Ruby crashed in an uncontrolled way, no error was supplied. This error is introduced.

OtHash, OtMatrix and OtVector

• Introduced the properties erf and erfc for OtHash, OtMatrix and OtVector. These properties allow you to calculate the (complementary) error function.

Main Corrections

 
It's now possible to compare network data between variants and sub-variants of another variant.

Implementation of the OtTraffic.getPath property has been improved, and now run times are much faster than before.

Several users experienced that the background maps were being moved from their proper location. This has been fixed.

Below, you find the list of all corrections:
 
Graphical User Interface

• Deselecting multiple objects is accelerated.

• Previously, a one way link (defined as direction 2) was not properly drawn (wrong link width). This has been corrected.
• Previously, a transit line was drawn incorrectly when a link point is positioned at the same place as the node. This has been corrected.
• Previously, adding transit lines did not take into account that links could be invisible, because they are filtered. This has been fixed.
• Previously, background maps could sometimes move to random locations. This has been prevented.
• Previously, deleting centroids in super mode did not remove all data associated with centroids in the variants. This has been corrected.
• Previously, it was not possible to compare network data (e.g. speed) between a subvariant and another variant. This has been fixed.
• Previously, it was not possible to extend a transit line backward on one-way links. This has been corrected.
• Previously, it was not possible to extend/shorten a transit line at a node where the same transit line passes multiple times. This has been corrected.
• Previously, removing a link and quickly selecting a new link could remove both links. This has been prevented.
• Previously, the Transit Line Editor gave a warning about missing links for other time period than which one was asked to open in the Attribute Editor. This has been corrected.
• Previously, when exporting data with the Matrix Cube Manager with row titles selected,data was exported with the column titles and vice versa. This has been corrected.
• Previously, when having a network with a link where (one of) the node(s) didn't exist, running check database results in a corrupt network (all link related data is removed). This has been corrected.
• Previously, when selecting a screenline, they became invisible when repainting the network again. This has been corrected.
• Removing many combinations is now much faster by introducing a pop-up to skip the undo option.

Import/Export

• Previously, OtOmnitransImport.pmturiMapping did not work. This has been corrected.
• Previously, the Promil export supplied "no load" warnings for all one-way links. This has been corrected.
• Previously, when exporting a sub-network using a defined selection, it could happen that not all links are exported. This has been corrected.

• OmniTRANS now writes temporary files to the TEMP directory. This overcomes a problem previously when these files were being written to directories that had Administrator rights only, and so caused OmniTRANS to fail.

• Previously, copying and moving skims using the OtSkimCube class did not work between variants. This has been corrected.

• Previously, unsignalised junctions could get (randomly) signalised junction output data (such as cycle time). This has been corrected.
• Previously, using the property overCapacityPerLink resulted in an access violation. This has been corrected.
• Previously, when getPath was used several times, it reloaded the network for each run. The network is now reloaded only once which is much faster.
• Previously, when making a multi class assignment with the property selectedCentroids, the total assignment was written to the database. This has been corrected.

Frequently asked questions about OmniTRANS minor versions

 
Below, you will find five questions that we often receive about our OmniTRANS minor versions.

What is the difference between an OmniTRANS minor and major version?
Approximately once a year we release a new major OmniTRANS version (5.1, 6.0, etc.). During the year, we are still supporting the previous major version and therefore we are releasing minor versions which include small fixes and features. These minor versions are released approximately every six weeks.

Can I use my current V6.0 license on a new minor V6.0 release?
Yes, you can simply install OmniTRANS and the software will automatically recognise the license of your previous installed OmniTRANS 6.0 version.   

Can I use different OmniTRANS versions beside each other?
Yes, you can install as many OmniTRANS versions (major and minor) on your computer r as you wish. These versions will not have influence each other. You must of course have a valid licence for each major version.

If I use the latest release in which OtTraffic algorithmic corrections have been made, can I reproduce the results I got in an 'older' release?
Yes, each minor version of OmniTRANS 6.0 is capable of producing the same OtTraffic results as a previous minor V6.0 release, although by default it will use the latest code. To invoke the code of a previous minor version you must set the properties: OtTraffic.modelVersion and OtTraffic.junctionVersion within your jobs accordingly. Ask your model builder, contact us or read the manual how to do this.

Contacting us: Feedback
We are happy to get feedback from our users; suggesting new ideas or reporting problems.

You can share your OmniTRANS experiences by:

• E-mail (techsupport@omnitrans.nl)

• Skype (techsupport.omnitrans)
• Telephone +31 (0)570 666 810