...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Export Hierarchy
There are a number of things to consider that all affect the results that are output from WinCan VX during the export process, and they are almost all handled automatically in the background during the data exchange routine without any user options available to the user.
...
In the HADDMS data files, there is only ever one combined inspection and asset data record of each object, but of course, WinCan VX has the concept of ‘multiple inspections’ and ‘combined inspections’, so how do we decide which inspection to export when there are several to chose from? This is where the Export Hierarchy comes into play, and the selected export order of the one inspection record to be exported (applies to all object types) is like this:
Combined inspection - if a combined inspection record exists on an object then it is exported and no other inspection data is exported for the current asset.
A complete inspection from end to end - this might not be the most recent inspection because maybe there was am abandoned inspection carried out after the complete one, but this does not matter under HADDMS rules - a complete inspection trumps an abandoned inspection regardless of date and time.
An abandoned inspection - the most recent abandoned inspection will be exported. Of course if there was at least one abandoned inspection from each end then there should be a combined inspection, so we are back up this tree to option 1.
The original imported data, untouched, unvalidated, not re-scored and unmodified.
At the end of this export process, every asset has an inspection record exported into the data regardless of whether it was inspected by the contractor during this package of work or not.
...
Creating HADDMS Exports
The files that are produced by the HADDMS export routine are described in the next section, but are essentially only the files required by HADDMS for upload and a .dxf file. The important part about this is that any other deliverables that your client may like to receive have to be created separately from the export routine.
...
Before running the export routine, the user is strongly advised to revisit and evaluate the following checklist in the order given and ensure that all items are 100% satisfied, because failure to do this will almost certainly result in critical rejection errors when the shapefiles are attempted to be uploaded to HADDMS:
Run the ‘Duplicates Finder’ tool on Sections and Nodes from the Edit ribbon (Tools → Misc Tools list before VX v15.2) and resolve issues.
Execute the ‘Delete Empty Inspections’ tool from the Edit ribbon (Tools → Misc Tools list before VX v15.2) list.
Execute the ‘Regenerate Sort order’ tool from the Edit ribbon (Tools → Misc Tools list before VX v15.2) list.
Run the inspection merging tool using the default options as described here.
Run the ‘Calculate Invert Levels’ tool on the project.
Run the ‘Job Checker’ tool from the Edit ribbon (Tools → Misc Tools list before VX v15.2) list and resolve issues.
In WinCan VX v10.3 or lower only, regenerate the section and lateral SUPP_REFs using the tool from the project tab.
Validate the Sections and clear all Errors to zero.
Validate the Laterals and clear all Errors to zero.
Validate the Nodes and clear all Errors to zero.
The first step in the export process is to click on the ‘Export’ button in the ‘Data Exchange’ ribbon:
...
When the process has finished, you maybe presented with some warnings, but provided the final message says that the ‘Process has been finished’, then you are good to go, and clicking on the folder icon to the right will take you straight to the export file folder ([Project Folder] → Misc → Exchange → [Project Name]_Date_Time and the folder containing the export files will be named [Project Name]_DDMS_CD535. Inside here, you will find the export files as described:
...
Export final stage.
...
Auto Nodes
A common question after export is ‘Why has my data now got Auto ghost nodes in it after export?’
...
| Info |
|---|
Notes: When these ‘hidden’ auto nodes are created, they are only created in the shapefile exports and there is no change to the data in the WinCan VX project. The reason for this is that there was only ever one video inspection of this pipe, and the operator simply created an inspection with some codes, as is good an proper. We only create one report in the pdf file for this inspection, there is only one video and there is only one record of the inspection in the project database, and this has to stay this way for our sanity inside the database. Hence, these are the hidden auto nodes that are only in the exported shapefiles. But, if you need to know where they have been created, then use the filtering options to find observation codes SC% MC% and LC% in the inspections in the project. These are the places where the these auto nodes will be created. Furthermore, if you are struggling to diagnose a HADDMS upload error based on these point items and the continuous items that are created as a result of this process, then there is little point in searching through the WinCan VX project to find these nodes, because they simply will not be there. They are only in the shapefiles. You should open the shapefiles directly in WinCan Map without WinCan VX, and start your investigations from there, which then may lead you into the WinCan VX project to fix the problems. Remember - whenever you run the export routine for the final deliverables, a backup is made of the current database inside [Project Folder] → Misc → Backup. We do this because we are modifying the data during the export process and you have no control over this process, so if you are not happy with the results after export, you can roll back your project to the place where it was at when you started the export process if you wish, make some fixes and run the export again. |
...
Data Review After Export
After running a HADDMS export, there will usually be changes that have been made to your project during the export routine. This has been mentioned already here. There will also be a backup made of you’re database files immediately before the export was run, so…
...
If you see a lot of auto ghost nodes after export (double or triple figures), then something is seriously wrong in your project and there is little point even trying to upload these shapefiles to HADDMS.
...
Understanding the Outputs
The HADDMS export routine creates two files for each catchment in the project and this is exactly the reason why it is essential to keep a solid grip on the job data within the WinCan project at all times during data processing and site analysis:
A zipped folder containing all of the HADDMS data files for upload including the inspection photos, shapefiles and observation .dbf file. You can try to upload this file to HADDMS and if the data is good, then it will be approved.
A .dxf file containing the shape geometry of the project including attribute data, but without any significant layer styling. This is not a HADDMS deliverable which is why it is saved outside of the .zip file, but it creates a geometrically correct representation of the data that is being uploaded in a generic layered CAD file from where the user can style and design their own CAD files for delivery to the area client.
...
Uploading to HADDMS
The upload process to HADDMS is not for any real description here, because that is a HADDMS process using their systems and website, but it is worth just noting a few minor points that are maybe a little unclear with their system:
...