How the Editor Works

The Lucity Editing extension updates Lucity with any edits the user makes in ArcMap or any new features the user adds to related feature classes. The Lucity Editor launches automatically when a user begins an edit session in ArcMap, tracking new features and attribute changes.

When the ArcMap edit session is saved, the tracked changes are synced with the Lucity databases and become permanent. In certain cases, users must use Lucity-provided tools to make edits. These situations include changing Alt ID fields, deleting features, etc.

Rules for Editing

Even with a custom geodatabase configuration, users must follow certain standard business rules to meet Lucity requirements. The Lucity Editing extension must follow the same rules that Lucity follows when adding and editing records. Not all data in the geodatabase must follow these rules; Lucity places no general restrictions on data in the geodatabase. However, only those features that meet Lucity's requirements will propagate to Lucity databases and thereby be accessible in the Lucity Desktop Inventory modules.

Every feature must have a unique text identifier, which is defined as the Feature Class Common Link Field 1 in the custom geodatabase configuration.
- This identifier links the feature to a Lucity asset. Without this identifier, Lucity cannot create a new record or link a feature to an existing record.
- Unless disabled the program will warn you if you have entered a duplicate Common ID.
All required fields in Lucity Inventory modules must be linked to a field in the geodatabase. When creating new features, any required fields must be completed before the feature can be added to Lucity.
- Fields designated as required within the Lucity program are highlighted during the geodatabase configuration.

Important Field Names

Several fields are important to the Lucity sync process. An agency may use different names for these fields, depending on its naming schema and the subject matter .

Alt ID

(Found in Lucity)

The primary user-defined ID field for most modules within Lucity. Alt ID is a required text field that provides each record with a unique identifier.

Also called: Alt ID, Common ID, Common Link, Asset Number

Facility ID

(Found in Geodatabase)

The primary user-defined ID field for feature classes and the ESRI equivalent to Lucity's Alt ID. The Facility ID is used in the ESRI Local Government Information Model schema and in the Lucity GIS data schema.

Also called: Whatever the agency named the field in its custom geodatabase.

Rec #

(Found in Lucity)

The database-assigned ID for every record stored within the Lucity database. The Rec # is automatically generated when the user creates a new record in Lucity. It cannot be changed.

Also called: Lucity Auto ID

Lucity ID

(found in Geodatabase)

The geodatabase field that stores the Rec # for each feature in Lucity. If this field is configured with Lucity, it is automatically populated in the geodatabase when a feature is created and synced to Lucity.

Also called: LucityLink, gbaMSLink, Lucity Auto ID

Editing Process

Startup

An ArcMap edit session begins.
The Lucity Editor extension checks to see:
- that the edit workspace (geodatabase) is linked to Lucity;
- that the geodatabase version being edited is configured to update Lucity; and
- that at least one feature class in the map, within the current edit workspace (geodatabase), is linked to Lucity.
If all three criteria are met, the For this edit session Lucity will be updated upon saving edits prompt appears.
- The Lucity extension then tracks OnChange, OnCreate, and OnDelete editor events.

During Editing

During editing, the Editor extension follows these rules for general attribute edits, new features, and deleted features:


Types of Syncs
New Feature Sync	The new feature's attributes are all pushed into the Lucity database. This includes any fields that were automatically updated in the geodatabase when the Editor extension verified that the new feature would be linked to an existing feature in Lucity. The Lucity Rec# is sent back to the geodatabase to update the LucityID field for the feature.
Existing Feature Sync	All of the new feature's attributes are pushed into the Lucity database, overwriting all linked fields for the related feature. (NULL fields in the geodatabase do NOT overwrite fields that are NOT null in Lucity.)
Delete Feature	The feature is deleted from Lucity because it has already been deleted from ArcMap.

GISEditing

* This step occurs when the ArcMap edit session is saved.

**When a Facility ID is set (for a new feature) or changed (for an existing feature), the following processes run automatically:

The program checks the Facility ID against Lucity. It prompts if the ID is a duplicate.
GIS attributes that are null or empty are updated with Lucity data IF a related record already exists in Lucity.
Spatial relationships are updated. These include:
- hard-coded spatial relationships, like the To/From fields for Sewer, Storm, and Water pipes; and
- user-defined spatial relationships.

Saving

Edit cache is processed
Each edit is synced to Lucity.
- Any Default Values in the Geodatabase Configuration are pushed to Lucity for the assets synced.
- Lucity Auto ID is sent back to the GIS record. (If the field is mapped).
- The Length/Area fields are updated (if the option is enabled).

Special Situations

General Editing

If the Facility ID = 0, the Editor extension ignores the feature. It does not sync it to Lucity.
If the shape/position of a feature is changed:
- the spatial relationships are updated;
- the X/Y fields in Lucity are updated; and
- the Length and Area fields are updated for feature classes that are configured to be updated.

Transportation Modules

If the Intersection Lock is enabled on the intersection record., the Street Names and the Intersection diagram are automatically updated.
Editing a Street Segment updates the Segments tab on all related structures in the Structures module.
Editing Street Segments updates the To and From Street Name fields for related Street records.
If the record is not locked, the Total Pavement Area in Lucity is updated.
If Lucity field XX_SN_ID exists and is populated, the Street fields are updated.
The MUTCD field is updated in ArcMap.
Creating or editing Street Segments automatically creates or edits the related Street Subsegment(s).

Trees

The Tree Code fields in ArcMap are updated.

Built-in Spatial Relationships

Address/Parcel - The Address/Parcel relationship is automatically managed by Lucity.
Facility - The Endpoint relationships for Irrigation Pipes are managed by Lucity.
Facility - The relationship between a Room and a Facility is automatically calculated based on Floor the Room is attached to.
Park - The Endpoint relationships for Irrigation Pipes are managed by Lucity.
Sewer - The Endpoint relationships for Sewer Pipes are managed by Lucity.
Storm - The Endpoint relationships for Storm Pipes are managed by Lucity.
Streets - Editing a Street Segment updates the To and From Node IDs.
Water - The Endpoint relationships for Water Pipes are managed by Lucity.

Editing Settings

Settings that control how some of the edit tools work are located in the Lucity Administration Tool under System > Settings > GIS Desktop.