<p>Not strictly on-topic, but just in case anyone is interested not so much in the methodology (i. e. querying via <em><a href="https://simbad.u-strasbg.fr/simbad/" rel="nofollow noreferrer">SIMBAD</a></em>) but rather in the result: Using CDS's <em><a href="https://vizier.cds.unistra.fr/viz-bin/VizieR" rel="nofollow noreferrer">VizieR</a></em>-service one can access two relevant catalogues concerning the solar neighbourhood:</p>
<ul>
<li><a href="https://cdsarc.cds.unistra.fr/viz-bin/cat/J/A+A/650/A201" rel="nofollow noreferrer">10 parsec sample in the Gaia era</a> (within 10 parsec of the Sun)</li>
<li><a href="https://cdsarc.cds.unistra.fr/viz-bin/cat/J/A+A/649/A6" rel="nofollow noreferrer">Gaia Catalogue of Nearby Stars - GCNS</a> (within 100 parsec of the Sun)</li>
</ul>

CC BY-SA 4.0
2022-02-26T17:54:17.840Z
It's highly relevant because SIMBAD isn't a catalogue that is easy to interpret and using it as a "source" is fraught with difficulties (like this one).
ProfRob
CC BY-SA 4.0
2022-02-25T19:32:29.373Z
2022-02-25T19:32:29.373Z
CR131873
<p>Well - not sure why distance and parallax tables are empty, but I missed something super simple, the PLX_VALUE column on the BASIC table.</p>
<p><code>SELECT * FROM BASIC  WHERE plx_value IS NOT NULL ORDER BY plx_value DESC</code></p>
<p>OR convert to distance with D = 1000/PLX_VALUE for dist in parsecs</p>

CC BY-SA 4.0
2021-01-11T13:51:56.423Z
Note that taking the reciprocal of the parallax is a biased estimator of the distance. It should only be used where the uncertainty in the parallax is smaller than about 10%. If not, then there is no simple correspondence between parallax and distance.
ProfRob
CC BY-SA 4.0
2021-01-11T07:44:56.027Z
2021-01-11T07:44:56.027Z
user25153
<p>I'm attempting to create a map of all objects within 50LY, including main-sequence stars, binaries, planemos, etc. As such, I'm trying to do it all from first principles, building a micro-ETL to scrape SIMBAD data and build a model. However - I'm experiencing some issues with getting distance measurements from ADGL queries. Watch the following:</p>
<p>Using TAP (<a href="http://simbad.u-strasbg.fr/simbad/sim-tap" rel="nofollow noreferrer">http://simbad.u-strasbg.fr/simbad/sim-tap</a>)</p>
<p><code>SELECT * FROM BASIC WHERE main_id like '%alf%Cen%'</code></p>
<p>Returns 4 rows:</p>
<p><a href="https://i.sstatic.net/8L0eO.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/8L0eO.png" alt="enter image description here" /></a></p>
<p>However - when I check out the mesDistance table with this query:</p>
<p><code>SELECT * FROM mesDistance WHERE oidref IN (3396297, 3396059, 3396054, 7880120)</code></p>
<p>Returns empty.... So maybe there's a missing parent. Let's check h_link</p>
<p><code>SELECT * FROM h_link WHERE parent IN (3396297, 3396059, 3396054, 7880120) OR child in (3396297, 3396059, 3396054, 7880120)</code></p>
<p>Which yields no new objects. 3396059 is the top level object and it has no distance measurement.</p>
<p>However, many other objects show up just fine, such as Proxima Centauri (OID = 3379714 )</p>
<p>It's VERY hit or miss where distance measurements exist and where they don't, but it makes it impossible to query objects based on relative distance. I'm guessing that maybe this has something to do with the age of the catalogs or studies which create a new distance measurement. If a catalog is old enough, it probably wasn't digitized or forced into the SIMBAD ADQL model...</p>
<p>Does anybody have some good suggestions on how to get distance data for nearby stars? Preferably something modern, or with the ability to join it to SIMBAD references. I'd like not to have to do a fuzzy join based on RA/DEC or scraping through alternate IDs. That can get messy or break table grain.</p>

CC BY-SA 4.0
2021-01-11T14:19:15.023Z
Is this parallax data ultimately coming from Gaia? If so, the problem may be that Gaia data skips a few hundred of the brightest stars because of instrument limits.
Steve Linton
<distances><data-analysis><star-catalogues>
SIMBAD TAP queries seem to indicate there are no distance measurements for a great many nearby stars, including Alpha Centauri or Barnard's Star
user25153
# SIMBAD TAP queries seem to indicate there are no distance measurements for a great many nearby stars, including Alpha Centauri or Barnard's Star

(Asked by: username_0 on 2021-01-11)

I'm attempting to create a map of all objects within 50LY, including main-sequence stars, binaries, planemos, etc. As such, I'm trying to do it all from first principles, building a micro-ETL to scrape SIMBAD data and build a model. However - I'm experiencing some issues with getting distance measurements from ADGL queries. Watch the following:

Using TAP (<http://simbad.u-strasbg.fr/simbad/sim-tap>)

`SELECT * FROM BASIC WHERE main_id like '%alf%Cen%'`

Returns 4 rows:

[![enter image description here](https://i.sstatic.net/8L0eO.png)](https://i.sstatic.net/8L0eO.png)

However - when I check out the mesDistance table with this query:

`SELECT * FROM mesDistance WHERE oidref IN (3396297, 3396059, 3396054, 7880120)`

Returns empty.... So maybe there's a missing parent. Let's check h\_link

`SELECT * FROM h_link WHERE parent IN (3396297, 3396059, 3396054, 7880120) OR child in (3396297, 3396059, 3396054, 7880120)`

Which yields no new objects. 3396059 is the top level object and it has no distance measurement.

However, many other objects show up just fine, such as Proxima Centauri (OID = 3379714 )

It's VERY hit or miss where distance measurements exist and where they don't, but it makes it impossible to query objects based on relative distance. I'm guessing that maybe this has something to do with the age of the catalogs or studies which create a new distance measurement. If a catalog is old enough, it probably wasn't digitized or forced into the SIMBAD ADQL model...

Does anybody have some good suggestions on how to get distance data for nearby stars? Preferably something modern, or with the ability to join it to SIMBAD references. I'd like not to have to do a fuzzy join based on RA/DEC or scraping through alternate IDs. That can get messy or break table grain.

**Tags:** distances, data-analysis, star-catalogues

> **Comments:**
> **username_1**: Is this parallax data ultimately coming from Gaia? If so, the problem may be that Gaia data skips a few hundred of the brightest stars because of instrument limits.  

---

## 2 answers

### Answer by username_2 on 2022-02-25. Score: 1

Not strictly on-topic, but just in case anyone is interested not so much in the methodology (i. e. querying via *[SIMBAD](https://simbad.u-strasbg.fr/simbad/)*) but rather in the result: Using CDS's *[VizieR](https://vizier.cds.unistra.fr/viz-bin/VizieR)*-service one can access two relevant catalogues concerning the solar neighbourhood:

* [10 parsec sample in the Gaia era](https://cdsarc.cds.unistra.fr/viz-bin/cat/J/A+A/650/A201) (within 10 parsec of the Sun)
* [Gaia Catalogue of Nearby Stars - GCNS](https://cdsarc.cds.unistra.fr/viz-bin/cat/J/A+A/649/A6) (within 100 parsec of the Sun)

> **Comments:**
> **username_3**: It's highly relevant because SIMBAD isn't a catalogue that is easy to interpret and using it as a "source" is fraught with difficulties (like this one).  

---

### Answer by username_0 on 2021-01-11. Score: 1

Well - not sure why distance and parallax tables are empty, but I missed something super simple, the PLX\_VALUE column on the BASIC table.

`SELECT * FROM BASIC WHERE plx_value IS NOT NULL ORDER BY plx_value DESC`

OR convert to distance with D = 1000/PLX\_VALUE for dist in parsecs

> **Comments:**
> **username_3**: Note that taking the reciprocal of the parallax is a biased estimator of the distance. It should only be used where the uncertainty in the parallax is smaller than about 10%. If not, then there is no simple correspondence between parallax and distance.  

---

