1 Problem Statement

Chennai is India's second-largest submarine cable landing hub after Mumbai, with 5 operational cable systems and 3+ planned.[1] However, all existing Cable Landing Stations (CLS) in Chennai are concentrated in the Santhome Beach / MRC Nagar area on the northern coast, creating a single point of geographic failure. The MIST cable system (200 Tbps, 12 fiber pairs) landed at this same location in 2024.[2]

Meanwhile, Ambattur Industrial Estate has emerged as Chennai's premier data centre cluster with 12+ facilities and 200+ MW capacity[3], yet all terrestrial fiber routes from cable landing points converge through common corridors, creating vulnerability to urban disruptions (road construction, flooding, metro expansion).

This proposal addresses the critical need for a geographically diverse submarine cable landing on Chennai's southern coast (ECR, Neelankarai–Uthandi) with an optimised, fully analysed terrestrial route to data centre facilities at Nxtra Data Centre and NTT Global Data Centers' Ambattur campus.

2 Scope of Work

This tool and analysis covers the entire cable route lifecycle from sea to data centre:

1. Beach Manhole (BMH) Placement: Identifying non-eroding beach locations on ECR's seaward side for submarine cable termination, with CRZ Notification 2019 compliance[4]
2. Landing Station Site Assessment: CRZ zone verification, geology, soil bearing capacity, flood risk, and master plan zoning at candidate ECR properties
3. Terrestrial Route Optimisation: Shortest-path computation via Google Maps Directions API, with 18-layer geospatial obstacle analysis
4. Crossing Identification & Engineering: Automated detection of every highway, railway, canal, metro corridor, HT line, and water body crossing along the route
5. Manhole Schedule Generation: Precise placement every 250 metres with additional road-crossing manholes on both sides of each crossing
6. Regulatory Mapping: Identification of all NOC-requiring authorities with specific regulation citations
7. Avoid-and-Reroute: Interactive zone avoidance with automatic route recalculation

3 Methodology & Algorithms

3.1 Route Computation

Routes are computed using the Google Maps Directions API (driving mode) to follow actual road networks. The API uses Dijkstra's algorithm variant with real-time road graph data, ensuring routes follow physically traversable paths rather than straight-line approximations. For each source location, two routes are simultaneously computed to both destination data centres.

3.2 Manhole Placement Algorithm

The decoded route polyline (typically 500–2000 coordinate points for a 30km route) is traversed using the Haversine distance formula (via google.maps.geometry.spherical.computeDistanceBetween()) with linear interpolation to place manholes at exact 250m intervals. At detected road crossings, additional manholes are inserted 5m before and after the crossing point. These are marked as "Road Crossing" type in the manhole schedule.

3.3 Crossing Detection: Hybrid Client-Server Architecture

Crossing detection uses a two-tier approach for maximum coverage and accuracy:

• Client-side (known features): Major named roads and landmarks (ECR, Buckingham Canal, GST Road NH45, Kelambakkam-Vandalur Road, Outer Ring Road) are defined as polyline segments with geographic coordinates. The route path is tested for proximity to these segments using perpendicular distance to line segment computation. When the route passes within the threshold distance (80–120m depending on feature width), a crossing is flagged.
• Server-side (Supabase PostGIS): The route is sampled at ~100m intervals, generating 150–350 sample points for a typical 30km route. Each point is checked against 18 geospatial layers via Supabase RPC functions backed by PostGIS spatial queries (ST_Contains, ST_DWithin, ST_Distance). Results are deduplicated to consolidate consecutive detections of the same feature into a single crossing record.

3.4 Zone Avoidance & Rerouting

When a user selects zones to avoid (e.g., a Ramsar site or a critical railway crossing), the system generates bypass waypoints offset perpendicular to the avoid zone and injects them into the Directions API request. The API's road-graph routing naturally finds the next-best path that avoids the flagged area. All crossing analysis and manhole placement is then re-executed on the new route.

4 Geospatial Data Sources

This analysis is powered by an extensive geospatial data infrastructure developed by the LandLens platform. Every data point is sourced from authoritative government or scientific databases. No data is estimated or approximated.

Data Layer	Source	Coverage	Used For
CMRL Metro	TN-GIS WFS + CMRL Official Data[5]	172 stations, 465 route segments, 5 corridors	Metro crossing detection, TOD zone analysis
Railway Lines	Supabase PostGIS (Southern Railway data)	Full Chennai suburban + main line network	Railway crossing detection, 30m setback analysis
Water Bodies	TN-GIS + Supabase[5]	119,797 mapped water features (lakes, canals, rivers, tanks)	Canal/river crossing detection, buffer zones
CRZ Zones	TNSCZMA / NCSCM CZMP[6]	9 CRZ sub-categories (1A, 1B, 2, 3A, 3B, 4A, 4B, IV-A, Mangrove)	Beach landing CRZ classification, NDZ distance
Cadastral Parcels	TN-GIS WMS/WFS[5]	6,666,665 survey parcels across 38 TN districts	Property identification at landing site
Geology	Geological Survey of India via TN-GIS	Full TN coverage: rock type, lithology, stratigraphic age	Soil/rock assessment for NDD feasibility
Flood Zones	TN-GIS flood inundation mapping	Chennai metropolitan flood-prone areas	Cable burial depth and waterproofing requirements
Ramsar Sites	MoEFCC / Ramsar Convention[7]	Pallikaranai Marshland + 1km NGT buffer	Route blocker (mandatory avoidance)
Reserve Forests	TN Forest Dept via Supabase	All TN reserve forests with 5km buffer	Route blocker (mandatory avoidance)
ASI Monuments	Archaeological Survey of India	Protected monuments with 100m/200m/300m zones	Excavation restriction zones
CMWSSB Pipelines	Chennai Metro Water Supply Board[8]	Metrowater + sewage pipeline networks (Chennai metro)	Avoid existing underground infrastructure
HT Power Lines	TANGEDCO data via Supabase	High Tension line corridors	HT line crossing detection, safety clearance
Airport Zones	AAI CCZM data (8 airports)[9]	3,805 detailed grid cells + 4,401 basic cells	Height restriction check (relevant for above-ground CLS)
Road Widenings	CMDA / Highways Dept	Proposed road widening zones (3 categories)	Future-proofing: cable may need relocation
Eco-Sensitive Zones	MoEFCC notification data	All TN ESZ boundaries	Restricted excavation areas
Aquifer Zones	CGWB / TN-GIS	Chennai metropolitan aquifer boundaries	High water table (affects NDD depth)
Swamp/Wetlands	TN-GIS environmental data	Seasonal wetland boundaries	Construction feasibility (waterlogged ground)
HACA Areas	Hill Area Conservation Authority	Ecologically sensitive hill areas	Restricted ground disturbance zones

5 Key Infrastructure Crossings

The terrestrial cable route from ECR to Ambattur (approximately 30–35 km) must navigate through some of Chennai's most critical infrastructure corridors. Each crossing requires specific engineering methods and regulatory approvals:

5.1 ECR (East Coast Road) Crossing

The cable must cross ECR from the seaward BMH to the landing station property. ECR is a State Highway under the Tamil Nadu Highways Department. Crossing requires Horizontal Directional Drilling (HDD) at minimum depth per highway norms to avoid carriageway disturbance. Since the seaward side falls under CRZ regulations, dual clearance from both State Highways Dept and TNSCZMA is required.[4]

5.2 Buckingham Canal Crossing

The Buckingham Canal (National Waterway 4) runs parallel to ECR approximately 200–400m inland.[10] Two methods are evaluated: (a) Bridge clamping, which attaches OFC ducts to existing bridge structures and requires structural load assessment by PWD; (b) HDD beneath the canal bed, which maintains minimum depth under the waterbed. Bridge clamping is preferred for cost and speed but requires PWD Water Resources Dept approval.

5.3 Chennai Metro Rail (CMRL) Corridor Crossings

The route intersects multiple CMRL corridors (Corridors 1–5). Our Supabase database contains 172 station locations and 465 route segments with construction type classification (underground/elevated). CMRL requires detailed method statements and drawings. No trenching is permitted within safe clearance distance of pier foundations and viaduct pillars. Cable must be routed via NDD at CMRL-approved depth.[11]

5.4 GST Road (NH45) Crossing

The Grand Southern Trunk Road (now NH32/NH45) is a National Highway under NHAI jurisdiction. There is a strict prohibition on open trenching. Only NDD or micro-tunneling methods are accepted. A detailed proposal including alignment drawings, depth profile, and restoration plan must be submitted to NHAI.[12]

5.5 Railway Line Crossings

Chennai's suburban railway network (Southern Railway) requires a 30-metre setback from tracks. Our system detects railway proximity using PostGIS spatial queries against digitised railway line geometry. Railway crossings mandate HDD beneath the track bed with Ministry of Railways NOC and detailed alignment drawings.[12]

5.6 Kelambakkam–Vandalur Road & Outer Ring Road

These State Highway crossings require State Highways Department approval. The Outer Ring Road / bypass corridor from Perungalathur to Ambattur should be evaluated for existing OFC duct corridors or common utility pits, since shared infrastructure can significantly reduce cost and approval timelines.

6 Regulatory Framework

Submarine cable landing and terrestrial routing in India involves a complex multi-authority approval process. We have mapped every applicable regulation:

Regulation / Authority	Applicable Act / Rule	Requirement
CRZ Clearance	CRZ Notification 2019, Environment (Protection) Act 1986[4]	MoEFCC + TNSCZMA clearance for BMH in coastal zone. Precedent: MIST cable at Santhome Beach (2024)
Submarine Cable License	ILD License (DoT) / Telecom (Captive Services) Rules 2025[13]	International Long Distance license or Captive authorization for subsea cable ownership
Right of Way	Telecommunications (RoW) Rules 2024[14]	Single-window via Gati Shakti Sanchar Portal. Fee: Rs. 1,000/km
National Highway Crossing	NHAI Road Crossing Policy[12]	No open trenching. Mandatory HDD. Detailed alignment + restoration plan
State Highway Crossing	TN Highways Dept G.O.[15]	RoW permission for OFC along state highways
Railway Crossing	Indian Railways Act / Southern Railway[12]	30m setback. NOC + alignment drawings. HDD mandatory
Metro Rail Proximity	CMRL Guidelines[11]	Method statement + drawings. Safe clearance from pier foundations
Canal / Waterway Crossing	PWD Water Resources Dept[10]	Bridge clamping or HDD approval. Structural assessment for bridge attachment
HT Line Crossing	TANGEDCO / Electricity Act 2003	NOC for crossing HT line corridors. Safety clearance maintained
Municipal Road Cutting	Chennai Corporation / Greater Chennai Corporation Act	Permission for road cutting in municipal areas
Environmental Clearance	EIA Notification 2006 (if in ESZ/Ramsar buffer)	Environmental Impact Assessment for work in sensitive zones

7 Technical Specifications

• Submarine Cable: Multi-fiber pair armoured submarine cable with UV-resistant polyethylene sheathing. Steel wire armour for burial in shallow waters. Typical capacity: 12–48 fiber pairs.
• Beach Manhole (BMH): Reinforced concrete chamber (2.5m x 2.5m x 2.5m minimum) at cable sea-entry point. Must be constructed in non-eroding area per MOEF recommendation (MIST cable precedent).[2] Waterproof with cathodic protection.
• Terrestrial Duct: HDPE duct, 40mm OD for fiber cable. Minimum burial depth: 1.2m under roads, 2.0m under railways, 3.0m under water bodies.
• Cable Laying Method: NDD (No-Digging / Horizontal Directional Drilling) throughout. Zero surface disruption.
• Manhole Spacing: Every 250 metres. Additional manholes on both sides of every road crossing.
• Bridge Crossings: Cable routed along the side of the bridge or through bottom clamping, with structural safety assessment and secure fixing.
• Cable Landing Station: 500–1000 sqm facility with dedicated power (dual feed), precision cooling, fire suppression, 24/7 security, and carrier-neutral meet-me rooms.

8 Risk Analysis

Risk	Severity	Mitigation
CRZ clearance delay	High	Engage TNSCZMA early. Use MIST cable precedent as reference case
Railway NOC delays	High	Submit detailed drawings upfront. Use Gati Shakti portal for tracking
Pallikaranai Ramsar proximity	Critical	Route avoidance algorithm ensures minimum 1km buffer. Auto-rerouting
Flood zone cable damage	Medium	Enhanced burial depth + waterproof manhole chambers in flood-prone sections
Existing pipeline damage	Medium	CMWSSB pipeline proximity analysis (30m buffer). GPR survey before NDD
Metro expansion conflict	Medium	CMRL Phase 2 corridor data integrated. Route avoids proposed alignments
Urban road widening	Low	Proposed road widening zones checked. Cable placed outside widening envelope

9 Platform Capabilities

This analysis tool is built on the LandLens geospatial intelligence platform by Verified.RealEstate, India's most comprehensive land and property verification system. The platform integrates:

• 6.6 million cadastral survey parcels across all 38 Tamil Nadu districts with full polygon geometry[5]
• 119,797 mapped water bodies including lakes, rivers, canals, tanks, and ponds
• 28+ Supabase PostGIS spatial tables with real-time RPC functions for point-in-polygon, proximity, and buffer analysis
• 18 regulatory check layers simultaneously evaluated at every point along the route
• Google Maps Directions API integration for real road-network routing
• Intelligent caching: every Supabase RPC result cached for 1 hour per coordinate pair to enable rapid re-analysis
• Automatic deduplication: consecutive detections of the same feature collapsed into single crossing records
• Interactive avoid-and-reroute: select any NOC-required zone to bypass, triggering automatic route recalculation and re-analysis

The platform processes approximately 300–500 spatial queries per route analysis (150–350 sampled points x 18 check layers), with results returned in under 60 seconds due to aggressive caching and PostGIS spatial indexing.

10 Cost Estimation Framework

Item	Unit	Estimated Range
Submarine cable (nearshore segment)	Per km	USD 25,000–50,000
Beach Manhole (BMH) construction	Lump sum	INR 15–25 Lakhs
Cable Landing Station (CLS) building	500–1000 sqm	INR 2–5 Crore
Terrestrial NDD cable laying	Per km	INR 8–15 Lakhs
Road crossing (NDD method)	Per crossing	INR 3–8 Lakhs
Railway crossing (HDD)	Per crossing	INR 10–20 Lakhs
Canal/water crossing (HDD or bridge clamp)	Per crossing	INR 5–15 Lakhs
RoW administrative fees	Per km	INR 1,000[14]
Manhole chambers (250m interval)	Per unit	INR 30,000–60,000
Regulatory & consultation costs	Lump sum	INR 25–50 Lakhs
Project management (12–18 months)	Lump sum	INR 30–50 Lakhs
Contingency (15%)	Percentage	15% of total

11 Conclusion

The proposed submarine cable landing on ECR provides critical geographic diversity for Chennai's data connectivity infrastructure. By leveraging LandLens' comprehensive geospatial database of 18+ regulatory layers, 6.6 million cadastral parcels, and real-time PostGIS spatial analysis, this tool provides an unprecedented level of detail for cable route planning, from automated manhole placement to per-crossing regulatory authority mapping.

The combination of Google Maps road-network routing, PostGIS spatial analysis, and a 119,797-record water body database ensures that no crossing or obstacle is missed, while the avoid-and-reroute feature allows stakeholders to interactively evaluate alternative paths in real time.