RoadRunner Asset Mapping

Consolidated lookup tables for mapping source map format elements to RoadRunner project asset paths. All paths are relative to the project Assets/ folder.

When to Use

• Resolving lane marking subtypes to RoadRunner .rrlms asset paths
• Mapping sign codes (US MUTCD, German StVO, Japanese) to sign asset SVGs
• Looking up barrier/extrusion asset paths for fence, guard rail, jersey barrier, wall
• Finding prop/static object asset paths for placement in RRHD
• Determining region-specific sign paths based on geoReference coordinates
• Assigning lane type enums from source format lane classifications

When NOT to Use

• Building RRHD objects from scratch — use roadrunner-rrhd-authoring
• Performing the full Lanelet2 conversion pipeline — use roadrunner-convert-lanelet2-to-rrhd
• Importing maps into RoadRunner — use roadrunner-import-scene

Key Rules

• All asset paths start with `Assets/` — always prefix when constructing RelativeAssetPath objects.
• Extension matters. .rrlms = lane marking style, .rrcws = crosswalk style, .rrpms = polygon marking style. Using wrong extension causes "Asset file is missing" on import.
• Region detection from geoReference. Use lat/lon to determine Japan/Germany/US for sign paths.
• Sign naming convention. All signs use Sign_<code>.svg format based on national regulatory numbering.
• Japan speed signs have a space. Sign_323 (30).svg — note space before parenthesis.

Source Data

Asset mappings are derived from the official RoadRunner project configuration XMLs:

• DefaultAssets.xml — default materials and markings
• ApolloAssetData.xml — Apollo/Baidu HD Map format
• OpenDriveAssetData.xml — OpenDRIVE format
• HEREAssetData_NA.xml / HEREAssetData_WE.xml — HERE HD Map (NA/EU)
• TomTomAssetData.xml — TomTom HD Map format

These XML files are located in the RoadRunner project's configuration directory (typically <RoadRunner Project>/Configuration/).

Lane Markings

See references/laneMarkings.md for full mapping table.

Key patterns:

• All marking assets are in Assets/Markings/ with .rrlms extension
• Markings are keyed by type (solid/dashed/double) + color (white/yellow)
• Default road center marking: SolidDoubleYellow.rrlms
• Default outer boundary: SolidSingleWhite.rrlms

Signs

See references/signs.md for full mapping table.

Key patterns:

• US signs: Assets/Signs/US/Regulatory Signs/ or Assets/Signs/US/Warning Signs/
• German signs: Assets/Signs/Germany/Regulatory Signs/
• Japan signs: Assets/Signs/Japan/Regulatory Signs/ or Assets/Signs/Japan/Warning Signs/
• Speed limit signs use regulatory numbering: Sign_R2-1(30).svg (US), Sign_274(30).svg (DE), Sign_323 (30).svg (JP)
• Fallbacks: Sign_R2-1(Blank).svg (US), Sign_101.svg (DE warning), Sign_215.svg (JP warning)
• Sign geometry uses 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):

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.

Signals (Traffic Lights)

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.

Barriers & Extrusions

See references/barriers.md for full mapping table.

Key patterns:

• All extrusions in Assets/Extrusions/ with .rrext or .rrext.rrmeta extension
• Barriers use roadrunner.hdmap.BarrierType with ExtrusionPath

Props & Static Objects

See references/staticObjects.md for full mapping table.

Key patterns:

• Props in Assets/Props/ subdirectories (Trees, Signals, TrafficControl, etc.)
• Static objects use roadrunner.hdmap.StaticObjectType with AssetPath
• Objects use GeoOrientedBoundingBox for placement

Lane Types

See references/laneTypes.md for full mapping table.

Crosswalks & Curve Markings

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)

Stencils (Road Surface Markings)

Materials

Default Assets

These are the project-wide defaults (from DefaultAssets.xml):

Usage Pattern (MATLAB)

% 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.

Conventions

• All marking assets: Assets/Markings/<Name>.<ext> — extension determines type
• All sign assets: Assets/Signs/<Region>/<Category>/Sign_<code>.svg
• All extrusion assets: Assets/Extrusions/<Name>.rrext
• All prop assets: Assets/Props/<Category>/<Name>.fbx
• Use RelativeAssetPath(AssetPath="...") for RRHD construction (Name=Value syntax)
• Default road center: SolidDoubleYellow.rrlms; default outer boundary: SolidSingleWhite.rrlms

----

Copyright 2026 The MathWorks, Inc.