How to keep your own user patterns etc. with NAVdata update?

[beaver]

All ships all ships all ships!
Is there a way to keep your own created user paterns/airspaces etc. when updating NAVdatabase?
Every time I update NAVdatabase to keep them at the moment I go through the process
->Tools and info
->Airspaces and patterns
->[country etc.]
followed by manually deleting e.g. old/wrong pattern from NAVdatabase download followed by importing and editing user created one to have them displayed as desired again.
Can anybody help me to one of these days get organ(iz)ized?
Maybe there is a faster/an easier workaround?
Thanks for reading!
beaver

[kitercuda]

Hi,
unfortunatelly it is not possible to do it in easiest way.
If your patters are official, I can publish them...

[beaver]

Hi and thanks for your answer!
Mine were created from the offical VOCs of the AIP Part II AD referencing topographical features from the VOCs in GoogleEarth. I wouldn't know where to get official coordinates for the patterns unfortuately. There was a website somewhere that had a lot of patterns in open air format but this wasn't official. I'd really like to contribute with official data for the patterns but for now just don't know how. If someone knows let me know! While here's an official source for airspace data it's not the problem here and not quite up to date obviously, but still: http://www.daec.de/fileadmin/user_uploa ... Air_V2.txt

[kitercuda]

What about this - if the airspace (or pattern) is marked as user defined - it will not be deleted when database update.

If you would like to contribute, we can improve database

[beaver]

I think it was marked (and displayed with >U<) as user defined etc. but still a goner with the update. Maybe if I'd change >Type< and >Class< to "not specified"? I'll try this with next database update. I don't consider this a big issue but since there's the option to create your own patterns, spaces, whatever I thought there might be an easy way to keep them with an update (e.g. putting them in a subfolder or having it specified in a way that it will be kept with an update). For now I only played with patterns for two small airfields. Tried to attach them here but it says "The extension kml is not allowed".

Still maybe this function might have bigger potential. In the area there are some official/half-official/inoffcial recommendations concerning airspace usage and while maybe not interesting for the occasional trespasser for the local frequent flyer it's probably good to have these on the screen for situational awareness (and cooperation with the big ones). Just to give you an idea here's a bigger example: Occupational forces at ETAR (pretty busy! see https://en.wikipedia.org/wiki/Ramstein_Air_Base ) via DFS and local pilot organisations have communicated the request to mind approaches and patterns and pilots are politely asked to at least learn enough English to provide position information when crossing. This is to prevent further restrictions of airspace in the area they say due to too many near misses in the past. So it would be nice to at least be able to have this user data on the screen and keep it with updates for better situational awareness before you're shot down by a F-35 before you even noticed there was one (see http://www.lsvrp.de/img/memocard2014.pdf). I could give another example concerning EDFH but guess there could be many individual reasons to install your private airspaces and/or neuralgic paths (without having to reimport them after update).

PS: Two or three minor (bug-?)reports:
1.) I use English language with FIS while the tablet runs German OS. Still I noticed the menu bar every now and then changes to German and also back to English again which in my case is not a problem (as long as it doesn't change to Czech ) but still.
2.) I use screen orientation >Reverse Landscape< (in order to get organized in the cockpit while keeping GPS antenna up). Maybe it has to do with your acrobatic flying (very nice!) but going rather straight along the sky it's rather strange that every time you go deeper in the menus or folders the screen flips from Landscape to reverse (not to mention plus the vibrations I just can't get rid off). Sometimes after changing some preference you might also end up in Landscape and have to close and restart software again to get Reverse Landscape not displayed upside down . Sometimes I even have to restart OS! I tried switching screen settings in the OS for screen rotation >on< and >off> but to noo avail it seems.
3.) (In simulator mode!) when going along airspace C2500MSL north of Berlin it disappeared when zooming in (see screenshots attached - wrong order though-, same with range 1NM but only 3 attachments allowed). This was NOT due to screen customization for zooms!

[kitercuda]

Hi, thanks a lot for you feedback and sorry for my late respnses, I am at the Indian ocean now and my connecting to the internet is poor and only sometimes

At this moment U - user defined are deleted when database upgrade. In thew next upgrade it will be solved
Can you send me by mail your patterns, which are not allowed?

The rest I will answer later today...

[beaver]

Enjoy the Indian Ocean! (I'm not in a hurry at all.) Will send e-mail with files.

[kitercuda]

I am connected

Airspace info:
How to easy keep up to date all information?

Bugs:
1. Did you try to to set language in Preferences or you use default language settings?

2. I do not use reverse landscape. I was surprised by screen aerobatic too . I will have look at it.

3. This is e problem of data source. WPTs of airspace must be polygon. If it is 8 (means the lines of one aircpase are crossed) it makes thsi problems. I try to analyze airspace before its displaying.

[beaver]

Keeping up to date all information sure'd be a tough task! But since users have to plan according to official national regulations anyway and therefore probably update and tweak things here and there themselves anyway it's no big worry. To make this user-resource open source is an idea I like. I will use the more appropriate Forum's topic "Navigation Database" in the future.

As for the bugs:
1.) English language was set in Preferences.
2.) Surprise that you're surprised (thought you might not have noticed since you're just used to flipping horizon anyway).
3.) For now I don't understand why 8 means crossed but guess it probably might be as with creating your own airspaces, patterns etc.

Anyway thanks a lot for taking the time (I feel bad because you should enjoy the Indian Ocean while I enjoy getting away from the tasks in the office scribbling here...)!