ZSQD airport position still on the old one

Hello, on XP12, I noticed that the ZSQD on the MAP is not showing correct when I choose ZSQD Rwy 34 for example.I think it is still displaying the old one.( airac 2303 ).Maybe it is not navigraph related but I just report it here because in the FMS ,it only has one Rwy instead of two.
Best Regards
isaaclevi




Hi,

Welcome

In the default XP12 without scenery addons (with AIRAC 2303), there appear to be two ZSQD airports:

Make sure you select the Qingdao Jiaodong Intl to get the airport with two runways.

Cheers
Ian

Thanks for the response IAN ,yes indeed , in the picture the boeing and the airbus both are on the “line up” position ZSQD Rwy 34 ,and the issues are on the FMS showing the one about 14NM away.
Would you mind just showing me your case at the same position for a flight plan like ZSQD to ZYTX for example.
Cheers,
isaaclevi

Hi,

Sorry for the delay of this answer but such “issue” analyzes needs a little bit more time …

After a view tests, I´m pretty sure, that this is an XP12 issue rather a navdata issue. The problem here is, that XP12 offers two identical airports (in their global scenery apt.dat file) with two different ICAO codes, as Ian mentioned in his screenshots. I have now compared these two airports:

Here one with icao code XZ00 in line 1 but on the field icao_code ZSQD

1     28 0 0 XZ001I Qingdao Jiaodong Intl
1302 city Qingdao
1302 country CHN China
1302 datum_lat 36.364755
1302 datum_lon 120.086827
1302 gui_label 3D
1302 iata_code TAO
1302 icao_code ZSQD
1302 region_code ZS
1302 state Shandong
1302 transition_alt 9800
1302 transition_level 11800
100 60.00 2 2 0.30 1 3 0  16 36.3812370 120.0932050 0 121 3 2 1 0 34 36.3503498 120.1053458 0 116 3 1 0 0
100 45.00 2 2 0.30 1 3 0  17 36.3709654 120.0716952 0 119 3 2 1 0 35 36.3400690 120.0837981 0 119 3 1 0 0

… and here the same with ZSQD in line and on the field icao_code ZSQX

1     28 0 0 ZSQD Qingdao Jiaodong Intl
1302 city Qingdao
1302 country CHN China
1302 datum_lat 36.364755
1302 datum_lon 120.086827
1302 gui_label 3D
1302 iata_code TAO
1302 icao_code ZSQX
1302 region_code ZS
1302 state Shandong
1302 transition_alt 8860
1302 transition_level 10830
100 60.00 2 0 0.00 1 2 0  16 36.3812485 120.0931802 0 121 2 2 1 0 34 36.3503048 120.1053457 0 116 2 1 0 0
100 45.00 2 0 0.00 1 2 0  17 36.3710139 120.0716603 0 119 2 2 1 0 35 36.3400741 120.0838097 0 119 2 1 0 0

According the XP12 specification the X+ident in the first lines means “a fictional airport on not Scenery gateway coordinates ID’s”. That means the first one XZ00I is a fictional one but has the correct icao_code field ZSQD …

The second one has the correct identifier in the first line but the wrong icao_code field. The code in the first line is only an internal one and should not be used by addon aircrafts, therefore I assume that Zibo and all other addons which uses the apt.dat file as reference looks on the icao_code field, which is the correct process/workflow.

But now the great BUUUUT in this case:
When an addon looks now on the icao_code field, it only finds the “wrong/fictional” airport because as you see in the 1st screenshot, it has the correct ZSQD included. The second part will not be touched because here the icao_code is ZSQX … but this should be the correct one.

It´s a little bit tricky , but in this case the “wrong/fictional” airport (first line with XZ00I) should be removed and in the “real” airports (first line with ZSQD) the field icao_code should be replaced from ZSQX to ZSQD. When this is done, it will be working …

So, the final version should look like, and only these airport in the apt.dat file:

1     28 0 0 ZSQD Qingdao Jiaodong Intl
1302 city Qingdao
1302 country CHN China
1302 datum_lat 36.364755
1302 datum_lon 120.086827
1302 gui_label 3D
1302 iata_code TAO
1302 icao_code ZSQD
1302 region_code ZS
1302 state Shandong
1302 transition_alt 8860
1302 transition_level 10830
100 60.00 2 0 0.00 1 2 0  16 36.3812485 120.0931802 0 121 2 2 1 0 34 36.3503048 120.1053457 0 116 2 1 0 0
100 45.00 2 0 0.00 1 2 0  17 36.3710139 120.0716603 0 119 2 2 1 0 35 36.3400741 120.0838097 0 119 2 1 0 0

Here, after the manual change (only one ZSQD - the right one ;-))
image

Last point … we have nothing todo with this file and we may not change this. Also we don´t offer any runways or similar, only the navigation facilities for it - so in nearly all cases this is normally a scenery issue in XP.

Hope something is clearer now … what can you do now? Please report this (you can also make a reference to this posting) to X-Plane, that they make the chances and to release it in any upcoming version.

Hope that helps,
Richard

Hi,

Thank you so much for this explanation, I will suggest it to XP

Best Regards

| NAVData FMS Data Developer
April 17 |

  • | - |

Hi,
sorry for the delay of this answer but such “issue” analyzes needs a little bit more time …

After a view tests, I´m pretty sure, that this is an XP12 issue rather an navdata issue. The problem here is, that XP12 offers two identical airports (in their global scenery apt.dat file) with two different ICAO codes. As Ian mentioned in his screenshots. I have now compared these two airports:

Here one with icao code XZ00 in line 1 but on the field icao_code ZSQD

1     28 0 0 XZ001I Qingdao Jiaodong Intl
1302 city Qingdao
1302 country CHN China
1302 datum_lat 36.364755
1302 datum_lon 120.086827
1302 gui_label 3D
1302 iata_code TAO
1302 icao_code ZSQD
1302 region_code ZS
1302 state Shandong
1302 transition_alt 9800
1302 transition_level 11800
100 60.00 2 2 0.30 1 3 0  16 36.3812370 120.0932050 0 121 3 2 1 0 34 36.3503498 120.1053458 0 116 3 1 0 0
100 45.00 2 2 0.30 1 3 0  17 36.3709654 120.0716952 0 119 3 2 1 0 35 36.3400690 120.0837981 0 119 3 1 0 0

… and here the same with ZSQD in line and on the field icao_code ZSQX

1     28 0 0 ZSQD Qingdao Jiaodong Intl
1302 city Qingdao
1302 country CHN China
1302 datum_lat 36.364755
1302 datum_lon 120.086827
1302 gui_label 3D
1302 iata_code TAO
1302 icao_code ZSQX
1302 region_code ZS
1302 state Shandong
1302 transition_alt 8860
1302 transition_level 10830
100 60.00 2 0 0.00 1 2 0  16 36.3812485 120.0931802 0 121 2 2 1 0 34 36.3503048 120.1053457 0 116 2 1 0 0
100 45.00 2 0 0.00 1 2 0  17 36.3710139 120.0716603 0 119 2 2 1 0 35 36.3400741 120.0838097 0 119 2 1 0 0

According the XP12 specification the X+ident in the first lines means “an fictional airport on not Sceney gateway coordinates ID’s”. That means the first one XZ00I is a fictional one but has the correct icao_code field ZSQD …

The second one has the correct identifier in the first line but the wrong icao_code field. The code in the first line is only an internal one and should not be used by addon aircrafts, therefore I assume that Zibo and all other addons which uses the apt.dat file as reference looks on the icao_code field, which is the correct process/workflow.

But now the great BUUUUT in this case:
When an addon looks now on the icao_code field, it only finds the “wrong/ficional” airport because as you see in the 1st screenshot, it has the correct ZSQD included. The second part will not be touched becaause here the icao_code is ZSQX … but this should be the correct one.

It´s a little bit tricky one, but in this case the “wrong/fictional” airport (first line with XZ00I) should be removed and in the “real” airports (first line with ZSQD) the field icao_code must be replaced from ZSQX to ZSQD. When this is done, it will be working …

So, the final version should look like, and only these airport in the apt.dat file:

1     28 0 0 ZSQD Qingdao Jiaodong Intl
1302 city Qingdao
1302 country CHN China
1302 datum_lat 36.364755
1302 datum_lon 120.086827
1302 gui_label 3D
1302 iata_code TAO
1302 icao_code ZSQD
1302 region_code ZS
1302 state Shandong
1302 transition_alt 8860
1302 transition_level 10830
100 60.00 2 0 0.00 1 2 0  16 36.3812485 120.0931802 0 121 2 2 1 0 34 36.3503048 120.1053457 0 116 2 1 0 0
100 45.00 2 0 0.00 1 2 0  17 36.3710139 120.0716603 0 119 2 2 1 0 35 36.3400741 120.0838097 0 119 2 1 0 0

Here, after the manual change (only one ZSQD - the right one ;-))
image

Last point … we have nothing todo with this file and we may not change this. Also we don´t offer any runways or similar else, only the navigation facilities for it - so in nearly all cases this is normally a scenery issue in XP.

Hope something is clearer now … what can you do now? Please report this (you can also make a reference to this posting) to X-Plane, that they make the chances and to release it in any upcoming version.

Hope that helps,
Richard

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