Re: Airports, Scenery and Aircraft

Patrick Callahan <[email protected]> Sat, 25 Jul 2026 14:42:56 -0400
Newsgroups gmane.games.flightgear.devel
Message-ID <CACt=GQoQ0VrEEtwv2_2t9sKJD-J_GRVgs10_QjpEq-s_4r0+Dw@mail.gmail.com>
--===============8287771717711972691==
Content-Type: multipart/alternative; boundary="000000000000b493bd065773dd37"

--000000000000b493bd065773dd37
Content-Type: text/plain; charset="UTF-8"

Scott,

Thanks for your comments on my post.   I was unable to find the details you
provided collected in any one place as a brief list of stuff needing work.
Getting your opinion on actual work needed in diverse areas was helpful.

And yeah, I'm all over the place. But complexity is just another bright
shiny object. I need to pick one and do some work.

I'm thinking I can best learn and contribute at this point by writing
documentation in areas that actually need it.

The relationship between geographic source data, WS2.0 and WS3.0 scenery,
Airport data, and the same data in generation software and the running
simulation might be an area that could benefit.  The points I mentioned
about BIKF and KBED would be the motivation.

Perhaps there's a simple fix to what we see in the next branch at these
locations, but it hasn't been addressed since I first noted it months ago.
Anyone with an opinion on where the solution lies is welcome to chime in
anytime, even if their analysis is complex or the cause is obscure.

Maybe a detailed look at the underlying data and processing will help. I'm
certainly willing to take that on if anyone thinks it will actually move
things forward.  If not, there are plenty of bright shiny objects in the
issues list.

-Pat

--000000000000b493bd065773dd37
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Scott,</div><div><br></div><div>Than=
ks for your comments on my post.=C2=A0 =C2=A0I was unable to find the detai=
ls you provided collected in any one place as a=C2=A0brief list of stuff ne=
eding work.</div><div>Getting your opinion on actual work needed in diverse=
 areas was helpful.</div><div><br></div><div>And yeah, I&#39;m all over the=
 place. But complexity is just another bright shiny object. I need to pick =
one and do some work.</div><div><br></div><div>I&#39;m thinking I can best =
learn and contribute at this=C2=A0point by writing documentation in areas t=
hat actually need it.</div><div><br></div><div>The relationship between geo=
graphic source data, WS2.0 and WS3.0 scenery, Airport data, and the same da=
ta in generation software and the running simulation might be an area that =
could benefit.=C2=A0 The points I mentioned about BIKF and KBED would be th=
e motivation.=C2=A0=C2=A0</div><div><br></div><div>Perhaps there&#39;s a si=
mple fix to what we see in the next=C2=A0branch at these locations, but it =
hasn&#39;t been addressed since I first noted it months ago.=C2=A0 Anyone w=
ith an opinion on where the solution lies is welcome to chime in anytime, e=
ven if their analysis is complex or the cause is obscure.</div><div><br></d=
iv><div>Maybe a detailed look at the underlying data and processing will he=
lp. I&#39;m certainly willing to take that on if anyone thinks it will actu=
ally move things forward.=C2=A0 If not, there are plenty of bright shiny ob=
jects in the issues list.</div><div><br></div><div>-Pat</div><div><br></div=
><div><br></div></div>
</div>

--000000000000b493bd065773dd37--


--===============8287771717711972691==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8287771717711972691==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--===============8287771717711972691==--