Re: [Boost-bugs] [Boost C++ Libraries] #11917: geometry default geographic (andoyer) antipodal distance is zero

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11917: geometry default geographic (andoyer) antipodal distance is zero
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-01-17 19:20:16


#11917: geometry default geographic (andoyer) antipodal distance is zero
----------------------------------------+----------------------------------
  Reporter: Ken Barker <ken.barker@…> | Owner: barendgehrels
      Type: Bugs | Status: new
 Milestone: To Be Determined | Component: geometry
   Version: Boost 1.61.0 | Severity: Problem
Resolution: | Keywords: wgs84 distance
                                        | andoyer
----------------------------------------+----------------------------------

Comment (by Ken Barker <ken.barker@…>):

 I agree with Charles Karney's comment above.

 I originally raised this issue after finding an issue with the `Vincenty`
 function, see: http://stackoverflow.com/questions/34767736/why-is-
 boostgeometry-geographic-vincenty-distance-inaccurate-around-the-equato

 On further investigation (and with a bit of help from Charles) I came to
 realise that both the `Vincenty` and `Andoyer` algorithms calculate
 incorrect distances for antipodal points on the equator. Whilst
 [GeographicLib](http://geographiclib.sourceforge.net/) calculates the
 correct distance.

 It should be included in boost geometry and replace `Andoyer` as the
 default algorithm.

 BTW, please note that Charles's link to `GeographicLib` is incorrect,
 please use the one in this comment.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/11917#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:19 UTC