Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workover Chapter 7.2: General #162

Open
LudwigFriedmann opened this issue Oct 31, 2024 · 0 comments
Open

Workover Chapter 7.2: General #162

LudwigFriedmann opened this issue Oct 31, 2024 · 0 comments
Assignees
Labels
isState:New A new issue that needs to be classified to a type. isSubGroup:GEOMETRY isType:Feature An issue that adds new features to the project.

Comments

@LudwigFriedmann
Copy link
Collaborator

LudwigFriedmann commented Oct 31, 2024

Is your feature request related to a problem? Please describe.

  • Replace sentence from 7.2.2.1
    "If a road network is referenced from a scenario, the world coordinate system is aligned with the inertial coordinate system present in this description."
    By
    "Nevertheless, the origin of the OpenMATERIAL world coordinate system should coincide with the origin of a corresponding ASAM OpenDRIVE map (if available). The origin of the world coordinate system in ASAM OSI should also be aligned with these two coordinate systems."
  • In 7.2.2.2:
    • Replace sentence
      "The local coordinate system is in line with the standards ASAM OpenDRIVE, ASAM OpenSCENARIO, and ASAM OSI"
      By
      "Top-most local coordinate frames of 3D assets (so called reference coordinate frames) in OpenMATERIAL are typically defined in the center of the bounding box of the corresponding asset, projected to the bottom of the bounding box. By static transformations, these coordinate frames can be synchronized with reference coordinate frames in ASAM OpenSCENARIO and ASAM OSI. Besides reference coordinate frames, 3D assets may incorporate other local coordinate frames, see chapter 7.3"
    • Remove Note
  • Chapter 7.2.4: Answer/close Resolve open questions from 3D asset file section (7.2.4) #117 and move this section/information to an overarching chapter (e.g. 0.Introduction)
  • Chapters 7.2.5 and 7.2.6: Check input from Define (quality) requirements to the Requirements chapter (7.2.5) #129 and Add recommendations to the Recommendations chapter (7.2.6) #130 , see if we can create sufficient meaningful content or postpone these topics

Describe the solution you'd like
See above

Describe alternatives you've considered

Additional context

@LudwigFriedmann LudwigFriedmann added isState:New A new issue that needs to be classified to a type. isType:Feature An issue that adds new features to the project. isSubGroup:GEOMETRY labels Oct 31, 2024
@LudwigFriedmann LudwigFriedmann self-assigned this Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
isState:New A new issue that needs to be classified to a type. isSubGroup:GEOMETRY isType:Feature An issue that adds new features to the project.
Projects
None yet
Development

No branches or pull requests

1 participant