Tools
The apps ship with no built-in database, deliberately: a dataset baked into an app goes stale, and it is never the one you fly. You build your own set in the browser, get a short code, and type it into the watch once. Both uploaders are free and need no account — you do not have to own an app to try them.
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
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.