Mesa-Geo: GIS Extension for Mesa Agent-Based Modeling
| CI/CD | |
| Package | |
| Meta | |
| Chat |
Mesa-Geo implements a GeoSpace that can host GIS-based GeoAgents, which are like normal Agents, except they have a geometry attribute that is a Shapely object and a crs attribute for its Coordinate Reference System. You can use Shapely directly to create arbitrary geometries, but in most cases you will want to import your geometries from a file. Mesa-Geo allows you to create GeoAgents from any vector data file (e.g. shapefiles), valid GeoJSON objects or a GeoPandas GeoDataFrame.
Using Mesa-Geo
To install Mesa-Geo, run:
pip install -U mesa-geo
Mesa-Geo pre-releases can be installed with:
pip install -U --pre mesa-geo
You can also use pip to install the GitHub version:
pip install -U -e git+https://github.com/mesa/mesa-geo.git#egg=mesa-geo
Or any other (development) branch on this repo or your own fork:
pip install -U -e git+https://github.com/YOUR_FORK/mesa-geo@YOUR_BRANCH#egg=mesa-geo
Take a look at the examples repository for sample models demonstrating Mesa-Geo features.
For more help on using Mesa-Geo, check out the following resources:
Contributing to Mesa-Geo
Want to join the team or just curious about what is happening with Mesa & Mesa-Geo? You can...
- Join our Matrix chat room in which questions, issues, and ideas can be (informally) discussed.
- Come to a monthly dev session (you can find dev session times, agendas and notes at Mesa discussions.
- Just check out the code at GitHub.
If you run into an issue, please file a ticket for us to discuss. If possible, follow up with a pull request.
If you would like to add a feature, please reach out via ticket or join a dev session (see Mesa discussions). A feature is most likely to be added if you build it!
Don't forget to check out the Contributors guide.
Citing Mesa-Geo
To cite Mesa-Geo in your publication, you can click the "Cite this repository" button in the right sidebar of the repository landing page, and choose either the APA or BibTeX citation format.
Metadata
Release files for Mesa-Geo 0.9.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mesa_geo-0.9.3.tar.gz | 76.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mesa_geo-0.9.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 109.9 kB
Release files / mesa_geo-0.9.3.tar.gz
| Download URL | mesa_geo-0.9.3.tar.gz |
|---|---|
| Size | 76.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c2402b3ebfd7ff99040fa3ee808e0aeb66c47cedcd5ae32882d05af8b82b6f7
|
|
BLAKE2b-256 checksum How to use checksums |
7addbae7e05b4f9710ce85bcdb21a83ef2bbf0ac297f1538eb1974de8810817b
|
| 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 Feb 17, 2026.
Transparency logRelease files / mesa_geo-0.9.3-py3-none-any.whl
| Download URL | mesa_geo-0.9.3-py3-none-any.whl |
|---|---|
| Size | 33.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ca43c842f962319b76eaf8473e99fedc9e06fcafbff6ad6e54762f8c2bcc190
|
|
BLAKE2b-256 checksum How to use checksums |
b6c83cab18145e13f28cba14c398875f83ad9010877a85f2ade91ffa809b6ddf
|
| 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 Feb 17, 2026.
Transparency log