40M: Turkey Mountain Estates WEDBot position is about 4 city blocks west of actual current (FAA.gov, Airnav, 2019 Google image and other sat views) and the X-Plane version sticks out into Table Rock Lake messing up the terrain due to flattening in the wrong place. In addition, 40M, Turkey Mtn Estates is now MO00 per current FAA.gov data. (Mike, Oscar, Zero Zero) Unable to create a 3D airport for MO00 in the correct postion using 40M as ID and MO00 as FAA ID because it won't validate at upload, apparently because of in-correct runway position of 40M. Do I request a new ID for MO00 and also request 40M be removed? Or do I request 40M position be fixed, then wait for that fix and then do my 3D airport using 40M as ID and MO00 as FAA ID?
Or is there another option?
By the way, my current 3D build of MO00 (FAA) with 40M (X-Plane) ID validates in WED 2.04 with gateway target but fails due to 'validation error' (not identified) when I try to submit to gateway. Thanx in advance for help on this. HeadwindH
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.
------------
Airport name and/or location changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, with the new name and/or location in effect.
You must be logged in to participate in the discussion
40M: Turkey Mountain Estates WEDBot position is about 4 city blocks west of actual current (FAA.gov, Airnav, 2019 Google image and other sat views) and the X-Plane version sticks out into Table Rock Lake messing up the terrain due to flattening in the wrong place. In addition, 40M, Turkey Mtn Estates is now MO00 per current FAA.gov data. (Mike, Oscar, Zero Zero) Unable to create a 3D airport for MO00 in the correct postion using 40M as ID and MO00 as FAA ID because it won't validate at upload, apparently because of in-correct runway position of 40M. Do I request a new ID for MO00 and also request 40M be removed? Or do I request 40M position be fixed, then wait for that fix and then do my 3D airport using 40M as ID and MO00 as FAA ID?
Or is there another option?
By the way, my current 3D build of MO00 (FAA) with 40M (X-Plane) ID validates in WED 2.04 with gateway target but fails due to 'validation error' (not identified) when I try to submit to gateway. Thanx in advance for help on this. HeadwindH
Julian Lockwood July 2, 2019 4:49 AM
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.
------------
Airport name and/or location changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, with the new name and/or location in effect.