Setup: Lucity-to-Geodatabase Integration

The Lucity-to-geodatabase integration allows edits made in Lucity Inventory modules to be pushed to the geodatabase. This is a recommended configuration for all agencies as it is required for many Lucity tools to work properly. It can be configured so that edits are not passed to the geodatabase.

Lucity updates the geodatabase

Note: An agency that uses GIS must complete this configuration if it wants to allow Lucity to update the geodatabase.

Process

Inventory Edits

Setup

There are two ways to set up this integration: 1) using a feature service, or 2) using a map service. The suggested method uses a feature service as this is based on ESRI's newer more robust technology.

Complete one of the following configuration processes to establish a default link between Lucity and the geodatabase.

Feature Service

A feature service is usually the primary link between Lucity and the geodatabase. Feature services are map services published through ArcServer that have feature access capabilities enabled. An administrator adds a feature service to the Lucity connection string using the Lucity Administration Tool, which is located under GIS > Connection Strings.

How to configure the feature service

How to point Lucity to a feature service as the default feature service

  

Relevant Settings

Settings that affect this integration are found in Lucity Web, under Admin Portal > Settings > System Settings > GIS Edit Integration section.

 

Optional Setup

Alternate Feature Services

While the integration instructions outlined above create a default link between Lucity and the geodatabase, an agency can also set up alternate links between Lucity and the geodatabase. Doing so allows an agency to divide its feature classes into different feature services.

Using alternate feature services is not necessary; however, feature services are also used to establish edit capabilities in the Webmap and other web-editing platforms. Feature services used for Webmap editing are typically small and contain feature classes from only one set of GIS data (e.g., Storm features). Therefore, multiple editing feature services are required for different types of data.

In such a situation, an agency can reuse its editing feature services as alternate feature services within the geodatabase configuration.

How to configure the editing feature service

How to point Lucity to a feature service as an alternate feature service

In This Section

Disabling the Lucity-Geodatabase Sync