Pymap3d

also move to python "src/" directory layout

v2.0 introduced the use of numpy.vectorize to allow seamless pymap3d use with ndarray but also without numpy and scalars. However, this returned 0-d ndarray for certain functions rather than scalars for scalar inputs. This fixes that issue and adds tests for it.

API change: the last releases geodetic2geocentric and geocentric2geodetic have a "alt_m" parameter now. Set it to zero to act like before / Matlab. include the altitude to account for object height above ellipsoid.

Type hinting / quality / refactoring

Added diagnostic plots

Corrected / updated docs and error messages.

Thanks to rpavlick for adding numerous functions in rcurve, rsphere, latitude, lox, utils and more.
These functions each had tests written.
Further, some Numpy functionality that was accidentally removed from v2.0 was restored for v2.1.

The goal of the PyMap3D package remains to support non-Numpy users, while also fully supporting those who have Numpy. The non-Numpy users are typically robots or platforms that stream positions in realtime, and don't need arrays, and want the faster performance of Python's built-in `math` module.

v.2.0.1
also breaking out tests to make easier to read and more comprehensive (checking for singularities, numpy vs scalar, etc.)

* Drop Python 2.x as code duplication and maintenance burden is too high.
* improve numerical stability, thanks bcminch 27
* make non-Numpy use a first-class use case, with all but ECI working without Numpy (let us know if non-Numpy ECI is desirable). Of course Numpy, Pandas and Xarray are still handled first-class as well.
* move CI to GitHub Actions.

Put ellipsoid in own file
put examples in own dir

test python setup.py install as well as python setup.py develop