Appendix: what's inside a PitStopper GPX file

A GPX file from PitStopper is not "plain GPX". It is a valid GPX 1.1 file that any app can open, but it carries extra information that the GPX standard has no place for: the route's line colour and width, turn-by-turn instructions, POI icons and colours, and estimated times. This page lists the additions, which export option controls each, and exactly where in the XML it goes - useful if you write your own tools, compare files, or wonder why another app shows more (or less) than you expected.

Will it break my app? No. Everything extra lives either in standard GPX elements (filled with values a particular app understands) or inside <extensions>, which apps that don't recognise it simply skip. Our exports are checked against the official GPX 1.1 schema in our tests.
The three-minute version: the standard parts coming in, each app's extras, and everything going back out. Watch it on its own page, with the transcript.
To see what a file of your own carries - every extension, which app it comes from, and anything PitStopper does not read yet - open it in the GPX inspector and converter. It runs in your browser, and can write the file back out with all of the additions on this page.

GPX in brief

A GPX file is XML: elements nested inside each other, in an order the GPX 1.1 standard fixes. These are the ones that matter here.

ElementWhat it isIn a PitStopper file
<gpx>The root that holds everything. Says which GPX version it is, which program wrote it (creator) and which extra vocabularies (namespaces) it uses.One per file
<metadata>About the file itself: its name, author, links, the time it was made.The route name, a link to PitStopper and the export time
<wpt>A waypoint: a single place, at a latitude and longitude, with an optional name, description and symbol. Not part of the line.Your stops, and distance markers
<rte> / <rtept>A route: an ordered series of turn points leading to a destination. How a device gets between them is up to the device.The app exports the line itself, as a track. The GPX inspector's converter writes a file's own route back out as it came, Garmin via and shaping points included; untick Keep the file's route (rte) for a smaller file
<trk>A track: the line itself, as an ordered list of points to follow exactly.One per route
<trkseg>A segment of a track: one unbroken run of points. A track splits into segments where the line has a gap, such as a recording paused or lost signal.One per track (a navigation track kept exactly as you imported it keeps its own)
<trkpt>A track point: one point on the line. It can carry the same child elements as a waypoint.The route's points, and where turn-by-turn instructions sit
<extensions>A box for anything the standard has no element for, written in another vocabulary. Allowed in most elements; apps that don't know its contents skip it.Line colour, POI icons and colours, surface
Inside a waypoint or track point
<ele>, <time>Elevation in metres, and a time (UTC).Elevation from the route; estimated times if you ask for them
<name>A short name.The stop's name; on a track point, the name of a point you placed on the route
<cmt>, <desc>A comment, and a longer description.Your note and type for Ride with GPS; the category, opening hours and contact details. On a track point, <cmt> is the road a turn leads onto
<src>, <link>Where the data came from, and a web link.On stops: OpenStreetMap, and a link to the place on openstreetmap.org. On a route planned here: the planner that drew it, and beeline or osm on the point that ends a straight-line or any-path stretch
<sym>The name of the symbol to draw it with. The standard does not say which names exist; each app has its own list.Garmin symbol names on stops; turn instructions (left, roundabout_e3) on track points
<type>A free-text classification.The kind of stop (FOOD, WATER); via or shaping on route points you placed

Because the standard leaves <sym>, <type> and <cmt> open, much of what makes a PitStopper file useful is values other apps agree on, not new elements. Everything else goes in <extensions>.

Which app reads these?

We don't keep a list. Apps change what they read from one version to the next, often without saying so, and a table of it would go out of date while still looking like a reference. This page sticks to what a file contains and where. To see what a file of your own carries, open it in the GPX inspector; for what an app reads, its own documentation is the place (some are linked under From the apps themselves). If an app reads our file differently from what you expect, please tell us.

Where each addition lives

The options are in Export → Export a file, with GPX selected (see Export GPX). "Always" means it is written without an option.

WhatOption (default)Where in the XMLNamespace
The track
Line colour, width and transparencyInclude the route line colour and width (on). Set them per route in Route Settings or the route manager<trk><extensions>, three ways in this order: gpxx:TrackExtension (nearest of 16 colours, or Transparent), gpx_style:line (color, opacity, width in screen pixels), xsi:gpx (color as #RRGGBB, or #AARRGGBB when transparent, and width)gpxx, gpx_style, xsi
CorridorWritten with the line colour and width (on). Set the corridor per route in Route Settings<trk><extensions><xsi:gpx>: <physicalWidth> (the whole band, in metres) and <physicalColor> (#AARRGGBB). See PitStopper's own elementsxsi
Turn-by-turn instructionsAlways, on a route planned here with turn-by-turn on, or a track rebuilt on roads<trkpt>: <name>, <cmt> (road name), <sym> (left, right, roundabout_e3, pass_place...), <type> (via or shaping)standard elements
SurfaceAlways, on a rebuilt track<trkpt><extensions><xsi:gpx><route_information> (paved, unpaved), where it changesxsi
Estimated timesInclude estimated times on the track and waypoints (ticked when there is a start time)<trkpt><time> and <wpt><time>standard
Where a planned route leaves the roadsAlways, on a route planned here<trkpt><src>beeline</src> or osm on the point that ends a straight-line or any-path stretch; the track's own <src> names the plannerstandard elements
Your original file's extrasAlwaysA track that arrives with turn-by-turn or extra per-point data (power, heart rate...) is written back as it came, extensions and all - except that the line colour, if included, is written in all three forms (it is the file's own colour unless you change it), and estimated times are added if you ask for them. The file's top-level <extensions> are kept when only one route is loadedthe original file's own
Waypoints (your stops)
Garmin symbolAlways<wpt><sym> (Restaurant, Drinking Water...)standard
Course-point typeAlways<wpt><type> (FOOD, WATER...)standard
Type for Ride with GPS, and your noteAlways<wpt><cmt> (coffee. Closes early Sunday). A stop imported from another app keeps that file's own comment, with your note added after itstandard
Opening hours, website, phoneAlways<wpt><desc>. A stop imported from another app keeps that file's own description unchangedstandard
OpenStreetMap linkAlways, for OpenStreetMap places<wpt><src> and <link>standard
Web linksAlways<wpt><link>: the links a stop was imported with, then its OpenStreetMap page, then its web sitestandard
Elevation and time a stop arrived withAlways, for a stop imported from a file that has them<wpt><ele> and <wpt><time>. A time from another app's file is written back as it was and wins over an estimated time; a time in a file PitStopper wrote is only an estimate, so it is worked out againstandard
Photos on a stopGPX + icons & photos (.gpz) in the route export, or Compress it (.gpz) in Export POIs only, for a stop imported from a .gpz with photos<wpt><link href="files/photo.jpg">, with the photo itself in the archive at that path. A plain .gpx has no file for the link to name, so it leaves these outstandard
OsmAnd iconAlways, for OpenStreetMap categories<wpt><extensions><xsi:gpx><icon> (amenity_cafe)xsi
Marker shapeA circle on stops that have an OsmAnd icon; starred and flagged shapes are yours to choose (square, octagon)<wpt><extensions><xsi:gpx><background>xsi
POI colourInclude POI category colours (off)<wpt><extensions><xsi:gpx><color>xsi
Starred and flagged colourShown when you have starred or flagged stops<wpt><extensions><xsi:gpx><color>, in place of the category colour on those stops (Garmin has no waypoint colour)xsi
Direction and planned time in the nameAdd direction to name (suffix), Add planned time to name (off)<wpt><name> (Cafe L20m 15:15 - the name is shortened more to make room for the time)standard
Distance markersWhen you have added them (not in separate-file exports)<wpt> with <type>km_marker</type> or mile_markerstandard
Compressed files
Our own POI icons, and yoursGPX + icons & photos (.gpz) in the route export (icon files under Advanced options), or Compress it (.gpz) then Send our icons with it in Export POIs only<wpt><sym>PS_cafe</sym>, <xsi:gpx><anchor>, and PNG/SVG files inside the zip. Your own icons (see POIs) use the separate PSU_ namespace instead, such as PSU_cafe_3f9a1c: a slug (the category, or the file's name) plus six characters of the icon's id. Each carries the anchor you chose for it (hsbc, bottom centre, for a picture you upload; hscc, centre, for one that came in a .gpz that gave none), and its PNG, and SVG when it has one, sits in the zip beside the route. Ours are centred (hscc). A stop that kept its own <extensions> on import is left as it was.xsi

Photos and attachments in a .gpz

A waypoint, track or route names its photo with a standard <link> whose href is a path inside the archive; the picture sits in the zip at that path. A stop from a .gpz made in Locus Map looks like this:

<wpt lat="51.0411449" lon="3.9846805">
  <ele>6.49</ele>
  <time>2026-10-07T06:06:14.000Z</time>
  <name>Kapel</name>
  <link href="files/screenshot_20260504-175910.png"></link>   <!-- the photo, in the zip -->
  <sym>Scenic Area</sym>                                   <!-- the icon: "Scenic Area.png" in the zip root -->
</wpt>
  • Read - the path is resolved from the archive root (exact case first, then any case). Only files a link names are unpacked. A picture (checked by its contents: JPEG, PNG, WebP or GIF) is a photo; any other file (PDF, document, audio, video, web page) is kept as an attachment with its bytes untouched, offered for download and never rendered. Limits: 10 MB a file, 40 MB in all.
  • Kept - the original bytes, stored once per picture (by a SHA-256 of its contents) in the browser's own database, with the link left exactly as written.
  • Written - a .gpz export puts each photo and attachment back at its path, under files/, with the same <link> (on the <trk>, after its name, for a track's). Two different photos that claim one path: the second gets -2 added. A photo outside files/ is moved into it, so it cannot meet an icon (icons sit in the archive root). A plain .gpx leaves relative links out; http, https and mailto links are always written.
  • Also on that waypoint - <ele> becomes the stop's elevation and <time> its own time, and both are written back; the <sym> picture becomes the stop's icon (see Icons in a .gpz).

For how this looks in PitStopper, see Photos and attachments in a .gpz.

Namespaces

PrefixURIDeclared
(default)http://www.topografix.com/GPX/1/1Always, on <gpx>
xsihttp://www.w3.org/2001/XMLSchema-instanceAlways, on <gpx>. The <xsi:gpx> block - a convention started by Cruiser - reuses it, so it needs no declaration of its own
gpxxhttp://www.garmin.com/xmlschemas/GpxExtensions/v3On <gpx>, only when the file uses it
gpx_stylehttp://www.topografix.com/GPX/gpx_style/0/2On <gpx>, only when the file uses it
Any other, such as trpAs the imported file had it (trp: http://www.garmin.com/xmlschemas/TripExtensions/v1, Garmin's via and shaping points)Once, on <gpx>, when a carried route or track uses it

An annotated example

A shortened export with most options turned on: one distance marker, one starred café, and a track with a turn, a roundabout and a change of surface.

<gpx version="1.1" creator="PitStopper.net"
  xmlns="http://www.topografix.com/GPX/1/1"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3"
  xmlns:gpx_style="http://www.topografix.com/GPX/gpx_style/0/2"
  xsi:schemaLocation="http://www.topografix.com/GPX/1/1 https://www.topografix.com/GPX/1/1/gpx.xsd">
  <metadata>...</metadata>

  <wpt lat="51.041" lon="3.99">                     <!-- a distance marker -->
    <time>2026-10-05T08:04:00Z</time>               <!-- estimated times -->
    <name>1 km</name><desc>1 km</desc><sym>Dot</sym><type>km_marker</type>
  </wpt>

  <wpt lat="51.0455" lon="3.9902">                  <!-- a starred cafe -->
    <time>2026-10-05T08:02:00Z</time>
    <name>Cafe Centr L20m</name>                    <!-- short name + "on your left, 20 m" -->
    <cmt>coffee. Closes early Sunday</cmt>          <!-- type + your note -->
    <desc>Full name: Cafe Centraal. Cafes. Hours: Mo-Sa 08:00-18:00</desc>
    <src>OpenStreetMap</src>
    <link href="https://www.openstreetmap.org/node/11">...</link>
    <sym>Restaurant</sym>                           <!-- Garmin symbol -->
    <type>FOOD</type>                               <!-- course-point type -->
    <extensions>
      <xsi:gpx>
        <color>#FFFF00</color>                      <!-- starred colour (else the category colour) -->
        <background>square</background>             <!-- starred shape -->
        <icon>amenity_cafe</icon>                   <!-- OsmAnd icon -->
      </xsi:gpx>
    </extensions>
  </wpt>

  <trk>
    <name>My ride</name>
    <extensions>                                    <!-- line colour and width -->
      <gpxx:TrackExtension><gpxx:DisplayColor>DarkBlue</gpxx:DisplayColor></gpxx:TrackExtension>
      <gpx_style:line><gpx_style:color>1976D2</gpx_style:color><gpx_style:width>5</gpx_style:width></gpx_style:line>
      <xsi:gpx><color>#1976D2</color><width>5</width></xsi:gpx>
    </extensions>
    <trkseg>
      <trkpt lat="51.05" lon="3.99"><ele>3</ele>
        <extensions><xsi:gpx><route_information>paved</route_information></xsi:gpx></extensions>
      </trkpt>
      <trkpt lat="51.0455" lon="3.99"><ele>4</ele>
        <cmt>High Street</cmt><sym>left</sym>       <!-- turn left onto High Street -->
      </trkpt>
      <trkpt lat="51.041" lon="3.99"><ele>5</ele>
        <sym>roundabout_e3</sym>                    <!-- roundabout, third exit -->
        <extensions><xsi:gpx><route_information>unpaved</route_information></xsi:gpx></extensions>
      </trkpt>
    </trkseg>
  </trk>
</gpx>

From the apps themselves

Where the apps describe their own support. These are their words, as they stood when we read them; apps change, so check the app itself.

PitStopper's own elements

A few things PitStopper keeps have no element in any existing GPX extension. For those we add our own, inside the <xsi:gpx> block that Cruiser, OsmAnd and Locus Map already read. The rule for them is simple: an app that doesn't know an element skips it, so they never break a file. We keep them few, plain and documented here, so any app can read them too.

ElementOnValueMeaning
<physicalWidth><trk>, <rte>Metres, a whole numberThe route corridor: the full width of the band, so half of it either side of the line. The same measure as KML's gx:physicalWidth.
<physicalColor><trk>, <rte>#AARRGGBBThe corridor's colour, alpha first as in <color>. PitStopper writes the line colour at 25% (#40); when it reads a file the corridor follows the line colour.
<trk>
  <name>Morning ride</name>
  <extensions>
    <xsi:gpx>
      <physicalWidth>40</physicalWidth>        <!-- the band, under: 40 m, 20 m either side -->
      <physicalColor>#401976D2</physicalColor> <!-- the line colour, 25% -->
      <color>#1976D2</color>                  <!-- the line, on top -->
      <width>4</width>
    </xsi:gpx>
  </extensions>
  <trkseg>...</trkseg>
</trk>

They come before <color> and <width>, in drawing order: the band underneath, the line on top. A KML export keeps the same order, writing the band's placemark before the route's. The corridor elements were suggested by one of our users (October 2026), so that a band needs no second track. The GPX inspector names both elements, checks <physicalColor> is a valid colour, and shows the corridor in its summary and in "In and out".

Good to know

  • Colours come in as well as go out. When you load a GPX file, a track keeps the colour, width and transparency it was given, read from gpx_style first, then xsi:gpx, then Garmin's colour name; a KML line style is read too. On export the same look is written in all three forms, so a route coloured in one app arrives coloured in the others. Garmin can only take the nearest of its 16 colours, with no width. Locus Map's own line settings inside gpx_style:line (such as a line pattern) are kept and written back, with Locus's copy of the colour and width brought in step with yours.
  • Transparency is set per route in Route Settings or the route manager: solid, 25%, 50% or 75% transparent, or fully transparent. Fully transparent means "hidden in other apps" - it is exported as Garmin's Transparent and an opacity of 0 - while PitStopper still draws the route, dashed, so you can see it.
  • Width is set in Route Settings with a slider, from 1 to 24 px, and a preview above it shows the line with its colour, transparency and dash before you save. The route manager keeps four quick widths. The width goes out in all three forms.
  • A corridor (Route Settings) draws a see-through band in the route's colour so many metres either side of it, keeping its ground width as you zoom. It travels in every format that can hold it, and comes back in: in GPX and .gpz as <physicalWidth> on the track (see PitStopper's own elements); in KML and .kmz as a second line under the route with gx:physicalWidth, the form Google Earth and Locus Map draw. When PitStopper opens a KML, that second line becomes the route's corridor again, not a route of its own. FIT has no form for it.
  • The track colour is written three ways because each app family reads a different one: Garmin's gpxx first, then gpx_style, then xsi:gpx - the order a Locus and Cruiser user reported some readers need (see the sources above).
  • How a section was routed travels in the track point's <src>: beeline for a straight line, osm for any path. These two mean the same in every router, so they are worth keeping: Cruiser leaves a beeline section straight when it recalculates the route (it has no any-path profile, so it ignores osm). Locus Map reads neither yet; its developer has been asked. Cruiser also writes its profile's name there (fastest, curvy and so on); PitStopper keeps those as they are, but other routers will not draw the same road from them. (From a Locus and Cruiser user, November 2026.)
  • Several routes in one file ("Combined", the default) give one <trk> per route, each in its own colour. "Separate files" gives a zip of single-route GPX files.
  • Icons come in as well as go out. A .gpz from another app brings the PNG for each <sym> its stops use (pictures no stop uses are left out); PitStopper offers to draw the stops with them, and writes the same symbol name and original picture back when a stop wearing one is exported in a .gpz with icons. The file's own anchor (hscc in Cruiser's reference file) is kept when its stops agree on one, and each stop's <scale> draws its icon that much bigger or smaller.
  • Locus Map and .gpz icons (from a user's testing of the Locus Map beta, October 2026): it reads SVG icons from a .gpz as well as PNG, and when both are there it uses the SVG. It draws every .gpz icon with its bottom centre on the spot (hsbc), whatever anchor the file asks for, and does not use a waypoint's <anchor> or colour yet. So in Locus our own icons, which are centred artwork, sit just above the place; your own icons default to bottom centre, which is what Locus does anyway.
  • A stop you imported keeps its own <extensions> from the original file, in place of the icon, colour and shape PitStopper would add. From another app's file it also keeps its own <desc>, <cmt> and <link> entries.
  • Export POIs only writes no colours, but still adds the OsmAnd icon and marker shape.
  • Times are never invented: estimated times need a start time, and a track that came with recorded times keeps them whatever the option says.
  • FIT and KML carry the same information their own way: FIT as course points, KML as styles and folders. See Export FIT and Export KML.