11.3 Tool & Template Sharing

11.3 Tool & Template Sharing

Beyond sharing data and cartographic layers, enterprise GIS organizations must standardize analytical workflows, automated processing models, page layouts, and overall project architectures. ArcGIS Pro facilitates operational governance and reusability through specialized sharing formats for analytical tools and design templates. Mastering Geoprocessing Packages (.gpkx), Web Tools, Map Files (.mapx), Layout Files (.pagx), and Project Templates (.aptx) ensures consistent GIS outputs and streamlines organizational efficiency.

---

Standardizing Geoprocessing Workflows & Cartographic Assets

Scope note: The Foundation objective in play here is "Determine the appropriate method to share content from ArcGIS Pro" — recognizing that a geoprocessing package, a map file, a layout file, and a project template are each a sharing container, and matching each to a stated need. Authoring the ModelBuilder models and Python toolboxes that go inside a .gpkx, and publishing Web Tools to ArcGIS Enterprise, are Associate and Professional tasks that the EAPF_2025 exam information guide places outside this tier. Read the automation detail below for context, and memorize the file extensions and their purposes.

In a collaborative environment, GIS teams frequently build custom automation tools in ModelBuilder or Python, as well as cartographic layout standards (e.g., standard map borders, corporate logo placements, dynamic legend blocks). Rather than having each analyst build maps or analysis scripts from scratch, ArcGIS Pro enables authors to package these assets into reusable template and execution files.

+-----------------------------------------------------------------------------------------+
|                              ARCGIS PRO ASSET & TOOL SHARING                            |
+------------------------------------+----------------------------------------------------+
|      ANALYTICAL TOOL SHARING       |           TEMPLATE & DESIGN SHARING                |
| - Geoprocessing Package (.gpkx)    | - Map File (.mapx) [Map Definition]                |
| - Web Tool / GP Service (Enterprise)| - Layout File (.pagx) [Cartographic Template]      |
| - Python Toolbox (.pyt)            | - Project Template (.aptx) [Project Blueprint]     |
+------------------------------------+----------------------------------------------------+

---

Geoprocessing Packages (.gpkx): Sharing Custom Analysis Models

A Geoprocessing Package (.gpkx) consolidates one or more custom geoprocessing tools—created in ModelBuilder or written as Python scripts (.py / .pyt)—along with their input sample datasets, execution history, and dependent resource files into a single portable container.

Key Characteristics of .gpkx Containers

• Successful Execution Requirement: Before a geoprocessing tool can be packaged into a .gpkx, it must be executed successfully within ArcGIS Pro. The successful run creates an entry in the History pane, which serves as the baseline for packaging.
• Input Data Consolidation: The packaging engine includes sample input datasets used during the successful test run, allowing recipients to test and run the model immediately upon unpacking.
• Parameter Definitions: Preserves tool parameter types (Inputs, Outputs, Optional parameters, Value Tables, Choice Lists) and environment settings (Workspace, Output Coordinate System, Cell Size).
• Use Cases: Sharing custom analytical tools with team members, distributing training scripts, and archiving audited spatial models.

---

Publishing Web Tools & Geoprocessing Services to ArcGIS Enterprise

For enterprise workflows requiring cloud-based computation, custom ModelBuilder models and Python toolboxes can be published to ArcGIS Enterprise as Web Tools (backed by ArcGIS Server Geoprocessing Services).

Execution Modes: Synchronous vs. Asynchronous

When sharing a Web Tool from ArcGIS Pro, the author must configure the Execution Mode based on expected tool processing duration:

+-----------------------------------------------------------------------------------------+
|                                 WEB TOOL EXECUTION MODES                                |
+----------------------------------+------------------------------------------------------+
|           SYNCHRONOUS            |                     ASYNCHRONOUS                     |
| - Client waits directly for HTTP | - Client submits job & receives Task ID              |
|   response.                      | - Server executes task in background queue.          |
| - Fast execution (< 5-10 secs).  | - Client polls server for completion status.         |
| - Best for simple buffering or   | - Best for heavy spatial analysis, watershed         |
|   attribute calculations.        |   delineation, or massive overlay operations.        |
+----------------------------------+------------------------------------------------------+

• Synchronous Execution: The client application sends a request to the server and waits for the tool to complete before receiving the response. Designed for fast-running tools (typically executing within a few seconds). If a long-running tool is configured as synchronous, web browser client connections will time out.
• Asynchronous Execution: The client submits a job request to the server, immediately receiving a unique Job ID. The server processes the request in a background execution queue while the client periodically polls the server for status updates. Once completed, the server notifies the client and provides download links to the result Feature Set or Raster Layer. Asynchronous execution is mandatory for complex, time-intensive geoprocessing tasks.

---

Map Files (.mapx) and Layout Files (.pagx)

Cartographic design elements can be saved independently of spatial data to create reusable layout and map blueprints:

1. Map Files (.mapx)

A Map File (.mapx) is an exported JSON text document that stores the complete configuration of a single map or 3D scene (layer order, symbology rules, coordinate system, bookmarks, scale ranges) WITHOUT embedding physical spatial data. Importing a .mapx file into another project recreates the map structure, connecting to original data sources if accessible.

2. Layout Files (.pagx)

A Layout File (.pagx) is an exported cartographic page template. It contains map frame elements, page dimensions (e.g., ANSI D, Arch E), legend configurations, north arrows, graphic elements, dynamic text blocks (e.g., System Date, Author, Project Title, Page Numbers), and corporate branding logos.

Importing a .pagx into an ArcGIS Pro project provides a pre-formatted layout page. Users simply link the layout's map frame to their active project map, guaranteeing that all produced PDF/print deliverables strictly adhere to corporate cartographic standards.

---

Project Templates (.aptx): Organizational Workflow Baselines

A Project Template (.aptx) serves as a master blueprint for launching new ArcGIS Pro projects. When users create a new project in ArcGIS Pro, they can select a custom .aptx template instead of the default blank templates.

What is Included in a Project Template?

• Pre-configured Maps and Layouts (.mapx and .pagx configurations).
• Standardized Folder Connections pointing to shared network drives.
• Pre-configured Database Connections (.sde enterprise geodatabase files).
• Custom toolboxes, ModelBuilder workflows, and organization-specific style files (.stylx).
• Default basemaps and custom spatial reference definitions.

---

Summary of ArcGIS Pro Export & Template Extensions

---

Best Practices for Enterprise Asset Sharing & Governance

To maintain high standards across enterprise deployments, GIS administrators should adhere to key governance guidelines:

• Document Item Metadata: Ensure all shared tools, packages, and templates contain complete ISO-compliant metadata, including Title, Summary, Tags, Description, and Use Limitations.
• Assign Unique Layer IDs: When publishing Web Tools or Web Maps from ArcGIS Pro, enable Explicitly assign element IDs in Map Properties to ensure stable REST endpoint references during future map service updates.
• Version Control Tools: Store Python Toolboxes (.pyt) and ModelBuilder source files in version control systems (e.g., Git) alongside published .gpkx packages.