Custom Geodatabases - Synchronizer Setup

This Geodatabase Synchronization Setup tool can be used for the following:

• Add/Remove feature class(es) to be synchronized with the desktop.
• Add/Remove feature class fields to be synchronized with the desktop.
• Setting up spatial relationships for feature classes.
• Setting up auto-numbering fields for feature classes.
• Indicating which geodatabase versions should update the desktop.
• Validating the geodatabase synchronization setup.

1. To open the tool, there is a shortcut in the ArcCatalog toolbar (pictured below), or this tool can be found at [local]\Lucity\GIS\GGCstDB.exe.

   

2. A login is required; this is the same login as the desktop user name and password.
3. After you login, the Geodatabase Synchronization Setup form will load (example below).  

   This is way the form will look like when populated with the standard Lucity geodatabase settings.

   

4. The tree on the left hand side of the form is the list of feature classes that are currently set up to synchronize with the desktop.  To view the settings for an individual feature class, select the feature class from the tree at the left and the settings will be displayed.

   

5. The fields defined in the upper right side of the form define how the feature class links to a Lucity module.
6. For information on the toolbar buttons and the fields on this form, consult the Custom Geodatabase Fields and Tools topic.

Notes: See Spatial Relationships for information on how to set up the system to automatically update these fields.  If the spatial relationships function is not used, the user will be responsible for keeping these values current.

The Sewer Pump Station Inventory, Storm Pump Station Inventory, and Detention Basin Inventory modules may be maintained automatically if the option in Sewer Editing options is checked.  See Sewer Editing Options or Storm Editing Options for more information.

For these three feature classes, you must maintain two additional fields: One character field that stores the structure number, and one ID field that stores the structure ID.  These fields should be mapped to the Feature Class Parent Common ID Link Field and Feature Class Parent Link field, respectively.  The field entered for the Feature Class Parent Link  field must be mapped to the associated field in the grid as well.  For sewer pump stations this is the SN_MHID field; for storm pump stations this is the PN_SN_ID; for storm detention basins this is DN_SN_ID.