Build repeatable EMDS workflows
Connect data preparation, model tasks, and result review. Start with a working example, then adapt the workflow to your GIS host and installed EMDS release.
Make the analysis steps explicit
EMDS workflow definitions describe tasks, variables, loops, conditions, logging, and error handling. Use them to organize repeated analytical work and make each step easier to inspect.
Start with an example
The workflow gallery includes model chains, conditional processing, retries, and Python post-processing. Configure its task references, data paths, models, and field mappings for your workspace before running it.
Explore workflow examples →Check the destination host
QGIS projects use .qgz or .qgs; ArcGIS Pro projects use .aprx. A shared workflow format does not make the project files interchangeable or guarantee that every task runs unchanged in another host.
Review engine availability, script environments, and release requirements when adapting a workflow between products.
Prepare the evidence your model needs
Choose the spatial units, preserve their identifiers, and map input fields to the measurements expected by your knowledge or decision model.
Use your GIS tools or existing data-processing scripts to prepare those inputs. Confirm units, missing values, and model scales before interpreting an assessment. The Chewaucan guide provides a concrete set of data, models, field mappings, and reference results to explore.
Follow the Chewaucan example →Read workflow variables and return a result
QGIS Python script tasks run a selected script in a separate Python process. Workflow variables arrive as JSON on standard input and in EMDS_WORKFLOW_VARIABLES_JSON. A JSON object on standard output becomes the task result; progress messages written to standard error appear in the execution log.
Save this example as workflow_summary.py, select it in a Python script task, and choose the appropriate interpreter. It reports how many workflow variables it received; it does not run an analytical model.
A nonzero exit code signals a task failure. Install any dependencies your own script needs in its selected Python environment and review scripts before running them.
import json
import sys
variables = json.load(sys.stdin)
if not isinstance(variables, dict):
raise ValueError("Expected a workflow variable object")
print("Workflow variables received", file=sys.stderr)
print(json.dumps({"variable_count": len(variables)}))For engine-level batch integration or a custom connector, contact the team about the contracts and runtime dependencies of your chosen release. This page does not define a standalone connector SDK.
Match the extension to the platform
ArcGIS Pro
Custom add-in work must account for the Pro SDK, EMDS release, analytical engine interfaces, and deployment dependencies. Contact the team to review a proposed .NET integration and its supported contracts.
EMDS Online
The public beta is coming soon. Discuss hosting, authentication, data handling, and integration needs with the team before planning an Online extension.
Begin with the workflow and its requirements
Python script tasks provide a starting point for QGIS automation. Other languages, libraries, and external services require a supported integration for the selected host; the website does not promise ready-to-install R or JavaScript connector packages.
When contacting the team, include your GIS host and version, EMDS package, data formats, model types, expected volume, and whether the workflow must operate offline.
Discuss a developer integration →