Dira ProSuite Python Client
Functionality
The Dira ProSuite Python Client is the Python API for the ProSuite Quality Verification Server. ProSuite is a suite of high-end productivity tools for ArcGIS for data production, quality assurance, and cartographic refinement.
The ProSuite Python Client API is a lightweight package that provides access to the ProSuite QA functionality. It has been specifically designed as an easy-to-use programming interface that supports intellisense and comes with a documentation and samples. Quality specifications containing QA tests for geodata can be fully defined in Python and executed on a ProSuite server which runs either locally or on a remote machine. Alternatively, an existing XML specification or a specification stored in the configuration database (data dictionary) can be executed with just a few lines of code.
Find out more about ProSuite at Dira GeoSystems.
Installation
pip install prosuite
Alternatively, if you have a wheel file (e.g. prosuite-1.0.3-py3-none-any.whl), install it directly:
pip install prosuite-1.0.3-py3-none-any.whl
Connecting to the QA microservice
Service needs a host and port. To take them from the standard channel configuration
(prosuite.microservice.qa.client.config.yml, looked up in the documented locations, falling back to
localhost:5151) use QAMicroserviceClient, which will also start a local server if the configuration names
localhost and nothing is serving there yet:
import prosuite
with prosuite.QAMicroserviceClient.from_config_file() as client:
service = prosuite.Service(client.host_name, client.port, client.credentials)
for response in service.verify(specification=spec, output_dir=out_dir):
print(response.message)
Leaving the with block stops the server only if this client started it, so a server you were already
running is never taken down. If the server should outlive the script - as it must inside ArcGIS Pro, where the
next tool run would otherwise pay process startup again - call it without the context manager:
client = prosuite.QAMicroserviceClient.from_config_file()
client.allow_starting_local_server()
service = prosuite.Service(client.host_name, client.port, client.credentials)
Service itself is unchanged and can still be constructed with an explicit host and port.
Documentation
See ProSuite Python.
1 maintainer
Metadata
1 maintainer
Release files for prosuite 1.7.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| prosuite-1.7.1.0.tar.gz | 135.4 kB | Without provenance | Details |
Release files / prosuite-1.7.1.0.tar.gz
| Download URL | prosuite-1.7.1.0.tar.gz |
|---|---|
| Size | 135.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2322b4e83460c2cf7beecb1dca7ee85e552673b4afb94fcc4af1c87ca37bebd
|
|
BLAKE2b-256 checksum How to use checksums |
28f4df39de24f56c71331e23b13941c3dc43ca39fda8b3660223cd26199bf15c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.7
|
Security for prosuite 1.7.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
