alus-it / airspaceconverter Goto Github PK

Una cosa curiosa: passo gli spazi aerei ad un amico che ha ANP, il quale è un po' pistino sui contenuti degli stessi: se non è tutto OK genera un sacco di errori.

Nel caso corrente non riusciva a caricarli e si bloccava a metà. Ha poi scoperto che il problema era dato dal fato che in alcuni casi le righe erano separate solo da LF inceve che CRLF (con Notepad++ non riesco a vedere questa stranezza, però con il Notepad nativo sono riuscito a vedere quali erno cotruiti in questo modo strano.

Nono ho idea del perchè questo sia successo (uso solamente Notepad++), ma prescindere da questo, in tema di controlli, non sarebbe male se il tuo convertitore evidenziasse anche se il carattere di separazione tra le righe fosse fatto solo da LF anzichè dal più normale (windows) CRLF.

Se guardi il file che ti allego, troveri nella zona degli spazi di Erice (ma anche in acluni altri casi) quest particolarità (della quale continuo a non capire l'origine).

Both MFC and Qt.

Make deb packages for Debian Jessie and Wheezy. On 32 and 64 bits.

On request from Massimo Belloni:
Draw them at FL600 in Google Earth. (Maximum height for civil airspace)
Not more high otherwise is messing up...
Set them back with AH UNLIMITED when writing in OpenAir.
Write UNLIMITED in the Google Earth labels so we know that are unlimited...

QT will allow to use the program with graphical user interface on Linux, Windows and Mac.

May be this is not so unuseful.

Problem reported by: Valerio Messina
Unable to link on Ubuntu 16.04 to the libairspaceconverter.so dinamic library.

On Windows XP the same open folder dialog is not available, so all buttons (airspaces, waypoints, terrain maps) opening a folder should be disabled. Otherwise they will open an unuseful open file dialog.

Adapt the debianize.sh script to produce the DEB packages also for Ubuntu 16.04 considering the proper versions of the dependencies.

Apparently it seems that in the OpenAIP files there are duplicate airspaces: same type/class, same floor and ceiling and exactly some points; but different names. When loading OpenAIP would be nice to avoid the duplicates.

DEB packages should be built automatically for Debian 7 (wheezy) on 32 bit, Debian 8 (jessie) on 64 bit and Debian 9 (stretch) on 64 bit.
The script should take care of setting the right dependencies versions.

The abbreviated identifier "IDENT" from the label may be handy to identify faster the airspace. It sould be present in the airspace name.

Qt version 4.8 is used on Debian Wheezy, it must just compile without any need to change manually includes and other options.

can be usefull an option to save the last used settings/user preferences in the GUI. For example the latitude/longitude settings, and output file format settings

A new request from: Ico van der Bijl.

I've just updated your AirspaceConverter to the latest version (v0.23) and was wondering if you have ever thought about adding xml files to the converter.

First I have to explain that I'm totally unfamiliar with programming and don't know if my request is even possible.

As you may know to execute a safe flight you have to do flightpreparation and check the charts and NOTAMS. This takes a lot of time and I'm looking for solutions to make things easier.

I get my NOTAMS from AVINOR IPPC which is connected to the European AIS Database (EAD) from Eurocontrol. I also have an account registered to get the information directly from the EAD. They present the information in 4 different layouts HTML, XML, TXT and PDF.

I thought what would be nicer if one could visualize NOTAM information like you did with the airspacestructure? Therefore my request if this is possible and is XML the layout you need?

I attached a xml file I saved this morning from the EAD.
AreaPIB.zip

EAD login (register first): www.ead.eurocontrol.int

Perhaps this is useful:

• I think you can use the NOTAM numbers as the name of the area. In this way it can be easily checked with printed NOTAM lists.
• Many areas are defined as cylinders (geographical position with a radius and a lower and upper limit).
• The more challenging areas are those that consist of multiple positions sometimes in combination with an arc (clockwise or counterclockwise). I saw that these areas are defined separately as free text.
• If you want to create an account for the EAD at EuroControl, make sure that you use Firefox as a browser together with an outdated JAVA plugin (Java SE Runtime Environment 8u25). See: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html

When importing CUP waypoints, specifically airfields, the KML file is not generated correctly. The tags are wrong and not closed correctly with random text in it. This makes Google Earth give error and the file is not displayed.

Sometimes the airspace class is specified also in the name like: "Name Class: B" when writing to OpenAir already an airspace of that class would be nice to avoid to write the class also there. While would be nice to keep/add that information in KMZ for example for a TMA to specify somewhere what class is.

GPL license and conditions to use this software can be shown to the user during the windows installation. He will be able to continue only accepting the conditions.

I noticed that you have tried to create runways when information about waypoint style, runway length and direction was available. The problem with this approach is that the waypoint geographical position isn't always the runway position but the aerodrome reference point. This resulted in totally incorrect runway positions.
Maybe it is better to keep things simple and stick to the shapes (e.g. pin) that come with GE.

just to remember to check

This is happening with special characters.

Credo ci sia un piccolo baco: il tipo di bandierina che utilizza su GE è sempre il solito spillo giallo, anche se nei WP sono iseriti valori che dovrebbero farlo diventare diverso.

It is necessary to #include in some source file to compile in the latest Debian 9

A completely unuseful work.

... while reading OpenAir files

Lib, MFC app and Qt app as well...

A request from BravoLima of www.postfrontal.com/forum:

What also would be useful, is the ability of showing waypoints in Google Earth. Waypoints are saved as cup-file but you can edit the file with MS Notepad. (See: http://www.keepitsoaring.com/LKSC/Downloads/cup_format.pdf)

On request from Massimo Belloni:
When loading files from a folder would be nice to display the number of files loaded.

Bug reported by: Massimo Belloni

Con la nuova rivoluzione degli spazi aerei (10 novembre) l'Italia sarà tutta spazio D sopra (grossomodo) FL85.

Sto preparando gli spazi aerei, ma ho scoperto uno strano comportamento relativo alla CTA Roma Zona 2 "Mediterraneo": se guardi il file che ti allcudo, vedrai che su Sicilia/Calabrie e una fettina davanti alla toscana quello spazio aereo ("D") non c'è (anzi, cambia i bordi in funzioe del livello di zoom). Ho provato anche a generare la carta senza i file .DEM scaricati da LK8000 (che, peraltro, pare non coprano interamente l'Italia), ma il problema permane (sembra che lo spazio si "assottigli" fino a sparire).

Potrebbe essere un bug?

ITA_ASP_10-NOV-2016_V03.txt

On request of a couple of users, the program should be able to produce better IMG maps for Garmin devices using cGPSmapper.

On Windows and on Debian Wheezy is just working fine!

Bug reported by: Ico van der Bijl

Problem with a converted openair file (see attachment, TMA1 and TMA1X files and pictures). In TMA1X there are 7 additional positions but these are causing double lines (upper and lower limit) in the displayed 3D figures.

TMA1.txt
TMA1X.txt

The ZIP here are in relity KMZ so rename to KMZ after download.
TMA1.zip
TMA1X.zip

It seems not working when doing a complete new installation.

All functionalities should be in a shared library.
The user interface should be then separated, using the library and compiled for different platforms.

Another completely unuseful work.

There are a couple of bugs in the Qt interface.
By default it is suggesting a file.kmz as output file name also if another format has been selected in the combo box. It is crashing if I try to choose the output file name before than reading airspaces.

I have used my own airspace files in the converter and discovered the following problem. For unclear reasons, two areas that are adjacent to each other, are displayed with a crack between them, see picture. The same file is used in LK8000 without any error.

OpenAir Airspace definition:

*______________________
*>>> EHR4D VLIEHORS <<<
AC R
AN EHR4D [a]
AH 1500FT MSL
AL SFC
DP 53:09:17 N 004:40:28 E
V X=53:15:00 N 004:57:00 E
DB 53:11:06 N 004:38:08 E , 53:15:00 N 004:37:01 E
V D=-
DB 53:15:00 N 004:43:41 E , 53:10:13 N 004:46:21 E
*to point of origin
*______________________
*>>> EHR4F VLIEHORS <<<
AC R
AN EHR4F [a]
AH 5000FT MSL
AL SFC
V X=53:15:00 N 004:57:00 E
DB 53:15:00 N 004:37:01 E , 53:21:59 N 004:40:45 E
V D=-
DB 53:19:40 N 004:46:10 E , 53:15:00 N 004:43:41 E
*to point of origin

In order to make a decent Linux command line app a man page should be present!
And of course part of the DEB package.

While reading KMZ the CTAs and TMAs (both not supported in OpenAir) sometimes they have written in the label what kind of airspace class they are. So this information should be stored and used when outputting to OpenAir (as generic airspace of a certain class).

This should improve the Windows user experience and hopefully solve the 32 bit - 64 bit problems. The installer should install the 32bit version under C:\ProgramFiles(x86)\AirspaceConverter with icons uninstaller and so on...