When elevation data is missing from a GPX file, check which points have an elevation and what the app displays as separate questions. An elevation chart does not show whether the original file contains elevation values. Leave missing values unspecified, and record any heights obtained from a map or another source separately from the original. Start by identifying what is missing and where the displayed values came from.
Distinguish missing elevation from a value of zero
In GPX 1.1, the ele element for elevation is optional. Both route points (rtept) and trackpoints (trkpt) use wptType, which allows ele to be omitted. The latitude and longitude attributes are required. Missing elevation and missing location data are different situations.
The fact that ele is optional does not establish whether the whole file is valid. Check the rest of its structure and any other required fields separately. Missing elevations alone are neither a sign of corruption nor evidence that the file conforms to the specification. Start by reading the points you need to check.
We suggest noting “not specified” when a point has no ele and “zero recorded” when a zero is present. Whether zero is a correct observation is a separate question. Avoid filling blanks with zeros or deleting zeros just because you find them. Record what the original file actually contains.
Identify the points and note whether all or only some lack elevation
Identify the file, track and segment you are checking. GPX 1.1 allows several tracks in one file and several segments in a track. Check sections separately. The first point cannot tell you whether the whole file lacks elevation. Note which parts you checked and which you have yet to examine.
If you can see individual points, check whether each one has its own ele. Counting appearances of the text “ele” is insufficient to establish that every point in your selection has a value. For the range you checked, note whether all elevations are missing, some are missing or the points you saw have values. If you did not check the whole file, state the limit.
Keep the original unchanged and use a copy for inspection or editing. If your file, the sender’s source data and the app’s display differ, note the differences and how you received the file. Asking the sender may help explain the missing values. The gaps alone cannot tell you whether the device failed to record something or conversion dropped it.
Find out whether the displayed elevation came from the file or another source
Check whether the app can obtain elevation itself. Strava’s elevation FAQ says that activity pages show the elevation recorded in the file when the device has a barometric altimeter and is in Strava’s device database. For devices without a barometric altimeter or files from Strava’s mobile app, it shows corrected elevation by matching GPS data against its database.
If a device has a barometric altimeter but Strava does not use its values, the FAQ gives two possibilities: the device may be absent from its database or the uploaded file may lack a Device ID. This explains how Strava recognizes and processes a file. It does not establish why ele is missing in your file or how another app supplies elevations.
When noting a displayed value, record whether you confirmed it came from the original, whether it was obtained from a map or another service, or whether its source is unknown. The FAQ says a correction depends on the accuracy of the GPS data in the file and the elevation basemap. A smoother chart does not mean that a missing field measurement has been recovered.
Record the requirements and source before replacing values with map elevations
Check the conditions of the tool that supplies elevations. Garmin’s BaseCamp manual for Mac says you need a map that includes elevation data before editing track elevations. Its feature can replace the height for a point or selected range with the elevation from that map. That gives you a map value, which differs from recovering what the original device measured.
Strava’s elevation basemap guide says the service builds its database from users’ barometric altimeter measurements. If the basemap has no data for all or part of an activity, Strava falls back to a public database. When using the service’s elevations, check what data they are based on. The guide provides no guarantee of uniform accuracy across regions or of recovering missing parts.
We suggest keeping a copy from before replacement separately from the edited file. Note the selected range, the map and feature you used, the date and the fields changed. Keep original values distinguishable from later additions so others can tell which came from field measurements. If you are unsure what maps or features are available, check the official documentation before editing.
Summary: Record what is missing alongside where the values came from
Note the file and segment, whether its points have ele, whether a value is missing or zero, the source of any displayed elevation and any replacement. An example is “No ele in the points checked in this segment. The app shows an elevation chart. I haven’t confirmed its source.” That makes the next check clear. A complete-looking display does not fill the gap in the original file.
Before using elevation gain, elevation loss or gradient figures, check which points supplied the elevations, what range the calculation covers and what processing was used. Avoid comparing totals based on partial elevations with totals based on map replacements without recording their sources. A table of key points also cannot recover all the original elevations.
Treat a GPX with missing elevations as a file that leaves some fields unspecified. Check the information you need separately. Keep original, displayed and map-derived values distinct so you can review them later. See the related articles on versions, data types and breaks. Check current trail conditions independently of any elevation display.