[Octave-patch-tracker] [patch #10021] [octave forge] (mapping) meridianfwd

[Philip Nienhuis]

Follow-up Comment #16, patch #10021 (project octave):

Sorry for a bit of delay, other patches + real life crept in.

IMO sph_chk.m had better be called "ell_chk.m" as it checks ellipsoids rather
than spheroids (they seem to have different fields). Moreover as it isn't
meant to be a user-callable function   "__ell_chk__.m'  is even better.
I've attached a first draft here, actually a renamed and morphed sph_chk.m

TBD: find a way to get the name of the calling function (for the error
messages). TTBOMK there's no way for that in .m-file functions, so maybe the
caller needs to specify its name as 2nd arg.

I'm wondering if we need to rigidly check all fields. Cf. Matlab, ellipsoids
have defining properties "Code", "Name", "SemimajorAxis", "SemimiorAxis",
"LengthUnit", "InverseFlattening" and "Eccentricity", while "Flattening,
ThirdFlattening", "MeanRadius", "SurfaceArea" and "Volume" are "additional"
(derived?) properties. The latter can be derived / computed using paramcalc
(now a subfunc in referenceEllipsoid.m). We can separate paramcalc and make it
a private function.

What is your opinion on all these points?

The next days/weeks I'll try to work on geodeticfwd and meridianfwd, 
sph_chk/__ell_chk__  is actually an auxilliary thing (maybe even a distraction
:-) ).

(file #51193)
    _______________________________________________________

Additional Item Attachment:

File name: __ell_chk__.m                  Size:2 KB
    <https://file.savannah.gnu.org/file/__ell_chk__.m?file_id=51193>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?10021>

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