# Trail File — full text > Trail File is an independent educational publication about GPX files, offline maps, route checks, and hiking-navigation preparation. It is not a mapping service, land manager, guide company, rescue service, app developer, equipment seller, or continuation of any former entity associated with this domain. Digital route information cannot establish current access or replace skills, official notices, and appropriate backup navigation. # How to Check a GPX File Before a Hike > Check a hiking GPX file by identifying whether it contains waypoints, a route, or a track; recording its source and date; and inspecting the complete geometry at high zoom. Verify the trailhead, finish, direction, junctions, gaps, straight jumps, water and road crossings, distance, elevation source, and missing return legs. Compare the line with current official maps, alerts, closures, permits, and access rules. Import a checked copy into the exact field device, confirm every segment and waypoint survived, download the surrounding map, and carry independent paper navigation. Source: https://megatrail.info/check-gpx-file-before-hike/ Publisher: Trail File Published: 2026-07-19 Updated: 2026-08-26 ## Treat a GPX file as data, not permission Check a hiking GPX file by opening it in a trusted viewer, confirming its source and date, inspecting start, finish, geometry, gaps, direction, distance, elevation, and waypoints, and comparing the line with current official trail information and a topographic map. A GPX track can describe where someone or something recorded coordinates; it does not prove the path is legal, open, maintained, safe, or suitable for your group. The official GPX description calls the format a lightweight XML exchange format for waypoints, routes, and tracks. Those element types have different purposes, and software may display them similarly enough to conceal the difference until it matters. ## Identify what the file contains Use an application that can show file metadata and individual layers. Keep the original file unchanged and inspect a copy. Do not enable macros, install unknown software, or upload sensitive private tracks to a public service merely to view them. A **waypoint** is a named location. A **route** is an ordered set of route points that may rely on software or human interpretation between points. A **track** is an ordered record of track points, potentially divided into segments. A track with dense points may resemble a walked line; a route with sparse points can cut straight across terrain when the viewer does not calculate paths. The [GPX format site](https://www.topografix.com/gpx.asp) links the GPX 1.1 schema and documentation. File extension alone does not guarantee that a file is valid GPX 1.1 or that every application will preserve every extension field. Browse [route files](/route-files/) for more data checks before field use. ## Verify provenance and recency Record who created or exported the file, where it was obtained, when the underlying trip occurred, and what the creator says it represents. Distinguish an official land-manager route from a community recording, race course, private itinerary, or automatically generated suggestion. Compare the geometry with current official maps, alerts, closures, permits, seasonal restrictions, and access rules. Trail names can be reused, junctions rerouted, and roads gated. Contact the land manager when status is unclear. Do not infer permission from a line crossing private land or a closed area. A GPS receiver can locate a coordinate with great confidence while being completely uninformed about a locked gate. ## Inspect start, finish, and every junction Zoom in at the trailhead. Confirm the file begins at a legal, current access point—not at someone's parked car, campsite, or mid-route recording start. Check whether the finish returns to the start and whether an out-and-back file contains one direction or both. Follow the full line at high zoom. Look for straight jumps, duplicated loops, missing segments, implausible switchback shortcuts, water crossings, road crossings, cliffs, and deviations from the mapped trail. Inspect every junction where a wrong turn would be easy. If editing is necessary, save a new version with a clear name and document the change. Never silently repair uncertain geometry and then forget which points came from observation and which came from your mouse. ## Recompute practical numbers Compare distance reported by more than one reliable tool when possible. Point spacing, smoothing, track noise, and gap handling can change totals. Elevation gain is especially sensitive to the elevation source and filtering; a file may contain recorded elevation, calculated elevation, no elevation, or noisy values. Use distance and climbing as planning estimates, not promises. Add approach walking, route-finding, breaks, side trips, and any return absent from the file. Assess terrain, weather, altitude, group pace, daylight, water, and escape options separately. Visit [offline navigation](/offline-navigation/) before transferring the route to a device. ## Test the exported copy Import the checked copy into the exact device and application intended for the hike. Confirm that track segments, waypoints, labels, and direction survived. Ensure the surrounding map is downloaded; a colored line alone cannot show terrain, alternative exits, or neighboring drainages. Use our [offline trail-map guide](/prepare-offline-trail-map/) to test coverage without service. Carry a suitable paper map and compass and know how to use them, as the [National Park Service Ten Essentials](https://www.nps.gov/articles/10essentials.htm) recommends. Share a trip plan and the authoritative route description with a trusted contact, not only the GPX. The final file should be a checked navigation aid with known limitations. If it starts presenting itself as proof of safety, access, and wisdom, remember: XML is very organized, but it has never met tomorrow's fallen tree. ## Frequently asked questions **What is the difference between a GPX track and route?** A track is an ordered record of track points and may be divided into segments, often representing recorded or prepared geometry. A route is an ordered set of route points that software or a person may interpret between points. A sparse route can display as straight connectors when no routing engine is applied. Applications vary, so identify the element type and confirm how the exact field app imports and displays it. **Does a GPX file prove a hiking trail is open?** No. GPX stores geographic data; it does not establish current access, ownership, permission, maintenance, safety, or closures. A file may be old, unofficial, recorded off trail, or generated across private land. Compare it with current land-manager maps and alerts, obey signs and closures on arrival, and ask the responsible authority when access is uncertain. Treat the line as a navigation aid with provenance, not a permit. **Why does GPX elevation gain vary between apps?** Applications may use elevation recorded in the file, replace it with a terrain model, smooth noise differently, bridge gaps differently, or sample points at different intervals. A track may also lack elevation. These choices change cumulative ascent even when horizontal geometry looks similar. Record the source and method when available, compare more than one reliable calculation, and use gain as a planning estimate alongside terrain and official route information. **How do I spot a bad GPX track?** Inspect the complete line at high zoom for straight jumps, gaps, duplicated loops, impossible shortcuts, off-trail deviations, a mid-route start, absent return, and junctions that do not align with current authoritative maps. Compare distance and elevation, and check whether track segments disappeared during import. A smooth-looking overview can hide a large error. Do not repair uncertain points silently; save a new copy and document any edit. **Is a GPX file enough for hiking navigation?** No. The file may provide a route line or waypoints but not surrounding terrain, legal access, current hazards, or an alternative exit. Load an appropriate offline map around it, test the device without service, and carry a current paper map and compass with the skills to use them. Check official conditions, plan power, share a trip plan, and be ready to change or cancel when field conditions differ from the digital plan. --- # How to Read GPS Coordinates: Formats and Safe Sharing > Read GPS coordinates by identifying latitude and longitude, their format, and hemisphere letters or signs. Latitude is north or south; longitude is east or west. Decimal degrees, decimal minutes and degrees-minutes-seconds can express the same position differently. Preserve the datum and label each value when sharing. Coordinates do not establish safe or legal access: use official conditions, navigation skills and appropriate backup navigation. Do not delay an emergency call to convert coordinates. Source: https://megatrail.info/how-to-read-gps-coordinates/ Publisher: Trail File Published: 2026-09-08 Updated: 2026-09-08 ## How do you read GPS coordinates? Read GPS coordinates by identifying the format, the latitude and longitude, and their hemisphere letters or signs. Latitude describes north or south; longitude describes east or west. Keep the coordinate format and map datum with the numbers when sharing them. A correctly copied position does not establish a safe or legal route to it: use current official information, appropriate navigation skills and backup navigation. You do not need to become a surveyor to make this less confusing. Start by separating three questions: what do these numbers mean, how are they written, and what position does the device actually represent? ## Which number is latitude, and which is longitude? Latitude measures position north or south of the equator. Longitude measures position east or west of the prime meridian. The [NOAA latitude explanation](https://oceanservice.noaa.gov/facts/latitude.html) describes degrees, minutes and seconds; its [longitude explanation](https://oceanservice.noaa.gov/facts/longitude.html) explains the east-west coordinate. In signed decimal degrees, north and east are positive; south and west are negative. Thus a negative longitude indicates west, not south. A minus sign belongs to its own number. Label the values when you share them. Google Maps search expects latitude first and longitude second, but the receiving system's field labels and documentation should determine how you enter a coordinate. Do not assume that an unlabeled pair from another file uses the same order. A useful first check is whether the values are possible: - Latitude must be between -90 and 90 degrees. - Longitude must be between -180 and 180 degrees. - In degrees-minutes-seconds notation, minutes and seconds must each be less than 60. The [USGS coordinate data dictionary](https://www.usgs.gov/centers/eros/science/usgs-commercial-data-purchases-data-dictionary) documents those limits. Passing them only means a coordinate is numerically possible. Swapped numbers can sometimes both fall within the allowed ranges while pointing somewhere entirely different. ## What are the three common coordinate formats? Degrees can be subdivided in different ways. One degree contains 60 minutes, and one minute contains 60 seconds. These are angular units, not elapsed time. The following is an arithmetic-only training example. It is not a trail recommendation, meeting point or place to visit. All three rows express the same coordinate pair. | Format | Latitude | Longitude | |---|---|---| | Degrees, minutes, seconds: DMS | 40° 30' 18" N | 105° 15' 36" W | | Degrees and decimal minutes: DDM | 40° 30.300' N | 105° 15.600' W | | Decimal degrees: DD | 40.505000 | -105.260000 | The location of the decimal point matters. In DDM, the decimal belongs to the minutes. In DD, it belongs to the degrees. Never remove the degree and minute symbols and join the remaining digits together. A value such as 40.30 degrees means 40 degrees plus 0.30 of a degree. It therefore equals 40 degrees 18 minutes, not 40 degrees 30 minutes. That difference comes from multiplying 0.30 by 60. Keep the original text or screenshot before changing formats. If something goes wrong, you need the source coordinate, not several successive conversions whose starting point has disappeared. ## How do you convert degrees, minutes and seconds? For the magnitude of a coordinate, use: Decimal degrees = degrees + minutes ÷ 60 + seconds ÷ 3,600. Then apply the hemisphere: south or west becomes negative in signed decimal notation. Apply that sign to the whole result. For the example latitude: 40 + 30 ÷ 60 + 18 ÷ 3,600 = 40 + 0.5 + 0.005 = 40.505. For the example longitude: 105 + 15 ÷ 60 + 36 ÷ 3,600 = 105 + 0.25 + 0.01 = 105.26. Because that longitude is west, its signed result is -105.26. To obtain DDM instead, convert only the seconds into a fraction of a minute. Eighteen seconds becomes 0.300 minutes; 36 seconds becomes 0.600 minutes. Add those fractions to the existing minutes, leaving the degrees unchanged. You can check the latitude conversion backwards: 0.505 × 60 gives 30.3 minutes. The whole minutes are 30; the remaining 0.3 × 60 gives 18 seconds. This is a useful desk check, not a task to prioritize during an emergency. When using a converter, select the input format explicitly. A tool that accepts your numbers without an error has not necessarily interpreted them as you intended. ## How should you enter a coordinate into a map? Use this check before relying on a saved waypoint: 1. Copy the original coordinate, including hemisphere letters or minus signs. 2. Identify DD, DDM or DMS. Check which unit contains the decimal. 3. Record the stated datum, if supplied. 4. Read the destination fields or search instructions. Enter each value in its required format and order. 5. Check the plotted region, then compare the position with relevant mapped landmarks. 6. Keep the original alongside the saved waypoint so another person can verify it. [Google Maps' computer instructions](https://support.google.com/maps/answer/18539?hl=en&co=GENIE.Platform%3DDesktop) accept DD, DDM and DMS searches. They specify latitude before longitude and decimal points rather than decimal commas. Use the documented syntax; a comma separating the two coordinates is different from a comma inside a decimal number. Those instructions also explain how to right-click a map position to retrieve coordinates. That produces the coordinate of the selected map point. It does not establish that you are standing there. If a result falls in an unexpected country, hemisphere or part of a valley, stop and recheck the source. Do not repeatedly change signs or swap numbers until a pin looks plausible. A plausible pin can still be wrong. ## Does changing the coordinate format change the datum? No. Changing between DD, DDM and DMS changes how you write the angles. A datum or reference framework concerns how positions relate to the Earth. [Ordnance Survey distinguishes conversion from transformation](https://www.ordnancesurvey.co.uk/geodesy-positioning/os-net/faq): changing the representation is not the same operation as changing the reference framework. Its examples include GPS's WGS84 framework and the OSGB36 framework associated with the British National Grid. Look for the datum in the map margin, file documentation or app's relevant settings. Preserve the stated datum when sharing coordinates. If it is unknown, say so rather than labeling the numbers WGS84 because they came from a digital device. If the source and destination use different datums, use an appropriate documented transformation or get help from the mapping authority. Simply changing a label does not transform the position. The [USGS explanation of NAD27 and NAD83 shifts](https://www.usgs.gov/faqs/how-large-north-american-datum-1927-nad-27-nad-83-shift) illustrates why this is not merely a formatting detail. A grid reference is also not automatically latitude and longitude. If your map supplies grid coordinates, retain its reference-system information and use instructions for that system. ## Do more decimal places mean a more accurate position? No. Extra decimal places describe how finely a number is written; they do not prove that the underlying position was measured accurately. Adding zeros changes neither the position nor the quality of the measurement. A correctly converted coordinate can still represent a misplaced pin, an old location or an uncertain GPS fix. Check what the app is displaying: a selected map point, a saved waypoint, a current device position or a last-known position. Use the app's documentation where those indicators are unclear. The [archived GPS.gov accuracy explanation](https://archive.gps.gov/systems/gps/performance/accuracy/) identifies blocked and reflected satellite signals among sources of positioning error. Buildings and trees can affect reception. A detailed display should not be treated as proof that these effects are absent. Do not move toward an edge, into traffic or onto unsafe terrain to improve reception. Remain in a safe position and use other navigation information. If the coordinate and your surroundings disagree, treat the disagreement as unresolved. ## What should you include when sharing a hiking position? A useful location message identifies the numbers and their context. Copy this structure into your trip notes: - Latitude and longitude, explicitly labeled. - Format: DD, DDM or DMS. - Datum, if known; otherwise marked unknown. - Time of the reading, including the relevant time zone. - Whether it is your current position, last-known position or a selected map point. - Trail or park name, nearby identifiable landmarks and any uncertainty. This separates the intended destination from the sender's actual position. A waypoint named “meeting place” and a live location reading answer different questions. Before the trip, agree how your group will exchange positions and practice interpreting them. Check a familiar location from a safe place, using the original coordinate and the receiving map. The purpose is to catch misunderstandings before you need the information outdoors. ## What if you need to give coordinates in an emergency? Seek help promptly; do not delay an emergency call to convert a coordinate. In the United States, call 911 when emergency assistance is needed; elsewhere use the local emergency number. Read the display carefully, including labels, signs or hemisphere letters, and follow the dispatcher's instructions. The [National Park Service emergency guide](https://www.nps.gov/articles/gtgemergencyplan.htm) advises sharing coordinates, landmarks and trip information when lost. Explain whether your position is current or last known and whether you are uncertain about it. Also give the trail or park name and other requested details. Its guidance for someone lost who cannot safely retrace their steps includes staying put unless there is an immediate threat to life. Follow emergency responders' directions. This coordinate guide is not a complete emergency plan. ## What should you prepare beyond the coordinates? A position is one part of navigation. It does not identify a permitted approach, confirm a bridge is open or show that a path is passable today. Use our [GPX checking guide](/check-gpx-file-before-hike/) to examine a route file separately, and [offline map preparation guide](/prepare-offline-trail-map/) to test your map coverage before departure. The [National Park Service Ten Essentials](https://www.nps.gov/articles/10essentials.htm) includes navigation equipment and knowing how to use it. Carry appropriate backup navigation and power, check current official conditions and leave a trip plan with a trusted person. Learn and practice the necessary map and compass skills before relying on them outdoors. ## Sources - [NOAA: What is latitude?](https://oceanservice.noaa.gov/facts/latitude.html) - [NOAA: What is longitude?](https://oceanservice.noaa.gov/facts/longitude.html) - [USGS: Commercial data coordinate dictionary](https://www.usgs.gov/centers/eros/science/usgs-commercial-data-purchases-data-dictionary) - [Google Maps: Find or search for coordinates](https://support.google.com/maps/answer/18539?hl=en&co=GENIE.Platform%3DDesktop) - [Ordnance Survey: Geodesy and positioning FAQ](https://www.ordnancesurvey.co.uk/geodesy-positioning/os-net/faq) - [USGS: NAD27 to NAD83 shift](https://www.usgs.gov/faqs/how-large-north-american-datum-1927-nad-27-nad-83-shift) - [GPS.gov archive: GPS accuracy](https://archive.gps.gov/systems/gps/performance/accuracy/) - [National Park Service: Outdoor emergency plan](https://www.nps.gov/articles/gtgemergencyplan.htm) - [National Park Service: Ten Essentials](https://www.nps.gov/articles/10essentials.htm) ## Frequently asked questions **Are latitude and longitude always written in that order?** Google Maps search expects latitude first and longitude second. When receiving coordinates from another source, follow the receiving system's labels and documentation instead of assuming the order. Label both values when sharing them. A pair of swapped values can sometimes remain within valid numerical ranges while pointing to the wrong place. **How do you convert GPS coordinates to decimal degrees?** Add the degrees, minutes divided by 60, and seconds divided by 3,600. Then apply the hemisphere to the entire result: south and west are negative in signed decimal notation. For example, 40 degrees 30 minutes 18 seconds north becomes 40.505 degrees. Keep the original coordinate and verify the input format. **Does a negative GPS coordinate mean south?** A negative latitude means south of the equator. A negative longitude means west of the prime meridian. The sign belongs to its own value, so label latitude and longitude separately. When entering coordinates, follow the app's requested sign or hemisphere convention and check that the plotted region matches the source. **Do six decimal places guarantee an accurate GPS location?** No. Decimal places describe the representation of a number, not the accuracy of its measurement. A detailed coordinate can still be an uncertain fix, saved waypoint, selected map point or last-known position. Check what the device is displaying and compare it with other navigation information while remaining in a safe place. **Should I convert coordinates before calling for emergency help?** Do not delay an emergency call to convert coordinates. Read the display with its labels, signs or hemisphere letters and follow the dispatcher's instructions. Explain whether the position is current or last known, and state uncertainty. Give the trail or park name and landmarks as requested; coordinates are only part of the information responders need. --- # Prepare an Offline Trail Map That Works > Prepare an offline trail map by downloading the route, approaches, alternate exits, and surrounding terrain at multiple zoom levels. Import only a checked route file, then close the app, enable airplane mode, reopen it, pan and zoom across the coverage, and verify outdoors that satellite location updates without cellular data. Confirm route segments, waypoints, labels, and map detail survived. Plan battery and weather protection, carry a paper map and compass with the skills to use them, check official alerts before departure, and share a trip plan with a trusted contact. Source: https://megatrail.info/prepare-offline-trail-map/ Publisher: Trail File Published: 2026-07-19 Updated: 2026-08-26 ## Prove the map works without a network Prepare an offline trail map by downloading coverage for the entire route, approaches, alternative exits, and surrounding terrain; importing any checked route file; and then testing the exact device in airplane mode before leaving home. Confirm the map renders at useful zoom levels, location updates, labels remain readable, and saved waypoints and route geometry are present. Offline mapping is one part of navigation. Carry an appropriate paper map and compass and know how to use them. Check current official conditions separately, share a trip plan, and never let a successful download make an unsuitable route suitable. ## Download a wider area than the line Use a reputable map source appropriate to the location and activity. Select coverage that includes the trailhead, parking or transit approach, complete route, nearby roads, drainages, ridges, junctions, possible retreat paths, and an intentional margin beyond them. Zoom through the downloaded area before disconnecting. Some tools store only selected regions or levels of detail; controls and limits vary by application, subscription, device, and map license. Follow current official documentation for the exact version you use rather than an old screenshot tutorial. For U.S. national parks, the [National Park Service](https://www.nps.gov/subjects/trails/where-can-i-hike.htm) advises downloading park information for offline use where cell service is limited. Always compare app data with the park's current official trail page and alerts. Browse [offline navigation](/offline-navigation/) for more device-and-backup preparation. ## Import only a checked route Before importing a GPX or similar file, verify its source, date, geometry, access, and limitations. Our [GPX inspection guide](/check-gpx-file-before-hike/) explains the preflight. Keep the source file and your edited copy separately named. After import, compare the displayed line against the source. Look for missing track segments, straight connectors, shifted points, lost waypoints, changed colors, or a start marker in the wrong place. Software can interpret routes and tracks differently. Add only useful waypoints: trailhead, critical junctions, water sources whose current availability has been verified, camps or permits as applicable, exit points, and known hazards from authoritative current information. Do not clutter the display until every icon looks equally urgent. ## Run an airplane-mode test Charge the device, enable airplane mode, and ensure Wi-Fi is off for the test. Reopen the app from a fully closed state. Pan across the complete area and zoom in and out. Confirm terrain, contours, trail names, roads, labels, and route data remain available. Go outdoors where the device can obtain a satellite position and confirm that location works without cellular data. GPS reception and map downloads are separate functions: a phone may know its coordinates while showing a blank map, or show a map while lacking a reliable position. Do not rely on a simulated or cached screen viewed moments after disconnecting. Restarting exposes missing data more honestly than a map still borrowing from memory like a student who did not realize the exam had begun. ## Prepare power and weather protection Learn the device's actual battery performance with the screen, location, temperature, and tracking settings you plan to use. Carry an appropriate charged power bank and cable, protect connections from moisture, and keep electronics insulated from severe cold or heat as the manufacturer directs. Reduce unnecessary battery use, but do not disable a safety or communication feature without understanding the consequence. Record key route information outside the phone. A screenshot can help with a reference, but it lacks the full scale, coordinate, and surrounding detail of a proper map. Visit [route files](/route-files/) when exported data needs another check. ## Carry independent navigation and a trip plan Bring a current paper topographic or trail map covering the wider area, a suitable compass, and the skills to orient and use both. Protect the map from weather. The NPS trip-planning guide recommends navigation tools, a backup physical map, extra phone power, and a plan shared with a trusted contact. Give that contact the route, group, vehicle, start, expected return, contingency, and instructions for when and how to seek help. Check back promptly after the trip. At the trailhead, read current signs and alerts and reassess weather, group condition, water, daylight, and access. If observed conditions conflict with the download, the download loses. An offline map is ready when it survives disconnection, restart, and scrutiny—and when you remain ready to turn around with a fully charged ego left unused. ## Frequently asked questions **How much area should I download around a trail?** Include the trailhead and approach, full intended route, nearby roads, ridges, drainages, junctions, possible retreat or exit paths, and a useful margin beyond them. The right margin depends on terrain, remoteness, route complexity, and map scale. Inspect all required zoom levels because some applications limit what a region stores. A narrow ribbon around the line can leave you without context precisely when you move away from it. **How do I test whether a map is really offline?** Finish the download, close the app completely, enable airplane mode, ensure Wi-Fi is off, and reopen it. Pan across the entire area and zoom through the levels you expect to use. Confirm route data and labels remain. Then go outdoors and verify the location marker updates. Restarting is important because a screen viewed immediately after disconnecting may still display cached tiles that were never saved for later use. **Does phone GPS work without cell service?** A phone can often calculate position from satellite signals without cellular data, but hardware, settings, permissions, sky view, and conditions affect performance. Position and map imagery are separate: the device may know its coordinates while the basemap is blank. Test the exact phone and app outdoors in airplane mode before the trip. Carry independent navigation and do not interpret one successful test as a guarantee in every location. **What backup should I carry for an offline map?** Carry a current paper topographic or trail map that covers the wider area, a suitable compass, and the skills to orient and navigate with both. Protect the map from weather. Also record essential route and emergency details outside the mapping app and plan power appropriately. A screenshot is a supplement, not a full paper-map replacement, because it may omit scale, coordinates, surrounding terrain, and alternative routes. **Can I trust a crowd-sourced trail map?** Use it as one input, not the authority for current access or safety. Community data can be helpful but may be outdated, mislabeled, recorded off route, or drawn through closed or private land. Compare it with current land-manager maps, alerts, permits, signs, and local guidance. If the official source and downloaded line conflict at the trailhead, follow the official restriction and observed conditions rather than the more visually persuasive screen. --- # How to Read Contour Lines on a Hiking Map > Read the map key for the contour interval and units, then trace labelled lines: each contour joins points at the same height. Compare spacing to understand the terrain, but do not treat contours as trails or proof of safe access. Check current official conditions and carry backup navigation you know how to use. If lost and unable to retrace safely, seek help; in the United States call 911 and stay put unless there is an immediate threat to life. Source: https://megatrail.info/read-contour-lines-on-hiking-map/ Publisher: Trail File Published: 2026-10-10 Updated: 2026-10-10 ## How do you read contour lines on a hiking map? Read the map key for the contour interval and units, then trace labelled lines: each contour joins points at the same height. Compare spacing to understand the terrain, but do not treat contours as trails or proof of safe access. Check current official conditions and carry backup navigation you know how to use. If lost and unable to retrace safely, seek help; in the United States call 911 and stay put unless there is an immediate threat to life. Start at home with a complete map, including its key. This guide explains a reading skill and a fictional arithmetic exercise; it is not a route recommendation or a substitute for navigation training. Keep the identity of the map beside your notes so its units and symbols do not become separated from the numbers you copy. ## What does a contour line represent? [Ordnance Survey's beginner guide](https://osmaps.com/discover/guides/understanding-map-contour-lines-for-beginners/) defines a contour as joining points of equal height above sea level. Follow a line to a label when one is not immediately visible. Some contours are unlabelled; nearby labelled contours help establish their height. Do not confuse a contour with the route you intend to walk. On your own map, identify the legend entry for a trail separately from the entry for relief. If an app's route overlay hides the underlying map, inspect the map without that overlay before relying on your interpretation. Consult that app's documentation for its actual controls. ## What is the contour interval? The interval is the vertical height difference between successive contours. [OS's advanced guide](https://osmaps.com/discover/guides/advanced-contours-and-relief/) directs readers to the map key for the interval used. Read the units too. Record these fields before calculating anything: - Map title or saved map-layer name. - Contour interval and its unit. - Two legible contour labels around the area being studied. - The direction in which the labelled heights increase. Keep an uncertain reading marked uncertain. Do not decide that a partly hidden digit must be the value that makes your calculation work. Find a clearer label or a better view of the same map. Our [coordinate guide](/how-to-read-gps-coordinates/) covers a different task: identifying and sharing a position. ## How do you count elevation steps correctly? Use this invented desk example. It represents no real trail, map or destination. Suppose a training sketch specifies a 20-metre contour interval and shows an uninterrupted uphill sequence from a labelled 240-metre line to a labelled 320-metre line. | Line reached | Height | Increase from starting line | |---|---|---| | Starting line | 240 metres | 0 metres | | Next line | 260 metres | 20 metres | | Next line | 280 metres | 40 metres | | Next line | 300 metres | 60 metres | | Final line | 320 metres | 80 metres | The difference is 320 - 240 = 80 metres. Dividing 80 by the stated 20-metre interval gives four steps. There are five lines including both endpoints, but only four intervals between them. Counting both endpoints as additional climbing would give the wrong result. Now change the fictional itinerary: start at 240 metres, climb to 320, descend to 280, then climb to 340. The arithmetic changes: - First ascent: 320 - 240 = 80 metres. - Descent: 320 - 280 = 40 metres. - Second ascent: 340 - 280 = 60 metres. - Combined ascent in this simplified exercise: 80 + 60 = 140 metres. - Finish minus start: 340 - 240 = 100 metres. The 100-metre endpoint difference and 140-metre combined ascent answer different questions. This exercise assumes the stated segments contain no other rises or dips. It does not estimate the total ascent of a real GPX recording. Use the separate [GPX inspection guide](/check-gpx-file-before-hike/) for file-specific checks. ## What does close spacing tell you? OS explains that closer contours indicate steeper slopes. Compare within the same map scale and interval. Its advanced guide warns that small features can fall between contours and ground slopes can vary. Spacing cannot certify safe passage. Use the pattern to form a question for further checking, not a shortcut. For example: "This part of the mapped route crosses a closely spaced section; what does the current official route description say about that section?" That is a reading prompt, not permission to select a different line across the hillside. ## How can you check your interpretation before a trip? Write a short map-reading record while the full key is available. Our suggested headings are **observed**, **calculated** and **unresolved**. In the training example, "the key says 20 metres" belongs under observed. "Four intervals account for 80 metres" belongs under calculated. "Does this describe the whole ascent?" remains unresolved until you have examined the complete sequence. Do not copy the calculated column into a trip plan as though it settled the unresolved one. For a real route, note which sections need further explanation from the land manager or a qualified navigation instructor. Check current official route information and restrictions before travel. An arithmetic check cannot answer whether a gate is locked, a crossing is usable or a trail is closed. Avoid adding an inferred shortcut to your route file. [NPS's Ten Essentials guidance](https://www.nps.gov/articles/10essentials.htm) says to learn your navigation tools before going out, bring a physical backup map and extra phone power, and tell someone where you are going and when to expect you back. Read the park's current information. Our [offline map guide](/prepare-offline-trail-map/) covers download and device checks separately. ## What if the map and your surroundings disagree? Stop somewhere safe and assess. The [NPS emergency plan](https://www.nps.gov/articles/gtgemergencyplan.htm) advises retracing only if safe. If lost and unable to retrace, call 911 in the US and describe your location. Stay put unless there is an immediate threat to life. Elsewhere use the local emergency number. Follow responders' instructions; do not enter hazardous terrain. ## Sources - [OS: beginner contour guide](https://osmaps.com/discover/guides/understanding-map-contour-lines-for-beginners/) - [OS: advanced contours and relief](https://osmaps.com/discover/guides/advanced-contours-and-relief/) - [NPS: Ten Essentials](https://www.nps.gov/articles/10essentials.htm) - [NPS: outdoor emergency plan](https://www.nps.gov/articles/gtgemergencyplan.htm) ## Frequently asked questions **Does following a contour mean following a trail?** No. A contour connects equal-height points; it is not a trail designation. Identify the trail symbol separately in the map key and verify current official access information. Do not create an off-trail route simply because a contour appears to offer a convenient level line. **Do widely spaced contours prove a section is safe?** No. OS explains that features can fall between contour lines and that slopes can vary on the ground. Spacing helps you interpret mapped relief, but it does not establish current access, passability or suitability. Check the route description and conditions rather than selecting a shortcut from spacing alone. **Why are five contour lines only four intervals?** In the fictional example, the starting line is 240 metres and the final one is 320 metres. The four steps are 240 to 260, 260 to 280, 280 to 300 and 300 to 320. At 20 metres per step, that is 80 metres, not five additional increments. **Is the height difference between endpoints the total climb?** Only in a simplified example with no intervening descent. Our invented sequence climbs 80 metres, descends 40, then climbs another 60. Its combined ascent is 140 metres while its finish is only 100 metres above the start. Keep those quantities separately labelled when checking your arithmetic. **What should I do if I cannot locate myself safely?** Stop and assess rather than entering hazardous terrain to match a map feature. NPS advises retracing only if safe; if lost and unable to retrace, seek help. In the US call 911 and stay put unless there is an immediate threat to life. Elsewhere use the local emergency number and follow responders' instructions. ---