Tools
Nothing here ships with a database inside it. A dataset baked into an app goes stale, and it is never quite the one you fly. You build your own in the browser, get a short code, and type it into the watch once. Every tool here is free and needs no account.
Landing fields and airports, from a .cup or
.csv file — the same file your glide computer or SeeYou uses.
Drop the file in, pick the area you fly as a rectangle or a circle on the map, and the page tells you how many sites your watch model holds before you sync. Airports sync before outlanding fields, so a sync cut short by a dropped connection keeps the airports.
Used by GlideRange and GlidePanel.
Step-by-step: From .cup to cockpit
Controlled, restricted and danger areas, from a Naviter
.cub file.
Filter the airspace types you care about down the left of the map, draw the area you fly, and the page counts both the airspaces and their boundary points against your watch's memory — the second number is the one that runs out first.
Used by GlideSpace and GlidePanel.
Step-by-step: Uploading airspace
Build one from openAIP, for anywhere in the world, and get a
.cub out of it.
Click the map to load the airspace around a point, keep the types you care about, and cap the floor so you are not carrying airspace a glider never reaches. NOTAMs can be laid over the top. When it looks right, Send to watch hands the file straight to the airspace uploader.
Feeds the airspace uploader above, for GlideSpace and GlidePanel.
openAIP data is not certified and not for navigation. What you export inherits every error in its source.
Fly a flight you have already flown again, on the ground, from
its .igc file — with the watch on your wrist doing what it did in
the air.
Drop the file in and you get the track back on a map to scrub like a video. A five-digit code puts the watch in simulator mode on the same fixes, so you can stop at a moment you remember and ask it a question: was that field still reachable when you turned back, how close did that airspace get, what did the vario do in that thermal. Everything the watch does from there is the same code that runs in the air.
Used by GlidePanel.
On the watch: Setup › Fix source › Simulator, then type the code — not the sync below, which is for data. Nothing is published and nothing is logged as a flight: the file is held in memory for a few hours and never written to disk, the pilot name and registration in its header are discarded as it is read, and a watch in simulator mode cannot transmit to PureTrack even if it is told to.
The uploader hands you a five-character code. On the watch, open the app's setup and choose the matching sync — the watch fetches your set once through the Garmin Connect app on your phone, which needs an internet connection for that one step. After it lands, the data lives on the watch.
Your watch model is not a detail: it sets how much fits. Scanning the QR code the app shows you opens the uploader with your model already chosen, which is the reason the app draws one at all. Picking a roomier watch than you own by hand produces a code that syncs and then quietly stops part-way through.