Merge Storm Conduits

The Storm Merge tool is used to merge two Storm Conduits within both the map and the Lucity database. The tool also enables users to delete the associated Storm Structure from the map and from the Lucity database.

The Storm Merge tool is enabled only when: 1) two features are selected in the map; 2) both are linear; and 3) they are snapped together at one end.

How To Merge Two Features in the Map

1. Start an edit session in ArcMap.
2. Select two adjacent Storm conduits in the map either by dragging a box around them or by clicking on one conduit and then holding down the SHIFT key while clicking on the second conduit.
3. Click the Storm Merge tool on the Lucity GIS Edit toolbar.

   

4. The tool requires the system to save edits before and after performing the merge. When prompted to confirm the save (examples below), click Yes.

   

   

5. The Storm Merge form appears: The three sections at the top of the form display information about the two Pipes being merged and the related Storm Structure.

   

6. In the top-center box (Existing Split Feature), choose how you want the system to handle the storm structure following the merge:
   • Don't Delete Feature: Retains the structure in both the Desktop Inventory module and in the structure feature class.
   • Delete Feature From GIS Only: Retains the Structure in the Desktop Inventory module, but removes it from the structure feature class.
     Note: This option is disabled if the tool cannot locate a Structure within one map unit of the common End Point for the two Pipes or if the structure feature class is not editable.
   • Delete from GIS and Lucity: Removes the Structure from both the Desktop Inventory module and the structure feature class.
     Note: This option is disabled if the tool cannot locate a Structure within one map unit of the common End Point for the two Pipes, the structure feature class is not editable, or the Structure doesn't exist in the Desktop Inventory module.
   • Structure Status: If the Structure is to be retained in the Desktop Inventory, select a Status. This will set the Status for the archived conduit.
7. In the New Alt Pipe ID (Optional) section, choose whether to:
   • Manually enter a New Alt Pipe ID,
   • Use the Lucity Auto Number function (enabled only when an Alt Pipe ID field in the feature class uses a number-generator),
   • Use the End Point IDs, or
   • Use the Existing Longer Pipe ID.

     Note: The New Alt Pipe ID cannot be the same as one of the existing Alt Pipe IDs.

8. In the New Pipe Length section, choose how the system should treat any difference in the Pipe Length between Lucity and GIS (enabled only when such a difference exists):
   • Set Lucity Length = GIS Length or
   • Use Lucity-Calculated Length
9. In the New Pipe Attributes section, indicate whether the system should copy the new Pipe’s attributes from:
   • the Existing From Pipe,
   • the Longer Pipe, or
   • the Existing To Pipe.
10. To retain the pre-merge records for both Pipes in Lucity Desktop’s Pipe Inventory (optional), enable the Archive Pre-merged Pipes option and set a Status for the pre-merge (To and From) Pipes.
    • Archived Pipes cannot be shown in the map.
    • Users cannot create Requests, Work Orders or PM/Work Templates for the archived Pipes.
11. To override the settings that control which Lucity modules are associated with the new Pipe, click the Advanced Settings button.
    • Modules associated by default when deleting (not archiving) Pipes:
      • Inspections
      • Overflows
      • Requests
      • Work Orders
      • PM/Work Templates
    • Modules associated by default when archiving Pipes:
      • PM/Work Templates

    

12. Click OK. The following message appears when the merge is complete.