Release OmniTRANS V6.0.10

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

Features

Graphical User Interface

• When working with split screens, the visualised objects are now synchronised. This means that in both screens, the same network objects are visible.

Import/Export

• Introduced an export wizard for the software packages; Geonoise and Promil Spatial.
• Introduced several new properties for the OtArcViewImport and OtArcViewExport:  splitDuplicateLinks, splitLinksNodeTypeItem, mergeSplitLinks, splitDirections and overrideFieldName.

OtTraffic

• The OtTraffic.silent property applies now also for OtTraffic.getPath.

Fixes

Graphical User Interface

• Due to changes in Google Maps, a new API key has been applied to prevent a Google 'warning' pop-up.

• Previously, after applying a value in the Attribute Editor on a box-, polygon- or cordon- selection, the new value did not disappear from the Attribute Editor when making a new selection. This has been fixed.
• Previously, closing a project with a docked matrix cube window resulted in an error. This has been fixed.
• Previously, creating a report based on a "current selection" in split screen mode always returned the current selection of the second window. This has been fixed.
• Previously, editing transit lines could result in errors during the OtTransit assignment. This has been fixed.
• Previously, if an imported image was 'transparent', it would not be displayed and printed properly. This has been corrected.
• Previously, OtMatrixCube.zonalDataFields did not add a zonal datafield. This has been corrected.
• Previously, several types of images used as object icon were not saved consistently when closing the project. This has been fixed.
• Previously, switching templates could result in a changing right or left hand rule. This has been prevented.
• Previously, the Query Window supplied an error when no object is active. This has been fixed.
• Previously, when adding linkpoints on links with transit lines, transit lines could be incorrectly rerouted. This has been fixed.
• Previously, when shortening or extending multiple transit lines at once, some data (e.g. name) was not set properly (used from one of the transit lines). This has been resolved.

Import/Export

• Previously, OtArcViewExport.writeTypesAsNumbers = true still resulted in fields of the data type "string". This has been corrected.

Other

• Previously, immediately re-opening OmniTRANS after closing resulted in an error. This has been corrected.

OtMatrixEstimation

• Reading the property mapScreenlineMatrices did not work properly since OmniTRANS 6.0.8. This has been corrected.

OtSystem

• The properties OtSystem.exeName and OtSystem.exeTitle has not worked since the release of OmniTRANS 6.0. This has been fixed.
• Introduced several new, cpu related, properties for the OtSystem class: cpuVendor, cpuModel , cpuID?, cpuMMX?, cpu3DNOW?, cpuSSE?, cpuSSE2?, cpuMultiThreading? and cpuNumberOfCores.

OtTraffic

• Important: A stochastic assignment (| NORMAL) sometimes did not get all the demand on the network. This has been fixed and will result in new assignment results. A new modelVersion (modelVersion = 9) has been introduced to reproduce older results.
• Important: An issue has been corrected concerning junction modelling used in sub-variant networks when using the left hand rule of road. This will result in new assignment results. A new modelVersion (modelVersion = 9) has been introduced to reproduce older results.
• Important: Previously, when adjusting the calculated cycle time to the maximum allowed cycle time, slow traffic and bus lanes were not taken into account. This could result in a cycle time that still exceeds the maximum allowed cycle time and resulted in an error. This has been fixed. This will result in new assignment results. A new modelVersion (junctionVersion = 21) has been introduced to reproduce older results.
• Previously, an assignment could be made with an odMatrix with fewer centroids than present in the network. This has been corrected. Now, an error will be generated.
• Previously, creating selected link matrices did not remove the temporary files well. This has been fixed.
• Previously, no warning was given when gaps were available in the centroid numbering system of an OtTraffic assignment. This warning has been introduced.
• Previously, OtTraffic did not report the centroid origin when many centroids were unreachable. This has been fixed.
• Previously, setting many links in property routeLinks slowed the assignment. This has been fixed.
• Previously, several OtTraffic properties cannot be used in multi class. This is now possible (e.g. functionType = [1,2,3]).
• Previously, the warning about non-connected centroids was incomplete. This has been corrected.
• Previously, when making an stochastic assignment, the error 'empty OD-Matrix or no linkcosts' could appear at the end (although data was still written). This has been corrected.
• Since OmniTRANS 6.0.8, OtTraffic required administrator rights on the C-root drive, this has been changed such that these rights are not required anymore.

Update

• Previously, when upgrading an OmniTRANS 5.1 project to OmniTRANS 6.0, the stop5_4data1 table received an index file. This resulted in a slower handling of the table (e.g. OtTransit). The index file (stop5_4data1.px) will not be created anymore during the update.