On 2/26/07, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
* Melchior FRANZ -- Sunday 25 February 2007:
> I would fix the files if people agree that what I consider a
> bug is indeed a bug.
I assume that the whole stuff should be dumped and replaced with
geo_*_wgs_84() functions, right? And this is
* Melchior FRANZ -- Sunday 25 February 2007:
> I would fix the files if people agree that what I consider a
> bug is indeed a bug.
I assume that the whole stuff should be dumped and replaced with
geo_*_wgs_84() functions, right? And this is the end of my one-man
thread. :-)
m.
---
* Melchior FRANZ -- Sunday 25 February 2007:
After looking into those files, it looks less dramatic. These
would be the only ones to fix:
> SimGear/simgear/route/waypoint.cxx
> SimGear/simgear/scene/sky/cloudfield.cxx
> SimGear/simgear/scene/sky/cloud.cxx
> FlightGear/src/ATC/approach.cxx
* Melchior FRANZ -- Sunday 25 February 2007:
> Apparently, all users of the functions throughout sg and fg (and
> there are quite some) hacked around this oddness, [...]
And the winners are ...
SimGear/simgear/environment/visual_enviro.cxx
SimGear/simgear/route/waypoint.cxx
SimGear/simgear/
I noticed today that functions calc_gc_course_dist() and calc_gc_lon_lat()
in simgear/math/polar3d.cxx wrongly assume that positive longitude
values are in the West, and negative in the East.
Apparently the functions were copied/adapted from the "Aviation Formulary"
site (http://williams.best.vwh.
5 matches
Mail list logo
