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.
11 catalogs found

ALL
       or   
      
    
J/ApJ/876/70
(density 7)
(c)
28
Massive YSOs in the IR dark cloud G79.3+0.3 (Laws+, 2019) Query images/fits /fits
spectrum/SED
img(gal)
    
J/ApJ/903/145
(density 7)
(c)
ALMaQUEST. IV. ALMA-MaNGA QUEnching & star formation (Lin+, 2020)
img(gal)
    
J/ApJ/929/76
(density 7)
(c)
VANDAM survey of Orion protostars. VI. Disks (Sheehan+, 2022)
img(gal)
    
J/ApJS/236/51
(density 7)
(c)
215
PGCCs in lambda Orionis complex. II. Cores at 850um (Yi+, 2018)
img(gal)
    
J/ApJS/251/20
(density 7)
(c)
212
ALMA survey of Orion PGCCs (ALMASOP). II. 1.3mm (Dutta+, 2020)
spectrum/SED
img(gal)
    
J/A+A/640/A27
(density 7)
(c)
189
Protoplanetary disk masses in NGC 2024 (van Terwisga+, 2020) Query images/fits /fits
image/fits
img(gal)
    
J/AJ/155/54
(density 7)
(c)
465
TBOSS Survey. II. ALMA continuum observations (Ward-Duong+, 2018)
img(gal)
    
J/MNRAS/513/2719
(density 7)
(c)
457
Stellar parameters study with SED fit algo (Vines+, 2022)
img(gal)
    
J/other/PASA/41.55
(density 7)
(c)
2k
YSOs in GRSMC 045.49+00.04 from IR obs. (Azatyan+, 2024)
img(gal)
    
J/ApJ/944/26
(c)
934
YSO candidates in 30 Doradus from IR and ALMA obs. (Nayak+, 2023)
img(gal)
    
J/A+A/696/A151
(c)
6k
ALMAGAL III. Compact source catalog (Coletta+, 2025)
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
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR2704073.err (2026-01-13T11:52:04)
-2
-kw.cat=36960151
-ref=VIZ696631e42942c9
elapse time 2