Skip to main content
Cartegraph Campus

ArcGIS Integration for Tasks

A Task may have point, linear, or polygon geometry in Cartegraph. When setting up ArcGIS integration, the Tasks recordset can be integrated with an Esri Point Feature Class.

The GIS Shape field is always saved as point. 

  • Points are saved with current point data.
  • Lines are converted to points based on the midpoint of the line. If that point is in a gap on a multi-part line, it returns whichever vertex is closest on either side of the gap.
  • Polygons are converted to points based on the polygon centroid. If that point does not fall within the polygon, it returns whichever vertex is closest on either side of the center point.

All Task data is represented as points in ArcGIS. We recommend creating a text field in the Task Point feature class with the field name Carte_Geometry_Type. When this field exists, the integration automatically populates the field with the type of geometry that exists in Cartegraph. The only values allowed are Point, Linear, and Polygon.

Option for Full Linear and Polygon Geometry

In order to use this option, create two feature classes in Esri, Linear Geometry, and Polygon Geometry. Each feature class contains a field to hold the Task ID and holds the true geometry of the task. Other fields can be added to the feature class but Cartegraph only keeps these two pieces of data in sync. Cartegraph requires that these feature classes are in the same Feature Service as the Tasks Point Feature Class.

One-Way Integration

The entire Task feature class is one way. The integration of Tasks with Esri is a one-way integration, from Cartegraph to Esri. All additions, edits, and deletions in Cartegraph push to Esri. Any changes in Esri are overwritten by what is in the Cartegraph system on a nightly basis.

Filtering

Cartegraph allows for the user to filter which task records are integrated with Esri. Setting up the filter allows for a smaller subset of the task records to be integrated. For example, all Tasks where the start date falls within a specific date range or only integrating Tasks for a specific Asset Type. Once a task falls out of the filter range it is removed from Esri when either the task is updated or a background sync is performed.

Projected Tasks

Tasks with a Projected status are also pushed to ArcGIS in the one-way integration.

The CartegraphWorkFeatures Feature dataset creates three feature classes: Tasks_Point, Tasks_Linear, and Tasks_Poly.

The fields in each feature class are listed below:

Tasks_Point

  • OBJECTID
  • Task ID
  • created_user
  • created_date
  • last_edited_user
  • last_edited_date
  • Activity
  • Actual Start Date
  • Actual Stop Date
  • Cartegraph Geometry Type
  • Asset Type
  • Asset ID
  • Department
  • Due Date
  • Equipment Cost
  • FEMA
  • Labor Cost
  • Labor Hours
  • Material Cost
  • Notes
  • Other Cost
  • Priority
  • Request
  • Status
  • Total Cost
  • Work Order
  • Address Number
  • Street
  • Intersecting Street
  • Location Description
  • City
  • State
  • Zip Code
  • SHAPE

Tasks_Linear

  • OBJECTID
  • Task ID
  • created_user
  • created_date
  • last_edited_user
  • last_edited_date
  • SHAPESHAPE.STLength()

Tasks_Poly

  • OBJECTID
  • Task ID
  • created_user
  • created_date
  • last_edited_user
  • last_edited_date
  • SHAPE
  • SHAPE.STArea()
  • SHAPE.STLength()

Field Mappings Automatically Loaded

Cartegraph allows for the field mappings for a task to automatically load during the creation of the Task Association. When a Task Association is created, Cartegraph automatically populates field mappings by checking if the Field ID matches the Field Name value setup with GIS. Letter case is ignored when performing this check. This auto-population happens for standard and custom Task fields.

NOTE: ArcMap is required to implement the XML. For more information contact Cartegraph Technical Support at 800-647-3050.

 

  • Was this article helpful?