Skip to main content
Cartegraph Campus

ArcGIS Integration for Assets

You must have administrator rights to access this feature.

An Asset may have point, linear, or polygon geometry in Cartegraph. When setting up an ArcGIS integration, Asset recordsets can be integrated with an Esri Point, Linear, or Polygon Feature Class as long as it matches the geometry type in Cartegraph.

Two-Way Integration

The integration of Assets with Esri is a two-way integration. Records can be added, edited, and deleted in Cartegraph and Esri with the exception of Cartegraph Locked Value fields. The Cartegraph and Esri environments show the updated records once a sync has occurred.

Cartegraph Locked Values

Cartegraph Locked Value fields are indicated by a lock icon in the Field Associations section. Locked fields in a two-way integration always have the Cartegraph value as the value of record. Any GIS modifications to these associated fields will be overwritten with the Cartegraph value.

Current Inspection Data

Current Inspection data for an Asset is available to be synchronized through the Current Inspection ID lookup in the Field Associations section. Any inspection fields or other Cartegraph Locked Value fields that are synchronized will participate in the one-way sync. The other Asset fields participate in a two-way sync. The inspection data for the Current Inspection is available in the ArcGIS feature. Edits to these inspection fields in ArcGIS are ignored. All edits to one-way sync fields are expected to be made in Cartegraph.

Condition Category fields are also available to be synchronized through the Current Inspection ID lookup. These fields act the same way as the Current Inspection fields and participate in the one-way sync.

Side Effects of Deleting an Asset

We do not recommend deleting assets because if you try to delete an asset from OMS, the system requires you to delete all related tasks for that asset. For example, if Sign A has three related tasks, each with $100 of resources, and I want to delete Sign A, I am saying that $300 was not spent or used. The historical data is needed to prevent skewing individual resource data. Instead, retire the asset to keep the historical data, and then filter out retired records.

If the asset is inaccurate, it is OK to delete it, just delete the asset in OMS first, it would then delete in ArcGIS. If you delete the asset in ArcGIS first, it gets retired in OMS and that could potentially cause issues.