roadrunner-import-scene
Import HD Map or OpenDRIVE files into a RoadRunner scene using MATLAB
Install / Use
npx skills add matlab/matlab-agentic-toolkit --skill roadrunner-import-sceneInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Customer SupportSupported Platforms
Tags
Our assessment of roadrunner-import-scene
roadrunner-import-scene scores 90/100 on our quality scale, 154th of 319 Customer Support skills we index (top 49%).
Its SKILL.md is 14 KB long, well organised into 23 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.
With 1,098 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 21 days ago, so roadrunner-import-scene is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
roadrunner-import-scene compared with similar skills
All 4 of these similar skills score higher than roadrunner-import-scene; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| roadrunner-import-scene (this skill)by matlab | 90 | 1.1k | 21d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 14d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 14d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 133.6k | 3d ago | SKILL.md |
| ui-ux-pro-maxby nextlevelbuilder | 100 | 133.6k | 3d ago | SKILL.md |
Frequently asked questions
- How do I install roadrunner-import-scene?
- Run
npx skills add matlab/matlab-agentic-toolkit --skill roadrunner-import-scene. The install tabs above show the steps for each supported agent. - Which AI agents does roadrunner-import-scene work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is roadrunner-import-scene safe to use?
- It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is roadrunner-import-scene still maintained?
- The repository was last updated 21 days ago, so roadrunner-import-scene is actively maintained.
Skill content
View source on GitHubname: roadrunner-import-scene description: > Import HD Map or OpenDRIVE files into a RoadRunner scene using MATLAB. Use when loading driving scenes in RoadRunner or RoadRunner Scene Builder, importing RRHD, OpenDRIVE, or other RoadRunner-supported formats for simulation, or verifying Lanelet2-to-RRHD conversion results visually. Requires rrApp handle from roadrunner-core. license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md metadata: author: MathWorks version: "1.1"
RoadRunner Scene Import
Import map files into a RoadRunner scene for visualization, verification, and building.
When to Use
- Importing a
.rrhdfile into RoadRunner for visual verification - Importing an OpenDRIVE
.xodrfile into RoadRunner - Verifying converted maps after Lanelet2-to-RRHD or other conversions
- Configuring build options (asphalt surfaces, bridge detection, junction preservation)
When NOT to Use
- Launching RoadRunner or managing projects — use
roadrunner-core - Building RRHD map content — use
roadrunner-rrhd-authoring - Converting Lanelet2 to RRHD — use
roadrunner-convert-lanelet2-to-rrhd - Looking up asset paths — use
roadrunner-asset-mapping
Key Rules
- Always write to .m files when executing code. Never put multi-line MATLAB code directly in
evaluate_matlab_code. Write to a.mfile, run withrun_matlab_file, edit on error. Exception: if the user asks to "show the pattern" or says "do not execute", show code inline without writing files. - Requires
rrAppfromroadrunner-core. Do not launch or connect to RoadRunner in this skill. IfrrAppdoes not exist, invokeroadrunner-corefirst. - Always copy file to project folder. Use
status(rrApp).Project.Filenameandcopyfile()explicitly in every import workflow — never omit or hide behind a variable. - Always set
bridgeOpts.IsEnabled = trueexplicitly. Never rely on constructor defaults for bridge auto-detection. - Run enforcement gates before
importScene. File location, extension, and build-option checks are mandatory. - Load before Build by default. Use
ImportStep="Load"unless user explicitly requests a full build. - NEVER hardcode
DetectAsphaltSurfaces = truefor converted maps. Always inspect the RRHD for closed-loop topology first. Closed-loop networks (most Lanelet2 conversions) MUST useDetectAsphaltSurfaces = false— asphalt detection fills the interior of loops. - ALWAYS preserve junctions when they exist. If
tempMap.Junctionsis non-empty, you MUST setoverlapOpts.IsEnabled = true,overlapOpts.PreserveJunctionLanes = true, andoverlapOpts.PreserveJunctionShape = true. Never rely on RoadRunner's auto-detection to re-infer junctions — it discards authored geometry.
Prerequisites
- A valid
rrApphandle must exist (produced byroadrunner-coreskill) - A RoadRunner project must be open
- If
rrAppdoes not exist, invokeroadrunner-corefirst to launch and connect
Connection, launching, and project lifecycle are owned by roadrunner-core. This skill assumes rrApp is already available.
Import Workflow
Step 1: Create a Fresh Scene
Always create a new scene before importing to avoid stale data:
newScene(rrApp);
Step 2: Copy File to Project (MANDATORY — always show explicitly)
RoadRunner requires imported files to be inside the project folder. You MUST always include this exact pattern in your generated code — never assume the file is already there or hide it behind a variable:
st = status(rrApp);
projectFolder = st.Project.Filename;
[~, fileName, ext] = fileparts(sourceFile);
destFile = fullfile(projectFolder, fileName + ext);
copyfile(sourceFile, destFile);
NEVER omit the copyfile() call or the status(rrApp).Project.Filename lookup. Even if you define a destFile variable elsewhere, you MUST show both the project path retrieval and the copy operation explicitly in every import workflow.
Step 3: Import the Map
RoadRunner HD Map (.rrhd)
Load only (inspect RRHD view before build):
importOpts = roadrunnerHDMapImportOptions;
importOpts.ImportStep = "Load";
importScene(rrApp, destFile, "RoadRunner HD Map", importOpts);
Full import with build (use conditional logic — NEVER hardcode asphalt/junction settings):
Do NOT copy a fixed template. Always use the "Conditional Build Options" section below to determine the correct settings based on RRHD content. The enforcement gate will reject hardcoded DetectAsphaltSurfaces = true for RRHD files.
IMPORTANT: When enabling bridge auto-detection, you MUST always write bridgeOpts.IsEnabled = true explicitly. Do NOT rely on the constructor default — the line must appear in the generated code.
Conditional Build Options (MANDATORY — apply based on map content)
Inspect the RRHD content before choosing build options. The following rules determine when to enable/disable specific settings:
| Condition | Action | Reason |
|-----------|--------|--------|
| No Junctions in RRHD (empty or zero) | Set overlapOpts.IsEnabled = false | Without explicit junction definitions, overlap detection uses only geometry and produces incorrect groupings |
| Closed-loop road network (lanes form rings) | Set buildOpts.DetectAsphaltSurfaces = false | Asphalt detection fills interior of closed loops, creating unwanted surface polygons |
| Explicit Junctions present in RRHD | Set overlapOpts.PreserveJunctionLanes = true and overlapOpts.PreserveJunctionShape = true | Preserves authored junction geometry and lane connectivity instead of re-inferring from geometry |
Example: Import with junction-aware options:
importOpts = roadrunnerHDMapImportOptions;
buildOpts = roadrunnerHDMapBuildOptions;
buildOpts.ClearSceneOfExistingData = true;
% Read RRHD to inspect content before build
tempMap = roadrunnerHDMap;
read(tempMap, destFile);
% Conditional: asphalt surfaces
hasClosedLoops = false; % Detect from lane topology (any lane chain forming a cycle)
if hasClosedLoops
buildOpts.DetectAsphaltSurfaces = false;
else
buildOpts.DetectAsphaltSurfaces = true;
end
% Conditional: overlap groups / junctions
overlapOpts = enableOverlapGroupsOptions;
if isempty(tempMap.Junctions) || numel(tempMap.Junctions) == 0
overlapOpts.IsEnabled = false;
else
overlapOpts.IsEnabled = true;
overlapOpts.PreserveJunctionLanes = true;
overlapOpts.PreserveJunctionShape = true;
end
buildOpts.EnableOverlapGroupsOptions = overlapOpts;
bridgeOpts = autoDetectBridgesOptions;
bridgeOpts.IsEnabled = true;
buildOpts.AutoDetectBridgesOptions = bridgeOpts;
importOpts.BuildOptions = buildOpts;
importScene(rrApp, destFile, "RoadRunner HD Map", importOpts);
OpenDRIVE (.xodr)
importOpts = openDriveImportOptions;
importOpts.ImportSignals = true;
importOpts.ImportObjects = true;
importScene(rrApp, destFile, "OpenDRIVE", importOpts);
Step 4: Save the Scene
[~, sceneName] = fileparts(sourceFile);
saveScene(rrApp, sceneName);
Import Options Reference
roadrunnerHDMapImportOptions
| Property | Description |
|----------|-------------|
| ImportStep | "Load" (RRHD view only) or "Unspecified" (full load+build) |
| LoadOptions | roadrunnerHDMapLoadOptions — offset, projection |
| BuildOptions | roadrunnerHDMapBuildOptions — build configuration |
roadrunnerHDMapBuildOptions
| Property | Description | Default |
|----------|-------------|---------|
| ClearSceneOfExistingData | Remove existing scene content | auto |
| DetectAsphaltSurfaces | Generate road surfaces | auto |
| FitCrossSections | Fit lane cross sections | auto |
| CurvatureBlend | Curvature blending factor | auto |
| UseLaneGroups | Group lanes for editing (R2024a+) | auto |
| CombineTransitionLanes | Merge transition lanes (R2025a+) | auto |
| AutoDetectBridgesOptions | autoDetectBridgesOptions object | auto |
| EnableOverlapGroupsOptions | enableOverlapGroupsOptions object (junctions) | auto |
| FixUnrealisticRoadElevation | Correct elevation jumps from HD sources | auto |
| FixInconsistentLaneConnections | Remove physically unrealistic lane links | auto |
enableOverlapGroupsOptions
| Property | Description | Default |
|----------|-------------|---------|
| IsEnabled | Use junction location info (false = geometric overlaps) | auto |
| PreserveJunctionLanes | Keep original junction lanes from imported map | auto |
| PreserveJunctionShape | Keep junction polygon geometry from imported map | auto |
| GroupName | Name of the overlap group | auto |
openDriveImportOptions
| Property | Description |
|----------|-------------|
| ImportSignals | Import traffic signals |
| ImportObjects | Import static objects |
| LaneOptions | Lane conversion settings |
| Offset | Scene position offset |
| Projection | Geospatial projection |
| ImportRegion | Region filter (R2024a+) |
Supported Formats
| Format Name | File Type | Since |
|-------------|-----------|-------|
| "RoadRunner HD Map" | .rrhd | R2022b |
| "OpenDRIVE" | .xodr | R2022a |
| "HERE HD Map" | (catalog) | R2024a |
| "TomTom HD Map" | (catalog) | R2024b |
Default Behavior
When the user asks to "import a map" or "load into RoadRunner":
- Ensure
rrAppexists (invokeroadrunner-coreif not) - Create a new scene (clean slate)
- Copy file to project Assets folder
- Import with Load only (
ImportStep="Load") so user can verify RRHD view - Save the scene with the filename as scene name
Only perform a full build (with BuildOptions) when the user explicitly asks to build or the RRHD view has been verified.
When building, always inspect the RRHD content first and apply the conditional build options from the "Conditional Build Options" section above. Never use fixed/hardcoded build options without checking map content.
Key Functions
| Function | Purpose |
|----------|---------|
| newScene(rrApp) | Create fresh scene (clean slate) |
| status(rrApp) | Get project info (.Project.Filename) |
| importScene(rrApp, file, format, opts) | Import map file into scene |
| saveScene(rrApp, name) | Save current scene |
| roadrunnerHDMapImportOptions | Create import options (set ImportStep, BuildOptions) |
| roadrunnerHDMapBuildOptions | Create build options (asphalt, bridges, junctions) |
| autoDetectBridgesOptions | Bridge detection settings (IsEnabled) |
| enableOverlapGroupsOptions | Junction preservation (PreserveJunctionLanes, PreserveJunctionShape) |
| openDriveImportOptions | OpenDRIVE-specific import options |
Enforcement Gate (MANDATORY — run before import)
You MUST execute these checks before calling importScene. Do NOT skip.
%% --- ENFORCEMENT: RoadRunner is connected ---
try
st = status(rrApp);
assert(~isempty(st.Project.Filename), 'No project open');
fprintf('RoadRunner connected, project: %s\n', st.Project.Filename);
catch
error('RoadRunner:NotConnected', ...
'No RoadRunner instance connected. Run the Connection Strategy block first.');
end
%% --- ENFORCEMENT: File is inside project folder ---
projectFolder = st.Project.Filename;
assert(startsWith(destFile, projectFolder) || isfile(destFile), ...
'Import file must be inside the project folder. Copy it first.');
fprintf('File location check: PASS\n');
%% --- ENFORCEMENT: File extension matches format ---
[~, ~, ext] = fileparts(destFile);
if formatName == "RoadRunner HD Map"
assert(ext == ".rrhd", 'Expected .rrhd file for RoadRunner HD Map format');
elseif formatName == "OpenDRIVE"
assert(ext == ".xodr", 'Expected .xodr file for OpenDRIVE format');
end
fprintf('Format check: PASS\n');
%% --- ENFORCEMENT: Build options match RRHD content (MANDATORY for .rrhd) ---
if ext == ".rrhd"
tempMap = roadrunnerHDMap;
read(tempMap, destFile);
% Junction preservation check
if ~
Truncated for display — read the full file on GitHub.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
133.6kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
ui-ux-pro-max
133.6kUI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
