Learn to create Google Earth Pro elevation profiles, add contour-line KML overlays and avoid terrain-clearance mistakes in simulator flight planning.
For general flight-simulator planning, Google Earth Pro can show a ground-elevation profile beneath any saved path, but it does not generate contour lines itself. Draw and save a route, right-click it in Places and choose Show Elevation Profile. For contours, import a KML or KMZ overlay from a suitable topographic dataset.
How do I create an elevation profile in Google Earth Pro?
A saved path is the object Google Earth Pro uses to calculate a terrain elevation profile.
- Enable the terrain model. In the Layers panel, make sure Terrain is selected, then move to the area containing your planned route.
- Draw the route. Choose Add > Path or use the path button on the toolbar. Name the path and click points along the intended ground track. Add enough points to follow bends rather than cutting directly across them.
- Save the path. Select OK when the line is complete. It should now appear under Places as a path rather than a placemark, polygon or folder.
- Open the chart. Right-click the saved path and select Show Elevation Profile. On macOS, use the equivalent secondary-click or Control-click action.
- Inspect the terrain. Move the pointer across the chart to identify the corresponding position on the route. The horizontal axis represents distance along the path, while the vertical axis shows ground elevation.
The profile follows the terrain beneath the route; it is not a planned aircraft altitude trace. Its slope value describes the ground between samples, not the climb gradient your aircraft must achieve. The chart's distance axis is useful for an overall route, while our Google Earth path-measurement method explains how to check individual leg lengths.
Why does Google Earth Pro not show contour lines?
Google Earth Pro has no built-in command that converts its 3D terrain mesh into conventional topographic contour lines.
The Terrain layer supplies shaded three-dimensional relief, not lines joining equal elevations. Enabling Roads, Borders and Labels or changing the map appearance will not add true contours.
To display them, obtain a contour dataset supplied as KML or KMZ by a suitable mapping authority or export one from a GIS workflow. Open it through File > Open, check its visibility under Places and save it from Temporary Places into My Places if you want it retained. Our KML import and layer-management instructions cover that process in detail.
Before relying on an overlay, check its contour interval, elevation units, coverage, source resolution and vertical datum. A contour file can disagree with the Google Earth profile because the two may come from different terrain models. Very large regional overlays can also make Google Earth Pro slow; load only the area needed when possible.
What does each terrain display actually tell me?
Elevation profiles, imported contours and the 3D view answer different planning questions.
| Display | Useful for | What it can miss |
|---|---|---|
| Elevation profile | Finding ridges and the highest sampled ground beneath the exact route centreline | Terrain beside the line, narrow features between samples, buildings, trees, masts and other obstacles |
| Contour overlay | Understanding the shape and spacing of surrounding terrain | Anything absent or generalised in the contour source, including later terrain changes and obstacles |
| 3D terrain view | Visual reconnaissance of valleys, passes and approach directions | Reliable numerical clearance; perspective and vertical exaggeration can make slopes look misleading |
For a route through confined or mountainous terrain, draw parallel paths on either side of the intended track as well as the centreline. A single profile can pass through a valley while completely missing a ridge that becomes relevant after a small navigation error or wind drift.
Can I use the elevation profile to choose a safe altitude?
Use Google Earth Pro as a visual terrain cross-check, not as the sole source for a safe or legal flight altitude.
The profile does not apply obstacle clearance, procedure restrictions, airspace, minimum sector altitudes, weather effects or aircraft performance. Google Earth terrain can also contain smoothing, void-filling and local elevation errors. For real-world navigation, use authorised aviation charts, procedures and obstacle information; for simulation, use the data and procedures appropriate to the simulator and scenery package.
If you need a route tied to simulator airports and navigation data, our Little Navmap planning guide explains its route elevation display. Google Earth Pro remains particularly useful for visual inspection and checking terrain outside the immediate route line.
Why is the elevation profile missing or incorrect?
Most missing or implausible profiles come from selecting the wrong object, incomplete terrain data or comparing incompatible elevation sources.
- No Show Elevation Profile option: Select the saved path itself under Places. The command may not appear for a folder, ordinary placemark or contour overlay.
- Blank or blocky terrain: Confirm that Terrain is enabled and allow the area to load. Google Earth Pro streams terrain data, so an incomplete cache or unavailable connection can leave gaps.
- Unexpectedly flat profile: Check whether the path crosses water or genuinely level ground. Redraw a short test path over obvious hills to separate a data problem from the route itself.
- Wrong units: Change the measurement and elevation units in Google Earth Pro's preferences or options. Menu placement differs slightly between operating systems.
- Profile and contours disagree: Compare their source resolution, contour interval and vertical datum. Neither should override authorised aviation elevation or obstacle information.
- Terrain looks much steeper than the chart suggests: Check the 3D vertical-exaggeration setting. Exaggeration changes the visual model, not the underlying quality of the elevation data.