39 lines
1.1 KiB
Markdown
39 lines
1.1 KiB
Markdown
# Guide Static Data
|
|
|
|
This directory contains the production guide/explain static package exported from
|
|
the Dameng `NATURE_SGS` schema.
|
|
|
|
Generated files:
|
|
|
|
- `manifest.json`
|
|
- `halls.json`
|
|
- `outlines.json`
|
|
- `guide-stops.json`
|
|
- `exhibits.json`
|
|
- `guide-contents.json`
|
|
- `pois.json`
|
|
- `indexes.json`
|
|
- `poi-bridge.json`
|
|
|
|
Re-export:
|
|
|
|
```bash
|
|
python scripts/export-guide-static-data.py
|
|
```
|
|
|
|
Optional arguments:
|
|
|
|
```bash
|
|
python scripts/export-guide-static-data.py --config <application-local.yaml> --output static/guide-data --nav-assets static/nav-assets/<nav-package>
|
|
```
|
|
|
|
Frontend mode:
|
|
|
|
- Default: `VITE_GUIDE_CONTENT_SOURCE_MODE=static`
|
|
- Future API mode: `VITE_GUIDE_CONTENT_SOURCE_MODE=remote`
|
|
- Explicit development demo mode only: `VITE_GUIDE_CONTENT_SOURCE_MODE=mock`
|
|
|
|
The static package preserves original database IDs and relationship fields.
|
|
`poi-bridge.json` maps SGS guide/explain POI references to the active nav-assets POI IDs.
|
|
Confirmed exhibit/stop/content POI mappings are used as exact locations; hall mappings are used as hall-level fallback locations when exhibit-level POI data is missing.
|