Turnpoint list creation checklist

I am in the process of creating / editing a turnpoint list for another site in the US. I have created a few, this time I thought it might be good to gather input on what the best practices to do this as efficiently and accurately as is reasonable. Here the the notes I've written up so far on a check list. I would like to hear any helpful feedback.

* Establish a boundary based on possible best flights on best day ever, and remove all airstrips/airports "well outside" the boundary (items close to the boundary will probably be included for completeness).

* Remove all obviously abandoned/missing airports/airstrips.
Add in airports within the established boundary that are in the nearby databases, but not in the current database.

* Decide which are Turnpoints for contest and badges and what are additional landpoints, Plan points for 300+500km O&R & Triangles, plan to Accommodate the Best Pilot on the Strongest Day.

* Check to see if any TP are listed at 0ft MSL by error.

* Check each point in Google Earth, often the location is very wrong in official databases, do not change FAA data if its not off by more than about 750' in distance or 50'altitude. [bias toward offical data].

* Review special use airpace in task area.

* Separate turnpoints for Start and Finish?

* Verify Attributes, HSFTA, G

* Verify spelling

* Convert Metric Alt to feet if needed [or inverse]

* Renumber

* Sort all points alphabetically and see if any truncated names would be identical, such as a Turnpoint name Etowah, and a landable point called Etowah Bend.

* Names should not include special characters which are incompatible with 1 or more gps systems, examples: , ' * ! : ; & $

* Turnpoint names which start with numbers can be bad: number 2 which was 411X64 in the current database is a bad name for some software since it shows up as 02411X64 and computers think it is turnpoint number 2411 and put it at the bottom of lists.

* Names need to work (be differentiated) when truncated down to 6 and 8 characters, some navigation systems only display 6 characters, also some TP file formats have 2 numbers at the front of the name so that takes away 2 letters. Some systems such as SeeYou will abbreviate by eliminating vowels, this can make some names worthless and will need to be edited to have critical vowels.

* Regarding coordinate correction, Generally, John L's process "snaps" coordinates within a given radius of official airport coordinates to the airport coordinates. Of course this is not always appropriate (coordinates wrong etc). So give him a list of stuff not to snap and he will code it to be left alone."

* Recheck names and positions after getting back from Leibacher.

* Test import into scoring program, Winscore or SeeYou, and cockpit nav programs if possible.

* Review with other stakeholders.

* Approve for release.


---

On a side note the more I discuss with people which landout spots should be included the more I want to add more points. I hear comments like that "field could have a crop in it", or it might not be usable due to such and such. The same can be said of airports, I've see airports be closed due to accidents or maintenance, or to be converted into farm fields or housing developments. Perry last year had something like 2 gliders blocking 2 parts of the runway at the same time - a gear up and something else, pretty much made it hard to use for the people low in the pattern.

As far as I can tell there is no way to guarantee that ANY field, paved or grass runway will be available or useable when you want it. All points in a turnpoint file should be considered with suspicion until you get to inspect it from the landing pattern.


Chris