Star-planet parans (Brady)
Changed onLatitudes where a fixed star and a planet are angular at the same moment, which is how Brady tabulates a paran: not a place, a latitude. Twelve event pairs per star and planet (rise, set, culminate, anticulminate, minus meridian against meridian, which is a shared right ascension rather than a paran). Each row carries the houses of the technique in plain form: which body does what, the latitude, and the meridian where it happens at this chart moment. Solved on hour angles rather than by intersecting map polylines, so the latitude is exact rather than quantised to the polyline step. horizon selects the geometric horizon (default) or the apparent one at -34 arcmin, measured at about two degrees of paran latitude at mid-latitudes.
Request
- Base URL: https://api.astroway.info/v1
- URL: https://api.astroway.info/v1/parans/star
- Auth: API key in header X-Api-Key
Query parameters
Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.
Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.
Request body
Example request
{
"timezone": "Europe/Kyiv"
}Response
Successful calculation
Example response
{
"ok": true
}Changes
- warning
changed the pattern of the request property
////from^\d{2}:\d{2}:\d{2}$to^\d{2}:\d{2}(:\d{2})?$
- warning
- info
added the new optional
queryrequest parameterfields - info
added the new optional
queryrequest parameterprecision
- info