[bug #68076] [mapping] geodetic2aer() fails to support scalar local to vector target

Philip Nienhuis <[email protected]> Sat, 21 Feb 2026 07:16:38 -0500 (EST)

Newsgroups	gmane.comp.gnu.octave.bugs
Message-ID	<[email protected]>

Please use the bug tracker to post updates to a bug report.  The mailing list is intended as a read-only notification stream.  Info posted to this mailing list address won't appear in the tracker database where it is most useful.

Update of bug #68076 (group octave):

                Category:         Octave Function => Octave Package
                  Status:                    None => Need Info
                 Release:                  10.3.0 => other
        Operating System:                  Mac OS => Any
                 Summary: [mapping] geodetic2aer() with fails to support
scalar local to vector target => [mapping] geodetic2aer() fails to support
scalar local to vector target

    _______________________________________________________

Follow-up Comment #2:

Forgot to mention that I have several other projects at hand with higher
priority.  Fixing this may not happen in time for the next mapping package
release (planned soon).

Higher dimensions wouldn't be much of an issue; internally it would be along
the lines of (in your example case):

lat = repmat (lat, size (lat0));
## etc.

But ... as all inputs perhaps may have different nrs. of dimensions and maybe
even different dimension magnitudes, finding out the largest nr. of dimensions
and largest dimension of all coordinate inputs, followed by morphing them all
into the same (largest) sizes, is also required.

This same issue applies to most if not all of the other "coordsysA2coordsysB"
functions in the Coordinate systems category, and undoubtedly other mapping
package functions as well.  Quite a bit of sorting out :-)
Nevertheless, it's a good thing you brought up this issue.

Matlab docs say nothing about different numbers and lengths of each
dimension.
What does Matlab return for e.g.:

geodetic2aer (1, 2    , [3 4]  , [4 5], [6 7]        , [8 9])

geodetic2aer (1, [2 3], [3 4 5], [4 5], [6 7; 8 9]   , [8 9])

geodetic2aer (1, 2    , 3      , [4 5], [6 7; 8 9 10], [8 9])

geodetic2aer (1, [2 3], [3 4 5], 3    , [6 7; 8 9]   , [8 9])

?

(Adapted some fields in the bug header as this is about a package, not core
Octave)


    _______________________________________________________

Reply to this item at:

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

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

signature.asc (application/pgp-signature, 228 B)