geoai-common
Contains Geospatial AI/ML related code
Developing
- Checkout the code.
- Install uv (if not already installed):
pip install uv. - Set up environment and install dependencies:
scripts/recreate_venv.sh. - Activate environment:
source .venv/bin/activate. This saves you from having to adduv run ...to every command. - Run
pre-commit installto install pre-commit hooks. - Configure your editor for realtime linting:
- For VS Code:
- Set the correct Python environment for the workspace via
ctrl+shift+P>Python: Select Interpreter. - Install the Pylance and Ruff extensions.
- Set the correct Python environment for the workspace via
- For VS Code:
- Make changes.
- Verify linting passes
scripts/lint.sh. - Verify tests pass
scripts/test.sh.- The
--use-real-bedrock-clientcan be used to test against real LLMs.
- The
- Commit and push your changes.
- Note: if using Gitkraken, launch it from the terminal (with
gitkraken) with the correct python environment activated to ensure that it can use the pre-commit hooks.
- Note: if using Gitkraken, launch it from the terminal (with
Contributions
We are happy to take contributions! It is best to get in touch with the maintainers about larger features or design changes before starting the work, as it will make the process of accepting changes smoother.
Contributor License Agreement (CLA)
Everyone who contributes code to E84 Geoai Common will be asked to sign a CLA, which is based off of the Apache CLA.
-
Download a copy of one of the following from the
docs/cladirectory in this repository:- Individual Contributor (You're using your time):
2025_1_29-E84-Geoai-Common-Open-Source-Contributor-Agreement-Individual.pdf - Corporate Contributor (You're using company time):
2025_1_29-E84-Geoai-Common-Open-Source-Contributor-Agreement-Corporate.pdf
- Individual Contributor (You're using your time):
-
Sign the CLA -- either physically on a printout or digitally using appropriate PDF software.
-
Send the signed CLAs to Element 84 via one of the following methods:
- Emailing the document to contracts@element84.com
- Mailing a hardcopy to:
Element 84, 210 N. Lee Street Suite 203 Alexandria, VA 22314, USA.
Metadata
Release files for e84-geoai-common 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| e84_geoai_common-0.0.7.tar.gz | 616.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| e84_geoai_common-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 668.3 kB
Release files / e84_geoai_common-0.0.7.tar.gz
| Download URL | e84_geoai_common-0.0.7.tar.gz |
|---|---|
| Size | 616.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b95cbb4f7c9eebf13985e5765aafe590a574ab06dea497c499bf9b5906ebbdeb
|
|
BLAKE2b-256 checksum How to use checksums |
c2947e34bf273fc1e3d365d159b6e84a59ec62239db486e685da0cc947bb7d12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 26, 2025.
Transparency logRelease files / e84_geoai_common-0.0.7-py3-none-any.whl
| Download URL | e84_geoai_common-0.0.7-py3-none-any.whl |
|---|---|
| Size | 51.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a037e791514b2d5bc4f1b5e479cd26147fc59afd60d00505e96e359afafb079e
|
|
BLAKE2b-256 checksum How to use checksums |
9b659f81beccf51b42c044d792656200d1e42e3eacfbf0132cf23b6b77461fc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 26, 2025.
Transparency log