Skip to content

matlab/matlab-agentic-toolkit / skills-catalog/automotive/roadrunner-build-rrhd-map

roadrunner-build-rrhd-map

Verified

Build, convert, and import RoadRunner HD Maps (.rrhd) in MATLAB. Author lanes, lane boundaries, markings, junctions, signs, barriers, and speed limits with roadrunnerHDMap; convert Lanelet2 (.osm, Autoware) maps to RRHD; resolve RoadRunner road asset paths for markings, crosswalks, signs, signals, and barriers; and import or build .rrhd or OpenDRIVE (.xodr) files into a RoadRunner scene. Use when creating road networks for driving simulation, converting Lanelet2 or other HD map sources to RRHD, looking up road asset paths, or loading and verifying a map in RoadRunner or RoadRunner Scene Builder. Not for building scenes from recorded sensor data, running simulations, or recreating OpenSCENARIO (.xosc) scenarios.

FileKindSize
SKILL.mdskill md15.5 KB
manifest.yamlconfig557 B
references/assets/assetCatalog.mdmarkdown7.4 KB
references/assets/barriers.mdmarkdown3.6 KB
references/assets/laneMarkings.mdmarkdown5.8 KB
references/assets/laneTypes.mdmarkdown2.2 KB
references/assets/signs.mdmarkdown5.0 KB
references/assets/staticObjects.mdmarkdown5.1 KB
references/authoring/alignmentRules.mdmarkdown10.3 KB
references/authoring/apiReference.mdmarkdown9.0 KB
references/authoring/authoringWorkflow.mdmarkdown20.4 KB
references/authoring/deduplicateBoundaries.mdmarkdown4.9 KB
references/authoring/junctionPolygon.mdmarkdown6.8 KB
references/authoring/leftGapFilter.mdmarkdown6.5 KB
references/authoring/orthogonalSplit.mdmarkdown7.7 KB
references/authoring/resolveHeights.mdmarkdown2.4 KB
references/authoring/snapEndpoints.mdmarkdown4.0 KB
references/authoring/splitClosedGeometry.mdmarkdown3.8 KB
references/authoring/synthesizeCenterLine.mdmarkdown4.6 KB
references/authoring/validateMap.mdmarkdown1.1 KB
references/import/buildOptions.mdmarkdown4.0 KB
references/import/importScene.mdmarkdown12.9 KB
references/lanelet2/buildRRHD.mdmarkdown14.2 KB
references/lanelet2/conversionPipeline.mdmarkdown13.3 KB
references/lanelet2/coordinates.mdmarkdown4.9 KB
references/lanelet2/discoverRelations.mdmarkdown2.4 KB
references/lanelet2/enforcementGate.mdmarkdown3.3 KB
references/lanelet2/extractGeometry.mdmarkdown3.4 KB
references/lanelet2/extractJunctions.mdmarkdown5.0 KB
references/lanelet2/extractLanelets.mdmarkdown2.6 KB
references/lanelet2/extractNonLaneElements.mdmarkdown14.4 KB
references/lanelet2/extractSemantics.mdmarkdown4.4 KB
references/lanelet2/extractTopology.mdmarkdown5.4 KB
references/lanelet2/placedObjects.mdmarkdown4.4 KB
references/lanelet2/readOSM.mdmarkdown4.0 KB
references/lanelet2/splitClosedRoads.mdmarkdown3.0 KB
scripts/detectAlignment.mother3.3 KB
scripts/detectClosedLoop.mother5.8 KB
scripts/detectJunctions.mother12.4 KB
scripts/discoverWayTypes.mother4.8 KB
scripts/parseOSM.mother4.0 KB
scripts/resolveHeightConflicts.mother6.8 KB
scripts/resolveSignAsset.mother7.2 KB
scripts/snapConnectedEndpoints.mother4.0 KB
scripts/validateRRHD.mother6.3 KB

references/authoring/deduplicateBoundaries.md

View on GitHub
# Boundary Deduplication (MANDATORY Post-Construction Step)

When building RRHD from any source that assigns separate boundary objects to opposing lanes (Lanelet2, HERE, NDS, etc.), duplicate boundaries are nearly guaranteed. Two ways in the source may contain **identical geometry in reverse order** — the per-way deduplication (`wayToBndID`) only catches same-ID reuse, NOT reversed-duplicate ways.

**This step is MANDATORY after all boundaries and lanes are built, before `write()`.**

## Why

Without deduplication, opposing lanes have separate boundary objects for the same physical line. RoadRunner renders them independently, causing:
- Visual doubling of lane markings
- Incorrect shared-boundary topology
- Rendering artifacts at lane edges

On a typical map with 184 lanes, expect ~30 reversed duplicates.

## Algorithm

After building all `LaneBoundary` objects and all `Lane` objects:

```matlab
%% --- BOUNDARY DEDUPLICATION (MANDATORY) ---
nBnd = numel(laneBoundaries);
duplicates = {};
for i = 1:nBnd
    for j = i+1:nBnd
        g1 = laneBoundaries(i).Geometry;
        g2 = laneBoundaries(j).Geometry;
        if size(g1,1) ~= size(g2,1), continue; end

        % Check reverse match (most common case for opposing lanes)
        maxDiffRev = max(vecnorm(g1 - flipud(g2), 2, 2));
        if maxDiffRev < 0.001
            duplicates{end+1} = struct('keep',i,'remove',j,'type','reversed');
            continue;
        end

        % Check forward match (rare but possible)
        maxDiffFwd = max(vecnorm(g1 - g2, 2, 2));
        if maxDiffFwd < 0.001
            duplicates{end+1} = struct('keep',i,'remove',j,'type','identical');
        end
    end
end

% Update lane references: point removed boundaries to kept ones
for d = 1:numel(duplicates)
    dup = duplicates{d};
    keepID = string(laneBoundaries(dup.keep).ID);
    removeID = string(laneBoundaries(dup.remove).ID);

    for i = 1:numel(lanes)
        % Update left boundary references
        if string(lanes(i).LeftLaneBoundary.Reference.ID) == removeID
            currAlign = lanes(i).LeftLaneBoundary.Alignment;
            if strcmp(dup.type, 'reversed')
                if currAlign == "Forward", newAlign = "Backward";
                else, newAlign = "Forward"; end
            else
                newAlign = currAlign;
            end
            ar = roadrunner.hdmap.AlignedReference;
            ref = roadrunner.hdmap.Reference; ref.ID = keepID;
            ar.Reference = ref; ar.Alignment = newAlign;
            lanes(i).LeftLaneBoundary = ar;
        end

        % Update right boundary references
        if string(lanes(i).RightLaneBoundary.Reference.ID) == removeID
            currAlign = lanes(i).RightLaneBoundary.Alignment;
            if strcmp(dup.type, 'reversed')
                if currAlign == "Forward", newAlign = "Backward";
                else, newAlign = "Forward"; end
            else
                newAlign = currAlign;
            end
            ar = roadrunner.hdmap.AlignedReference;
            ref = roadrunner.hdmap.Reference; ref.ID = keepID;
            ar.Reference = ref; ar.Alignment = newAlign;
            lanes(i).RightLaneBoundary = ar;
        end
    end
end

% Remove duplicate boundaries from the array
removeIDs = containers.Map('KeyType','char','ValueType','logical');
for d = 1:numel(duplicates)
    removeIDs(char(string(laneBoundaries(duplicates{d}.remove).ID))) = true;
end
newBoundaries = roadrunner.hdmap.LaneBoundary.empty;
for i = 1:numel(laneBoundaries)
    if ~removeIDs.isKey(char(string(laneBoundaries(i).ID)))
        newBoundaries(end+1) = laneBoundaries(i);
    end
end
laneBoundaries = newBoundaries;
fprintf('Boundary deduplication: removed %d duplicates (%d boundaries remain)\n', ...
    numel(duplicates), numel(laneBoundaries));
```

## Key Details

- **Tolerance:** 0.001m (1mm) — accounts for floating-point precision without false positives
- **Reversed duplicates:** When merging a reversed pair, FLIP the alignment for all lanes that referenced the removed boundary (`Forward` ↔ `Backward`)
- **Identical duplicates:** Keep alignment unchanged — geometry direction matches
- **Marking preservation:** The kept boundary retains its `ParametricAttributes`. If the removed boundary had markings that the kept one doesn't, merge them (rare in practice — usually one of the pair is unmarked)
- **Order:** Run AFTER endpoint snapping and height conflict resolution, BEFORE the enforcement gate

## When to Skip

- Synthetic scenes built from scratch (boundaries are created once, no duplication)
- Maps where the source format guarantees unique boundary geometry (uncommon)

## Integration with Pipeline

In the standard RRHD construction pipeline:

1. Build all boundaries and lanes
2. Endpoint snapping
3. Height conflict resolution
4. **Boundary deduplication** ← this step
5. Enforcement gate (alignment + spatial checks)
6. Assemble map and `write()`

----

Copyright 2026 The MathWorks, Inc.

----
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall