[CPC900]

So, has anyone had the same issues with the navdat.sql file?! It does NOT show accurately where certain VOR's are, nor correct listings of fixes etc.
For instance, MANY vor's don't list a correct latitude. It just will put a '0' in there. This is very prevalent in many U.S. vor's. So when someone flies a route, on the map, it shows the vor along the equator. Also, many FIX'es get listed as vors and vice versa, on the map.
So what I am getting at, is.....did I do something wrong with the install, or is the navdata file just really bad?!

[CPC900]

Also, is there a way to refresh the data AFTER I change an item in the database, so the map shows correctly?! In other words, refreshing a pilot report map to reflect the newly chnaged/corrected data.
I hope I am not confusing anyone here.

[CPC900]

Sorry, the "Reset cached PIREP routes" took care of that.

[Nabeel]

The data is incomplete, I don't have a complete set of all the points, etc, so I have to cobble them together from various sources

[CPC900]

Oh, ok. So when I fix some data to make it show correctly, I should NOT do the navdata.sql in an update then, because it will overwrite anything I have fixed?!

[Nabeel]

Yeah, you can do it directly in the DB. Don't reimport the navdata.sql. I haven't had the time to regen a new one anyway