XSG-5075
NH12 Wrong Location, Wrong Name
Closed
Scenery bug report
Reported by:
jschall
on April 21, 2018 3:31 PM
Assigned to:
Julian Lockwood
I'd like to report a default scenery error in XP 11.11 to Laminar Research.
The default airport NH12 has the wrong name and is in the wrong location.
The "real" NH12 is Evans Seaplane Base on the Merrimack River in Manchester, New Hampshire.
In the attached screenshot, "NH12" is on the left, and my "corrected" version of 1P1 Plymouth Muni is on the right.
If NH12 can be corrected (or just removed), then I will request the missing airport 1P1 Plymouth Municipal.
Julian Lockwood April 23, 2018 6:28 PM
Please re-submit from WED to Gateway with corrections applied:
Airport ID must remain unchanged ('NH12'). Airport name, runway locations, other infrastructure, and meta data should be those associated with Evans Seaplane Base.
jschall April 23, 2018 8:38 PM
The AirNav coordinates for NH12 appear to be inaccurate. The WED/WEDOMaker screenshot shows the runway on land rather than several hundred feet South, in the river.
I am unable to upload my scenery pack to the gateway - "validation error".
jschall April 23, 2018 8:41 PM
I am unable to upload my NH12 Scenery Pack - "validation error".
The AirNav coordinates place the Evans Seaplane Base on dry land, several hundred feet from the Merrimack River.
Michael Minnhaar April 24, 2018 12:35 AM
The airport with the X-plane Airport ID NH12 should stay whatever is in that location, so the automatic airport exclusion mechanism can still exclude this airport correctly.
Please set the FAA code meta tag to "1p1", move the grass strip by some 100 feet to its desired location and submit this as the improved location for the Plymouth Muni to the gateway - with an unchanged Airport ID of NH12.
You will also have to fix any validation errors there are to bring this airstrip to the required standards - which mostly entails adding an airport boundary here.
The seaplane base in the Merrimac River will require a new airport ID request prior to submission and that one should have the FAA code set to NH12 when submitting it to the gateway.
The confusion here results from the scenery design internal "Airport ID" and the user visible "Airport Code" coninciding - which is unfortunate, but required for database consistency and unavoidable.
jschall April 24, 2018 1:48 PM
@Michael Minnhaar: Thank you for jumping into this discussion.
I am new to WED and the Scenery Gateway, so I have some questions:
1. I got a "validation error" when I tried to submit a corrected "NH12 Evans Seaplane Base" to the Gateway. Is that an error in my Login details, or an error in the scenery package (there was no Airport Boundary)?
2. What is "the FAA code meta tag, and how is it different from the Airport ID? Are therer separate entries in the scenery package?
3. Are you suggesting that I just change the NH12 Airport Name to Plymouth Muni and its FAA code to 1P1, and of course its position South of Quincy Rd.?
4. And then I should request a "new airport ID request" for Evans Seaplane Base (which is known to the FAA as "NH12")?
jschall April 24, 2018 2:30 PM
OK, I just submitted a corrected package with Airport ID "NH12". The coordinates have been corrected, and the Airport Name changed to "Plymouth Muni".
Now, how does the Airport ID get corrected to "1P1"?
Michael Minnhaar April 24, 2018 2:47 PM
See my post:
"Please set the FAA code meta tag to '1p1' "
The AIrport ID will NOT be changed - it stays NH12.
jschall April 24, 2018 2:55 PM
@Michael Minnhaar: I did see your post, and I asked "What is the FAA code meta tag, and how is it different from the Airport ID?".
I don't see any place in WED or in the submission dialog to enter a code.
Michael Minnhaar April 24, 2018 3:11 PM
Select the Airport line, use Airport -> Add Meta Data -> FAA code, then fill it out.
The Airport ID is just an scenery design internal handle - try to just completely forget that it even exists.
jschall April 24, 2018 3:15 PM
I finally found the "Enter Meta-Data" menu item. Sorry for the ignorance.