Coordinates

Closed

Scenery bug report

Reported by:
CCA8541 on December 26, 2017 9:19 PM

Assigned to:
Julian Lockwood


Although the evaluation is correct,but the coordinates of the airport seems a little bit diifferent from the chart or compare with FSX Scenery(they are 100% aligned)

  • dotsha747 December 26, 2017 9:25 PM


    Could you give more specific details of what isn't aligned? i.e. some examples would help to troubleshoot. Some attachments with what you are seeing wrong would help. I used ortho calibrated with onsite GPS readings when laying things out.

  • CCA8541 December 26, 2017 9:43 PM


    I have no idea why my uploaded image became failed to load....

  • CCA8541 December 26, 2017 9:49 PM


    In my onboard GPS data at Gate C35. the coordinate is 02-45.1N/101-41.5e
    but in jeppesen chart, Gate C31,33,35 IS N02 44.8/E101 42.9. Obiviously there's some deviation....also when I'am taxing on H taxiway, FSX User always have a bit north compare to my scenery...

  • Jan Vogel December 26, 2017 10:51 PM

    The good part about X-Plane is that you can totally fix this yourself! Fire up WED, import the airport from the Scenery Gateway, move everything into the right position, upload it and voila, everything is fine.

    I know it sounds easier said than done, but all X-Plane airports are crowd sourced and Laminar Research will not fix them, only the community can.

    This can get you started (check out the NOTAM tab for a link to a tutorial):

    https://gateway.x-plane.com/

  • dotsha747 December 27, 2017 3:02 AM


    In WED, I have "KLIA SAT-A C35" at:

    decimal degrees: N2.746273380 E101.715370510
    decimal minutes: N2 44.7764028 E101 42.9222306

    It's also what I get in the FMC in 737-800.

    Which is pretty close to what the jepp data has "C31, C33, C35" as, N02 44.8 E101 42.9.

    2.45.1N 101-41.5E is quite far away, almost at the highway entrance to the airport. I'm not sure how you could get that for C35 ... Are you on the latest X-Plane version and scenery?

  • dotsha747 December 27, 2017 3:08 AM

  • CCA8541 December 27, 2017 3:08 AM


    Latest Xplane11.10 from Steam

  • dotsha747 December 27, 2017 3:24 AM


    For the second issue reported, in WED I have the intersection of taxiway H and S4/H3 as 2.74523N 101.714757E.
    This matches quite well in Google Earth.

    screenshots: https://imgur.com/a/7Q1CK

    Is there anyone else getting the misalignments that CCA8541 is reporting?

  • CCA8541 December 27, 2017 3:29 AM


    Is there a possibility that the coordinating system is totally different for Xplane and Prepar3D? I mean despite the longtitude and latitude are the same, but they are just in different position in sim?

  • dotsha747 December 27, 2017 10:31 PM


    I can't think of any good reason to have different coordinate systems between the different sims.

    I did the following test, could you try it in your sim and compare the position readings. Use the dataref editor as this is probably the most accurate position reading you can get.

    • Install fresh X-Plane, Steam Edition
    • Only one add-on, DataRefEditor http://www.xsquawkbox.net/xpsdk/mediawiki/File:DataRefEditor_12-11.zip, subfolder DataRefEditor installed in /raiddata/Steam/steamapps/common/X-Plane 11/Resources/plugins.
    • Launch X-Plane 11.11
    • Main Menu
    • Aircraft: Cessna Skyhawk
    • Location: WMKK Customize: Ramp Start, "KLIA1 SAT-A C35"
    • Select plugin -> dataref editor, show dataref
    • filter "sim/flightmodel/position"
    • read latitude "2.746280" longitude "101.715380"
    • change to external view, and position camera above aircraft
    • Press (M)ap, pop-our, zoom in and click on "You"
    • Drag aircraft to intersection of taxiway H and S4/H3 (as close to the intersection of the yellow lines as possible)
    • I read latitude "2.743526" longitude "101.714762"

    https://imgur.com/a/UlXCW

  • CCA8541 December 27, 2017 10:57 PM


    I have exactly same reading to you in C35, and acceptable readings in intc. of S4/H3……

  • CCA8541 December 28, 2017 6:01 AM


    Issued Solved!!!! A huge thanks to you ,although I found that it was the fault on FSX scenery....RS(a fsx scenery author) made some mistakes on coordinate and cannot aligned to the satellite image....

Airport Identifier WMKK
Scenery Pack ID 42906