<p>Ok, I know the question sounds silly, but please hear me out (at the very end it will probably still be silly though, albeit maybe differently).</p>
<p>I'm trying to create a visualization of the galactic web on different distances measured in v. In 2d and 3d.
I'm using Hyperleda datatabase as the source of data - there are over 2.8 million galaxies with data on redshift. HyperLeda doesn't provide redshift per se, but it provides v, which is cz, so getting redshift is just a question of dividing it by the speed of light. This seems correct, highest one in the database is 7.019723.</p>
<p>The problem I encountered was when I tried to show distances on the visualizations - the radius of my universe was at over 2 times bigger then current estimations
of the radius of the Observable Universe (30.3 billion parsecs compared to  estimated.14.3 billion parsecs).</p>
<p>The problem seem to lie with the &quot;v&quot; (Mean Heliocentric radial velocity, in km/s) from Hyperleda, which I tried to use to estimate the distance in parsecs:</p>
<pre><code>df['d_v_pc'] = (df['v'] / cosmo.H(0)) * 1000000
</code></pre>
<p>where cosmo.H(0)) is Hubble Constant, 69.32 km/Mpc s.</p>
<p>I noticed that the higest v in the data is 2,104,460.</p>
<p>At the same time, GN z11, galaxy with the higest redshift observed, has estimated helio radial velocity of 295,050 ± 119,917 km/s.</p>
<p>So some of the galaxies seem to be moving away over 7 times faster then GN-z11, which doesn't look very correct.</p>
<p>The question is, how can I (can I?) convert the current HyperLeda 'v' (cz) to actual helio radial velocity, that would be in the same order as the one of GN z11,
and which I could in turn use to calculate distance? And why is there such a difference in those numbers?</p>

CC BY-SA 4.0
2022-01-02T09:27:07.480Z
If you look it up in the [NASA Extragalactic Database](http://ned.ipac.caltech.edu/byname?objname=GN-z11&hconst=67.8&omegam=0.308&omegav=0.692&wmap=4&corr_z=1), you will find that GN-z11 has a "V (heliocentric)" of 3,324,699 km/s, which corresponds to z = 11.09. The "295,050" value you're quoting is simply wrong.
Peter Erwin
CC BY-SA 4.0
2022-01-02T09:31:44.063Z
I realize that the Wiki article on GN-z11 has "295,050", with a link to a [Simbad entry](http://simbad.u-strasbg.fr/simbad/sim-id?mescat.velocities=on&Ident=%406231699&Name=%5BBIG2010%5D+GNS-JD2&submit=display+all+measurements#lab_meas), so the error is in the Simbad entry; nonetheless, it's an error.
Peter Erwin
CC BY-SA 4.0
2022-01-02T10:13:18.883Z
@PeterErwin I think the NED value is just $cz$, which isn't the recession velocity. I think $z=11$ should be around $2.5c$.
ProfRob
CC BY-SA 4.0
2022-01-02T14:17:41.650Z
@ProfRob The question is about $cz$ values, not “recession velocities”. The point I was making is that GN-z11 does *not* have a “helio[centric] radial velocity” (i.e., $cz$) of “290,050 km/s”, despite what its Simbad entry says.
Peter Erwin
CC BY-SA 4.0
2022-01-03T12:35:46.197Z
@PeterErwin I've checked other very distant objects, and you ar right, it must be a mistake. To compare:

MACS1149-JD1: 2878008±59958 km/s
EGSY8p7: 2,603,098 km/s
EGS-zs8-1: 2,098,548 km/s
GN-z11 has an invalid entry on Wikipedia.
Jan Niedospial
CC BY-SA 4.0
2022-01-03T12:44:03.397Z
@ProfRob, thank you very much for this. So, I just discovered that to do what I want to do, I have to make explicit assumtions about the universe, omega matter and omega lamda. I decided to follow the most accepted, flat universe with omega matter = 0.3 and omega lambda = 0.7. Now, I'm trying to get through the math here: https://arxiv.org/pdf/astro-ph/0310808.pdf, to get (also new concepts) light-travel distance and co-moving distance. Hopefully when done, the most distant object will be inside the bounds of the Observable Universe :) Not there yet, but I'm really glad I've asked. Thank you.
Jan Niedospial
<redshift><radial-velocity>
How to calculate radial velocity from redshift?
Jan Niedospial
# How to calculate radial velocity from redshift?

(Asked by: username_0 on 2022-01-02)

Ok, I know the question sounds silly, but please hear me out (at the very end it will probably still be silly though, albeit maybe differently).
I'm trying to create a visualization of the galactic web on different distances measured in v. In 2d and 3d.
I'm using Hyperleda datatabase as the source of data - there are over 2.8 million galaxies with data on redshift. HyperLeda doesn't provide redshift per se, but it provides v, which is cz, so getting redshift is just a question of dividing it by the speed of light. This seems correct, highest one in the database is 7.019723.
The problem I encountered was when I tried to show distances on the visualizations - the radius of my universe was at over 2 times bigger then current estimations
of the radius of the Observable Universe (30.3 billion parsecs compared to  estimated.14.3 billion parsecs).
The problem seem to lie with the "v" (Mean Heliocentric radial velocity, in km/s) from Hyperleda, which I tried to use to estimate the distance in parsecs:
df['d_v_pc'] = (df['v'] / cosmo.H(0)) * 1000000

where cosmo.H(0)) is Hubble Constant, 69.32 km/Mpc s.
I noticed that the higest v in the data is 2,104,460.
At the same time, GN z11, galaxy with the higest redshift observed, has estimated helio radial velocity of 295,050 ± 119,917 km/s.
So some of the galaxies seem to be moving away over 7 times faster then GN-z11, which doesn't look very correct.
The question is, how can I (can I?) convert the current HyperLeda 'v' (cz) to actual helio radial velocity, that would be in the same order as the one of GN z11,
and which I could in turn use to calculate distance? And why is there such a difference in those numbers?

**Tags:** redshift, radial-velocity
> **Comments:**
> **username_1**: If you look it up in the [NASA Extragalactic Database](http://ned.ipac.caltech.edu/byname?objname=GN-z11&hconst=67.8&omegam=0.308&omegav=0.692&wmap=4&corr_z=1), you will find that GN-z11 has a "V (heliocentric)" of 3,324,699 km/s, which corresponds to z = 11.09. The "295,050" value you're quoting is simply wrong.  
> **username_1**: I realize that the Wiki article on GN-z11 has "295,050", with a link to a [Simbad entry](http://simbad.u-strasbg.fr/simbad/sim-id?mescat.velocities=on&Ident=%406231699&Name=%5BBIG2010%5D+GNS-JD2&submit=display+all+measurements#lab_meas), so the error is in the Simbad entry; nonetheless, it's an error.  
> **username_2**: @PeterErwin I think the NED value is just $cz$, which isn't the recession velocity. I think $z=11$ should be around $2.5c$.  
> **username_1**: @ProfRob The question is about $cz$ values, not “recession velocities”. The point I was making is that GN-z11 does *not* have a “helio[centric] radial velocity” (i.e., $cz$) of “290,050 km/s”, despite what its Simbad entry says.  
> **username_0**: @PeterErwin I've checked other very distant objects, and you ar right, it must be a mistake. To compare:  MACS1149-JD1: 2878008±59958 km/s EGSY8p7: 2,603,098 km/s EGS-zs8-1: 2,098,548 km/s GN-z11 has an invalid entry on Wikipedia.  
> **username_0**: @ProfRob, thank you very much for this. So, I just discovered that to do what I want to do, I have to make explicit assumtions about the universe, omega matter and omega lamda. I decided to follow the most accepted, flat universe with omega matter = 0.3 and omega lambda = 0.7. Now, I'm trying to get through the math here: https://arxiv.org/pdf/astro-ph/0310808.pdf, to get (also new concepts) light-travel distance and co-moving distance. Hopefully when done, the most distant object will be inside the bounds of the Observable Universe :) Not there yet, but I'm really glad I've asked. Thank you.  

---

## 0 answers

