diff --git a/.flake8 b/.flake8
deleted file mode 100644
index cb50e3a..0000000
--- a/.flake8
+++ /dev/null
@@ -1,3 +0,0 @@
-[flake8]
-max-line-length = 88
-extend-ignore = E501
diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000..4587672
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1,7 @@
+# Enforce LF line endings for all text files
+* text=auto eol=lf
+
+# Git LFS - track large binary assets in generated/input/
+generated/input/**/*.png filter=lfs diff=lfs merge=lfs -text
+generated/input/**/*.pdf filter=lfs diff=lfs merge=lfs -text
+generated/input/**/*.xodr filter=lfs diff=lfs merge=lfs -text
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..fac5767
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,82 @@
+# HD-Map Asset Example — Copilot Instructions
+
+## Project Overview
+
+This is a **reference asset repository** for onboarding HD-Map simulation data into the ENVITED-X Dataspace. Users stage input files in `generated/input/`, then `make generate` runs the sl-5-8 pipeline to produce a complete, EVES-003-conformant asset in `generated/output/`.
+
+Assets follow the [EVES-003](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html) specification.
+
+## Asset Creation Flow
+
+### Input → Output
+
+Users provide an OpenDRIVE `.xodr` file and an `input_manifest.json` (plus optional images, docs, LICENSE) in `generated/input/`. The pipeline auto-extracts metadata, runs quality checks, generates GeoJSON previews, and packages everything into an EVES-003 asset in `generated/output/`.
+
+### Two Paths
+
+1. **Automated (default):** `make generate` — pipeline auto-extracts all metadata from the `.xodr` and input manifest. No user interaction needed.
+2. **Wizard-assisted (optional):** `make wizard` starts a SHACL-driven web UI (Podman containers) at `http://localhost:4200` for interactively enriching metadata. Users can also edit `input_manifest.json` and `metadata/hdmap.json` by hand as an alternative to the wizard.
+
+### Gaia-X Integration
+
+The pipeline adds [Gaia-X Trust Framework](https://gaia-x.eu/) vocabulary to every asset (`gx:name`, `gx:license`, `gx:copyrightOwnedBy`, `gx:resourcePolicy`) inside `metadata/hdmap.json`. These properties live in closed GX-compliant nodes, while domain-specific properties (road types, lane counts, format version) go in open ENVITED-X wrapper shapes. The wizard's SHACL forms reflect both layers. Users don't need to understand Gaia-X — the pipeline handles compliance automatically.
+
+### Pipeline Stages (18 total)
+
+`meta_data_extractor` → `jsonLD_creator` → `shacl_combiner` → `wizard_caller` (disabled by default) → `jsonLD_validator` → `qualitychecker_caller` (ASAM + OpenMSL) → `xodr_routing_creator` → `xodr_to_geojson_caller` → `asset_reducer` → `structure_creator` → `manifest jsonLD_creator` → `jsonLD_validator`
+
+Key config files are in `submodules/sl-5-8-asset-tools/configs/`. Each stage can be enabled/disabled via `process.json`.
+
+## Repository Structure
+
+- `generated/input/` — Staged pipeline inputs (manifest, `.xodr` files, media, docs)
+- `generated/output/` — Pipeline output: complete EVES-003 asset ready for validation and release
+- `submodules/sl-5-8-asset-tools/` — Asset creation and processing tools (git submodule from [openMSL/sl-5-8-asset-tools](https://github.com/openMSL/sl-5-8-asset-tools))
+ - `submodules/ontology-management-base/` — Nested submodule: SHACL shapes, OWL ontologies, JSON-LD contexts, and Python validation tools (from [ASCS-eV/ontology-management-base](https://github.com/ASCS-eV/ontology-management-base))
+
+## Setup and Validation
+
+```bash
+make setup
+make validate
+```
+
+All commands are exposed via `make` targets -- run `make help` for the full list.
+
+## Linting (pre-commit hooks)
+
+Configured in `.pre-commit-config.yaml` — all hooks delegate to `make` targets.
+
+## Key Conventions
+
+### Asset Structure (EVES-003)
+
+Every asset must contain: `simulation-data/`, `metadata/`, `media/`, `documentation/`, and a `manifest.json` at the root. Optional: `validation-reports/`.
+
+### JSON-LD Metadata
+
+- `manifest.json` — Content registry linking all asset files with access roles (`isOwner`, `isRegistered`, `isPublic`) and categories (`isSimulationData`, `isMetadata`, `isMedia`, etc.)
+- `metadata/hdmap.json` — Domain-specific metadata (format, content, quantity, quality, data source, georeference) conforming to the HD-Map SHACL shapes from ontology-management-base
+
+Both files use typed `@value`/`@type` pairs for literals and reference ontologies via `@context` prefixes like `hdmap:`, `manifest:`, `envited-x:`, `georeference:`, `gx:`.
+
+### Submodules
+
+Two direct submodules:
+
+- `submodules/sl-5-8-asset-tools` — Asset creation and processing tools (which contains `ontology-management-base` as a nested submodule)
+- `submodules/EVES` — The [EVES specification](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html) that defines the structure and requirements for Simulation Assets in the ENVITED-X Dataspace
+
+After cloning, initialize with:
+
+```bash
+make setup
+```
+
+### Commits
+
+This project uses [DCO sign-off](CONTRIBUTING.md). All commits require `Signed-off-by` — use `git commit -s`. Do **not** add `Co-authored-by: Copilot` trailers.
+
+## Release Workflow
+
+The GitHub Actions workflow (`.github/workflows/release.yml`) triggers on version tags (`v*.*.*`), runs `make setup && make generate && make validate`, and uploads the pipeline-generated `asset.zip` as a GitHub release artifact.
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index acfbe1f..c2d5f97 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -5,48 +5,36 @@ on:
tags:
- 'v*.*.*' # Triggers the workflow on version tags
+permissions:
+ contents: write
+
jobs:
release:
runs-on: ubuntu-latest
steps:
- - name: Checkout repository (+ download lfs dependencies)
+ - name: Checkout repository
uses: actions/checkout@v4
with:
lfs: true
+ submodules: recursive
+
- name: Checkout LFS objects
run: git lfs checkout
- - name: Set up Node.js
- uses: actions/setup-node@v4
+ - name: Set up Python
+ uses: actions/setup-python@v5
with:
- node-version: '20'
-
- - name: Install zip
- run: sudo apt-get install -y zip
+ python-version: '3.12'
- - name: Create zip file
+ - name: Setup, generate, and validate
run: |
- cd asset
- zip -r ../Testfeld_Niedersachsen_ALKS_xodr_sample.zip ./*
-
- - name: Create Release
- id: create_release
- uses: actions/create-release@v1
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- with:
- tag_name: ${{ github.ref }}
- release_name: Release ${{ github.ref }}
- draft: false
- prerelease: false
-
- - name: Upload Release Asset
- uses: actions/upload-release-asset@v1
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ make setup
+ make generate
+ make validate
+
+ - name: Create Release and Upload Asset
+ uses: softprops/action-gh-release@v2
with:
- upload_url: ${{ steps.create_release.outputs.upload_url }}
- asset_path: ./Testfeld_Niedersachsen_ALKS_xodr_sample.zip
- asset_name: Testfeld_Niedersachsen_ALKS_xodr_sample.zip
- asset_content_type: application/zip
+ files: "generated/output/**/*.zip"
+ generate_release_notes: true
diff --git a/.gitignore b/.gitignore
index d3b7e50..3b0ad68 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,5 @@
/.venv/
output.log
+*.zip
+/generated/output/
+!/generated/input/
\ No newline at end of file
diff --git a/.gitmodules b/.gitmodules
index 184cfeb..6692a47 100644
--- a/.gitmodules
+++ b/.gitmodules
@@ -1,3 +1,7 @@
-[submodule "ontology-management-base"]
- path = ontology-management-base
- url = https://github.com/GAIA-X4PLC-AAD/ontology-management-base.git
+[submodule "submodules/sl-5-8-asset-tools"]
+ path = submodules/sl-5-8-asset-tools
+ url = https://github.com/openMSL/sl-5-8-asset-tools.git
+ branch = main
+[submodule "submodules/EVES"]
+ path = submodules/EVES
+ url = https://github.com/ASCS-eV/EVES.git
diff --git a/.markdownlint.yaml b/.markdownlint.yaml
new file mode 100644
index 0000000..52414b2
--- /dev/null
+++ b/.markdownlint.yaml
@@ -0,0 +1,27 @@
+# Markdownlint configuration
+# https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
+default: true
+
+# Allow long lines — tables and descriptive prose need room
+MD013:
+ line_length: 300
+ code_blocks: false
+ tables: false
+
+# Allow inline HTML for collapsible sections and formatting
+MD033:
+ allowed_elements:
+ - a
+ - br
+ - details
+ - img
+ - noscript
+ - strong
+ - summary
+ - sup
+
+# Disable table column style — compact pipes are fine
+MD060: false
+
+# Allow bold text as step labels (e.g., **Step 1 — ...**)
+MD036: false
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 9ce777e..502072e 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -2,45 +2,15 @@
repos:
- repo: local
hooks:
- - id: black
- name: black
- entry: black
+ - id: validate
+ name: validate asset JSON-LD
+ entry: make validate
language: system
- types: [python]
- args: ["--config=pyproject.toml"]
- pass_filenames: true
- exclude: ontology-management-base/
-
- - id: isort
- name: isort
- entry: isort
+ pass_filenames: false
+ always_run: true
+ - id: lint-md
+ name: lint markdown
+ entry: make lint-md
language: system
- types: [python]
- args: ["--settings=pyproject.toml"]
- pass_filenames: true
- exclude: ontology-management-base/
-
- - id: flake8
- name: flake8
- entry: flake8
- language: system
- types: [python]
- args: ["--config=.flake8"]
- pass_filenames: true
- exclude: ontology-management-base/
-
- - id: jsonld-lint
- name: JSON-LD Linter
- entry: python ontology-management-base/src/jsonld_lint.py
- language: system
- types: [json]
- files: \.json$
- exclude: ontology-management-base/
-
- - id: turtle-lint
- name: Turtle Linter
- entry: python ontology-management-base/src/turtle_lint.py
- language: system
- types: [text]
- files: \.(ttl)$
- exclude: ontology-management-base/
+ pass_filenames: false
+ types: [markdown]
diff --git a/Makefile b/Makefile
new file mode 100644
index 0000000..2b33456
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,222 @@
+# Makefile for hd-map-asset-example
+# Build command center for common development tasks
+
+# Allow parent makefiles to override the venv path/tooling.
+# NOTE: VENV must be a relative path — the root Makefile prefixes it with CURDIR
+# when delegating to this submodule.
+VENV ?= .venv
+
+# Submodule path aliases (hide deep paths)
+ASSET_TOOLS := submodules/sl-5-8-asset-tools
+OMB := $(ASSET_TOOLS)/submodules/ontology-management-base
+
+# OS detection for cross-platform support (Windows vs Unix)
+ifeq ($(OS),Windows_NT)
+ SHELL := sh
+ VENV_BIN := $(VENV)/Scripts
+ PYTHON ?= $(VENV_BIN)/python.exe
+ BOOTSTRAP_PYTHON ?= python
+ ACTIVATE_SCRIPT := $(VENV_BIN)/activate
+ ACTIVATE_HINT := use the activation script under $(VENV_BIN) for your shell
+else
+ VENV_BIN := $(VENV)/bin
+ PYTHON ?= $(VENV_BIN)/python3
+ BOOTSTRAP_PYTHON ?= python3
+ ACTIVATE_SCRIPT := $(VENV_BIN)/activate
+ ACTIVATE_HINT := source $(ACTIVATE_SCRIPT)
+endif
+
+# Generated asset directory
+GENERATED_DIR := generated
+GEN_INPUT := $(GENERATED_DIR)/input
+GEN_OUTPUT := $(GENERATED_DIR)/output
+GEN_CONFIGS := $(ASSET_TOOLS)/configs
+
+# ── Subcommand support ───────────────────────────────────────────────
+# Enables: make generate clean, make wizard stop
+SUBCMD = $(word 2,$(MAKECMDGOALS))
+
+# ── Guards ───────────────────────────────────────────────────────────
+define check_dev_setup
+ @"$(PYTHON)" -c "True" 2>/dev/null || { \
+ echo ""; \
+ echo "[ERR] Development environment not set up."; \
+ echo " Run: make setup"; \
+ echo ""; \
+ exit 1; \
+ }
+endef
+
+.PHONY: all setup install lint format validate generate clean wizard help
+
+# Default target
+all: lint validate
+
+# ── Setup & Install ──────────────────────────────────────────────────
+
+setup: $(ACTIVATE_SCRIPT)
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" setup VENV="$(CURDIR)/$(VENV)" PYTHON="$(CURDIR)/$(PYTHON)"
+ @echo "[INFO] Installing quality checker runtime dependencies..."
+ @"$(PYTHON)" -m pip install -e "$(ASSET_TOOLS)[qc-deps]" --quiet
+ @echo "[INFO] Installing quality checker packages (--no-deps to avoid upstream lxml/numpy constraints)..."
+ @"$(PYTHON)" -m pip install poetry-core --quiet 2>/dev/null || true
+ @"$(PYTHON)" -m pip install --no-deps \
+ "asam-qc-baselib@git+https://github.com/asam-ev/qc-baselib-py@v1.1.0" \
+ "asam-qc-opendrive@git+https://github.com/jdsika/qc-opendrive@fix-contact-point-missing-road-link" \
+ "asam-qc-openscenarioxml@git+https://github.com/asam-ev/qc-openscenarioxml@v1.0.0" \
+ "openmsl-qc-opendrive@git+https://github.com/openMSL/sl-5-9-openmsl-qc-opendrive@main"
+# NOTE: qc-opendrive is pinned to a fork pending upstream PR asam-ev/qc-opendrive#139.
+# Switch back to @v1.0.0 (or newer) once the PR is merged.
+ @"$(PYTHON)" -m pre_commit install --allow-missing-config >/dev/null 2>&1 || true
+ @echo "[OK] Setup complete. Activate with: $(ACTIVATE_HINT)"
+
+$(PYTHON):
+ @echo "[INFO] Creating virtual environment at $(VENV)..."
+ @"$(BOOTSTRAP_PYTHON)" -m venv "$(VENV)"
+ @"$(PYTHON)" -m pip install --upgrade pip
+
+$(ACTIVATE_SCRIPT): $(PYTHON)
+ @"$(PYTHON)" -m pip install -e "$(ASSET_TOOLS)[dev]" --quiet
+ @touch "$(ACTIVATE_SCRIPT)"
+
+install:
+ $(call check_dev_setup)
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" install VENV="$(CURDIR)/$(VENV)" PYTHON="$(CURDIR)/$(PYTHON)"
+ @echo "[OK] Install complete"
+
+# ── Lint & Format ────────────────────────────────────────────────────
+# Root repo has no Python files -- lint validates JSON-LD asset data.
+
+lint: validate lint-md
+
+lint-md:
+ @echo "[INFO] Linting Markdown..."
+ @npx --yes markdownlint-cli2 "README.md" "CONTRIBUTING.md"
+ @echo "[OK] Markdown lint passed"
+
+format: format-md
+
+format-md:
+ @echo "[INFO] Formatting Markdown..."
+ @npx --yes markdownlint-cli2 --fix "README.md" "CONTRIBUTING.md"
+ @echo "[OK] Markdown format complete"
+
+# ── Validate ─────────────────────────────────────────────────────────
+# Validates JSON-LD files for every generated asset in the output directory.
+
+validate:
+ $(call check_dev_setup)
+ @"$(PYTHON)" -c "\
+import pathlib, sys; \
+out = pathlib.Path('$(GEN_OUTPUT)'); \
+dirs = sorted(d for d in out.iterdir() if d.is_dir()) if out.exists() else []; \
+sys.exit('[SKIP] No generated asset found (run: make generate)') if not dirs else None; \
+bad = [str(d) for d in dirs if not [p for p in [d / 'manifest.json', d / 'metadata' / 'hdmap.json'] if p.exists()]]; \
+sys.exit('[ERR] No manifest or metadata found in: ' + ', '.join(bad)) if bad else None; \
+all_paths = [str(p) for d in dirs for p in [d / 'manifest.json', d / 'metadata' / 'hdmap.json'] if p.exists()]; \
+print(' '.join(all_paths)); \
+" > .validate_paths 2>&1 && \
+ "$(PYTHON)" -m src.tools.validators.validation_suite \
+ --run check-data-conformance \
+ --data-paths $$(cat .validate_paths) \
+ --artifacts "$(OMB)/artifacts" && \
+ rm -f .validate_paths && \
+ echo "[OK] Validation complete" || \
+ { cat .validate_paths 2>/dev/null; rm -f .validate_paths; exit 1; }
+
+# ── Generate (full pipeline) ─────────────────────────────────────────
+
+generate:
+ifeq ($(SUBCMD),clean)
+ @echo "[INFO] Removing generated/output/ directory..."
+ @"$(PYTHON)" -c "import shutil; shutil.rmtree('$(GEN_OUTPUT)', ignore_errors=True)"
+ @echo "[OK] Generated output removed (input/ blueprint preserved)"
+else
+ $(call check_dev_setup)
+ @"$(PYTHON)" -c "\
+import pathlib, sys; \
+im = pathlib.Path('$(GEN_INPUT)') / 'input_manifest.json'; \
+sys.exit('[ERR] No input_manifest.json in $(GEN_INPUT)/. Stage input files first.') if not im.exists() else None; \
+"
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" generate \
+ INPUT_DIR="$(CURDIR)/$(GEN_INPUT)" \
+ OUTPUT_DIR="$(CURDIR)/$(GEN_OUTPUT)" \
+ VENV="$(CURDIR)/$(VENV)" \
+ PYTHON="$(CURDIR)/$(PYTHON)"
+ @echo ""
+ @echo "[OK] Asset generated in $(GEN_OUTPUT)/"
+endif
+
+# ── Wizard (SD Creation Wizard frontend + API) ───────────────────────
+
+wizard:
+ifeq ($(SUBCMD),stop)
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" wizard stop
+else
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" wizard
+endif
+
+# ── Clean ────────────────────────────────────────────────────────────
+
+clean:
+ifneq ($(firstword $(MAKECMDGOALS)),generate)
+ifeq ($(SUBCMD),all)
+ @echo "[INFO] Cleaning everything..."
+ @rm -rf build/ dist/ .pytest_cache/ .mypy_cache/ "$(GEN_OUTPUT)"
+ @rm -rf *.egg-info
+ @rm -f *.zip
+ @echo "[INFO] Removing virtual environment and submodules..."
+ @rm -rf "$(VENV)"
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" clean all 2>/dev/null || true
+ @echo "[OK] Full clean complete -- run 'make setup' to reinitialise"
+else
+ @echo "[INFO] Cleaning..."
+ @rm -rf build/ dist/ .pytest_cache/ .mypy_cache/ "$(GEN_OUTPUT)"
+ @rm -rf *.egg-info
+ @rm -f *.zip
+ @"$(MAKE)" -C "$(ASSET_TOOLS)" clean 2>/dev/null || true
+ @echo "[OK] Cleaned"
+endif
+else
+ @:
+endif
+
+# ── Help ─────────────────────────────────────────────────────────────
+
+help:
+ @echo "hd-map-asset-example -- Available Commands"
+ @echo ""
+ @echo " make setup Create venv and install all dependencies (incl. QC tools)"
+ @echo " make install Install packages"
+ @echo ""
+ @echo " make generate Run full pipeline: .xodr -> generated/ asset + zip"
+ @echo " make generate clean Remove generated/output/ directory"
+ @echo ""
+ @echo " You can also run the pipeline for a custom input directory:"
+ @echo " make -C submodules/sl-5-8-asset-tools generate \\"
+ @echo " INPUT_DIR=/path/to/input OUTPUT_DIR=/path/to/output"
+ @echo ""
+ @echo " make lint Lint (validates asset JSON-LD + Markdown)"
+ @echo " make lint-md Lint Markdown files only"
+ @echo " make format Auto-fix Markdown lint issues"
+ @echo " make validate Validate generated/output/ asset against SHACL"
+ @echo ""
+ @echo " make wizard Start SD Creation Wizard (Podman, auto-setup if needed)"
+ @echo " make wizard stop Stop the wizard containers"
+ @echo ""
+ @echo " make clean Remove all build artifacts, caches, and generated/"
+ @echo " make clean all Clean + remove venv and submodules (full reset)"
+ @echo ""
+ @echo "Debug logging:"
+ @echo " SL58_LOG_MODE=debug make generate"
+ @echo " Shows full subprocess command lines, stdout/stderr, and tracebacks."
+ @echo ""
+ @echo "Deterministic mode (reproducible output):"
+ @echo " SL58_DETERMINISTIC=1 make generate"
+ @echo " Same input files produce identical UUIDs, timestamps, and CID."
+
+# ── Catch-all for subcommand arguments ───────────────────────────────
+ifneq ($(filter setup generate wizard clean install,$(firstword $(MAKECMDGOALS))),)
+%:
+ @:
+endif
diff --git a/README.md b/README.md
index 984dea8..885e2e9 100644
--- a/README.md
+++ b/README.md
@@ -1,78 +1,488 @@
-# HD-Map Asset Example
-
-This repository serves as a reference for onboarding a HD-Map asset into the ENVITED X Dataspace and can be used as a template for other dataspaces as well. It contains the full description as **`manifest_reference.json` - file** in addition to a consistent example of an HD-Map asset data.
-
-A complete **`asset`** in a specific domain includes the data itself and all necessary files for describing, evaluating, and visualizing the dataset.
-
-The repository has the following folder structure and the asset sample can be downloaded as artifact from the lastest release (**`asset.zip`**).
-
-All ENVITED X Dataspace assets are defined according to [EVES-003](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html).
-
-## Installation
-
-If you want to use the validation scripts from 📁 `ontology-management-base/src` then you need to isntall the following dependencies:
-
-```bash
-# On Windows use python instead of python3
-sudo apt-get install python3-full
-python3 -m venv .venv/
-source .venv/bin/activate # On Windows use: source .venv/Scripts/activate
-python3 -m pip install -r ontology-management-base/requirements.txt
-# Example check
-python3 ontology-management-base/src/check_jsonld_against_shacl_schema.py asset/manifest_reference.json asset/metadata/hdmap_instance.json
-```
-
-## Repo Structure
-
-The Repo has the following structure:
-
-📁 `.github` *-> github workflows*
-
-📁 `asset` *-> contains the asset*
-
-- 📄 *`README.md`* (defines asset folder structure)
-- 📄 *`..more..`* (see folder)
-
-📁 `ontology-management-base`
-
-- contains all SHACLs and ontologies needed for onboarding and registering datasets, including semantic and syntactic validation of the provided metadata.
-- Versioned git submodule of [ontology-management-base](https://github.com/GAIA-X4PLC-AAD/ontology-management-base).
-
-📄 `CONTRIBUTING.md` *-> contributing guidelines*
-
-📄 `README.md` *-> documentation of the Repo and the asset*
-
-### Legend
-
-- 📁 `folder-name`: A folder in the repo.
-- 📄 `assetName`: A file in the repo.
-- (optional) : This file or folder is optional and can be added or omitted as needed.
-
-## FAQ
-
-### How can I easily create a Simulation Asset?
-
-- **Preparation :** *Ensure you understood this repository and the necessary data to create a SimulationAsset for the ENVITED-X Data Space and familiarize yourself with the concept of an asset [EVES-003](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html).*
-
-- **Provider Tools :** *You can use the [GaiaX 4 PLC-AAD Provider Tools](https://github.com/GAIA-X4PLC-AAD/provider-tools) to create your own asset in a guided way.*
-
-### Which roles can I define for access management?
-
-- **isOwner** *: The owner has full access to the asset and its associated files. This role includes permissions to download the asset.*
-
-- **isRegistered** *: A registered user has access to certain files and data within the asset but can't download the asset.*
-
-- **isPublic** *: A public user has only viewing rights to certain files or metadata.*
-
-### Which SCHAL - Files are used to generate the domainMetadata.json ?
-
--You need to use the following Ontology from [Ontology Management Base Repository](https://github.com/GAIA-X4PLC-AAD/ontology-management-base) - [HdMap_Ontology](https://github.com/GAIA-X4PLC-AAD/ontology-management-base/blob/main/hdmap/hdmap_ontology.ttl).
-
-## Usage
-
- 1. Read the `README.md` - file.
- 2. Download the lastest `asset.zip` - file release.
- 3. Explore the provided data files and documentation.
- 4. Create the same folder and file structure for your asset, along with an appropriate `hdmap_instance.json` - file and `manifest_reference.json` - file.
- 5. Zip your fills to an `asset.zip` - file.
- 6. You are now ready to upload `asset.zip` - file and start registration of your asset.
+# HD-Map Asset Example
+
+This repository demonstrates how to transform an [ASAM OpenDRIVE](https://www.asam.net/standards/detail/opendrive/) map (`.xodr`) into a **Simulation Asset** — a standardized, quality-checked, machine-readable package that can be shared with partners and integrated into simulation workflows.
+
+A Simulation Asset enriches raw map data with:
+
+- **Structured metadata** — road types, lane counts, geolocation, format version (JSON-LD)
+- **Quality reports** — automated ASAM and OpenMSL compliance checks
+- **Visual previews** — GeoJSON maps, bounding box, 3D road/lane geometry
+- **Access control** — per-file visibility roles (owner, registered, public) for data marketplace use
+- **Content-addressed packaging** — deterministic CID-named archive for integrity verification
+
+The asset structure follows [EVES-003][eves-003], the specification that defines folder
+layout and metadata schemas for Simulation Assets in the
+[ENVITED-X Dataspace](https://2025.2.envited-x.net).
+This repository serves as both a working reference and a template for creating new assets.
+
+[eves-003]: https://ascs-ev.github.io/EVES/EVES-003/eves-003.html
+
+## Prerequisites
+
+| Tool | Why | Install |
+|------|-----|---------|
+| **Python 3.12+** | Pipeline runtime | [python.org](https://www.python.org/downloads/), Microsoft Store, or `winget install Python.Python.3.12` |
+| **Git** | Submodule management | [git-scm.com](https://git-scm.com/downloads) (includes Git Bash on Windows) |
+| **GNU Make** | Task runner | see below |
+
+
+Windows — installing Make
+
+**Git Bash / MSYS2** — Make is included if you selected the MSYS2 option during Git install, or install it with:
+
+```bash
+# Using Scoop (recommended)
+scoop install make
+
+# Using Chocolatey
+choco install make
+```
+
+**PowerShell** — The same `scoop` or `choco` commands work. After installing, `make` uses Git's bundled `sh.exe` for recipe execution, so it works from PowerShell, Git Bash, and CMD alike.
+
+**Without Make** — You can run the pipeline directly with Python (see [Option B](#option-b--run-the-pipeline-directly) below).
+
+
+
+
+macOS / Linux
+
+Make and Git are typically pre-installed. Install Python 3.12+ via your package manager:
+
+```bash
+# macOS
+brew install python@3.12
+
+# Ubuntu/Debian
+sudo apt install python3.12 python3.12-venv
+```
+
+
+
+> **Podman** is only needed for `make wizard` (the SD Creation Wizard web UI). The pipeline itself does not require it. Podman is auto-installed by `make setup wizard` if missing.
+
+## Quick Start
+
+```bash
+# 1. Clone with submodules
+git clone --recurse-submodules https://github.com/ASCS-eV/hd-map-asset-example.git
+cd hd-map-asset-example
+
+# 2. Install everything
+make setup
+
+# 3. Generate a complete asset from the example .xodr
+make generate
+
+# 4. Validate the generated asset
+make validate
+```
+
+If already cloned without submodules:
+
+```bash
+git submodule update --init --recursive
+make setup
+```
+
+## How It Works
+
+The `generated/input/` folder contains the **pipeline inputs** — an OpenDRIVE `.xodr` file plus supplementary material (images, docs, license). `make generate` uses the [sl-5-8-asset-tools](https://github.com/openMSL/sl-5-8-asset-tools) pipeline to produce a complete EVES-003 asset in `generated/output/`.
+
+### Input → Output at a Glance
+
+```text
+ generated/input/ generated/output//
+ ├── input_manifest.json ─── make generate ──► ├── simulation-data/ (.xodr + .bjson)
+ ├── YourMap.xodr ├── metadata/ (hdmap.json)
+ ├── impression-01.png ├── media/ (GeoJSON, PNGs, 3D)
+ ├── documentation.pdf ├── documentation/ (PDF, stats)
+ ├── LICENSE ├── validation-reports/(QC results)
+ └── (optional extras) ├── manifest.json
+ └── LICENSE
+ ──► .zip (release archive)
+```
+
+**You provide:** a `.xodr` map file, an `input_manifest.json` describing your files, and optional supplementary material (screenshots, docs, license).
+
+**The pipeline generates:** domain metadata (`hdmap.json`), GeoJSON maps, 3D preview data, quality check reports, a search index, and the `manifest.json` content registry — all packaged as an EVES-003 asset.
+
+### Two Workflows for Creating Assets
+
+| | **Automated (default)** | **Wizard-assisted (optional)** |
+|---|---|---|
+| **How** | `make generate` | `make wizard` → edit in browser → `make generate` |
+| **Metadata source** | Auto-extracted from `.xodr` + `input_manifest.json` | Auto-extracted + manually enriched via SHACL-driven web form |
+| **When to use** | CI/CD, standard assets, bulk processing | First-time asset creation, when you need to add domain-specific details the extractor can't infer |
+| **Requires** | Python, Make | Python, Make, Podman |
+
+**Automated path:** Place your files in `generated/input/`, create an `input_manifest.json`, run `make generate`. The pipeline auto-extracts all metadata from your `.xodr` file — road types, lane counts, georeferencing, format version, etc.
+
+**Wizard path:** Start the SD Creation Wizard with `make wizard`, open `http://localhost:4200`, load the SHACL shapes for your domain, and fill in any metadata the extractor cannot infer. Export the enriched JSON-LD, place it in your input folder, then run `make generate`.
+
+### Metadata and Gaia-X
+
+The generated metadata uses the [Gaia-X Trust Framework](https://gaia-x.eu/) vocabulary alongside ENVITED-X domain ontologies. This enables Simulation Assets to participate in Gaia-X-compliant data ecosystems.
+
+**What Gaia-X adds to your asset:**
+
+| Property | Source | Example |
+|----------|--------|---------|
+| `gx:name` | Auto-extracted from `.xodr` filename | `"Testfeld_Niedersachsen_..."` |
+| `gx:description` | Auto-extracted from `.xodr` content | `"road network"` |
+| `gx:license` | Auto-detected from `LICENSE` file | `"MPL-2.0"` |
+| `gx:copyrightOwnedBy` | Parsed from license text | `"see contributors"` |
+| `gx:resourcePolicy` | Default | `"allow"` |
+
+These properties live inside `metadata/hdmap.json` as part of an `envited-x:ResourceDescription` node. The asset is identified by a DID (`did:web:registry.gaia-x.eu:HdMap:{UUID}`).
+
+**Design pattern:** ENVITED-X uses a wrapper architecture — Gaia-X properties go in closed GX-compliant nodes, while domain-specific properties (road types, lane geometry, format version) go in open ENVITED-X shapes. This keeps domain extensions from violating Gaia-X's strict SHACL constraints.
+
+> **You don't need to know Gaia-X to use this repo.** The pipeline handles all GX compliance automatically. The wizard provides a form UI if you want to inspect or edit the GX metadata.
+
+### What Gets Auto-Generated vs. Provided as Input
+
+Everything begins with **one input file**: an OpenDRIVE (`.xodr`) HD-Map file. The pipeline auto-generates most of the asset — the rest is supplementary material you provide (screenshots, docs, license).
+
+| File | Auto-Generated? | How |
+|------|:---:|---|
+| `simulation-data/*.xodr` | — | **Your input file** (the map itself) |
+| `simulation-data/*.bjson` | ✅ | `asset_reducer` extracts a search-optimized binary JSON |
+| `metadata/hdmap.json` | ✅ | `meta_data_extractor` → `jsonLD_creator` builds the JSON-LD |
+| `manifest.json` | ✅ | `structure_creator` → `jsonLD_creator` builds the manifest |
+| `media/roadNetwork.geojson` | ✅ | `xodr_routing_creator` converts road geometry to GeoJSON |
+| `media/bbox.geojson` | ✅ | `xodr_routing_creator` computes the bounding box polygon |
+| `media/3d_preview/*.json` | ✅ | `xodr_to_geojson_caller` converts road/lane/object geometry |
+| `validation-reports/*_asam_*.xqar/.txt` | ✅ | `qualitychecker_caller` runs ASAM OpenDRIVE checks |
+| `validation-reports/*_openmsl_*.xqar/.txt` | ✅ | `qualitychecker_caller` runs OpenMSL checks |
+| `media/*.png` (screenshots) | ❌ | Manually captured in a map viewer |
+| `documentation/*.pdf` | ❌ | Manually written documentation |
+| `documentation/*_stats.txt` | ❌ | Manually created statistics |
+
+### Pipeline Architecture
+
+The asset creation pipeline runs as a sequence of modular steps, each building on the previous one's output:
+
+```text
+ Your .xodr file ──► meta_data_extractor ──► jsonLD_creator (asset)
+ Parse .xodr XML Build hdmap.json
+ 🌐 geocoding
+
+ │
+ ├──► shacl_combiner ──► jsonLD_validator
+ │ Combine SHACL shapes Validate metadata
+ │
+ ├──► qualitychecker_caller
+ │ Run ASAM + OpenMSL checks → validation-reports/
+ │
+ ├──► xodr_routing_creator
+ │ .xodr → roadNetwork.geojson + bbox.geojson
+ │
+ ├──► xodr_to_geojson_caller
+ │ .xodr → 3d_preview/*.json (road/lane/object geometry)
+ │
+ ├──► asset_reducer
+ │ .xodr → .bjson (binary search index)
+ │
+ └──► structure_creator ──► jsonLD_creator (manifest)
+ Organize into EVES-003 Build manifest.json
+ folder structure ──► jsonLD_validator (manifest)
+
+ 🌐 = requires internet connection (reverse geocoding only)
+```
+
+## Generating an Asset (Step by Step)
+
+### Step 1 — Set up the environment
+
+```bash
+make setup
+```
+
+Creates a Python virtual environment (`.venv/`) and installs the pipeline with all dependencies.
+
+### Step 2 — Generate the asset
+
+```bash
+make generate
+```
+
+This single command:
+
+1. **Reads** the `input_manifest.json` blueprint from `generated/input/`
+2. **Runs** the full pipeline → outputs to `generated/output//`
+3. **Creates** a release-ready zip at `generated/output/.zip`
+
+The generated asset contains the complete EVES-003 folder structure:
+
+```text
+generated/output//
+├── simulation-data/ ← .xodr + .bjson search index
+├── metadata/ ← hdmap.json (JSON-LD)
+├── media/ ← GeoJSON maps + impression PNGs + 3D preview
+├── documentation/ ← PDF + stats
+├── validation-reports/ ← ASAM + OpenMSL QC reports
+├── manifest.json
+└── README.md
+```
+
+> 🌐 **Internet required for geocoding only** — reverse geocoding uses the Nominatim API. Ontology schemas and SHACL shapes are bundled via the `ontology-management-base` submodule.
+
+### Step 3 — Validate the generated asset
+
+```bash
+make validate
+```
+
+Runs the SHACL validation suite against the generated `manifest.json` and `hdmap.json`.
+
+### Step 4 — Clean up
+
+```bash
+make generate clean
+```
+
+Removes the `generated/output/` directory. Re-run `make generate` to regenerate.
+
+## Creating Your Own Asset
+
+To create a new HD-Map asset from **your own** `.xodr` file, you have two options:
+
+### Option A — Use `make generate` (recommended)
+
+1. Replace the `.xodr` in `generated/input/` with your own
+2. Replace images and docs in `generated/input/` with yours
+3. Update `generated/input/input_manifest.json` to list your files (see below)
+4. Run `make generate clean && make generate`
+
+The pipeline will run all steps and produce a fresh asset in `generated/output/`.
+
+#### Writing your `input_manifest.json`
+
+The `input_manifest.json` tells the pipeline which files to process, how to categorize them, and who can access them. Here's a minimal example:
+
+```json
+{
+ "@context": [
+ "https://w3id.org/ascs-ev/envited-x/manifest/v5/",
+ { "envited-x": "https://w3id.org/ascs-ev/envited-x/envited-x/v3/" }
+ ],
+ "@id": "did:web:registry.gaia-x.eu:HdMap:generated",
+ "@type": "envited-x:Manifest",
+ "hasArtifacts": [
+ {
+ "@type": "Link",
+ "hasCategory": { "@id": "envited-x:isSimulationData" },
+ "hasAccessRole": { "@id": "envited-x:isOwner" },
+ "hasFileMetadata": {
+ "@type": "FileMetadata",
+ "filePath": "your_map.xodr",
+ "mimeType": "application/xml"
+ }
+ },
+ {
+ "@type": "Link",
+ "hasCategory": { "@id": "envited-x:isMedia" },
+ "hasAccessRole": { "@id": "envited-x:isPublic" },
+ "hasFileMetadata": {
+ "@type": "FileMetadata",
+ "filePath": "screenshot.png",
+ "mimeType": "image/png"
+ }
+ }
+ ],
+ "hasLicense": {
+ "@type": "Link",
+ "hasCategory": { "@id": "envited-x:isLicense" },
+ "hasAccessRole": { "@id": "envited-x:isPublic" },
+ "hasFileMetadata": {
+ "@type": "FileMetadata",
+ "filePath": "LICENSE",
+ "mimeType": "text/plain"
+ }
+ }
+}
+```
+
+**Field reference:**
+
+| Field | Purpose | Values |
+|-------|---------|--------|
+| `filePath` | Filename relative to the input directory | Any filename present in the folder |
+| `mimeType` | MIME type of the file | `application/xml`, `image/png`, `application/pdf`, `text/plain`, etc. |
+| `hasCategory` | EVES-003 category | `envited-x:isSimulationData`, `envited-x:isMedia`, `envited-x:isDocumentation`, `envited-x:isLicense` |
+| `hasAccessRole` | Who can access this file | `envited-x:isOwner` (download), `envited-x:isRegistered` (view), `envited-x:isPublic` (browse) |
+
+> **LICENSE is required.** Every asset must declare a license via the `hasLicense` field. See `generated/input/input_manifest.json` for a complete working example.
+
+### Option B — Run the pipeline directly
+
+You can invoke the pipeline from any directory without `make`. This works in **any shell** — Bash, PowerShell, CMD:
+
+```bash
+# Create a working directory with your input files
+mkdir -p my_asset/input my_asset/output
+
+# Copy your files into the input directory
+cp path/to/your_map.xodr my_asset/input/
+cp path/to/screenshot.png my_asset/input/
+cp path/to/documentation.pdf my_asset/input/
+cp LICENSE my_asset/input/
+```
+
+Create `my_asset/input/input_manifest.json` using the template above, then run:
+
+```bash
+# Bash / Git Bash / macOS / Linux:
+.venv/bin/python -m asset_extraction.main \
+ my_asset/input/input_manifest.json \
+ -config submodules/sl-5-8-asset-tools/configs \
+ -out my_asset/output
+```
+
+```powershell
+# PowerShell:
+.\.venv\Scripts\python.exe -m asset_extraction.main `
+ my_asset\input\input_manifest.json `
+ -config submodules\sl-5-8-asset-tools\configs `
+ -out my_asset\output
+```
+
+> **Legacy format:** The pipeline also accepts `uploadedFiles.json` (a simple JSON array). See the [FAQ](#what-is-the-uploadedfilesjson) for details. New projects should use `input_manifest.json`.
+
+## What Partners Get
+
+When you share the generated asset (the `.zip`), recipients get a self-contained package they can evaluate without asking you anything:
+
+| What | How it helps partners |
+|------|----------------------|
+| **`manifest.json`** | Machine-readable content registry — partners' tools can automatically index, search, and verify every file in the asset |
+| **`metadata/hdmap.json`** | Structured domain metadata — road types, lane counts, coordinate system, geographic bounds — queryable without opening the map |
+| **`validation-reports/`** | Transparent quality — ASAM and OpenMSL compliance reports show exactly which checks passed or failed |
+| **`media/roadNetwork.geojson`** | Visual preview — partners can render the road network on a map without a specialized viewer |
+| **`media/3d_preview/`** | 3D geometry — roads, lanes, junctions, signals as lightweight JSON for web-based visualization |
+| **Access roles** | Per-file access control — you decide what's public (previews), registered-only (docs), or owner-only (raw data) |
+| **CID naming** | Content-addressed zip — the filename IS the hash, so partners can verify integrity without trusting the transport |
+
+## Repo Structure
+
+📁 `.github` → GitHub Actions release workflow
+
+📁 `generated/input` → Pipeline input files (`.xodr`, images, docs, license, `input_manifest.json`)
+
+📁 `generated/output` → Pipeline output (auto-generated, not committed)
+
+- 📁 `/simulation-data` → OpenDRIVE map file (`.xodr`) + search index (`.bjson`)
+- 📁 `/metadata` → `hdmap.json` (domain-specific JSON-LD metadata)
+- 📁 `/media` → Screenshots, GeoJSON maps, 3D preview data
+- 📁 `/documentation` → PDF documentation and statistics
+- 📁 `/validation-reports` → ASAM and OpenMSL quality check results
+- 📄 `/manifest.json` → Content registry linking all files with access roles
+
+📁 `submodules/sl-5-8-asset-tools`
+
+- Asset creation and processing pipeline tools.
+- Contains `ontology-management-base` as a nested submodule with all SHACLs and ontologies needed for validation.
+- Versioned git submodule of [sl-5-8-asset-tools](https://github.com/openMSL/sl-5-8-asset-tools).
+
+📁 `submodules/EVES`
+
+- The [EVES specification](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html) — defines the structure and requirements for Simulation Assets in the ENVITED-X Dataspace.
+- Versioned git submodule of [EVES](https://github.com/ASCS-eV/EVES).
+
+📄 `CONTRIBUTING.md` → Contributing guidelines (DCO sign-off required)
+
+📄 `Makefile` → Central command center for all operations
+
+## Available Make Targets
+
+```bash
+make help # Show all available commands
+
+make setup # Create venv and install all dependencies (incl. QC tools)
+make install # Install packages
+
+make generate # Run full pipeline: .xodr → generated/ asset + zip
+make generate clean # Remove generated/output/ directory
+
+make validate # Validate the generated asset against SHACL
+make lint # Lint (same as validate)
+
+make wizard # Start SD Creation Wizard (Podman, auto-setup if needed)
+make wizard stop # Stop the wizard containers
+
+make clean # Remove all build artifacts, caches, and generated/
+make clean all # Clean + remove venv and submodules (full reset)
+```
+
+## FAQ
+
+### How can I easily create a Simulation Asset?
+
+- **One command:** Run `make generate` — it reads the input blueprint from `generated/input/`, runs the full pipeline, and outputs a complete EVES-003 asset to `generated/output/`.
+
+- **Preparation:** Ensure you understood this repository and the necessary data to create a SimulationAsset for the ENVITED-X Data Space and familiarize yourself with the concept of an asset ([EVES-003](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html)).
+
+- **Guided Web UI:** Run `make wizard` to start the SD Creation Wizard — a SHACL-driven web form for inspecting and enriching asset metadata. See [Two Workflows for Creating Assets](#two-workflows-for-creating-assets) above.
+
+### Which roles can I define for access management?
+
+- **isOwner**: The owner has full access to the asset and its associated files. This role includes permissions to download the asset.
+
+- **isRegistered**: A registered user has access to certain files and data within the asset but can't download the asset.
+
+- **isPublic**: A public user has only viewing rights to certain files or metadata.
+
+### Which SHACL files are used to generate the domain metadata?
+
+You need to use the following ontology from [Ontology Management Base Repository](https://github.com/ASCS-eV/ontology-management-base) — [HdMap Ontology](https://github.com/ASCS-eV/ontology-management-base/blob/main/artifacts/hdmap/hdmap.owl.ttl).
+
+### What does the pipeline need to run?
+
+- **Python 3.12+**, **Git**, and **GNU Make** (see [Prerequisites](#prerequisites))
+- The `sl-5-8-asset-tools` submodule (initialized via `git submodule update --init --recursive` or `make setup`)
+- **Internet connection** — required only for reverse geocoding (Nominatim API); ontology schemas and SHACL shapes are provided locally by the `ontology-management-base` submodule
+- Quality checkers (ASAM + OpenMSL) are installed automatically by `make setup`
+
+### How do I enable debug logging?
+
+```bash
+# Bash / Git Bash / macOS / Linux:
+SL58_LOG_MODE=debug make generate
+
+# PowerShell:
+$env:SL58_LOG_MODE = "debug"; make generate
+
+# Or with direct Python invocation:
+$env:SL58_LOG_MODE = "debug"
+.\.venv\Scripts\python.exe -m asset_extraction.main ...
+```
+
+Shows full subprocess command lines, stdout/stderr, and tracebacks.
+
+### What is the `uploadedFiles.json`?
+
+It's the legacy input format — a simple JSON array that tells the pipeline which files to process and how to categorize them. Each entry has:
+
+- `filename` — path or URL to the file
+- `type` — what kind of file it is (`Asset`, `Document`, `Image`, `License`, etc.)
+- `category` — the EVES-003 category (`isSimulationData`, `isDocumentation`, `isMedia`, etc.)
+- `did` (optional) — a decentralized identifier for the asset
+
+The modern replacement is `input_manifest.json` (JSON-LD format). Both formats are supported. See `generated/input/input_manifest.json` for a complete example.
+
+### Known Limitations
+
+- **Geocoding timeouts** — The `meta_data_extractor` uses the Nominatim API for reverse geocoding. If the API is slow or rate-limited, the pipeline may fail. Simply retry.
+- **Quality checkers install from Git branches** — The `[qc]` optional dependencies (installed automatically by `make setup`) pull from Git branches and may take a while on first install. If you see stale checker errors after switching branches, run `make clean all && make setup` to get a fresh environment.
+- **Ontology versions** — The pipeline generates metadata using the **latest** ontology versions. Both current and older versions are valid but produce different JSON-LD structures.
+
+### Podman / Wizard Troubleshooting
+
+The SD Creation Wizard (`make wizard`) uses Podman containers. Common issues on Windows:
+
+| Error | Cause | Fix |
+|-------|-------|-----|
+| `CreateFile \\.\pipe\docker_engine: All pipe instances are busy` | Docker Desktop is running and holds the Docker API pipe | Quit Docker Desktop before starting Podman, or run `podman machine stop && podman machine start` |
+| `machine not in running state` | Podman machine failed to start | Run `podman machine rm` then `podman machine init && podman machine start` |
+| Port 4200 or 8080 already in use | Another process holds the port | `make wizard stop` first, or stop the other process |
diff --git a/asset.zip b/asset.zip
deleted file mode 100644
index d65624a..0000000
Binary files a/asset.zip and /dev/null differ
diff --git a/asset/README.md b/asset/README.md
deleted file mode 100644
index 823205c..0000000
--- a/asset/README.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# Testfeld Niedersachsen ALKS xodr sample
-
-Simple hdmap example file on the Testfeld Niedersachsen suitable for ALKS scenarios.
-
-## Digital Assets
-
-This is a digital asset according to the ENVITED Ecosystem Specification [EVES-003](https://ascs-ev.github.io/EVES/EVES-003/eves-003.html) for the ENVITED-X Data Space. It can be used as a template for other dataspaces as well. It contains a fully described and consistent example of a digital asset including a **`manifest.json` - file** as content registry.
-
-A complete **`digital asset`** in a specific domain includes the data itself and all necessary files for describing, evaluating, and visualizing the dataset.
-
-## Example Asset Folder Structure
-
-A sample **`digital asset`** can be downloaded from the [GAIA-X4PLC-AAD/hd-map-asset-example](https://github.com/GAIA-X4PLC-AAD/hd-map-asset-example) as artifact of the lastest release (**`asset.zip`**) containing the following structure:
-
-📁 `asset`
-
-- 📁 `simulation-data`
- - 📄 `assetName.xodr`
- - 📄 *`assetName_offset.xodr`* (optional)
-- 📁 `documentation`
- - 📄 `assetName_Documentation.pdf`
- - 📄 *`assetName_[Name].[ext]`* (optional)
-- 📁 `metadata`
- - 📄 `hdmap_instance.json`
-- 📁 *`validation-reports`* (optional)
- - 📄 *`qcReport.txt`* (optional)
-- 📁 `media`
- - 📁 `3d_preview` *-> 3d preview files* (optional)
- - 📄 `assetName_01.png` *-> eyecatcher*
- - 📄 *`assetName_[XX].png`* *-> impression* (optional)
- - 📄 `bbox.geojson`
- - 📄 *`roadNetwork.geojson`* (optional)
- - 📄 *`detailRoadNetwork.geojson`* (optional)
-- 📄 `README`
-- 📄 `manifest.json`
-
-### Legend
-
-- 📁 `folder-name`: A folder in the repo.
-- 📄 `assetName`: A file in the repo.
-- (optional)