run_verification
Run ProSuite quality verification on geospatial datasets. Define conditions, apply them to a workspace, and get a per-condition error breakdown.
Instructions
Run a ProSuite quality verification.
Build an ad-hoc condition-list specification and run it against the given workspace. The ProSuite service (prosuite-qa-microservice) must be reachable at the host/port configured via PROSUITE_HOST / PROSUITE_PORT environment variables (default: localhost:5151).
Args: model_catalog_path: Workspace path on the server, e.g. 'C:/data/mydb.gdb' or a .sde connection file. model_name: Logical name for the data model (arbitrary, used in generated condition names). datasets: Feature classes or tables to make available for conditions. Each entry has a 'name' (feature class name) and an optional 'filter_expression' (SQL WHERE clause). conditions: Conditions to run. Each entry has: - condition: method name from list_conditions (e.g. 'qa_min_length_0') - params: dict mapping parameter names to values. Dataset parameters take a string matching a name in 'datasets'; primitive parameters take their direct value. output_dir: Optional server-side directory for Issues.gdb and HTML report; the service process must have write access. Omitted, a local runs/ directory is used only when PROSUITE_HOST is local, since the path is resolved on the service's machine. envelope: Optional spatial filter {x_min, y_min, x_max, y_max}. Omit for full-extent verification.
Returns a summary with status, total_errors, and per-condition breakdown. Check 'status': 'error' for connection or parameter failures.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| datasets | Yes | ||
| envelope | No | ||
| conditions | Yes | ||
| model_name | Yes | ||
| output_dir | No | ||
| model_catalog_path | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||