TheEagle wrote in Mon Sep 05, 2022 11:58 am:I think you have a bit of a misunderstanding right now, @phlash - but no worries, we'll clear that up !
phlash wrote in Wed Aug 31, 2022 9:37 pm:From what I can tell, the current scenery is fine and matches reality quite closely, it's the runway co-ordinates that are wrong.
Which runway coordinates ? Is the scenery runway in the right place, and the HUD / map (Menu -> Equipment -> Map) shows the wrong coordinates, or the other way round ?
I most likely do have a mis-understanding, especially as I was unable to find any design info or docs on how FG loads airport information (perhaps I should write that up on the wiki once I've groked it?
) Rummaging through files in $FGDATA I found apt.dat.gz with all the airport details in. As per my first post, the co-ordinates it contains appear in the HUD right after spawning the UFO, and are wrong compared to reality (at least according to SkyVector), while the terrain itself appears to be correctly placed (ie: if I position the UFO using SkyVector co-ordinates, I spawn on the runway), so hopefully no Terragear rebuild required.
I assumed that the apt.dat.gz file is built from various sources (real world data from somewhere??), possibly also local data maintained in a repository, all put together by some tooling (also unstated..) hence me asking folks who should known how this all works for where this is so I can correct things at source. Of course it may be that apt.dat.gz is entirely manually maintained, on someone's random machine outside any form of version control, which would be unwise
(edited to add) Just found this post:
viewtopic.php?p=208286 which implies that apt.dat originally came from X-Plane, and this repo:
https://sourceforge.net/p/flightgear/fg ... /Airports/ that has a binary gzip file in source control with no provenance