<p>Trigonometric parallaxes are measured, not calculated.</p>
<p>Simbad reports the source of its parallax measurements if you look carefully. For example, Simbad reports Rigel's parallax as <span class="math-container">$3.78\pm 0.34$</span> milli-arcsecs, which comes from the revised Hipparcos catalogue of <a href="https://simbad.u-strasbg.fr/simbad/sim-ref?bibcode=2007A%26A...474..653V" rel="noreferrer">van Leeuwen et al. (2007)</a> (which will be the case for many bright stars that do not feature in the Gaia catalogue).</p>
<p>A parallax in arcseconds can be reciprocated to give a distance in parsecs. However, if the parallax has a significant uncertainty (say greater than about 10%), then simply reciprocating the parallax is not a correct procedure, because the uncertainty in distance has an asymmetric distribution. In addition, there are various biases to do with the number of stars as a function of distance, which means the likelihood distribution of the distance is biased towards larger values (it is more likely to find a more distant star scattering into a volume, than a closer star scattering out of that volume). This is thoroughly discussed in <a href="https://arxiv.org/abs/1804.09376" rel="noreferrer">Luri et al. (2018)</a> along with (non-trivial) methods for correctly calculating a distance from a parallax (and uncertainty).</p>
<p>Just doing the naive reciprocation of Rigel's parallax gives a distance of 265 pc, with an uncertainty of just under 10%. I'm not sure why you say this is nothing like the other numbers quoted.</p>
<p>Simbad and sky-map.org are not primary sources of parallax or distance information. You should always try to find the primary source.</p>
<p>Betelgeuse has a very uncertain parallax because its angular size on the sky is comparable with its parallax and it has shifting surface brightness inhomogeneities. There are several questions on this site about that. See for example <a href="https://astronomy.stackexchange.com/questions/36365/what-will-it-finally-take-to-accurately-measure-the-distance-to-betelgeuse">What will it finally take to accurately measure the distance to Betelgeuse?</a> and linked questions.</p>

CC BY-SA 4.0
2021-09-26T20:19:23.810Z
Thank you for the detailed answer! I think half the problem was that I didn't realise things would be provided in *milli*-arcseconds, and that `[0.34]` represents uncertainty. It makes a lot more sense now
aggregate1166877
CC BY-SA 4.0
2021-09-26T13:53:20.597Z
2021-09-26T14:08:18.063Z
2021-09-26T14:08:18.063Z
ProfRob
<p>I've been trying to figure out how to convert parallax information from SIMBAD's database into parsecs. Looking at <a href="https://en.wikipedia.org/wiki/Stellar_parallax" rel="nofollow noreferrer">Wikipedia</a> as well as many other sources, parallax is calculated as follows:</p>
<pre><code>distance in parsecs = 1 / parallax
</code></pre>
<p>Given the nature of reciprocals, we can inverse this relationship:</p>
<pre><code>parallax = 1 / distance in parsecs
</code></pre>
<p>The thing is, all stars I've looked up in SIMBAD do not match other sources using these methods.</p>
<p>For example:</p>
<ul>
<li>Rigel, according to <a href="http://www.wikisky.org/starview?object_type=1&amp;object_id=207" rel="nofollow noreferrer">sky-map.org</a> is 236.967 parsecs away (0.0042p | ~773 ly). <a href="https://en.wikipedia.org/wiki/Rigel" rel="nofollow noreferrer">Wikipedia</a> places it at 260 parsecs. <a href="https://simbad.u-strasbg.fr/simbad/sim-basic?Ident=Rigel&amp;submit=SIMBAD+search" rel="nofollow noreferrer">SIMBAD</a> has nothing even close to these numbers.</li>
<li>Betelgeuse, according to <a href="http://www.wikisky.org/starview?object_type=1&amp;object_id=210" rel="nofollow noreferrer">sky-map.org</a> is 131.062 parsecs away (0.0076p | ~427 ly). <a href="https://en.wikipedia.org/wiki/Betelgeuse" rel="nofollow noreferrer">Wikipedia</a> places it at 168.1 parsecs. Again, <a href="https://simbad.u-strasbg.fr/simbad/sim-basic?Ident=Betelgeuse&amp;submit=SIMBAD+search" rel="nofollow noreferrer">SIMBAD</a> has completely different numbers.</li>
</ul>
<p>I've checked a few other stars from SIMBAD as well and the parallaxes seem to be following some other format. They have a <a href="http://simbad.u-strasbg.fr/guide/chG.htx" rel="nofollow noreferrer">description of measurement types</a> page, but it does not seem to indicate how these values are to be interpreted.</p>
<p>How does one actually interpret SIMBAD parallaxes, and how can they be converted to distance in parsecs?</p>

<distances><parallax>
How are SIMBAD's parallaxes calculated?
aggregate1166877
# How are SIMBAD's parallaxes calculated?

(Asked by: username_0 on 2021-09-26)

I've been trying to figure out how to convert parallax information from SIMBAD's database into parsecs. Looking at Wikipedia as well as many other sources, parallax is calculated as follows:
distance in parsecs = 1 / parallax

Given the nature of reciprocals, we can inverse this relationship:
parallax = 1 / distance in parsecs

The thing is, all stars I've looked up in SIMBAD do not match other sources using these methods.
For example:

Rigel, according to sky-map.org is 236.967 parsecs away (0.0042p | ~773 ly). Wikipedia places it at 260 parsecs. SIMBAD has nothing even close to these numbers.
Betelgeuse, according to sky-map.org is 131.062 parsecs away (0.0076p | ~427 ly). Wikipedia places it at 168.1 parsecs. Again, SIMBAD has completely different numbers.

I've checked a few other stars from SIMBAD as well and the parallaxes seem to be following some other format. They have a description of measurement types page, but it does not seem to indicate how these values are to be interpreted.
How does one actually interpret SIMBAD parallaxes, and how can they be converted to distance in parsecs?

**Tags:** distances, parallax


---

## 1 answers

### Answer by username_1 on 2021-09-26. Score: 8 | Accepted answer

Trigonometric parallaxes are measured, not calculated.

Simbad reports the source of its parallax measurements if you look carefully. For example, Simbad reports Rigel's parallax as $3.78\pm 0.34$ milli-arcsecs, which comes from the revised Hipparcos catalogue of [van Leeuwen et al. (2007)](https://simbad.u-strasbg.fr/simbad/sim-ref?bibcode=2007A%26A...474..653V) (which will be the case for many bright stars that do not feature in the Gaia catalogue).

A parallax in arcseconds can be reciprocated to give a distance in parsecs. However, if the parallax has a significant uncertainty (say greater than about 10%), then simply reciprocating the parallax is not a correct procedure, because the uncertainty in distance has an asymmetric distribution. In addition, there are various biases to do with the number of stars as a function of distance, which means the likelihood distribution of the distance is biased towards larger values (it is more likely to find a more distant star scattering into a volume, than a closer star scattering out of that volume). This is thoroughly discussed in [Luri et al. (2018)](https://arxiv.org/abs/1804.09376) along with (non-trivial) methods for correctly calculating a distance from a parallax (and uncertainty).

Just doing the naive reciprocation of Rigel's parallax gives a distance of 265 pc, with an uncertainty of just under 10%. I'm not sure why you say this is nothing like the other numbers quoted.

Simbad and sky-map.org are not primary sources of parallax or distance information. You should always try to find the primary source.

Betelgeuse has a very uncertain parallax because its angular size on the sky is comparable with its parallax and it has shifting surface brightness inhomogeneities. There are several questions on this site about that. See for example [What will it finally take to accurately measure the distance to Betelgeuse?](https://astronomy.stackexchange.com/questions/36365/what-will-it-finally-take-to-accurately-measure-the-distance-to-betelgeuse) and linked questions.

> **Comments:**
> **username_0**: Thank you for the detailed answer! I think half the problem was that I didn't realise things would be provided in *milli*-arcseconds, and that `[0.34]` represents uncertainty. It makes a lot more sense now  

---

