Nav database user patterns

[SiC42]

Hi, been using FIF for quite a while (3 years) and am still having problems with keeping user patterns in the Nav database. I have created a series of circuit patterns in the South of the UK in GE and imported them into FIF no problem, they work very well, however, every cycle update they get wiped and have to be imported again. They are marked 'U' in the type field with either a red dot (or a green one if I select 'VFR airfield' instead of 'unknown'), either way they are still written over and then have to be re-imported. They are easy enough to re-import from the airspaces/patterns page, either from GPS_ILS_VOR as .gia files or from my separate import folder on the device as a .kml, but as I make more it is turning into a lengthy process every update (on two devices). Also the 'import/folder' route is not always remembered inbetween entries, so every entry may require re-navigating to the root folder. It would be helpful to be able to select multiple files for import but this isn't easy in android. Any ideas?

Other than this it is working well for me and I like it a lot!

[Tonio]

Hi
Did you try to send this user patterns to Petr Kouril, asking him to integrate/incorporate them in th the nav item database
This what I did with some ultralight RWY, and he accepted to integrate them

[kitercuda]

When importing patterns set country which you do not use when you update nav database, for example Afganistan.

If you send me your patterns, I will add them to FIF database.

[SiC42]

Thanks Petr, Tonio, sorry for the delay in replying. That is a very useful suggestion, I will give it a try with the next airac update and see what happens.

Re posting circuit patterns to be added to the FIF database is there some way of warning others to use at their own risk? I'm happy that they are flyable in a C42 at 70-80 knots (they are made by information being taken off the airfield's own website guidance into GE with fairly good accuracy or possibly modelled to be similar to Old Sarum as a reasonable GA airfield) but I would not guarantee that I would keep checking to see if they are up to date if for some reason they were changed locally? Importing the .gia from within the FIF GPS_ILS_VOR folder reinstates the QFE circuit height and type (pattern) but just posting the .kml and importing has then to have the values added in the edit window. Are the .gia files made by FIF when importing/editing?