> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/sources-and-evidence/map.md).
# Map
Explore governed geographic evidence and manage approved map packages.
**Open this area:** In the CORTEX menu, select **Sources & evidence → Map & spatial context**.
Use approved base sources, temporary local overlays, retained material locations and versioned geographic layers without manufacturing precision.
**Who uses this:** Analyst, Collector\
**Open in CORTEX:** `/map`\
**In-app guide:** `/help?topic=map`
**Expected result:** You can distinguish cartographic context, temporary preview, retained source-backed geography and reproducible derived results.
## Before you start
* Select a current authorised workspace. Online policy can permit the reviewed standard OpenStreetMap source; Offline uses an approved local package or the bundled outline and never falls back to public tiles.
* Know the real marking and restrictions of every file to display. A file cannot establish its own classification.
* Prepare one local GeoJSON, JSON or CSV at a time, within 2 MiB, 2,000 features and 20,000 coordinates; CSV needs latitude and longitude headers.
## What to do
{% stepper %}
{% step %}
## Read readiness and see the preview
Open **Sources & evidence → Map & spatial context**.
The Map destination stays discoverable when access is incomplete so this page can identify the exact missing control. The preview fills the working viewport.
Confirm the highest displayed handling to open authorised layers; the operational map then replaces the preview and fills the working viewport. Readiness and configuration remain below the map.
Confirm:
* Workspace access
* Internet policy
* Current base
Read the three-check readiness bar.
The bundled Natural Earth preview remains available when a detailed catalogue or provider cannot be used.
> The map is context, not evidence of a live location.
> {% endstep %}
{% step %}
## Declare the handling
On Map review the initial full-authority declaration and set the highest marking and all restrictions needed by the intended data, retaining the workspace floor.
Select **Open operational map**.
{% endstep %}
{% step %}
## Confirm and import
Confirm that the local data fits the declaration, then choose **Choose local data** or drop one supported file.
* GeoJSON coordinates must be valid WGS84.
* CSV may also contain a name column.
Read any validation error before changing the dataset.
{% endstep %}
{% step %}
## Choose an approved source
Use the source manager to select one available base map and independently toggle permitted overlays.
Read:
* Provider
* Map type
* Attribution
* Extent
* Zoom
* Connectivity
* Cache/export limits
Disabled, blocked, unconfigured and unreachable sources state the reason.
Switching source preserves operational overlays and extent.
{% endstep %}
{% step %}
## Explore temporary data explicitly
Use visibility, opacity/order controls, **Remove**, **Fit visible layers** and **Area of interest** for approved overlays, the retained workspace overlay and temporary files.
Base maps remain exclusive.
Local GeoJSON/CSV stays in the tab and is cleared on exit.
Read source context separately; proximity does not establish identity, intent or corroboration.
{% endstep %}
{% step %}
## Inspect authorised retained geography
Use the time window and pages of up to 100 retained records.
Read the exact authorised match count; saved views and lifecycle hand-offs are excluded from missing-geometry/time observations.
Open a feature's exact linked source and read:
* Confidence
* Provenance
* Temporal precision
* CRS
* Handling
Detail shows 20 features and states when more remain; inaccessible records are not represented as absent.
{% endstep %}
{% step %}
## Retain an annotation
Choose **Point**, **LineString** or **Polygon**, enter explicit longitude,latitude coordinates and confirm their current order and plotted location.
Optionally resolve a current Requirement, Collection plan, Analysis, Product or retained Material before pinning its canonical ID, version and hash.
State attribution, handling and reason before retaining.
{% endstep %}
{% step %}
## Attest a workspace area
A Manager can add or change retained workspace area context with a source description, non-future observed UTC time and declared precision.
After workspace creation, select an authorised retained geographic record on Map and copy the full record ID, current version and SHA-256 plus an exact Point feature ID from **Selected record**.
Workspace details rechecks that current point, coordinates, source quality, access and handling; copying identifiers does not itself approve an Operations pin.
{% endstep %}
{% step %}
## Promote retained material
Use **Acquire governed material** to follow Ingest and return with the exact material ID/version.
Declare:
* Source CRS and field mapping
* x/longitude then y/latitude order
* Attribution
* Handling
* Reason
CORTEX re-reads the governed original; validation preserves source identity and hash and does not turn a browser-only overlay into evidence.
{% endstep %}
{% step %}
## Retain analysis, view or hand-off
Select exact retained layers for bounded distance, area, buffer, containment or summary analysis.
Read every retained parameter and quality statement, including:
* Bounded cells
* Per-input counts
* Geometry distribution
* Daily comparison when produced
Save extent, time, selection and permitted layer visibility/opacity/order, or create a linked hand-off to the existing Requirement, Collection, Analysis or Product workflow.
{% endstep %}
{% step %}
## Manage scope and cleanup
Use **Clear layers** when finished.
To change the declaration, select **Clear map** and change handling; current temporary overlays are removed first.
A retained layer remains in its repository and history.
{% endstep %}
{% endstepper %}
## Check the result
* Does the declaration cover every displayed dataset and the workspace floor?
* Are coordinates and the intended area correct?
* Have I checked source provenance independently of the drawing?
* Do I need a retained evidence record rather than a temporary overlay?
* Have I cleared layers before changing handling or leaving shared equipment?
## If you get stuck
Why can I sign in as an organisation owner but still lack mapping?
Organisation administration, workspace membership and mapping operations are separate grants.
Read **Workspace access**. If `mapping.read` is missing, use **Users and access** to review the identity grant and active workspace role. If it is present, read the detailed source status before changing policy.
Where do I configure mapping?
Use the **Configure mapping** actions on the Map page.
* **Grant mapping access** opens Users and access.
* **Workspace map feature** opens the selected workspace feature settings.
* **Internet policy** opens the organisation control.
* **Sources & packages** appears with `mapping.packages.manage`.
* **Node & capabilities** appears with `configuration.inspect`.
The browser does not accept arbitrary provider URLs or credentials; provider sources remain reviewed signed node configuration.
How do I recover a failed tile source?
Read the base-source status and select **Use local outline**.
Bundled Natural Earth country outlines and available local place labels load beneath your overlays, preserving the current extent. The outline is broad context, not street or imagery detail.
If local assets also fail, contact the operator. Recovery never enables a public provider or bypasses Online, handling or workspace policy.
Why was an import rejected?
Read the error and check:
* File size
* Required CSV headers
* Finite WGS84 coordinates
* Closed polygon rings
* Feature/coordinate limits
Remove a layer before exceeding eight.
Correct the actual source safely; do not assume a partially accepted dataset.
Why can I preview a file but not retain it?
Temporary preview accepts only its bounded browser formats.
Retention requires an already ingested, authorised material version, explicit CRS/field mapping, coordinate-order confirmation, attribution, handling and Mapping write permission.
Use Ingest first; do not cite the temporary overlay as evidence.
Why is a workspace list-only in the atlas?
The workspace atlas pins only a current exact Geographic Point link that remains authorised and meets the 1,000-metre, Medium/High confidence, bounded-time and 90-day area policy.
Mapped, Unknown and Unmapped status labels use the same meaning in the list and map legend.
Use **Locate on map** or a numbered pin to select an eligible workspace; keyboard selection stays available through the equivalent list. On a narrow screen, **Hide list** exposes the full map and **Show list** restores every authorised row.
Legacy, manual, stale, changed or inaccessible retained areas are labelled Unknown and stay in the list. A workspace with no retained area is Unmapped.
Search, workspace selection and Details remain available. These display controls do not change retained records, access or handling, and a pin is retained area-of-interest context, never a live or operational source-item location.
Why is a retained workspace area list-only in Operations?
Legacy and manual context stays available for ordinary workspace preview but needs a current exact Point link for an Operations pin.
The declaration and source must meet the 1,000-metre, Medium/High confidence, bounded-time and 90-day policy.
Changed, blocked-quality, stale, coarse or inaccessible sources fail closed.
This policy still describes a source-linked workspace area-of-interest assertion, never a live operational or source-item location.
Why is a package or imagery layer unavailable?
Read whether it is offline, blocked by policy, unconfigured, unreachable, outside coverage or inactive.
Operators must review credentials, licence, checksum, expiry, source health and deployment mode.
CORTEX does not silently contact another provider or scrape public tiles.
Why did a saved layer not reopen?
A saved view never stores temporary bytes and restores only layer IDs still present and permitted.
Temporary settings work only while that exact layer remains in the same tab.
CORTEX discards unavailable IDs, restores at most one base map and uses the local outline if no saved base remains available.
Where did my layers go after navigation?
Temporary layers are intentionally cleared on disposal/navigation, with no localStorage or server evidence copy.
Reimport only under the correct handling; use the separate evidence workflow for material that must be retained.
## Responsibility and limits
* The operator imports, verifies, activates and retires licensed local packages or configures reviewed online sources. Package state, checksum, extent, zoom, timestamps, licence and disk use are retained; broken or stale assets fall back visibly.
* Analysts declare handling, retain source attribution and evaluate meaning. Derived geometry is descriptive and reproducible, not a causal finding or automated target decision.
* Online tile requests reveal bounded viewport coordinates to the configured gateway. No overlay labels or record bodies are forwarded; Offline makes no external tile or availability request.
**Reference and scope:** Implementation guidance supporting geographic context and assessment in JDP 2-00 (4th ed.), 7.6–7.11. The map is an exploration aid, not automated JIPOE, targeting or a doctrine-prescribed tool.
## Related workflows
* [Find evidence and select exact retained passages](/sources-and-evidence/memory.md)
* [Preserve an original and review processing](/workflow-guides/collection/ingest.md)
* [Work through connection and deployment limits](/workflow-guides/assurance/offline.md)