Building a Route with Waypoints & POIs in a Single GPX

Can One GPX File Hold a Route and Its Waypoints?

Yes — that's exactly what the format was designed for. A GPX file can carry any mix of <wpt> (standalone waypoints), <trk> (the recorded or drawn line), and <rte> (an ordered sequence of points to follow), all in the same file. Waypoints are top-level elements, not children of the track, so a "route bundle" is simply a file with one track plus a set of named waypoints for water sources, camps, junctions, bailout points, and hazards. Every serious app imports the bundle whole: the line draws on the map and the pins land on top of it, and one file — not a folder of fragments — moves the whole plan between devices and people.

What a Waypoint Actually Stores

Each <wpt> is a position plus a handful of optional fields worth using deliberately:

<wpt lat="34.0625" lon="-116.1585">
  <ele>1291</ele>
  <name>WTR_CottonwoodSpring</name>
  <desc>Reliable spring May-Oct, pipe on N side. Treat before drinking.</desc>
  <sym>Drinking Water</sym>
</wpt>

• name is what renders on the map next to the pin — keep it short and front-loaded (more below).
• desc is the field notes: reliability, season, which side of the wash. This is the difference between a pin and intelligence.
• sym requests an icon. Support varies by app — standard names like "Drinking Water" or "Campground" render nicely on many devices and fall back to a generic pin elsewhere. Treat it as a bonus, never as the only signal.
• ele matters for bailout decisions — a water source 400 m below the ridge is a real detour, and the profile won't show off-track elevations for you.

What to Mark (and What Not To)

• Water — every source, with reliability notes in desc. The most valuable waypoint class in dry country.
• Camps — planned sites plus known alternates.
• Bailouts — where the route crosses a road or a shortcut trail home. Mark these before the trip; you will not be researching escape routes calmly at 4 pm in weather.
• Hazards and gates — crossings, locked gates, private-land boundaries, the turn everyone misses.
• Junction confirmations — a pin at each critical fork turns "did we miss it?" into a yes/no answer on the screen.

Restraint is a feature: fifty pins bury the five that matter. If everything is marked, nothing is. And think before publishing sensitive locations — fragile springs, archaeological sites, and private property boundaries deserve the same care as your own privacy when a file leaves your hands.

The Build Workflow

1. Get the line. Record the track on a previous trip, draw it in a route planner, or start from someone else's vetted file.
2. Add waypoints in a planning app. Most route builders and desktop tools (CalTopo and friends) let you drop and name waypoints alongside the route, then export everything as one GPX. This is the comfortable path.
3. Or capture them in the field. Marking positions as you travel beats guessing from imagery — MyGPSWaypoints, this site's iOS waypoint logger, captures named waypoints with photos and exports them as GPX for merging into the route file. (For best accuracy at each mark, give the receiver sky and a moment to settle.)
4. Merge and hand-check. Since GPX is plain text, combining files is moving <wpt> blocks into the track file above the closing </gpx> tag — GPX File Basics shows the anatomy if hand-editing is new to you.
5. Validate the bundle. Run the finished file through the GPX Validator to confirm it parses and reports the expected counts ("1 track, 12 waypoints"), then load it in the GPX Analyzer — waypoints are counted in the file summary, and the map view confirms the pins sit on the line, not in the next valley.

Naming Conventions That Survive a Small Screen

Waypoint names get truncated, sorted alphabetically, and read at a glance in glare. A prefix system fixes all three at once:

Prefixed names group by type in any alphabetical list, read unambiguously when truncated, and carry their category even in apps that ignore sym icons entirely. Verbs in junction names (_GoLeft) put the decision in the name itself.

Frequently Asked Questions

What's the difference between a waypoint, a route point, and a track point?

A waypoint (<wpt>) is a standalone named place. A route point (<rtept>) is one step in an ordered to-follow sequence. A track point (<trkpt>) is one breadcrumb in a recorded or drawn line. POI is app-speak for what GPX stores as a waypoint.

Why don't my waypoints show up after import?

Usually one of three things: the app imported only the track layer (check its import options), the waypoints sit in a separate file that never got merged, or the file is malformed. The validator tells you in seconds whether the waypoints are actually in the file.

Why do my waypoint icons look different in every app?

The <sym> field is a request, not a command — each app maps symbol names to its own icon set and falls back to a generic pin for names it doesn't know. Put the meaning in the name prefix and treat icons as decoration.

Is there a limit to how many waypoints a GPX can hold?

The format imposes none; practical limits come from devices (some older handhelds cap stored waypoints). For a route bundle the practical ceiling is attention, not storage — a couple dozen deliberate pins beat hundreds of noise.

Related Tools and Guides