GEO-STANDARD.md — Geospatial Component Type (stub-maturity record for an externally-authored geospatial product)
Inherits the component-composition model (COMPONENT-REGISTRY.md). Governs the
(geospatial)component type ONLY. A geospatial product is a PRESCRIPTIVE product — its value is a spatial operating picture the client uses to MOVE, POSITION, and OPERATE (routes, chokepoints, lines of sight, venues), NOT knowledge about a subject — so it does NOT carry the report anatomy (BLUF / Key Judgments / ACH / KAC / PIR). It has its own spine, below.
1. What a geospatial component is
Value = an authored spatial operating picture (KML / MyMaps / GeoJSON / map-book atlas) whose layers prescribe how to move and position on the ground. Imperative/spatial, not estimative. Stub-maturity by deliberate registry decision: the authored binary lives in an external_artifact; the .md only records identity, layer manifest, sourcing, confidence, and gaps. The type stays stub until promoted to first-class.
2. Required anatomy (the EXTERNAL artifact carries this spine; the .md records identity + sourcing + confidence)
The authored KML/MyMaps/GeoJSON/atlas at external_artifact MUST contain:
- Coordinate system & datum — declared (e.g., WGS84) and consistent across every layer.
- Layer manifest & symbology — named layers with a legend; every symbol/color defined.
- Source imagery provenance & currency — basemap/imagery source and capture date per layer.
- OCOKA / route / venue analytic overlays — the operating overlays (routes, chokepoints, LOS, venues, OCOKA) the product is built to convey.
The .md itself carries ONLY: frontmatter (the required fields below) + a short Layers / contents summary + a short Sourcing & confidence line. Required frontmatter fields (gated by the linter): component_type, maturity, name, external_artifact, source_grade, confidence, gaps.
3. Mandatory caveat
This geospatial product is decision-support for movement and positioning planning only; it does not warrant ground truth. Verify routes, access, and hazards in person before reliance, and conduct no unlawful collection or trespass in its preparation.
4. Sourcing & confidence discipline
Where a layer rests on graded intelligence, the source line carries a two-char NATO Admiralty grade (reliability A–F × credibility 1–6, reproduced verbatim in the artifact’s legend/annex). Where layers rest only on imagery/observation, record provenance + capture date instead of a grade. No L×I risk key applies — this type does not score risk; do not pad one in.
5. Geospatial-specific discipline (the load-bearing rule)
Every layer in the manifest names its source and currency, and every operating overlay (route, chokepoint, LOS, venue) is anchored to a declared coordinate system/datum — no unsourced, undated, or ungeoreferenced layer ships.
6. Format
Pure heading hierarchy; bracketed [placeholders] everywhere content goes; no worked content; no live tools; blank skeleton (like the report/profile skeletons). For this stub type the .md is short by design.
Authored from a Templater skeleton; the obsidian-linter plugin enforces the required frontmatter (presence-only gate). The type is stub-maturity until promoted to first-class.