Utility Corridor Access Planning
What This Tool Does
Utility Corridor Access Planning prioritizes encroachment hotspots near utility corridors and pairs them with the nearest access points for field-response planning.
Typical Questions This Tool Helps Answer
- Which encroachments are highest priority based on corridor proximity and access difficulty?
- What is the nearest viable access point for each hotspot and what response SLA category applies?
- What ranked field-response queue should operations execute first this week?
When To Use
- Utility corridor patrol planning
- Encroachment triage for line, pipe, or right-of-way assets
- Dispatch queue generation for maintenance response teams
What You Need
| Input | Description |
|---|---|
| Corridor lines | Utility corridor centerlines. |
| Encroachment observations | Points, lines, or polygons describing the threat. |
| Access points | Field access points used to plan response. |
Key Settings
| Setting | Default | Guidance |
|---|---|---|
corridor_influence_distance | 30.0 | How far from the corridor a hotspot can be and still be retained. |
high_risk_distance | 10.0 | Distance used to define the highest-risk condition. |
What You Get
| Deliverable | Format | Description |
|---|---|---|
hotspots | Vector | Hotspot points sorted by priority. |
priority_csv | CSV | Ranked response queue. |
planning_report | JSON | Planning summary report. |
summary | JSON | Alias for the planning report. |
response_queue_csv | CSV | Optional dispatch-ready queue with response guidance. |
html_report | HTML | Optional dashboard report. |
The hotspot layer includes corridor, access, risk, priority, SLA, access-difficulty, and lineage fields. The CSV lists the same records in ranked order.
Runtime Output Keys
result.outputs["hotspots"]
result.outputs["priority_csv"]
result.outputs["planning_report"]
result.outputs["summary"]
result.outputs["response_queue_csv"]
result.outputs["html_report"]
Common Questions
Q: Which output should I review first for decision-making?
A: Start with priority_csv and planning_report.counts_by_priority_band, then confirm urgency in hotspot PRIORITY and SLA_HOURS.
Q: What is a common interpretation mistake?
A: Treating distance to corridor alone as urgency. Priority combines RISK_SCORE, ACCESS_DIST, and corridor proximity.
Q: Which settings most change outcomes?
A: corridor_influence_distance and high_risk_distance usually drive the biggest shift in critical hotspot counts.
Q: How should operations use the outputs?
A: Use response_queue_csv for dispatch sequencing and validate top critical records with field confirmation before issuing final work orders.
Results Delivery Checklist
- The corridor, encroachment, and access layers were checked for alignment
-
hotspotswas reviewed in GIS software -
The top rows in
priority_csvwere confirmed - The chosen response queue matches the operations plan
Operational Notes
- This workflow does not build or traverse a road-routing graph.
- One-way routing parameters (for example
one_way_fieldwith FT/TF/B values) are not used. - Prioritize sensitivity testing on
corridor_influence_distanceandhigh_risk_distancebefore locking production thresholds.
Related Tools
network_readiness_and_diagnostics_intelligenceservice_area_planning_and_coverage_optimizationemergency_scenario_routing_and_accessibility_simulator
When To Use This Workflow
Use Utility Corridor Access Planning when you need a repeatable hotspot-prioritization and access-assignment package for dispatch and field-response planning.