Skip to content

Elevation Finder: Get the Altitude of Any Point

Enter latitude and longitude in decimal degrees, or select a map point. This elevation finder returns a surface estimate with its source, units, and accuracy grade.

US address search by Census. Click the map for any other place.

Enter decimal degrees, latitude first. Coordinates are kept out of analytics. Map coverage stops near the poles.

Finding our bearings…

Click anywhere to find its elevation.

Worldwide coverage · No account needed
GLO-30 · ~30 m · Grade C

Last updated · MapElevation

Find elevation from latitude and longitude

This elevation finder is designed for a known point rather than a place name. You may have coordinates from a GPS track, a map pin, a field notebook, or another mapping service. Enter the pair in decimal degrees and submit it. Once the marker appears, check its surroundings: a valid numerical pair can still describe the wrong place if a digit, sign, or field order was copied incorrectly.

The elevation map emphasises browsing the terrain, while this page makes coordinates the primary input. For a street address rather than a coordinate, use the address elevation finder. Keeping these tasks distinct helps you see where uncertainty enters the lookup. Address matching introduces its own location estimate; entering coordinates bypasses that step but does not improve the terrain dataset.

How to use this page

  1. Enter latitude and longitude in the labelled decimal-degree fields.
  2. Submit the point and check its map position against a recognisable landmark.
  3. Read the sampled height, units, model, original resolution, and reference.
  4. Record the same coordinate and source when comparing with another reading.

How to enter coordinates correctly

Latitude describes the north–south position and longitude the east–west position. Preserve negative signs. A west longitude entered as a positive number selects an eastern longitude, even if every other digit is unchanged. Do not paste directional letters into a decimal field unless you have first converted the coordinate to the format the form expects. A value that looks familiar is not enough to establish that its interpretation is correct.

Coordinate pairs from software are not always ordered the same way. The labels on this page are latitude followed by longitude; geospatial data formats often use longitude followed by latitude. If you are uncertain, compare the pin with a recognisable place or use what is my elevation to obtain a nearby position as a cross-check. The supported map projection also excludes the immediate polar regions.

Choose a point on the map

You can select the map directly instead of typing coordinates. The tool retrieves the relevant terrain tile and reads the encoded height at the selected pixel. The result describes that modeled surface location. A click on a broad label is not a query for the whole city, and a click near a road is not automatically snapped to the road’s engineered surface.

Compare a few nearby points when exploring a ridge, a valley, or a slope. If a readout changes abruptly, inspect the landform, pin position, and source limitations before concluding that the change is real. The contour map generator provides another view of the same modeled terrain, with lines connecting equal elevations. These visualisations are complementary rather than independent measurements.

Understand the elevation result

The returned card pairs the height with model type, original resolution, and vertical reference. Feet and metres are display choices. A DSM can represent vegetation or buildings above bare earth, and tile resampling can smooth or alter small features. Read elevation data accuracy when the distinction could affect your interpretation.

The height above sea level guide explains why a GPS altitude or a published flood elevation may not be directly comparable with this number. This finder does not infer a local datum transformation, calculate a building’s floor height, or certify a benchmark. Those tasks require information that is not present in a global surface tile.

Make a coordinate lookup reproducible

For a meaningful example, preserve the exact coordinate, chosen dataset, query date, and units along with the result. A city’s commonly quoted elevation is not a substitute for sampling the specific point shown. The recorded example below includes that audit information; it must not be interpreted as a city-wide altitude.

A timeout means the requested terrain did not complete within the allowed wait. Use Retry to repeat the same lookup, or inspect another point to distinguish a local data issue from a connection problem. You can continue reading this page while a tile request is pending, and precise coordinates are not included in the performance analytics events.

A recorded point-query example

At latitude 39.7392, longitude −104.9903, a Denver-area point query on 2026-10-21 decoded a GLO-30 terrain-tile sample of 1,596.5 metres. The result card rounds that to 1,597 m or 5,238 ft. The browser’s feet readout was checked against the independent tile decode. The saved example record includes the tile URL, pixel, RGB values, and file checksum; it is a surface-model observation in the EGM2008 reference, not a surveyed building height or an independent vertical-accuracy assessment.

Data sources and accuracy

Elevation estimates currently use Copernicus GLO-30, a digital surface model (DSM), sampled from Mapterhorn terrain tiles at zoom 12. Original resolution is approximately 30 metres: our Grade C. Buildings, trees, location errors, and the source vertical reference affect interpretation. A grid resolution is not a vertical error guarantee. The reference is the EGM2008 geoid; a reading must not be subtracted from a FEMA flood elevation in another datum.

Read about elevation data accuracy, source-specific limitations, and our current regional coverage.

Terrain licence and attribution

produced using Copernicus WorldDEM-30 © DLR e.V. 2010-2014 and © Airbus Defence and Space GmbH 2014-2018 provided under COPERNICUS by the European Union and ESA; all rights reserved

Mapterhorn attribution · Copernicus licence

Frequently asked questions

How do I find altitude by coordinates?

Enter latitude in the first field and longitude in the second, using decimal degrees and a minus sign for south or west. Submit the point, check where the pin appears, then read the elevation card. The card can show feet or metres and identifies the surface dataset used.

Does coordinate order matter?

Yes. Swapping latitude and longitude may select another continent or an invalid location. The input fields are explicitly labelled, while some mapping systems present coordinates in longitude–latitude order. Read the format of your source rather than assuming that every pair is written in the same order.

Can I paste degrees, minutes, and seconds?

The current form accepts decimal degrees. Convert a degrees–minutes–seconds coordinate carefully before using it, preserving the hemisphere or negative sign. An accidental sign change can move a point across the equator or prime meridian. The map pin is a useful check before interpreting the returned altitude.

Is this a GPS elevation finder?

It can look up a terrain elevation at coordinates from a GPS receiver. It does not use a receiver’s vertical measurement or certify GPS accuracy. A location copied from a track may be offset from the path, particularly under trees or near structures, so review both the coordinate and the terrain source.

Why can I not query the exact poles?

The interactive map and terrain tiles use a Web Mercator projection with a latitude limit close to 85 degrees north and south. The form rejects positions outside its supported terrain coverage instead of returning an unrelated tile. A polar specialist dataset is needed for locations beyond that range.

Can I use a finer coordinate to get a more precise height?

Additional coordinate digits can describe a more specific point, but they do not add detail to the source terrain grid. The current source has approximately 30-metre original spacing. Displayed coordinate precision, terrain resolution, and vertical accuracy describe separate things and should not be substituted for one another.