Airspace issue with CoTaCo and CoMoMap

[Rotareneg]

Todays Tchin-Tchin task had no active airspaces, but CoTaCo and CoMoMap both incorrectly showed the "OBAN ATZ" class D airpspace at the finish as active. Attached is the flightplan, and inside a code block as you can't attach text files on the forum, the airspace .txt file output from CoTaCo:

Code: Select all

***********************************************************************
***                                                                 ***
*** CONDOR AIRSPACE AND PENALTY ZONES                               ***
***                                                                 ***
*** NOT TO BE USED FOR REAL-LIFE FLYING                             ***
*** PLEASE DO NOT REMOVE THIS NOTICE                                ***
***                                                                 ***
***********************************************************************
***                                                                 ***
*** This file has been created for Condor flight plan:              ***
*** C:\Users\Jon\Documents\Condor3\FlightPlans\viv-UK3-Earnhead-160K***td-Airstart.fpl
***                                                                 ***
***********************************************************************
*
AC D
AN OBAN ATZ
AF 118.055
AL SFC
AH 2024 ft
V X=56:27:49 N 005:24:00 W
DC 2

[Bre901]

Sorry for the late reply, I have been away for a few days

I have been able to reproduce that issue, except that I get a few more airspaces in the file created by CoTaCo, although they are outside the task area, see below. Did you remove them from the file before posting it ?

The same issue also happens with VerifLocal, which is not surprising as all 3 apps use the same airspace file reading routine.

After looking into more details, I think that the issue might happen between Condor and the airspace file:
- if you take a look at the FPL file, the last disabled airspace # is 642
- but if you count the number of air spaces in the .air file, there are 766 of them (#=0-765)
- all the zones activated are after the 642th in the file

I thought initially that some zones outside the landscape might have been cropped by Condor, but my airspace cropping tool found none

Apparently Condor ignores some zones which changes the numbering, hence the issue with my tools which assume that no zone in the airspace file is ignored by Condor.

If I enable all airspace and disable only the Oban ATZ, I can see that its number in Condor is 605, but its rank in the file is 726 ( > 642)

Code: Select all

***********************************************************************
***                                                                 ***
*** CONDOR AIRSPACE AND PENALTY ZONES                               ***
***                                                                 ***
*** NOT TO BE USED FOR REAL-LIFE FLYING                             ***
*** PLEASE DO NOT REMOVE THIS NOTICE                                ***
***                                                                 ***
***********************************************************************
***                                                                 ***
*** This file has been created for Condor flight plan:              ***
*** D:\Marc\Condor3\FlightPlans\viv-UK3-Earnhead-160Km-std-Airstart.***
***                                                                 ***
***********************************************************************
*
AC D
AN CUMBERNAULD ATZ
AF 120.605
AL SFC
AH 2350 ft
V X=55:58:29 N 003:58:32 W
DC 2
*
AC D
AN EDINBURGH CTR
AF 121.205
AL SFC
AH 6000 ft
V X=55:57:00 N 003:22:21 W
DC 10
*
AC D
AN GLASGOW CTR
AF 119.100
AL SFC
AH 6000 ft
DP 56:04:00 N 004:20:00 W
DP 56:01:30 N 004:04:35 W
DP 55:44:34 N 004:09:24 W
DP 55:41:32 N 004:24:05 W
DP 55:37:00 N 004:28:47 W
DP 55:44:28 N 004:50:35 W
DP 55:46:00 N 004:49:51 W
DP 55:55:00 N 004:52:00 W
DP 56:04:00 N 004:20:00 W
*
AC D
AN OBAN ATZ
AF 118.055
AL SFC
AH 2024 ft
V X=56:27:49 N 005:24:00 W
DC 2

[Bre901]

I did the same test-with AA3: if all airspace is disabled, the last # in the disabled airspace list in the .fpl file is 1317, and there are 1318 airspaces in the .air file (numbered 0-1317)

Hence no issue with this landscape

[dgtfer]

How is it possible? If I activate only OBAN ATZ for Condor everything is OK, and no other zone is activated. But in the fpl the disabled zones list end at 641... How condor knows which zone is activated?

[Bre901]

Condor works fine.

The issue is that for UK3, it just ignores some 130 airspaces, meaning that its internal numbering [0-642] does not correspond to the ranks in the .air file [0-766], making the airspace information in the .fpl file unusable for external applications