...
| Page Tree | ||||
|---|---|---|---|---|
|
...
Inspection Merging
...
There is very little to say bout the technique for successful project merging with HADDMS data that is any different from that for non HADDMS data, and this process is described in detail in a WinCan Confluence page outside of this HADDMS manual here - Project Merging.
| Warning |
|---|
Do not go any further through this guide until you have first referred to the Project Merging page. |
Good project merging requires a detailed and clear approach and is usually best done by office processors with an in-depth knowledge of what looks good and what looks bad in this type of data.
The vitally important parts to the project merging process are:
Validate the data and clear all Errors in all projects that are going to be merged.
Resolve duplicates on sections, laterals and nodes in all projects that are going to be merged.
Run the WinCan VX Project Merger as described in the linked page.
Validate the data in the merged result project.
Resolve duplicates on sections, laterals and nodes in the merged result project.
If after this process the data does not appear to be as it you might expect, then stop processing the data any further and roll back the project as described and review the settings. There is no point in carrying any errors introduced by the merging process to further developments in the project.
There are some cases where slightly modifying these settings can give a better result and by rolling back the required databases you can try to merge again to see how the new merged result looks:
...
8.
...
In the Section tab, ensure the Section options are set to ‘Differential' merging:
...
9.
...
In the Node tab, ensure the Node options are set to ‘Differential' merging:
...
10.
In the Lateral tab, ensure the Lateral options are set to ‘Differential' merging:
...
HADDMS requires that only one inspection of an asset is ever included in the final delivery data to the system.
WinCan VX allows users to create multiple inspections of assets, so there needs to be some controls in place to ensure that the correct inspection is used at the point of export to shapefile.
One special case exists where there is at least one abandoned inspection from each end of a continuous item. In this case, we need to combine the two inspections into a single inspection in a downstream direction.
There are a number of additional controls and rules around this concept, but they are all covered internally by the software without user input, and there is a full description of the inspection merging tool available outside of this manual here - Inspection Merging - Service & Support - Confluence (atlassian.net)
...