...

...

Change Log

This page contains information regarding data entry fixes and updates between WinCan VX release versions. These do not include bug fixes or feature developments, only fixes to captions and list items as required to either remove conflicting information or as a result of updates to the standard.

...

• Import/Export mapping editor tool improvements.

  • Various improvements including conversion mappings as described in this section - https://cdlabdev.atlassian.net/wiki/spaces/FAQ/pages/1201569849/Importing+External+Data#WinCan-VX-v11-Update

• Simplification of the continuous asset dimension fields.

  • The asset dimension fields have been reduced from 5 to 3 and now have a direct one-to-one mapping with the relevent shapefile fields.

  • Before v11.0:

  • 

    v11.0 onwards:

  • 

    There are a number of rulesin HADDMS concerning when each of these fields is valid and when they are not based on other criteria in the data including the asset type. Previously, VX was manipulating these values automatically in the background and the result was that sometimes after export, the data was in the wrong fields in the shapefile.

  • This background manipulation has been removed and the transfer of data is no clear and direct between the WinCan database fields and the shapefile fields.

  • The contractor should understand from the HADDMS documentation when and how to use these fields appropriately.

  • The WinCan VX validation files and import mapping files have been modified to match this change.

  • Please use the tip text in WinCan VX that appears when you hover over the field caption.

  • See also additional information here - The Section/Lateral Header - Service & Support - Confluence (atlassian.net)

• New features added to the ‘Import from GIS’ tool as described https://cdlabdev.atlassian.net/wiki/spaces/FAQ/pages/1201569843/WinCan+VX+Project+Setup#Update-in-WinCan-VX-v11.0

• Imported reference fields added to the node and section headers for error checking.

  • See additional information in the two ‘Imported’ ‘Importd Supplier’s Reference’ field descriptions in The Node Header and in The Section/Lateral Header

...