Waypoints for glider pilots flying in the Cape, South Africa.

A note on naming: Although pilots usually talk of "turnpoints", this project uses the more general term "waypoints" (WP) to explicitly include Starting Points, Finishing Points, Reporting Points, Airfields, etc. and the actual Turn Points. This is defined in Sporting Code for Gliding (SC3).

---

🇿🇦 To Fly with the waypoints 🇿🇦

To use the WP file on your glide computer (that supports CUP files):

1. Download or copy the latest released ZA_Cape_yyyy-mm-dd.cup CUP file (under Releases' "Assets") to the correct location on your device.
2. Activate it.
3. Fly.

---

Goals

1. One, single point of truth for waypoints, including unique names, unique three character shortcodes (trigraphs), unique locations, and normalised descriptions.
2. Version controlled, with full history (who did what, when, and why).
3. Open source, open data, including all history and versions.
4. Anybody can contribute (and anybody can fork).
5. Automatically incorporated into glide computers that support downloading (e.g. XCSoar)

To View the WPs

1. WaypointsZA master spreadsheet. (Please help us resolve the 🔺red🔺 CGC comments therein.)
2. Generated, current HEAD GeoJSON map.
3. Generated, current HEAD searchable CSV file.
4. Generated, released Google map.

To Contribute and Maintain the WPs

We explicitly welcome contributions, comments, requests, and suggestions.

Please see CONTRIBUTING.md for the details.

---

Precedents

The BGA have been honing their WPs (and the management policies thereof) since 1988. In lieu of our own policies and procedures, please use theirs for guidance:

1. Policy

Arizona gliding community WP documentation (who also use the modern git version control system):

1. Instructions for updating and editing
2. Map
3. Waypoint repository.

---

Out-landings

(Up for debate: please make your voice heard!)

We are attempting to keep a list of out-landing (OL) fields in ZA_Cape_Outlandings.cup.

Rules for inclusion:

1. Special: I.e. we are not going to include every successful out-landing in the vast fields of Porterville.
2. Useful: A permanent field reachable from Robertson Spur is very useful. Or ones along any popular route.
3. Surveyed: By in-person inspection, previous out-landing, cross-country training, etc.

It is a separate file containing only landables (style: "3 Outlanding"), with a low hurdle for accepting contributions.

Please contribute, so that we can improve safety and help introduce new pilots to cross-country flying.

---

Definitions

(Up for debate: please make your voice heard!)

In a WP name field, the following suffixes are defined:

1. # (hash): Air Activity, caution. E.g. Para-gliding launch site (source BGA).
2. 911: Emergency only. Landing area may be too narrow or otherwise unsuitable (source Arizona).
3. U: Unsurveyed. A ground inspection has not been done; data from satellite only (source Arizona).
4. X: Emphasize that a non-landable (e.g. waypoint, bridge, etc.) is indeed, not landable, even if it looks like an airstrip from the air.

Multiple suffixes can be combined (space separated): e.g. "Buffelsport 911 U"

---