Which elevation question are you asking?
An elevation profile is only one possible answer. Name the quantity first so a point readout, a route, and a terrain summary do not get mistaken for one another. For a broader choice among line, area, and routed measurements, use the Maps and Earth measurement guide.
| Question | Use | What you receive | Do not call it |
|---|---|---|---|
| How high is this one place? | Earth point or placemark elevation | Estimated ground elevation at one latitude and longitude | A profile or the camera altitude |
| How does terrain rise and fall along my line? | Earth on the web or Earth Pro elevation profile | Elevation plotted against distance along a chosen path | Total ascent or a GPS track |
| What are the sampled terrain extremes? | Advanced measurements in current Earth | Minimum, median, and maximum terrain elevation and slope where supported | Every local high, low, or road grade |
| How long is my drawn line? | Earth Measure | Length along the geometry you placed | Rise-and-fall ground distance |
| How far is the trip by road or trail routing? | A documented routing tool and travel mode | Distance along the selected route | A freehand terrain transect |
| What value can support a design, boundary, or safety decision? | Authoritative data and a qualified method or professional | Evidence matched to the decision and required accuracy | A consumer-globe estimate |
For one location, the Google Earth coordinates guide explains how to find, enter and copy latitude and longitude. A point value cannot reveal the terrain between two endpoints.
Create an elevation profile in Google Earth on the web
Google added Elevation Profile to current Google Earth on April 30, 2026. It is listed as a regular feature in the release notes, not as an Experimental tool. The documented computer workflow is:
- Open Google Earth on the web on a computer and frame the public or fictional terrain you want to examine.
- Start Measure for a temporary line, or choose Path or polygon when you want a project feature you can name, save, and edit.
- Click the start of the transect, then add at least one more point. With two points placed, the Elevation Profile chart appears in the inspector.
- Add vertices where the line must bend. The chart changes as you draw or edit the line.
- Double-click the last point or choose Done to finish. Wait for the completed result before transcribing values: Google says the initial elevation resolution can depend on zoom and is refined when drawing finishes.
- Record the product, line definition, date, units, displayed minimum and maximum, and the fact that the terrain values are estimates.
Measure and a saved project path can reach the same kind of chart, but they serve different working habits. Use Measure for a quick disposable transect. Use a project path when classmates need to inspect or revise the same geometry. If the starting material is a public My Maps line, the My Maps export and Earth handoff guide explains the difference between viewing, copying, and downloading it; verify that the intended path arrived before profiling it.
These steps are for a computer. Before planning a phone or tablet activity, check whether the required profile controls are available on the class device.
Create an elevation profile in Google Earth Pro
Earth Pro uses its own installed desktop interface. It is not the same product as the current cloud Professional plan. The Earth web, mobile, and Pro comparison covers that naming and the wider file differences.
- Open Google Earth Pro and go to the terrain you need.
- Draw a path or open an existing path. If you started with Tools → Ruler, save and name the path so it appears under Places.
- Select the path, then choose Edit → Show Elevation Profile.
- Read the chart in the lower half of the 3D Viewer. Move the pointer over the profile to relate a chart position to the path; click and drag across a portion when you need to inspect a subsection.
- If elevation reads 0, make sure the Terrain layer is on.
- Set units under Tools → Options on Windows or Google Earth → Preferences on Mac, then record the same method and limitation details used for a web profile.
Do not install Pro solely because an old tutorial says the web lacks profiles. Choose Pro when its saved Places workflow, local files, or profile interactions suit the task; choose the web when the inspector and current project workflow suit it.
Google Earth web vs Earth Pro profile workflow
| Step or behavior | Earth on the web | Earth Pro |
|---|---|---|
| Start the line | Measure or Path or polygon | Draw or open a path; a Ruler line can be saved to Places |
| Open the profile | Appears in the inspector after at least two points | Choose Edit → Show Elevation Profile |
| While editing | Chart updates as points move or are added | Edit the selected path, then inspect its profile |
| Finish state | Complete the drawing for refined values | Keep the intended path selected and Terrain on |
| Chart location | Inspector panel | Lower half of the 3D Viewer |
| Useful interaction | Revise vertices and watch the profile change | Hover to connect chart and path; drag to select a subsection |
| Documented caution | Initial resolution can depend on zoom; finished values remain estimates | A zero reading calls for a Terrain check; the result still is not survey authority |
Neither workflow is a complete copy of the other. Choose between Google Maps, My Maps, and Earth for the whole project before treating one matching feature as product parity.
How to read the chart without overreading it
The profile is a two-dimensional section through estimated terrain beneath your chosen line. A high point on the chart corresponds to a high sampled part of the terrain; it is not automatically a summit, building top, bridge deck, road surface, flight altitude, or a value recorded by a GPS device.
| Chart element | Read it as | Check before comparing |
|---|---|---|
| X-axis | Distance from the start along the chosen path | Same endpoints, vertex order, and distance units |
| Y-axis | Estimated terrain elevation above sea level | Same elevation units and no confusion with camera altitude |
| Minimum | Lowest displayed sampled terrain value along the line | Completed line and comparable path geometry |
| Maximum | Highest displayed sampled terrain value along the line | Completed line, view/zoom context, and estimate limits |
| Selected position | One distance/elevation relationship on the chosen profile | That the marker corresponds to the intended place on the path |
| Shape of the line | Relative rises, falls, ridges, and valleys in sampled terrain | The transect did not cut across a different slope because vertices moved |
Current Earth’s Advanced measurements can add summary statistics. For a line between two points and for longer paths, the documentation lists minimum, median, and maximum terrain elevation and slope. Median means the 50th percentile of the sampled values; it is not the arithmetic mean and not the elevation halfway along the line. Those summaries are useful for comparison, but they do not promise every local extreme or cumulative climbing.
A controlled example: two lines across one fictional ridge
Suppose a class studies a fictional public landform called Pine Ridge. Group A draws a direct west-to-east transect across the high point. Group B uses the same endpoints but adds a middle vertex that diverts into a shallow saddle. The numbers below are invented for method practice; they are not observed Earth values or a real location.
| Recorded item | Group A: direct line | Group B: line through saddle |
|---|---|---|
| Endpoints | Public trailhead marker W to marker E | The same W and E markers |
| Middle vertices | None | One fictional saddle marker |
| Illustrative line length | 2.0 km | 2.3 km |
| Illustrative maximum | 620 m | 540 m |
| Defensible conclusion | This chosen line crosses the higher part of the fictional ridge | This chosen line is longer but crosses lower fictional terrain |
The groups should not average the two profiles or argue that one is the “true” ridge. They asked different spatial questions by drawing different lines. That is precisely why vertices belong in the method record.
Why a profile is missing, zero, flat, or surprising
| Symptom | Check | Next move |
|---|---|---|
| No chart on the web | Product, computer surface, and number of points | Use current Earth on the web and place at least two points with Measure or Path or polygon. |
| No Show Elevation Profile in Pro | Whether a path—not a point or polygon—is selected | Draw or open the path, select it under Places, then use the Edit menu. |
| Earth Pro reads zero | Terrain layer | Turn Terrain on, the remedy named in Google's Pro help. |
| Web values change after finishing | Completion and initial zoom-dependent resolution | Use the finished, refined result and record that it remains an estimate. |
| Two profiles disagree | Endpoints, middle vertices, vertex order, units, and completion state | Recreate the same transect before comparing the charts. |
| The line looks too flat or too steep | Y-axis range and the terrain actually crossed | Read axis values rather than judging the chart's visual angle alone. |
| Length seems too short on hills | Path geometry versus terrain relief | Remember that the documented length does not account for elevation change. |
| No total ascent or export button | Whether the expected output is documented | Do not invent it from the chart; use a documented data-analysis workflow suited to the decision. |
Avoid “fixes” that merely make the picture look persuasive. Moving endpoints, adding vertices, changing units, or zooming to a different context changes the method or presentation. Record the change and rerun both comparison lines the same way.
Make a profile reproducible
Use this checklist before students compare results or a researcher returns later:
- Product and surface: Earth on the web on a computer, or Earth Pro with its version recorded.
- Line identity: a named saved path, or a written description of the temporary Measure line.
- Start and end: non-sensitive public landmarks or source-backed coordinates, in the correct order.
- Vertices: every deliberate bend and why it was added.
- State: drawing finished; in Pro, intended path selected and Terrain on.
- Units: distance and elevation units copied with the values.
- Outputs: chart minimum/maximum and any separate median or slope statistics labeled by name.
- Date and context: observation date plus enough view/zoom context to repeat the method.
- Limit: one sentence saying the values are inferred terrain estimates, not route, survey, engineering, legal, or navigation authority.
For a graded map, apply the research-question, citation, accessibility, and presentation checks in the student map project framework. A screenshot alone is weak evidence if it omits the path and method.
Classroom activity: compare public transects
Choose a public park, broad landform, or wholly fictional terrain—never a student home, private routine, or sensitive field site. Give pairs the same public start and end markers. Half draw the direct line; half add one agreed vertex around a ridge or through a valley. Each pair records units, maximum and minimum, the number of vertices, and one uncertainty.
Then ask: did the terrain change, or did the sampling line change? That question turns a chart-reading exercise into spatial reasoning. The mapping lesson ideas collection can place the transect in science, geography, history, or literature, while the teacher workflow guide covers account, privacy, and accessible alternatives.
Make the evidence accessible: repeat key values in a table, describe the overall rises and falls in words, do not encode meaning by color alone, and offer the path description alongside the image. If Earth is unavailable, students can still compare teacher-provided fictional path/profile pairs on paper.
What the profile cannot establish
Google describes current Earth measurements as inferred estimates and says they may contain errors. Use a profile to explore terrain, compare deliberately controlled transects, and form questions. Do not use it as the sole evidence for:
- cumulative ascent or descent that the interface does not document;
- a terrain-following walking, cycling, driving, or trail distance;
- the altitude captured by a GPS device or embedded in a KML track;
- a road surface across bridges and tunnels, the top of buildings or vegetation, or obstacle clearance;
- property boundaries, grading plans, drainage design, earthworks, construction quantities, aviation, emergency routing, or another legal or safety decision;
- a raw series of sampled elevations unless a separately documented export method actually supplies it.
For source tables and citations, use the mapping research guide. Choose a specialist analysis tool when a consumer terrain estimate cannot support the decision.
Sources and update note
This guide was checked on September 15, 2026 against Google’s current Earth release notes, computer project-feature documentation, current measurement documentation, Earth Pro Help, altitude/coordinate documentation, and Earth versions page.
Sources: Google Earth release notes, add features and view an elevation profile, measure distances, terrain elevation, and slope, Earth Pro measurement and elevation profile, find altitude and coordinates, and Google Earth versions.
Interface labels and supported outputs can change. Recheck the official instructions before a class session or any decision that depends on the result.
Our guides used
- The Maps Guide: How to Measure Distance and Area in Google Maps and Google Earth.
- The Maps Guide: Google Earth Coordinates: How to Find, Enter, Copy, and Convert Latitude and Longitude.
- The Maps Guide: Google Earth Web vs Mobile vs Earth Pro: Which Version Should You Use?.
- The Maps Guide: How to Export Google My Maps to KML or KMZ—and a Layer to CSV.



