roadrunner-asset-mapping

Name: roadrunner-asset-mapping
Author: matlab

815stars105forks

How to install roadrunner-asset-mapping?

matlab/matlab-agentic-toolkit/roadrunner-asset-mapping

$npx -y skills add matlab/matlab-agentic-toolkit --skill roadrunner-asset-mapping

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# RoadRunner Asset Mapping
2
3	Consolidated lookup tables for mapping source map format elements to RoadRunner project asset paths. All paths are relative to the project `Assets/` folder.
4
5	## When to Use
6
7	- Resolving lane marking subtypes to RoadRunner `.rrlms` asset paths
8	- Mapping sign codes (US MUTCD, German StVO, Japanese) to sign asset SVGs
9	- Looking up barrier/extrusion asset paths for fence, guard rail, jersey barrier, wall
10	- Finding prop/static object asset paths for placement in RRHD
11	- Determining region-specific sign paths based on geoReference coordinates
12	- Assigning lane type enums from source format lane classifications
13
14	## When NOT to Use
15
16	- Building RRHD objects from scratch — use `roadrunner-rrhd-authoring`
17	- Performing the full Lanelet2 conversion pipeline — use `roadrunner-convert-lanelet2-to-rrhd`
18	- Importing maps into RoadRunner — use `roadrunner-import-scene`
19
20	## Key Rules
21
22	- All asset paths start with `Assets/` — always prefix when constructing `RelativeAssetPath` objects.
23	- Extension matters. `.rrlms` = lane marking style, `.rrcws` = crosswalk style, `.rrpms` = polygon marking style. Using wrong extension causes "Asset file is missing" on import.
24	- Region detection from geoReference. Use lat/lon to determine Japan/Germany/US for sign paths.
25	- Sign naming convention. All signs use `Sign_<code>.svg` format based on national regulatory numbering.
26	- Japan speed signs have a space. `Sign_323 (30).svg` — note space before parenthesis.
27
28	## Source Data
29
30	Asset mappings are derived from the official RoadRunner project configuration XMLs:
31	- `DefaultAssets.xml` — default materials and markings
32	- `ApolloAssetData.xml` — Apollo/Baidu HD Map format
33	- `OpenDriveAssetData.xml` — OpenDRIVE format
34	- `HEREAssetData_NA.xml` / `HEREAssetData_WE.xml` — HERE HD Map (NA/EU)
35	- `TomTomAssetData.xml` — TomTom HD Map format
36
37	These XML files are located in the RoadRunner project's configuration directory (typically `<RoadRunner Project>/Configuration/`).
38
39	## Lane Markings
40
41	See [references/laneMarkings.md](references/laneMarkings.md) for full mapping table.
42
43	Key patterns:
44	- All marking assets are in `Assets/Markings/` with `.rrlms` extension
45	- Markings are keyed by type (solid/dashed/double) + color (white/yellow)
46	- Default road center marking: `SolidDoubleYellow.rrlms`
47	- Default outer boundary: `SolidSingleWhite.rrlms`
48
49	## Signs
50
51	See [references/signs.md](references/signs.md) for full mapping table.
52
53	Key patterns:
54	- US signs: `Assets/Signs/US/Regulatory Signs/` or `Assets/Signs/US/Warning Signs/`
55	- German signs: `Assets/Signs/Germany/Regulatory Signs/`
56	- Japan signs: `Assets/Signs/Japan/Regulatory Signs/` or `Assets/Signs/Japan/Warning Signs/`
57	- Speed limit signs use regulatory numbering: `Sign_R2-1(30).svg` (US), `Sign_274(30).svg` (DE), `Sign_323 (30).svg` (JP)
58	- Fallbacks: `Sign_R2-1(Blank).svg` (US), `Sign_101.svg` (DE warning), `Sign_215.svg` (JP warning)
59	- Sign geometry uses `GeoOrientedBoundingBox` (Center + Dimension + GeoOrientation)
60
61	Region detection from geoReference:
62	```matlab
63	lat = geoRef(1); lon = geoRef(2);
64	if lat >= 24 && lat <= 46 && lon >= 122 && lon <= 154
65	region = "Japan";
66	elseif lat >= 35 && lat <= 72 && lon >= -10 && lon <= 25
67	region = "Germany";
68	else
69	region = "US";
70	end
71	```
72
73	Region-specific sign paths (verified R2026a):
74
75	\| Sign \| Japan \| US \| Germany \|
76	\|---\|---\|---\|---\|
77	\| 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` \|
78	\| 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` \|
79	\| 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` \|
80
81	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`.
82
83	## Signals (Traffic Lights)
84
85	\| Configuration \| Asset Path \|
86	\|---\|---\|
87	\| 3-light vertical (post) \| `Props/Signals/Signal_3Light_Post01.fbx` \|
88	\| 3-light vertical (bare) \| `Props/Signals/Signal_3Light_Bare01.fbx_rrx` \|
89
90	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 writte

People who liked this also viewed

6 picks

Type

roadrunner-asset-mapping

815stars105forks

View on GitHub

How to install roadrunner-asset-mapping?

matlab/matlab-agentic-toolkit/roadrunner-asset-mapping

$npx -y skills add matlab/matlab-agentic-toolkit --skill roadrunner-asset-mapping

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# RoadRunner Asset Mapping
2
3	Consolidated lookup tables for mapping source map format elements to RoadRunner project asset paths. All paths are relative to the project `Assets/` folder.
4
5	## When to Use
6
7	- Resolving lane marking subtypes to RoadRunner `.rrlms` asset paths
8	- Mapping sign codes (US MUTCD, German StVO, Japanese) to sign asset SVGs
9	- Looking up barrier/extrusion asset paths for fence, guard rail, jersey barrier, wall
10	- Finding prop/static object asset paths for placement in RRHD
11	- Determining region-specific sign paths based on geoReference coordinates
12	- Assigning lane type enums from source format lane classifications
13
14	## When NOT to Use
15
16	- Building RRHD objects from scratch — use `roadrunner-rrhd-authoring`
17	- Performing the full Lanelet2 conversion pipeline — use `roadrunner-convert-lanelet2-to-rrhd`
18	- Importing maps into RoadRunner — use `roadrunner-import-scene`
19
20	## Key Rules
21
22	- All asset paths start with `Assets/` — always prefix when constructing `RelativeAssetPath` objects.
23	- Extension matters. `.rrlms` = lane marking style, `.rrcws` = crosswalk style, `.rrpms` = polygon marking style. Using wrong extension causes "Asset file is missing" on import.
24	- Region detection from geoReference. Use lat/lon to determine Japan/Germany/US for sign paths.
25	- Sign naming convention. All signs use `Sign_<code>.svg` format based on national regulatory numbering.
26	- Japan speed signs have a space. `Sign_323 (30).svg` — note space before parenthesis.
27
28	## Source Data
29
30	Asset mappings are derived from the official RoadRunner project configuration XMLs:
31	- `DefaultAssets.xml` — default materials and markings
32	- `ApolloAssetData.xml` — Apollo/Baidu HD Map format
33	- `OpenDriveAssetData.xml` — OpenDRIVE format
34	- `HEREAssetData_NA.xml` / `HEREAssetData_WE.xml` — HERE HD Map (NA/EU)
35	- `TomTomAssetData.xml` — TomTom HD Map format
36
37	These XML files are located in the RoadRunner project's configuration directory (typically `<RoadRunner Project>/Configuration/`).
38
39	## Lane Markings
40
41	See [references/laneMarkings.md](references/laneMarkings.md) for full mapping table.
42
43	Key patterns:
44	- All marking assets are in `Assets/Markings/` with `.rrlms` extension
45	- Markings are keyed by type (solid/dashed/double) + color (white/yellow)
46	- Default road center marking: `SolidDoubleYellow.rrlms`
47	- Default outer boundary: `SolidSingleWhite.rrlms`
48
49	## Signs
50
51	See [references/signs.md](references/signs.md) for full mapping table.
52
53	Key patterns:
54	- US signs: `Assets/Signs/US/Regulatory Signs/` or `Assets/Signs/US/Warning Signs/`
55	- German signs: `Assets/Signs/Germany/Regulatory Signs/`
56	- Japan signs: `Assets/Signs/Japan/Regulatory Signs/` or `Assets/Signs/Japan/Warning Signs/`
57	- Speed limit signs use regulatory numbering: `Sign_R2-1(30).svg` (US), `Sign_274(30).svg` (DE), `Sign_323 (30).svg` (JP)
58	- Fallbacks: `Sign_R2-1(Blank).svg` (US), `Sign_101.svg` (DE warning), `Sign_215.svg` (JP warning)
59	- Sign geometry uses `GeoOrientedBoundingBox` (Center + Dimension + GeoOrientation)
60
61	Region detection from geoReference:
62	```matlab
63	lat = geoRef(1); lon = geoRef(2);
64	if lat >= 24 && lat <= 46 && lon >= 122 && lon <= 154
65	region = "Japan";
66	elseif lat >= 35 && lat <= 72 && lon >= -10 && lon <= 25
67	region = "Germany";
68	else
69	region = "US";
70	end
71	```
72
73	Region-specific sign paths (verified R2026a):
74
75	\| Sign \| Japan \| US \| Germany \|
76	\|---\|---\|---\|---\|
77	\| 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` \|
78	\| 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` \|
79	\| 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` \|
80
81	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`.
82
83	## Signals (Traffic Lights)
84
85	\| Configuration \| Asset Path \|
86	\|---\|---\|
87	\| 3-light vertical (post) \| `Props/Signals/Signal_3Light_Post01.fbx` \|
88	\| 3-light vertical (bare) \| `Props/Signals/Signal_3Light_Bare01.fbx_rrx` \|
89
90	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 writte

People who liked this also viewed

6 picks

Type