Traffic scene renderer
This traffic scene renderer enables drawing top-view overviews of traffic constellations.
This drawings can be printed on screen using matplotlib and exported to images or tikz files that can be rendered with LaTeX to create vector-based drawings of the traffic scenes.
Installation
Installation can be done using pip. Simply run
pip install traffic-scene-renderer
Usage
Development
Yes, you can help! Follow the steps below to contribute to this package:
-
Download the git repository, e.g., using
git clone git@github.com:ErwindeGelder/TrafficSceneRenderer.git. -
Create a virtual environment, e.g., using
python -m venv venv. -
Activate the virtual environment (e.g., on Windows,
venv\Scripts\activate). -
Install
uvusingpip install uvand thentox-uvusinguv pip install tox-uv. -
The main branch is protected, meaning that you cannot directly push changes to this branch. Therefore, if you want to make changes, do so in a seperate branch. For example, you can create a new branch using
git checkout -b feature/my_awesome_new_feature. -
Before pushing changes, ensure that the code adheres to the linting rules and that the tests are successful. Run
tox. This does a linting check and runs all test scripts. To manually perform these steps, use the following commands:- Run
tox -e lint. You can do the linting commands manually using:- (One time)
uv pip install -r requirements-lint.txt ruff format . --check(remove the--checkflag to letruffdo the formatting)ruff check .mypy .
- (One time)
- Run
tox -e py310. - Run
tox -e py311. - Run
tox -e py312. - Run
tox -e py313. - Run
tox -e py314. - Run
tox -e combine-test-reports
- Run
-
Check if the tests covered everything using the coverage report in
/reports/coverage_html/index.html.NOTE: Currently, not all code is covered. Ideally, all code is covered, but for now, ensure that all new code is covered by the testing.
-
Push changes to GitHub. If everything is OK and you want to merge your changes to the
mainbranch, create a pull request. Ideally, there is at least one reviewer who reviews the pull request before the merge.
Note that currently only "Code owners" can merge pull requests onto the main branch. This is to
ensure that not everyone can break the main code (even unintentially). If you want to be a "Code
owner", let us know!
Metadata
Release files for traffic-scene-renderer 1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| traffic_scene_renderer-1.4.tar.gz | 62.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| traffic_scene_renderer-1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 121.9 kB
Release files / traffic_scene_renderer-1.4.tar.gz
| Download URL | traffic_scene_renderer-1.4.tar.gz |
|---|---|
| Size | 62.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f19196b4955d7c30d42455354d89ed22cd2bceeb4433af24a5b0dc5b2ec130a7
|
|
BLAKE2b-256 checksum How to use checksums |
c132d19fe46b938bbc6e743a353532ede74439467b26043df55fc8499c322e04
|
| 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 Aug 19, 2026.
Transparency logRelease files / traffic_scene_renderer-1.4-py3-none-any.whl
| Download URL | traffic_scene_renderer-1.4-py3-none-any.whl |
|---|---|
| Size | 59.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53dfc23e6148392525e7d873c93e83903870ba69fef509dd02c222859569a998
|
|
BLAKE2b-256 checksum How to use checksums |
fc504292bd0c42f86bea3de9dc7210365047a7ace83de02da705ba9c359acdea
|
| 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 Aug 19, 2026.
Transparency log