I must've tested the wrong way back then as ftp(1) definitely does encode
URL characters if needed, so stop stating otherwise.
`portroach-cli -m .' (showing all ports for all maintainers) yields no
errors (anymore?), so ftp does encode all MAINTAINER values correctly.
i386 fails with SSE errors, aarch64 riscv64 and sparc64 fail when trying
to compile x86 asm. Cut the noise until some brave soul tries to make
this build and run on !amd64.
ok brynet@
Skyfield computes positions for the stars, planets, and satellites in
orbit around the Earth. Its results should agree with the positions
generated by the United States Naval Observatory and their Astronomical
Almanac to within 0.0005 arcseconds (half a "mas" or milliarcsecond).
Skyfield can compute geocentric coordinates or topocentric coordinates
specific to your location on the Earth's surface.
While Skyfield itself has no dependency on the AstroPy library, it's
willing to accept AstroPy time objects as input and return results in
native AstroPy units.
This is a recent short-period ephemeris published by the Jet Propulsion
Laboratory. It requires only 27 MB of storage and is specially accurate
with respect to the position of Earth's Moon.
This package can load and use a Jet Propulsion Laboratory (JPL)
ephemeris for predicting the position and velocity of a planet or other
Solar System body.
Note that jplephem offers only the logic necessary to produce plain
three-dimensional vectors. Most programmers interested in astronomy
will want to look at Skyfield instead, which uses jplephem but converts
the numbers into more traditional measurements like right ascension and
declination.
Most users will use jplephem with the Satellite Planet Kernel (SPK)
files that the NAIF facility at NASA JPL offers for use with their own
SPICE toolkit. They have collected their most useful kernels beneath the
directory: http://naif.jpl.nasa.gov/pub/naif/generic_kernels/spk/
This Python package computes the position and velocity of an
earth-orbiting satellite, given the satellite's TLE orbital elements
from a source like https://celestrak.com/.
It implements the most recent version of SGP4, and is regularly run
against the SGP4 test suite to make sure that its satellite position
predictions agree to within 0.1 mm with the predictions of the standard
distribution of the algorithm. This error is far less than the 1-3km/day
by which satellites themselves deviate from the ideal orbits described
in TLE files.
