Internal airspace file format specification?

[Tibor]

Hi!
This is a great app, I just bought it! I plan to use it for VFR navigation, low and slow .
However I am not satisfied with the airspace databases (Hungarian) that I could find on the web, most of them seem to bee outdated, and inaccurate from some aspects (eg. none of them include the bird migration restricted areas).
I had a project that translates the latest official Hungarian AIP https://ais.hungarocontrol.hu/aip/ into a 3 dimensional .kmz (Google Earth) file that I used to use for visualized flight planning. https://drive.google.com/open?id=1Lq8ZSENj4Bk_rsNnfNrI_Le3STMJhHlM
I discovered that FiF's own file format for airspaces is a variation of the keyhole markup language, an I think it wouldn't be a big issue to modify my project to generate the same airspace structure in FiF's format as well. This way we could have an accurate and detailed airspace for Hungary.
Do you have any specification on FiF's internal file format? Element names, constants, etc?
Best regards:
Tibor

[Tonio]

Hi Tibor

Airspaces created within OpenAir and Google Earth could be imported into FIF
You will find some explanation in FIF usergide page 169 and following
http://www.funair.cz/downloads/manuals/flyisfun.pdf

Have fun

[Tibor]

Hi Tonio,

Thank you for your reply, but it did not help me too much.
I know the manual, and how to create airspaces "by hand" on my tablet.
My real problem is, that the LH database that comes with FiF lacks roughly 50-60 airspaces. All bird migration areas, all drop zones, acrobatic and glider areas. Too much to manage them one-by-one, and too dangerous not seeing the latters on the map.
I have a database, and would like to import them as a single step, but was not sucessfull.
Importing as a .kml will import the coordinates, but the upper and lower limits and the type and class of the airspace. All these must be set by hand on the tablet for that many airspace.

Is there any format that could contain these information and could be imported as a single step?

An interesting (bug?) : if I create an airspace on the device (eg. a Park type with 1500 FT AGL top) and export it as .gia, then when I import it back, it shows up as bird type with 2000 FT AGL top

BR
Tibor

[kitercuda]

Hi Tibor,
please send me your files by email or post them here (zip them first), I will have a look. KML file is OK for me...

[Tibor]

Dear kitercuda,

I attach an example about this (now I am sure) bug. If you export a park type airspace and later import it back, you will end up with a bird type airspace with wrong vertical limits.
If this is solved, I could easily import the missing ones.

I found some inaccuracies in the FiF's Hungarian airspaces (deviation from the official AIP: frequencies, cancelled ones, missing many, duplications on different names). Would it be somehow possible contributing to keep it updated?

Best regards:
Tibor

[kitercuda]

Hi, sorry, there is really bug. I will publish upgrade in a few days.

please send me email, we can talk about the Hungarian data.

[Tibor]

Great! Works fine! FiF provides great assistance in navigation.