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.
5 catalogs found
  
J/ApJ/761/112
  High-redshift MgII absorption QSOs with FIRE (Matejek+, 2012)
img(gal)
    J/ApJ/761/112/table1(c)FIRE MgII survey sightlines (46 rows)
    J/ApJ/761/112/table2Summary of absorption properties for the FIRE MgII sample (111 rows)
  
J/ApJ/817/55
  NIR spectroscopy of 1.5<z<3.5 broad-band QSOs (Shen, 2016)
spectrum
  
  
J/ApJS/214/23
  IR spectra and photometry of z<0.5 quasars (Shi+, 2014)
spectrum
img(gal)
    J/ApJS/214/23/sample(c)IR photometry and measured features of the PG/2MASS sample (tables 1, 2 and 4)[spectrum] (139 rows)
    J/ApJS/214/23/table3Infrared spectra of the sample (37519 rows)
  
J/ApJS/259/18
  SHELLQs. XVI. New quasars at 5.8<z<7 (Matsuoka+, 2022)
  
    J/ApJS/259/18/table1Journal of discovery spectroscopy (108 rows)
    J/ApJS/259/18/table2Objects detected in the near-IR bands (24 rows)
    J/ApJS/259/18/table3Spectroscopic properties (82 rows)
    J/ApJS/259/18/table4*Spectral classes of the Galactic dwarfs (Note) (31 rows)
  
J/ApJS/261/32
  Finding GPQs. II. Sp. observations of |b|<20° QSOs (Fu+, 2022)
img(gal)
    J/ApJS/261/32/gpqcat(c)Main (Table A1) and extended (Table A2) spectral catalog of the 204 identified quasars behind the Galactic plane (GPQs) (204 rows)
    J/ApJS/261/32/tablec1(c)List of the stellar and galaxy contaminants (19 rows)

ALL
     
       (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
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR1495923.err (2025-07-18T22:55:29)
-2
-kw.cat=18170055
-ref=VIZ687ad0e116d373
elapse time 0