What's inside your right-of-way that shouldn't be? New

VoltGrid buffers your PLS-CADD conductor geometry into a corridor polygon — default 30 m half-width, yours to change — and intersects it with the parcels, buildings, and roads already loaded in the data hub. Every hit is graded by intersection area, highlighted on the map, and optionally written to the Transmission findings layer.

Corridor buffer (EPSG:3857 metres)Parcels · Buildings · Roads Severity by areaMap highlight Findings write-throughGPKG · DuckDB · Connectors

Land & ROW · Phase 1

The encroachment sweep, from data you already have

No new survey required: the conductor lines come from your PLS-CADD import (with KMZ geometry), the candidate layer is anything FeatureServer-backed — a parcels GeoPackage, a buildings extract, a DuckDB table, or a live connector. Ribbon → TRANSMISSION → FINDINGS → ROW.

Corridor = union of buffered spans — conductor geometry buffered by a metre half-width in EPSG:3857; you pick the width per run.
Intersect any hub layer — polygons or lines from GeoPackage Manager, DuckDB ingest, or the multi-DB connectors; anything that appears as a right-click target.
Severity by intersection area — default ladder 25 / 200 / 1000 m² (minor / major / critical); hits highlight on the map.
Optional findings write — source_analysis=row-encroachment into the same Transmission findings FeatureServer as vegetation and as-built deltas.

/api/row/analyze

POST /api/row/analyze
{
  "conductorDbId":  "plscadd_7f2a",
  "candidateDbId":  "parcels",
  "candidateCollId": "0",
  "bufferMeters":   30,
  "writeFindings":  true
}
→ parcel 118-40-021  1,240 m²  critical
→ barn (bldg 3311)     210 m²  major

In-App Screenshot

Transmission ROW Encroachment Analysis Widget

VoltGrid desktop — Transmission Line Analysis ROW Encroachment widget — ROW Encroachment analysis floating widget shown in default state ready for conductor buffer width, parcel intersection layers, and severity thresholds

Why this matters for ops

From "we should check the ROW" to a ranked worklist

🏠

Structures in the ROW

New sheds, additions, and stacked materials inside the corridor surface as ranked findings — before the annual patrol does.

🌲

Pairs with vegetation

Run it beside ΔNDVI corridor change detection: man-made encroachment and vegetation encroachment in one findings queue.

📄

Land-desk evidence

Area-quantified, severity-graded intersections make the easement conversation concrete — exportable with the rest of your findings.

Honest boundary: requires PLS-CADD imported with KMZ so conductor geometry exists (XML-only has no lines). Findings persist as point centroids; live Overture buildings pull and span-level attribution are roadmap — not shipped.