tm24fan8/Airports
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge in master

Browse Source
This commit is contained in:
Calvin Ng
2021-02-09 19:29:35 -08:00
parent 0f561cc9da 67ec14d606
commit 2f6c732fb8
13 changed files with 6829 additions and 683 deletions
Download Patch File Download Diff File Expand all files Collapse all files
final/AS/HKG/VHHHTMA_mobile_readme.md
-193
View File
@@ -1,193 +0,0 @@
# Hong Kong TMA / VHHH Hong Kong
!Important: This is a such simpler version develop for Mobile EATC player.
The folder going to store in your phone is: `\\Android\data\com.dirgtrats.endlessatc\files`
This is an implementation of the Hong Kong FIR and TMA for [Endless ATC](https://steamcommunity.com/app/666610) featuring `VHHH` Hong Kong International Airport. The airspace ceiling is FL250.
This Map ONLY include Hong Kong Terminal Control Area and some Extended Section on Zhuhai TCA.
Based upon AIP Hong Kong 11/20 (2020 11th Version) . The SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All traffic are designed to fly RNAV(GNSS) and ILS APCH. The Northern Boundary data between VHHK FIR and ZGZU FIR are from Basic Law Instrument 11.
The border of the map has included VHHH TMA, VMMC ATZ, ZGGG FIR and ZGZUTM04 TCA and playable range only include VHHH TMA and VMMC ATZ due to the size of FIR are too big to play.
Information of Hong Kong TMA, Transition Altitude (TA) shall be 9000ft and Transition Level (TFL) shall be FL110 (QNH980+), FL120 (QNH979-). Do not assign FL100! Live QNH can be retrieved at [ATIS](https://atis.cad.gov.hk/ATIS/ATISweb/atis.php) by CADHK.
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Press the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
Inside VHHK FIR have 4 Airports, `VHHH`, `VHHX`, `VHSK` and `VMMC`. Further Information will be included below.
## Airports
### `VHHH` Hong Kong International Airport
The main airport of this sector. Which is also only airport included in current verison *v1.0*. HKIA is also the only International Airport had two runway within FIR. All departures and arrivals come from or to Southern, Eastern and Western only due the packed Airspace with nearby Guangzhou FIR and Shenzhen Airport approach route.
There is custom traffic for `VHHH`. Although it is NOT reliable and only designed for the hub airline callsign to show up. *For Government / HKG, are usually operating Helicopters and Small Planes, I had included C172 for its slow purpose. Please be alert with it as it can't follow the speed with airliner.
All visible fixes on the map have a defined hold including many fixes along the STARs but excluded SMT. Standard Missed Approach Route will be included in later versions.
#### Arrival STARS
- `ABBEY`: Eastern route from RCAA (Taipei) FIR, ZGZU (Guanzhou) FIR and ZSHA (Shanghai) FIR
- `BETTY`: Southeast route from RPMR (Manlia) FIR and ZGZA (Sanya) FIR
- `CANTO`: Southwest route from ZGZA (Sanya) FIR, ZGZU (Guangzhou) FIR
- `SIERA`: Northern route from ZGZU (Guangzhou) FIR
#### Departure SID
-`BEKOL`: Northern Route, No TTR, No Handoff below S0690 / F226.
-`LAKES`: Northeast Route, TTR V1/V13, Handoff at F230
-`OCEAN`: Eastern Route, TTR V2/V3/V4/V5, Handoff at F250
-`PECAN`: Southwest Route: TTR V10/V11/V12, Handoff at F160
#### Runway (Suffix for SID/STAR)
- 07R (A)
- 25L (B)
- 07L (C) *Use (A) for STAR
- 25R (D) *Use (B) for STAR
#### Operations
Due to Complication of airspace, all traffic are suggested to follow STAR approach and Do not assign holding at / under 15+ inbound within 30 minutes.
**For Runway 07:**
- TD VOR is a collision point between Departure SID and Arrival STAR:
- Departure maintain 7000ft or below
- Arrival maintain 9000ft or above
**Operations:**
- Northern Runway 07L/25R is the usual Arrival Runway
- Southern Runway 07R/25L is the usual Departure Runway / Cargo Arrival
- Cargo Airlines: CPA w/ B748, HKC, AHK, HKC
### `VMMC` Macau International Airport
Macau International Airport, To be built.
ISO 3166-2: MO
Runway 16/34
MO ATZ has included in *v1.1*
### `VHHX` Hong Kong Airport (aka Kai Tak Airport)
Kai Tak Airport (Depreciated)
Name: KT
Runway 13/31 (Special Operation on 13)
KT ATZ has included in *v1.0*
### `VHSK` Shek Kong Airport
Shek Kong airport, Millitary Airport
Shall Not expect simualtion in EATC
## Known Issues
Everything is still missing ;(
Due game bug, While Both runway operation either only departure or both departure and arrival, the ILS of South Runway will be active. Beware double click the APP button to choose Northern 07L/25R Runway.
## Disclaimer
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that the representation of Hong Kong FIR /TMA, Macao TMA, Guangzhou FIR and Zhuhai TCA matches real life procedures in any way. Any information regarding inaccuracies is appreciated.
## For Developers
For further infomative version, consider PC version developed by ckwng.
## Resources
* [eAIP](https://www.ais.gov.hk/) by CADHK
* [ATIS](atis.cad.gov.hk/) by CADHK
* from [IVAO HK](https://xe.ivao.aero) (Currently Sub-division of XE)
* from [Civil Aviation Department Hong Kong](https://www.cad.gov.hk/)
* from [Airport Authority Hong Kong](https://www.hongkongairport.com/)
* from Hong Kong Government
* Special Thanks: README.md template from RJTT_readme.md by [ckwng](https://github.com/AdamJCavanaugh/EndlessATCAirports/commits?author=ckwng)
## Changelog
* 1.0 ( / ) - 2020/12/31 - Initial version.
* 1.1 ( / ) - 2021/01/01 - HotFix: North Border
* 1.2 ( / ) - 2021/01/03 - Included ZGZUTM04 Airspace / VMMC Border line.
* 1.3 (p1.3) - 2021/01/10 - File Name Conflict Update, Extra Information Inc.
final/AS/HKG/VHHH_mobile.txt
+465 -449
View File
File diff suppressed because it is too large Load Diff
final/AS/HKG/VHHH_mobile_readme.md
+143
View File
@@ -0,0 +1,143 @@
# Hong Kong TMA / VHHH Hong Kong
__Important Notes__
This is a such simpler version develop for Mobile EATC player.The folder going to store in your phone is: `\\Android\data\com.dirgtrats.endlessatc\files`
Height Measurement to be used are Feet and NM, included China Airspace. Otherwise specifically stated.
## Information
This is an implementation of the Hong Kong FIR and TMA for [Endless ATC](https://steamcommunity.com/app/666610) featuring `VHHH` Hong Kong International Airport. The airspace ceiling is FL250.
This Map ONLY include Hong Kong Terminal Control Area and some Extended Section on Zhuhai TCA.
*v1.0* Based upon AIP Hong Kong 11/20 (2020 11th Version) . The SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All traffic are designed to fly RNAV(GNSS) and ILS APCH. The Northern Boundary data between VHHK FIR and ZGZU FIR are from Basic Law Instrument 11.
The border of the map has included VHHH TMA, VMMC ATZ, ZGGG FIR and ZGZUTM04 TCA and playable range only include VHHH TMA and VMMC ATZ due to the size of FIR are too big to play.
Information of Hong Kong TMA, Transition Altitude (TA) shall be 9000ft and Transition Level (TFL) shall be FL110 (QNH980+), FL120 (QNH979-). Do not assign FL100! Live QNH can be retrieved at [ATIS](https://atis.cad.gov.hk/ATIS/ATISweb/atis.php) by CADHK.
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Press the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
Inside VHHK FIR have 4 Airports, `VHHH`, `VHHX`, `VHSK` and `VMMC`. Further Information will be included below.
## Airports
### `VHHH` Hong Kong International Airport
The main airport of this sector. HKIA is also the only International Airport had two runway within FIR. All departures and arrivals come from or to Southern, Eastern and Western only due the packed Airspace with nearby Guangzhou FIR and Shenzhen Airport approach route.
There is custom traffic for `VHHH`. Although it is NOT reliable and only designed for the hub airline callsign to show up. *For Government / HKG, are usually operating Helicopters and Small Planes, I had included C172 for its slow purpose. Please be alert with it as it can't follow the speed with airliner.
All visible fixes on the map have a defined hold including many fixes along the STARs but excluded SMT. Standard Missed Approach Route will be included in later versions.
#### Arrival STARS
- `ABBEY`: Eastern route from RCAA (Taipei) FIR, ZGZU (Guanzhou) FIR and ZSHA (Shanghai) FIR
- `BETTY`: Southeast route from RPMR (Manlia) FIR and ZGZA (Sanya) FIR
- `CANTO`: Southwest route from ZGZA (Sanya) FIR, ZGZU (Guangzhou) FIR
- `SIERA`: Northern route from ZGZU (Guangzhou) FIR
#### Departure SID
- `BEKOL`: Northern Route, No TTR, No Handoff below S0690 / F226.
- `LAKES`: Northeast Route, TTR V1/V13, Handoff at F230 (Auto-Handoff)
- `OCEAN`: Eastern Route, TTR V2/V3/V4/V5, Handoff at F250 (Auto-Handoff)
- `PECAN`: Southwest Route: TTR V10/V11/V12, Handoff at F160
#### Operations
Due to Complication of airspace, all traffic are suggested to follow STAR approach and Do not assign holding at / under 15+ inbound within 30 minutes.
##### For Runway 07:
- TD VOR is a collision point between Departure SID and Arrival STAR:
- Departure maintain 7000ft or below
- Arrival maintain 9000ft or above
##### Avbl for All Runway
- Northern Runway 07L/25R is the usual Arrival Runway
- Southern Runway 07R/25L is the usual Departure Runway / Cargo Arrival
- Cargo Airlines: CPA w/ B748, HKC, AHK, HKC
### `VMMC` Macau International Airport
> Macau International Airport, built and released at *v1.4*.
#### Info
Macau Int'l Airport, short for `MO`
Single Runway, Runway 16 / 34
> ISO 3166-2: MO
>
> For In-game TTS Purpose, Full Name included only have **Macau** instead of **Macau Int'l Airport**
#### Arrival STAR
> Transition Route included Below Sub-Chapter
- Belongs Hong Kong VHHH TMA / FIR
* `CHALI`: Southern Route from RPHI (Manila FIR Eastern), ZGZU (Guangzhou FIR South-Western), ZSJA (Sanya FIR Southern)
* `SMT`: Northeastern Route from RCAA (Taipei FIR Eastern), ZGZU (Guangzhou FIR NorthEastern)
- Belongs China ZGZU FIR / ZSJD TCAD
> Due to Objective Airspace, Limited STAR from China will be provided
* `UJ` : Only Southern Route from China
* Original STAR: `BIRGO`
* `MC511` / `LATOP`: Only Northern Route from China
* Original STAR: `CON`,`POU`,`NLG`
* `MC511`: Operation for Runway 16 Only.
* Suggested Operation: Hold and Descent till 3000' AGL, continue Approach
* `LATOP`: Operation for Runway 34 Only.
* Suggested Operation: Hold and Descend till 6890' (2100m) AGL, continue Approach
#### Departure SID
> Due to Objective Airspace, Limited SID for both Hong Kong and China will be provided
>
> Runway 34: All Departure Transit Hong Kong will use 2U (cross TD) Departure.
* Departure Handled by Hong Kong
> For Traffic Crossing Hong Kong, Cross Border at or above 5500'
* `ALLEY`: End at `ALLEY`/ `PECAN`
* `CONGA`/ `GRUPA`/`SOUSA`: Ended at `SKATE`/`OCEAN`
* Departure Handled by Guangzhou
* `BIGRO`: Last point in operating Airspace: `BOKAT`
* Suggested Handoff Point: `LATOP`
* `NLG`/`SHL`/`MIPAG`: `LATOP` will be End of Operation (Both Runway)
#### Transition Route
> These TTR are within VHHK TMA for VMMC Approach, which are shortened and Having High chance of Error
* For CHALI Approach
* `ROBIN`: Route from `SANBO`, `SIKOU`, `DUMOL`
* `PECAN`: Entry Point
* For SMT Approach
* `NEDLE`: Route from J101: `ELATO`, `DOTMI`
#### Special Operation
* Runway 16 Runway Extension Line (In-game ILS)
> Due to Unavbl Offset LLZ, Sepcial Setup for better game experience.
* Left Offset 5deg (M163 Sim, M158 Real-life)
* Angle of LLZ: 3.5deg (3deg IRL)
* Runway 16 Offect Localiser Unavailable
* Alternative: Setted up LLZ 16 apch
* LLZ16 Ops: After Alignment on LLZ (ZAO radian 217), DCT give ILS Clearance.
* Immediate Clear ILS after Aligned, or I guarantee you Go Around
* Runway 16 Circle to Land
* PAPA Inbound, Approach Route Reference ONLY
* Left Holding at MCU (Default) , Speed Max 160kt
* Go Around Speed
* Default Go Around: 2000', 200kt
* Suggested Ops: <3000', <180kt
* Remains inside VMMC ATZ for Go Around Traffic
### `VHHX` Hong Kong Airport (aka Kai Tak Airport)
Kai Tak Airport (Depreciated)
Name: VX
Runway 13/31 (Special Operation on 13)
VX ATZ has included in *v1.0*
### `VHSK` Shek Kong Airport
Shek Kong airport, Millitary Airport
Shall Not expect simualtion in EATC
## Known Issues
* VHHX Kai Tak WIP
### Hong Kong Int'l Airport
Due game bug, While Both runway operation either only departure or both departure and arrival, the ILS of South Runway will be active. Beware double click the APP button to choose Northern 07L/25R Runway.
### Macau Airport
All Issues Included inside Macau Airport / Special Operation
## Disclaimer
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that the representation of Hong Kong FIR /TMA, Macao TMA, Guangzhou FIR and Zhuhai TCA matches real life procedures in any way. Any information regarding inaccuracies is appreciated.
All right reserved
## For Developers
For further infomative version, consider PC version developed by ckwng.
## Resources used
* [eAIP](https://www.ais.gov.hk/) by CADHK
* [ATIS](atis.cad.gov.hk/) by CADHK
* from [IVAO HK](https://xe.ivao.aero) (Currently Sub-division of XE)
* from [Civil Aviation Department Hong Kong](https://www.cad.gov.hk/)
* from [Airport Authority Hong Kong](https://www.hongkongairport.com/)
* from Hong Kong Government
* Special Thanks: README.md template from RJTT_readme.md by [ckwng](https://github.com/AdamJCavanaugh/EndlessATCAirports/commits?author=ckwng)
## Changelog
* 1.0 ( / ) - 2020/12/31 - Initial version.
* 1.1 ( / ) - 2021/01/01 - HotFix: North Border
* 1.2 ( / ) - 2021/01/03 - Included ZGZUTM04 Airspace / VMMC Border line.
* 1.3 (p1.3) - 2021/01/10 - File Name Conflict Update, Extra Information Inc.
* 1.4 (p1.4) - 2021/01/18 - VMMC/MCU Macau Airport Integration (VHHX Reserve Name Update)
* 1.4 Suppliments: Game File Clean-up Comments, Readme file remove extra lines
* 1.4.2 - 2021/02/08 - Readme Format Update
## License
All Rights Reserved
Copyright (c) 2021 ycohui
Map data for EndlessATC included / retrieved by ycohui
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
final/AS/JPN/ROAH.txt
+3589
View File
File diff suppressed because it is too large Load Diff
final/AS/JPN/ROAH_readme.md
+177
View File
@@ -0,0 +1,177 @@
**DUE TO NATURE OF TRAFFIC AT THE `ROAH` AERODROME, THIS AIRPORT FILE HAS QUIRKS RELATED TO MILITARY AIRCRAFT TO/FROM `ROAH`.**
# `ROAH` ACA 1.0.0
This is an implementation of the Naha ACA (Approach Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `ROAH` Naha Airport in Okinawa, Japan, as well as `RODN` Kadena Air Base and `ROTM` MCAS Futenma. The airspace ceiling is FL200.
Based on AIP Japan (Ministry of Land, Infrastructure, Transport and Tourism) (https://aisjapan.mlit.go.jp/html/AIP/html/DomesticAIP.do). The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs are implemented unless there is no RNAV alternative. Coastline data from naturalearthdata.com.
The Naha ACA is a mostly circular terminal area typical for an island airport. There is a heavy military presence, and military training areas are scattered around the main island as well between the airways that extend out from the Naha `NHC` VORTAC. Approach and departure paths cross over/under each other just north of Naha, and there are many potential conflict points to the west/east of Okinawa as well. The majority of traffic enters the ACA from the northeast from mainland Japan and southwest from the other Ryukyu islands such as Miyakojima and Ishigaki. USAF training area W-178(A) is depicted as inactive for gameplay purposes. Expect heavy use of vectors, especially as traffic increases.
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix, to the same airport or even different airports. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
`ROKR` Kerama, `RORA` Aguni, `RORE` Iejima, and `RODE` Ie Shima Auxiliary are not represented due to a lack of traffic to/from outside of the ACA. However, the runways of the former three airports are shown on the map.
## Airports
### `ROAH` Naha
The main airport of this sector. Jointly used by civilian and JSDF traffic, this airport on the southern tip of Okinawa Island has added a new parallel runway in the sea to the west in response to increased traffic including the increases in scrambles of fighter jets. Unlike Chitose in Hokkaido, civilian and military traffic use the same runways, meaning passengers onboard airliners are able to see fighters taking off with afterburners from their window seat.
As a controller, the mix of aircraft may be more exciting than the normal airport, but will need attention when the `F16` zooming along catches up to the `AT46`... STARs are available, however in real life vectors are used heavily.
**SOME MILITARY AIRCRAFT (`F16`, `T4`, `P3`, `E2`) ARE DEPICTED AS AIRCRAFT LANDING AT "`JF`" AERODROME FOR TECHNICAL REASONS. THESE AIRCRAFT SHOULD LAND AT `ROAH`.**
There is custom traffic for `ROAH`. The proportions are very much estimates but shouldn't be too far off from reality.
Major fixes on the map have a defined hold including many fixes along the STARs. The published hold for missed approaches is `OLVAL`.
Aircraft arrive at 3 points:
- `PRIUS` -`Y525`-> `IHEYA` (north/north east from mainland Japan/Korea)
- `GEMNI` -`Y57`-> `VELNO` (southwest from western Ryukyu Islands/Taiwan)
- `BUICK` -`V75`-> `NANJO` (east from Daito Islands/Pacific Ocean)
Aircraft depart via:
- `CHAMP` (north via `Y579` to Korea)
- `AMAMI` (north/northeast via `Y574`/`Y53`/`Y25` etc. northeast for mainland Japan)
- `BUICK` (east via `V75` for Daito Islands/Pacific Ocean)
- `GANJU` or `CANOP` depending on runway (southwest for western Ryukyu Islands/Taiwan)
There are two runways:
- 18L/36R
- 18R/36L (new west parallel runway)
Two landing configurations are in general use:
- Landing 36L, departing 36R
The west runway is used for arrivals while the east runway is used for departures. In real life, traffic may land 36R for a shorter taxi if traffic allows.
Approaches to 36L are available from `BLISS`.
STARs are available using APP mode from `IHEYA`, `VELNO`, `BUICK`, and some intermediate points on the STARs. Military aircraft may only engage app mode from certain outer fixes due to technical reasons; recommend vectors to final if not suitable STAR available.
Use caution for departures towards `KIZNA` conflicting with 05 arrivals to `RODN`. Vectoring may be required to the west at altitude 1200 to clear `RODN` 05 arrivals descending through 2200 at `JIMMY`.
Simultaneous approaches to 36L and 36R are NOT authorized.
- Landing 18R, departing 18L
The west runway is used for arrivals while the east runway is used for departures. In real life, traffic may land 18L for a shorter taxi if traffic allows.
Approaches to 18R are available from `SALSA`.
STARs are available using APP mode from `IHEYA`, `VELNO`, `BUICK`, and some intermediate points on the STARs. Military aircraft may only engage app mode from certain outer fixes due to technical reasons, **except for from `VIGER`**. **FOR `JF` AIRCRAFT, TO INITIATE AN APPROACH FROM `VIGER`, USE THE SECOND APPROACH BY SELECTING "APP" TWICE. THE ASSIGNED APPROACH SHOULD BE TO RWY `18LJF` VIA 15 DME ARC CCW. *`JF` aircraft will go around if the runway selected is `18L`.*** Recommend vectors to final if not suitable STAR available.
Use caution for arrivals conflicting with 05 arrivals to `RODN`. `RODN` arrivals may need to held over `JACKS` for a gap in `ROAH` arrivals.
Simultaneous approaches to 18L and 18R are NOT authorized.
### `RODN` Kadena Air Base
This is the USAF's home in Okinawa. A variety of aircraft, military or chartered civilian, fly in and out of this aerodrome going to training areas or other USAF bases in Japan/Guam/USA.
There is custom traffic for `RODN`. The proportions and callsigns are very much plain guesses however, no assertions are made regarding accuracy (instead, assertions are made regarding its *inaccuracy*.)
Major fixes on the map have a defined hold.
Aircraft depart to ATS routes via `BASHO` `BUICK` `DODGE` or `ONC`, or to the North Range and South Range. There are real life SIDs but they are all just two points in a (mostly) straight line after departure to a waypoint not connected to the ATS routes. Therefore no SIDs are implemented, just a heading after departure. Departures should be vectored until direct to exit point can be issued.
There are two runways:
- 05L/23R
- 05R/23L
There are two simple runway configurations:
- Landing 05L, departing 05R
The north runway is mainly used for arrivals and the south runway is mainly used for departures.
Approaches to 05L are available from `JACKS` etc.
No STARs are available, arrivals should be vectored to `JACKS` or other fixes on the approach.
Use caution for `ROAH` arrivals to 18s or departures from 36s. Arrivals must descend through 2200 at `JIMMY` to remain on GS. Recommend vectors for `ROAH` 36 departures to maintain separation. ~~Recommend holding `RODN` arrivals at `JACKS` until gap can be made in `ROAH` 18 arrivals.~~ **Due to conflicts with `ROAH` 36 departures, 05L has been raised 500ft to displace the glideslope so 05 approaches do not conflict.** However, the `JIMMY` 2200 restriction has been maintained to simulate the original GS.
The published hold for missed approaches is straight ahead to `IMONO`.
- Landing 23R, departing 23L
The north runway is mainly used for arrivals and the south runway is mainly used for departures.
Approaches to 23R are available from `IMONO` etc.
No STARs are available, arrivals should be vectored to `IMONO` or other fixes on the approach.
Use caution for `ROAH` arrivals to 18s or departures from 36s. Departures must climb to at least 2200 to clear. **Due to conflicts between 05 arrivals and `ROAH` 36 departures, 05L/23R has been raised 500ft to displace the glideslope.** However, the altitudes for the fixes along the 23R ILS have been maintained to simulate the original GS.
The published hold for missed approaches is straight ahead to `JACKS`.
### `ROTM` MCAS Futenma
A USN airfield south of Kadena. Most traffic would be helicopters to training areas around Okinawa, but there is some fixed wing traffic to other US military facilities.
There is custom traffic for `ROTM`. The proportions and callsigns are very much plain guesses however, no assertions are made regarding accuracy (instead, assertions are made regarding its *inaccuracy*.)
Aircraft depart to ATS routes via `BASHO` `BUICK` `DODGE` or `ONC`. No SIDs are implemented, just a heading after departure. Departures should be vectored until direct to exit point can be issued.
There is one runway:
- 06/24
There are two simple runway configurations:
- Landing and departing 06
No approach fixes are available, and no STARs are available, arrivals should be vectored to final.
Use caution for `ROAH` traffic under the approach path and parallel `RODN` arrivals to the north.
- Landing and departing 24
No approach fixes are available, and no STARs are available, arrivals should be vectored to final.
Use caution for `ROAH` traffic under the departure path and parallel `RODN` arrivals to the north.
### `ROKJ` Kumejima
A runway with a small apron on this island west of Okinawa. The only scheduled service is to `ROAH` Naha, and a seasonal service to `RJTT` Tokyo Haneda.
There is custom traffic for `ROKJ`. Unfortunately, traffic to `ROAH` cannot be simulated due to the game not supporting this. Only the seasonal traffic to/from the northeast is simulated.
Aircraft depart and arrive via the `NHC` - `LAVON` - `GURUX` - `DORIS` corridor.
There is one runway:
- 03/21
Only one runway configuration is implemented:
- Landing and departing 03
Approaches are available from `DUFFY` and `DORIS`.
The published hold for missed approaches is a *left* turn to `DORIS`.
## Known Issues
- Have different types of traffic use different entry/exit gateways are not possible in this game, therefore aircraft using civil and military routes are separated by duplicating `ROAH`, which means there are two runways each of 18L/36R and 18R/36L. As the game will allow you to select approaches meant for a different airport if they share a starting fix with an approach for the airport the selected aircraft is landing at, this can lead to military aircraft flying the "civilian" approach and going around due to trying to land at the "wrong" airport. To avoid this issue, civil and military aircraft landing `ROAH` do not have approaches that share fixes.
- Many areas have their ceiling marked as "0" as they are likely not active for all of their hours of operation and interfere with standard flight paths, or because they are shared with traffic to different airports (which is not supported by the game)
- No `ROAH`-`ROKJ` traffic
- No `RODN` SIDs - the SIDs are available on the AIP, but the connecting routes to airways are not published as airways or procedures, or even as direct routes or flight planned routes via AIC. Author is only aware of one - `ADDAN` (`DCT`) `BASHO` (`DCT`) `AMAMI`. In fact, `BASHO` does not appear to be used for any other purpose...
## Disclaimer
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that the representation of Naha ACA matches real life procedures in any way. Especially, procedures around `RODN` Kadena and `ROTM` Futenma may be grossly inaccurate, and callsigns for military aircraft are very likely to be either incorrect, out of date, or completely fabricated. Any information (that is not classified or secret in any way) regarding inaccuracies is appreciated.
## For Developers
This file is built from `source\ROAH.txt` via `deploy.py`. Make any contributions to `source\ROAH.txt` and NOT to `.\ROAH.txt`.
## Changelog
* 1.0 - 2021/02/08 - Initial version.
final/AS/JPN/source/ROAH.txt
+2044
View File
File diff suppressed because it is too large Load Diff
final/AS/JPN/source/common.ini
+10
View File
@@ -0,0 +1,10 @@
[expand.callsigns]
ckstr = check star
rch = reach
cnv7 = convoy 7
cnv3 = convoy 3
madfox = mad fox
pswrd = password
brgham = brigham
vampr = vampire
final/EU/DEU/EDDM.txt
+30 -22
View File
@@ -1,4 +1,4 @@
# EDDM v1.0 # EDDM v1.1
# Munich Airport "Franz Josef Strauß" in the south of Germany. # Munich Airport "Franz Josef Strauß" in the south of Germany.
[airspace] [airspace]
@@ -10,8 +10,9 @@ floor = 3700
descendaltitude = 11000 descendaltitude = 11000
ceiling = 13000 ceiling = 13000
above = 19000 above = 19000
transitionaltitude = 5000 transitionaltitude = 6000
usa = false usa = false
speedrestriction = 2, 250
boundary = boundary =
N48.705608, E11.9316 N48.705608, E11.9316
@@ -110,7 +111,6 @@ beacons =
OTT, N48.18039, E11.81653, 080, Ottersberg OTT, N48.18039, E11.81653, 080, Ottersberg
MAH, N48.26340, E11.31190, 0, Maisach MAH, N48.26340, E11.31190, 0, Maisach
IGL, N48.71780, E11.56980, 0, Ingolstadt IGL, N48.71780, E11.56980, 0, Ingolstadt
OBI, N48.08060, E11.28540, 0, Oberpfaffenhofen
WLD, N48.57940, E11.12940, 0, Walda WLD, N48.57940, E11.12940, 0, Walda
NEU, N48.71250, E11.21100, 0, Neuburg NEU, N48.71250, E11.21100, 0, Neuburg
AUG, N48.42430, E10.93300, 0, Augusta AUG, N48.42430, E10.93300, 0, Augusta
@@ -119,6 +119,10 @@ beacons =
EUR, N47.73500, E11.24940, 0, Eurach EUR, N47.73500, E11.24940, 0, Eurach
SBG, N48.00260, E12.89280, 0, Salzburg SBG, N48.00260, E12.89280, 0, Salzburg
RDG, N49.04030, E12.52650, 0, Roding RDG, N49.04030, E12.52650, 0, Roding
ROKIL, N48.513314, E11.196725, 126, rokil
BETOS, N48.068056, E11.350000, 067, betos
NAPSA, N48.144167, E12.345556, -273, napsa
LANDU, N48.596361, E12.273928, -213, landu
line1 = line1 =
N48.45291, E10.12717 N48.45291, E10.12717
@@ -158,18 +162,14 @@ runways =
rwys, 08R, N48.3407, E11.751, 83.4, 13123, 0, 0, 1486 rwys, 08R, N48.3407, E11.751, 83.4, 13123, 0, 0, 1486
entrypoints = entrypoints =
40, miq 40, landu
100, ott 100, napsa
120, ott, 120, napsa
130, ott 130, napsa
220, ott, 220, betos
230, ott, 230, betos
300, miq 300, rokil
320, miq 320, rokil
sids =
INPUD, N48.6671, E11.5414, Inpud
TULSI, N47.7016, E11.7887, Tulsi
climbaltitude = 7000 climbaltitude = 7000
@@ -184,28 +184,34 @@ airlines =
AMC, 1, A320/A20N, Air Malta, s AMC, 1, A320/A20N, Air Malta, s
ANA, 1, B789, All Nippon, ne ANA, 1, B789, All Nippon, ne
AUA, 2, A320/A319, Austrian, e AUA, 2, A320/A319, Austrian, e
AUI, 2, B738, Ukraine International, e AUI, 2, B738/E190, Ukraine International, e
AVA, 1, B788, Avianca, w
AZA, 2, A319/A320/E175, Alitalia, s AZA, 2, A319/A320/E175, Alitalia, s
AZO, 1, SU95, Azimuth, ne AZO, 1, SU95, Azimuth, ne
BAW, 3, a319/a320/a21n/a20n, Speedbird, nw BAW, 3, a319/a320/a21n/a20n, Speedbird, nw
BCS, 1, a306/b752, eurotrans, n
BLA, 1, B735/B738, Blue Air, se BLA, 1, B735/B738, Blue Air, se
BRU, 1, E195, Belarus Avia, ne BRU, 1, E175, Belarus Avia, ne
BTI, 1, bcs3, Air Baltic, ne BTI, 1, bcs3, Air Baltic, ne
CAI, 1, B738, Corendon, sew CAI, 1, B738, Corendon, sew
CCA, 1, a359/b77w, Air China, ne CCA, 1, a359/b77w, Air China, ne
CFG, 3, A320, Condor, sew
CFG, 1, B752/B753/B763, Condor, sew CFG, 1, B752/B753/B763, Condor, sew
CFG, 3, A320, Condor, sew
CLH, 3, CRJ9, Hansaline CLH, 3, CRJ9, Hansaline
cs-abc, 1, CL30/C560, 0, swne
CTN, 1, dh8d, Croatian, se CTN, 1, dh8d, Croatian, se
D-abcd, 1, C525/C560/E135/J328/A318/A319/A359, 0, swne
DAL, 1, B763/B764/A332/A333, Delta, nw DAL, 1, B763/B764/A332/A333, Delta, nw
DLA, 3, e195, Dolomiti, s DLA, 3, e195, Dolomiti, s
DLH, 10, A319/A320/A20N/A321/E195/CRJ9, Lufthansa DLH, 10, A319/A320/A20N/A321/E195/CRJ9, Lufthansa
DLH, 10, A319/A320/A20N/A321/E195/CRJ9, Lufthansa
DLH, 10, A319/A320/A20N/A321/E195/CRJ9, Lufthansa
DLH, 2, A346/A388, Lufthansa DLH, 2, A346/A388, Lufthansa
DLH, 2, A359, Lufthansa DLH, 2, A359, Lufthansa
EIN, 1, a320, Shamrock, nw EIN, 1, a320, Shamrock, nw
ELY, 1, B738/B739, Elal, s ELY, 1, B738/B739, Elal, s
ETD, 1, B77W/B789/B78X, Etihad, se ETD, 1, B77W/B789/B78X, Etihad, se
EWG, 3, A320/A319, Eurowings EWG, 10, A320/A319, Eurowings
EZY, 2, A319/A320/A20N, Easy, nw EZY, 2, A319/A320/A20N, Easy, nw
FDX, 1, B77L, Fedex, nw FDX, 1, B77L, Fedex, nw
FIN, 2, A320/A321, Finnair, n FIN, 2, A320/A321, Finnair, n
@@ -213,18 +219,19 @@ airlines =
IBK, 2, B738, Nortrans IBK, 2, B738, Nortrans
ICE, 1, b752/b753/b763, Iceland air, n ICE, 1, b752/b753/b763, Iceland air, n
KAC, 1, a20n/B77W, Kuwaiti, se KAC, 1, a20n/B77W, Kuwaiti, se
KLM, 2, b738/b737/e190, KLM, nw KLM, 2, b738/b737/e190/e175, KLM, nw
LGL, 1, dh8d, Luxair, nw LGL, 1, dh8d, Luxair, nw
LOT, 2, b738/e170/e190/e195, Pollot, e LOT, 2, b738/e170/e190/e195, Pollot, e
MSR, 1, B738, Egyptair, s MSR, 1, B738, Egyptair, s
NAX, 1, B738, Norshuttle, n NAX, 1, B738, Norshuttle, n
OMA, 1, A333, Oman Air, s OMA, 1, A333, Oman Air, s
PGT, 2, A320/A20N, Sunturk, se PGT, 2, A320/A20N/B738, Sunturk, se
QTR, 2, b77w/a359, Qatari, se QTR, 2, b77w/a359, Qatari, se
RAM, 1, B738/E190, royal air maroc, sw RAM, 1, B738/E190, royal air maroc, sw
RJA, 1, a319/a321, Jordanian, nse RJA, 1, a319/a321, Jordanian, nse
ROT, 1, A318/B738/B733, Tarom, se ROT, 1, A318/B738/B733, Tarom, se
RYR, 1, B738, Ryanair, n RYR, 1, B738, Ryanair, n
SAA, 1, a332/a343/a346, springbok, s
SAS, 3, crj9/a20n/b738/b737, Scandinavian, n SAS, 3, crj9/a20n/b738/b737, Scandinavian, n
SBI, 1, b738/a320/a20n, Siberian, ne SBI, 1, b738/a320/a20n, Siberian, ne
SDM, 1, A319, Rossiya, ne SDM, 1, A319, Rossiya, ne
@@ -236,12 +243,13 @@ airlines =
TAP, 2, a319/a320/a20n/a21n/a321/e190, Airportugal, nsw TAP, 2, a319/a320/a20n/a21n/a321/e190, Airportugal, nsw
TAR, 1, A319/A320, Tunair, s TAR, 1, A319/A320, Tunair, s
THA, 1, B77W, Thai, se THA, 1, B77W, Thai, se
TUI, 3, B738, Tuifly, swe
THY, 1, a319/a320/a332/a333, Turkish, se THY, 1, a319/a320/a332/a333, Turkish, se
THY, 3, a321/a21n/b738, Turkish, se THY, 3, a321/a21n/b738, Turkish, se
TUI, 3, B738, Tuifly, swe
UAE, 1, B77W/A388, Emirates, se UAE, 1, B77W/A388, Emirates, se
UAL, 3, b78x/b789/b788/b763/b764, United, nw UAL, 3, b78x/b789/b788/b763/b764, United, nw
UZB, 1, A20N, Uzbek, e UZB, 1, A20N, Uzbek, e
VDA, 1, A124/IL76, Volga, nswe
VUE, 1, a319/a320/A20N/a321, Vueling, s VUE, 1, a319/a320/A20N/a321, Vueling, s
WIF, 1, E190, Wideroe, n WIF, 1, E190, Wideroe, n
# TODO fix missing E290 # TODO fix missing E290
final/EU/DEU/EDDM_Readme.md
+22
View File
@@ -2,6 +2,12 @@
Second hub of Lufthansa, offering many international and intercontinental routes. Second hub of Lufthansa, offering many international and intercontinental routes.
## Some tips on how it can be played
- The approaches are meant to help coordination during high traffic. In real life the transitions from ROKIL/LANDU/NAPSA/BETOS end on a heading. However, Endless ATC currently requires that approaches end with an ILS approach. So if you want to play realistic, you have to manually vector every plane onto the ILS. During low traffic, controllers usually skip the transitions completely and vector to final, sometimes giving directs to waypoints.
- Departures are cleared to FL70, meaning that they might have to pass below approaching traffic following the transitions. This is one reason why vectoring arriving planes can be handy, as you can keep more space between arrivals and departures
- Skill Cap 16 works fine so that some planes can still depart between the arrivals
## Already working: ## Already working:
- most SIDs exist - most SIDs exist
- various transitions and approach waypoints - various transitions and approach waypoints
@@ -17,4 +23,20 @@ Second hub of Lufthansa, offering many international and intercontinental routes
- runway configs missing - runway configs missing
- check if arrival entry directions make sense, same for descent altitude - check if arrival entry directions make sense, same for descent altitude
## Changelog
### v1.1
- Planes now arrive with clearance to ROKIL, LANDU, BETOS or NAPSA, more like in real life where MIQ/OTT are pretty much never used
- Moved transition altitude to 6000ft, to make transition more realistic for arriving traffic. This is not 100% realistic, but the game does not offer a transition level
- Added new Commercial jets and cargo airlines, also added some airlines I forgot
- Added some explanations on how to play to readme
- Overwriting default speed restriction set by the game, so that planes don't slow down automatically anymore
- Removed OBI VOR because it was next to a waypoint, so it was more annoying than helpful
- Removed unused default sids
### v1.0
Initial version
**Feedback or improvements? Create an issue or contribute directly: https://github.com/AdamJCavanaugh/EndlessATCAirports#contributing** **Feedback or improvements? Create an issue or contribute directly: https://github.com/AdamJCavanaugh/EndlessATCAirports#contributing**
final/EU/FIN/EFOU.txt
+288
View File
@@ -0,0 +1,288 @@
[airspace]
elevation = 47
center = N64.9300994873, E25.3546009064
magneticvar = 8.024
radius = 40 ; airspace radius in NM
zoom = 7.0 ; default zoom level, increase to zoom in
elevation = 13 ; ground altitude in feet
floor = 1500 ; minimum selectable altitude
descendaltitude = 10000 ; minimum initial altitude for arrivals
ceiling = 9000 ; maximum selectable altitude
above = 37000 ; maximum departure altitude when SID is enabled (must be above ceiling)
transitionaltitude = 5000 ; highest altitude displayed in feet instead of flight level
speedrestriction = 15, 220 ; radius in NM, and speed in knots
usa = false ; American-style callsign pronunciation and runway names
metric = false ; display altitudes in metres instead of feet
separation = 3 ; minimum allowed distance between aircraft in NM
beacons =
OUK, N64.93160, E25.35930, 0, Oulu
LAA, N64.96630, E25.21120, 0, Laanila
TP, N64.88450, E25.53160, 0, Tango-Papa
VA, N64.12950, E24.64280, 0, Victor-Alfa
SUVIB,N64.25.55.00,E25.07.44.000 , 0 SUVIB
IXONO,N064.35.30.000,E024.41.07.000,0,IXONO
XEVAP,N064.50.13.000, E024.18.36.000,0, XEVAP
NUBVU,N065.12.04.000, E025.45.11.000,0,NUBVU
UGMOR,N064.39.40.000, E026.08.30.000,0,UGMOR
ABKEM,N064.28.55.000, E025.48.41.000,0,ABKEM
MIKNU,N064.26.39.000,E025.26.14.000,MIKNU
OSMAM,N064.46.02.320,E025.36.37.670,OSMAM
GITVU,N065.01.15.460,E024.59.42.200,GITVU
ADKIN,N064.50.17.870,E025.42.41.880,ADKIN
line1 =
N65.08643, E24.78604
N65.07397, E24.65117
N65.04287, E24.57656
N64.97856, E24.57861
N64.95781, E24.69893
N64.99102, E24.84824
N65.02627, E24.89180
N65.03872, E24.99756
N65.05532, E24.97061
N65.08643, E24.78604
line2 =
N65.80654, E22.62031
N65.87095, E22.74658
N65.78647, E22.91934
N65.73535, E23.10234
N65.74990, E23.15459
N65.78613, E23.22109
N65.80435, E23.41836
N65.80532, E23.59209
N65.82852, E23.69141
N65.78223, E23.89053
N65.80527, E24.15547
N65.81235, E24.23750
N65.78047, E24.40430
N65.82202, E24.53262
N65.85835, E24.59160
N65.85918, E24.62803
N65.83169, E24.62324
N65.75713, E24.58154
N65.67070, E24.67490
N65.65640, E24.76426
N65.66035, E24.83936
N65.54629, E25.24180
N65.47925, E25.34785
N65.35273, E25.30791
N65.24321, E25.29785
N65.14326, E25.25586
N65.09863, E25.34023
N65.06514, E25.36230
N65.00947, E25.37266
N64.98428, E25.27109
N64.95103, E25.22803
N64.91641, E25.28076
N64.86035, E25.28818
N64.85347, E25.21426
N64.87520, E25.13428
N64.88403, E24.94219
N64.85210, E24.74756
N64.80630, E24.65762
N64.80103, E24.55791
N64.73867, E24.53018
N64.68013, E24.44063
N64.51528, E24.27832
N64.38599, E24.02227
N64.27412, E23.92480
N64.25825, E23.86143
N64.13418, E23.65293
N64.04092, E23.59893
N64.03447, E23.49395
line3 =
N64.39116, E26.77988
N64.41499, E26.81465
N64.44038, E26.83086
N64.46948, E26.81387
N64.50542, E26.82676
N64.52998, E26.86611
N64.52329, E27.11182
N64.49668, E27.21367
N64.41392, E27.21729
N64.36929, E27.26162
N64.33042, E27.36543
N64.33906, E27.46914
N64.38047, E27.57822
N64.39668, E27.72695
N64.38135, E27.92500
N64.33325, E27.91309
N64.30674, E27.92969
N64.30854, E27.88252
N64.30405, E27.80059
N64.28174, E27.73779
N64.24468, E27.76465
N64.23281, E27.85918
N64.20488, E27.94014
N64.17769, E28.05762
line4 =
N64.12119, E28.07334
N64.12808, E28.00947
N64.14478, E27.92891
N64.22480, E27.65264
N64.27446, E27.56240
N64.26958, E27.50645
N64.25049, E27.48115
N64.22979, E27.42070
N64.20918, E27.32285
N64.17339, E27.28223
N64.13071, E27.28750
N64.12036, E27.25850
N64.15791, E27.20010
N64.20088, E27.07324
N64.23848, E26.94248
N64.27778, E26.92070
N64.36162, E26.79297
N64.39116, E26.77988
N64.39116, E26.77988
N64.39116, E26.77988
line5 =
N65.91210, E24.71056
N65.85918, E24.62799
[airport1]
name = Oulu Airport
code = EFOU
runways =
rwy1, 12, N64.9358, E25.3319, 121.0, 8205, 0, 0, 47
sids=
MIKNU
IXONO
UGMOR
ABKEM
## name, position, <pronunciation>
airlines =
FIN, 3, A320, FINNAIR, SUVIB
SAS, 3, A320, Scandinavian, IXONO
# you may also give just the name of a beacon from the beacon list
entrypoints =
150,SUVIB
210,IXONO
100,ABKEM
290,XEVAP
[departure1]
runway = rwy1
route1 =
MIKNU1A, MIKNU one alpha
N064.53.39.380,E025.29.40.240
N064.26.39.000,E025.26.14.000
route2 =
IXONO1A, IXONO one alpha
N064.53.39.380,E025.29.40.240
N064.49.23.300,E025.23.37.340
N064.35.30.000,E024.41.07.000
route3 =
ABKEM1A, ABKEM one alpha
N064.53.39.380,E025.29.40.240
N064.28.55.000,E025.48.41.000
route4 =
UGMOR1A, UGMOR one alpha
N064.53.39.380,E025.29.40.240
N064.39.40.000,E026.08.30.000
route5 =
XEVAP1A, XEVAP one alpha
N064.53.39.380,E025.29.40.240
N064.49.23.300,E025.23.37.340
N064.50.13.000,E024.18.36.000
[approach1]
runway = rwy1
beacon = SUVIB
route1 =
369
N64.25.55.00,E25.07.44.000
N064.56.58.180,E024.53.42.380
12, 2300, 210
[approach2]
runway = rwy1
beacon = IXONO
route1 =
004
N064.35.30.000,E024.41.07.000
N064.56.58.180,E024.53.42.380
12, 2300, 210
[approach3]
runway = rwy1
beacon = XEVAP
route1 =
055
N064.50.13.000,E024.18.36.000
N064.56.58.180,E024.53.42.380
12, 2300, 210
[approach4]
runway = rwy1
beacon = ABKEM
route1 =
310
N064.28.55.000,E025.48.41.000
N064.56.58.180,E024.53.42.380
12, 2300, 210
[approach5]
runway = rwy1,rev
beacon = SUVIB
route1 =
021
N64.25.55.00,E25.07.44.000
N064.46.02.320,E025.36.37.670
10, 2300, 210
[approach6]
runway = rwy1,rev
beacon = IXONO
route1 =
056
N064.35.30.000,E024.41.07.000
N064.46.02.320,E025.36.37.670
10, 2300, 210
[approach7]
runway = rwy1,rev
beacon = XEVAP
route1 =
087
N064.50.13.000,E024.18.36.000
N064.46.02.320,E025.36.37.670
10, 2300, 210
[approach8]
runway = rwy1,rev
beacon = ABKEM
route1 =
333
N064.28.55.000,E025.48.41.000
N064.46.02.320,E025.36.37.670
10, 2300, 210
[approach9]
runway = rwy1,rev
beacon = OSMAM
route1 =
021
N064.46.02.320,E025.36.37.670
10, 2300, 210
##############################################################
[configurations]
##############################################################
config1 =
0, rwy1, landstart
config2 =
0, rwy1, landstartrev
## score, identifier, usage, <offsetheading>, <nosid>
# score is the score (skill) at which the runway will be activated
# identifier is a unique runway name specified earlier
# usage is a string (without spaces) that may contain these words: start, land, rev, int, track
# where rev means reversed use (opposite direction), int means intersection departure (takeoffs begin 30% down the rwy), track means backtrack after landing
# offsetheading means planes will fly a specific heading just after takeoff (especially useful for allowing parallel takeoffs with divergent climbout headings)
# nosid option means planes will depart on the given offsetheading, with SID mode disabled
# when rwy configurations are omited, two configs are automatically created, one for each rwy direction, with all runways active
final/EU/FIN/EFOU_readme.md
+7
View File
@@ -0,0 +1,7 @@
Oulu Airport located in northern finland
most flights are from stockholm/helsinki
# Already Working
- sids to the south
- stars from the south
# wip sids and stars from the north(rarely used cause all traffic to the airport is from the south)
tools/common.ini
+20 -1
View File
@@ -1,4 +1,6 @@
[expand.callsigns] [expand.callsigns]
#pax
afl = aeroflot afl = aeroflot
cpa = cathay cpa = cathay
axm = red cap axm = red cap
@@ -81,15 +83,26 @@ hvn = viet nam airlines
vir = virgin vir = virgin
cxa = xiamen air cxa = xiamen air
xax = xanadu xax = xanadu
sky = skymark
akx = alfa wing
jta = j-ocean
jac = commuter
rac = ryukyu
snj = new sky
sfj = star flyer
ttw = smart cat
cbj = capital jet
amu = air macau amu = air macau
bav = bamboo bav = bamboo
jcc = cambo jcc = cambo
ryl = double gold ryl = double gold
sjx = star walker sjx = star walker
ttw = smart cat
kor = air koh-ryo kor = air koh-ryo
jsa = jetstar asia
dkh = air june-yao dkh = air june-yao
twb = tee-way twb = tee-way
#cargo
abw = air bridge cargo abw = air bridge cargo
clx = cargolux clx = cargolux
icv = cargolux italia icv = cargolux italia
@@ -114,6 +127,10 @@ yzr = yangtze river
rmy = raya express rmy = raya express
tmg = tri lines tmg = tri lines
ups = u-p-s ups = u-p-s
oae = cimber
vda = volga
#special
jf = japan force jf = japan force
af = air force af = air force
code = code code = code
@@ -132,6 +149,8 @@ brs = brasilian air force
asy = aussie asy = aussie
ssg = slovak government ssg = slovak government
saa = springbok saa = springbok
jcg = japan coast guard
flc = flight check
[expand.gateways] [expand.gateways]
* = nswe * = nswe
tools/expand.py
+24 -8
View File
@@ -50,6 +50,7 @@ class Airline:
directions: str directions: str
callsigns = None callsigns = None
use_callsigns = True
def __init__(self, callsign, frequency, types, *data, gateways=None): def __init__(self, callsign, frequency, types, *data, gateways=None):
"""Create an airline from an entry in the airlines= list. `data` should be """Create an airline from an entry in the airlines= list. `data` should be
@@ -62,9 +63,17 @@ class Airline:
self.frequency = int(frequency.strip()) self.frequency = int(frequency.strip())
self.types = types.strip() self.types = types.strip()
self.callsign = callsign.strip() self.callsign = callsign.strip()
if Airline.callsigns is not None: if Airline.callsigns is not None and Airline.use_callsigns:
self.pronunciation = Airline.callsigns[callsign] if '-' not in callsign \ if '-' not in callsign:
else Airline.callsigns.get(callsign[:callsign.index('-')], '0') self.pronunciation = Airline.callsigns[callsign]
else:
# if length of key is more than 3, assume it is not registration
key = callsign[:callsign.index('-')]
self.callsign = callsign.strip('_')
# if key length is longer than 3 and key doesn't have match,
# we strip '_' to allow for mil callsigns with length <= 3
self.pronunciation = Airline.callsigns.get(key, key.strip('_')) if len(key) > 3 \
else Airline.callsigns.get(key, '0')
else: else:
self.pronunciation = data[0].strip() self.pronunciation = data[0].strip()
data = data[1:] data = data[1:]
@@ -261,7 +270,8 @@ def process(args, input_file=None):
# read optional header to be written in output # read optional header to be written in output
header = None header = None
if 'meta' in source and 'header' in source['meta']: if 'meta' in source:
if 'header' in source['meta']:
header = ["# " + line for line in source['meta']['header'].splitlines()] header = ["# " + line for line in source['meta']['header'].splitlines()]
header.extend([ header.extend([
"", "",
@@ -271,6 +281,10 @@ def process(args, input_file=None):
"", "",
""]) ""])
header = "\n".join(header) header = "\n".join(header)
if 'callsigns' not in source['meta']:
Airline.use_callsigns = False;
else:
Airline.use_callsigns = source['meta'].getboolean('callsigns');
# remove meta section so it won't be written in output # remove meta section so it won't be written in output
del source['meta'] del source['meta']
@@ -427,10 +441,12 @@ if __name__ == "__main__":
gateways. Default gateways can be specified in a common.ini in the same directory as the source file, or in the folder where gateways. Default gateways can be specified in a common.ini in the same directory as the source file, or in the folder where
this tool is located; gateways= still needs to be defined in an [airport] to activate this feature for the [airport]. this tool is located; gateways= still needs to be defined in an [airport] to activate this feature for the [airport].
\n\n \n\n
In [airport] airlines, the airline <pronunciation> can be omitted given [expand.callsigns] is defined in a common.ini in the In [airport] airlines=, the airline <pronunciation> can be omitted if [meta] callsigns= is true. A lookup will be loaded from
same directory as the source file, or in the folder where this tool is located. The former takes precedence. [expand.callsigns] [expand.callsigns] defined in a common.ini in the same directory as the source file, or in the folder where this tool is
is a list of <code>, <pronunciation>, and the first item in each line of airlines (stripped of a dash and anything after it) located. The former takes precedence. [expand.callsigns] is a list of <code>, <pronunciation>. The first item in each
is used to lookup in [expand.callsigns] to obtain the pronunciation. If nothing is found, pronunication defaults to "0". line of airlines (stripped of a dash and anything after it, hereafter referred to as the "key") is used to lookup in
[expand.callsigns] to obtain the pronunciation. If nothing is found, pronunication defaults to the key if it is longer than
3 characters (assuming it is a military callsign), otherwise it defaults to "0".
\n\n \n\n
In a [approach/transition] route=, specify "@<name>" to "tag" the approach route. Any subsequent [approach] route= can then In a [approach/transition] route=, specify "@<name>" to "tag" the approach route. Any subsequent [approach] route= can then
specify "@<name>" as the last point to chain the approach route tagged as "name" to the end. specify "@<name>" as the last point to chain the approach route tagged as "name" to the end.