Initial import of NavSea pbf project

This commit is contained in:
OpenAI Codex
2026-03-17 19:48:15 +08:00
commit 5f3f7409b3
84 changed files with 43889 additions and 0 deletions

View File

@@ -0,0 +1,54 @@
# NavSea Semantic Overlay Validation System
## Purpose
Validate the NavSea semantic overlay without touching rendering logic, style configuration, or vector tile structure.
## Inputs
The task reads the existing semantic overlay and audit tables in database `pbf_analysis`, including:
- `canonical_layer_rules`
- `canonical_object_rules`
- `object_geometry_allowlist`
- `pbf_relayer_candidates`
- `pbf_render_compatibility`
- `pbf_detection_catalog`
- `style_layers`
- `features`
- `tile_density`
## Execution
Rebuild the semantic overlay metadata and then run validation:
```bash
.venv/bin/python navsea_relayer.py
.venv/bin/python navsea_semantic_validation.py
```
## Validation Tables
The validation task creates or refreshes:
- `classification_validation`
- `geometry_consistency`
- `style_render_equivalence`
- `detection_catalog_integrity`
- `spatial_anomalies`
- `semantic_validation_summary`
## Current Design Notes
- Rendering compatibility is verified at database level only.
- `canonical_object_rules` is the stable object-level rule source.
- `object_geometry_allowlist` is the geometry whitelist used to separate valid multi-geometry objects from true anomalies.
- `spatial_anomalies` is intentionally lightweight and currently focuses on tile-density and tile-index anomalies.
## Success Criteria
- No render equivalence break
- No classification errors
- No geometry consistency errors
- No detection catalog integrity errors
- Spatial anomalies limited to acceptable warnings