Bad CIFP data

Navigation Data General non MSFS data
1

Hi,

While reviewing the worldwide CIFP database for threshold coordinates (X-Plane 12 navdata 2407), I came across bad data for the following airports :

30F :
The coordinates are given for runway 18R/36L but actually point at runway 18L/36R, the asphalt one. Moreover, coordinates for the actual threshold 18L are slightly inaccurate, because of small drift to the East.

SBGP :
The CIFP coordinates of runway 02R/20L are actually the ones for runway 02L/20R.

LFJU :
The coordinates 06/24 do not match the thresholds on the map, resulting in quite a significant heading difference.

LKSN :
All 4 runway coordinates drifted 10 to 17 meters South.

I do not know what you can do about it, but it would be great if you could find a way to fix it.
Best regards,

2

Hi,
What do you mean with bad data - can you explain wgat issue you exactly have. What issue/error message do you see in XP12?

Cheers
Richard

3

I do not see any error in X-Plane.
But when I display the CIFP coordinates on a map like Google Earth or WED, the result does not match the satellite imagery.
In some of the cases listed above, the official data seems to be incorrect aswell.

4

Understood, these coordinates have another functionallity in XP and are correct so far. When you need the runway thresholds, you should use the APT.DAT file, which will provided/supported by XP.

We don’t offer runways in our data for XP. In other words, you shouldn’t use these coordinates for checking it on google maps.

Cheers
Richard

PS: sat images are not really a good reference due the missing accurancy. You should compare the data directly with the AIPs. Not sure what you want todo with the comparision.

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.