(Importing a new version from external source) |
(Updating to match new version of source page) |
||
| Line 9: | Line 9: | ||
You can import airspaces files from the embedded Webserver, in the «Airspace» tab. | You can import airspaces files from the embedded Webserver, in the «Airspace» tab. | ||
| + | |||
| + | You can find a description of the Tim New Port Peace format here: | ||
| + | http://soaringweb.org/TP/sua.html | ||
Important: OpenAir files must have a “.txt” file extension, Tim Newport-Peace must have an “.air” file extension. | Important: OpenAir files must have a “.txt” file extension, Tim Newport-Peace must have an “.air” file extension. | ||
| Line 19: | Line 22: | ||
Once uploaded, the airspaces should appear on the moving map. | Once uploaded, the airspaces should appear on the moving map. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 16:12, 3 October 2016
Air Navigation is compatible with two well known Airspace file formats:
- OpenAir
- Tim Newport-Peace
Both formats are easy to understand text files format describing Airspace attributes and geographic boundaries as well as lower and upper limits.
You can import airspaces files from the embedded Webserver, in the «Airspace» tab.
You can find a description of the Tim New Port Peace format here: http://soaringweb.org/TP/sua.html
Important: OpenAir files must have a “.txt” file extension, Tim Newport-Peace must have an “.air” file extension.
You can find a description of the Tim New Port Peace format here: http://soaringweb.org/TP/sua.html
You can find a description of the OpenAir format here: http://www.winpilot.com/UsersGuide/UserAirspace.asp
Once uploaded, the airspaces should appear on the moving map.