Skip to content
My Current Elevation

Corrections

Last updated

We want every number on this site to be right. If you find one that is not, please tell us. This page explains how, what we do with your report, and lists every correction we have made.

How to report an error

Email support@mycurrentelevation.org with:

  • the address of the page (or the tool and what you entered);
  • the figure or sentence you think is wrong;
  • if you have one, the source you are comparing with: a survey datasheet, a government page, a map, or your own GPS reading with the device you used.

You do not need an account, and we do not publish your name or email address.

What happens next

  • We read every report and aim to reply within seven days.
  • We check the figure against the original data source named on the page, and against the source you sent.
  • If the page is wrong, we fix it, note the change in the log below with the date, and tell you.
  • If the page is right but unclear, we improve the wording. Many reports come from two sources measuring different things: a survey mark below a summit, an old datum (NGVD 29) against the current one (NAVD 88), or a city's official elevation measured at one spot against the elevation where you are standing.
  • If two good sources disagree, we follow our rules for conflicting sources and show both figures on the page.

A live reading from the elevation tools can differ from a published figure without either being wrong; your device's GPS position and the elevation grid both have a margin of error, shown with each result.

Corrections log

Newest first. Each entry says what the page said, what it says now, and why.

  1. Pikes Peak

    Was: The rebuilt page gave the summit as 14,105 ft, the height of NOAA National Geodetic Survey mark PIKES PEAK DMWW (PID DR8168).

    Now: The headline is 14,115 ft, the summit figure published by the City of Colorado Springs, which runs the Pikes Peak Highway and summit visitor center. The NGS mark height is still shown in the note, because a survey mark does not always sit on the highest rock.

  2. Phoenix

    Was: The old site had three Phoenix pages (/phoenix-elevation/, /phoenix-elevation-2/ and /phoenix-elevation-3/) that disagreed. They gave the highest point as 2,610 ft (South Mountain), 2,704 ft and 2,680 ft (both Camelback Mountain), and the lowest as 900 ft, 1,060 ft and 1,020 ft.

    Now: One page, computed from USGS 3DEP inside the 2024 Census city boundary: 1,088 ft downtown, and a sampled range of 984 to 2,467 ft across 160 grid points, labelled as sampled. The three old addresses redirect to it.

  3. Elevation from lat/long, Elevation by address

    Was: When the USGS service timed out, a US point got the coarser Terrain Tiles value and kept it for the whole 90-day cache period. A Death Valley test point showed -177 ft this way; USGS gives -189 ft.

    Now: A US value that came from the fallback is asked of USGS again after one hour, so the USGS figure replaces it.

  4. Salt Lake City, Denver, Denali, Mount Blue Sky

    Was: The old site had duplicate pages for the same place with different figures, among them three Salt Lake City pages, two Denver pages, separate Denali and Mount McKinley pages, and separate Mount Evans and Mount Blue Sky pages.

    Now: Each place has one page with sourced figures, and every old address redirects to it in a single step.

  5. Every page (footer)

    Was: The old site footer named the site MyCurrentElevation.com.

    Now: The footer gives the correct address, MyCurrentElevation.org.

  6. Annapolis, Louisiana

    Was: A rounding bug printed ranges such as "-0 to 26 m" on the Annapolis, Louisiana, Algiers and Luanda pages.

    Now: Values that round to zero print as 0.

These entries cover the rebuild of the site, which went live on October 26, 2026, replacing the earlier WordPress version.