[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-patch-tracker] [patch #10022] [octave forge] (mapping) Auxillary
From: |
Philip Nienhuis |
Subject: |
[Octave-patch-tracker] [patch #10022] [octave forge] (mapping) Auxillary Latitudes |
Date: |
Sun, 17 Oct 2021 14:44:26 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #9, patch #10022 (project octave):
I compared con2geo with Matlab r2021b:
>> spheroid = referenceEllipsoid ('wgs84');
>> converter = map.geodesy.ConformalLatitudeConverter (spheroid)
converter =
ConformalLatitudeConverter with properties:
Eccentricity: 0.0818
>> chi = [0:15:90]
chi =
0 15 30 45 60 75 90
>> inverse (converter, chi)
ans =
0 15.0965 30.1669 45.1923 60.1662 75.0958 90.0000
>> forward (converter, chi)
ans =
0 14.9041 29.8337 44.8077 59.8332 74.9036 90.0000
In Octave, with con2geo:
>> con2geo (chi)
ans =
0 15.1117 30.1821 45.1923 60.1510 75.0806 90.0000
>> geo2con (chi)
ans =
0 14.9041 29.8337 44.8077 59.8332 74.9036 90.0000
so it seems geo2con.m works properly but con2geo.m's output doesn't match
Matlab.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/patch/?10022>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-patch-tracker] [patch #10022] [octave forge] (mapping) Auxillary Latitudes,
Philip Nienhuis <=