Worldwide Soaring Turnpoint Exchange
Unofficial Boulder, Colorado Control Points

Files formatted for downloading and importing into your programs

Here are some hints about downloading and importing files.

Courtesy of Clemens Ceipek
Dated: 24 March 2024
Magnetic Variation: 9.3E, Datum: 100
Time zone: US/Mountain, Summer offset from GMT is -6:00 and in Winter it is -7:00.

Information about soaring at Boulder, Colorado is available at soar.boulder.co.us/ssb_misc.htm

The primary specification of the waypoint coordinates is degrees, minutes, and seconds

Potential landout fields have names starting with an "x". After the name there may be a question mark followed by some codes that describe potential/likely hazards associated with that field. I like that because I can see these immediately on the map in advance without having to click on each field and read the notes. In my experience there is often little time to read instruments once I find myself in a situation where I have to consider landout fields. The downside is that these are my codes and someone not familiar with them will not easily understand them. They are described in the article that I referenced above.

Emergency landout fields have names starting with "XX". In the software they are labelled as "unknown" because I don't want the flight computer to mislead me thinking that there may be a viable field. My criteria for these fields is that I would prefer such a field over bailing out but I would anticipate major damage to the glider. I find them useful to have in my database even if I would never want to use any of them.

Some airports are so ill-suited for gliders that I changed their names to begin with an x or xx depending on the field. They may also have question marks after the name with my hazard codes just like landout fields. An example would be Saguache which is a public airport but a narrow 50 ft runway that will not work for an 18m glider because there is typically tall grass on either side of the runway right up to the edge. Ground looping here would be very likely.

Some airports no longer exist and are so bad that they should not be in the database at all. In my initial effort I completely deleted them from my database. An example would be Crystal Lakes which is so narrow with tall banks at the side that I would not want to use it at all. There is a mountain meadow a few miles away that would make for a better (but still very poor) landout. Unfortunately, these unusable airports come back into the file each time I download the updated airport data from soaringdata.info. My current file (that's attached) unfortunately includes these non-existant or otherwise unusable airports again that I had previously deleted. Unfortunately I have found no practical way to avoid this without my database getting out of date (I obviously want to make sure that I periodically download airport data so that UNICOM and AWOS frequencies are up to date) - however, this means that the previously deleted airports keep coming back. I don't know a practical solution for this problem.

With respect to numbering I have stopped using waypoint numbers for airports and landout fields. That's why my numbers start at 500. Waypoints are generally just that, waypoints. If a waypoint starts with a 3-digit number I know I can't land there. The 14er peaks in Colorado (mountains over 14,000 ft tall) have numbers in the 900s.

UNOFFICIAL, USE AT YOUR OWN RISK

Do not use for navigation, for flight verification only.

Always consult the relevant publications for current and correct
information. This service is provided free of charge with no warrantees,
expressed or implied.
User assumes all risk of use.

"Please note that private use airports in the FAA's National
Airspace System are for the use of the owner only or with the
permission of the owner only. Other users are not authorized
and should not be attempting to land at private use airports."

Use is subject to these conditions.

Select to download the indicated material.
Select to view the indicated material.
Select for a description of the material.
appears when the format is not available because its maximum number of waypoints has been exceeded.

Jump down to A, B, C, E, F G, I, K, L, M, O, P, S, T, V, W, X, Z
Airspace ( Tim Newport-Peace format )

Airspace ( Zander format )
  Airspace ( SeeYou® CUB format )
Airspace ( OpenAir® format )

Apollo Precedus®
Borgelt Joey®
Borgelt B2000®
Borgelt B100®
Cambridge Aero Instruments®
Cambridge Aero Instruments® [ control point number after name ]
Cambridge Aero Instruments® [ control point number before name ]
Cenfis/Holltronic® [ IDB format ]
ClearNav® [ STX format ]
Comma Separated
  CouTraCi®
  Eagle AccuNav, more than 200 waypoints, no *.WS-1 or *.WS-2 output
  EasyGPS LOC®
  EasyGPS LOC® [ control point number placed before the name ]
EW View II and III®

  Filser, more than 600 waypoints, no *.DA4 output
  Filser, more than 100 waypoints, no *.ATT output
FLARM®
Flight Check®
Flight Planner®
ForeFlight®
  Garmin BaseCamp®
Garmin PCX5AVD 2.05®
Garmin PCX5AVD 2.07®
Garmin PCX5AVD 2.08®
Garmin PCX5AVD 2.09®
Gardown®
Gardown® 15 character names
G7toWin®
IGCview®
Waypoint+®
Waypoint+® [ control point number after name ]
Waypoint+® [ control point number before name ]
  Google Earth
  Google Earth for SPOT Tracking

Ilec SN-10®
Ilec SN-10® [ DOS 8.3 filename ]

  KFLog embedded®
KFLog®
  LX Navigation, SDI, Posigraph, and Colibri Mk 1, more than 600 waypoints, no *.DA4 output

Memory-Map®
  Peschges VP 6 ver 2.0, more than 250 waypoints, no output
Print Technik® [ simple names ]
Print Technik® [ control point number placed before the name ]
SeeYou [CUP]®
SeeYou® [CUP, DOS 8.3 filename ]
SeeYou® [ control point number placed before the name ]
SeeYou® [ control point number placed before the name, DOS 8.3 filename ]
SkyDemon® [ GPX format]
Soaring Innovations Glide Nav II®
Soaring Innovations Glide Nav® control point format
Soaring Innovations Glide Nav® landing site format

Soaring Turnpoint Exchange [ STI format ]
  Spreadsheet [XLSX]
  StrePla®
Pocket*StrePla®
Tab delimited
Task Finder®
TaskNav®
TaskPlan®
  TomTom®
  Trackmaker®
Trimble SMLTU®
Volkslogger®

Westerboer 921® [ simple names ]
Westerboer 921® [ control point number placed before the name ]
Winpilot®
Winpilot® [ control point number after name ]
Winpilot® [ control point number before name ]

XCSoar [CUP]
XCSoar [CUP] [ control point number placed before the name ]

Zander® [ simple names ]
Zander® [ control point number placed before the name ]

  All of the above plus the control point listings and map zipped together

Return to the Boulder, Colorado Control Points Home Page?
Please contact John Leibacher with any suggestions concerning this material.
This page last updated on

Worldwide Soaring Turnpoint Exchange Unofficial Boulder, Colorado Control Points

Files formatted for downloading and importing into your programs

Here are some hints about downloading and importing files.

Worldwide Soaring Turnpoint Exchange
Unofficial Boulder, Colorado Control Points