octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59444] [octave forge] (mapping) missing refer


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #59444] [octave forge] (mapping) missing referenceSphere function
Date: Wed, 11 Nov 2020 17:15:21 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #59444 (project octave):

                  Status:                    None => In Progress            

    _______________________________________________________

Follow-up Comment #5:

Looks good.

Matlab's referenceSphere returns exactly: 

referenceSphere with defining properties:

          Name: 'Earth'
    LengthUnit: 'meter'
        Radius: 6371000
:


rather than 6371008.771415059 m; just a factor of 1e-6 off.
Similar and sometimes larger variations show up for the other celestial
bodies, for completeness here Matlab's outcome (r2014a) in meters:

Sun     694460000
Mercury   2439000
Venus     6051000
Earth     6371000
Moon      1738000
Mars      3390000
Jupiter  69882000
Uranus   25362000
Neptune  24622000
Pluto     1151000


Would you think we'd better follow Matlab exactly here? 
In principle as an earth scientist I'd obviously prefer the other answers, but
assuming a spherical shape for esp. the larger and faster rotating bodies is
already quite far from the truth anyway so I can follow TMW's reasoning to
some extent. Plus, we want to be Matlab compatible don't we.
Easily adapted in the hard-coded 'case' statements.

Other than that option I think it's ready. You can push it or otherwise I can
adapt it if you want and push.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59444>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]