Attached is a WED screen capture of a reasonably close approximation of KEVV since its 04/22 RWY has been lengthened to 10,000 ft. and new terminal added.
According to Air Nav, the FAA has not yet released revised coordinates for this extension and this RWY rebuild also to accommodate heavier aircraft. The RWY has been open since nearly a year ago.
XP's default rendition of EVV's layout is obsolete back to the 1960's when its new terminal was constructed, see Wiki.
You will see in this attachment an exclusion to which I've surrounded with an orange outlined box. Within this area there is a severe hump in default scenery which must be leveled before KEVV can ever be updated as it affects the TXWY to 04/22's north end.
Also, since I've expanded 04/22 in my custom build there is an indelible ILS antenna array in the north end of this RWY I cannot find a way to remove.
Default neighborhood scenery (I excluded) must also be deleted in the general area of the new terminal's parking lot where none ever existed I know of.
The latest satellite view of this RWY expansion can be seen in Bing Maps, and only while under construction but verifies the expansion was made.
I can put my build out there onto Dropbox if it will help, but it contains objects from Open Scenery-X.
Please advise me when the default terrain hump is corrected and I'll complete my build and base it upon XP's correction. If you can obtain the new 04/22 coordinates, that would also be great.
Later research has found not a lengthening of RWY 04/22 but a move towards the NNW and reconstructed for heavier aircraft. The southwestern end has been shortened. Air Nav has now reissued updated charts of the changes.
Full remake of the airport by RonB - this issue can be closed.
Robin Peel
commented
in reference to scenery pack
42795on January 19, 2016 5:20 PM
I have moved the localiser and glideslope aerials to their correct locations for the rebuilt runway 04/22. This is in the data release that can be downloaded from the NOTAMs page. The new nav-aid positions are pretty clear on GoogleEarth, even though this still shows the runway itself as under construction.
But, I see errors with the submitted airport design. In real-life, this runway has not been significantly extended (as stated by the author), just shifted to the Northeast (an extension built on the approach end of runway 22, and a section decommissioned on the approach end of 04). The submitted design does not seem to reflect the new taxiway layout, as published on the FAA charts (which seem up to date).
Robin
EBOB_MARSH
commented
in reference to scenery pack
42795on May 4, 2016 11:26 PM
This AP is another example of one where the ground countours in the mesh are incorrect for the runways and taxiways to RW 4-22. This airport requires x-Plane operated with the unchecking of "airport follows land countours" in the rendering screen to work properly. otherwise the lumps in the RW and in the taxiways to RW 4 can catch a prop tip of some AC. With the new release of WED 1.5 airports like this can be selectively set flat as Ben has pointed out. KEVV will need this setting.
This is a great GA Airport with great features and I have generated the taxipaths for it to top off Bruce's fine design. I will submit the TaxiRoute data after a bit more checking of its correctness.
AI Ground Service and AI Taxiing lines crossing one another can throw validation error reports requesting they should be merged, when it seems they should ignore one another,
That is just the way it is. When they are laid down across each other they will normally (although not always) create a node at the crossing point. When they don´t it will show up on validation. Then it is a quick CTRL-E to split or CTRL-M to merge them, just as the validation requests.
Within XP default scenery, there is a roadway conflict crossing RWY 04 at the top of the build. This roadway appears within XP (latest) but does not display within WED's Slippy ESRI or Street Mapping.
Attached is a WED screen capture of a reasonably close approximation of KEVV since its 04/22 RWY has been lengthened to 10,000 ft. and new terminal added.
According to Air Nav, the FAA has not yet released revised coordinates for this extension and this RWY rebuild also to accommodate heavier aircraft. The RWY has been open since nearly a year ago.
XP's default rendition of EVV's layout is obsolete back to the 1960's when its new terminal was constructed, see Wiki.
You will see in this attachment an exclusion to which I've surrounded with an orange outlined box. Within this area there is a severe hump in default scenery which must be leveled before KEVV can ever be updated as it affects the TXWY to 04/22's north end.
Also, since I've expanded 04/22 in my custom build there is an indelible ILS antenna array in the north end of this RWY I cannot find a way to remove.
Default neighborhood scenery (I excluded) must also be deleted in the general area of the new terminal's parking lot where none ever existed I know of.
The latest satellite view of this RWY expansion can be seen in Bing Maps, and only while under construction but verifies the expansion was made.
I can put my build out there onto Dropbox if it will help, but it contains objects from Open Scenery-X.
Please advise me when the default terrain hump is corrected and I'll complete my build and base it upon XP's correction. If you can obtain the new 04/22 coordinates, that would also be great.
Thanks
Bruce Erwin
R Erwin October 12, 2015 11:02 PM
Later research has found not a lengthening of RWY 04/22 but a move towards the NNW and reconstructed for heavier aircraft. The southwestern end has been shortened. Air Nav has now reissued updated charts of the changes.
Jan Vogel February 23, 2021 8:55 AM
Full remake of the airport by RonB - this issue can be closed.
I have moved the localiser and glideslope aerials to their correct locations for the rebuilt runway 04/22. This is in the data release that can be downloaded from the NOTAMs page. The new nav-aid positions are pretty clear on GoogleEarth, even though this still shows the runway itself as under construction.
But, I see errors with the submitted airport design. In real-life, this runway has not been significantly extended (as stated by the author), just shifted to the Northeast (an extension built on the approach end of runway 22, and a section decommissioned on the approach end of 04). The submitted design does not seem to reflect the new taxiway layout, as published on the FAA charts (which seem up to date).
This AP is another example of one where the ground countours in the mesh are incorrect for the runways and taxiways to RW 4-22. This airport requires x-Plane operated with the unchecking of "airport follows land countours" in the rendering screen to work properly. otherwise the lumps in the RW and in the taxiways to RW 4 can catch a prop tip of some AC. With the new release of WED 1.5 airports like this can be selectively set flat as Ben has pointed out. KEVV will need this setting.
This is a great GA Airport with great features and I have generated the taxipaths for it to top off Bruce's fine design. I will submit the TaxiRoute data after a bit more checking of its correctness.
Does not affect using the airport. See attachment.
Julian Lockwood September 2, 2019 8:16 PM
Safe to ignore.
AI Ground Service and AI Taxiing lines crossing one another can throw validation error reports requesting they should be merged, when it seems they should ignore one another,
Jan Vogel March 6, 2021 5:53 AM
That is just the way it is. When they are laid down across each other they will normally (although not always) create a node at the crossing point. When they don´t it will show up on validation. Then it is a quick CTRL-E to split or CTRL-M to merge them, just as the validation requests.
Within XP default scenery, there is a roadway conflict crossing RWY 04 at the top of the build. This roadway appears within XP (latest) but does not display within WED's Slippy ESRI or Street Mapping.
Jan Vogel March 6, 2021 3:22 PM
Fully reworked upgrade to this airport ready to be injected with next XPlane update.