// RoadRunner asset path lookup tables for map format conversions in MATLAB. Maps lane markings, signs, signals, barriers, objects, and lane types to RoadRunner asset paths. Use when converting map formats to RRHD, resolving asset paths, or assigning visual assets to HD Map objects.
| name | roadrunner-asset-mapping |
| description | RoadRunner asset path lookup tables for map format conversions in MATLAB. Maps lane markings, signs, signals, barriers, objects, and lane types to RoadRunner asset paths. Use when converting map formats to RRHD, resolving asset paths, or assigning visual assets to HD Map objects. |
| license | MathWorks BSD-3-Clause |
| user-invocable | false |
| metadata | {"author":"MathWorks","version":"1.0"} |
Consolidated lookup tables for mapping source map format elements to RoadRunner project asset paths. All paths are relative to the project Assets/ folder.
.rrlms asset pathsroadrunner-rrhd-authoringroadrunner-convert-lanelet2-to-rrhdroadrunner-import-sceneAssets/ — always prefix when constructing RelativeAssetPath objects..rrlms = lane marking style, .rrcws = crosswalk style, .rrpms = polygon marking style. Using wrong extension causes "Asset file is missing" on import.Sign_<code>.svg format based on national regulatory numbering.Sign_323 (30).svg — note space before parenthesis.Asset mappings are derived from the official RoadRunner project configuration XMLs:
DefaultAssets.xml — default materials and markingsApolloAssetData.xml — Apollo/Baidu HD Map formatOpenDriveAssetData.xml — OpenDRIVE formatHEREAssetData_NA.xml / HEREAssetData_WE.xml — HERE HD Map (NA/EU)TomTomAssetData.xml — TomTom HD Map formatThese XML files are located in the RoadRunner project's configuration directory (typically <RoadRunner Project>/Configuration/).
See references/laneMarkings.md for full mapping table.
Key patterns:
Assets/Markings/ with .rrlms extensionSolidDoubleYellow.rrlmsSolidSingleWhite.rrlmsSee references/signs.md for full mapping table.
Key patterns:
Assets/Signs/US/Regulatory Signs/ or Assets/Signs/US/Warning Signs/Assets/Signs/Germany/Regulatory Signs/Assets/Signs/Japan/Regulatory Signs/ or Assets/Signs/Japan/Warning Signs/Sign_R2-1(30).svg (US), Sign_274(30).svg (DE), Sign_323 (30).svg (JP)Sign_R2-1(Blank).svg (US), Sign_101.svg (DE warning), Sign_215.svg (JP warning)GeoOrientedBoundingBox (Center + Dimension + GeoOrientation)Region detection from geoReference:
lat = geoRef(1); lon = geoRef(2);
if lat >= 24 && lat <= 46 && lon >= 122 && lon <= 154
region = "Japan";
elseif lat >= 35 && lat <= 72 && lon >= -10 && lon <= 25
region = "Germany";
else
region = "US";
end
Region-specific sign paths (verified R2026a):
| Sign | Japan | US | Germany |
|---|---|---|---|
| Stop | Assets/Signs/Japan/Regulatory Signs/Sign_330-A.svg | Assets/Signs/US/Regulatory Signs/Sign_R1-1.svg | Assets/Signs/Germany/Regulatory Signs/Sign_206.svg |
| Speed N | Assets/Signs/Japan/Regulatory Signs/Sign_323 (<N>).svg | Assets/Signs/US/Regulatory Signs/Sign_R2-1(<N>).svg | Assets/Signs/Germany/Regulatory Signs/Sign_274(<N>).svg |
| Fallback | Assets/Signs/Japan/Warning Signs/Sign_215.svg | Assets/Signs/US/Regulatory Signs/Sign_R2-1(Blank).svg | Assets/Signs/Germany/Warning Signs/Sign_101.svg |
Naming convention: All signs use Sign_<code>.svg format based on national regulatory numbering (MUTCD for US, StVO for Germany, Japanese road sign numbers). Note: Japan speed signs have a space before the parenthesis: Sign_323 (30).svg.
| Configuration | Asset Path |
|---|---|
| 3-light vertical (post) | Props/Signals/Signal_3Light_Post01.fbx |
| 3-light vertical (bare) | Props/Signals/Signal_3Light_Bare01.fbx_rrx |
Authoring vs Import limitation: You CAN author SignalType objects in MATLAB, add them to rrMap.Signals, and write the map to .rrhd — signal data IS written to the file. However, RoadRunner does NOT import signals from .rrhd maps. Signal data in the file is silently ignored on import. Show the asset paths and authoring code, but warn the user that signals will not appear in the RoadRunner scene after import.
See references/barriers.md for full mapping table.
Key patterns:
Assets/Extrusions/ with .rrext or .rrext.rrmeta extensionroadrunner.hdmap.BarrierType with ExtrusionPathSee references/staticObjects.md for full mapping table.
Key patterns:
Assets/Props/ subdirectories (Trees, Signals, TrafficControl, etc.)roadrunner.hdmap.StaticObjectType with AssetPathGeoOrientedBoundingBox for placementSee references/laneTypes.md for full mapping table.
Extension rules (commonly confused):
.rrcws = crosswalk style (only for actual crosswalks).rrlms = lane marking style (stop lines, bike markings, zig-zag).rrpms = polygon marking style (striped regions, chevrons)| Type | Asset Path | Extension |
|---|---|---|
| Simple crosswalk | Assets/Markings/SimpleCrosswalk.rrcws | .rrcws |
| Continental crosswalk | Assets/Markings/ContinentalCrosswalk.rrcws | .rrcws |
| Ladder crosswalk | Assets/Markings/LadderCrosswalk.rrcws | .rrcws |
| Stop line | Assets/Markings/StopLine.rrlms | .rrlms |
| Striped region | Assets/Markings/StripedRegion.rrpms | .rrpms |
| Type | Asset Path |
|---|---|
| Arrow left | Assets/Stencils/Stencil_ArrowType4L.svg |
| Arrow right | Assets/Stencils/Stencil_ArrowType4R.svg |
| STOP text | Assets/Stencils/Stencil_STOP.svg |
| Purpose | Asset Path |
|---|---|
| Road surface | Assets/Materials/Asphalt1.rrmtl |
| Sidewalk / concrete | Assets/Materials/Concrete1.rrmtl |
| Ground / grass | Assets/Materials/Grass1.rrmtl |
These are the project-wide defaults (from DefaultAssets.xml):
| Name | Path |
|---|---|
| Island Curb Material | Assets/Materials/Concrete1.rrmtl |
| Blank Sign | Assets/Signs/US/Sign_BlankWhite.rrsign |
| Blank Warning Sign | Assets/Signs/US/Yellow_Blank_US.svg |
| Surface Material | Assets/Materials/Grass1.rrmtl |
| Crosswalk | Assets/Markings/SimpleCrosswalk.rrcws |
| Stop Line | Assets/Markings/StopLine.rrlms |
| Parking Space Marking | Assets/Markings/SolidSingleWhite.rrlms |
| Road Surface Material | Assets/Materials/Asphalt1.rrmtl |
| Road Center Marking | Assets/Markings/SolidDoubleYellow.rrlms |
| Dashed Road Marking | Assets/Markings/DashedSingleWhite.rrlms |
| Road Outer Boundary | Assets/Markings/SolidSingleWhite.rrlms |
| Road Inner Boundary | Assets/Markings/SolidSingleYellow.rrlms |
| One Way Passing | Assets/Markings/DashedSolidYellow.rrlms |
| Vehicle | Assets/Vehicles/Sedan.fbx |
% Example: resolve marking asset path
function assetPath = resolveMarkingAsset(type, color)
% type: "solid", "dashed", "solid_solid", etc.
% color: "white", "yellow" (default: white)
if nargin < 2, color = "white"; end
% Use lookup from references/laneMarkings.md
end
All asset paths are prefixed with Assets/ when used in RRHD RelativeAssetPath objects.
Assets/Markings/<Name>.<ext> — extension determines typeAssets/Signs/<Region>/<Category>/Sign_<code>.svgAssets/Extrusions/<Name>.rrextAssets/Props/<Category>/<Name>.fbxRelativeAssetPath(AssetPath="...") for RRHD construction (Name=Value syntax)SolidDoubleYellow.rrlms; default outer boundary: SolidSingleWhite.rrlmsCopyright 2026 The MathWorks, Inc.
Convert Lanelet2 maps (.osm) to RoadRunner HD Map (.rrhd) format using MATLAB. Use when converting Lanelet2 maps into RoadRunner Scene Builder, building driving scenes from open-source map data, or transforming road network definitions for simulation.
Connect to RoadRunner and import HD Map or OpenDRIVE files into a new 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.
Build RoadRunner HD Map entities in MATLAB — lanes, boundaries, markings, junctions, signs, signals, barriers, parking. Use when creating driving scenes from scratch, authoring road networks for simulation and testing automated driving systems, or assembling RRHD maps from Lanelet2 or other HD map sources.
Build, modify, and diagram SimBiology models — API reference, helper functions, and layout patterns. Use when constructing or editing models programmatically or visually.
Simulate SimBiology models — ODE, stochastic (SSA), scenarios, and sensitivity analysis. Use when asked to run, simulate, predict, explore what-if, or identify influential parameters.
Display 3-D image volumes, medical image volumes, surface meshes, and annotations for 3-D image processing. Use when displaying 3-D images or isosurfaces with volshow, creating volume viewers with viewer3d, adding Regions of Interest (ROI) or annotations, overlaying masks or segmentations, streaming volumetric data, or building apps with volume display.