...
Page Tree | ||||
---|---|---|---|---|
|
...
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 rules in 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 now 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 ‘Imported Supplier’s Reference’ field descriptions in The Node Header and in The Section/Lateral Header
PLR Suffix field removed.
The PLR Suffix concept is not relevent in HADDMS data and never has been. It is a WRC inspection standard that has no place in HADDMS data and causes problems with data management, so it hasbeen removed. It is now the responsibility of the operator to ensure that they have specified a unique Supplier’s Reference for each asset at all times, and the value will not be edited by the software.
Node Header field name changes to simplify field links between HADDMS shapefiles and WinCan and minor changes made to import and export to ensure good mapping of cover level values.
National Gtid Grid Reference ‘(X)’ field caption changed to Easting [m]
National Grid Reference ‘(Y)’ changed field captionchanged to Northing [m]
Eelevation / Cover Level ‘(Z)’ changed field captionchanged to Cover Level [m]
More information is available at https://cdlabdev.atlassian.net/wiki/spaces/FAQ/pages/1228179243/The+Node+Header#Easting%2C-Northing-and-Cover-Level-(X)%2C-(Y)-%26-(Z)
Not related to WinCan VX, but changes made in this manual:
New ‘Support’ section added to the front cover page of this manual.
References to Highways England changed and/or modified to National Highways throughout this manual.
New chapter Connectivity & Asset Uses added regarding connectivity and asset types.
...
WinCan VX v12.0
Node observation code updates:
Observation codes SC, SCA, SCB, SCH, SCK, SCU removed for nodes, leaving only SCC, SCR and SCZ. Shape change codes are compatibility codes only from WinCan v7, but they have some uses, other than where the shape is inappropriate for the asset type.
Quantification updates for node observations:
All deposits codes and water level codes in nodes have had their quantification parameters changed from % to mm, thickness for attached deposits and depth or width for all others. It is not considered appropriate to measure these observations in nodes by the % method.
Inclination chapter added to this manual
Click here to read the new page. Contains information for site operators and for data processors and managers.
...
WinCan VX v12.1
Node Side View printing option with dimensions:
New printing report added for all UK standards which includes some key dimensions for nodes. Full information is in the new user manual page that has been created here.
...
WinCan VX v13.0
Duplicate Detection on Import:
When importing more than 1 catchment shapefile into a single project, WinCan VX now checks to see if there are duplicate point item SUPP_REFs in the selected shapefile groups.
If duplicates are detected, the user can export a summary list to Excel and the import will not proceed, or they can opt to let WinCan VX fix the data. The software will add ‘_1’ to the end of one of the SUPP_REFs so that there are no duplicates in the WinCan VX database, and will also modify the shapefiles so that the data that is shared to the GIS team also matches the data in the WinCan VX project.
A full description of this feature is available here.
...
WinCan VX v15.0
Multipoint Node Geometry:
This is not a DDMD specific change but a global change across all VX territories and standards. It means that we now store points as 2 points and not just 2 anymore, where 1 point is the centre of the cover and the other point is the centre of the chamber base. This opens up some clever editing opportunities in the application, but they must not be used in DDMS projects dues to the DDMS data model not accepting such data.
...
WinCan VX v15.2
New Edit Ribbon:
There are a number of tools in the VX ribbons that were previously located in the Tools ribbon under the ‘Misc Tools’ button drop down list. All of these tools have now been moved to a wholly new ribbon bar called ‘Edit’. The functions of these tools has not changed.
...
WinCan VX v16.0
Rotate Node Images to North:
In the Edit ribbon, there is now a ‘Nodes North Up’ button which is toggled either on or off. When it is on, all node 2D sketches are rotated to ‘North Up’ where the North direction is specified in the node inspection data. This also follows through into the printed reports.'
...