VizieR

CfA VizieR . ADAC VizieR . Cambridge (UK) VizieR . IUCAA VizieR . INASAN VizieR .

Catalog

Looking for catalogs ..
The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.
13 catalogs found

ALL
       or   
      
    
J/ApJ/937/46
(c)
7k
Chandra obs. of the Trifid region & ARCoIRIS sp. (Kuhn+, 2022)
spectrum
img(gal)
    
J/ApJS/253/22
(c)
Ks absolute magnitudes from LAMOST for OB stars (Xiang+, 2021)
img(gal)
    
J/ApJS/268/46
(c)
Kinematics of young open clusters & O-B2-type stars (Liu+, 2023)
img(gal)
    
J/A+A/645/L8
(c)
9k
Parallaxes & proper motions of OB stars from Gaia EDR3 (Xu+, 2021)
img(gal)
    
J/AJ/167/262
(c)
1k
LMI and LDT observation of Berkeley 50 members (Speckert+, 2024)
img(gal)
    
J/MNRAS/487/1400
(c)
15k
Spiral structure as revealed by O and B stars (Chen+, 2019)
img(gal)
    
J/MNRAS/487/2977
(c)
5k
Runaway stellar groups in the Orion A cloud (Getman+, 2019)
img(gal)
    
J/MNRAS/508/2370
(c)
4k
Revisiting the Cygnus OB associations (Quintana+, 2021)
img(gal)
    
J/MNRAS/508/4952
(c)
4k
OB stars in Carina Arm (Drew+, 2021)
img(gal)
    
J/MNRAS/511/6179
(c)
2k
Low-mass cool dwarfs of NYMGs from Gaia EDR3 (Lee+, 2022)
img(gal)
    
J/MNRAS/515/687
(c)
664
Large-scale expansion of OB stars in Cygnus (Quintana+, 2022)
img(gal)
    
J/MNRAS/515/5993
(c)
164
Spectroscopic study of OB stars in Carina Arm (Drew+, 2022)
spectrum
img(gal)
    
J/MNRAS/522/3124
(c)
5k
OB stars and associations in Auriga (Quintana+, 2023)
img(gal)

ALL
       or   
       (c)  indicates tables which contain celestial coordinates 


The following problems were encountered in this VizieR run:
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR1743043.err (2026-02-03T13:16:58)
-2
-kw.cat=36459008
-ref=VIZ6981f54a1a98c3
elapse time 2