plan_fiber_leadin
Plan diverse fiber lead-in routes from a data center site to a carrier hotel, with indicative build cost and route diversity analysis. Answers how many routes, distance, cost, and shared corridors.
Instructions
Plan N diverse, road-following fibre lead-in routes from a candidate data-center site to a carrier hotel / POP, with indicative build cost and a route-diversity read. Answers "can I get N diverse fibre routes into this site, how far, how much, and where do they share a corridor?". Example: plan_fiber_leadin from="250 Paringa Road, Murarrie QLD" to="20 Wharf Street, Brisbane City QLD" n=4. Params: from (lat,lng OR street address), to (lat,lng OR address — e.g. a NextDC/Equinix POP), n (1-6 routes, default 4), fibre ("720F"|"1440F"), bore_m (river/rail bore length in metres, optional). Returns per-route length_km + GeoJSON geometry, total_route_km, diversity {min_separation_m_midhaul, shared_street_km}, and indicative cost {capex_usd, opex_usd_yr}. INDICATIVE auto-routed road corridors — NOT engineered alignments; subject to survey, DBYD and carrier confirmation. Do NOT use for a single site-suitability score (use analyze_site) or fibre-provider footprints (use get_fiber_intel).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| n | No | Number of diverse routes to plan, 1-6 (default 4) | |
| to | No | Destination carrier hotel/POP as "lat,lng" OR an address, e.g. "20 Wharf Street, Brisbane City QLD" | |
| from | No | Origin site as "lat,lng" OR a street address, e.g. "250 Paringa Road, Murarrie QLD" | |
| fibre | No | Fibre count spec for cost estimate: "720F" or "1440F" | |
| bore_m | No | River/rail bore length in metres to add to the route, 0-100000 (optional) |