Public Review

ASAM OSI 3.7.0

Deadline: May 05, 2024

This minor release candidate contains a number of incremental enhancements and improvements:

• Sub-bounding boxes can be provided for ground truth objects to model e.g. concave non-rectangular objects in more realistic ways without resorting to full 3D models.
• Logical lanes can contain effective speed limit information to avoid the need to process traffic signs for speed selection.
• Routing information can be transmitted as part of HostVehicleData.
• Orientation rates can be transmitted as part of pedestrian skeleton information.
• A virtual detection area can be supplied in SensorData to visualize or indicate the currently active nominal detection area of a sensor.
• The system time of a source of SensorData can be supplied in addition to the simulation measurement timestamp to aid timing simulation and measurement use cases.
• An offset has been introduced that is to be added to the cartesian global ground truth coordinate system prior to mapping into a geodetic coordinate system with the proj.4 string. This harmonizes OSI with OpenDRIVE and allows the easier provision of false easting/northing in the coordinate transformation.
• The set of car types has been reduced to better harmonize with other OpenX standards as part of overall harmonization efforts.

Beyond that, many clarifications, improvements in definitions and documentation, enhanced installation information and enhanced Python support, including provisioning of Python packages on PyPI are key improvements in this release.

See all changes ASAM OSI 3.7.0 "Jolly Jones" Release Candidate 1

The project group asks all ASAM OSI users to review the release candidates and provide feedback on 

• Completeness:  Are there any missing parts or features that are required to use the standard? 
• Unclarities and ambiguities:  Are there any terms, definitions or content parts that are imprecise, unclear, not (sufficiently) defined or not understandable?
• Inconsistencies:  Are there any terms, definitions or content parts that contradict each other or are incompatible with other parts of the standard? Is the structure and line of reasoning plausible and consistent?
• Usefulness:  According to your expertise, is the standard practical and useful? Does it meet current market needs and requirements? 
• Implementability:  According to your expertise, is the standard in its current form feasible and can it be implemented cost-effectively? Does the standard allow an implementation with state-of-the-art technologies? Is the standard designed to be future-proof.
• Please do not submit new use-cases, features or requirements for the upcoming release

Review

• Release candidate: ASAM OSI 3.7.0 Release Candidate 1
• Changelog: ASAM OSI 3.7.0 "Jolly Jones" Release Candidate 1

This is a public review. Membership is not required to take part.