Venues

Admin → Venues (/admin/venues) defines reusable locations — a stadium, a port, a campus, a border stretch — so that spinning up a mission at that site is a one-click operation. Each venue carries a bounding polygon, a contact, attached cameras, and a free-form notes field.

Requires admin or superadmin, or the venue_creator custom role.

The venue list

Columns:

Column	Source	Notes
Name	`Venue.name`	Unique within the org.
Type	`Venue.type`	Stadium, Arena, Port, Airfield, Campus, Border, Other.
Area	derived	Polygon area in km². Computed at save time.
Cameras	`Venue.cameraIds.length`	Count of VMS cameras attached.
Updated	`Venue.updatedOn`	Last edit.
Actions	—	Open detail, launch tracer, delete.

A Launch demo button sits in the top-right — it opens a standalone full-screen 3D demo of a sample venue to showcase the overlay system. It is safe to click; no data is written.

Create a venue

Click New venue. The form is a two-step process:

Step 1 — Metadata

Name (required) — e.g. Wembley Stadium.
Type — pick-list from VENUE_TYPES: Stadium, Arena, Concert Hall, Convention Center, Airport, Heliport, Port, Warehouse, Campus, Border, Critical Infra, Energy Plant, Other.
Contact — a name and phone. Displayed on mission-active missions for the comms officer to dial if escalation is needed.
Address — reverse-geocoded from the polygon centroid but editable.
Notes — free-form markdown. Useful for gate codes, parking rules, radio frequencies.

Step 2 — Polygon

Click Draw polygon on map to switch to the drawing view. The map defaults to the org’s country centroid. Click once per vertex, double-click to close. The polygon is stored as a GeoJSON Polygon on Venue.boundary. You can also paste a GeoJSON fragment directly into the text area below the map for vetted sites coming from GIS.

Save writes the venue to /organizations/{orgId}/venues/{venueId}.

Venue detail

Clicking a row opens /admin/venues/:id. The detail view has three sections:

Profile

Same fields as the create form, plus the read-only createdOn / createdBy. Click Edit to modify any field.

Attached VMS cameras

IP cameras previously provisioned on the mission drone-stream tile can be attached here and will be auto-added to every mission that uses this venue. Fields per camera: name, RTSP URL, position (lat/lng/alt), FOV cone. Capacity is capped by ORG_PLAN_LIMITS[plan].maxIpCameras — Guardian is zero, Tactical gets four, Command sixteen, Sovereign unlimited.

Sub-areas (aspirational)

Nested zones within the venue (a stadium’s pitch vs. stands vs. car park). Roadmapped for the 2026-Q3 venue intelligence release. The data model already has a subAreas field — the UI will follow.

Launching the open-area tracer

The Open tracer action on a venue row loads /admin/venues/:id/tracer — a photoreal 3D tile of the venue with the polygon overlaid. Useful for walking the boundary with a stakeholder before a mission. Saves are disabled in tracer mode; it is a read-only review.

Using a venue at mission-create time

On the mission-create wizard, tick the Venue box and pick a venue from the dropdown. ARGUS then:

Centres the mission map on the venue centroid.
Sets the mission geofence to the venue polygon.
Auto-adds every attached VMS camera to the drone-stream tile.
Pre-fills the mission contact from the venue’s contact.

Manual overrides still work — the venue acts as a starting point, not a lock.

Editing and deleting

Edit — inline form identical to the create flow. Polygon edits open the drawing view with the existing vertices draggable.
Delete — popover-confirmed, soft-delete (deletedOn set). Missions that previously used the venue keep the snapshot of the polygon they were created with, so historical geofences are preserved.