KDRO search from the import scenery gateway returns three choices all of which have runway data from MMDO Durango Mexico instead of Durango Colorado , United States 17993 has the correct latitude and longitude but the runway data is listed with the coordinates from mexico.
I was hoping the short description I provided would trigger an inspection that would reveal the problem, No luck there so here is the long version and screenshots.
This is my first flight sim so I am aware of my noob status. I have only one month using x-plane 11. When I first imported KDRO from the scenery gateway I chose 50030 because it was recommended. To my surprise the airport was listed as Durango INTL and the identifier was MMDO. When I clicked on the runway 3/21 the data did not match the location in the lower left corner of the airport display screen. I checked airnav.com and noticed that the RUNWAY data latitude, longitude and heading did not match. I decided to try to fix it myself and imported the meta data with KDRO as the identifier. the new AIRPORT data was changed to the KDRO data that was at the airnav site. But when I clicked on the RUNWAY 3/21 the data was still incorrect. I looked up MMDO and found that the runway data was from that site in Mexico. Sense the airport display screen had a black background which was different than any of the other airport displays I decided I was out of my depth and needed to report this to discover if this anomaly was at my computer or at the scenery gateway site. In the meantime I decided to revert to the parent file ID 17993 and found that the runway data of that file was also the data from the Mexico MMDO airport. I found on this occasion that when I clicked the airport after checking the runway data that the Scenery ID had changed to 53521, I verified by re-importing 50030 and checking the runway data and when I clicked on the airport name the Scenery ID had also changed to 53521. This suggested that the parent file 17993 was the source of the error or had somehow been corrupted. I include screenshots. I hope they are sufficient to illustrate the point.
You must be logged in to participate in the discussion
KDRO search from the import scenery gateway returns three choices all of which have runway data from MMDO Durango Mexico instead of Durango Colorado , United States 17993 has the correct latitude and longitude but the runway data is listed with the coordinates from mexico.
Julian Lockwood February 10, 2018 2:21 PM
Runway co-ordinates are correct. Additional check with WEDBing imagery confirms perfect alignment.
LesOldham February 11, 2018 6:39 AM
I was hoping the short description I provided would trigger an inspection that would reveal the problem, No luck there so here is the long version and screenshots.
This is my first flight sim so I am aware of my noob status. I have only one month using x-plane 11. When I first imported KDRO from the scenery gateway I chose 50030 because it was recommended. To my surprise the airport was listed as Durango INTL and the identifier was MMDO. When I clicked on the runway 3/21 the data did not match the location in the lower left corner of the airport display screen. I checked airnav.com and noticed that the RUNWAY data latitude, longitude and heading did not match. I decided to try to fix it myself and imported the meta data with KDRO as the identifier. the new AIRPORT data was changed to the KDRO data that was at the airnav site. But when I clicked on the RUNWAY 3/21 the data was still incorrect. I looked up MMDO and found that the runway data was from that site in Mexico. Sense the airport display screen had a black background which was different than any of the other airport displays I decided I was out of my depth and needed to report this to discover if this anomaly was at my computer or at the scenery gateway site. In the meantime I decided to revert to the parent file ID 17993 and found that the runway data of that file was also the data from the Mexico MMDO airport. I found on this occasion that when I clicked the airport after checking the runway data that the Scenery ID had changed to 53521, I verified by re-importing 50030 and checking the runway data and when I clicked on the airport name the Scenery ID had also changed to 53521. This suggested that the parent file 17993 was the source of the error or had somehow been corrupted. I include screenshots. I hope they are sufficient to illustrate the point.