maliput / maliput/maliput_documentation
Small improvement on maliput overview's picture
Nobody has claimed this yet.
- Dominant language
- CMake
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
### Summary
In the Maliput Overview section there is this image:
While it is ok, there could be improvements to better explain the difference between the lane, segment and junction entities.
### Proposal
- Segments A, B, and C should be part of a junction.
- 1_0, 2_0, 3_0 shouldn't be part of the same intersection junction, they should be different junctions.
Also, demo maps like TShapeRoad would follow this pattern for the intersection.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Maliput Overview documentation and locate the embedded image shown in the issue; no file or test path is provided. Update the illustration so segments A, B, and C belong to one junction while 1_0, 2_0, and 3_0 belong to separate junctions, consistent with the TShapeRoad example. Done means the overview clearly distinguishes lanes, segments, and junctions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100