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.
Pre-requisites
- Python virtual environment with Python 3.10, 3.11, or 3.12
- Git
Installation
pip install evo-data-converters-shp
Shapefiles
A shapefile is a set of files which can contain points, lines, and polygons with associated attributes. At minimum, it consists of a main .shp file, an index .shx file, and a dBASE .dbf file.
Refer to this page for more information: https://desktop.arcgis.com/en/arcmap/latest/manage-data/shapefiles/what-is-a-shapefile.htm or view the technical specification here: https://www.esri.com/content/dam/esrisites/sitecore-archive/Files/Pdfs/library/whitepapers/pdfs/shapefile.pdf
Multipatch Shapefiles
There are multiple shape types which can be used to define a shapefile, though all (non-null) shapes in a given file must be of the same type. Multipatch shapes consist of triangles (defined as 'triangle strips' or 'triangle fans') and rings.
Implementations
The python pyshp package is used to work with shapefiles.
The SHP converter currently only supports importing multipatch shapefiles which do not contain any rings. These are translated to the triangle-mesh schema and published to an Evo workspace. NULL shapes are discarded.
Publish geoscience objects from ESRI Shapefile files
The evo-sdk-common Python library can be used to sign in. After successfully signing in, the user can select an organisation, an Evo hub, and a workspace. Use evo-objects to get an ObjectAPIClient, and evo-data-converters-shp to convert your file.
Have a look at the code-samples/convert-shp-mesh/convert-shp-mesh.ipynb notebook for a complete example of how to publish shapefiles.
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 data converters are open source and licensed under the Apache 2.0 license.
Copyright © 2026 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
Metadata
Release files for evo-data-converters-shp 0.2.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 | Actions |
|---|---|---|---|---|
| evo_data_converters_shp-0.2.0.tar.gz | 14.7 kB | With provenance | Details for evo_data_converters_shp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| evo_data_converters_shp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for evo_data_converters_shp-0.2.0-py3-none-any.whl |
Total release size: 36.2 kB
Release files / evo_data_converters_shp-0.2.0.tar.gz
| Download URL | evo_data_converters_shp-0.2.0.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c3a8332b590f5978999d8148027ae544a65b79df08547c16b5143d1a73b3483
|
|
BLAKE2b-256 checksum How to use checksums |
98b7a0267b7581a651a467393af1a7ee0d1ca6ddf87f5b657276652e5b84ea93
|
| 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 Oct 19, 2026.
Transparency logRelease files / evo_data_converters_shp-0.2.0-py3-none-any.whl
| Download URL | evo_data_converters_shp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 21.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2bd003d6124079b0fcf749195264675263bc0f6600a7403799a29271f3e8351
|
|
BLAKE2b-256 checksum How to use checksums |
72dbb4787d84efcae3605d0a87e1a606a5eeb69df77263d2124336bda5b041c9
|
| 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 Oct 19, 2026.
Transparency logSecurity for evo-data-converters-shp 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for evo_data_converters_shp-0.2.0.tar.gz
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 Oct 19, 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.