Select to view content in your preferred language

Lightweight Sync for Read-Only Dynamic Data in ArcGIS Field Maps

123
0
Wednesday
Status: Open
Labels (2)
CharlesGasseAGS
Emerging Contributor

We use ArcGIS Field Maps extensively for field operations. More than 1,000 field workers rely on offline-enabled maps and synchronize data back to our Enterprise Geodatabase. This workflow is critical, but when multiple layers have sync enabled, the process can put significant strain on our GIS infrastructure, and in particular, our underlying database.

 

This Idea serves to highlight challenges we have encountered and propose solutions.

________________________________________

Current Challenge:

  • Sync is essential for editable data, but it is heavy and resource-intensive for read-only layers.
  • Some layers are read-only but highly dynamic, meaning they change frequently and need to be updated in the field.
  • Vector Tile Packages (VTPK) are great for performance, but currently cannot update dynamically in offline areas without a full re-download.

 

We have encountered limitations like [BUG-000165311: Clicking Update in Manage Areas in Field Maps Designer does not update the vector tile layers after using the Replace Layer option in ArcGIS Online.] (https://support.esri.com/en-us/bug/clicking-update-in-manage-areas-in-field-maps-designer-bug-000165...) and we have submitted Enhancement Requests with our Esri distributor, such as [ENH-000179378: Enhance the 'Check for Updates' functionality to update Vector Tile Layers included in downloaded offline map areas without the need to remove the offline area and re-download it.].

________________________________________

Proposed Solution:

Introduce a lightweight sync mechanism for read-only layers in Field Maps. Two possible approaches:

  1. Enhance the “Check for Updates” feature so that Vector Tile Layers in offline map areas can be updated without removing and re-downloading the entire area.
  2. Create a new “read-only sync” process optimized for performance and minimizing database load.

________________________________________

Benefits:

  • Reduced database strain during sync operations.
  • Improved performance for large-scale deployments with many field workers.
  • Better user experience for field staff who need up-to-date reference data without delays.

________________________________________

Why This Matters:

Field Maps is a powerful tool, but as organizations scale, the current sync model becomes a bottleneck and there is significant cost associated with scaling infrastructure. A lighter approach for read-only data would make the platform more efficient and sustainable for enterprise-level operations.

Tags (2)