ArcGIS Blog

Data Management

ArcGIS Workflow Manager

Edit data offline with ArcGIS Workflow Manager

By Xiaomeng (Meggie) Zheng and Janine Barrett

 

Available with ArcGIS Enterprise 11.2 or later

 

At ArcGIS Enterprise 11.2 and ArcGIS Pro 3.2, ArcGIS Workflow Manager introduced out-of-the-box features to edit layers in disconnected or connectivity-limited environments. With the addition of two new step templates and enhanced capabilities with the Open Pro Project Items and Cleanup steps, editing layers could now be handled seamlessly offline!

To show how data replication and editing can be handled by an organization, we’ll demonstrate how a GIS Analyst for a transportation department manages a transportation data network and works with organization members to re-digitize road geometry after construction using Workflow Manager in ArcGIS Enterprise 11.4 and ArcGIS Pro 3.4.

Don’t have time to read the article? Watch the video instead!

[insert media]

 

What is an offline editing workflow?

In the field, it’s common to experience slow or limited internet connectivity when connecting to the centralized database, performing data edits, or posting re-digitized road data back to the centralized database.

Offline editing capabilities in Workflow Manager enable mobile workers to access the road data from a shared location and edit the road properties with a local copy of the data. Once the mobile workers are back in the office and connected to the internet, the road data can be synchronized with the mobile geodatabase. The updated road data is then evaluated by a data quality reviewer and the changes are pushed to the centralized database once edits are approved.

 

 

Replicate layers to access and edit data offline

 

This scenario represents a typical data editing use case. With offline editing capabilities in ArcGIS Workflow Manager, the organization can improve the scope, scalability, and process of work by coordinating and assigning steps to members while mitigating risks of network failures during data collection and editing.

Let’s take a look at how this works:

 

Data source

In the transportation department, the data is stored in a linear referencing network. All roads, streets, intersections, and bridges, along with pavement types and road centerlines, are stored in a network using relative locations along a measured linear feature.

The GIS Analyst publishes the linear referencing data as a feature service to the transportation department’s ArcGIS Enterprise portal. Before the feature service can be published, the linear referencing feature service must have branch versioning enabled. This is done on the data source section of the feature service’s settings page.

 

 

After the feature service is published, the GIS Analyst updates the Feature Service Advanced Options in ArcGIS Server Manager to allow a new version to be created when the branch versioned data is replicated.

 

Enabling the sync operation allows mobile workers to synchronize edits with the replicated data

 

Location of interest

To allocate tasks assigned to a mobile worker, a location of interest must be defined. The goal of defining a location of interest is to narrow down the extent of where data-editing is performed and minimize the size of the data that a mobile worker would need to download locally.

A location of interest can be defined by opening a map and selecting the geometry based on map layers, or it can be defined with an ArcGIS Arcade expression that returns the location’s geometry with the Define Location step.

 

 

Data replication

The essential part of our diagram creates a replica of the data for the defined area of interest, saves it to a shared directory, and allows the mobile worker to access and edit layers in the field. We’ll use the Create Replica step to create a branch version of the data, which stores it in the form of a mobile geodatabase accessible by ArcGIS Pro.

 

The Create Replica step configured to replicate the LRS data source based on the job's defined location

 

Edit data

Once the data has been replicated and stored locally, the mobile worker can perform data editing in ArcGIS Pro by opening the pre-defined map with the Open Pro Project Items step.

The step is associated with an ArcGIS Pro project package hosted on the transportation department’s Enterprise portal and configured with a two-way synchronization on the Start and Finish tabs of the step. When this option is enabled, changes can be sent to and received from the mobile geodatabase when the project is opened, paused, or completed.

 

The Open Pro Project Items step configured with a hosted project package and configured to sync changes when the project is opened, paused, or completed

 

When the project is opened in ArcGIS Pro, the data source of the road map is repointed to the replica mobile geodatabase created by the Create Replica step. Because Create Replica was configured to replicate specific layers, the map opens in ArcGIS Pro and repoints those layers to the replicated data.

 

The road map project opened in ArcGIS Pro synchronizes edits when the step is paused or completed

 

Once the mobile worker is done editing the road data, data edits can be synchronized with the replica by closing the map and finishing the step.

 

Reconcile and post edits

Once the team has approved the edits made by the mobile worker, changes can be pushed from the replica to the default version with the Reconcile and Post step. This step can be configured to check for specific conflicts and allow the team to resolve those conflicts before posting edits to the default version. Given the reconcile and post process may take some time, we can optionally choose to run this process asynchronously.

Reconciling and posting can only be performed by the replica owner, which in this scenario is the mobile worker who opened and ran the create replica step. As the GIS analyst, we can configure the mobile worker’s credentials using an encrypted user-defined setting to reconcile and post the data on their behalf once data checks have passed.

 

The Reconcile and Post step detects conflicts and posts edits once conditions have been met

 

Cleanup

Finally, after edits have been posted to the default version, we can have Workflow Manager clean up the job data using the Cleanup step. This process deletes the location associated with the job, unregisters the replica with the job, and deletes the replicated version of the data source and the mobile geodatabase stored in our local file path.

 

Clean up job data by removing the job location, unregistering the replica, and deleting replica files from the shared file location

 

A replica-ble workflow

Jokes aside, this process outlines a repeatable workflow that can be used to standardize work across organization members to update a linear referencing network. By leveraging an offline editing workflow, data distribution and assignment to mobile workers becomes scalable, offering the flexibility to make edits and post changes in areas with limited connectivity.

 

Additional resources

If you want to learn more about ArcGIS Workflow Manager, you can check out our Resources for ArcGIS Workflow Manager blog to connect with us and discover everything you can do with Workflow Manager.

To learn more about offline editing capabilities and replication, you can check out the following resources:

Share this article

Subscribe
Notify of
0 Comments
Oldest
Newest
Inline Feedbacks
View all comments