Airport code changes no longer need to be requested through the Gateway bug reporter to be handled by Laminar Research. The X-Plane Airport ID must remain the same, but the appropriate metadata field (ICAO, FAA, IATA, etc.) should be changed in WED, and the modified airport uploaded to the Gateway.
I agree but I have stopped trying to figure out why some Canadian airports like CSE4 are in the system WEDBOT as SE4. I have started work on adding Seaplane Bases in Ontario that are not in the system like CPK8 Black Donald Lake that code was rejected by Julian and is now in the system as XC0002 although it is clearly marked on charts and in Skyvector.
I gave up trying to figure out why. My first attempt at CST3 stated out the same way but it is ok now.
SE4 is now CSE4, and there are missing 1302 codes in the Resources\default scenery\default apt dat\Earth nav data\apt.dat file. I noticed this error after becoming a subscriber to Navigraph and then noticing that I could not find the IFR approaches associated with that airport in the default gps navigators. Here is the missing data:
Airport identifier-code changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, but the appropriate metadata (ICAO, FAA, IATA, etc.) should be inserted in WED, and the modified airport uploaded to the Gateway.
You must be logged in to participate in the discussion
IS SE4
S/B CSE4
see data here :
-https://en.wikipedia.org/wiki/Lachute_Airport
-https://skyvector.com/airport/CSE4/Lachute-Airport
Julian Lockwood July 17, 2018 9:26 PM
Airport code changes no longer need to be requested through the Gateway bug reporter to be handled by Laminar Research. The X-Plane Airport ID must remain the same, but the appropriate metadata field (ICAO, FAA, IATA, etc.) should be changed in WED, and the modified airport uploaded to the Gateway.
fastalan March 13, 2019 7:13 AM
Julian, you cannot simply change the airport id to CSE4, I tried that and received the following error on submission "Unknown airport code CSE4".
I agree but I have stopped trying to figure out why some Canadian airports like CSE4 are in the system WEDBOT as SE4. I have started work on adding Seaplane Bases in Ontario that are not in the system like CPK8 Black Donald Lake that code was rejected by Julian and is now in the system as XC0002 although it is clearly marked on charts and in Skyvector. I gave up trying to figure out why. My first attempt at CST3 stated out the same way but it is ok now.
SE4 is now CSE4, and there are missing 1302 codes in the Resources\default scenery\default apt dat\Earth nav data\apt.dat file. I noticed this error after becoming a subscriber to Navigraph and then noticing that I could not find the IFR approaches associated with that airport in the default gps navigators. Here is the missing data:
1302 city Lachute
1302 country Canada
1302 datum_lat 45.639555556
1302 datum_lon -74.370444444
1302 faa_code CSE4
1302 iata_code
1302 icao_code CSE4
1302 region_code CY
1302 state Quebec
1302 transition_alt 18000
1302 transition_level 18000
And for further reference, here is a link to the discussion that lead to this report (and the confirmed fix) :
https://forum.navigraph.com/viewtopic.php?f=20&t=8037&sid=82beb85aa59e09bd7017d379dfb8e52c
This is my first bug report, so please let me know if you need any further details. And finally, thanks for considering this fix!
-Joe
Julian Lockwood August 9, 2019 3:52 PM
Airport identifier-code changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, but the appropriate metadata (ICAO, FAA, IATA, etc.) should be inserted in WED, and the modified airport uploaded to the Gateway.