que01/road-compiler
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: export portable native road packages

Browse Source
This commit is contained in:
que01
2026-08-26 11:59:48 +08:00
parent 3b4befb025
commit 81e02c670d
9 changed files with 118 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/native-road-package-v1.md
View File

@@ -73,6 +73,20 @@ shape and owns all path derivation.
The editable signal source at `trafficSignalsFile` is a sibling of `outDir`.
It is included in the parity baseline because regeneration must be stable.
## ZIP Export
The Web workbench's **导出道路包** action and the CLI's optional
`--export-zip <output.zip>` emit the portable package form. The ZIP root is
flat: it contains the six JSON documents above and `layers/*.geojson`, without
an enclosing area directory. It contains no OSM input, overrides, or compiler
workspace paths. `compiled.json` retains only model and movement data needed by
the downstream preview; its internal `source` paths are removed.
The ZIP manifest adds informational `generator: { name, version }`. Consumers
must select compatibility only from `contract`, `areaId`, and declared files.
Entry order and timestamp are fixed, so unchanged compiled output exports to
the same ZIP hash.
Successful CLI execution prints exactly one completion marker:
```text