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

ALL
       or   
      
    
IX/52
(density 7)
(c)
143k
XXL Survey. DR2 (Chiappetti+, 2018)
2018yCat.9052....0C
Official XXL DR2
img(gal)
    
J/ApJ/814/11
(density 7)
(c)
756
Obscured AGNs from XMM-Newton and AKARI (Terashima+, 2015)
img(gal)
    
J/ApJ/850/66
(density 7)
(c)
Stripe 82X survey multiwavelength catalog (Ananna+, 2017)
img(gal)
    
J/ApJ/888/78
(density 7)
(c)
2k
The ACS-AGN Catalog: AGN luminosity vs SFR (Stemo+, 2020)
img(gal)
    
J/ApJ/941/46
(density 7)
(c)
138
X-ray to FIR observations for an AGN sample (Spinoglio+, 2022)
img(gal)
    
J/ApJS/191/124
(density 7)
(c)
801
Optical spectroscopy of ECDF-S X-ray sources (Silverman+, 2010)
img(gal)
    
J/ApJS/208/24
(density 7)
(c)
Spitzer MIR AGN survey. I. (Lacy+, 2013)
img(gal)
    
J/ApJS/262/15
(density 7)
(c)
X-ray-to-FIR SED data in W-CDF-S, ELAIS-S1 & XMM-LSS (Zou+, 2022)
img(gal)
    
J/AJ/128/1002
(density 7)
(c)
228
SDSS candidate type II quasars. II (Zakamska+, 2004)
img(gal)
    
J/MNRAS/505/4726
(density 7)
(c)
Study of relativistic jets in blazar objects (Keenan+, 2021)
img(gal)
    
J/MNRAS/510/4909
(density 7)
(c)
493
Chandra X-ray's study of LeMMINGs galaxies (Williams+, 2022)
img(gal)
    
J/A+A/418/465
(c)
111
Mid-infrared and hard X-ray emission in AGN (Lutz+, 2004)
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_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_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_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_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_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
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR2108029.err (2025-07-19T01:05:59)
-2
-kw.cat=34180465
-ref=VIZ687aef77202a7d
elapse time 0