Skip to main content

pyxodr

Tests Python 3.7+

Read OpenDRIVE files into a class structure that represents road objects as arrays of (x,y,z) coordinates rather than parameterised functions.

This class structure implements an API which should act as a middle layer between OpenDRIVE files and other applications, used to create road networks from their coordinates.

               

Installation

Install with pip:

pip install pyxodr

Testing

Testing is done on the OpenDRIVE example files. I have not included them in this repository as ASAM requires you enter your details to access them, so I assume they don't want them publically distributed through any means other than their own website. You can access them here.

You can also test on the networks for the OpenSCENARIO example files, obtainable here.

Once you've downloaded these files, create an example_networks subdirectory under tests and place them there.

.
├── docs
├── pyxodr
│   ├── geometries
│   ├── road_objects
│   └── utils
└── tests
    ├── example_networks
    │   ├── Ex_Lane-Border
    │   │   ...
    │   └── UC_Simple-X-Junction-TrafficLights
    ├── output_plots

and then you should be able to run the (Pytest) tests as normal:

pytest tests

Note: with version 1.7.0 of the OpenDRIVE spec, the Ex_LHT-Complex-X-Junction file throws a connection position ValueError on plotting with this module. I think this is due to a mistake in the file; older versions of this file work without throwing an error, and I believe that the direction of the reference line of road id==3 was reversed without swapping the corresponding contactPoint(s) - e.g. in road id==34, where it is listed as a successor with contactPoint=="start" despite the reference lines now traveling in opposite directions. If I'm incorrect about this and this is an error with the code, please raise an issue.

TODO

Large components of the OpenDRIVE spec are not currently supported, including:

  • Super Elevation / Road Shape (8.4.2 & 8.4.3)
  • Road surfaces (8.5)
  • Road markings (9.6)
  • Junction groups (10.7)
  • Objects (11)
  • Signals (12)
  • Railroads (13)
  • elementDir / elementS for road & junction linking.

Some of these will be supported in the future. Pull requests implementing (or partially implementing) any of these are welcome. Additionally if you find anything else unsupported by this repo which is not covered by the above list (and there will be lots), please raise an issue.

Metadata

Release files for pyxodr 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyxodr 0.1.3
File Size Uploaded Provenance Actions
pyxodr-0.1.3.tar.gz 31.0 kB Without provenance Details for pyxodr-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pyxodr 0.1.3
File Interpreter ABI Platform Actions
pyxodr-0.1.3-py3-none-any.whl Python 3 none any Details for pyxodr-0.1.3-py3-none-any.whl

Total release size: 67.1 kB

Release files / pyxodr-0.1.3.tar.gz

Download URL pyxodr-0.1.3.tar.gz
Size 31.0 kB
Tags Source
SHA-256 checksum
How to use checksums
e8625d976b08973a81daa0a9586042d0eb4d9f89fa76a3202481dcebd0600d9e
BLAKE2b-256 checksum
How to use checksums
50a8d277c2180027974b373a037ff08a8f8293b393573693a0e82c89b40e415c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.4

Release files / pyxodr-0.1.3-py3-none-any.whl

Download URL pyxodr-0.1.3-py3-none-any.whl
Size 36.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e77a0b29ad05dfdab7bafb8f82523cf6681ee4ece91fe0d87badf996b06a010d
BLAKE2b-256 checksum
How to use checksums
577676e744f0299d0f2e1521cf0c951ace0f73b24c41050332e8777dd5ba9589
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.4

Security for pyxodr 0.1.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page