Setup: Lucity Spatial Generator

The Lucity Spatial Indexer process is designed to review work order and work request addresses, coordinates, and assets and store the related spatial information in a special table. This data can then be viewed using special Lucity GIS tools.

Configuration

The Lucity Services must be installed.
For Assets to be processed the Edit Map Service URL must be configured in the Administration Tool under GIS > Connection Strings.
Note: All of the feature classes that are linked to lucity should be contained in this service or an Alternate Feature Service that is directly linked to the feature classes in the Geodatabase configuration.
For Addresses to be processed the URL for Geocoding Service must be setup in the 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 control how far back into your work history the Indexer looks 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 anything within the last 180 days.
- Note: The Spatial Indexer is reliant on back end configuration that was added to the program in 7.4. Therefore the Indexer can only process work data that added after you upgraded to 7.4 or above.

Restrictions

This service will not work for clients who have their Lucity databases stored 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 there are records that fail to process. When a spatial change record cannot be processed it is kept in the Spatial Change table (GBAWork.WKSPATIALCHANGE) and marked with an error code. These records are kept in the Spatial Change table for thirty days after they were initially processed. After 30 days they are deleted.

Error Codes

The error codes are found in the SPCH_SU_ERROR.

MissingData	This usually means that there is an issue with the data in WKSPATIALCHANGE like the moduleID is invalid, ParentRecID is invalid, invalid x/y data, etc.
ServiceIssue	This occurs if there isn't a map service associated with the feature class OR if the feature class related to this asset type is not in the service.
NoGeometry	Returned if a geometry was found but it was empty, if the indexer was unable to geocode an address, or if there was an issue with the REST call to retrieve the geometry.
NoLucityRecord	Returned if 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.