Introduction to tsunami evacuation distance and terrain slope
Do not use this calculator during an active tsunami warning. When a warning, siren, or natural sign of a tsunami is present, the correct action is to move immediately according to official local guidance, not to stop and calculate. This page is meant for preparedness conversations before an emergency. It offers a simple way to think about one narrow question: if you want to gain a certain amount of elevation and the inland terrain rises at an average rate, how much horizontal distance would that elevation gain imply?
That is a planning question, not a safety guarantee. In a simplified model, elevation gain and average slope can be linked by basic unit conversion. If the land rises 10 meters for every 1 kilometer you travel inland, then gaining 20 meters of elevation would imply about 2 kilometers of travel. The calculator below applies exactly that idea. It compares your current elevation, a target elevation, and an average inland slope, then reports the distance implied by that slope. An optional benchmark field lets you compare the estimate with a route length, map note, or inland distance you already have in mind.
This can be useful when reviewing contour maps, hiking routes, neighborhood street grids, or community preparedness materials. It can also help explain why gentle coastal plains require much longer inland travel than steep headlands. Still, the page should be treated as a worksheet for understanding terrain context, not as a flood model, route selector, hazard-zone boundary, or evacuation instruction. Real tsunami risk depends on many local factors that this calculator does not and cannot represent.
How to use the tsunami elevation and slope inputs
Using the tsunami evacuation distance calculator begins with your current elevation in meters above sea level. This is the approximate elevation of the point where you begin, such as a coastal road, parking area, beach access point, or building entrance. Then enter a target elevation. The target is not produced by the calculator. It is a planning value you choose while studying official guidance, local geography, or preparedness materials. The form does not tell you what target is safe; it only estimates the horizontal distance associated with the difference between the two elevations.
Next, enter the average inland slope in meters of elevation gain per kilometer of inland travel. This number is important because it controls how quickly elevation increases as distance increases. A steep hillside may gain many meters in a short distance, while a broad coastal plain may require much more horizontal travel to gain the same elevation. If you know or want to compare against a particular route length, enter it in the optional inland-distance benchmark field. Leaving that field blank is fine; the main estimate still works.
The calculator returns three ideas in plain language. First, it computes the elevation gain to target, which is simply the positive difference between target elevation and current elevation. Second, it computes the distance implied by the average slope. Third, if you supplied a benchmark, it reports the difference between the benchmark and the estimate. A positive benchmark gap means your benchmark is longer than the slope-based estimate. A negative gap means the benchmark is shorter than the estimate.
Use the result as a prompt for better questions rather than as a decision by itself. If the estimate seems much shorter or much longer than what you see on a map, that may mean the average slope you entered is unrealistic, the route bends around waterways or roads, or the terrain changes sharply instead of rising evenly. In real route planning, distance on paper is only part of the picture. Access, surface quality, stairs, bridges, congestion, mobility needs, and official evacuation maps all matter at least as much.
- Current elevation: where you start, in meters above sea level.
- Target elevation: the higher elevation you want to compare against for planning purposes.
- Average inland slope: average elevation gain per kilometer of inland travel.
- Benchmark distance: an optional route length or inland-distance reference to compare with the estimate.
One small but helpful detail: if the target elevation is already below or equal to the current elevation, the needed elevation gain becomes zero in this model. That means the estimated additional distance to achieve that target elevation is also zero. In other words, the calculator never returns a negative travel distance. It only estimates how much inland distance is implied when more elevation must be gained.
The tsunami slope-to-distance formulas, step by step
The tsunami distance calculation is deliberately simple. First, find the elevation gain needed to reach the target. If the target is below the starting point, the gain is treated as zero because no additional climb is required to meet that target elevation. Then divide that elevation gain by the average slope. Because the slope is measured in meters per kilometer, the meter units cancel, leaving a result in kilometers.
Plain-language calculation: subtract current elevation from target elevation and do not let the gain fall below zero. Divide that gain by the average slope in meters per kilometer. If a benchmark is supplied, subtract the estimated distance from the benchmark distance.
In words, the formula says: required distance equals required climb divided by how quickly the land rises on average. If the land rises 20 meters per kilometer and you need 20 meters of gain, the estimate is 1 kilometer. If the land rises only 5 meters per kilometer, the same 20 meters of gain would imply 4 kilometers. This is why slope matters so much in tsunami preparedness discussions. A seemingly small change in average terrain can produce a large change in horizontal travel distance.
The table below applies the same division to a range of coastal landforms. Each row keeps the elevation gain fixed at 20 meters and changes only the average slope, so the distance column is 20 divided by the slope figure. Reading it from top to bottom shows how sharply the implied inland distance decreases as terrain steepens. It also demonstrates why a flat delta and a bluff-backed cove are completely different planning environments even though both are on a coast.
| Coastal landform | Typical average slope (m per km) | Distance implied for 20 m of gain | What usually dominates planning |
|---|---|---|---|
| Broad delta or alluvial plain | 2โ5 | 4.0โ10.0 km | Travel time and route capacity; horizontal evacuation may be impractical on foot |
| Low coastal terrace | 6โ12 | 1.7โ3.3 km | Distance still dominates; designated routes and assembly areas matter most |
| Rolling coastal town | 15โ30 | 0.7โ1.3 km | Street layout, bridges over creeks, and congestion at junctions |
| Headland or bluff back-shore | 60โ150 | 0.13โ0.33 km | Access points to high ground: paths, gates, and stair capacity |
| Engineered stairway or ramp | 200โ400 | 0.05โ0.10 km | Climb rate and crowding, not distance; mobility limits become decisive |
| Vertical evacuation structure | Not applicable | 0 km horizontal | Building capacity, opening hours, and the time required to climb inside |
The benchmark comparison is optional and does not affect the main estimate. It simply subtracts the estimated distance from whatever benchmark value you entered. For example, if your route note says 3.0 kilometers inland and the estimate is 2.5 kilometers, the gap is 0.5 kilometers. That tells you the benchmark is half a kilometer longer than the simple slope-based estimate. It does not mean the route is safe, fast enough, or better. It only describes the difference between two distances.
The formula assumes one average slope across the whole inland path. Real terrain is rarely that tidy. Roads flatten, then climb. Bridges may force detours. Stairs, switchbacks, and ridge access points change the route. A model based on one average slope is helpful for understanding first-order relationships between gain and distance, but it should never be mistaken for a detailed geographic analysis.
Worked example: climbing from a beachfront road
This tsunami evacuation distance example begins at a coastal neighborhood road 5 meters above sea level and uses a planning target of 30 meters. The elevation gain is 25 meters. If the inland terrain rises at an average of 10 meters per kilometer, the estimated distance is 25 รท 10 = 2.5 kilometers. If you also have a benchmark route length of 3.0 kilometers, the benchmark gap is 3.0 โ 2.5 = 0.5 kilometers.
That result does not say a 2.5-kilometer route is usable in an emergency. It only says that, in a simplified average-slope model, gaining 25 meters would correspond to about 2.5 kilometers of inland travel. If your actual mapped route is longer, that may be perfectly normal. Streets may curve, bridges may add detours, or accessible routes may avoid steep shortcuts. The value of the example is that it helps you read the output intelligently: the number is a terrain-context estimate, not a clearance certificate.
Limitations of this tsunami evacuation distance estimate
This tsunami evacuation distance estimate leaves out almost everything that makes an actual evacuation difficult. It does not model tsunami generation, wave height, run-up, arrival time, local bathymetry, harbor amplification, river channels, debris, overtopping, erosion, damaged roads, traffic, crowding, landslides, or bridge failure. It does not know where official hazard zones end. It does not compare horizontal evacuation with vertical evacuation structures. It does not account for mobility limits, weather, darkness, or whether a route is actually open to the public.
It also does not tell you whether moving inland or moving to higher ground is the correct local strategy. In some places, official guidance emphasizes nearby high ground. In others, designated routes or vertical evacuation sites matter. Some areas have steep bluffs close to shore; others have wide low plains where distance becomes the main challenge. Those are exactly the reasons official local maps and emergency-management instructions must override a simple calculator every time.
Another limitation is timing. The calculator estimates distance, not how long it takes to cover that distance. Walking, running, and driving times vary enormously. A route that looks short on a map may be slow because of stairs, bottlenecks, or surface conditions. A route that is mathematically efficient may be inaccessible to some people. Preparedness planning should include household mobility needs, meeting points, backup options, and familiarity with posted local evacuation signs. Distance alone is not enough.
This simplified model cannot determine safety. Use it only as a study aid while reading official evacuation products, talking with local emergency managers, or learning how slope and elevation interact. During an actual warning, do not compare formulas, inspect benchmark gaps, or play the game below. Follow official evacuation maps, alerts, sirens, local authorities, and preidentified official evacuation routes immediately. If you live, work, or travel in a tsunami-prone area, check your local emergency-management agency for the most current maps, assembly areas, and vertical evacuation guidance.
Preparedness use only: the calculator below estimates slope-based distance for educational planning. It is not an emergency decision tool.
Mini-game: Evacuation Route Planner
This optional mini-game turns the calculatorโs slope model into a compact route-planning challenge. The chart is an elevation profile: the horizontal axis is inland distance in kilometers, the vertical axis is elevation in meters, and the bright dashed line is the planning safety elevation. Three route types leave the shore assembly pointโa gentle coastal road, a town street, and a bluff stair route. Each route illustrates the same relationship used by the calculator: required elevation gain divided by average slope gives the implied horizontal distance.
The trade-off is the point. A steep stair route can reach the elevation line in less horizontal distance, but its grade slows walkers and affects group members with limited mobility most. A coastal road is easier to walk but may require much more distance. Bridges can close as the modelled water rises, debris can slow route links, and a vertical evacuation building can lift a limited number of people to a refuge floor. The challenge is educational and fictional; it does not represent a real location or predict tsunami behavior.
Scenario not started. Select โClick to play,โ or seed a scenario from the elevation, target, and slope entered above.
Game status messages about route choices and evacuation outcomes appear here.
- Coastal road (gentle, long)
- Town street (moderate)
- Bluff stairs (steep, slow)
- Modelled run-up water
- Planning elevation
- Keyboard: focus the chart, then use Up and Down to choose a branch, A to assist, E for the refuge tower, P to pause, and Enter to start or continue.
- Pointer or touch: tap a highlighted branch on the chart or use the labeled controls. Every keyboard action has a button equivalent.
Scoring rewards walkers brought above the target elevation, remaining time, and route efficiency. Procedural terrain, debris, bridge placement, group mobility, and shorter warning windows make later scenarios different and more demanding. The best score is saved in this browser.
Educational takeaway: a larger average slope reduces the horizontal distance associated with a fixed elevation gain, but real route usability also depends on travel speed, accessibility, obstructions, and official instructions.
The game is a teaching model, not a hazard model. Do not play it during a warning. Real evacuation planning must come from official local maps, designated routes, posted signs, and emergency authorities.
