The Lucity GIS integration is designed to pass information back and forth between the Lucity System/Databases and a GIS system/geodatabase. The integration is made up of multiple parts. Different parts of the integration are used depending on how users have configured the system and what is being done.
The diagram below displays all of the components and how data is passed through each part of the integration.
Note: It is important to understand that everything within the integration is governed by the Geodatabase configuration. The geodatabase configuration is what tells the integration which feature classes are linked to which modules and which fields are linked.
Lucity Desktop, Web, or Mobile > Geodatabase
Inventory Edits
Edits from the Lucity Interface are pushed directly into the Lucity Database.
During the push the program checks the Lucity Settings to see how it should connect to the geodatabase.
If it is configured to use the Lucity SOE it will connect to the map service. The Lucity SOE enabled on the map service will then push updates to the geodatabase.
If it is configured to use a Feature Service it will push updates into the feature service, which automatically updates the geodatabase.
Inspections
Edits from the Lucity interface are pushed directly into the Lucity Database.
Inspections are not automatically pushed to the geodatabase, they are pushed to the geodatabase using a GIS Task.
The GIS Task runs on a schedule. It checks the Lucity Database for new records or updated records and pushes them into a Feature Service, which automatically updates the geodatabase.
ArcMap > Lucity Database
Inventory
Edits in an ArcMap edit session with the Lucity Editor enabled are pushed directly into the Geodatabase and into the Lucity Database.
Inspections
Inspections can be created in ArcMap two different ways.
The first way is to use the Lucity Relationship tool to create an inspection. This creates an inspection directly in the lucity database, but has no presence in the map.
The second way is to create a record in an inspection feature class. These records are automatically saved in the geodatabase but are pushed to Lucity using a GIS Task.
The GIS Task runs on a schedule. It checks the Feature Service for new/updated records, which are then processed and pushed into the Lucity database.
Webmap > Lucity Database
Inventory Edits
Edits in the webmap are made to a Feature Service which automatically updates the geodatabase. These edits are not automatically pushed to Lucity but are pushed to the Lucity Database using a GIS Task.
The GIS Task runs on a schedule. It checks the Feature Service for new/updated records, which are then processed and pushed into the Lucity database.
Inspections
Inspections can be created in the Webmap two different ways.
The first way is to use the Create Inspection tool to create an inspection. This creates an inspection directly in the lucity database, but has no presence in the map.
The second way is to create a record in an inspection feature class. These records are automatically saved in the geodatabase but are pushed to Lucity using a GIS Task.
The GIS Task runs on a schedule. It checks the Feature Service for new/updated records, which are then processed and pushed into the Lucity database.
