i dont know if you remember, but i want to open that again if not.
Whenever i install a new Aircac Cycle via the FMS Data Manager, my Intersections for EDDP in Topcat are gone.
For the other airports the INtersections are updated.
Why not for EDDP ?
Why are they always deleted?
They are in the FMS Data for sure.
The Topcat File changed by the FMS Data Manager is called
C:\Program Files (x86)\Common Files\TOPCAT\Database.tdb
Would be really nice to hafe the Isecs also for EDDP up to date.
Hi Matthias,
we don’t update intersecrions, not for EDDP nor any other airports. Only airports and runways but no intersecrions and EOSIDs. These data are all from the release if Topcat. Sorry!
thats not really the truth…sorry.
The File, mentioned above, is always updated/changed, when i update the Navdata via the FMS Data Manager and then my manually added Intersections are gone.
As i say, that always happen when i update the Airac via the FMS Data Manager. So the file is definitly changed by the FMS Data Manager.
Ok, maybe you did not update the Isecs, but you change the file !
Here is the Part of the file which is changed always:
That’s exactly what I have written … no intersections, no EOSIDs only airports and runways which implicit that we update the file (but only special parts). Because when we would nothing change why should we offer an AIRAC update then?
no, you do not.
When i look in the db file before the Update, the Intersections are there.
After doing the Update, the Intersections are gone.
So FMS Data Manager is NOT doing that.
I have added 2 files.
The file BEFORE the Update and AFTER the update.
If you use Notepad++ as example to compare the files, you will see the Isecs for EDDP, which i have to add manually directly in the file, are gone after doing the Update !
Matthias,
I believe you don´t understand the system … therefore here a short description, what the FMS Data Manager does:
We offer one file database.tdb this file contains the content - airport, runways which we update and a static part which will not be updated EOSIDs and intersections. This file will be created on every AIRAC via a special parser which we had developed. The created file database.tdb will then be zipped and uploaded to our different backend systems.
The FMS Data Manager downloads the file and install the file into the right folder, means he overwrites the previous cycle file(s). The FMS Data Manager doesn´t install only deltas, he overwrites the file(s) which are on your system.
In your case, it means that all chances what you´re made locally manually on your system, will be overwritten on the next cycle. That´s the functionality of the FMS Data Manager since 16 years …
Again, there is no delta update with removing/appending lines in a file - the FMS Data Manager overwrites every time the whole file(s). So, when you want to update anything with your own values, you must do this after every cycle.
What I have mean with “append” of the static file is what our parser do. The parser creates the airport/runway information, writes this into a file and then it append the static part to this file, that we can offer one whole file.
Hope it´s clear now, what the FMS Data Manager does exactly in the background.
Matthias, your only option is to manually copy the Airport and Runway entries from the new cycle .tbd to your own Database.tdb using an editor such as notepad++
ahh, now i understand…the FMS Datamanager is ony COPYing the file and not "Edit"ing the File.
Ok, then i have to edit it manually after each update.
But maybe i can send you the intersections for Leipzig ( EDDP ) so that you can add it automatically in the parser. That would help me very much and dont have to edit it manually after each update.
Here the Intersections for EDDP, you can also find it in the file before the update from above.
Will inform you, when it´s done but you should expect it with the upcoming cycle 2308 …