...
Back to WinCan VX DDMS User Guide
...
| Page Tree | ||||
|---|---|---|---|---|
|
Page Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Project Merging for HADDMS in WinCan VX
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 requiress 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:  |
...
Post Merge Cleanup
After project merging, please immediately take a moment to check out your catchment info in the Job Grid in the project tab in your WinCan VX project before goinga any further:
...
In this project, there are now 4 catchments (jobs), where as before the merge there were only 2. This is because the catchments were duplicated in each of the projects used in the merge. You will see that:
Catchment ID ‘Catch1’ has a new sister Catchment ID ‘Catch13879ede5’
Catchment ID ‘Catch2’ has a new sister Catchment ID ‘Catch2.1’
The new catchment IDs with the additional characters on the end have been created by the system to ensure that data from the individual projects can still be identified and filtered if necessary in the merged project.
To clean this up:
Select the newly created sister Catchment ID.
Click on the delete button.
You will be presented with a pop up which has 2 options - delete the job and merge the job. DO NOT select the ‘delete’ option. Select the merge option (is selected by default) and then select the catchment (job) that you wish to merge the sister catchment into and click Ok. DO NOT try to delete the original ‘proper’ catchment.
Repeat 1 - 3 for each other pair of doubled up catchments in the project.
...