Stand Assignment Based on Cargo Callsigns

Suprojit Paul (1351391)

We are developing GRPlugin for Dubai and have run into a peculiar use case for the stand assignments.

Emirates uses the callsign "9xxx" for it's cargo flights (eg. UAE9827). Is there a way to have the plugin to understand that specific callsign ranges are only cargo flights. Right now the plugin is assuming these aircraft to be passenger flights and thus assigning these passenger stands.

Basically we want the cargo aircraft to be assigned the Apron E stands of appropriate size, however I'm unable to get this to work in our current setup using the ATYP and CALLSIGN setting.

For example this is a passenger stand definition:
STAND:OMDB:F3:N025.15.20.437:E055.21.02.841:35 USE:A CODE:D:F CALLSIGN:UAE,QFA,ACA,UAL

And this is our current cargo stand definition:
STAND:OMDB:E23:N025.15.37.037:E055.21.55.953:35 USE:C:A CODE:C:E CALLSIGN:ERT,AFG,IRC,IAW,PGT,AXB,DAO,FDB,KIS,QSM,RWD,TBN,TUA,UBD,IRG,KMF,TRA,TVS,TYA,JBW,SMR,TBM,OMS,CPN,WZZ,EXV,MMA,TUA,HIM,RNA,AZO,UTA,BDR,SDM,TQQ NOTADEP:UAAA,UACC,LFSB,ORMM,LYBE,UCFM,LROP,LHBP,LICC,LGKR,HTDA,VTSG,EPKK,WMKL,LJLJ,VRMM,LIME,UMMS,HKMO,LGMK,LIRN,LIEO,VTBU,WMKP,LIRP,LKPR,EVRA,LOWS,LGSR,LBSF,EETN,UTTT,OIII,LLBG,EYVI,EPWA,LDZA,HTZA COPY CALLSIGN:UAE9 NOTADEP:OJAI,HECA,OIIE,ORBI,ORMM,OLBA ATYP:B77L,B744

Any help would be appreciated!

Juha Holopainen (839337)

There is no way to define callsign ranges as cargo flights.

You can try to adjust the cargo stand definition as follows:

Change "USE:C:A" to "USE:AC"
- Invalid syntax, the "A" is not read at all in your definition
Add a positive priority line to the COPY definition (for example PRIORITY:+1")
- This forces the stand to be assigned over lesser priority stands such as F3 which would also meet the assignment criteria

Note that the stand E23 would also be then assigned for "UAE9" or "UAE91" etc. even if they weren't cargo flights. You'll have to define the valid callsigns as accurately as possible to reduce the possibility of a passenger flight being assigned there. Depending on the valid "cargo ranges", this may be a lot of work.

I suggest to define the cargo callsigns using a GROUP line at the beginning of the file, that way you don't have to copy/paste the same string to a lot of stands and any changes to the callsign list will only need to be done to that one line.

Suprojit Paul (1351391)

Thanks for the reply, this seemed to fix our problem.