With version 2014r2, Lucity added functionality that greatly expands its GIS integration capabilities with the use of feature services. No longer are you bound to an Esri® ArcMap edit session for synchronizing geodatabase edits to Lucity. Edits to a feature service, regardless of who did it and what environment they did it in, can now be automatically synchronized with Lucity.
You can publish your GIS data linked to Lucity as a feature service and then deploy that feature service to:
- Collector for ArcGIS (iOS & Android)- including disconnected editing
- Lucity Web Map
- Lucity Mobile (coming soon for Android and iOS)
- ArcGIS.com map viewer
- Trimble® Positions™
- Any other 3rd party app that supports feature service editing. A list of possibilities can be found here.
Edits made to the feature service in any of these environments then have the ability to be synchronized with Lucity automatically. For example, you could have crews in the field creating new asset or inspection data using Esri’s Collector for ArcGIS app and in near real-time their changes will be reflected in the Lucity database back in the office.
Here are more details on how to set this up for your agency:
Before I discuss how a feature service can be configured in Lucity, some may be asking “What is a feature service?” A feature service is simply a map service that has feature access capabilities enabled. More information on feature services can be found here and Esri-hosted feature services can be found here.
Then under Feature Access you will need to set the desired edit operations that users will be allowed to perform: Create, Delete, Query, and Update. In addition, with version 10.2.2+, you can enable the Sync operation to support offline use including disconnected editing.
Once the service has been published you are ready to have it configured with Lucity. The first step in configuring the synchronization between Lucity and a feature service is to add a record for the service in Map Services and link it to the associated feature classes.
After the service has been defined in Map Services and associated to the applicable feature class(es) you are ready to setup a Lucity GIS Scheduled Task. These tasks are defined in the Lucity Geodatabase Configuration tool within ArcCatalog.
The Scheduled Task contains various options used with synchronization between Lucity and the feature service.
Task Type. This indicates the type of synchronization. Lucity to GIS– is only available for inspection modules and will push data from Lucity into your inspection feature class. The GIS to Lucity option is available for all modules and will update Lucity with the edits made to the feature class.
Filter Options. This can be used if you wish to limit the records that should be processed based upon set criteria.
Only process records modified since last run. It is strongly recommended this option be used for GIS to Lucity tasks. This will greatly improve processing times as only features that have been edited since the previous synchronization are processed. If you check this option then you need to specify the field in the feature class that stores the last edited date. This would typically be Esri’s Editor Tracking field.
Insert record if it doesn’t already exist. Leave this unchecked to prevent new records from being created in Lucity.
Update existing record. Leave this unchecked if you want to prevent existing records from being updated.
Scheduling Info. This is used to indicate how often this scheduled task should be performed. The highest frequency available is once a minute. Every situation is different and each task can have its own frequency, you may have the need for some tasks to run every minute, others once a day, any maybe some just once a month or even a year.
Once the scheduled task has been defined you are done with the feature service configuration with Lucity. Based upon the frequency you defined for your scheduled tasks, Lucity will start being updated with the changes made to the feature service.
More detailed information on each of these settings can be found here. Please leave a comment below if you have any questions or suggestions.