Sites & Geofences
Loading sites and geofences… (skeleton shimmer pauses under reduced motion)
No geofences yet — draw your first
Geofence drawing and management shipped in P1 — polygons and circles, editable after the fact. There's no CSV to import here (a fence is a shape, not a spreadsheet row); draw one on the map or start from a sample.
Sample data draws 3 site boundaries and 3 zone fences across Silloth Yard, North Ridge, and Bridgeport — clear it in one click. Sites-as-records and geofence activation (below) stay visible either way, since they're proposed/design-ahead regardless of what's drawn.
2 units flagged as of last sync. New exceptions won't appear until you reconnect.
| Fence | Shape | Created | Notify | Gear inside | Actions |
|---|---|---|---|---|---|
| Silloth Yard boundary | Polygon | 2026-02-11 | ○ cached | — | |
| North Ridge site | Circle · 420 m | 2026-03-02 | ○ cached | — | |
| Fuel dock | Circle · 150 m | 2026-02-11 | ○ cached | — |
Showing 3 of 14 cached fences. Reconnect to draw, edit, or delete.
238 of 260 units carry a site assignment. 22 — including SS-107, on rent to Ridgeline Construction — aren't assigned to any site. Sites as records, and the assigned-vs-present split above, are a proposed object model (pending a data-model session) — nothing here exists in the schema yet.
Assigned Bridgeport · seen North Ridge — 2 units flagged. This is the whole point of tracking both edges: planning truth (assigned) and observed truth (present) can disagree, and disagreement is worth a human's attention.
Proposed rollup: Geofence hours this period — 41h 20m across these two units, billing-tied via the rental record. Dwell ledger + hours rollup are P2, PR #254.
⚡ If RL-88 exits North Ridge after 6:00 PM ⚡ Then create a task and DM Dana
Same automation engine as every other trigger — Automations — just with a geofence enter/exit condition that doesn't exist yet. This card is illustrative, not a live rule.
P2 also adds a fence-filter map overlay on the fleet map — show only the gear inside a chosen fence, with live per-fence counts (PR #254).
Two shapes: polygon (min 3, max 1,000 vertices) and circle (radius up to 1,000,000 m). Names are 1–255 characters and don't have to be unique. Manage needs admin; every member can view. Notify toggles and gear-inside counts below are P2 — the fields exist, detection doesn't run yet.
| Name | Shape | Created | Notify (◇ P2) | Gear inside (◇ P2) | Actions | |
|---|---|---|---|---|---|---|
| Silloth Yard boundary | Polygon · 14 pts | 2026-02-11 | ✓ Enter ✓ Exit | 182* | ||
| North Ridge site | Circle · 420 m | 2026-03-02 | ✓ Enter ✓ Exit | 36* | ||
| Bridgeport site | Polygon · 9 pts | 2026-03-19 | ○ Enter ✓ Exit | 20* | ||
| Shop bay | Polygon · 5 pts | 2026-02-11 | ○ Enter ○ Exit | 6* | ||
| Fuel dock | Circle · 150 m | 2026-02-11 | ✓ Enter ○ Exit | 2* | ||
| Laydown yard | Polygon · 6 pts | 2026-04-02 | ○ Enter ○ Exit | 14* |
▲ Schematic — not to scale
Tokens: foundation-tokens-vC2e-straight.json (every ratio computed) · gloved 44/48px floors · status = glyph + label, never color alone.
Shipped: geofence P1 manage/draw with real caps (min 3 / max 1,000 vertices; circle ≤1,000,000 m; name ≤255) — verified against monorepo PR #30, 2026-07-09.
Design-ahead, tagged: P2 activation (PR #254 — enter/exit, dwell ledger, automations → task + GearChat DM, live counts, geofence-hours billing).
Proposed: Sites as first-class records + assigned-vs-present dual edges — undesigned in every spec; this screen is the proposal, pending a data-model session.
Geofence RBAC beyond two roles: descoped — launch = admins manage / members view.
← Prototype home