Corridor Mapping and Route Planning
Purpose
Corridor Mapping and Route Planning identifies optimal transportation, utility, or recreational corridor routes that balance cost, environmental sensitivity, and stakeholder constraints. Generates multiple routing alternatives and comparative analysis.
Typical Questions This Tool Helps Answer
- Which route corridor minimizes combined environmental impact, terrain construction cost, and stakeholder conflict under our stated constraint priorities?
- How do the alternative corridor routes compare against each other when different constraint weights or thresholds are applied?
- Which corridor segment has the highest conflict concentration and requires the most detailed engineering and permitting review?
Background
Terrain siting workflows convert topographic and contextual constraints into suitability or conflict surfaces. The methodological goal is to compress many physical and operational factors into transparent, reviewable decision layers.
Because suitability is relative to assumptions, the recommended practice is to run sensitivity scenarios and compare candidate zones under alternative thresholds before final siting commitments.
Corridor mapping intelligence consolidates terrain, access, and constraint surfaces into reviewable corridor alternatives. Background interpretation should emphasize trade-off transparency rather than single-score dominance.
Methodological Considerations
- Treat suitability/conflict scores as relative rankings under stated assumptions.
- Run threshold sensitivity tests to identify stable candidate zones.
- Preserve assumptions and parameter profiles in decision records for reproducibility.
Practical Interpretation Pitfalls
Over-interpreting a single scoring run as a final siting decision can conceal constraint trade-offs that emerge under alternate but reasonable parameter settings.
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
| dem | Raster | Yes | Digital elevation model (defines slope cost) |
| start_features | Vector (point or polygon) | Yes | Corridor start terminals. |
| end_features | Vector (point or polygon) | Yes | Corridor end terminals. |
| constraints | Vector (polygon) | No | Optional exclusion zones. |
Parameters
- cost_profile (optional):
slope_only,slope_roughness,conservative. - terminal_anchor_strategy (optional):
mixed,centroid_only,boundary_only. - corridor_tolerance (optional): fraction above optimum cost used to define corridor suitability band.
- output_prefix (optional): output naming prefix.
Outputs
Output artifact keys below are runtime outputs, not input parameters.
| Artifact | Runtime Output Key | Type | Description |
|---|---|---|---|
| Cost surface raster | cost_surface | Raster | Traversal impedance surface. |
| Accumulated cost raster | accumulated_cost | Raster | Cost-to-reach map from start anchor. |
| Optimal route vector | optimal_route | Vector | Best route polyline and route metrics. |
| Corridor suitability raster | corridor_suitability | Raster | Feasible corridor area around best route based on tolerance. |
| Summary contract | summary | JSON | Full run contract and interpretation diagnostics. |
| Optional report | html_report | HTML | Stakeholder-ready report artifact. |
Route metrics in optimal output
- Route length
- Mean slope along route
- Accumulated route cost
- Cost profile used
Example
import whitebox_workflows as wbw
env = wbw.WbEnvironment()
env.corridor_mapping_intelligence(
dem="dem_10m.tif",
start_features="route_start.gpkg",
end_features="route_end.gpkg",
constraints="protected_areas.gpkg",
cost_profile="slope_roughness",
terminal_anchor_strategy="mixed",
corridor_tolerance=0.15,
output_prefix="outputs/corridor"
)
References
- Dijkstra, E. W. (1959). "A Note on Two Problems in Connexion with Graphs." Numerische Mathematik 1(1), 269–271.
Parameter Interaction Notes
Planning outcomes are sensitive to profile, terminal strategy, and tolerance settings.
- Conservative profile tends to avoid rough terrain more aggressively.
- Anchor strategy can shift route origin/destination cells when polygons are used.
- Larger tolerance produces wider corridors suitable for alternatives screening.
QA and Acceptance Criteria
Use a staged acceptance approach for Corridor Mapping and Route Planning:
- Confirm endpoints and optional constraints are valid and in compatible CRS.
- Confirm route output is generated and includes expected metrics.
- Confirm corridor suitability aligns with project tolerance intent.
- Validate summary interpretation notes for anchor stability and reprojection actions.
Recommended acceptance checks:
- Route is present and continuous.
- Cost and suitability outputs are non-empty for feasible scenarios.
- Summary output paths align with generated artifacts.
Advanced Operational Guidance
For production deployment of Corridor Mapping and Route Planning:
- Use centroid-only anchors when strict repeatability is required.
- Keep constraints layer governance-controlled for design review cycles.
- Archive summary JSON and report for route approval packages.
Implementation Patterns
Common implementation patterns with Corridor Mapping and Route Planning:
- Baseline corridor feasibility run.
- Tolerance sweep for corridor-width decision support.
- Constraint update rerun for permitting iterations.
Related Tools
Use Corridor Mapping and Route Planning together with upstream conditioning and downstream validation tools in the same bundle to ensure end-to-end consistency and stronger decision confidence.
Common Questions
Q: Why did the route move after changing anchor strategy?
A: Polygon terminals can provide many candidate anchor points; strategy controls how candidates are chosen.
Q: Why is corridor area much larger than expected?
A: Corridor area scales with corridor_tolerance; lowering tolerance tightens the feasible band.
Q: Why are some areas completely avoided?
A: Constraint polygons are rasterized as impassable cells.