![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
![]()
Here are a couple of things I've been asked about several times. I
thought I would post here for wider distribition: Hint #1 - If your glide computer or PNA can't handle the airspace file for the entire US, consider making a custom extract of a smaller region. Here is how you do it: 1. Go to http://www.soaringdata.info 2. Follow the link near the top of the page to US Airport Information 3. Specify bounding information: a. Put in the FAA/IATA airport identifier of the airport at the center of your flying area. Don't put a "K" on the front. b. Set the drop-down box underneath to "Maximum Radius (nm)". Put in the radius of your area of interest. 4. In the "Companion File Formats" area, select the checkbox for "Airspace in Tim Newport-Peace Format". or "Airspace in OpenAir format" 5. Type "Soar" into the provided box, and press "Submit". 6. Download and unzip the resulting file. Hint #2 - By far the most common error I see is people trying to upload Cambridge formatted input turnpoint files. Cambridge is a supported -output- file type but not an input type. Nearly all of these files come right from the Worldwide Soaring Turnpoint Exchange. The solution is to get an input file from the Soaring Turnpoint Exchange with the same data in a supported format: 1. Go to the Turnpoint Exchange at http://soaringweb.org/TP/ 2. Browse to your soaring site of interest. 3. Choose "Files for downloading and importing into your programs" 4. Choose "Soaring Turnpoint Exchange" format, and download the file. "Tab Delimited" also works. 5. Use that file as the input to my site at http://wwww.soaringdata.info. You can request a Cambridge output file (or any of the other supported formats), and my site will do the conversion and update all of the data from the current FAA charting cycle. Hint #3 -- Consider updating more frequently. Airspace and particularly airport data changes more rapidly than you might think. Unfortunately, dozens of airports vanish every charting cycle, but new ones are born as well. Virtually every input turnpoint file I see contains two or three airports that no longer exist. Happy Downloading! Lynn Alley "2KA" |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Improvements in US Airspace/Airport data at www.soaringdata.info | 2KA | Soaring | 10 | December 8th 10 05:08 AM |
ATC subtle hints | kontiki | Piloting | 76 | October 25th 06 01:13 AM |
Hints on Securing L'Hotellier with Wedekind Sleeves | ContestID67 | Soaring | 0 | December 1st 05 08:29 PM |
Hints for parents of 13 year old student pilot? | Jay Honeck | Piloting | 52 | March 29th 04 04:16 PM |
POSA Carb Info and HAPI Engine Info | Bill | Home Built | 0 | March 8th 04 08:23 PM |