Lucity Spatial Indexer

The Lucity Spatial Indexer reviews addresses, coordinates, and assets on Work Orders and Work Requests and stores the related spatial information in a special table. This data can then be viewed using special Lucity GIS tools.

Configuration

Lucity Services must be installed.
To process Assets, the Edit Map Service URL must be configured in the Lucity Administration Tool (under GIS > Connection Strings).
Note: All of the feature classes that are linked to Lucity should be contained in this service or in an alternate feature service that is directly linked to the feature classes in the geodatabase configuration.
To process Addresses, the URL for Geocoding Service must be set up in the Lucity Administration Tool (under System > Settings > GIS Web tab).
The Enable Lucity Spatial setting must be enabled in the Administration Tool (under System > Settings > General tab).
Use the Max amount of days to process spatial history setting to determine how far back into your work history the Indexer should look for records to process. This setting is found in the Administration Tool under System > Settings > General tab.
- Example: If you enter 180 in this field, the Indexer will process all Work Orders/Requests from today and all those within the last 180 days.
  Note: The Spatial Indexer relies on back-end tables that were added to the program in version 7.4 and have been populated since. Therefore, the Indexer can only process Work data added after an agency upgraded to version 7.4 or greater.

Restrictions

The Lucity Spatial Indexer will not work for clients who store the Lucity databases in Microsoft Access or SQL Server 2005 or earlier.
Oracle clients must have the MDSYS.SDO_GEOMETRY data type enabled.

Process

process

Records That Fail To Process

Sometimes, certain records fail to process. When a Spatial Change record cannot be processed, it is kept in the Spatial Change table (GBAWork.WKSPATIALCHANGE) and tagged with an error code. Failed records are kept in the Spatial Change table for 30 days after they were processed, and then they are deleted.

Error Codes

Error codes appear in the GBAWork.WKSPATIALCHANGE.SPCH_SU_ERROR field.

MissingData	Usually indicates that there is an issue with the record in the WKSPATIALCHANGE table; for example, the moduleID is invalid, the ParentRecID is invalid, or there is invalid x/y data, etc.
ServiceIssue	Denotes that: no map service is associated with the feature class; or the feature class related to this asset type is not in the service.
NoGeometry	Signifies that: a geometry was found but it was empty; the Indexer was unable to geocode an address; or there was an issue with the REST call to retrieve the geometry.
NoLucityRecord	Indicates that the associated record no longer exists in Lucity.

How To Process Records That Have Failed

In the WKSPATIALCHANGE table, find the record that failed.
Review the error code for the record and resolve the problem.
Delete the contents of the SPCH_GUID field for that record.
The next time the Indexer checks the WKSPATIALCHANGE table, it will attempt to process the record again.