Repository navigation
Airport Config
NeoSTAND uses per-airport configuration files (placed in Documents/NeoRadar/Plugins/NeoSTAND) to control how stands are assigned to arriving aircraft. Each airport has its own config file, named according to its ICAO code (e.g., LFPG.json).
Below is a guide to the structure and available options in these JSON files.
A minimal config file looks like:
{
"version": "1.0.0",
"ICAO": "LFPG",
"Coordinates": "43.633086:1.369442:5000",
"STAND": {
"A01": {
"Coordinates": "43.633086:1.369442:25"
},
"B05": {
"Coordinates": "43.632854:1.368977:25"
}
}
}-
version:
Type: string
Description: Indicates the config version. Must match theversion.jsonfile from Github config (if using remote config) -
Coordinates:
Type: string
Description: Center coordinates of airport + radius of airport in meters -
STAND:
Type: object
Description: A dictionary where each key is a stand name (e.g., "A01", "B05") and the value is a set of options for that stand.
Coordinates: Set of coordinates in Decimal Degrees and radius of the Stand
Each stand in the STAND section can define the following options:
- Type: string
- Description: Restricts the Stand to a specific Size.
-
Possible Values:
-
"A": Wingspan < 15m -
"B": Wingspan < 24m -
"C": Wingspan < 36m -
"D": Wingspan < 52m -
"E": Wingspan < 65m -
"F": Wingspan < 80m
-
-
Behavior: If set, only aircraft with a matching size Code will be assigned this stand. If not set or
"ABCDEF", the stand is not restricted by Code. Can be multiple (ex: "ABCDE" to only refuse > 80m or "EF" to only accept < 52m).
- Type: string
- Description: Restricts the Stand to specific types of aircraft/operation.
-
Possible Values:
-
"A": Airliner -
"P": General Aviation -
"H": Helicopter -
"M": Military -
"C": Cargo
-
- Behavior: Only aircraft matching the specified type will be considered for this stand. If omitted, the stand is not restricted by type. Can be multiple (ex: "AC" to accept Airliners and Cargo.
- Type: boolean
- Description: Restricts the Stand to Schengen flights or Exclude Schengen flights
-
Behavior: If set to
true, only flights departing from Schengen airspace will be able to get this Stand, if set tofalseSchengen flight won't get this stand (if you want to assign regardless of origin, do not add a Schengen key).
- Type: Array of string
- Description: Restricts the Stand to flights originating from specific countries.
- Behavior: Set the first two letters from ICAO country code (ex: "LF" for flight originating from France).
- Type: array of strings
- Description: Restricts the stand to specific airlines.
- Possible Values: Airline ICAO codes.
-
Behavior: If set to
["AFR", "KLM"], only Air France & KLM flights will be able to get this Stand.
- Type: array of strings
- Description: Block other Stands if this one is assigned.
- Possible Values: Blocked Stands name.
-
Behavior: If set to
["V10", "V08"], when this stand is assigned, it will block assignation of "V10" & "V08".
- Type: integer
- Description: Used to determined if stand should be assigned before other valid stands.
- Possible Values: Any integer.
- Behavior: Lowest priority from remaining stands will be assigned.
- Type: boolean
- Description: Used to consider "stand" as an apron containing multiple unnamed stands.
-
Possible Values:
true/false. -
Behavior: If
true, the "stand" is not considered occupied when assigned to a pilot, ence it can be assigned to multiple. Used to depict Terminal/Apron assignation instead of specific stand number.
{
"version": "v1.0.0",
"ICAO": "LFBO",
"Coordinates": "43.633086:1.369442:3000",
"Stands": {
"V10": {
"Coordinates": "43.633086:1.369442:25",
"Use": "A",
"Schengen": true,
"Callsigns": [
"RYR",
"RAM",
"BEE",
"KLM"
],
"Code": "ABC",
"Block": ["V11"],
"Priority": -1
},
}
}
-
V10: Stand at coordinates
43.633086N1.369442E with a radius of25meters, for aircrafts with wingspan < 36m, airliner traffic from Schengen airspace from either Ryanair, Royal Air Maroc, Brussels Airline or KLM, and when assigned, this stand blocksV11and this stand will be assigned before all other valid stands of priority > -1.
- Any of these option can be omitted to indicate that there is no restrictions.
- Each Airport Config should have some fallbacks stand that do not have any/or little restriction to avoid not finding stand for a flight, those would need a low priority (meaning high integer) to avoid being assigned before more specific stands.
- Stands can be blocked dynamically if they are already occupied or too close to another occupied stand.
For more advanced/extended options or plugin updates, consult the plugin changelog or source code.