TU Delft SUMO Wrapper
A research-oriented wrapper for SUMO[1] in python, developed for the DAIMoND lab at the Technische Universiteit Delft (TUD), the Netherlands. The full documentation & examples can be found at tud-sumo.github.io/docs/. Example code can be found at github.com/DAIMoNDLab/tud-sumo-examples.
Requirements
Python 3.10 or later is required. Dependencies are; tqdm, matplotlib, mpl-tools, shapely, requests, moviepy, sumolib, scipy and traci.
Using TUD-SUMO
TUD-SUMO is developed in the DAIMoND lab of TU Delft. For any questions or feedback, please contact Callum Evans at c.evans@tudelft.nl. Bug reports can be created in the GitHub repository: github.com/DAIMoNDLab/tud-sumo.
If you decide to use TUD-SUMO in your projects, please cite our SoftwareX publication using:
@misc{evans_tud_sumo_2026,
title = {TUD-SUMO: A Research-oriented SUMO Wrapper for Traffic Simulation in Python},
author = {Evans, Callum Done and Rinaldi, Marco and Taale, Henk and Hoogendoorn, Serge},
journal = {SoftwareX},
volume = {34},
pages = {102745},
year = {2026},
issn = {2352-7110},
doi = {https://doi.org/10.1016/j.softx.2026.102745},
url = {https://www.sciencedirect.com/science/article/pii/S2352711026002372},
publisher={Elsevier},
keywords = {Adaptive Traffic Control, Python, SUMO, Traffic Simulation}
}
Acknowledgements
TUD-SUMO is part of the research under the project "AI in Network Management," funded by Rijkswaterstaat, grant agreement nr. 31179439, under the label of ITS Edulab.
References
- "Microscopic Traffic Simulation using SUMO"; Pablo Alvarez Lopez, Michael Behrisch, Laura Bieker-Walz, Jakob Erdmann, Yun-Pang Flötteröd, Robert Hilbrich, Leonhard Lücken, Johannes Rummel, Peter Wagner, and Evamarie Wießner. IEEE Intelligent Transportation Systems Conference (ITSC), 2018.
Metadata
Release files for tud-sumo 3.3.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 | Provenance | Actions |
|---|---|---|---|---|
| tud_sumo-3.3.3.tar.gz | 109.3 kB | Without provenance | Details for tud_sumo-3.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tud_sumo-3.3.3-py3-none-any.whl | Python 3 | none | any | Details for tud_sumo-3.3.3-py3-none-any.whl |
Total release size: 230.9 kB
Release files / tud_sumo-3.3.3.tar.gz
| Download URL | tud_sumo-3.3.3.tar.gz |
|---|---|
| Size | 109.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bfddfe9012e7f2587c917465af1684162f8e7276ff94997ce041d25b688c299
|
|
BLAKE2b-256 checksum How to use checksums |
7522e210f7d7aa4d9c1d16a6db1eacb6fc8f17a7c140f868a9ced3cd9c03b215
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Release files / tud_sumo-3.3.3-py3-none-any.whl
| Download URL | tud_sumo-3.3.3-py3-none-any.whl |
|---|---|
| Size | 121.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b44c4f70156885bc9ae505acab3657d5c49369d049dba7fa2ae76190b7f9404c
|
|
BLAKE2b-256 checksum How to use checksums |
74c93b82e947552a43e861a33405ea28559c73982d5ba89a841074433bd4af4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Security for tud-sumo 3.3.3
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.