roadrunner-rrhd-authoring

What it does

Build RoadRunner HD Map (.rrhd) entities directly using the roadrunnerHDMap API in MATLAB. Provides the generic building blocks for constructing RRHD from any source — synthetic scenes, converted map data, or custom formats.

How it works

• The skill targets creating RRHD objects in MATLAB by following the provided patterns for constructing lanes, boundaries, markings, junctions, signs, signals, barriers, and parking.
• It emphasizes a Create-then-assign pattern for RRHD objects (e.g., creating objects like roadrunner.hdmap.Reference, then assigning properties).
• It requires starting with rrMap = roadrunnerHDMap; to load the namespace before using roadrunner.hdmap.* classes.
• It prescribes using RelativeAssetPath and AlignedReference only with Name=Value constructors when applicable.
• It enforces type-safe, Nx3 geometry (including a Z column) and describes enforcement gates to run before write() to validate geometry and alignment.
• It provides several high-level construction steps and example snippets for common RRHD elements and multi-lane road assembly, including how to wire topology, assign boundaries, and apply markings.

When to use it

• Building RRHD maps from scratch (synthetic scenes, test roads)
• Assembling RRHD entities from converted map data (Lanelet2, HERE, NDS, OpenDRIVE, custom formats)
• Needing reusable geometry algorithms and RRHD object construction patterns
• Debugging RRHD construction errors (wrong property names, alignment issues)

What it can touch

• The skill references and operates on roadrunner.hdmap.* objects, including Lanes, LaneBoundaries, LaneMarkings, Junctions, Signs, Signals, Barriers, Parking, and the top-level roadrunnerHDMap object. It requires rrMap = roadrunnerHDMap; before using any roadrunner.hdmap.* classes.

Caveats

• Licensing is NOASSERTION per the metadata.
• It enforces the rule to write to .m files and to execute code via a file, except when explicitly instructed to inline code.
• It cautions against modifying behavior beyond user requests and emphasizes using format-agnostic RRHD construction patterns, not source-specific parsing logic.