Seequent Developer Portal • Seequent Community • Seequent website
Evo
Evo is a unified platform for geoscience teams. It enables access, connection, computation, and management of subsurface data. This empowers better decision-making, simplified collaboration, and accelerated innovation. Evo is built on open APIs, allowing developers to build custom integrations and applications. Our open schemas, code examples, and SDK are available for the community to use and extend.
Evo is powered by Seequent, a Bentley organisation.
Geoscience object schemas
Seequent geoscience object schemas define metadata and data serialisation of various geoscience objects. The goals include:
- Facilitate interoperability between various applications and services that produce and consume geoscience data.
- A data interchange specification to facilitate interoperabilities between various industry/segment standards.
For more details on geoscience object schemas, see the geoscience object schema documentation.
Pre-requisites
- Python >= 3.10
Installation
pip install evo-schemas
Contributing
Steps for setting up the development environment can be found in the developer documentation
Thank you for your interest in contributing to Seequent software. Please have a look over our contribution guide.
Code of conduct
We rely on an open, friendly, inclusive environment. To help us ensure this remains possible, please familiarise yourself with our code of conduct.
License
Evo schemas are open source and licensed under the Apache 2.0 license.
Copyright © 2025 Bentley Systems, Incorporated.
Licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
1 maintainer
Metadata
1 maintainer
Release files for evo-schemas 2026.9.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| evo_schemas-2026.9.9-py3-none-any.whl | Python 3 | none | any | Details for evo_schemas-2026.9.9-py3-none-any.whl |
Release files / evo_schemas-2026.9.9-py3-none-any.whl
| Download URL | evo_schemas-2026.9.9-py3-none-any.whl |
|---|---|
| Size | 559.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
abe7d81f9374793556b4e14e37a02fe2456145e187480446f6908c6cd6ee2ee0
|
|
BLAKE2b-256 checksum How to use checksums |
3ee75725119e71fdedd21c9c89d145fcd1c961dec3670a1ca77eb48173e3520e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logSecurity for evo-schemas 2026.9.9
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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for evo_schemas-2026.9.9-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logA 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.
