The unit of `"_r"` suddenly disappeared from the Vizier result table.
- Dominant language
- Python
- Stars
- 791
- Forks
- 451
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 4
Description
Hi, I recently found that the Vizier query no longer gives the unit of angular separation `_r` in the result table, which makes error with previous codes I wrote.
I'm just wondering if this is just a temporary thing or intentional update.
This is one of my result table which I got few days ago,
```
_r RAJ2000 DEJ2000 ... yKmag e_yKmag yFlags
deg deg deg ... mag mag
-------- ------------- ------------- ... ------- ------- --------
0.013524 204.373110760 -9.504518530 ... 15.3153 0.0080 115000
0.016672 204.377877590 -9.502094490 ... 19.7155 0.0360 115000
...
```
and this is a result table now. The unit of `_r` is missing.
```
_r RAJ2000 DEJ2000 _2MASS Jmag ... Bflg Cflg Xflg Aflg
deg deg mag ...
float64 float64 float64 str17 float32 ... str3 str3 uint8 uint8
------- ---------- ---------- ---------------- ------- ... ---- ---- ----- -----
0.134 299.590280 35.201599 19582166+3512057 6.872 ... 111 000 0 0
10.135 299.587491 35.203217 19582099+3512115 10.285 ... 111 c00 0 0
...
```
Thank you!
Contributor guide
Research direction
The issue names only the Vizier query and `_r` result column; start by reproducing a Vizier query and comparing the two table formats shown. Trace the result-table unit handling, then verify that `_r` retains `deg` in a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100