I'm starting to work on a project to update the VOR database for Alaska. This includes updating the magnetic variation data, re-locating ones that have moved and etc. I just wanted to see what kind of audience might be interested in using this or helping out with it. (Or not at all:() I tried writing a small perl program that would do this automatically, but I soon realized my coding skills weren't up to the challenge.I'm now doing this by hand.

I also built an updated version of PAFA with the runway number changes, and updated RNAV approaches for the default GPS.(If anyone's interested)

I'm starting to work on a project to update the VOR database for Alaska. This includes updating the magnetic variation data, re-locating ones that have moved and etc. I just wanted to see what kind of audience might be interested in using this or helping out with it. (Or not at all:()

If I'm getting your drift right, wilevi93, some of this may have been done already. But not, I think, Alaska. Check this website. http://hsors.pagesperso-orange.fr/index.htmlThe FS Navaids update corrects erroneous geographical positioning of some default navaids in FS9 and FSX. There is also a program to correct magvars. Don't mistake it for Navigraph which updates AIRACs but does not correct the actual geographical positions. Although I cannot be certain it seems that the FS Navaids updates on that page will not overwrite navaids written into PMDG and other aircraft.

If I'm getting your drift right, wilevi93, some of this may have been done already. But not, I think, Alaska. Check this website. http://hsors.pagespe...e.fr/index.htmlThe FS Navaids update corrects erroneous geographical positioning of some default navaids in FS9 and FSX. There is also a program to correct magvars. Don't mistake it for Navigraph which updates AIRACs but does not correct the actual geographical positions. Although I cannot be certain it seems that the FS Navaids updates on that page will not overwrite navaids written into PMDG and other aircraft.

I think I might clarify what I intend to do with the project. The default simulator navaids are somewhat out of date. The magnetic variation data is out of sync with current charts, and some have moved. This makes VOR navigation in FS using current charts impossible. (Which is why I intend to develop an update.)The website you mentioned earlier has some fantastic resources, but it lacks any update for North America.The program "Easy Navs" can re-calculate true magnetic variation in the area that the navaid is in. But in reality, they (the VOR stations) are not always set to actual magnetic variation,which can even then cause some trouble in using current en-route charts.This update would only affect the FS database, and whatever aircraft you have installed that use that database.As far as addon payware aircraft, it really depends on if they use their own database for the VOR receiver, or the default FS database. Note. the VOR reciever, not the FMS.

I think I might clarify what I intend to do with the project. The default simulator navaids are somewhat out of date. The magnetic variation data is out of sync with current charts, and some have moved. This makes VOR navigation in FS using current charts impossible. (Which is why I intend to develop an update.)The website you mentioned earlier has some fantastic resources, but it lacks any update for North America.The program "Easy Navs" can re-calculate true magnetic variation in the area that the navaid is in. But in reality, they (the VOR stations) are not always set to actual magnetic variation,which can even then cause some trouble in using current en-route charts.This update would only affect the FS database, and whatever aircraft you have installed that use that database.As far as addon payware aircraft, it really depends on if they use their own database for the VOR receiver, or the default FS database. Note. the VOR reciever, not the FMS.

Are you proposing to modify the actual location data of VORs etc in the sim files?

There's only about 45 VORs in PA area (though in FSX there are also a number of DME-only VORs that are collocated with NDBs). So it would be fairly straightforward to update the default files, though the best would be to also the check out the CY and UH navaids that are also in the default files. Unfortunately I don't know a data source as good as FAA for getting current data on those.The thing is, though, it has been pointed out before that moving or deleting VORs can cause a problem if they are part of the enroute airway structure. Where they are, besides the NVX files they also have waypoints defined in the ATX files that contain the airway route data. I don't know if, say, SDE has been heavily tested for de-compiling the ATX files.scott s..

There's only about 45 VORs in PA area (though in FSX there are also a number of DME-only VORs that are collocated with NDBs). So it would be fairly straightforward to update the default files, though the best would be to also the check out the CY and UH navaids that are also in the default files. Unfortunately I don't know a data source as good as FAA for getting current data on those.The thing is, though, it has been pointed out before that moving or deleting VORs can cause a problem if they are part of the enroute airway structure. Where they are, besides the NVX files they also have waypoints defined in the ATX files that contain the airway route data. I don't know if, say, SDE has been heavily tested for de-compiling the ATX files.scott s..

There might be some problems the automatic flight planner with regards to navaids moving or disappearing, but the sim ATC will probably still work just fine if you manually set the planner. There is a good source of airway information as a free download from the FAA website that contains current airway data, waypoints navaids etc. (Just throwing that out there if somebody can use it). I Intend this to be a drop in for the add on scenery folder, The old default navaid files won't be replaced. I have tested this briefly, and it seems to work so far. I've already finished with the VOR's and am working on the NDB's now.

My experience is that moving VORs by creating a new file in a higher layer does not work reliably. It could be that just changing the MagDec will work.scott s..

My experience is that moving VORs by creating a new file in a higher layer does not work reliably. It could be that just changing the MagDec will work.scott s..

Moving Navaids in FSX generally does not work. At best nothing happens, at worst they duplicate. We eventually turned off the ability to move route navaids in ADE because of the problems. The only sure way would be to change the stock files and that is clearly not to be recommended. We have the same issues with Waypoints.Editing individual properties such as MagVar probably will work.