Inaccurate coordinates from SkyCoord.from_name('HD....')
See original GitHub issueCoordinates returned by SkyCoord.from_name for HD identifiers are almost 1 arcminute from the actual position, e.g., HD97658 = HIP 54906
>>> c_from_hd = SkyCoord.from_name('HD97658')
>>> c_from_hd.to_string(style='hmsdms')
'11h14m32.976s +25d43m19.56s'
>>> c_from_simbad = SkyCoord('11 14 33.161', '+25 42 37.39', unit='hour,degree')
>>> c_from_hd.separation(c_from_simbad).to_string()
'0d00m42.244s'
>>> c_from_hip = SkyCoord.from_name('HIP 54906')
>>> c_from_hip.to_string(style='hmsdms')
'11h14m33.1619s +25d42m37.3902s'
>>> c_from_hd.separation(c_from_hip).to_string()
'0d00m42.2446s'
>>> c_from_hip.separation(c_from_simbad).to_string()
'0d00m00.012s'
EDIT: Code formatting
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
SkyCoord — Astropy v5.2
Computes coordinates at the given offset from this coordinate. from_name (name[, frame, parse, cache]). Given a name, query the CDS name ...
Read more >astropy-workshop/astropy_coordinates.ipynb at main - GitHub
In Astropy, the most common way of representing and working with sky coordinates is to use the SkyCoord object. A SkyCoord can be...
Read more >arXiv:1712.09631v2 [astro-ph.IM] 2 Jan 2018
ing the full accuracy and precision of astropy ... from astropy.coordinates import SkyCoord. >>> sirius = FixedTarget.from_name("Sirius").
Read more >aladin.u-strasbg.fr/java/nph-glu.pl
WS %Description The CDS coordinate translator by Web services %Owner CDS'ws ... DataType $1=M %Test param="HD" %ResultDataType Mime(text/html) %Doc.
Read more >vocab.txt - Hugging Face
... register ##ols stop points ##ient meta ##ement close environ serial more ... kernel vals ##ending ##ls constraint most hd ##apshot ##poch catalog...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It seems the issue is due to very inaccurate positions of Draper catalogue, used by the VizieR resolver. I’ll forward this to my CDS colleagues.
I have more information to share: when querying Sesame asking for all resolvers (
A
flag), you can have indeed have multiple resolvers giving a coordinate. In such a case, it is advised to give priority to Simbad coordinates (the section starting with#=S
) if it is present. We can provide with a PR if that helps. cc @bmatthieu3