Description

A JSON array of custom operations that the Topographic Production Service runs after the files for a map product have been created.

postProcessing is the extension point for steps that need to act on the finished output—copying, renaming, transforming, or notifying downstream systems—rather than steps that build the map itself.

How it is used

After dataExtraction and operations complete and the output package is written, the service iterates the postProcessing array in order and runs each entry. Each entry is an operation object that follows the same syntax described under operations—typically custom operations (type 1) that wrap a geoprocessing script tool.

Expected values

An array of operation objects. Each entry uses the operation syntax documented in operations. Custom operations (type 1) are the most common choice because they let you run any geoprocessing script tool against the finished product.

Behavior and relationships

  • postProcessing runs after the package described by outputPackage has been produced. Use it to act on the package or its files.
  • postProcessing operations can reference resources (such as [Package]\\OutputPackage or [Job]\\Id) the same way operations entries do.
  • Failures in postProcessing do not invalidate the produced map files, but they are recorded on the job and surface through the following:
    • [Job]\\HasErrors
    • [Job]\\Messages

User considerations

  • Keep postProcessing steps idempotent when possible so jobs can be safely rerun.
  • Use stable GUIDs for each operation's ID so excludedOperations and productVersions.operationOverrides can target them per version.
  • Refer to the map product definitions in the Topographic Mapping product files for working examples of post-processing operations.

Example

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
"postProcessing": [
  {
    "name": "CopyFileToStaging",
    "type": 1,
    "id": "E51092DF-FC78-4D98-AA20-7E0FBD718840",
    "description": "Copies a PDF to the jobs staging directory.",
    "toolName": "CustomCopyTool.atbx",
    "toolBox": "C:\\Data\\Tools\\Custom\\CustomTools.atbx",
    "messageLevel": "info",
    "validation": 0,
    "parameters": [
      {
        "name": "fileName",
        "value": "C:\\Documents\\MyPDFs\\InfoPage.pdf"
      },
      {
        "name": "stagingDirectory",
        "value": "[PACKAGE]\\StagingDirectory"
      }
    ]
  }
]

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.