Elevation & Contour Analysis for India
Is this land high enough to stay dry? Get the min, mean, and max elevation above sea level, terrain cross-sections, and 10m contour lines for any plot in India — from NASA's 30m elevation data.
What is elevation, and why does it anchor everything else?
Elevation is the height of the land above mean sea level, measured in metres. It is the first number behind flood risk, wind load, infrastructure access, and even seismic amplification. Most other land risk parameters become useful only once elevation is known.
The three elevation ranges that matter in India
Below 10 metres — Very Low Elevation. This is the flood zone. Coastal Andhra Pradesh, the Sundarbans, the Krishna and Godavari deltas, large parts of Kerala backwater areas, and the Mumbai reclaimed land tracts all sit here. Storm surge during cyclones can push seawater inland by 5–15 km on this kind of low-lying coastal land. The 2018 Kerala floods and the 2024 Andhra Pradesh floods both hit low-elevation parcels disproportionately.
10 to 1500 metres — Normal Elevation. The vast majority of buildable India sits here: the Deccan plateau (around 500–700 m), the Indo-Gangetic plains (100–300 m), most of peninsular South India (300–900 m), and the inland Northeast (200–800 m). No elevation-related red flags. Standard construction practices and IS code base assumptions apply. Hyderabad sits at ~542 m, Bangalore at ~920 m, Pune at ~560 m — all comfortably within the “normal” range.
Above 1500 metres — High Elevation. Hill stations and Himalayan terrain. Construction logistics change significantly: cold-weather concrete pouring, frost protection for foundations, restricted material transport, and longer project timelines. IS 875 wind speed maps and IS 1893 seismic amplification factors both vary with altitude. Shimla sits at ~2200 m, Manali at ~2050 m, Ooty at ~2240 m, Munnar at ~1600 m — all in the high-elevation construction regime.
The internal spread — max minus min
Mean elevation is one number; the spread between max and min within the same plot is another. A 15 m elevation spread inside a single 1-acre plot is significant earthwork — even if mean slope looks moderate. The spread reveals the true internal gradient that mean slope can flatten out. It is the number that tells you whether the plot is genuinely buildable as-is or whether the brochure photos hid a sharp drop along one edge. Plots advertised as “level” in Bangalore’s western suburbs often have 8–12 m internal spread once measured — a fact that only shows up after the topographic survey.
How elevation drives flood risk
Low elevation is the single strongest leading indicator of flood exposure in India. The reasons are physical:
- Drainage gravity. Water flows downhill. A plot at 3 m above sea level has nowhere to drain to once the surrounding land is also flooded.
- Storm surge. Cyclones push seawater inland — Cyclone Phailin in 2013, Fani in 2019, and Michaung in 2023 all caused storm surges of 2–5 m. Plots below this height are flooded directly.
- Monsoon backflow. Coastal rivers in flood season can reverse direction near the mouth, pushing water up into low-lying tracts that are nominally upstream.
- Groundwater rise. In low-elevation alluvial land, monsoon raises the water table to within 1–2 m of the surface — even without surface flooding, this saturates the soil and reduces foundation bearing capacity.
Why measured elevation beats “looks high to me”
The eye is poor at judging elevation, especially relative to sea level. A plot that “feels high” because the road climbs up to it may actually sit at 6 m above MSL — well within the flood zone. A plot in a Bengaluru suburb that “feels flat” can be at 950 m elevation, with the entire city on a plateau. Measured elevation from satellite-derived data is the only honest baseline — and it is the same data NRSC and the central government use for disaster planning.
What do these numbers mean?
The result card shows four values — min, mean, max, and the internal spread (max minus min) — plus two terrain cross-section profiles. Each tells you something different about the plot.
How the analysis works
Three steps. Under one second. No setup.
You mark the plot
Draw the exact boundary on the map, drop a pin at the centre, or paste an address. Works for plots from 1 cent to 100 acres anywhere in India.
We read NASA's 30m elevation
Your plot is overlaid on NASADEM — NASA’s void-filled 30m elevation grid from the SRTM 2000 shuttle mission. We extract every elevation pixel inside your boundary.
You see min, mean, max — cross-sections and contour lines
We return the lowest, average, and highest elevation in metres, a verdict (Very Low / Normal / High), two terrain cross-section profiles (W→E and N→S), and contour lines at 10m intervals overlaid directly on the map and clipped to your plot boundary. The section cut-planes are shown as dashed lines.
Methodology and data sources
We use NASA elevation data directly. No interpolation, no models, no proprietary processing.
Where the data comes from
The single source is NASADEM HGT v001 — NASA’s reprocessed, void-filled version of the SRTM 2000 shuttle radar elevation data. Resolution is 1 arc-second, roughly 30 metres per pixel on the ground.
How we compute the three values
- Read the elevation window covering your plot from
elevation.tif(4.9 GB India-wide int16+ZSTD COG, 438 NASADEM tiles mosaicked). - Identify every elevation pixel falling inside your geometry.
min_elevation_m = nanmin(valid pixels)mean_elevation_m = nanmean(valid pixels)max_elevation_m = nanmax(valid pixels)- Verdict is applied to mean elevation.
How the cross-section profiles are computed
Two terrain profiles are extracted from the same pixel window:
- W→E profile: The middle third of pixel rows is averaged column-by-column, giving a west-to-east elevation transect through the centre of the plot. Interior NaN gaps (masked pixels at polygon boundaries) are filled by linear interpolation. The result is resampled to 40 points for consistent chart width.
- N→S profile: The same logic applied to the middle third of pixel columns, averaged row-by-row, giving a north-to-south transect.
- The Y-axis of each chart is zoomed to the local elevation range (not sea level) so terrain variation within the plot is always visible, even for small relief.
- The two section cut-planes are shown as dashed blue lines on the map so you can see exactly which slice each chart represents.
Verdict thresholds
Below 10 m mean is flagged as “Very Low Elevation” — a flood risk indicator. 10–1500 m is “Normal Elevation” — no elevation-related red flags. Above 1500 m is “High Elevation” — hill-station construction regime, IS 875 wind and IS 1893 seismic amplification considerations apply.
How contour lines are generated
- A padded elevation window is extracted from
elevation.tifaround your plot. gdal_contourgenerates contour lines at 10m intervals from that window.- Lines are clipped to your plot boundary (polygon inputs) or a 500m radius circle (pin inputs).
- Each line is labelled with its elevation in metres. Labels are placed at the midpoint of each clipped segment, so a label appears even if only a short section of a contour crosses your plot corner.
- Contour generation is skipped automatically if your bounding box is wider than 50km — the output would be too dense to be useful.
Coverage and limitations
- Pan-India coverage. 438 NASADEM tiles cover 8–38°N, 68–98°E — all of India and surrounding territories.
- Vertical accuracy. NASADEM has a global mean elevation error around 5 m, typically better (1–3 m) on open flat terrain and worse on steep, vegetated, or built-up terrain.
- Vintage. NASADEM is based on SRTM 2000 imagery. Recent earthwork (post-2000 fills, large excavations) is not in the data.
- Water body overlap. If a drawn polygon partially overlaps a river, lake, or reservoir, the tool proceeds with analysis but shows a caution — elevation pixels over water surfaces are included in the profile and may reduce accuracy. Pin drops directly on a water body are rejected outright.
