This is what I have done. The ICAO code has been changed to PAAT, but I did not change the Airport ID and attempt to upload it for fear of getting two co-located airports. I tested this out on my system, and this is precisely what occurred. Also, more importantly, setting up an area wide Exclusion zone to 'knock out' PATU doesn't work, as the runway can't be excluded. As I have had to re-position the runway and airport to correct a misalignment, it results in the PATU runway being visible under the PAAT runway.
Bottom line. While the ICAO has been changed in the meta data to PAAT, the ID remains as PATU. This works fine.
Airport ID is wrong. Currently PATU. Should be PAAT.
https://www.airnav.com/airport/PAAT
https://en.wikipedia.org/wiki/Casco_Cove_Coast_Guard_Station
Jan Vogel July 4, 2023 8:40 AM
Can be changed in meta data
CatonaPC July 4, 2023 12:44 PM
This is what I have done. The ICAO code has been changed to PAAT, but I did not change the Airport ID and attempt to upload it for fear of getting two co-located airports. I tested this out on my system, and this is precisely what occurred. Also, more importantly, setting up an area wide Exclusion zone to 'knock out' PATU doesn't work, as the runway can't be excluded. As I have had to re-position the runway and airport to correct a misalignment, it results in the PATU runway being visible under the PAAT runway.
Bottom line. While the ICAO has been changed in the meta data to PAAT, the ID remains as PATU. This works fine.
Jan Vogel July 4, 2023 9:25 PM
Correct. An airportID can never ever be changed - it has to stay whatever it was first. Only the meta data can and should be changed.
Jan Vogel March 30, 2024 5:54 PM
Fixed with latest update, ICAO is correct now in Meta Data.