-
Notifications
You must be signed in to change notification settings - Fork 10
/
airspaceconverter.1
134 lines (133 loc) · 8.05 KB
/
airspaceconverter.1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
.TH AIRSPACECONVERTER 1
.SH NAME
airspaceconverter \- convert between different airspace formats
.SH SYNOPSIS
.B airspaceconverter
[\fB\-q\fR \fIQNH\fR]
[\fB\-a\fR \fIterrainAltitude\fR]
[\fB\-i\fR \fIinputFile\fR]
[\fB\-w\fR \fIwaypointFile\fR]
[\fB\-m\fR \fIterrainMapFile\fR]
[\fB\-l\fR \fInorthLat,southLat,westLon,eastLon\fR]
[\fB\-p\fR]
[\fB\-s\fR]
[\fB\-t\fR]
[\fB\-o\fR \fIoutputFile\fR]
.PP
Example: airspaceconverter -q 1013 -a 35 -i fileOpenAir.txt -i openAIP_asp.aip -w waypoints.cup -w openAIP_wpt.aip -m terrainMap.dem -l 58,52,0.2,8.4 -o outputFile.kmz
.SH DESCRIPTION
.B airspaceconverter
an open source and multi-platform tool to convert between different airspace and waypoint formats.
.PP
Can read airspace and waypoint files in the following formats:
- OpenAir
- openAIP
- KML/KMZ
- SeeYou
- LittleNavMap
.PP
And the output can be done in the following formats:
- KMZ
- OpenAir
- SeeYou
- LittleNavMap
- Polish
- Garmin IMG
.PP
KMZ files are to be shown in 3D with Google Earth.
AirspaceConverter can take as input also SeeYou .CUP waypoints files and convert them as well in KMZ for Google Earth.
Airspace represented in 3D in Google Earth can help to visualize and better understand the airspace structure.
Not only, having the planned route or track of a flight (as GPX file), displayed as well in Google Earth will make easy to check for airspace crossed or to be avoided.
.PP
The PFM "Polish" format, (file .mp), can be used with cGPSmapper. This utility uses cGPSmapper to make the .img files for Garmin devices.
.PP
The output in OpenAir is useful to make the data from openAIP suitable for many devices which support OpenAir only format; in particular this feature attempts to recalculate arcs and circles (possible definitions in OpenAir) in order to contain the size of output files.
This software can also be useful for maintainers of OpenAir airspace and SeeYou .CUP waypoints files, not only to visualize airspace and waypoints but also to verify the syntax of OpenAir and CUP commands entered.
Duplicate consecutive points will be ignored, the converter will warn about them while reading OpenAir files. This will also detect the special case of an unnecessary point repeating the end of the arc defined on the previous line.
.PP
For the "landable" waypoints in the CUP files an estimation of the runway perimeter is drawn on the earth surface, in order to do that not only the position is used but also the runway orientation and length.
This is particularly useful to verify that the position of the airfield in the CUP file matches exactly the runway in Google Earth.
In software like LK8000 the airfield position is considered as the exact center of the runway, orientation and length are used to assist for landing with an HSI and glide slope indications; thus the correctness of: position, orientation and length becomes quite important.
.PP
AirspaceConverter can be used also to merge together several airspace files (openAIP repeated airspaces will be automatically removed) and filter the result on a specific range of latitudes and longitudes.
.PP
Converting openAIP files to OpenAir has also the advantage to reduce significantly the size of the total airspace database used on a portable device.
For example LK8000 recently supports also the openAIP format but it is not always possible to load bigger openAIP files on older PNA devices, while the same files converted in OpenAir yes.
.PP
There are also cases where the "official" airspace files are available only in KML format, also in this case is possible to convert it to OpenAir.
.PP
AirspaceConverter uses the same terrain raster maps (.DEM) of LK8000 to get the altitude of the terrain and so to convert altitudes from AGL to AMSL.
In case the loaded terrain maps are overlapping, the one with the best resolution will be automatically used.
On the LK8000 website there is a wide terrain raster map collection.
.PP
For more information visit: https://www.alus.it/AirspaceConverter
.SH OPTIONS
.TP
.BR \-q " " \fIQNH\fR
Specify the QNH in hPa used to calculate height of flight levels.
Default is 1013.15 hPa.
.TP
.BR \-a " " \fIterrainAltitude\fR
Specify a default terrain altitude in meters to calculate AGL heights of points not covered by loaded terrain map(s).
Default is 20 m.
.TP
.BR \-i " " \fIinputFile\fR
Multiple, input airspace file(s) can be OpenAir (.txt), openAIP (.aip), Google Earth (.kmz, .kml).
At least one input airspace or waypoint file must be present.
Additional input airspace files must be specified repeating the option \-i in front of each of them.
OpenAir input files are expected to be encoded in ANSI but if encoded in UTF-8 with BOM they will be also read properly.
.TP
.BR \-w " " \fIwaypointFile\fR
Multiple, input waypoint file(s) can be SeeYou (.cup), openAIP (.aip) or LittleNavMap (.csv).
At least one input airspace or waypoint file must be present.
Additional input waypoint files must be specified repeating the option \-w in front of each of them.
The waypoints will be used only if converting to KMZ or to SeeYou.
Hotspots files from openAIP are not supported while nav aids and airports yes.
.TP
.BR \-m " " \fIterrainMapFile\fR
Multiple, terrain map file(s) (.dem) used to lookup terrain heights.
Additional input terrain map files must be specified repeating the option \-m in front of each of them.
The terrain maps will be used when converting to KMZ. And when importing SeeYou waypoints with null altitude the corresponding ground elevation will be used.
.TP
.BR \-l " " \fInorthLatitude,southLatitude,westLongitude,eastLongitude\fR
Output filter limits in latitude and longitude, it must be followed by the 4 limit values.
The limits are comma separated, expressed in degrees, without spaces.
Negative values represent south latitudes or west longitudes.
.TP
.BR \-o " " \fIoutputFile\fR
Output file, can be: .kmz (Google Earth), .txt (OpenAir), .cup (SeeYou), .csv (LittleNavMap), .img (Garmin) or .mp (Polish).
If not specified will be used the name of first input file as KMZ.
Output OpenAir files will be always encoded in ANSI.
WARNING: any already existing output file will be automatically overwritten.
.TP
.BR \-D " " \fIopenAIPinputDir\fR
It will convert all openAIP files in the specified directory. If used the options: -i, -w and -o are no longer valid.
All airspace files (*_asp.aip) will be converted to OpenAir, while all waypoint files (*_wpt.aip and *_nav.aip) will be converted to SeeYou.
.TP
.BR \-p
If writing to OpenAir with this option arcs (DA) and circles (DC) definitions are avoided.
So the perimeter of each airspace will be defined using only points (DP).
By default, without this option, arcs and circles are used even attepmting to recalculate them from points.
.TP
.BR \-s
When writing to OpenAir this option will force coordinates expressed always in degrees minutes and seconds (DD:MM:SS).
Coordinates expressed as DD:MM:SS (with seconds) are more compact and readable but less accurate since one second can be more than 30 meters.
By default, without this option, the coordinates are automatically expressed in the most compact or accurate format every time:
with seconds when the coordinate matches a specific second value (whitin 1/20 of second, 1.64 m) or in decimal minutes in the other cases to remain accurate.
.TP
.BR \-d
When writing to OpenAir this option will force coordinates expressed always in degrees and decimal minutes (DD:MM.MMM).
Coordinates expressed as DD:MM.MMM (with decimal minutes) are usually more accurate but less compact and readable.
Without this option, by default, as described above, the coordinates are automatically expressed in the most convenient format.
.TP
.BR \-t
When reading from KML/KMZ this option will make also the "LineString" tracks to be imported as airspaces.
In this case the tracks found will be closed and treated as unknown GND based airspace with ceiling at 1000 mt AGL.
Without this option, KML "LineString" tracks are ingnored by default.
This option is meant to import long lists of points (like state borders) so then the airspace definitions can be adapted manually in OpenAir files.
.TP
.BR \-v
Print version number.
.TP
.BR \-h
Print a short help guide.